WO2012130020A1 - 业务流管理方法及装置 - Google Patents
业务流管理方法及装置 Download PDFInfo
- Publication number
- WO2012130020A1 WO2012130020A1 PCT/CN2012/071958 CN2012071958W WO2012130020A1 WO 2012130020 A1 WO2012130020 A1 WO 2012130020A1 CN 2012071958 W CN2012071958 W CN 2012071958W WO 2012130020 A1 WO2012130020 A1 WO 2012130020A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- response
- dynamic service
- request
- service
- service management
- Prior art date
Links
- 238000007726 management method Methods 0.000 title claims abstract description 222
- 230000004044 response Effects 0.000 claims description 307
- 238000000034 method Methods 0.000 claims description 142
- 238000012217 deletion Methods 0.000 claims description 70
- 230000037430 deletion Effects 0.000 claims description 70
- 230000005540 biological transmission Effects 0.000 claims description 62
- 230000003139 buffering effect Effects 0.000 claims description 62
- 230000008569 process Effects 0.000 claims description 35
- 238000012544 monitoring process Methods 0.000 claims description 31
- 238000011144 upstream manufacturing Methods 0.000 claims description 7
- 238000011017 operating method Methods 0.000 abstract 1
- 230000004048 modification Effects 0.000 description 52
- 238000012986 modification Methods 0.000 description 52
- 238000010586 diagram Methods 0.000 description 23
- 230000006978 adaptation Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 11
- 230000007246 mechanism Effects 0.000 description 10
- OVGWMUWIRHGGJP-WVDJAODQSA-N (z)-7-[(1s,3r,4r,5s)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@@H]1[C@@H](/C=C/[C@H](O)CCCCC)C[C@@H]2S[C@H]1C2 OVGWMUWIRHGGJP-WVDJAODQSA-N 0.000 description 9
- 101000988961 Escherichia coli Heat-stable enterotoxin A2 Proteins 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 101100161473 Arabidopsis thaliana ABCB25 gene Proteins 0.000 description 7
- 101100096893 Mus musculus Sult2a1 gene Proteins 0.000 description 7
- 101150081243 STA1 gene Proteins 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000010295 mobile communication Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000008439 repair process Effects 0.000 description 5
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 description 4
- 239000002699 waste material Substances 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000002715 modification method Methods 0.000 description 3
- 108700026140 MAC combination Proteins 0.000 description 2
- 238000012508 change request Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 239000012634 fragment Substances 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000007493 shaping process Methods 0.000 description 2
- 229920008347 Cellulose acetate propionate Polymers 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000009470 controlled atmosphere packaging Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 238000009432 framing Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 238000004080 punching Methods 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
Definitions
- the present invention belongs to the field of wireless communications, and in particular, to a service flow management method and apparatus. Background technique
- wireless communication systems have developed rapidly, such as 802.11-based wireless LAN technology WiFi, 802.15-based Bluetooth systems, and Femto technology for indoor applications generated by mobile communication systems. A wide range of applications.
- 802.11-based WiFi technology is one of the most widely used wireless network transmission technologies. Since the WiFi system uses the Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) mechanism, the system efficiency is higher than that of the wireless resources. The root cause of this problem is that the CSMA/CA mechanism is a contention-based random multiple access mechanism, between a central access point (CAP, Access Point) and a station (STA, Station), or between different STAs. The CSMA/CA mechanism will compete for the right to use radio resources, and at the same time compete for the wireless channel. At this time, collision will occur, resulting in waste of radio resources. In order to avoid collisions, the CSMA/CA mechanism requires the CAP or STA to randomly retreat when competing for the wireless channel.
- CAP central access point
- STA station
- 802.11 systems are less efficient. For example: 802. l lg system physical layer peak speed The rate can reach 54Mbps, but the TCP layer can reach no more than 30Mbps under the big packet download service. Despite the above shortcomings, the 802.11 system is flexible and does not rely on a centralized control mechanism, so it can also achieve lower equipment costs.
- the Femto technology based on the 3GPP standard is a new technology for indoor coverage that has evolved from a mobile communication system. Based on the statistics of 3G systems, about 70% of data services occur indoors, so indoor high-rate data access solutions are especially important.
- Femto base stations called pico base stations, are compact (similar to Wi-Fi) and flexible to deploy. Due to the evolution from mobile communication systems, Femto base stations have inherited almost all the characteristics of mobile communication systems. The Femto device only combines its limited coverage and fewer access user features, which reduces the processing power of the device and reduces the cost of the device.
- the duplex mode like the mobile communication system, the Femto base station can be divided into two types of duplex mechanisms: FDD and TDD.
- the uplink and downlink carrier resources of the FDD are symmetric, and the asymmetric service characteristics of the data traffic on the uplink and the downlink make the FDD system have a certain resource waste when facing the data service.
- the uplink and downlink of the TDD system work on the same carrier, and allocates different radio resources to the uplink and the downlink by dividing the time resources. Therefore, the FDD can better adapt to the asymmetric data service of the uplink and downlink services.
- the TDD duplex mode of the mobile communication system including the Femto system
- the static allocation of uplink and downlink resources, and the various types of data services with different needs, such as: browsing web pages, mobile video, mobile games, etc. it is difficult to achieve business needs and resources. Dynamic adaptation of the partition. Compared with Wi-Fi, since Femto uses a scheduling-based centralized control mechanism, there is no waste of radio resources between the base station or the CAP and the terminal or the terminal due to competition conflict and random backoff, so the link efficiency is high.
- the data transmission in the wireless communication system refers to that the communication peer end performs data transmission and reception through interaction, and the interaction may be an interaction between the network side and the terminal, or may be an interaction between the terminals.
- an object of the present invention is to provide a service flow management method and apparatus.
- a business flow management method comprising:
- the response to the dynamic service management request is: an acknowledgment indicating that the dynamic service management request was received correctly.
- the method further includes: carrying, in the dynamic service management request, one or more of a destination identifier, a service parameter, and a direction information, where the direction information indicates that the service flow is uplink or downlink.
- the response to the 40 pairs of dynamic service management requests is: a dynamic service management response carrying the FID and FID maximum buffering capability.
- the method further includes: sending an acknowledgement that the dynamic service management response is correctly received.
- the method further includes: carrying, in the dynamic service management request, one or more of a destination identifier, a service parameter, and a direction information, where the direction information indicates that the service flow is uplink or downlink.
- the dynamic service management response when the dynamic service management request carries the service parameter, the dynamic service management response further carries the adjusted service parameter.
- the method further includes: waiting for the set number of frames after sending the dynamic service management request, resending the dynamic service management request if the response is not received, or ending the current process.
- a business flow management method comprising:
- the response to the dynamic service management request is: an acknowledgment indicating that the dynamic service management request was received correctly.
- the dynamic service management request further includes one or more of a destination end identifier, a service parameter, and a direction information, where the direction information indicates that the service flow is uplink or downlink.
- the response to the 40 pairs of dynamic service management requests is: a dynamic service management response carrying the FID and FID maximum buffering capability.
- the method further includes: receiving an acknowledgement indicating that the dynamic service management response is correctly received.
- the method further includes: waiting for the set number of frames after sending the dynamic service management response, and resending the dynamic service management response if the acknowledgement is not received.
- the dynamic service management request further carries one or more of a destination identifier, a service parameter, and a direction information.
- the method further includes: determining, according to the service parameter carried in the dynamic service management request, the reserved resource, and adjusting the dynamic service according to the reserved resource.
- the service parameters carried in the request are managed, and the adjusted service parameters are carried in the dynamic service management response.
- a service flow management device comprising:
- a request sending unit configured to send a dynamic service management request carrying a maximum buffering capability of the service flow identifier FID and the FID;
- the response receiving unit receives a response to the dynamic service management request.
- the response to the dynamic service management request is: an acknowledgment indicating that the dynamic service management request was received correctly.
- the device further includes: a parameter providing unit, configured to send one or more of the destination identifier, the service parameter, and the direction information to the request sending unit, where the bearer is sent in the dynamic service management request ;
- the direction information indicates that the service flow is uplink or downlink.
- the device further includes: a monitoring unit, configured to monitor the response receiving unit within a set number of frames after the request sending unit sends the dynamic service management request, if the response receiving unit does not receive The response notifying the request sending unit to resend the dynamic service management request.
- a monitoring unit configured to monitor the response receiving unit within a set number of frames after the request sending unit sends the dynamic service management request, if the response receiving unit does not receive The response notifying the request sending unit to resend the dynamic service management request.
- the request sending unit encapsulates the dynamic service management request into a media access control protocol data unit MPDU, and discards the dynamic service management request when resending the dynamic service management request exceeding the number of MPDU retransmissions. And notify the service flow deletion device to perform the operation.
- the response to the dynamic service management request is: a dynamic service management response carrying the FID.
- the device further includes: an acknowledgment unit, configured to send an acknowledgment indicating that the dynamic service management response is correct.
- the device further includes: a parameter providing unit, configured to send one or more of the destination identifier, the service parameter, and the direction information to the request sending unit, where the bearer is sent in the dynamic service management request
- the direction information indicates that the service flow is uplink or downlink.
- the dynamic service management response further carries the adjusted service parameter.
- the apparatus further includes: a monitoring unit, configured to monitor the response receiving unit within a set number of frames after the request sending unit sends the dynamic service management request, if the response receiving unit does not Receiving the response, notifying the request sending unit to end the current process.
- a monitoring unit configured to monitor the response receiving unit within a set number of frames after the request sending unit sends the dynamic service management request, if the response receiving unit does not Receiving the response, notifying the request sending unit to end the current process.
- a service flow management device characterized in that the device comprises:
- a request receiving unit configured to receive a dynamic service management request carrying a maximum buffering capability of the FID and the FID;
- the response sending unit is configured to send a response for the dynamic service management request.
- the response to the dynamic service management request is: an acknowledgment indicating that the dynamic service management request was received correctly.
- the dynamic service management request further includes one or more of a destination end identifier, a service parameter, and a direction information, where the direction information indicates that the service flow to be established is uplink or downlink.
- the response to the 40 pairs of dynamic service management requests is: a dynamic service management response carrying the FID and FID maximum buffering capability.
- the device further includes: an acknowledgment receiving unit, configured to receive an acknowledgment indicating that the dynamic service management response is correctly received.
- the device further includes: a monitoring unit, configured to monitor the acknowledgement receiving unit within a set number of frames after the response sending unit sends the dynamic service management response, if the acknowledge receiving unit does not receive the Confirming that the response sending unit is triggered to resend the dynamic service management response.
- a monitoring unit configured to monitor the acknowledgement receiving unit within a set number of frames after the response sending unit sends the dynamic service management response, if the acknowledge receiving unit does not receive the Confirming that the response sending unit is triggered to resend the dynamic service management response.
- the response sending unit encapsulates the dynamic service management response into an MPDU, and when the retransmission exceeds the number of MPDU retransmissions, discards the dynamic service management response, and notifies the service flow deleting device to perform an operation.
- the dynamic service management request further carries one or more of a destination identifier, a service parameter, and a direction information.
- the device further includes a service parameter adjustment unit, configured to: when the dynamic service management request carries the service parameter, determine the reserved resource according to the service parameter carried in the dynamic service management request, and adjust according to the reserved resource And the service parameter carried in the dynamic service management request, and the adjusted service parameter is sent to the response sending unit, where the bearer is sent in the dynamic service management response.
- a service parameter adjustment unit configured to: when the dynamic service management request carries the service parameter, determine the reserved resource according to the service parameter carried in the dynamic service management request, and adjust according to the reserved resource And the service parameter carried in the dynamic service management request, and the adjusted service parameter is sent to the response sending unit, where the bearer is sent in the dynamic service management response.
- FIG. 1 is a flow chart of a method for establishing a service flow in the present invention
- FIG. 2 is a flow chart of a method for tampering a service flow according to the present invention
- Figure 3 is a reference model of an enhanced ultra-high speed wireless local area network (EUHT) system wireless communication system
- Figure 4 shows the composition of the access system of the EUHT system
- FIG. 5 is a schematic diagram of a process of transmitting and receiving protocol data between a STA and a CAP;
- FIG. 6 is a flowchart of a method for establishing and transmitting data of an uplink service flow according to an embodiment of the present invention;
- FIG. 7 is a dynamic service setup request according to an embodiment of the present invention; Schematic diagram of the structure of the frame;
- FIG. 8 is a schematic structural diagram of a dynamic service setup response frame according to an embodiment of the present invention
- FIG. 9 is a flowchart of a method for tampering and transmitting data of an uplink service flow according to an embodiment of the present invention
- FIG. 10 is a flowchart of a method for establishing and transmitting data of a downlink service flow according to an embodiment of the present invention
- FIG. 12 is a schematic structural diagram of a first service flow establishing apparatus according to the present invention
- Figure 13 is a schematic view showing the structure of the device shown in Figure 12 on the CAP side;
- Figure 14 is a schematic view showing the structure of the device shown in Figure 12 on the STA side;
- FIG. 15 is a schematic structural diagram of a second service flow establishing apparatus according to the present invention.
- Figure 16 is a schematic view showing the structure of the device shown in Figure 15 on the CAP side;
- FIG. 17 is a schematic structural diagram of a first service flow modification apparatus according to the present invention.
- Figure 18 is a schematic view showing the structure of the device shown in Figure 17 on the CAP side;
- Figure 19 is a schematic view showing the structure of the device shown in Figure 17 on the STA side;
- FIG. 20 is a schematic structural diagram of a second service flow modification apparatus according to the present invention.
- Figure 21 is a schematic view showing the structure of the device shown in Figure 20 on the CAP side;
- FIG. 23 is a schematic structural diagram of a first service flow management apparatus according to the present invention.
- Figure 24 is a schematic view showing the structure of the device shown in Figure 23 on the CAP side;
- Figure 25 is a schematic view showing the structure of the device shown in Figure 23 on the STA side;
- 26 is a schematic structural diagram of a second service flow management apparatus according to the present invention.
- Figure 27 is a schematic view showing the structure of the device shown in Figure 26 on the CAP side;
- 29 is a flowchart of a method for deleting an uplink service flow according to an embodiment of the present invention.
- FIG. 30 is a schematic structural diagram of a dynamic service deletion request frame according to an embodiment of the present invention.
- FIG. 31 is a flowchart of a method for deleting an uplink or downlink service flow according to an embodiment of the present invention
- FIG. 32 is a schematic structural diagram of a first service flow deletion device according to the present invention
- Figure 33 is a schematic view showing the structure of the device shown in Figure 32 on the CAP side;
- FIG. 34 is a schematic structural diagram of a second service flow deleting apparatus according to the present invention.
- Figure 35 is a schematic view showing the structure of the device shown in Figure 34 on the CAP side;
- 36 is a flow chart of a first method for establishing a service flow in the present invention.
- 39 is a flow chart of a second method for modifying a service flow according to the present invention.
- FIG. 40 is a flowchart of a third method for establishing a service flow in the present invention.
- 41 is a flowchart of a fourth method for establishing a service flow in the present invention.
- FIG. 1 is a flowchart of a method for establishing a service flow according to the present invention, where the process includes:
- Step 11 Send a dynamic service setup request carrying a service flow identifier (FID) and a destination identifier.
- FID service flow identifier
- Step 12 Receive a response to the dynamic service setup request.
- the service flow corresponding to the FID is established, which may be an uplink service flow or a downlink service flow.
- the service data may be sent on the service flow corresponding to the established FID, and the destination end identifier is not required to be transmitted every time the data is sent, and only the FID is used to indicate the data transmission.
- FIG. 2 is a flow chart of a method for tampering a service flow according to the present invention, where the process includes:
- Step 21 Send a dynamic service repair request with the destination end identifier, FID, and new service parameters.
- the current service parameters corresponding to the FID and the destination identifier can be modified.
- Step 22 Receive 40 responses to the dynamic service modification request.
- the service flow corresponding to the FID is modified, which may be an uplink service flow or a downlink service flow.
- the service data may be sent on the traffic flow corresponding to the FID after the tampering, without carrying the destination identifier every time the data is sent, and only using the FID to indicate the data transmission.
- the above-mentioned service flow establishment and service flow transformation are collectively referred to as service flow management.
- the service flow tampering can be regarded as the establishment of a service flow in a special case, which is equivalent to a service establishment in the case of retaining the original FID.
- the present invention establishes or modifies the "connection" between the requesting end and the destination end by the FID before the data transmission, so that the requesting end and the destination end perform data transmission on the service flow.
- the FID is used as the identifier, it is not necessary to carry the destination identifier in each packet of the interaction, and the operation is completed.
- FIG. 3 is the reference model of the EUHT system.
- the system reference model shown in Figure 3 mainly refers to the air interface reference model, including: Media Access Control (MAC) layer and physical (PHY) layer.
- MAC Media Access Control
- PHY physical
- the MAC layer includes an adaptation sublayer and a MAC sublayer.
- Adaptation sublayer Mainly provides the function of mapping and conversion between external network data and this part of the MAC Data Unit (MSDU).
- MSDU here refers to the information delivered as a unit between MAC Service Access Points (SAP).
- SAP MAC Service Access Points
- the adaptation sublayer completes the function as follows: receiving a service data unit (SDU) from an upper layer;
- MAC sublayer In addition to acting as a media access control function, it also includes management and control of the system and support for specific functions of the PHY layer. Specifically, the basic functions of the MAC sublayer are divided into a management control plane and a data plane.
- the management control plane includes the following functions:
- System configuration manage system configuration messages, and interact with the terminal to configure system configuration information
- Radio resource management Mainly completes the service scheduling function, completes resource allocation based on service parameters and channel conditions, and has functions such as load balancing and access control;
- Network access management responsible for the initialization and access process, generating the messages required for the access process, including: access code selection, capability negotiation, etc.
- QoS management Manage QoS parameters of services and maintain the establishment, tampering and deletion of each service flow;
- the STA that manages no service enters the sleep state, and returns from the sleep state to the active state;
- PHY layer control mainly includes the following sub-functions
- Channel management including channel switching, managing spectrum measurements and message reporting;
- MIMO Management Channel Detection Mechanism; MIMO Operation Mode Determination and Selection; Link Adaptation: Channel Quality Information (CQI) Measurement and Feedback; MCS Selection and Feedback; Power Control and Management.
- CQI Channel Quality Information
- the data plane includes the following functions:
- ARQ Automatic Request Retransmission
- Fragmentation/reorganization according to the scheduling result, the upper layer service data unit is fragmented and sent to the next processing module, and multiple fragments are recombined and restored at the receiving end;
- the upper layer service unit is encapsulated into a basic MAC frame, and then sent to the next processing module;
- MPDU aggregation According to the scheduling result, the originating end performs aggregation operation on the upper layer service data unit.
- 2 PHY layer mainly provides PHY transmission mechanisms for mapping MAC protocol data units (MPDUs) to corresponding physical channels, such as Orthogonal Frequency Division Multiplexing (OFDM) and Multiple Input Multiple Output (MIMO) technologies.
- MPDU here refers to the data unit exchanged between two peer MAC entities using the PHY layer service.
- FIG 4 shows the access system of the EUHT system, including the central access point (CAP) and the station (STA), where the STA can be various data devices, such as: PDA, notebook, camera, camera, mobile phone, tablet and pad. Wait.
- STA1 and STA2 access the CAP through the air interface protocol.
- the CAP establishes communication with existing external networks (such as IP backbone network and Ethernet) through wired or wireless.
- the protocol component of the CAP includes a MAC layer and a PHY layer.
- the STA protocol consists of an Application layer, a Transmission Control (TCP) layer, a Network (IP) layer, a MAC layer, and a PHY layer.
- FIG. 5 shows the process of transmitting and receiving protocol data between the STA and the CAP.
- the STA wants to send data to the CAP, and the STA first applies the application data (such as VoIP, video, etc.).
- the application layer and the TCP/IP layer process and package, and send it to the adaptation sublayer in the form of an IP packet.
- the adaptation sublayer performs conversion, mapping, and service flow division, and sends it to the MAC sublayer.
- the MAC sublayer is fragmented. Encryption, framing, aggregation, etc., are sent to the PHY layer, which is ultimately mapped by the PHY to the wireless channel for data transmission.
- connection between the requesting end and the destination end requires separate establishment of uplink and downlink traffic.
- FIG. 6 is a flowchart of a method for establishing an uplink service flow and data transmission according to an embodiment of the present invention, where the process includes:
- Step 61 The CAP receives the dynamic service setup request frame that is sent by the STA and carries the FID and the destination MAC address.
- the destination MAC address is used as the destination end identifier.
- the destination here can be CAP or other STAs in the CAP range.
- the dynamic service establishment request is implemented by a dynamic service establishment request frame.
- FIG. 7 is a schematic structural diagram of a dynamic service setup request frame according to an embodiment of the present invention.
- the dynamic service setup request frame includes: a frame control field, an FID field, a service type field, a direction field, a service guarantee rate field, a destination MAC address field, FID maximum buffer capability field, FCS field.
- Figure 7 also shows an example of the number of bits occupied by each field.
- the portion of the frame shown in Fig. 7 other than the frame control field and the FCS field is called a frame body.
- the above frame control field includes an identifier related to the frame type, indicating that the frame is a dynamic service establishment request frame.
- FCS field is the calibration field.
- the above service type field indicates the service type of the service flow to be established.
- the QoS parameters of the traffic flow are as follows:
- this parameter specifies the priority assigned to a traffic flow. For a given two traffic flows, if all QoS parameters are the same except for the priority, the high-priority traffic should get lower latency and higher cache.
- this parameter defines the basic rate to protect the service, in bits per second, which matches the SDU input by the IP Adaptation Layer. This parameter does not include MAC overhead.
- Maximum service rate This parameter describes the maximum service rate that the system provides to the service. It is used for rate shaping. Extra data beyond this rate will be discarded by the CAP. The unit bits are per second, which is related to the SDU input by the IP adaptation layer. match. This parameter does not include MAC overhead.
- eight service types are defined in the MAC layer according to the QoS parameters of the service, and are classified into two categories: reserved resource class and unreserved resource class, as shown in Table 1 below.
- the service types 1 to 4 belong to the reserved resource class.
- the system guarantees the transmission bit rate for such services.
- the service types 5 to 8 belong to the unreserved resource class. The system does not guarantee the transmission bit rate for such services.
- the above direction field indicates whether the service flow to be established is an upstream service flow or a downlink service flow.
- the CAP can directly know the direction of the current service flow to be established.
- the above service guarantee rate field indicates the basic rate of guaranteed service, in bits per second, which matches the SDU input by the adaptation sublayer. This parameter does not include MAC overhead. Due to the variety of services in the actual application, such as the voices listed in Table 1, real-time sessions, etc., this field can indicate the service guarantee rate that the STA expects for different services, and the application flexibility is improved. For the service type of the resource that is not reserved in the table, the STA can also report the desired service guarantee rate.
- the destination MAC address field above indicates the MAC address of the destination. Through this field, the CAP can directly know the destination for which the dynamic service establishment request is directed.
- the destination here can be either the CAP itself or another STA within the scope of the CAP.
- the above FID Maximum Buffering Capability field indicates the number of MPDUs that the STA wants to buffer at most.
- service parameters The above service types and service guarantee rates can be collectively referred to as service parameters.
- Step 62 The CAP sends a dynamic service setup response frame to the STA.
- the service establishment response in this embodiment is implemented by a dynamic service setup response frame.
- FIG. 8 is a schematic structural diagram of a dynamic service setup response frame according to an embodiment of the present invention, where the dynamic service setup response frame includes: a frame control field, an FID field, and a service type field. , Reserved Field, Service Guarantee Rate Field, Service Maximum Rate Field, FID Maximum Buffer Ability Field, and FCS Field.
- Figure 8 also shows an example of the number of bits occupied by each field.
- the above frame control field includes an identifier related to the frame type, indicating that the frame establishes a response frame for the dynamic service.
- FCS field is the calibration field.
- the above service guarantee rate field indicates the value of the service guarantee rate allowed by the CAP.
- the CAP can adjust the service guarantee rate in the dynamic service establishment request frame. The adjustment is based on whether the current resource is sufficient to provide the service guarantee rate. For the service type of the reserved resource, if the current resource is limited and the service guarantee rate of the dynamic service establishment request frame cannot be guaranteed, the CAP can adjust the service guarantee rate reported by the STA according to the actual situation. For a service type that does not reserve resources, the CAP directly adjusts the service guarantee rate reported by the STA to 0, regardless of whether the STA has the service guarantee rate in the dynamic service setup request frame, but the current resource is a service that reserves resources. When more resources are left in addition to the service guarantee rate, the CAP may allocate resources for the service requested by the STA and indicate the allocated resources to the STA.
- the STA may decide whether to continue the data transmission. If the rate of the service guarantee is lower than the reported service guarantee rate, the STA may choose not to continue the data transmission.
- the STA may choose to continue the data transmission by using the allocated resources.
- the maximum service rate field indicates the maximum service rate that the system can provide for the requested service. It is used for rate shaping. Extra data beyond this rate will be discarded, in bits per second. It matches the SDU input by the IP adaptation layer. This parameter does not include MAC overhead.
- the maximum service rate is a preset value.
- the FID maximum buffering capability field indicates the maximum number of MPDUs that can be cached by the CAP.
- the value carried in the field can be the value reported in the dynamic service establishment request frame, or the value adjusted by the CAP according to the actual situation.
- the CAP records information such as the FID, destination MAC address, and corresponding service parameters and maximum service rate. Further, the STA may send an acknowledgement to the CAP after receiving the dynamic service setup response frame correctly. Specifically, the STA may send an ACK to the CAP, or may send a group acknowledgement to the CAP.
- the embodiment of the present invention provides a group acknowledgment mode, where the group acknowledgment frame includes a management control frame indicator bit, and further includes a bitmap corresponding to different service flows of the same user, where the STA may indicate in the foregoing management control frame.
- the bit fills in an indication indicating whether the dynamic service establishment response frame is correctly received or not.
- the STA may use the bitmap in the group acknowledgement frame to send the acknowledgement for the different service flows to the CAP.
- Step 63 The STA sends data by using an uplink transmission resource allocated by the CAP.
- the STA may request an uplink resource by sending an independent resource request to the CAP; further, the CAP may send an acknowledgement to the STA after correctly receiving the independent resource request;
- the CAP can actively poll each STA and allocate uplink transmission resources;
- the STA may carry the path resource request in the service data frame, and request the uplink transmission resource from the CAP. Further, after receiving the corresponding resource request correctly, the CAP may send an acknowledgement to the STA.
- the CAP indicates the uplink transmission resource allocated to the STA through the Control Channel (CCH).
- CCH Control Channel
- an uplink service flow is established and data is transmitted based on the uplink service flow.
- FIG. 9 is a flowchart of a method for tampering and transmitting data of the uplink service flow according to the present invention.
- the fields included in the dynamic service modification_change request frame are the same as those shown in Fig. 7.
- the fields included in the dynamic service modification response frame are the same as those shown in Fig. 8.
- the FID and the destination identifier carried in the dynamic service modification request frame are recorded by the CAP, and the dynamic service modification request frame carries new service parameters, such as a new service type and After the dynamic service modification request frame is received, the CAP can also adjust the new service parameters based on the current resources.
- the adjustment method is the same as that described in the previous section.
- the CAP records the FID and destination.
- the current service parameter corresponding to the end identifier is modified into the adjusted new service parameter, and the modified service parameter is carried in the dynamic service tamper response frame and sent to the STA.
- the maximum buffering capacity of the FID carried in the dynamic service modification request frame may be a new value or an original value.
- FIG. 10 is a flowchart of a method for establishing and transmitting data of a downlink service flow according to an embodiment of the present invention, where the process includes:
- Step 101 The STA receives the dynamic service setup request frame that carries the FID and the destination MAC address sent by the CAP.
- the dynamic service establishment request is implemented by a dynamic service establishment request frame.
- the field included in the dynamic service setup request frame is the same as that shown in FIG. 7, and the content carried by each field is also basically the same, except that the FID maximum buffer capability field indicates the MPDU that the CAP wants the STA to buffer at most. The number.
- the destination MAC address here refers to the STA that receives the dynamic service setup request frame.
- Step 102 The STA sends an ACK to the CAP.
- the STA directly feeds back the ACK to the CAP, and saves the parameters carried in the FID and the destination identifier and the dynamic service setup request frame.
- the STA can also send a GroupAck.
- Step 103 The STA receives the data sent by the CAP, and knows the downlink transmission resource that sends the data.
- the CAP indicates the downlink transmission resource while transmitting data through the CCH.
- a downlink traffic flow is established and data is transmitted on the downlink traffic flow.
- FIG. 11 is a flowchart of a method for modifying a downlink service flow according to the present invention.
- the fields included in the dynamic service modification request frame are the same as those shown in FIG.
- the FID and the destination end identifier carried in the dynamic service repair request frame are recorded by the STA, and the dynamic service repair request frame carries the new service parameter, for example, new. Business type and new business assurance rate.
- the STA updates each new service parameter corresponding to the saved FID and the destination identifier.
- the maximum buffering capacity of the FID carried in the dynamic service modification request frame may be a new value or an original value.
- the method of the present invention can be used when two STAs need to perform data transmission.
- STA1 and STA2 in the CAP range need to perform data transmission.
- STA1 first establishes an uplink service flow with the CAP.
- the CAP learns that the destination end is STA2 and can establish a downlink service flow with STA2.
- the STA can send data to the CAP when the CAP establishes a downlink service flow between the CAP and the STA2.
- the CAP sends the data sent by the cached STA1 to the STA2.
- STA2 sends data to STA1, which is the same process, that is, first establishes the uplink service flow from STA2 to CAP, then establishes the downlink service flow from CAP to STA1, and then sends STA2 to STA1 data on the established service flow.
- the first service flow establishing device in the present invention is located at the requesting end, and the requesting end may be located at the STA side or at the CAP side.
- FIG. 12 is a schematic structural diagram of a first service flow establishing apparatus according to the present invention.
- the apparatus includes: a request sending unit 121 and a response receiving unit 122.
- the request sending unit 121 sends a dynamic service establishment request carrying the destination end identifier and the FID.
- the response receiving unit 122 receives the response of the ten pairs of dynamic service establishment requests.
- the structure is as shown in FIG. 13, and the device includes: a request sending unit 131, a response receiving unit 132, and service parameter providing.
- the request sending unit 131 sends a dynamic service establishment request carrying the destination end identifier and the FID.
- the response receiving unit 132 receives 40 responses to the dynamic service establishment request.
- the response of the dynamic service setup request received by the response receiving unit 132 is ACK or GroupAck.
- the service parameter providing unit 133 is configured to send the service parameter to the request sending unit 131 for carrying and transmitting in the dynamic service establishment request.
- the direction information providing unit 134 is configured to send the direction information indicating that the service flow to be established is uplink or downlink to the request sending unit 131, and the carrying information is sent in the dynamic service establishment request.
- the buffering capability providing unit 135 is configured to provide the FID maximum buffering capability to the request sending unit 131 for carrying and transmitting in the dynamic service establishment request.
- the FID maximum buffering capability indicates the number of MPDUs that are most cached by the receiving end of the desired dynamic service establishment request.
- the monitoring unit 136 is configured to monitor the response receiving unit 132 within the set number of frames after the request sending unit 131 sends the dynamic service establishment request, and if the response receiving unit 132 does not receive the response, notify the request sending unit 131 to resend the dynamic service. Create a request. On the basis of this, the request sending unit 131 encapsulates the dynamic service establishment request into an MPDU transmission. When the resending dynamic service establishment request exceeds the maximum number of MPDU retransmissions, the dynamic service establishment request is discarded, and the service flow deletion device is notified to perform the operation.
- the device includes: a request sending unit 141, a response receiving unit 142, a confirming unit 143, The service parameter providing unit 144, the direction information providing unit 145, the buffering capability providing unit 146, and the monitoring unit 147.
- the request sending unit 141 sends a dynamic service establishment request that carries the destination identifier and the FID.
- the response receiving unit 142 receives 40 responses to the dynamic service setup request.
- the response of the dynamic service setup request received by the response receiving unit 142 is a dynamic service setup response carrying the FID. Further, the dynamic service setup response received by the response receiving unit 142 can also carry the maximum service rate that the system can provide.
- the clarifying unit 143 is configured to send an ACK or a GroupAck indicating that the dynamic service establishment response is correctly received.
- the service parameter providing unit 144 is configured to send the service parameter to the request sending unit 141 for carrying and transmitting in the dynamic service establishment request. On this basis, the dynamic service establishment response can carry the adjusted service parameters.
- the direction information providing unit 145 is configured to send the direction information indicating that the service flow to be established is uplink or downlink to the request sending unit 141, and the carrying information is sent in the dynamic service establishment request.
- the buffering capability providing unit 146 is configured to provide the FID maximum buffering capability to the request sending unit 141 for being carried in the dynamic service establishment request, where the FID maximum buffering capability indicates that the dynamic service establishment request is expected to be received.
- the monitoring unit 147 is configured to monitor the response receiving unit 142 within the set number of frames after the request sending unit 141 sends the dynamic service establishment request, and if the response receiving unit 142 does not receive the response, the notification request sending unit 141 ends the current process. .
- the device may further include: a data transmission unit, configured to send the service data on the service flow corresponding to the established FID, whether the first service flow establishing device of the present invention is located on the STA side or the CAP side.
- a data transmission unit configured to send the service data on the service flow corresponding to the established FID, whether the first service flow establishing device of the present invention is located on the STA side or the CAP side.
- the first service flow establishing device of the present invention is located on the STA side or the CAP side, only one of the direction information providing unit and the buffering capability providing unit may be included.
- the second service flow establishing device is located at the request receiving end, and the request receiving end may be located at the STA side or the CAP side.
- FIG. 15 is a schematic structural diagram of a second service flow establishing apparatus according to the present invention, the apparatus comprising: a request receiving unit 151 and a response sending unit 152.
- the request receiving unit 151 is configured to receive a dynamic service establishment request that carries the destination end identifier and the FID.
- the response sending unit 152 is configured to send a response for the dynamic service establishment request.
- the dynamic service establishment request received by the request receiving unit 151 may further carry the service parameter.
- the response sending unit 152 sends
- the device When the second service flow establishing device of the present invention is located on the CAP side, as an optional embodiment, the structure is as shown in FIG. 16, the device includes: a request receiving unit 161, and a response sending unit. 162.
- the request receiving unit 161 is configured to receive a dynamic service establishment request that carries the destination end identifier and the FID.
- the response sending unit 162 is configured to send a response to the dynamic service establishment request.
- the response sending unit 162 sends a dynamic service setup response carrying the FID.
- the acknowledgment receiving unit 163 is configured to receive an ACK or a GroupAck indicating that the dynamic service establishment response is correctly received.
- the monitoring unit 164 is configured to monitor the acknowledgment receiving unit 163 in the set number of frames after the response sending unit 162 sends the dynamic service setup response, and if the acknowledgment receiving unit 163 does not receive the ACK or the GroupAck, the notification response sending unit 163 resends The dynamic service establishment response. On this basis, the response sending unit 162 encapsulates the dynamic service setup response into MPDU transmission. When the retransmission exceeds the maximum number of retransmissions of the MPDU, the dynamic service establishment response is discarded, and the service flow deletion device is notified to perform the operation.
- the service parameter adjustment unit 165 is configured to adjust the service parameter carried in the dynamic service establishment request, and send the adjusted service parameter to the response sending unit 162, where it is carried in the response.
- the service maximum rate determining unit 166 is configured to determine a maximum service rate that the system can provide, and send the signal to the response sending unit 162 for carrying in the response.
- the second service flow establishing device of the present invention may further include: a data transmission unit, configured to receive service data sent on the service flow corresponding to the established FID.
- the second service flow establishing device of the present invention is located on the STA side or the CAP side, and the dynamic service establishment request received by the request receiving unit may carry direction information and/or FID maximum buffering capability, where the direction information is Indicates that the service flow to be established is uplink or downlink, and the FID maximum buffering capability indicates the number of MPDUs that are expected to be cached by the receiving end of the dynamic service establishment request.
- the first service flow modification device of the present invention is located at the requesting end, and the requesting end may be located at the CAP side or at the STA side.
- FIG. 17 is a schematic structural diagram of a first service flow modification apparatus according to the present invention.
- the apparatus includes: a request sending unit 171 and a response receiving unit 172.
- the request sending unit 171 sends a dynamic service tampering request carrying the destination end identifier, the FID, and the new service parameter.
- the response receiving unit 172 receives a dynamic service tampering response carrying the FID.
- the structure thereof is as shown in FIG. 18.
- the device includes: a request sending unit 181, a response receiving unit 182, and a monitoring unit 183.
- the request sending unit 181 sends a dynamic service tampering request carrying the destination end identifier, the FID, and the new service parameter.
- the response receiving unit 182 receives the dynamic service tampering response carrying the FID.
- the response received by response receiving unit 182 is ACK or GroupAck.
- the monitoring unit 183 is configured to: after the request sending unit 181 sends the dynamic service modification request, the set intra-frame monitoring response receiving unit 182, if the response receiving unit 182 does not receive the response, notify the request sending unit 181 to resend the dynamic service. Change the request. On this basis, the request sending unit 181 encapsulates the dynamic service modification request into an MPDU transmission, when resending the dynamic service modification, please When the maximum number of retransmissions of the MPDU is exceeded, the dynamic service tampering request is discarded, and the service flow deleting device is notified to perform the operation.
- the direction information providing unit 184 is configured to send the direction information indicating that the service flow to be modified is uplink or downlink to the request sending unit 181, and the carrying information is sent in the dynamic service modification request.
- the buffering capability providing unit 185 is configured to provide the FID maximum buffering capability to the request sending unit 181 for being carried in the dynamic service modification request, where the FID maximum buffering capability indicates that the dynamic service modification request is expected to be received.
- the structure thereof is as shown in FIG. 19, and the device includes: a request sending unit 191, a response receiving unit 192, and a confirming unit 193. , monitoring unit 194,
- the request sending unit 191 sends a dynamic service tampering request carrying the destination end identifier, the FID, and the new service parameter.
- the response receiving unit 192 receives the dynamic service tampering response carrying the FID.
- the response received by response receiving unit 182 is a dynamic traffic tamper response.
- the dynamic service tampering response carries the modified service parameter.
- the dynamic service modification response carries the maximum service rate that the system can provide.
- the acknowledgment unit 193 is configured to send an ACK or a GroupAck indicating that the dynamic service modification response is correctly received.
- the monitoring unit 194 is configured to: after the request sending unit 191 sends the dynamic service modification request, the set intra-frame monitoring response receiving unit 192, if the response receiving unit 192 does not receive the response, the notification request sending unit 191 ends the current process.
- the direction information providing unit 195 is configured to send the direction information indicating that the service flow to be modified is uplink or downlink to the request sending unit 191, and the carrying information is sent in the dynamic service modification request.
- the buffering capability providing unit 196 is configured to provide the FID maximum buffering capability to the request sending unit 191 for being carried in the dynamic service modification request, where the FID maximum buffering capability indicates that the dynamic service modification request is expected to be received.
- the first service flow modification device of the present invention is located on the CAP side or the STA side, and the device may further include: a data transmission unit, configured to send the service data on the service flow corresponding to the falsified FID .
- the second service flow modification device is located at the request receiving end, and the request receiving end may be located at the STA side or at the CAP side.
- FIG. 20 is a schematic structural diagram of a second service flow modification apparatus according to the present invention.
- the apparatus includes: a request receiving unit 201 and a response sending unit 202.
- the request receiving unit 201 is configured to receive a dynamic service tampering request that carries the destination end identifier, the FID, and the new service parameter.
- the response sending unit 202 is configured to send a response to the dynamic service tampering request.
- the response sent by the response sending unit 202 is ACK or GroupAck.
- the second service flow tampering device of the present invention when located on the CAP side, the structure thereof is as shown in FIG. 21, and the device includes: a request receiving unit 211, a response sending unit 212, and an acknowledgment receiving unit. 213.
- the request receiving unit 211 is configured to receive a dynamic service tampering request that carries the destination end identifier, the FID, and the new service parameter.
- the response sending unit 212 is configured to send 40 responses to the dynamic service tampering request.
- the response sent by the response sending unit 212 is a dynamic service tampering response carrying the FID.
- the acknowledgment receiving unit 213 is configured to receive an ACK or a GroupAck indicating that the dynamic service tamper response is correctly received.
- the monitoring unit 214 is configured to monitor the acknowledgment receiving unit 213 within the set number of frames after the response sending unit 212 sends the dynamic service tampering response. If the acknowledgment receiving unit 213 does not receive the ACK or the GroupAck, the notification response sending unit 212 resends the dynamic. Business tamper response. On the basis of this, the response sending unit 212 sends the dynamic service modification/response MPDU. When the retransmission exceeds the maximum number of retransmissions of the MPDU, the dynamic service modification response is discarded, and the service flow deletion device is notified to perform the operation.
- a modifying unit 215, configured to determine, according to the new service parameter, a resource reserved for the service flow to be modified; adjusting the new service parameter according to the reserved resource; and modifying the FID and the destination according to the adjusted new service parameter
- the end identifies the current service parameter corresponding to the current service parameter, and sends the modified service parameter to the response sending unit 212 for carrying in the dynamic service tampering response.
- the service maximum rate providing unit 216 is configured to determine a maximum service rate that the system can provide, and send it to the response sending unit 212 for carrying and transmitting in the response.
- the second service flow modification device of the present invention is located on the STA side or the CAP side, and the device may further include: a data transmission unit, configured to receive, sent by, on the modified service flow corresponding to the FID Business data.
- the second service flow modification device of the present invention is located on the STA side or the CAP side, and the dynamic service modification request received by the request receiving unit may further carry direction information and/or FID maximum buffering capability;
- the information indicates that the service flow to be modified is uplink or downlink;
- the FID maximum buffering capability indicates the number of MPDUs that are expected to be cached by the receiving end of the dynamic service establishment request.
- the device may further include: a resource requesting unit, configured to request an uplink transmission resource for sending the service data.
- the device may further include: a resource acquiring unit, configured to obtain an uplink for sending service data by using active polling Transfer resources.
- the device may further include: a resource indicating unit, configured to send the service data while instructing to send Downlink transmission resources of service data.
- the device may further include: a resource allocation unit, configured to allocate an uplink transmission resource for sending the service data according to the request.
- the device may further include: a polling unit, configured to allocate, by using active polling, uplink transmission for sending service data. Resources.
- FIG. 22 is a flowchart of a service flow management method according to the present invention. The process includes:
- Step 221 Send a dynamic service management request carrying the FID and FID maximum buffering capability.
- the FID maximum buffering capacity here refers to the number of MPDUs that the requesting end wants the receiving end to buffer at most.
- the requesting end can be either CAP or STA.
- Step 222 Receive a response to the dynamic service management request.
- the service flow management method provided by the present invention on the one hand, each service flow has its own corresponding buffering capability, the management is finer and more flexible, and on the other hand, the service flow management is requested to be slowed down.
- the negotiation of the punching ability saves the operation process.
- the service flow management method provided by the present invention is a service flow establishment method, and includes the following two situations:
- the method for establishing uplink traffic and data transmission includes the following steps:
- Step 1 The CAP receives the dynamic service setup request frame sent by the STA and carries the FID and FID maximum buffering capability.
- the dynamic service establishment request is implemented by a dynamic service establishment request frame.
- the frame body of the dynamic service setup request frame in this step includes an FID field and an FID maximum buffer capability field, and may further include one or more of a service type field, a direction field, a service guarantee rate field, and a destination MAC address field.
- the meanings of these fields are the same as described above, and the structure including all the above fields in the frame body is the same as that shown in FIG.
- Step 2 The CAP sends a dynamic service setup response frame to the STA.
- the service establishment response in this embodiment is implemented by a dynamic service setup response frame.
- the frame body of the dynamic service establishment response frame in this step may include one or more of a service type field, a service guarantee rate field, and a service maximum rate field, in addition to the FID field and the FID maximum buffer capability field.
- a service type field a service guarantee rate field
- a service maximum rate field in addition to the FID field and the FID maximum buffer capability field.
- the service parameters carried by the dynamic service establishment response frame (which are carried by the service type field and the service guarantee rate field) may be obtained by adjusting the service parameters carried in the dynamic service establishment request frame by the CAP, and the adjustment method is as previously described in the foregoing. .
- the maximum buffering capability of the FID carried in the dynamic service setup response frame may be the same as that in the dynamic service setup request frame, or may be obtained by the CAP adjusting the maximum buffering capacity of the FID carried in the dynamic service setup request frame.
- the CAP records information such as the FID, destination MAC address, and corresponding service parameters and service maximum rate. Further, the STA may send an ACK to the CAP after correctly receiving the dynamic service setup response frame. Alternatively, the STA can send a GroupAck to the CAP.
- Step 3 The STA sends data by using the uplink transmission resource allocated by the CAP.
- the process of tampering the upstream service flow is similar to the foregoing step 1-2, except that the STA sends the same dynamic service modification request frame as the dynamic service establishment request frame structure, and the FID in the dynamic service modification request frame is already recorded by the CAP.
- the CAP updates the maximum buffering capacity and/or service parameters of the FID corresponding to the recorded FID according to the condition that the parameter is carried in the dynamic service modification request frame.
- the CAP may also adjust the maximum buffering capacity and/or service parameters of the FID carried in the dynamic service modification request frame before performing the update operation.
- the method for establishing downlink traffic flow and data transmission includes the following steps:
- Step 1 The STA receives the dynamic service setup request frame sent by the CAP and carries the maximum buffering capability of the FID and the FID.
- the dynamic service establishment request is implemented by a dynamic service establishment request frame.
- the frame body of the dynamic service setup request frame in this step includes an FID field and an FID maximum buffer capability field, and may further include one or more of a service type field, a direction field, a service guarantee rate field, and a destination MAC address field.
- the meanings of these fields are the same as described above, and the structure including all the above fields in the frame body is the same as that shown in FIG.
- Step 2 The STA sends an ACK to the CAP.
- the STA directly feeds back the ACK to the CAP, and saves the parameters carried in the FID and the destination identifier and the dynamic service setup request frame.
- the STA may also send a GroupAck to the CAP.
- the STA may also send a GroupAck to the CAP.
- Step 3' The STA receives the data sent by the CAP, and knows the downlink transmission resource that sends the data.
- the process of modifying the downlink service flow is similar to the above steps 1, 2, except that the CAP sends the same dynamic service modification request frame as the dynamic service establishment request frame structure, and the FID in the dynamic service modification request frame is already recorded by the STA.
- the STA updates the maximum buffering capacity and/or service parameters of the FID corresponding to the recorded FID according to the condition that the dynamic service repairs the request frame to carry the parameter.
- the present invention also provides two service flow management devices.
- FIG. 23 is a schematic structural diagram of a first service flow management apparatus according to the present invention.
- the apparatus is located on the request side, and includes: a request sending unit 231 and a response receiving unit 232.
- the request sending unit 231 is configured to send a dynamic service management request carrying the maximum buffering capability of the service flow identifier FID and the FID.
- the response receiving unit 232 receives 40 responses to the dynamic service management request.
- the first service flow management device in the present invention when the first service flow management device in the present invention is located on the CAP side, the structure thereof is as shown in FIG. 24, and the device includes: a request sending unit 241, a response receiving unit 242, and a parameter providing unit. 243 and monitoring unit 244.
- the request sending unit 241 is configured to send a dynamic service management request carrying the maximum buffering capability of the service flow identifier FID and the FID.
- the response receiving unit 242 receives a response to the dynamic service management request.
- the response to the dynamic service management request received by the response receiving unit 242 is: an acknowledgment indicating that the dynamic service management request is correct.
- the parameter providing unit 243 is configured to send one or more of the destination end identifier, the service parameter, and the direction information to the request sending unit 241, where the carrying information is sent in the dynamic service management request, where the direction information indicates that the service flow is Up or down.
- the monitoring unit 244 is configured to monitor the response receiving unit 242 within the set number of frames after the request sending unit 241 sends the dynamic service management request, and if the response receiving unit 242 does not receive the response, notify the request sending unit 241 to resend the dynamic service. Manage requests. On this basis, the request sending unit 241 encapsulates the dynamic service management request into an MPDU transmission. When the resending dynamic service management request exceeds the maximum number of MPDU retransmissions, the dynamic service management request is discarded, and the service flow deleting device is notified to perform the operation.
- the structure thereof is as shown in FIG. 25, and the device includes: a request sending unit 251, a response receiving unit 252, and a confirming unit 253.
- the parameter providing unit 254 and the monitoring unit 255 are included in the STA side.
- the request sending unit 251 is configured to send a dynamic service management request carrying a maximum buffering capability of the service flow identifier FID and the FID.
- the response receiving unit 252 receives a response to the dynamic service management request.
- the response to the dynamic service management request received by the response receiving unit 252 is: a dynamic service management response carrying the FID.
- the confirmation unit 253 is configured to send an acknowledgement indicating that the dynamic service management response is correctly received.
- the parameter providing unit 254 is configured to send one or more of the destination identifier, the service parameter, and the direction information to the request sending unit 251, where the carrying is sent in a dynamic service management request, where the direction information indicates the service flow. For the up or down. On the basis of this, further, when the dynamic service management request carries the service parameter, the dynamic service management response further carries the adjusted service parameter.
- the monitoring unit 255 is configured to monitor the response receiving unit 252 within the set number of frames after the request sending unit 251 sends the dynamic service management request, and if the response receiving unit 252 does not receive the response, the notification request sending unit 251 ends the current process. .
- Figure 26 is a block diagram showing the structure of a second service flow management apparatus according to the present invention.
- the apparatus is located at the receiving end side, and the apparatus includes: a request receiving unit 261 and a response transmitting unit 262.
- the request receiving unit 261 is configured to receive a dynamic service management request carrying the maximum buffering capability of the FID and the FID.
- the response sending unit 262 is configured to send a response for the dynamic service management request.
- the response to the dynamic service management request is: an acknowledgment indicating that the dynamic service management request is correctly received.
- the dynamic service management request further carries one or more of a destination end identifier, a service parameter, and a direction information, where the direction information indicates that the service flow to be established is uplink or downlink.
- the service flow management device when the service flow management device is located on the CAP side, its structure is as shown in FIG. 27, and the device includes: a request receiving unit 271, a response transmitting unit 272, an acknowledgment receiving unit 273, a monitoring unit 274, and Business parameter adjustment unit 275.
- the request receiving unit 271 is configured to receive a dynamic service management request carrying a maximum buffering capability of the FID and the FID.
- the response sending unit 272 is configured to send a response for the dynamic service management request.
- the response to the dynamic service management request sent by the response sending unit 272 is: a dynamic service management response carrying the FID and FID maximum buffering capability.
- the acknowledgment receiving unit 273 is configured to receive an acknowledgment indicating that the dynamic service management response is correctly received.
- the monitoring unit 274 is configured to monitor the acknowledgment receiving unit 273 within the set number of frames after the response sending unit 272 sends the dynamic service management response, and if the acknowledgment receiving unit 273 does not receive the acknowledgment, the trigger response sending unit 272 resends the dynamic service. Manage responses. On the basis of this, the response sending unit 272 encapsulates the dynamic service management response into MPDU transmission. When the retransmission exceeds the maximum number of retransmissions of the MPDU, the dynamic service management response is discarded, and the service flow deleting device is notified to perform the operation.
- the dynamic service management request further carries one or more of a destination end identifier, a service parameter, and a direction information.
- the service parameter adjustment unit 275 is configured to: when the service parameter is carried in the dynamic service management request, determine the reserved resource according to the service parameter carried in the dynamic service management request, and adjust, according to the reserved resource, the dynamic service management request The service parameters are sent to the response sender element 272 for transmission in the dynamic service management response.
- FIG. 28 is a flowchart of a method for deleting a service flow in the present invention, the process comprising:
- Step 281 Send a dynamic service deletion request carrying the FID and the direction information, where the direction information indicates that the service flow to be deleted is an uplink service flow or a downlink service flow.
- the originating end of the dynamic service deletion request may be an STA or a CAP.
- the direction information indicates the uplink service flow.
- the direction information may indicate the uplink service.
- the flow may also indicate a downlink traffic flow.
- Step 282 Receive 40 responses to the dynamic service deletion request.
- the present invention carries the direction information in the dynamic service deletion request, so that the CAP can delete the downlink service flow established by the STA not only when the service transmission ends, but also actively delete the uplink service flow corresponding to the STA, so that the CAP does not exist for a long time.
- STAs occupy long-term occupations in the event of an abnormal situation Use business flow resources.
- the STA may delete the uplink service flow established by itself at the end of the service transmission.
- FIG. 29 is a flowchart of a method for deleting an uplink service flow according to an embodiment of the present invention, where the process includes:
- Step 291 The CAP receives the dynamic service deletion request frame that is sent by the STA and carries the FID and the direction information.
- the dynamic service deletion request is implemented by a dynamic service deletion request frame.
- FIG. 30 is a schematic structural diagram of a dynamic service deletion request frame according to an embodiment of the present invention, where the dynamic service deletion request frame includes a frame control field, an FID field, a direction field, and an FCS field.
- the identifier related to the frame type in the frame control field indicates that the frame is a dynamic service deletion request frame
- the FID indicates the FID of the service flow to be deleted
- the direction field indicates that the service flow to be deleted is an uplink service flow
- the FCS field is a school. Fields. An example of the number of bits occupied by each field is also shown in FIG.
- Step 292 The CAP sends a dynamic service deletion response frame to the STA.
- the structure of the dynamic service deletion response frame is the same as that of the dynamic service deletion request frame, and the content carried in each field is also the same.
- Step 293 The CAP receives the ACK sent by the STA after receiving the dynamic service deletion response frame correctly.
- the STA can also send a GroupAck to the CAP.
- the CAP and the STA will delete the recorded FID and the corresponding related information, respectively, and end the data transmission on the deleted service flow.
- FIG. 31 is a flowchart of a method for deleting an uplink or downlink service flow according to an embodiment of the present invention, where the process includes:
- Step 311 The STA receives the dynamic service deletion request frame that carries the FID and the direction information sent by the CAP.
- the dynamic service deletion request is implemented by the dynamic service deletion request frame.
- the structure of the dynamic service deletion request frame is the same as that shown in FIG. 30.
- the direction field indicates the downlink service flow.
- the direction field indicates the upstream service flow.
- Step 312 The STA sends an ACK to the CAP.
- the STA can also send a GroupAck to the CAP.
- the CAP and the STA will delete the recorded FID and the corresponding related information, respectively, and end the data transmission on the deleted service flow.
- the present invention also provides two service flow deletion devices.
- FIG. 32 is a schematic structural diagram of a first service flow deleting apparatus according to the present invention.
- the apparatus includes: a request sending unit 321 and a response receiving unit 322.
- the request sending unit 321 is configured to send a dynamic service deletion request carrying the FID and the direction information, where the direction information indicates that the service flow to be deleted is uplink or downlink.
- the response receiving unit 322 is configured to receive a response of the 40 pairs of dynamic service deletion requests.
- the first service flow deleting device of the present invention when located on the CAP side, the structure thereof is as shown in FIG. 33, and the device includes: a request sending unit 331, a response receiving unit 332, and a monitoring unit 333.
- the request sending unit 331 is configured to send a dynamic service deletion request carrying the FID and the direction information, where the direction information indicates that the service flow to be deleted is uplink or downlink.
- the response receiving unit 332 is configured to receive a response of the 40 pairs of dynamic service deletion requests.
- the response to the dynamic service deletion request received by the response receiving unit 332 is: an indication that the dynamic service deletion request is correctly received.
- the monitoring unit 333 is configured to monitor the response receiving unit 332 after the request sending unit 331 sends the dynamic service deletion request, and if the response receiving unit 332 does not receive the response, the trigger request sending unit 331 resends the dynamic service. Delete the request. On this basis, the request sending unit 331 encapsulates the dynamic service deletion request into an MPDU transmission, and discards the dynamic service deletion request when the resending dynamic service deletion request exceeds the maximum number of MPDU retransmissions.
- the two service flow establishing devices of the present invention which are also located on the CAP side, or the two service flow tampering of the present invention may be received.
- the notification of the device begins to perform the operation.
- the notification of the two service flow management apparatuses of the present invention, which are also located on the CAP side, can be received to start the operation.
- the structure is the same as that shown in FIG. 33, except that the response received by the receiving unit 332 for the dynamic service deletion request is a carrying place.
- the dynamic service deletion response of the FID and the direction information is described, and the monitoring unit 333 notifies the request transmitting unit 331 to end the current flow when the response receiving unit 332 does not receive the response.
- FIG. 34 is a schematic structural diagram of a second service flow deleting apparatus according to the present invention.
- the apparatus includes: a request receiving unit 341 and a response sending unit 342.
- the request receiving unit 341 is configured to receive a dynamic service deletion request that carries the FID and the direction information, where the direction information indicates that the service flow to be deleted is uplink or downlink.
- the response sending unit 342 is configured to send a response for the dynamic service deletion request.
- the service flow deleting device when the service flow deleting device is located on the CAP side, the structure thereof is as shown in FIG. 35, and the device includes: a request receiving unit 351, a response sending unit 352, an acknowledgment receiving unit 353, and a monitoring unit 354. .
- the request receiving unit 351 is configured to receive a dynamic service deletion request that carries the FID and the direction information, where the direction information indicates that the service flow to be deleted is uplink or downlink.
- the response sending unit 352 is configured to send a response for the dynamic service deletion request.
- the response to the dynamic service deletion request is: a dynamic service deletion response carrying the FID and direction information.
- the acknowledgment receiving unit 353 is configured to receive an acknowledgment indicating that the dynamic service deletion response is correctly received.
- the monitoring unit 354 is configured to monitor the acknowledgement receiving unit 353 in the set number of frames after the response sending unit 352 sends the dynamic service deletion response, and if the acknowledge receiving unit 353 does not receive the acknowledgement, the trigger response sending unit 352 resends the Dynamic business delete response. On the basis of this, the response sending unit 352 encapsulates the dynamic service deletion response into an MPDU transmission, and discards the dynamic service deletion response when the retransmission exceeds the maximum number of retransmissions of the MPDU.
- the response to the dynamic service deletion request is: indicating that the dynamic service deletion request is correctly received.
- the maximum waiting interval of the service flow response frame indicates the maximum number of waiting frames that the STA can tolerate after sending the service flow management request.
- the default value can be set to 4;
- the maximum waiting frame interval for the downlink service flow request frame acknowledgement indicates the maximum number of waiting frames that the CAP can tolerate after sending the service flow management request.
- the default value can be set to 4;
- the maximum waiting frame interval for the service flow response frame acknowledgement indicates the maximum number of waiting frames that the CAP can tolerate after sending the service flow management response frame. As an example, the default value can be set to 4; 4. Maximum number of retransmissions of the MPDU: indicates the maximum number of times that an MPDU attempts to retransmit. As an example, the default value can be set to 5.
- the maximum number of consecutive transmission failures allowed by the CAP to the STA indicates the number of consecutive transmission failures that the CAP can tolerate for a certain STA.
- the default value can be set to 20.
- the exception handling manner in the service flow management of the present invention may specifically include:
- the STA waits for the "maximum waiting interval of the service flow response frame" after transmitting the request frame. If the response frame sent by the CAP is not received, the service flow management process is considered to have failed. The STA will initiate a new business flow management process.
- the CAP waits for the "maximum waiting frame interval for the service flow response frame acknowledgement" after transmitting the response frame. If the ACK or GroupAck sent by the STA is not received, the response frame is retransmitted until the number of retransmissions exceeds the maximum weight of the MPDU. The number of transmissions, at which point the CAP will initiate the service flow deletion process.
- the CAP waits for the "maximum waiting frame interval for the downlink service flow request frame acknowledgment" after sending the request frame. If the ACK or GroupAck sent by the STA is not received, the service flow management process fails. The request frame is retransmitted until the number of retransmissions exceeds the maximum number of retransmissions of the MPDU. At this time, the CAP initiates a service flow deletion process.
- the CAP sends an MPDU to the STA, and the CAP encapsulates the response frame or the request frame of the service flow of the STA into an MPDU and sends the message to the STA.
- the CAP sends a G-MPDU to the STA, and the CAP sends the response frame or the request frame of the service flow 1 for the STA to the STA in combination with the data frame of the STA service flow 2.
- timing is performed using a frame number, and timing is more accurate than using a timer.
- the CAP sends an MPDU to the STA, and the CAP encapsulates the response frame or the request frame of the service flow of the STA into an MPDU and sends the message to the STA.
- the CAP sends a G-MPDU to the STA, and the CAP sends the response frame or the request frame of the service flow 1 for the STA to the STA in combination with the data frame of the STA service flow 2.
- timing is performed using a frame number, and timing is more accurate than using a timer.
- the present invention further provides a method for establishing a service flow.
- the method includes: Step 361: Generate a dynamic service establishment request that carries an FID and a destination identifier.
- Step 362 Send the dynamic service establishment request.
- the present invention also provides another method for service flow establishment. As shown in FIG. 37, the method includes:
- Step 371 Generate a dynamic service setup response carrying the FID.
- Step 372 Send the dynamic service establishment response.
- the dynamic service establishment request may be implemented by using the dynamic service establishment request frame shown in FIG. 7, and the dynamic service establishment response may be implemented by using the dynamic service establishment response frame shown in FIG. 8.
- the present invention further provides two means for establishing a service flow, including a generating unit and a sending unit, wherein the generating unit is configured to generate a corresponding method in the generating step. The generated information, the sending unit is used to send the information generated by the generating unit.
- the present invention also provides a method for service flow tampering. As shown in FIG. 38, the method includes: Step 381: Generate a dynamic service tampering request carrying an FID, a destination end identifier, and a new service parameter.
- Step 382 Send the dynamic service establishment request.
- the present invention also provides another method for service flow modification. As shown in FIG. 39, the method includes:
- Step 391 Generate a dynamic service tampering response carrying the FID.
- Step 392 Send the dynamic service tamper response.
- the dynamic service modification request may be implemented by using the same dynamic service modification request frame as that shown in FIG. 7.
- the dynamic service tamper response may be as shown in FIG. Dynamic service tamper response frame implementation.
- the present invention further provides two apparatuses for service flow tampering, including a generating unit and a sending unit, where the generating unit is configured to generate a corresponding method.
- the information generated in the transmission element is used to transmit the information generated by the generating unit.
- the present invention further provides a method for establishing a service flow.
- the method includes: Step 401: Generate a dynamic service establishment request carrying a FID and FID maximum buffering capability; Step 402: Send the dynamic service Create a request.
- the present invention also provides another method for service flow establishment, as shown in FIG. 41, the method includes:
- Step 411 Generate a dynamic service setup response that carries the FID and FID maximum buffering capability.
- Step 412 Send the dynamic service setup response.
- the foregoing dynamic service establishment request may be implemented by using the dynamic service setup request frame shown in FIG. 7, and the dynamic service setup response may be implemented by using the dynamic service setup response frame shown in FIG.
- the present invention further provides two devices for service flow establishment, including a generating unit and a sending unit, where the generating unit is configured to generate a corresponding method in the generating step.
- the generated information, the sending unit is used to send the information generated by the generating unit.
- the present invention further provides a method for service flow tampering. As shown in FIG. 42, the method includes: Step 421: Generate a dynamic service modification request carrying a FID and FID maximum buffering capability; Step 422: The dynamic service repair _ change request.
- the present invention also provides another method for service flow tampering. As shown in FIG. 43, the method includes:
- Step 431 Generate a dynamic service tampering response carrying the maximum buffering capability of the FID and the FID.
- Step 432 Send the dynamic service tampering response.
- the dynamic service modification request may be implemented by using the same dynamic service modification request frame as that shown in FIG. 7.
- the dynamic service tamper response may be as shown in FIG. Dynamic service tamper response frame implementation.
- the present invention further provides two apparatuses for service flow tampering, including a generating unit and a sending unit, where the generating unit is configured to generate a corresponding method.
- the information generated in the transmission element is used to transmit the information generated by the generating unit.
- the present invention further provides a method for service flow deletion. As shown in FIG. 44, the method includes: Step 441: Generate a dynamic service flow deletion request carrying FID and direction information;
- Step 442 Send the dynamic service flow deletion request.
- the present invention also provides another method for service flow deletion. As shown in FIG. 45, the method includes:
- Step 451 Generate a dynamic service flow deletion response that carries the FID and the direction information.
- Step 452 Send the dynamic service flow deletion response.
- the foregoing dynamic service deletion request and dynamic service deletion response may be implemented by using the same frame as the structure shown in FIG.
- the present invention further provides two apparatuses for service flow deletion, including a generating unit and a sending unit, where the generating unit is configured to generate a corresponding method in the generating step.
- the generated information is sent to the information generated by the generating unit.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明提供的业务流管理方法中,在动态业务管理请求中携带业务流标识FID和FID最大缓冲能力,一方面使得每个业务流都有各自对应的缓冲能力,管理更精细、更灵活,另一方面在请求业务流管理的同时就进行缓冲能力的协商,节约了操作流程。
Description
业务流管理方法及装置
本申请要求申请日为 2011年 3月 31 日, 申请号为 201110081288.6, 发 明名称为 "一种无线通信方法"的中国专利申请的优先权, 该在先申请的全部 内容均已在本申请中体现。
本申请要求申请日为 2011年 7月 6 日, 申请号为 201110188606.9, 发明 名称为 "业务流建立方法和装置、及业务流修改方法和装置"的中国专利申请 的优先权, 该在先申请的全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 8 日, 申请号为 201210027851.6, 发 明名称为 "业务流建立方法和装置、及业务流修改方法和装置"的中国专利申 请的优先权, 该在先申请的全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 8 日, 申请号为 201210027916.7, 发 明名称为 "业务流管理方法及装置"的中国专利申请的优先权, 该在先申请的 全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 8 日, 申请号为 201210027852.0, 发 明名称为 "业务流删除方法及装置"的中国专利申请的优先权, 该在先申请的 全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 17 日, 申请号为 201210036754.3, 发 明名称为 "业务流建立方法和装置、 及业务流修改方法和装置"的中国专利申 请的优先权, 该在先申请的全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 17 日, 申请号为 201210038757.0, 发 明名称为 "业务流管理方法及装置"的中国专利申请的优先权, 该在先申请的 全部内容均已在本申请中体现。
本申请要求申请日为 2012年 2月 17 日, 申请号为 201210038079.8, 发 明名称为 "业务流删除方法及装置"的中国专利申请的优先权, 该在先申请的 全部内容均已在本申请中体现。 技术领域
本发明属于无线通信领域, 尤其涉及业务流管理方法及装置。 背景技术
近年来, 无线通信***迅速发展, 诸如基于 802.11标准的无线局域网技 术 WiFi、 基于 802.15的蓝牙 (Bluetooth ) ***以及由移动通信***^ "生而 来的面向室内应用的 Femto技术等等, 都得到了广泛的应用。
基于 802.11的 WiFi技术是当今使用最广的一种无线网络传输技术。 由 于 WiFi***釆用了载波侦听 /冲突避免 ( CSMA/CA, Carrier Sense Multiple Access with Collision Avoidance )机制, ***效率较 ^ [氐,对无线资源 -浪费较大。 导致这一问题的根本原因是 CSMA/CA机制是一种基于竟争的随机多址接入 机制, 中心接入点 (CAP, Access Point )和站点 ( STA, Station ), 或者不同 STA之间, 会通过 CSMA/CA机制竟争无线资源的使用权, 同时竟争无线信 道, 此时就发生碰撞, 导致无线资源的浪费。 为了避免碰撞, CSMA/CA机 制要求 CAP或 STA在竟争无线信道时需要随机退避, 在所有 CAP和 STA 都退避时, 无线信道虽有空闲, 但并未被使用, 这也是对无线信道的极大浪 费。 由于上述原因, 802.11 ***效率较低。 例如: 802. l lg***物理层峰值速
率可达 54Mbps, 但 TCP层在大数据包下载业务下可达速率不高于 30Mbps。 虽然存在上述缺点, 但 802.11 ***灵活, 不依赖集中控制机制, 因此也能够 实现较低的设备成本。
基于 3GPP标准的 Femto技术是从移动通信***演进而来的一种面向室 内覆盖的新技术。 基于对 3G***的数据统计, 大约 70%的数据业务都发生 在室内, 因此室内高速率数据接入方案就尤为重要。 Femto基站, 称为微微 基站, 体积小巧(与 Wi-Fi近似 ),部署灵活。 由于从移动通信***演进而来, Femto基站几乎继承了移动通信***的所有特点。 Femto设备只是结合其有 限的覆盖范围, 较少的接入用户等应用场景特征, 将设备处理能力降低, 进 而降低设备成本。 从双工方式考虑, 与移动通信***相同, Femto基站可分 为 FDD与 TDD两类双工机制。 FDD上下行载波资源对称, 而数据业务上下 行数据流量非对称的业务特征使得 FDD***面对数据业务时存在一定的资 源浪费。 TDD***上下行链路工作在同一载波上, 通过划分时间资源为上下 行链路分配不同的无线资源, 因此较 FDD能够更好的适配上下行业务需求 非对称的数据业务。 然而, 移动通信*** (包括 Femto***) 的 TDD双工 方式, 上下行资源静态分配, 面对需求不同的各类数据业务, 例如: 浏览网 页, 移动视频, 移动游戏等, 难以实现业务需求与资源划分的动态适配。 与 Wi-Fi相比, 由于 Femto釆用了基于调度的集中控制机制, 基站或 CAP和终 端或者终端之间不存在由于竟争冲突和随机退避导致的无线资源浪费, 因此 链路效率较高。
无线通信***中的数据传输, 指的是通信对端通过交互完成数据收发, 这种交互可以是网络侧和终端之间的交互, 还可以是终端之间的交互。
为了管理更精细, 希望在通信对端之间可以基于多个链接分别传输不同 的数据, 即基于业务流的数据传输, 由此存在业务流管理的需求。 发明内容
有鉴于此, 本发明的目的是提供业务流管理方法及装置。
为了对披露的实施例的一些方面有一个基本的理解, 下面给出了筒单的 概括。 该概括部分不是泛泛评述, 也不是要确定关键 /重要组成元素或描绘 这些实施例的保护范围。 其唯一目的是用筒单的形式呈现一些概念, 以此作 为后面的评细说明的序言。
本发明的技术方案是这样实现的:
一种业务流管理方法, 该方法包括:
发送携带业务流标识 FID和 FID最大緩冲能力的动态业务管理请求; 接收针对动态业务管理请求的响应。
一种实施例中, 所述针对动态业务管理请求的响应为: 指示所述动态业 务管理请求正确接收的确认。
可选的, 还包括: 在所述动态业务管理请求中携带目的端标识、 业务参 数和方向信息中的一种或几种,其中所述方向信息指示业务流为上行或下行。
一种实施例中, 所述 4十对动态业务管理请求的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
可选的, 还包括: 发送指示所述动态业务管理响应正确接收的确认。 可选的, 还包括: 在所述动态业务管理请求中携带目的端标识、 业务参 数和方向信息中的一种或几种,其中所述方向信息指示业务流为上行或下行。
可选的, 当所述动态业务管理请求中携带业务参数时, 所述动态业务管 理响应还携带调整后的业务参数。
一种实施例中,还包括: 在发送所述动态业务管理请求后等待设定帧数, 如果未收到所述响应, 重新发送所述动态业务管理请求, 或者, 结束本次流 程。
一种业务流管理方法, 该方法包括:
接收携带 FID和 FID最大緩冲能力的动态业务管理请求;
发送针对动态业务管理请求的响应。
一种实施例中, 所述针对动态业务管理请求的响应为: 指示所述动态业 务管理请求正确接收的确认。
可选的, 所述动态业务管理请求中还携带目的端标识、 业务参数和方向 信息中的一种或几种, 其中所述方向信息指示业务流为上行或下行。
一种实施例中, 所述 4十对动态业务管理请求的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
可选的, 还包括: 接收指示所述动态业务管理响应正确接收的确认。 可选的, 还包括: 在发送所述动态业务管理响应后等待设定帧数内, 如 果未收到所述确认, 重新发送所述动态业务管理响应。
可选的, 所述动态业务管理请求中还携带目的端标识、 业务参数和方向 信息中的一种或几种。
可选的, 当所述动态业务管理请求中携带业务参数时, 该方法还包括: 根据动态业务管理请求中携带的业务参数确定预留的资源, 根据所述预留的 资源调整所述动态业务管理请求中携带的业务参数, 并在所述动态业务管理 响应中携带调整后的业务参数。
一种业务流管理装置, 该装置包括:
请求发送单元, 用于发送携带业务流标识 FID和 FID最大緩冲能力的动 态业务管理请求;
响应接收单元, 接收针对动态业务管理请求的响应。
一种实施例中, 所述针对动态业务管理请求的响应为: 指示所述动态业 务管理请求正确接收的确认。
可选的, 该装置还包括: 参数提供单元, 用于将目的端标识、 业务参数 和方向信息中的一种或几种发送给所述请求发送单元, 供其携带在动态业务 管理请求中发送;
所述方向信息指示业务流为上行或下行。
可选的, 该装置还包括: 监控单元, 用于在所述请求发送单元发送所述 动态业务管理请求后的设定帧数内监控所述响应接收单元, 如果所述响应接 收单元未收到所述响应, 通知所述请求发送单元重新发送所述动态业务管理 请求。
可选的, 所述请求发送单元将所述动态业务管理请求封装为媒体接入控 制协议数据单元 MPDU发送,当重新发送所述动态业务管理请求超过 MPDU 重传次数时, 丟弃动态业务管理请求, 并通知业务流删除装置执行操作。
一种实施例中, 所述针对动态业务管理请求的响应为: 携带所述 FID的 动态业务管理响应。
可选的, 该装置还包括: 确认单元, 用于发送指示所述动态业务管理响 应正确接) 的确认。
可选的, 该装置还包括: 参数提供单元, 用于将目的端标识、 业务参数 和方向信息中的一种或几种发送给所述请求发送单元, 供其携带在动态业务 管理请求中发送, 其中所述方向信息指示业务流为上行或下行。
可选的, 当动态业务管理请求中携带业务参数时, 动态业务管理响应还 携带调整后的业务参数。
一种实施例中, 该装置还包括: 监控单元, 用于在所述请求发送单元发 送所述动态业务管理请求后的设定帧数内监控所述响应接收单元, 如果所述 响应接收单元未收到所述响应, 通知所述请求发送单元结束本次流程。
一种业务流管理装置, 其特征在于, 该装置包括:
请求接收单元, 用于接收携带 FID和 FID最大緩冲能力的动态业务管理 请求;
响应发送单元, 用于发送针对动态业务管理请求的响应。
一种实施例中, 所述针对动态业务管理请求的响应为: 指示所述动态业 务管理请求正确接收的确认。
可选的, 所述动态业务管理请求中还携带目的端标识、 业务参数和方向 信息中的一种或几种,其中所述方向信息指示要建立的业务流为上行或下行。
一种实施例中, 所述 4十对动态业务管理请求的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
可选的, 该装置还包括: 确认接收单元, 用于接收指示所述动态业务管 理响应正确接收的确认。
可选的, 该装置还包括: 监控单元, 用于在所述响应发送单元发送动态 业务管理响应后的设定帧数内监控所述确认接收单元, 如果所述确认接收单 元未收到所述确认, 触发所述响应发送单元重新发送动态业务管理响应。
可选的, 所述响应发送单元将所述动态业务管理响应封装成 MPDU发 送, 当所述重新发送超过 MPDU重传次数时, 丟弃动态业务管理响应, 并通 知业务流删除装置执行操作。
可选的, 所述动态业务管理请求中还携带目的端标识、 业务参数和方向 信息中的一种或几种。
可选的, 该装置还包括业务参数调整单元, 用于在动态业务管理请求中 携带业务参数时,根据动态业务管理请求中携带的业务参数确定预留的资源, 根据所述预留的资源调整所述动态业务管理请求中携带的业务参数, 并将调 整后的业务参数发送给所述响应发送单元, 供其携带在动态业务管理响应中 发送。
为了上述以及相关的目的, 一个或多个实施例包括后面将详细说明并在 权利要求中特别指出的特征。下面的说明以及附图评细说明某些示例性方面, 并且其指示的仅仅是各个实施例的原则可以利用的各种方式中的一些方式。 其它的益处和新颖性特征将随着下面的详细说明结合附图考虑而变得明显, 所公开的实施例是要包括所有这些方面以及它们的等同。 附图说明
图 1为本发明中业务流建立的方法流程图;
图 2为本发明中业务流爹改的方法流程图;
图 3为增强型超高速无线局域网 (EUHT ) ***无线通信***的参考模 型;
图 4为 EUHT***的接入***组成;
图 5为 STA和 CAP之间协议数据的发送和接收的过程示意图; 图 6为本发明实施例中上行业务流建立及发送数据的方法流程图; 图 7为本发明实施例中动态业务建立请求帧的结构示意图;
图 8为本发明实施例中动态业务建立响应帧的结构示意图;
图 9为本发明实施例中上行业务流爹改及发送数据的方法流程图; 图 10为本发明实施例中下行业务流建立及发送数据的方法流程图; 图 11为本发明实施例中下行业务流爹改及发送数据的方法流程图; 图 12为本发明中第一种业务流建立装置的结构示意图;
图 13为图 12所示的装置位于 CAP侧时的结构示意图;
图 14为图 12所示的装置位于 STA侧时的结构示意图;
图 15为本发明中第二种业务流建立装置的结构示意图;
图 16为图 15所示的装置位于 CAP侧时的结构示意图;
图 17为本发明中第一种业务流修改装置的结构示意图;
图 18为图 17所示装置位于 CAP侧时的结构示意图;
图 19为图 17所示装置位于 STA侧时的结构示意图;
图 20为本发明第二种业务流修改装置的结构示意图;
图 21为图 20所示装置位于 CAP侧时的结构示意图;
图 22为本发明中业务流管理的方法流程图;
图 23为本发明中第一种业务流管理装置的结构示意图;
图 24为图 23所示装置位于 CAP侧时的结构示意图;
图 25为图 23所示装置位于 STA侧时的结构示意图;
图 26为本发明中第二种业务流管理装置的结构示意图;
图 27为图 26所示装置位于 CAP侧时的结构示意图;
图 28为本发明中业务流删除的方法流程图;
图 29为本发明实施例中上行业务流删除的方法流程图;
图 30为本发明实施例中动态业务删除请求帧的结构示意图;
图 31为本发明实施例中上行或下行业务流删除的方法流程图; 图 32为本发明中第一种业务流删除装置的结构示意图;
图 33为图 32所示装置位于 CAP侧时的结构示意图;
图 34为本发明中第二种业务流删除装置的结构示意图;
图 35为图 34所示装置位于 CAP侧时的结构示意图;
图 36为本发明中第一种用于业务流建立的方法流程图;
图 37为本发明中第二种用于业务流建立的方法流程图;
图 38为本发明中第一种用于业务流修改的方法流程图;
图 39为本发明中第二种用于业务流修改的方法流程图;
图 40为本发明中第三种用于业务流建立的方法流程图;
图 41为本发明中第四种用于业务流建立的方法流程图;
图 42为本发明中第三种用于业务流修改的方法流程图;
图 43为本发明中第四种用于业务流爹改的方法流程图;
图 44为本发明中第一种用于业务流删除的方法流程图;
图 45为本发明中第二种用于业务流删除的方法流程图。 具体实施方式
以下描述和附图充分地示出本发明的具体实施方案, 以使本领域的技术 人员能够实践它们。 其他实施方案可以包括结构的、 逻辑的、 电气的、 过程 的以及其他的改变。 实施例仅代表可能的变化。 除非明确要求, 否则单独的 组件和功能是可选的, 并且操作的顺序可以变化。 一些实施方案的部分和特 征可以被包括在或替换其他实施方案的部分和特征。 本发明的实施方案的范 围包括权利要求书的整个范围, 以及权利要求书的所有可获得的等同物。 在 本文中, 本发明的这些实施方案可以被单独地或总地用术语 "发明" 来表示,
这仅仅是为了方便, 并且如果事实上公开了超过一个的发明, 不是要自动地 限制该应用的范围为任何单个发明或发明构思。
图 1为本发明中业务流建立的方法流程图, 该流程包括:
步骤 11: 发送携带业务流标识 ( FID ) 和目的端标识的动态业务建立请 求。
步骤 12: 接收针对动态业务建立请求的响应。
经过步骤 11〜步骤 12, 建立上述 FID对应的业务流, 可以是上行业务流 或下行业务流。
在建立业务流之后, 可以在建立的 FID对应的业务流上发送业务数据, 无需在每次发送数据时都携带目的端标识, 而只用上述 FID指示数据传输。
图 2为本发明中业务流爹改的方法流程图, 该流程包括:
步骤 21 : 发送携带目的端标识、 FID及新的业务参数的动态业务修_改请 求。
根据新的业务参数, 可以对 FID及目的端标识对应的当前业务参数进行 修改。
步骤 22: 接收 4十对所述动态业务修 _改请求的响应。
经过步骤 21〜步骤 22, 修改上述 FID对应的业务流, 可以是上行业务流 或下行业务流。
在爹改业务流之后, 可以在爹改后的所述 FID对应的业务流上发送业务 数据, 无需在每次发送数据时都携带目的端标识, 而只用上述 FID指示数据 传输。
上述业务流建立和业务流爹改统称为业务流管理, 其中业务流爹改可以 看成是特殊情况下的业务流建立, 相当于是在保留原有 FID的情况下的一种 业务 ^建立。
可以看出, 本发明在进行数据传输之前, 通过业务流管理, 建立或修改 请求端和目的端之间以 FID标识的 "连接", 因此当请求端与目的端在该业 务流上进行数据传输时, 可以只使用 FID作为标识、 而不必在交互的每个数 据包中都携带目的端标识, 筒化了操作。
在以下举出的实施例中, 均以目前新定义的 EUHT***为应用背景, 图 3为 EUHT***的参考模型。
图 3所示的***参考模型主要是指空中接口参考模型, 包括: 媒体接入 控制 (MAC ) 层和物理 (PHY ) 层, 各层的主要功能筒述如下:
① MAC层包括适配子层和 MAC子层。
适配子层: 主要提供外部网络数据和本部分 MAC 艮务数据单元 ( MSDU )之间的映射和转换的功能。 这里的 MSDU, 指 MAC服务访问点 ( SAP )之间作为单元而交付的信息。 具体的, 适配子层完成功能如下: 接收来自上层的服务数据单元 (SDU);
对接收的上层 SDU进行分类;
将本层生成的适配子层的 PDU送给 MAC 子层;
接收对等实体中适配子层的 SDU。
MAC子层: 除了担当媒体接入控制功能外, 还包括对***的管理和控 制以及对 PHY层的特定功能的支持。 具体的, MAC子层基本功能分为管理 控制平面和数据平面。
管理控制平面包括如下功能:
***配置: 管理***配置消息, 并和终端交互***配置信息;
无线资源管理: 主要完成业务调度功能, 基于业务参数和信道条件完成 资源分配, 具备负载均衡、 接入控制等功能;
入网管理: 负责初始化和接入流程, 产生接入流程所需的消息, 包括: 接入码选择、 能力协商等;
服务质量( QoS )管理: 管理业务的 QoS参数,并维护每个业务流的建立、 爹改和删除等;
节电管理: 管理无业务的 STA进入休眠状态, 以及从休眠状态回到激活 状态;
PHY层控制: 主要包括以下子功能
信道管理: 包含信道切换, 管理频谱测量和消息报告;
多入多出 (MIMO )管理: 信道探测机制; MIMO工作模式确定和选择; 链路自适应: 信道质量信息 (CQI ) 测量和反馈; MCS选择和反馈; 功 率的控制和管理。
数据平面包括如下功能:
自动请求重传 ( ARQ ): 对 MAC层的 MPDU或者分片 /聚合 MPDU的 确认和重传操作;
分片 /重组:根据调度结果发端将上层业务数据单元进行分片处理后发送 给下一个处理模块, 在接收端将多个分片重组恢复;
MPDU生成: 将上层业务单元封装成基本的 MAC帧, 然后发送给下一 个处理模块;
MPDU聚合: 根据调度结果发端将上层业务数据单元进行聚合操作。 ② PHY层: 主要提供将 MAC协议数据单元 ( MPDU )映射到相应的物 理信道的 PHY传输机制, 例如正交频分复用( OFDM )和多入多出( MIMO ) 技术。这里的 MPDU, 指两个对等 MAC实体之间利用 PHY层服务所交换的 数据单元。
图 4为 EUHT***的接入***组成, 包括中心接入点 (CAP ) 和站点 ( STA ), 其中 STA可以为各种数据设备, 例如: PDA, 笔记本、 照相机、 摄像机、 手机、 平板电脑和 pad等。 如图 2所示, STA1和 STA2 通过空中 接口协议接入 CAP, CAP通过有线或者无线与现有的外部网络 (如 IP骨千 网、以太网)建立通信。其中 CAP的协议组成包括 MAC层和 PHY层。 STA 协议组成包括应用 (Application ) 层、 传输控制 (TCP ) 层、 网络 (IP ) 层、 MAC层和 PHY层。
基于图 4所示的协议组成, 图 5给出了 STA和 CAP之间协议数据的发 送和接收的过程, 例如: STA想发送数据给 CAP, STA首先将应用数据(如 VoIP, 视频等) 经过应用层、 TCP/IP层处理并打包, 以 IP分组的形式发送 给适配子层, 由适配子层进行转换、 映射和业务流划分, 发送给 MAC子层, MAC子层经过分片、 加密、 成帧、 聚合等操作, 发给 PHY层, 最终由 PHY 映射到无线信道上进行数据传输。
本发明中请求端和目的端之间的连接, 需要分别独立的建立上行和下行 业务流。
作为一种可选的实施例, 图 6为本发明实施例中上行业务流建立及数据 传输的方法流程图, 该流程包括:
步骤 61: CAP接收 STA发送的携带 FID和目的 MAC地址的动态业务 建立请求帧。
本实施例中, 将目的 MAC地址作为目的端标识。 这里的目的端可以是 CAP, 也可以是 CAP范围内的其他 STA。
本实施例中, 动态业务建立请求由动态业务建立请求帧实现。
图 7为本发明实施例中动态业务建立请求帧的结构示意图, 该动态业务 建立请求帧包括: 帧控制字段、 FID字段、 业务类型字段、 方向字段、 业务 保障速率字段、 目的端 MAC地址字段、 FID最大緩冲能力字段、 FCS字段。 图 7还给出了各字段占用的比特数举例。图 7中所示帧中除帧控制字段和 FCS 字段外的部分称为帧体。
图 7中给出的各个字段的含义介绍如下:
① 上述帧控制字段中包括与帧类型相关的标识,指示该帧为动态业务建 立请求帧。
② 上述 FCS字段为校儉字段。
③ 上述 FID字段指示 FID。
④ 上述业务类型字段指示要建立的业务流的业务类型。
业务流的 QoS参数如下:
业务类型, 此参数唯一确定业务的种类;
业务优先级, 此参数规定了分配给一个业务流的优先级。 对于给定的两 个业务流, 若除优先级外, 所有 QoS参数都相同, 高优先级业务流应得到较 低的时延和较高的緩存。
业务保障速率, 此参数定义了保障本业务的基本速率, 单位比特每秒, 其与 IP适配层输入的 SDU相匹配。 此参数不包括 MAC开销。
最大业务速率, 此参数描述了***提供给业务的最大业务速率, 用于速 率整形, 超出该速率的额外数据将会被 CAP丟弃, 单位比特每秒, 其与 IP 适配层输入的 SDU相匹配。 此参数不包括 MAC开销。
本实施例中, 根据业务的 QoS参数, 在 MAC层定义八种业务类型, 分 为预留资源类和不预留资源类两大类, 如下面的表 1所示。 其中业务类型 1 到 4属于预留资源类, ***为这类业务保证传输比特速率, 业务类型 5到 8 属于不预留资源类, ***不为这类业务保证传输比特速率。
表 1
业 贝 优 时延 丟包 业务举例
务类型 源类型 先级 预算 率预算
0 2 100 10-2 语音会话
预 ms
1 留资源 4 150 10-3 视频会话 (实时流业
ms 务)
2 3 50 10-3 实时游戏
ms
3 5 300 10-6 非会话类视频(緩存流
ms 业务)
4 1 100 10-6 信令
ms
5 6 100 10-3 交互式游戏
不 ms
6 预留资 7 300 10-6 视频 (緩存流业务) 源 ms 基于 TCP的业务(例 如, WWW, FTP, P2P文 件共享等)
7 8 1000 10-6 对传输时间要求低的
ms 后台 E-Mail接收、 文件下 载和文件打印等
⑤ 上述方向字段指示要建立的业务流是上行业务流还是下行业务流。
CAP通过该字段可以直接获知当前要建立的业务流的方向。
⑥ 上述业务保障速率字段指示保障业务的基本速率,单位比特每秒, 其 与适配子层输入的 SDU相匹配。此参数不包括 MAC开销。由于实际应用中, 业务的种类很多, 例如表 1 中列出的语音、 实时会话等, 通过该字段可以指 示 STA针对各种不同业务所希望得到的业务保障速率, 提高了应用灵活性。 对于表 1 中所列出的不预留资源的业务类型, STA也可以上报所希望得到的 业务保障速率。
⑦ 上述目的端 MAC地址字段指示目的端的 MAC地址。 CAP通过该字 段可以直接获知动态业务建立请求所针对的目的端。 这里的目的端可以是 CAP本身, 也可以是该 CAP范围内的另一个 STA。
⑧ 上述 FID最大緩冲能力字段指示 STA希望 CAP最多緩冲的 MPDU 的个数。
上述业务类型和业务保障速率可以统称为业务参数。
步骤 62: CAP向 STA发送动态业务建立响应帧。
本实施例中的业务建立响应由动态业务建立响应帧实现。
对应图 7给出的动态业务建立请求帧的结构, 图 8为本发明实施例中动 态业务建立响应帧的结构示意图, 该动态业务建立响应帧中包括: 帧控制字 段、 FID字段、 业务类型字段、 预留字段、 业务保障速率字段、 业务最大速 率字段、 FID最大緩冲能力字段和 FCS字段。 图 8还给出了各字段占用的比 特数举例。
图 8中给出的各个字段的介绍如下:
① 上述帧控制字段中包括与帧类型相关的标识,指示该帧为动态业务建 立响应巾贞。
② 上述 FCS字段为校儉字段。
③ 上述 FID字段中的内容与动态业务建立请求帧中的相同。
④ 上述业务类型字段中的内容与动态业务建立请求帧中的相同。
⑤ 上述业务保障速率字段指示 CAP允许的业务保障速率值。 CAP可以 对动态业务建立请求帧中的业务保障速率进行调整, 调整的依据主要是当前 资源是否足够提供该业务保障速率。 对于预留资源的业务类型, 如果当前资 源有限, 无法保证动态业务建立请求帧中上 4艮的业务保障速率, 则 CAP可以 根据实际情况对 STA上报的业务保障速率进行调整。对于不预留资源的业务 类型, 无论 STA是否在动态业务建立请求帧中上艮了业务保障速率, CAP 都直接将 STA上报的业务保障速率调整为 0, 但是当前资源除了为预留资源 的业务提供业务保障速率外还剩余较多资源时, CAP可以为 STA请求的业 务分配资源、 并向 STA指示所分配的资源。
对于预留资源的业务类型来说, STA在解析该字段后, 可以决定是否继 续进行数据传输, 假设解析业务保障速率小于上报的业务保障速率时, STA 可以选择不继续进行数据传输。
对于不预留资源的业务类型来说, 如果 CAP分配了资源, STA可以选 择利用该分配的资源继续进行数据传输。
⑥ 业务最大速率字段中指示针对所请求的业务,***所能提供的最大业 务速率, 用于速率整形, 超出该速率的额外数据将会被丟弃, 单位比特每秒,
其与 IP适配层输入的 SDU相匹配。 此参数不包括 MAC开销。 最大业务速 率是预先设定的值。
⑦ FID最大緩冲能力字段指示 CAP最多可緩存的 MPDU的个数, 该字 段中携带的数值可以是动态业务建立请求帧中上报的数值, 也可以是 CAP 根据实际情况进行调整后的数值。
CAP记录 FID、 目的 MAC地址及对应业务参数、 最大业务速率等信息。 进一步, STA可以在正确接收动态业务建立响应帧后, 向 CAP发送确 认, 具体的, STA可以向 CAP发送 ACK, 也可以向 CAP发送组确认
( GroupAck ), 本发明实施例提出一种组确认方式, 组确认帧中包括管理控 制帧指示位, 还包括对应同一用户不同业务流的位图 ( bitmap ), 这里 STA 可以在上述管理控制帧指示位中填写指示动态业务建立响应帧正确接收与否 的指示, 后续在基于业务流进行数据传输时, STA可以利用组确认帧中的 bitmap, 将针对不同业 ^流的确认一起发送给 CAP。
步骤 63: STA利用 CAP分配的上行传输资源发送数据。
本步骤有三种实现方式:
1 ) STA可以通过发送独立资源请求、 向 CAP请求上行传输资源; 进一 步, CAP在正确接收到独立资源请求后, 可以向 STA发送确认;
2 )当 CAP的资源足够时, CAP可以主动对每个 STA进行轮询并分配上 行传输资源;
3 ) 如果 STA当前有其他业务数据传输, 可以在业务数据帧中携带随路 资源请求, 向 CAP请求上行传输资源, 进一步, CAP在正确接收到随路资 源请求后, 可以向 STA发送确认。
CAP通过控制信道( CCH ) 指示分配给 STA的上行传输资源。
通过上述步骤 61〜步骤 63 , 建立了上行业务流并基于该上行业务流发送 数据。
作为一种可选的实施例, 上行业务流爹改的过程与上述图 6所示类似, 图 9为本发明中上行业务流爹改及发送数据的方法流程图。 动态业务修 _改请 求帧中包括的字段和图 7所示相同, 动态业务修改响应帧中包括的字段和图 8所示相同。 在上行业务流爹改时, 动态业务修 _改请求帧中携带的 FID和目 的端标识是 CAP已经记录过的,且动态业务修改请求帧中携带是新的业务参 数, 例如新的业务类型和新的业务保障速率, CAP在收到动态业务修改请求 帧后, 也可以基于当前资源对新的业务参数进行适当调整, 调整方法与前文 已介绍过的相同, 然后 CAP将已记录的 FID和目的端标识所对应的当前业 务参数, 修改为调整后的新的业务参数, 并将修改后的业务参数携带在动态 业务爹改响应帧中发送给 STA。 在动态业务修 _改请求帧中携带新的业务参数 时, 动态业务修改请求帧携带的 FID最大緩冲能力, 可以是新的数值, 也可 以是原有数值。
作为一种可选的实施例, 图 10为本发明实施例中下行业务流建立及发 送数据的方法流程图, 该流程包括:
步骤 101 : STA接收 CAP发送的携带 FID和目的 MAC地址的动态业务 建立请求帧。
本实施例中, 动态业务建立请求由动态业务建立请求帧实现。
本步骤中, 动态业务建立请求帧中包括的字段与图 7所示的相同、 且各 字段承载的内容也基本相同,只是其中 FID最大緩冲能力字段指示的是 CAP 希望 STA最多緩冲的 MPDU的个数。
这里的目的 MAC地址指的就是接收动态业务建立请求帧的 STA。
步骤 102: STA向 CAP发送 ACK。
^步骤中, STA直接向 CAP反馈 ACK, 并保存 FID和目的端标识及动 态业务建立请求帧中携带的各项参数。
本步骤中, STA也可以发送 GroupAck。
步骤 103: STA接收 CAP发送的数据, 同时获知发送该数据的下行传输 资源。
CAP通过 CCH在发送数据的同时指示下行传输资源。
通过上述步骤 101-103 , 建立了下行业务流并在该下行业务流上发送数 据。
作为一种可选的实施例, 下行业务流爹改的过程与上述图 10类似, 图 11为本发明中下行业务流修改的方法流程图。 动态业务修改请求帧中包括的 字段和图 7所示相同。 但是在下行业务流爹改时, 动态业务修 _改请求帧中携 带的 FID和目的端标识是 STA已经记录过的,且动态业务修_改请求帧中携带 的是新的业务参数, 例如新的业务类型和新的业务保障速率。 STA更新已保 存的 FID和目的端标识对应的各项新的业务参数。 在动态业务修 _改请求帧中 携带新的业务参数时, 动态业务修改请求帧中携带的 FID最大緩冲能力, 可 以新的数值, 也可以是原有数值。
下面给出本发明方法的一个具体举例, 假设一个 CAP范围内有多个 STA, 当两个 STA需要进行数据传输时, 可以使用本发明的方法。 例如位于 CAP范围内的 STA1和 STA2需要进行数据传输, STA1先与 CAP建立上行 业务流, 在上行业务流的建立过程中, CAP获知了目的端为 STA2, 可以与 STA2建立下行业务流。 由于 CAP具有緩存能力, 在 CAP与 STA2建立下行 业务流时, STA1就可以向 CAP发送数据,当下行业务流建立完成后,由 CAP 将该緩存的 STA1发送的数据转发给 STA2。 STA2要向 STA1发送数据, 也 是相同的过程, 即先建立 STA2到 CAP的上行业务流, 再建立 CAP到 STA1 的下行业务流, 然后在建立的业务流上发送 STA2到 STA1的数据。
本发明中第一种业务流建立装置位于请求端, 该请求端可以位于 STA 侧, 也可以位于 CAP侧。
图 12为本发明中第一种业务流建立装置的结构示意图, 该装置中包括: 请求发送单元 121和响应接收单元 122。
请求发送单元 121 , 发送携带目的端标识及 FID的动态业务建立请求。 响应接收单元 122, 接收 4十对动态业务建立请求的响应。
当本发明中第一种业务流建立装置位于 CAP侧时,作为一种可选的实施 例, 其结构如图 13所示, 该装置包括: 请求发送单元 131、 响应接收单元 132、业务参数提供单元 133、方向信息提供单元 134、緩冲能力提供单元 135 和监控单元 136。
请求发送单元 131, 发送携带目的端标识及 FID的动态业务建立请求。 响应接收单元 132, 接收 4十对动态业务建立请求的响应。 响应接收单元 132接收到的动态业务建立请求的响应为 ACK或 GroupAck。
业务参数提供单元 133, 用于将业务参数发送给请求发送单元 131, 供 其携带在动态业务建立请求中发送。
方向信息提供单元 134, 用于将指示要建立的业务流为上行或下行的方 向信息发送给请求发送单元 131, 供其携带在动态业务建立请求中发送。
緩冲能力提供单元 135, 用于将 FID最大緩冲能力提供给请求发送单元 131, 供其携带在动态业务建立请求中发送。 FID最大緩冲能力指示期望动态 业务建立请求的接收端最多緩存的 MPDU的个数。
监控单元 136, 用于在请求发送单元 131发送动态业务建立请求后的设 定帧数内监控响应接收单元 132, 如果响应接收单元 132未收到所述响应, 通知请求发送单元 131重新发送动态业务建立请求。 在此基础上, 请求发送 单元 131将动态业务建立请求封装为 MPDU发送,当重新发送动态业务建立 请求超过 MPDU最大重传次数时, 丟弃动态业务建立请求, 并通知业务流删 除装置执行操作。
当本发明第一种业务流建立装置位于 STA侧时, 作为一种可选的实施 例, 其结构如图 14所示, 该装置包括: 请求发送单元 141、 响应接收单元 142、 确认单元 143、 业务参数提供单元 144、 方向信息提供单元 145、 緩冲 能力提供单元 146和监控单元 147。
请求发送单元 141, 发送携带目的端标识及 FID的动态业务建立请求。 响应接收单元 142, 接收 4十对动态业务建立请求的响应。 响应接收单元 142接收到的动态业务建立请求的响应为携带所述 FID的动态业务建立响 应。 进一步, 响应接收单元 142接收的动态业务建立响应还可以携带***能 提供的最大业务速率。
确认单元 143, 用于发送指示动态业务建立响应正确接收的 ACK或 GroupAck„
业务参数提供单元 144, 用于将业务参数发送给请求发送单元 141, 供 其携带在动态业务建立请求中发送。 在此基础上, 动态业务建立响应中可以 携带调整后的业务参数。
方向信息提供单元 145, 用于将指示要建立的业务流为上行或下行的方 向信息发送给请求发送单元 141, 供其携带在动态业务建立请求中发送。
緩冲能力提供单元 146, 用于将 FID最大緩冲能力提供给请求发送单元 141, 供其携带在动态业务建立请求中发送, 所述 FID最大緩冲能力指示期 望所述动态业务建立请求的接收端最多緩存的 MPDU的个数。
监控单元 147, 用于在请求发送单元 141发送动态业务建立请求后的设 定帧数内监控响应接收单元 142, 如果响应接收单元 142未收到所述响应, 通知请求发送单元 141结束本次流程。
可选的, 无论本发明第一种业务流建立装置位于 STA侧还是 CAP侧, 该装置都可以进一步包括: 数据传输单元, 用于在已建立的所述 FID对应的 业务流上发送业务数据。
可选的, 无论本发明第一种业务流建立装置位于 STA侧还是 CAP侧, 都可以只包括方向信息提供单元和緩冲能力提供单元中的一个。
本发明中第二种业务流建立装置位于请求接收端, 该请求接收端可以位 于 STA侧, 也可以在 CAP侧。
图 15为本发明中第二种业务流建立装置的结构示意图, 该装置包括: 请求接收单元 151和响应发送单元 152。
请求接收单元 151, 用于接收携带目的端标识及 FID的动态业务建立请 求。
响应发送单元 152, 用于发送针对所述动态业务建立请求的响应。
当本发明第二种业务流建立装置位于 STA侧时,请求接收单元 151接收 的动态业务建立请求中还可以携带业务参数。 响应发送单元 152发送的是
ACK或 Group Ack„
当本发明第二种业务流建立装置位于 CAP侧时, 作为一种可选的实施 例, 其结构如图 16所示, 该装置包括: 请求接收单元 161、 响应发送单元
162、 确认接收单元 163、 监控单元 164、 业务参数调整单元 165和业务最大 速率确定单元 166。
请求接收单元 161, 用于接收携带目的端标识及 FID的动态业务建立请 求。
响应发送单元 162, 用于发送针对所述动态业务建立请求的响应。 响应 发送单元 162发送的是携带所述 FID的动态业务建立响应。
确认接收单元 163, 用于接收指示所述动态业务建立响应正确接收的 ACK或 GroupAck„
监控单元 164, 用于在响应发送单元 162发送所述动态业务建立响应后 的设定帧数内监控确认接收单元 163,如果确认接收单元 163未收到 ACK或 GroupAck, 通知响应发送单元 163重新发送所述动态业务建立响应。 在此基 础上, 响应发送单元 162将动态业务建立响应封装成 MPDU发送, 当所述重 新发送超过 MPDU最大重传次数时, 丟弃动态业务建立响应, 并通知业务流 删除装置执行操作。
业务参数调整单元 165, 用于调整动态业务建立请求中携带的业务参数, 并将调整后的业务参数发送给响应发送单元 162, 供其携带在所述响应中发 送。
业务最大速率确定单元 166, 用于确定***能提供的最大业务速率, 并 发送给响应发送单元 162, 供其携带在响应中发送。
可选的, 无论本发明第二种业务流建立装置位于 STA侧还是 CAP侧, 都可以进一步包括: 数据传输单元, 用于接收在已建立的所述 FID对应的业 务流上发送的业务数据。
可选的, 无论本发明第二种业务流建立装置位于 STA侧还是 CAP侧, 请求接收单元接收的动态业务建立请求中都可以携带方向信息和 /或 FID最 大緩冲能力,其中所述方向信息指示要建立的业务流为上行或下行,所述 FID 最大緩冲能力指示期望所述动态业务建立请求的接收端最多緩存的 MPDU 的个数。
本发明第一种业务流修改装置位于请求端, 该请求端可以位于 CAP侧, 也可以位于 STA侧。
图 17为本发明中第一种业务流修改装置的结构示意图, 该装置中包括: 请求发送单元 171和响应接收单元 172。
请求发送单元 171, 发送携带目的端标识、 FID及新业务参数的动态业 务爹改请求。
响应接收单元 172, 接收携带所述 FID的动态业务爹改响应。
作为一种可选的实施例, 当本发明第一种业务流爹改装置位于 CAP侧 时, 其结构如图 18所示, 该装置包括: 请求发送单元 181、 响应接收单元 182、 监控单元 183、 方向信息提供单元 184和緩冲能力提供单元 185。
请求发送单元 181, 发送携带目的端标识、 FID及新业务参数的动态业 务爹改请求。
响应接收单元 182, 接收携带所述 FID的动态业务爹改响应。 响应接收 单元 182接收到的响应为 ACK或 GroupAck。
监控单元 183, 用于在请求发送单元 181发送动态业务修改请求后的设 定帧内监控响应接收单元 182, 如果响应接收单元 182未收到所述响应, 通 知请求发送单元 181重新发送动态业务爹改请求。 在此基础上, 请求发送单 元 181将动态业务修改请求封装为 MPDU发送,当重新发送动态业务修改请
求超过 MPDU最大重传次数时, 丟弃动态业务爹改请求, 并通知业务流删除 装置执行操作。
方向信息提供单元 184, 用于将指示要修改的业务流为上行或下行的方 向信息发送给请求发送单元 181, 供其携带在动态业务修改请求中发送。
緩冲能力提供单元 185, 用于将 FID最大緩冲能力提供给请求发送单元 181, 供其携带在动态业务修改请求中发送, 所述 FID最大緩冲能力表示期 望所述动态业务修改请求的接收端最多緩存的 MPDU的个数。
作为一种可选的实施例, 当本发明第一种业务流爹改装置位于 STA侧 时, 其结构如图 19所示, 该装置包括: 请求发送单元 191、 响应接收单元 192、 确认单元 193、 监控单元 194、
请求发送单元 191, 发送携带目的端标识、 FID及新业务参数的动态业 务爹改请求。
响应接收单元 192, 接收携带所述 FID的动态业务爹改响应。 响应接收 单元 182接收到的响应为动态业务爹改响应。 进一步, 该动态业务爹改响应 中携带修改后的业务参数。 再进一步, 该动态业务修改响应中携带***能提 供的最大业务速率。
确认单元 193,用于发送指示所述动态业务修改响应正确接收的 ACK或 GroupAck„
监控单元 194, 用于在请求发送单元 191发送动态业务修改请求后的设 定帧内监控响应接收单元 192, 如果响应接收单元 192未收到所述响应, 通 知请求发送单元 191结束本次流程。
方向信息提供单元 195, 用于将指示要修改的业务流为上行或下行的方 向信息发送给请求发送单元 191, 供其携带在动态业务修改请求中发送。
緩冲能力提供单元 196, 用于将 FID最大緩冲能力提供给请求发送单元 191, 供其携带在动态业务修改请求中发送, 所述 FID最大緩冲能力表示期 望所述动态业务修改请求的接收端最多緩存的 MPDU的个数。
可选的, 无论本发明第一种业务流修改装置位于 CAP侧还是 STA侧, 该装置中还可以包括: 数据传输单元, 用于在爹改后的所述 FID对应的业务 流上发送业务数据。
本发明中第二种业务流修改装置位于请求接收端, 该请求接收端可以位 于 STA侧, 也可以位于 CAP侧。
图 20为本发明第二种业务流修改装置的结构示意图, 该装置中包括: 请求接收单元 201和响应发送单元 202。
请求接收单元 201, 用于接收携带目的端标识、 FID及新的业务参数的 动态业务爹改请求。
响应发送单元 202, 用于发送针对所述动态业务爹改请求的响应。
作为一种可选的实施例, 当本发明第二种业务流爹改装置位于 STA侧 时, 响应发送单元 202发送的响应为 ACK或 GroupAck。
作为一种可选的实施例, 当本发明第二种业务流爹改装置位于 CAP侧 时,其结构如图 21所示,该装置包括:请求接收单元 211、响应发送单元 212、 确认接收单元 213、 监控单元 214、 爹改单元 215、 业务最大速率提供单元 216、
请求接收单元 211, 用于接收携带目的端标识、 FID及新的业务参数的 动态业务爹改请求。
响应发送单元 212, 用于发送 4十对所述动态业务爹改请求的响应。 响应 发送单元 212发送的响应为携带所述 FID的动态业务爹改响应。
确认接收单元 213 ,用于接收指示动态业务爹改响应正确接收的 ACK或 GroupAck„
监控单元 214, 用于在响应发送单元 212发送动态业务爹改响应后的设 定帧数内监控确认接收单元 213 , 如果确认接收单元 213未收到 ACK或 GroupAck,通知响应发送单元 212重新发送动态业务爹改响应。在此基础上, 响应发送单元 212将动态业务修 _改响应 MPDU发送, 当所述重新发送超过 MPDU最大重传次数时, 丟弃动态业务修改响应, 并通知业务流删除装置执 行操作。
修改单元 215, 用于根据新的业务参数确定为要修改的业务流预留的资 源; 根据所述预留的资源调整所述新业务参数; 根据调整后的新业务参数修 改所述 FID及目的端标识对应的当前业务参数, 并将修改后的业务参数发送 给响应发送单元 212, 供其携带在动态业务爹改响应中发送。
业务最大速率提供单元 216, 用于确定***能提供的最大业务速率, 并 发送给响应发送单元 212, 供其携带在响应中发送。
可选的, 无论本发明第二种业务流修改装置位于 STA侧还是 CAP侧, 该装置中都可以进一步包括: 数据传输单元, 用于接收在修改后的所述 FID 对应的业务流上发送的业务数据。
可选的, 无论本发明第二种业务流修改装置位于 STA侧还是 CAP侧, 请求接收单元接收的动态业务修改请求中还可以携带方向信息和 /或 FID最 大緩冲能力; 其中, 所述方向信息指示要修改的业务流为上行或下行; 所述 FID最大緩冲能力指示期望所述动态业务建立请求的接收端最多緩存的 MPDU的个数。
可选的, 本发明第一种业务流建立装置和第一种业务流修改装置位于 STA侧时, 该装置中还可以包括: 资源请求单元, 用于为发送业务数据请求 上行传输资源。
可选的, 本发明第一种业务流建立装置和第一种业务流修改装置位于 STA侧时, 该装置中还可以包括: 资源获取单元, 用于通过主动轮询, 获取 发送业务数据的上行传输资源。
可选的, 本发明第一种业务流建立装置和第一种业务流修改装置位于 CAP侧时, 该装置中还可以包括: 资源指示单元, 用于在发送所述业务数据 的同时, 指示发送业务数据的下行传输资源。
可选的, 本发明第二种业务流建立装置和第二种业务流修改装置位于 CAP侧时, 该装置中还可以包括: 资源分配单元, 用于按照请求分配发送业 务数据的上行传输资源。
可选的, 本发明第二种业务流建立装置和第二种业务流修改装置位于 CAP侧时, 该装置中还可以包括: 轮询单元, 用于通过主动轮询分配发送业 务数据的上行传输资源。
本发明还提供一种业务流管理方法, 图 22为本发明中业务流管理方法 的流程图, 该流程包括:
步骤 221 : 发送携带 FID和 FID最大緩冲能力的动态业务管理请求。 这里的 FID最大緩冲能力, 指请求端希望接收端最多緩冲 MPDU的个 数, 请求端既可以是 CAP、 也可以是 STA。
步骤 222: 接收针对动态业务管理请求的响应。
可以看出, 本发明提供的业务流管理方法中, 一方面使得每个业务流都 有各自对应的緩冲能力, 管理更精细、 更灵活, 另一方面在请求业务流管理 的同时就进行緩冲能力的协商, 节约了操作流程。
作为一种可选的实施例, 本发明提供的业务流管理方法为业务流建立方 法, 包括如下两种情况:
第一、 上行业务流建立及数据传输的方法包括如下步骤:
步骤 1 : CAP接收 STA发送的携带 FID和 FID最大緩冲能力的动态业 务建立请求帧。
本实施例中, 动态业务建立请求由动态业务建立请求帧实现。
本步骤中的动态业务建立请求帧的帧体中, 包括 FID字段和 FID最大緩 冲能力字段, 还可以包括业务类型字段、 方向字段、 业务保障速率字段和目 的 MAC地址字段中的一个或多个, 这些字段的含义与前文所述相同, 帧体 中包括所有上述字段的结构与图 7所示相同。
步骤 2: CAP向 STA发送动态业务建立响应帧。
本实施例中的业务建立响应由动态业务建立响应帧实现。
本步骤中的动态业务建立响应帧的帧体中, 除了包括 FID字段和 FID最 大緩冲能力字段之外, 还可以包括业务类型字段、 业务保障速率字段和业务 最大速率字段中的一个或多个, 这些字段的含义与前文所述相同, 帧体中包 括所有上述字段的结构与图 8所示相同。
动态业务建立响应帧携带的业务参数 (通过业务类型字段和业务保障速 率字段承载), 可以是 CAP对动态业务建立请求帧携带的业务参数进行调整 后得出的, 调整的方法举例前文中已经评述。
动态业务建立响应帧携带的 FID最大緩冲能力, 可以与动态业务建立请 求帧中的相同, 也可以是 CAP对动态业务建立请求帧携带的 FID最大緩冲 能力进行调整后得出的。
CAP记录 FID、 目的 MAC地址及对应业务参数、 业务最大速率等信息。 进一步, STA可以在正确接收动态业务建立响应帧后,向 CAP发送 ACK。 或者, STA可以向 CAP发送 GroupAck。
经过上述步骤 1-2, 不仅完成了上行业务流建立, 同时还协商了 FID最 大緩冲能力, 省去了单独协商 FID最大緩冲能力的操作, 节约操作流程。
步骤 3: STA利用 CAP分配的上行传输资源发送数据。
上行业务流爹改的过程与上述步骤 1-2类似,只是 STA发送的是与动态 业务建立请求帧结构相同的动态业务修改请求帧, 且动态业务修改请求帧中 的 FID是 CAP已经记录过的, CAP根据动态业务修改请求帧中携带参数的 情况, 更新已记录的 FID对应的 FID最大緩冲能力和 /或业务参数。 可选的,
CAP在执行更新操作之前,还可以对动态业务修 _改请求帧中携带的 FID最大 緩冲能力和 /或业务参数进行调整。
第二、 下行业务流建立及数据传输的方法包括如下步骤:
步骤 1,: STA接收 CAP发送的携带 FID和 FID最大緩冲能力的动态业 务建立请求帧。
本实施例中, 动态业务建立请求由动态业务建立请求帧实现。
本步骤中的动态业务建立请求帧的帧体中, 包括 FID字段和 FID最大緩 冲能力字段, 还可以包括业务类型字段、 方向字段、 业务保障速率字段和目 的 MAC地址字段中的一个或多个, 这些字段的含义与前文所述相同, 帧体 中包括所有上述字段的结构与图 7所示相同。
步骤 2,: STA向 CAP发送 ACK。
^步骤中, STA直接向 CAP反馈 ACK, 并保存 FID和目的端标识及动 态业务建立请求帧中携带的各项参数。
本步骤中, STA也可以向 CAP发送 GroupAck。
经过上述步骤 1,〜2,, 不仅完成了下行业务流建立, 同时还协商了 FID 最大緩冲能力, 省去了单独协商 FID最大緩冲能力的操作, 节约操作流程。
步骤 3': STA接收 CAP发送的数据, 同时获知发送该数据的下行传输 资源。
下行业务流修改的过程与上述步骤 1,〜2,类似, 只是 CAP发送的是与动 态业务建立请求帧结构相同的动态业务修改请求帧, 且动态业务修改请求帧 中的 FID是 STA 已经记录过的, STA才艮据动态业务修 _改请求帧中携带参数 的情况, 更新已记录的 FID对应的 FID最大緩冲能力和 /或业务参数。
本发明还提供两种业务流管理装置。
图 23为本发明中第一种业务流管理装置的结构示意图, 该装置位于请 求端一侧, 包括: 请求发送单元 231和响应接收单元 232。
请求发送单元 231 , 用于发送携带业务流标识 FID和 FID最大緩冲能力 的动态业务管理请求。
响应接收单元 232, 接收 4十对动态业务管理请求的响应。
作为一种可选的实施例, 当本发明中第一种业务流管理装置位于 CAP 侧时, 其结构如图 24所示, 该装置包括: 请求发送单元 241、 响应接收单元 242、 参数提供单元 243和监控单元 244。
请求发送单元 241, 用于发送携带业务流标识 FID和 FID最大緩冲能力 的动态业务管理请求。
响应接收单元 242, 接收针对动态业务管理请求的响应。 响应接收单元 242接收的针对动态业务管理请求的响应为: 指示所述动态业务管理请求正 确接 < 的确认。
参数提供单元 243, 用于将目的端标识、 业务参数和方向信息中的一种 或几种发送给请求发送单元 241, 供其携带在动态业务管理请求中发送, 所 述方向信息指示业务流为上行或下行。
监控单元 244, 用于在请求发送单元 241发送动态业务管理请求后的设 定帧数内监控响应接收单元 242, 如果响应接收单元 242未收到所述响应, 通知请求发送单元 241重新发送动态业务管理请求。 在此基础上, 请求发送 单元 241将动态业务管理请求封装为 MPDU发送,当重新发送动态业务管理 请求超过 MPDU最大重传次数时, 丟弃动态业务管理请求, 并通知业务流删 除装置执行操作。
作为一种可选的实施例, 当本发明中第一种业务流管理装置位于 STA侧 时, 其结构如图 25所示, 该装置包括: 请求发送单元 251、 响应接收单元 252、 确认单元 253、 参数提供单元 254和监控单元 255。
请求发送单元 251 , 用于发送携带业务流标识 FID和 FID最大緩冲能力 的动态业务管理请求。
响应接收单元 252, 接收针对动态业务管理请求的响应。 响应接收单元 252接收的针对动态业务管理请求的响应为: 携带所述 FID的动态业务管理 响应。
确认单元 253 , 用于发送指示所述动态业务管理响应正确接收的确认。 参数提供单元 254, 用于将目的端标识、 业务参数和方向信息中的一种 或几种发送给请求发送单元 251, 供其携带在动态业务管理请求中发送, 其 中所述方向信息指示业务流为上行或下行。 在此基础上, 进一步, 当动态业 务管理请求中携带业务参数时,动态业务管理响应还携带调整后的业务参数。
监控单元 255, 用于在请求发送单元 251发送动态业务管理请求后的设 定帧数内监控响应接收单元 252, 如果响应接收单元 252未收到所述响应, 通知请求发送单元 251结束本次流程。
图 26为本发明中第二种业务流管理装置的结构示意图, 该装置位于接 收端一侧, 该装置包括: 请求接收单元 261和响应发送单元 262。
请求接收单元 261, 用于接收携带 FID和 FID最大緩冲能力的动态业务 管理请求。
响应发送单元 262, 用于发送针对动态业务管理请求的响应。
作为一种可选的实施例, 当业务流管理装置位于 STA侧时, 所述针对动 态业务管理请求的响应为: 指示所述动态业务管理请求正确接收的确认。 在 此基础上, 进一步, 所述动态业务管理请求中还携带目的端标识、 业务参数 和方向信息中的一种或几种, 其中所述方向信息指示要建立的业务流为上行 或下行。
作为一种可选的实施例, 当业务流管理装置位于 CAP侧时, 其结构如图 27所示, 该装置包括: 请求接收单元 271、 响应发送单元 272、 确认接收单 元 273、 监控单元 274和业务参数调整单元 275。
请求接收单元 271, 用于接收携带 FID和 FID最大緩冲能力的动态业务 管理请求。
响应发送单元 272, 用于发送针对动态业务管理请求的响应。 响应发送 单元 272发送的针对动态业务管理请求的响应为: 携带所述 FID和 FID最大 緩冲能力的动态业务管理响应。
确认接收单元 273 , 用于接收指示所述动态业务管理响应正确接收的确 认。
监控单元 274, 用于在响应发送单元 272发送动态业务管理响应后的设 定帧数内监控确认接收单元 273, 如果确认接收单元 273未收到所述确认, 触发响应发送单元 272重新发送动态业务管理响应。 在此基础上, 响应发送 单元 272将动态业务管理响应封装成 MPDU发送, 当所述重新发送超过 MPDU最大重传次数时, 丟弃动态业务管理响应, 并通知业务流删除装置执 行操作。
所述动态业务管理请求中还携带目的端标识、 业务参数和方向信息中的 一种或几种。 业务参数调整单元 275, 用于在动态业务管理请求中携带业务 参数时, 根据动态业务管理请求中携带的业务参数确定预留的资源, 根据所 述预留的资源调整动态业务管理请求中携带的业务参数, 并将调整后的业务 参数发送给响应发送 元 272, 供其携带在动态业务管理响应中发送。
本发明还提供一种业务流删除的方法, 图 28为本发明中业务流删除的 方法流程图, 该流程包括:
步骤 281 : 发送携带 FID和方向信息的动态业务删除请求, 方向信息指 示要删除的业务流为上行业务流或下行业务流。
动态业务删除请求的发起端可以是 STA, 也可以是 CAP, 其中 STA发 送的动态业务删除请求中, 方向信息将指示上行业务流, CAP发送的动态业 务删除请求中, 方向信息就可以指示上行业务流、 也可以指示下行业务流。
步骤 282: 接收 4十对动态业务删除请求的响应。
可以看出, 本发明通过在动态业务删除请求中携带方向信息, 使得 CAP 不仅在业务传输结束时可以删除自身建立的下行业务流, 还可以主动删除 STA对应的上行业务流,从而在长时间无业务或出现异常情况时 STA长期占
用业务流资源。 另外, STA可以在业务传输结束时删除自身建立的上行业务 流。
作为一种可选的实施例, 图 29为本发明实施例中上行业务流删除的方 法流程图, 该流程包括:
步骤 291 : CAP接收 STA发送的携带 FID和方向信息的动态业务删除请 求帧。
本实施例中, 动态业务删除请求由动态业务删除请求帧实现。
图 30为本发明实施例中动态业务删除请求帧的结构示意图, 该动态业 务删除请求帧中包括帧控制字段、 FID字段、 方向字段和 FCS字段。 其中帧 控制字段中与帧类型相关的标识指示该帧为动态业务删除请求帧, FID字段 中指示要删除的业务流的 FID,方向字段指示要删除的业务流为上行业务流, FCS字段为校验字段。 图 30中还示出了各字段占用比特数的举例。
步骤 292: CAP向 STA发送动态业务删除响应帧。
动态业务删除响应帧的结构与动态业务删除请求帧的结构相同、 且各字 段中承载的内容也相同。
步骤 293: CAP接收 STA正确接收动态业务删除响应帧后发送的 ACK。 本步骤中, STA还可以向 CAP发送 GroupAck。
经过上述步骤 291〜293后, CAP和 STA将各自删除已记录的 FID及对 应的相关信息, 并结束在所删除业务流上的数据传输。
作为一种可选的实施例, 图 31为本发明实施例中上行或下行业务流删 除的方法流程图, 该流程包括:
步骤 311 : STA接收 CAP发送的携带 FID和方向信息的动态业务删除请 求帧。
本实施例中, 动态业务删除请求由动态业务删除请求帧实现, 这里的动 态业务删除请求帧的结构与图 30所示的相同, 只是当 CAP删除下行业务流 时, 方向字段指示下行业务流, CAP删除上行业务流时, 方向字段指示上行 业务流。
步骤 312: STA向 CAP发送 ACK。
本步骤中, STA还可以向 CAP发送 GroupAck。
经过上述步骤 311〜312后, CAP和 STA将各自删除已记录的 FID及对 应的相关信息, 并结束在所删除业务流上的数据传输。
本发明还提供两种业务流删除装置。
图 32为本发明中第一种业务流删除装置的结构示意图, 该装置中包括: 请求发送单元 321和响应接收单元 322。
请求发送单元 321,用于发送携带 FID和方向信息的动态业务删除请求, 方向信息指示要删除的业务流为上行或下行。
响应接收单元 322, 用于接收 4十对动态业务删除请求的响应。
作为一种可选的实施例, 当本发明第一种业务流删除装置位于 CAP侧 时, 其结构如图 33所示, 该装置包括: 请求发送单元 331、 响应接收单元 332和监控单元 333。
请求发送单元 331,用于发送携带 FID和方向信息的动态业务删除请求, 方向信息指示要删除的业务流为上行或下行。
响应接收单元 332, 用于接收 4十对动态业务删除请求的响应。 响应接收 单元 332接收的针对动态业务删除请求的响应为: 指示所述动态业务删除请 求正确接 >] 的确认。
监控单元 333, 用于在请求发送单元 331发送动态业务删除请求后的设 定帧数内监控响应接收单元 332, 如果响应接收单元 332未收到所述响应, 触发请求发送单元 331重新发送动态业务删除请求。 在此基础上, 请求发送 单元 331将动态业务删除请求封装为 MPDU发送,当重新发送动态业务删除 请求超过 MPDU最大重传次数时, 丟弃动态业务删除请求。
作为一种可选的实施例, 当本发明第一种业务流删除装置位于 CAP侧 时,可以接收同样位于 CAP侧的本发明的两种业务流建立装置或本发明的两 种业务流爹改装置的通知, 开始执行操作。
作为一种可选的实施例, 当本发明第一种业务流删除装置位于 CAP侧 时, 可以接收同样位于 CAP侧的本发明的两种业务流管理装置的通知, 开始 执行操作。
作为一种可选的实施例, 当本发明第一种业务流删除装置位于 STA侧 时, 其结构与图 33所示相同, 只是响应接收单元 332接收的针对动态业务 删除请求的响应为携带所述 FID和方向信息的动态业务删除响应, 并且监控 单元 333在响应接收单元 332未收到所述响应时, 通知请求发送单元 331结 束本次流程。
图 34为本发明中第二种业务流删除装置的结构示意图, 该装置中包括: 请求接收单元 341和响应发送单元 342。
请求接收单元 341,用于接收携带 FID和方向信息的动态业务删除请求, 方向信息指示要删除的业务流为上行或下行。
响应发送单元 342, 用于发送针对动态业务删除请求的响应。
作为一种可选的实施例, 当业务流删除装置位于 CAP侧时, 其结构如图 35所示, 该装置中包括: 请求接收单元 351、 响应发送单元 352、 确认接收 单元 353和监控单元 354。
请求接收单元 351,用于接收携带 FID和方向信息的动态业务删除请求, 方向信息指示要删除的业务流为上行或下行。
响应发送单元 352, 用于发送针对动态业务删除请求的响应。 针对动态 业务删除请求的响应为: 携带所述 FID和方向信息的动态业务删除响应。
确认接收单元 353, 用于接收指示所述动态业务删除响应正确接收的确 认。
监控单元 354, 用于在响应发送单元 352发送动态业务删除响应后的设 定帧数内监控确认接收单元 353, 如果确认接收单元 353未收到所述确认, 触发响应发送单元 352重新发送所述动态业务删除响应。 在此基础上, 响应 发送单元 352将动态业务删除响应封装成 MPDU发送,当所述重新发送超过 MPDU最大重传次数时, 丟弃所述动态业务删除响应。
可选的, 当业务流删除装置位于 STA侧时, 所述针对动态业务删除请求 的响应为: 指示所述动态业务删除请求正确接收的确认。
下面介绍本发明在业务流管理中的异常处理方式。
异常处理方式中可能使用到如下***设置参数:
1、 业务流响应帧的最大等待间隔: 指示 STA发送业务流管理请求后可 以容忍的最大等待帧数, 作为一种举例, 默认值可以设置为 4;
2、 下行业务流请求帧确认的最大等待帧间隔: 指示 CAP发送业务流管 理请求后可以容忍的最大等待帧数, 作为一种举例, 默认值可以设置为 4;
3、 业务流响应帧确认的最大等待帧间隔: 指示 CAP发送业务流管理响 应帧后可以容忍的最大等待帧数, 作为一种举例, 默认值可以设置为 4;
4、 MPDU最大重传次数:指示针对某一个 MPDU尝试重传的最大次数, 作为一种举例, 默认值可以设置为 5;
5、 CAP对 STA允许的连续发送失败最大次数:指示针对某一 STA, CAP 可以容忍的连续发送失败次数, 作为一种举例, 默认值可以设置为 20。
本发明业务流管理中的异常处理方式可以具体包括:
1、 针对上行业务流管理, 在 STA—侧, STA在发送请求帧后等待 "业 务流响应帧的最大等待间隔", 如果未收到 CAP发送的响应帧, 则认为本次 业务流管理过程失败, STA将发起新的业务流管理流程。 在 CAP—侧, CAP 在发送响应帧后等待 "业务流响应帧确认的最大等待帧间隔", 如果未收到 STA发送的 ACK或 GroupAck, 则重传响应帧、 直至重传次数超过 MPDU 最大重传次数, 此时 CAP将发起业务流删除流程。
2、 针对下行业务流管理, CAP在发送请求帧后等待 "下行业务流请求 帧确认的最大等待帧间隔", 如果未收到 STA发送的 ACK或 GroupAck, 则 认为本次业务流管理过程失败, 并重传该请求帧、 直至重传次数超过 MPDU 最大重传次数, 此时 CAP将发起业务流删除流程。
3、 在上述异常处理过程中, CAP向 STA发送 MPDU或组 MAC协议数 据单元(G-MPDU )后, 如果没有收到任何一个 MPDU正确的确认, 则认为 本次发送失败并启动发送失败次数计数器。 如果发给该 STA的后续 MPDU 或 G-MPDU仍然失败, 则将发送失败次数累加。 如果收到任何一个 MPDU 的正确的确认, 则将累加计数器清零。 如果该累加值超过 "CAP对 STA允 许的连续发送失败最大次数", CAP则认为该 STA已经出现异常, 将其从活 动 STA列 中删除。
上述 CAP向 STA发送 MPDU, 可以是 CAP将针对 STA的某一个业务 流的响应帧或请求帧封装为 MPDU发送给该 STA。
上述 CAP向 STA发送 G-MPDU, 可以是 CAP将针对 STA的业务流 1 的响应帧或请求帧, 与 4十对该 STA业务流 2的数据帧组合在一起发送给该 STA。
本发明中的异常处理的方式中, 使用帧号进行定时, 相比于使用定时器 进行定时更加 4青确。
上述 CAP向 STA发送 MPDU, 可以是 CAP将针对 STA的某一个业务 流的响应帧或请求帧封装为 MPDU发送给该 STA。
上述 CAP向 STA发送 G-MPDU, 可以是 CAP将针对 STA的业务流 1 的响应帧或请求帧, 与 4十对该 STA业务流 2的数据帧组合在一起发送给该 STA。
本发明中的异常处理的方式中, 使用帧号进行定时, 相比于使用定时器 进行定时更加 4青确。
本发明还提供一种用于业务流建立的方法, 如图 36所示, 该方法包括: 步骤 361 : 生成携带 FID及目的端标识的动态业务建立请求;
步骤 362: 发送所述动态业务建立请求。
本发明还提供另一种用于业务流建立的方法, 如图 37所示, 该方法包 括 ··
步骤 371 : 生成携带 FID的动态业务建立响应;
步骤 372: 发送所述动态业务建立响应。
作为一种可选的实施例, 上述动态业务建立请求可以釆用图 7所示的动 态业务建立请求帧实现, 上述动态业务建立响应可以釆用图 8所示的动态业 务建立响应帧实现。
对应图 36和 37所示的用于业务流建立的方法, 本发明还提供两种用于 业务流建立的装置, 包括生成单元和发送单元, 其中生成单元用于生成对应 方法的生成步骤中所生成的信息, 发送单元用于发送生成单元生成的信息。
本发明还提供一种用于业务流爹改的方法, 如图 38所示, 该方法包括: 步骤 381 : 生成携带 FID、 目的端标识及新的业务参数的动态业务爹改 请求;
步骤 382: 发送所述动态业务建立请求。
本发明还提供另一种用于业务流修改的方法, 如图 39所示, 该方法包 括 ··
步骤 391 : 生成携带 FID的动态业务爹改响应;
步骤 392: 发送所述动态业务爹改响应。
作为一种可选的实施例, 上述动态业务修_改请求可以釆用与图 7所示结 构相同的动态业务修 _改请求帧实现, 上述动态业务爹改响应可以釆用图 8所 示的动态业务爹改响应帧实现。
对应图 38和图 39所示的用于业务流修改的方法, 本发明还提供两种用 于业务流爹改的装置, 包括生成单元和发送单元, 其中生成单元用于生成对 应方法的生成步骤中所生成的信息,发送 ^元用于发送生成单元生成的信息。
本发明还提供一种用于业务流建立的方法, 如图 40所示, 该方法包括: 步骤 401 : 生成携带 FID和 FID最大緩冲能力的动态业务建立请求; 步骤 402: 发送所述动态业务建立请求。
本发明还提供另一种用于业务流建立的方法, 如图 41所示, 该方法包 括 ··
步骤 411 : 生成携带 FID和 FID最大緩冲能力的动态业务建立响应; 步骤 412: 发送所述动态业务建立响应。
作为一种可选的实施例, 上述动态业务建立请求可以釆用与图 7所示的 动态业务建立请求帧实现, 上述动态业务建立响应可以釆用图 8所示的动态 业务建立响应帧实现。
对应图 40和 41所示的用于业务流建立的方法, 本发明还提供两种用于 业务流建立的装置, 包括生成单元和发送单元, 其中生成单元用于生成对应 方法的生成步骤中所生成的信息, 发送单元用于发送生成单元生成的信息。
本发明还提供一种用于业务流爹改的方法, 如图 42所述, 该方法包括: 步骤 421 : 生成携带 FID和 FID最大緩冲能力的动态业务修 _改请求; 步骤 422: 发送所述动态业务修 _改请求。
本发明还提供另一种用于业务流爹改的方法, 如图 43所示, 该方法包 括 ··
步骤 431 : 生成携带 FID和 FID最大緩冲能力的动态业务爹改响应; 步骤 432: 发送所述动态业务爹改响应。
作为一种可选的实施例, 上述动态业务修_改请求可以釆用与图 7所示结 构相同的动态业务修 _改请求帧实现, 上述动态业务爹改响应可以釆用图 8所 示的动态业务爹改响应帧实现。
对应图 42和图 43所示的用于业务流修改的方法, 本发明还提供两种用 于业务流爹改的装置, 包括生成单元和发送单元, 其中生成单元用于生成对 应方法的生成步骤中所生成的信息,发送 ^元用于发送生成单元生成的信息。
本发明还提供一种用于业务流删除的方法, 如图 44所示, 该方法包括: 步骤 441 : 生成携带 FID和方向信息的动态业务流删除请求;
步骤 442: 发送所述动态业务流删除请求。
本发明还提供另一种用于业务流删除的方法, 如图 45所示, 该方法包 括 ··
步骤 451 : 生成携带 FID和方向信息的动态业务流删除响应;
步骤 452: 发送所述动态业务流删除响应。
作为一种可选的实施例, 上述动态业务删除请求和动态业务删除响应可 以釆用与图 30所示结构相同的帧实现。
对应图 44和图 45所示的用于业务流删除的方法, 本发明还提供两种用 于业务流删除的装置, 包括生成单元和发送单元, 其中生成单元用于生成对 应方法的生成步骤中所生成的信息,发送 ^元用于发送生成单元生成的信息。
应该明白,公开的过程中的步骤的特定顺序或层次是示例性方法的实例。 基于设计偏好, 应该理解, 过程中的步骤的特定顺序或层次可以在不脱离本 公开的保护范围的情况下得到重新安排。 所附的方法权利要求以示例性的顺 序给出了各种步骤的要素, 并且不是要限于所述的特定顺序或层次。
在上述的详细描述中, 各种特征一起组合在单个的实施方案中, 以筒化 本公开。 不应该将这种公开方法解释为反映了这样的意图, 即, 所要求保护 的主题的实施方案需要比清楚地在每个权利要求中所陈述的特征更多的特 征。 相反, 如所附的权利要求书所反映的那样, 本发明处于比所公开的单个 实施方案的全部特征少的状态。 因此, 所附的权利要求书特此清楚地被并入 详细描述中, 其中每项权利要求独自作为本发明单独的优选实施方案。
上文的描述包括一个或多个实施例的举例。 当然, 为了描述上述实施例 而描述部件或方法的所有可能的结合是不可能的, 但是本领域普通技术人员 应该认识到, 各个实施例可以做进一步的组合和排列。 因此, 本文中描述的 实施例旨在涵盖落入所附权利要求书的保护范围内的所有这样的改变、 修改 和变型。 此外, 就说明书或权利要求书中使用的术语 "包含", 该词的涵盖方 式类似于术语 "包括", 就如同 "包括," 在权利要求中用作 #†接词所解释的 那样。 此外, 使用在权利要求书的说明书中的任何一个术语 "或者" 是要表 示 "非排它性的或者"。
Claims
1.一种业务流管理方法, 其特征在于, 该方法包括:
发送携带业务流标识 FID和 FID最大緩冲能力的动态业务管理请求; 接收针对动态业务管理请求的响应。
2. 如权利要求 1所述的方法, 其特征在于, 所述 4十对动态业务管理请求 的响应为: 指示所述动态业务管理请求正确接收的确认。
3. 如权利要求 2所述的方法, 其特征在于, 还包括: 在所述动态业务管 理请求中携带目的端标识、 业务参数和方向信息中的一种或几种, 其中所述 方向信息指示业务流为上行或下行。
4. 如权利要求 1所述的方法, 其特征在于, 所述 4十对动态业务管理请求 的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
5. 如权利要求 4所述的方法, 其特征在于, 还包括: 发送指示所述动态 业务管理响应正确接收的确认。
6. 如权利要求 4所述的方法, 其特征在于, 还包括: 在所述动态业务管 理请求中携带目的端标识、 业务参数和方向信息中的一种或几种, 其中所述 方向信息指示业务流为上行或下行。
7. 如权利要求 6所述的方法, 其特征在于, 当所述动态业务管理请求中 携带业务参数时, 所述动态业务管理响应还携带调整后的业务参数。
8. 如权利要求 1所述的方法, 其特征在于, 还包括: 在发送所述动态业 务管理请求后等待设定帧数, 如果未收到所述响应, 重新发送所述动态业务 管理请求, 或者, 结束本次流程。
9.一种业务流管理方法, 其特征在于, 该方法包括:
接收携带 FID和 FID最大緩冲能力的动态业务管理请求;
发送针对动态业务管理请求的响应。
10. 如权利要求 9所述的方法, 其特征在于, 所述针对动态业务管理请 求的响应为: 指示所述动态业务管理请求正确接收的确认。
11. 如权利要求 10所述的方法, 其特征在于, 所述动态业务管理请求中 还携带目的端标识、 业务参数和方向信息中的一种或几种, 其中所述方向信 息指示业务流为上行或下行。
12. 如权利要求 9所述的方法, 其特征在于, 所述针对动态业务管理请 求的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
13. 如权利要求 12所述的方法, 其特征在于, 还包括: 接收指示所述动 态业务管理响应正确接 >\ 的确认。
14. 如权利要求 13所述的方法, 其特征在于, 还包括: 在发送所述动态 业务管理响应后等待设定帧数内, 如果未收到所述确认, 重新发送所述动态 业务管理响应。
15. 如权利要求 12所述的方法, 其特征在于, 所述动态业务管理请求中 还携带目的端标识、 业务参数和方向信息中的一种或几种。
16. 如权利要求 15所述的方法, 其特征在于, 当所述动态业务管理请求 中携带业务参数时, 该方法还包括: 根据动态业务管理请求中携带的业务参 数确定预留的资源, 根据所述预留的资源调整所述动态业务管理请求中携带 的业务参数, 并在所述动态业务管理响应中携带调整后的业务参数。
17.一种业务流管理装置, 其特征在于, 该装置包括: 请求发送单元, 用于发送携带业务流标识 FID和 FID最大緩冲能力的动 态业务管理请求;
响应接收单元, 接收针对动态业务管理请求的响应。
18. 如权利要求 17所述的装置, 其特征在于, 所述针对动态业务管理请 求的响应为: 指示所述动态业务管理请求正确接收的确认。
19. 如权利要求 18所述的装置, 其特征在于, 该装置还包括: 参数提供 单元, 用于将目的端标识、 业务参数和方向信息中的一种或几种发送给所述 请求发送单元, 供其携带在动态业务管理请求中发送;
所述方向信息指示业务流为上行或下行。
20. 如权利要求 18所述的装置, 其特征在于,该装置还包括:监控单元, 用于在所述请求发送单元发送所述动态业务管理请求后的设定帧数内监控所 述响应接收单元, 如果所述响应接收单元未收到所述响应, 通知所述请求发 送单元重新发送所述动态业务管理请求。
21. 如权利要求 20所述的装置, 其特征在于, 所述请求发送单元将所述 动态业务管理请求封装为媒体接入控制协议数据单元 MPDU发送,当重新发 送所述动态业务管理请求超过 MPDU最大重传次数时,丟弃动态业务管理请 求, 并通知业务流删除装置执行操作。
22. 如权利要求 17所述的装置, 其特征在于, 所述针对动态业务管理请 求的响应为: 携带所述 FID的动态业务管理响应。
23. 如权利要求 22所述的装置, 其特征在于,该装置还包括: 确认单元, 用于发送指示所述动态业务管理响应正确接收的确认。
24. 如权利要求 22所述的装置, 其特征在于, 该装置还包括: 参数提供 单元, 用于将目的端标识、 业务参数和方向信息中的一种或几种发送给所述 请求发送单元, 供其携带在动态业务管理请求中发送, 其中所述方向信息指 示业务流为上行或下行。
25. 如权利要求 24所述的装置, 其特征在于, 当动态业务管理请求中携 带业务参数时, 动态业务管理响应还携带调整后的业务参数。
26. 如权利要求 22所述的装置, 其特征在于,该装置还包括:监控单元, 用于在所述请求发送单元发送所述动态业务管理请求后的设定帧数内监控所 述响应接收单元, 如果所述响应接收单元未收到所述响应, 通知所述请求发 送单元结束本次流程。
27.一种业务流管理装置, 其特征在于, 该装置包括:
请求接收单元, 用于接收携带 FID和 FID最大緩冲能力的动态业务管理 请求;
响应发送单元, 用于发送针对动态业务管理请求的响应。
28. 如权利要求 27所述的装置, 其特征在于, 所述针对动态业务管理请 求的响应为: 指示所述动态业务管理请求正确接收的确认。
29. 如权利要求 28所述的装置, 其特征在于, 所述动态业务管理请求中 还携带目的端标识、 业务参数和方向信息中的一种或几种, 其中所述方向信 息指示要管理的业务流为上行或下行。
30. 如权利要求 27所述的装置, 其特征在于, 所述针对动态业务管理请 求的响应为: 携带所述 FID和 FID最大緩冲能力的动态业务管理响应。
31. 如权利要求 30所述的装置, 其特征在于, 该装置还包括: 确认接收 单元, 用于接收指示所述动态业务管理响应正确接收的确认。
32. 如权利要求 31所述的装置, 其特征在于,该装置还包括:监控单元, 用于在所述响应发送单元发送动态业务管理响应后的设定帧数内监控所述确 认接收单元, 如果所述确认接收单元未收到所述确认, 触发所述响应发送单 元重新发送动态业务管理响应。
33. 如权利要求 32所述的装置, 其特征在于, 所述响应发送单元将所述 动态业务管理响应封装成 MPDU发送, 当所述重新发送超过 MPDU重传次 数时, 丟弃动态业务管理响应, 并通知业务流删除装置执行操作。
34. 如权利要求 30所述的装置, 其特征在于, 所述动态业务管理请求中 还携带目的端标识、 业务参数和方向信息中的一种或几种。
35. 如权利要求 34所述的装置, 其特征在于, 该装置还包括业务参数调 整单元, 用于在动态业务管理请求中携带业务参数时, 根据动态业务管理请 求中携带的业务参数确定预留的资源, 根据所述预留的资源调整所述动态业 务管理请求中携带的业务参数, 并将调整后的业务参数发送给所述响应发送 单元, 供其携带在动态业务管理响应中发送。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201280012693.5A CN103460787B (zh) | 2011-03-31 | 2012-03-06 | 业务流管理方法及装置 |
Applications Claiming Priority (16)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110081288 | 2011-03-31 | ||
CN201110081288.6 | 2011-03-31 | ||
CN201110188606.9 | 2011-07-06 | ||
CN201110188606 | 2011-07-06 | ||
CN201210027852 | 2012-02-08 | ||
CN201210027916 | 2012-02-08 | ||
CN201210027851 | 2012-02-08 | ||
CN201210027916.7 | 2012-02-08 | ||
CN201210027851.6 | 2012-02-08 | ||
CN201210027852.0 | 2012-02-08 | ||
CN201210038079 | 2012-02-17 | ||
CN201210036754.3 | 2012-02-17 | ||
CN201210038757 | 2012-02-17 | ||
CN201210038757.0 | 2012-02-17 | ||
CN201210036754 | 2012-02-17 | ||
CN201210038079.8 | 2012-02-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012130020A1 true WO2012130020A1 (zh) | 2012-10-04 |
Family
ID=46929420
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/071959 WO2012130021A1 (zh) | 2011-03-31 | 2012-03-06 | 业务流删除方法及装置 |
PCT/CN2012/071958 WO2012130020A1 (zh) | 2011-03-31 | 2012-03-06 | 业务流管理方法及装置 |
PCT/CN2012/071955 WO2012130019A1 (zh) | 2011-03-31 | 2012-03-06 | 业务流建立方法和装置、及业务流修改方法和装置 |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/071959 WO2012130021A1 (zh) | 2011-03-31 | 2012-03-06 | 业务流删除方法及装置 |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/071955 WO2012130019A1 (zh) | 2011-03-31 | 2012-03-06 | 业务流建立方法和装置、及业务流修改方法和装置 |
Country Status (7)
Country | Link |
---|---|
US (1) | US9319320B2 (zh) |
EP (1) | EP2693828B1 (zh) |
JP (1) | JP2014514818A (zh) |
KR (1) | KR101971034B1 (zh) |
CN (6) | CN102946622A (zh) |
ES (1) | ES2633891T3 (zh) |
WO (3) | WO2012130021A1 (zh) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102300158B (zh) * | 2010-06-28 | 2015-03-11 | ***通信集团公司 | 时分双工***中获知载波信息及载波信息指示方法和设备 |
US8861538B2 (en) * | 2012-09-06 | 2014-10-14 | Unisys Corporation | Throttling for fast data packet transfer operations |
US9516356B2 (en) | 2013-12-06 | 2016-12-06 | Cable Television Laboratories, Inc. | Parallel scheduling of multilayered media |
US10142885B2 (en) | 2014-02-09 | 2018-11-27 | Lg Electronics Inc. | Method for operating terminal in wireless communication system and terminal using same |
US9832678B1 (en) * | 2015-01-13 | 2017-11-28 | Syniverse Technologies, Llc | Traffic hub system to provide roaming service in a wireless environment |
CN106230723B (zh) * | 2016-08-08 | 2019-08-13 | 北京邮电大学 | 一种报文转发缓存方法及装置 |
CN106685604A (zh) * | 2016-11-28 | 2017-05-17 | 北京新岸线移动通信技术有限公司 | 数据传输控制方法、***及装置 |
CN108574969B (zh) | 2017-03-08 | 2021-04-09 | 华为技术有限公司 | 多接入场景中的连接处理方法和装置 |
CN110312283B (zh) * | 2018-03-20 | 2021-05-04 | 华为技术有限公司 | 一种信息处理方法及装置 |
CN112118597B (zh) * | 2019-06-19 | 2023-11-24 | 上海新岸线电子技术有限公司 | 一种多流业务的传输方法及*** |
CN111211935B (zh) * | 2019-12-26 | 2021-06-25 | 国家计算机网络与信息安全管理中心 | 一种高效应用级并发探测实现方法 |
CN116192305B (zh) * | 2020-08-14 | 2024-05-10 | 华为技术有限公司 | 一种信道接入方法、通信装置、芯片、存储介质和程序产品 |
WO2022146507A1 (en) * | 2020-12-30 | 2022-07-07 | Arris Enterprises Llc | System to dynamically detect and enhance classifiers for low latency traffic |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1514618A (zh) * | 2002-12-16 | 2004-07-21 | ���Ͽع�����˾ | 辅助数字用户线路接入复用器上的业务量管理功能 |
CN101404610A (zh) * | 2008-10-29 | 2009-04-08 | 中兴通讯股份有限公司 | 业务流修改的实现方法及*** |
CN101494575A (zh) * | 2008-01-22 | 2009-07-29 | 华为技术有限公司 | 个域网的管理方法及代理设备 |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3490286B2 (ja) * | 1998-03-13 | 2004-01-26 | 株式会社東芝 | ルータ装置及びフレーム転送方法 |
FI105969B (fi) * | 1998-08-10 | 2000-10-31 | Nokia Networks Oy | Palvelunlaadun hallinta matkaviestinjärjestelmässä |
US7406098B2 (en) * | 1999-01-13 | 2008-07-29 | Qualcomm Incorporated | Resource allocation in a communication system supporting application flows having quality of service requirements |
US6574195B2 (en) * | 2000-04-19 | 2003-06-03 | Caspian Networks, Inc. | Micro-flow management |
AU2003247862A1 (en) * | 2002-07-15 | 2004-02-02 | Flarion Technologies, Inc. | Methods and apparatus for improving resiliency of communication networks |
US7483374B2 (en) * | 2003-08-05 | 2009-01-27 | Scalent Systems, Inc. | Method and apparatus for achieving dynamic capacity and high availability in multi-stage data networks using adaptive flow-based routing |
KR100713487B1 (ko) * | 2004-03-05 | 2007-05-02 | 삼성전자주식회사 | 이동 광대역 무선 접속 시스템에서 다수의 액티브기지국들을 가진 이동단말의 서비스 플로우 관리 방법 |
US20060160533A1 (en) * | 2005-01-19 | 2006-07-20 | Joey Chou | Method and system of network management and service provisioning for mobile broadband wireless networks |
US20070078955A1 (en) * | 2005-09-15 | 2007-04-05 | Xelor Software Pty Ltd | Service quality management in packet networks |
CN100461790C (zh) * | 2005-11-03 | 2009-02-11 | 华为技术有限公司 | 一种在微波接入全球互通网络中sfid的分配方法 |
KR100790152B1 (ko) * | 2005-11-24 | 2008-01-02 | 삼성전자주식회사 | 통신 시스템에서 데이터 송수신 방법 및 시스템 |
US20090059840A1 (en) * | 2005-12-08 | 2009-03-05 | Samsung Electronics Co., Ltd. | Wireless communication system and method for managing service flow identifier in the same |
CN100544485C (zh) * | 2005-12-28 | 2009-09-23 | 华为技术有限公司 | 一种无线通信***切换时的信息处理方法 |
CN101043504B (zh) * | 2006-03-22 | 2011-08-10 | 华为技术有限公司 | 网络侧服务流的创建、删除和更改的方法 |
CN101043401A (zh) * | 2006-03-23 | 2007-09-26 | 华为技术有限公司 | 一种网络服务流标识的分配、更新方法 |
CN101087243B (zh) * | 2006-06-05 | 2011-07-06 | 华为技术有限公司 | 在弹性分组环中限制多播范围的方法及装置 |
CN101512978B (zh) * | 2006-07-04 | 2013-02-13 | 夏普株式会社 | 通信装置、设备、通信装置控制方法 |
CN101155053B (zh) * | 2006-09-25 | 2011-03-30 | 华为技术有限公司 | 一种组播/广播业务实现方法和*** |
CN101515858B (zh) * | 2008-02-21 | 2012-12-12 | 华为技术有限公司 | 无线网络中终端加入多播广播业务的方法、***和终端 |
US8355357B2 (en) * | 2008-03-10 | 2013-01-15 | Samsung Electronics Co., Ltd. | Apparatus and method for admission control for service flow in broadband wireless access communication system using multi-hop relay scheme |
WO2009134066A1 (en) * | 2008-05-01 | 2009-11-05 | Lg Electronics Inc. | Direct link setup method in tunneled direct link setup wireless network and station supporting the method |
CN101884233B (zh) * | 2008-05-15 | 2013-06-12 | 松下电器产业株式会社 | 无线中继装置及无线中继方法 |
JP5169635B2 (ja) | 2008-08-29 | 2013-03-27 | 富士通株式会社 | 基地局装置、サービスフロー確立プログラム、およびサービスフロー確立方法 |
WO2010028106A2 (en) * | 2008-09-03 | 2010-03-11 | Nokia Siemens Networks Oy | Resource allocation during silence period for a wireless network |
US8934407B2 (en) * | 2008-09-05 | 2015-01-13 | Zte (Usa) Inc. | MAC layer packet data units for wireless communications |
CN101686191A (zh) | 2008-09-24 | 2010-03-31 | 华为技术有限公司 | 访问分组数据网业务的方法及***、网关和终端 |
US8284789B2 (en) * | 2009-04-29 | 2012-10-09 | Tellabs Operations, Inc. | Methods and apparatus for providing dynamic data flow queues |
KR101653310B1 (ko) * | 2009-09-02 | 2016-09-01 | 엘지전자 주식회사 | Mac 헤더 타입 정보를 이용한 mac pdu 송수신 방법 및 장치 |
KR101165642B1 (ko) * | 2009-09-02 | 2012-07-16 | 엘지전자 주식회사 | 압축 mac 헤더를 이용한 mac pdu 송수신 방법 및 장치 |
JP5758925B2 (ja) * | 2010-03-12 | 2015-08-05 | エルジー エレクトロニクス インコーポレイティド | 広帯域無線接続システムにおける保安連係を考慮した領域変更方法及びそのための装置 |
CN101808331B (zh) * | 2010-04-02 | 2012-12-19 | 华为技术有限公司 | 动态业务流的处理方法及基站 |
EP2381734B1 (en) * | 2010-04-20 | 2012-06-20 | Research In Motion Limited | Handling QOS flows when moving between systems |
-
2012
- 2012-03-06 CN CN201210057109XA patent/CN102946622A/zh active Pending
- 2012-03-06 WO PCT/CN2012/071959 patent/WO2012130021A1/zh active Application Filing
- 2012-03-06 CN CN2012100566091A patent/CN102917412A/zh active Pending
- 2012-03-06 WO PCT/CN2012/071958 patent/WO2012130020A1/zh active Application Filing
- 2012-03-06 WO PCT/CN2012/071955 patent/WO2012130019A1/zh active Application Filing
- 2012-03-06 CN CN2012100571009A patent/CN102858029A/zh active Pending
- 2012-03-06 JP JP2014501410A patent/JP2014514818A/ja active Pending
- 2012-03-06 EP EP12765849.0A patent/EP2693828B1/en active Active
- 2012-03-06 US US14/008,306 patent/US9319320B2/en active Active
- 2012-03-06 CN CN201280012693.5A patent/CN103460787B/zh active Active
- 2012-03-06 KR KR1020137029008A patent/KR101971034B1/ko active IP Right Grant
- 2012-03-06 CN CN201280012561.2A patent/CN103597902B/zh active Active
- 2012-03-06 ES ES12765849.0T patent/ES2633891T3/es active Active
- 2012-03-06 CN CN201280012683.1A patent/CN103688492B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1514618A (zh) * | 2002-12-16 | 2004-07-21 | ���Ͽع�����˾ | 辅助数字用户线路接入复用器上的业务量管理功能 |
CN101494575A (zh) * | 2008-01-22 | 2009-07-29 | 华为技术有限公司 | 个域网的管理方法及代理设备 |
CN101404610A (zh) * | 2008-10-29 | 2009-04-08 | 中兴通讯股份有限公司 | 业务流修改的实现方法及*** |
Also Published As
Publication number | Publication date |
---|---|
CN103460787B (zh) | 2017-12-29 |
EP2693828B1 (en) | 2017-05-10 |
CN103460787A (zh) | 2013-12-18 |
CN102917412A (zh) | 2013-02-06 |
CN103688492A (zh) | 2014-03-26 |
CN103597902A (zh) | 2014-02-19 |
US20140086045A1 (en) | 2014-03-27 |
KR101971034B1 (ko) | 2019-08-13 |
EP2693828A4 (en) | 2014-10-15 |
CN102858029A (zh) | 2013-01-02 |
EP2693828A1 (en) | 2014-02-05 |
US9319320B2 (en) | 2016-04-19 |
WO2012130021A1 (zh) | 2012-10-04 |
CN102946622A (zh) | 2013-02-27 |
WO2012130019A1 (zh) | 2012-10-04 |
CN103688492B (zh) | 2017-05-24 |
ES2633891T3 (es) | 2017-09-25 |
KR20140007935A (ko) | 2014-01-20 |
JP2014514818A (ja) | 2014-06-19 |
CN103597902B (zh) | 2017-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012130020A1 (zh) | 业务流管理方法及装置 | |
US10616913B2 (en) | Method for supporting multiple scheduling requests in next-generation mobile communication system | |
JP5986244B2 (ja) | チャネルアグリゲーションおよび媒体アクセス制御再送信を実行するための方法および装置 | |
KR101268200B1 (ko) | 이동통신 시스템에서의 무선자원 할당방법 | |
KR100966566B1 (ko) | 효율적인 공용 e-dch 관리를 위한 신호 전송 기법 | |
TWI435573B (zh) | 在無線通訊系統中用於傳輸語音封包之方法 | |
CA2692649C (en) | Method for sending rlc pdu and allocating radio resource in mobile communications system and rlc entity of mobile communications | |
WO2007019807A1 (en) | Method for implement hsdpa for td-scdma | |
JP2013515420A (ja) | リレーにおけるサービス品質の制御 | |
US8700965B2 (en) | Apparatus and method for determining number of retransmissions in a wireless system | |
KR20070080557A (ko) | 이동통신시스템의 향상된 rlc/mac 엔티티 동작 방법및 그 시스템 | |
KR101509766B1 (ko) | 이동통신시스템에서의 rlc pdu 전송 방법, 자원할당 방법 및 rlc 엔티티 | |
WO2007056953A1 (en) | A channel for multicarrier high speed downlink packet access and a method for allocating the carrier resource | |
WO2014110875A1 (zh) | 数据传输方法、基站和用户设备 | |
WO2012130094A1 (zh) | 一种用于帧确认的方法和装置 | |
WO2013155709A1 (zh) | 数据分流配置方法、基站***和用户终端 | |
WO2015113287A1 (zh) | 一种数据传输方法、设备和*** | |
WO2012119564A1 (zh) | 一种用户面配置参数的处理方法及装置 | |
CN105472658A (zh) | 业务流删除方法和装置 | |
JP2014216873A (ja) | パケット解析機能を有する基地局および無線通信システム | |
WO2012051962A1 (zh) | 终端上报调度信息的方法及终端 | |
KR101624937B1 (ko) | 무선 통신 시스템에서 단말의 버퍼 상태 보고 정보 생성 방법 및 이를 위한 장치 | |
US20240121658A1 (en) | Data transmission method and apparatus, device, and storage medium | |
WO2012136067A1 (zh) | 服务质量的优化方法及***、网络侧网元 | |
WO2012130092A1 (zh) | 一种用于帧确认的方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12765882 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12765882 Country of ref document: EP Kind code of ref document: A1 |