WO2018095172A1 - 网络策略的获取方法、设备及应用驱动网络 - Google Patents

网络策略的获取方法、设备及应用驱动网络 Download PDF

Info

Publication number
WO2018095172A1
WO2018095172A1 PCT/CN2017/107155 CN2017107155W WO2018095172A1 WO 2018095172 A1 WO2018095172 A1 WO 2018095172A1 CN 2017107155 W CN2017107155 W CN 2017107155W WO 2018095172 A1 WO2018095172 A1 WO 2018095172A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
requirement
network
qoe
network policy
Prior art date
Application number
PCT/CN2017/107155
Other languages
English (en)
French (fr)
Inventor
刘鹏
张军平
唐飞龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018095172A1 publication Critical patent/WO2018095172A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a device, and an application driver network for acquiring a network policy.
  • the application drive network (English: Application Driven Network; ADN) is a network that can adjust network parameters according to different service types and requirements. This network can improve the quality of user experience (English: Quality of Experience; QoE for short).
  • the current application driver network may include an access point (English: Access Point; abbreviation: AP) and a station (English: Station; abbreviation: STA) point, and the interaction between the AP and the site is based on the 802.11e protocol.
  • 802.11e protocol all services are divided into four types of services (background flow, video, voice, and best-effort data), and four priorities are set accordingly. That is, different service types correspond to different priorities. level.
  • An AP can require each site it manages to send a transport specification request for each type of service access. This request is used to indicate the amount of data accessed by each type of service for the site and the latency threshold that can be tolerated.
  • the AP determines the corresponding priority according to the service type corresponding to each application, and the high priority service obtains more channel competition opportunities.
  • the implementation of the current network policy is based on a predefined type of service, and the service granularity is relatively coarse, which cannot effectively improve the user's QoE.
  • the embodiment of the present application provides a method, a device, and an application driving network for acquiring a network policy.
  • the technical solution is as follows:
  • the embodiment of the present application provides a network environment of an application-driven network involved in a method for acquiring a network policy, where the application-driven network is a network that can adjust network parameters according to different service types and requirements, and the application-driven network includes at least one An AP and at least one site (also called a site), each AP serving at least one site.
  • the site can send an application portrait carrying the QoE requirement to the AP serving the site when the application is started, and the AP determines the corresponding requirement format to parse the QoE requirement, thereby obtaining a network policy for the application.
  • the network policy is a policy based on the service or data transmission in the network, and may include priority scheduling, channel allocation, mobility management, network selection, and the like.
  • the embodiment of the present application provides a decentralized application-driven network involved in a method for acquiring a network policy.
  • the required format and network policy of the AP storage need to be pre-configured, and may be periodically updated by a manual or other proprietary device, but the update efficiency is
  • the application environment of the application network is a centralized network.
  • the application environment is a centralized network.
  • Application-driven network which can also include a centralized application-driven network compared to a decentralized application-driven network
  • the controller can be a local controller or a cloud (also called remote) controller.
  • the embodiment of the present application provides a method for acquiring a network policy, which is applied to a first access point AP of an application-driven network, where the application-driven network includes at least one AP, and the first AP is the at least one.
  • the method includes:
  • an application portrait of the first application sent by the site served by the first AP where the application portrait is sent by the site to the first AP after the first application is started, where the application portrait includes: An application identifier and a first QoE requirement, the first application being any application installed in the site;
  • target requirement format corresponding to the first application identifier, where the target requirement format is used to represent an analysis manner of the content carried in the first application
  • each network policy is a customized network policy for different applications, which realizes customization of QoE requirements, refines service granularity, and implements dynamic adjustment of services, thereby effectively improving user QoE.
  • the application driving network includes a controller, where the controller is configured to manage an AP in the application driving network, before receiving the application portrait of the first application sent by the site served by the first AP
  • the method further includes:
  • Obtaining a target requirement format corresponding to the first application identifier including:
  • the target requirement format corresponding to the first application identifier is obtained by querying the requirement format table, which is an achievable manner for obtaining the target requirement format corresponding to the first application identifier.
  • the querying the requirement format table to obtain a target requirement format corresponding to the first application identifier includes:
  • the first application identifier may not be recorded in the requirement format table of the first AP. If the first application identifier is not recorded, the first AP sends the application portrait of the first application to the controller. After receiving the application portrait, the query is performed in the controller's requirement format table, and the corresponding target requirement format is sent to the first AP to ensure that the target requirement format corresponding to the first application identifier can be obtained.
  • the method before receiving the application portrait of the first application sent by the site served by the first AP, the method also includes:
  • At least one candidate network policy corresponding to the first application identifier is obtained, and the network policy that matches the content in the first QoE requirement in the at least one candidate network policy is targeted.
  • the network policy is an achievable way to obtain the target network policy corresponding to the first application.
  • the querying the network policy table to obtain at least one candidate network policy corresponding to the first application identifier includes:
  • the first application identifier may not be recorded in the network policy table of the first AP. If the first application identifier is not recorded, the first AP sends the first application identifier to the controller. After receiving the first application identifier, the control performs a query in the required format table of the controller, and sends the corresponding at least one candidate network policy to the first AP to ensure that at least one corresponding to the first application identifier can be obtained.
  • Alternative network strategy is
  • the application identifier is an identifier obtained by binary conversion of an application signature; when the application driving network is a private network, the application signature is an application name; when the application driving network is a public network, the The application signature consists of the application vendor ID and the application name.
  • the application service provider identifier is used to uniquely identify the service provider that provides the application.
  • the application signature is composed of the application service provider identifier and the application name; when the application driver network is a public network, the application is different.
  • the application signature and QoE requirements of the application are defined by the network administrator, and the application service provider identification information is not required, that is, the application signature is the application name.
  • the method further includes:
  • the QoE Demand Response being used to indicate that the AP received the application portrait.
  • the requirement format recorded in the requirement format table includes at least one set of format information, and each set of the format information includes: a parameter name, a data type, and a length.
  • the method further includes:
  • the receiving an application portrait of the first application sent by the site served by the first AP includes:
  • the frame type of the QoE requirement frame is a management frame, and the value of the frame subtype field of the management frame is 0111.
  • the element of the frame entity of the QoE requirement frame includes two sets of elements, and the element identifier ID of the first group element has a value of 17 and a length of X bytes, and the carried content is an application identifier, and the second group of elements
  • the value of the element ID is 18, the length is N bytes, the content carried is the QoE requirement, the X is a constant within 1-255, and the N is a constant within 1-255.
  • the sending a QoE demand response to the site includes:
  • the frame type of the QoE requirement response frame is a management frame, and the value of the frame subtype field of the management frame is 0111 or 1111, and the element of the frame entity of the QoE requirement response frame includes two groups of elements, the first group The value of the element ID of the element is 19, the length is X bytes, the content carried is the application identifier, the element ID of the second group element is 20, the length is N bytes, and the content carried is QoE demand, the X Is a constant within 1-255, which is a constant within 1-255.
  • QoE requirement frame and the QoE requirement response frame are new management frames defined by the existing 802.11 protocol family according to the embodiment of the present application, so as to ensure customization of QoE requirements, and thus effectively improve users. QoE.
  • the embodiment of the present application provides a network policy acquiring device, which is applied to a first access point AP of an application driving network, where the application driving network includes at least one AP, and the first AP is the at least one Any AP in an AP, where the device is configured to perform the method for acquiring a network policy provided by the foregoing first aspect.
  • the acquiring device of the network policy provided by the foregoing second aspect may include: a processor and a network interface.
  • the processor includes one or more processing cores.
  • the processor executes various functional applications and data processing by running software programs and modules.
  • the processor can include a QoE management module.
  • the acquiring device of the network policy further includes components such as a memory and a bus.
  • the memory and the network interface are respectively connected to the processor through a bus.
  • the memory can be used to store software programs as well as modules. Specifically, the memory can store an operating system, an application module required for at least one function.
  • the operating system can be an operating system such as Real Time eXecutive (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • RTX Real Time eXecutive
  • LINUX LINUX
  • UNIX UNIX
  • WINDOWS WINDOWS
  • OS X OS X
  • the QoE management module is used to execute program code to implement the relevant steps of the first aspect above.
  • the memory can be used to store a QoE requirement format table and a network policy table.
  • the embodiment of the present application provides an application driving network, where the application driving network includes: at least one AP and at least one site, where the AP includes the acquiring device of the network policy according to any one of the foregoing aspects.
  • the application driving network further includes: a controller, where the controller is configured to manage an AP in the application driving network.
  • the application driven network can be a centralized application driven network.
  • the method, device, and application driving network of the network policy provided by the embodiment of the present application, after the application of the first AP is started, query the requirement format table, and obtain a corresponding target requirement format to analyze the first application of the first application.
  • QoE needs to obtain the corresponding target network policy. Therefore, each network policy is a customized network policy for different applications, which realizes customization of QoE requirements, refines service granularity, and realizes dynamic adjustment of services, thereby effectively improving user QoE.
  • 1-1 is a schematic diagram of a network environment of an application-driven network involved in a method for acquiring a network policy according to an embodiment of the present application;
  • 1-2 is a schematic diagram of a network environment of an application-driven network involved in another method for acquiring a network policy according to an embodiment of the present application;
  • 2-1 is a flowchart of a method for acquiring a network policy according to an embodiment of the present application
  • FIG. 2-2 is a schematic diagram of a frame format of a conventional 802.11 MAC header according to an embodiment of the present application
  • 2-3 is a schematic diagram of frame control of a QoE demand frame according to an embodiment of the present application.
  • FIGS. 2-4 are schematic diagrams of a frame entity of a QoE demand frame according to an embodiment of the present application.
  • FIGS. 2-5 are schematic diagrams of frame control of a QoE demand response frame according to an embodiment of the present application.
  • FIGS. 2-6 are schematic diagrams of a frame entity of a QoE demand response frame according to an embodiment of the present application.
  • FIGS. 2-7 are flowcharts of a method for a first AP to acquire a target requirement format corresponding to a first application identifier according to an embodiment of the present disclosure
  • 2-8 are flowcharts of a method for updating a requirement format table of a first AP initiated by a first AP according to an embodiment of the present application
  • 2-9 are flowcharts of a method for updating a requirement format table of a controller initiated by a controller by using an embodiment of the present application
  • FIGS. 2-10 are flowcharts of a method for updating a network policy table in which a first AP actively initiates a first AP according to an embodiment of the present application
  • 2-11 are flowcharts of a method for updating a network policy table in which a controller actively initiates a first AP according to an embodiment of the present application
  • FIG. 3 is a block diagram of a network device acquiring apparatus 300 according to an embodiment of the present application.
  • FIG. 4 is a block diagram of another network policy obtaining apparatus 300 according to an embodiment of the present application.
  • FIG. 5 is a block diagram of a first obtaining module 302 in a device for acquiring a network policy according to an embodiment of the present disclosure
  • FIG. 6 is a block diagram of still another network policy obtaining apparatus 300 according to an embodiment of the present disclosure.
  • FIG. 7 is a block diagram of a second obtaining module 304 in a device for acquiring a network policy according to an embodiment of the present disclosure
  • FIG. 8 is a block diagram of an apparatus 300 for acquiring a network policy according to an embodiment of the present application.
  • FIG. 9 is a block diagram of still another network policy obtaining apparatus 300 according to an embodiment of the present application.
  • FIG. 10 is a block diagram of an apparatus 20 for acquiring a network policy according to an embodiment of the present application.
  • FIG. 11 is a block diagram of a network policy acquisition device 30 according to an embodiment of the present application.
  • FIG. 12 is a block diagram of a network policy acquisition device 40 according to an embodiment of the present application.
  • FIG. 1 is a network environment of an application-driven network 0 involved in a method for acquiring a network policy according to an embodiment of the present application.
  • the application-driven network is a network capable of adjusting network parameters according to different service types and requirements.
  • the application driver network 0 includes at least one AP01 and at least one site (also referred to as a site) 02, each AP01 serving at least one site 02.
  • the site can send an application portrait carrying the QoE requirement to the AP serving the site when the application is started, and the AP determines the corresponding requirement format to parse the QoE requirement, thereby obtaining the network policy for the application.
  • the network policy is a policy based on the service or data transmission in the network, and may include priority scheduling, channel allocation, mobility management, network selection, and the like.
  • AP also known as wireless access point or hotspot
  • wireless access point is an access point for mobile users to enter the wired network. It is mainly deployed in the home, inside the building and inside the park. The typical coverage radius is tens of meters to hundreds of meters. Of course, it can also be deployed outdoors.
  • An AP is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect the clients of each wireless network together, and then connect the wireless network to the wired network.
  • the AP may be a site device or a network device with a Wireless Fidelity (abbreviation: WiFi) chip.
  • the AP may be a device supporting the 802.11ax system. Further, the AP may be a device supporting multiple formats such as 802.11n, 802.11g, 802.11b, 802.11a, and 802.11ac.
  • the STA can be a wireless communication chip, a wireless sensor, or a wireless communication site such as a mobile phone, tablet, set top box, smart television, smart wearable device, in-vehicle communication device, and computer.
  • the STA can support the 802.11ax system.
  • the STA can also support multiple formats such as 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • Figure 1-1 provides a decentralized application-driven network.
  • the AP service requirements format and network policy need to be pre-configured. They can be updated periodically by manual or other proprietary devices, but the update efficiency is low.
  • the application format and network policy management and update, the embodiment of the present application provides another network policy acquisition method involved in the network environment of the application driver network 0, as shown in Figure 1-2, the application driver network 0 is a A centralized application driver network, the centralized application driver network 0 may further include a controller 03 for managing an application driver network, as compared to the decentralized application driver network shown in FIG. 1-1.
  • the controller 03 can be a local controller or a cloud (also called remote) controller.
  • the local controller is suitable for private networks such as enterprise networks
  • the cloud controller is suitable for public networks, such as home networks, wireless networks used in shopping malls or supermarkets.
  • a mapping table for applying QoE requirements and network policies is issued by the controller.
  • one end of the controller is connected to the AP through a communication interface, and the controller can send a requirement format table and a network policy table, where the requirement format table is used to record the correspondence between the application identifier and the requirement format, and the network policy table is used for recording.
  • the corresponding relationship between the application identifier and the network policy; the other end of the controller provides an application programming interface (English: Application Programming Interface; API) for the application service provider, and the application service provider updates the requirement format table and the network policy table to implement Apply customization of the corresponding network policy.
  • API Application Programming Interface
  • the application-driven network 0 includes at least one AP.
  • the embodiment of the present application is described by using the first AP as an example.
  • the first AP is any AP of at least one AP included in the application-driven network 0, and the application driver network is assumed to be 0.
  • 2-1 is a flowchart of a method for acquiring a network policy, as shown in FIG. 2-1, which is shown in FIG. :
  • Step 201 The site acquires an application profile (English: Application Profile) after the first application is opened.
  • Each application that can be installed on the site carries an application portrait, and when the site opens the first application, the site recognizes its application portrait.
  • Application portraits identified by the site typically include: application signatures and QoE requirements, and application signatures are used to uniquely identify the corresponding application.
  • the site may not be able to obtain the application portrait, and when the site cannot obtain the application portrait, the site ends the action.
  • the application driving network may be a private network or a public network.
  • the application signature can be an application name without adding an identifier such as an application service provider identifier.
  • the corresponding application can be an enterprise application.
  • the application signature may be an application name.
  • the private network is a network of “AA Pharmaceutical Company”. Accordingly, if the application name of an application in the network is “AA Medicine”, the application signature “AA Medicine” is applied. The application can be uniquely identified and the signature of the application is "AA Medicine.”
  • the application signature may be composed of the application service provider identifier and the application name.
  • the format of the application signature may be “application service provider identifier (English: venderID)_application name (English: name)”, and the application service provider identifier and the application name may be composed of characters other than “_”.
  • a string, the specific content can be defined by the application service provider.
  • the application: Sohu video application service provider identifier is "sohu”
  • the application name is "video”
  • the application signature is "sohu_video”
  • the application service provider identifier is "tencent” and the application name is "wechat”. Therefore, the application signature is "tencent_wechat”; for example, the application application identifier of qq is "tencent” and the application name is “qq”, therefore,
  • the application signature is "tencent_qq”.
  • Step 202 The station sends an application portrait to the first AP.
  • the application signature of the application signature needs to be binary-converted, and the binary-transformed application signature is called an application.
  • Identification also known as application identification (English: Identification; referred to as: ID).
  • ID the binary-transformed application signature
  • the application portrait needs to be encrypted before transmission.
  • the fifth version of the message digest algorithm (English: Message Digest Algorithm; MD5 algorithm) can be used for encryption and binary conversion.
  • MD5 algorithm can be used to convert the application signature into 128-bit binary (occupying 128 bits (Chinese: bit)) data, and finally obtain an encrypted and binary application identifier.
  • the application signature of Sohu video is “sohu_video”, and the application identifier is da73292b2b0351b1c5ce1ce7b275448c by the MD5 algorithm (here, the 128-bit encrypted data represented by hexadecimal is taken as an example).
  • the application portrait sent by the first application may include: a first application identifier and a first QoE requirement.
  • the first application identifier is used to uniquely identify the first application
  • the first QoE requirement is a QoE requirement of the first application
  • the first application is any one of the site installable applications.
  • the application may be an application that supports different types of services, for example, a management application such as a site management application, a chat application such as a qq application or a WeChat application, or a video application such as Sohu video.
  • the application portrait of the first application is reported to the first AP through a communication interface between the site and the first AP.
  • the site may transmit an application portrait to the first AP by sending a QoE demand frame carrying the application portrait.
  • the QoE requirement is in the range of 0-255 bytes (Chinese: byte, abbreviated as B) in the above QoE requirement frame, and the specific meaning is defined by the application service provider.
  • the QoE requirement length of a live broadcast application is 8 bytes, wherein the first 4 bytes are floating point type average opinion scores (English: mean opinion score; MOS for short), and the last 4 bytes are floating point type demand fluency.
  • Step 203 The first AP sends a QoE demand response to the station, where the QoE requirement response is used to indicate that the AP receives the application portrait.
  • the first AP periodically detects whether an application portrait is received, sends a QoE demand response to the site after receiving the application portrait, and continues to detect after the application portrait is not received.
  • a timer can be set on the first AP, and the first is triggered by the timer. Periodic detection of the AP.
  • the QoE demand response is sent to the site through the communication interface between the first AP and the site.
  • the first AP may transmit the QoE demand response to the site by sending a QoE demand response frame carrying the QoE demand response. That is, the first AP sends a QoE demand response frame to the station, and the QoE demand response frame carries a QoE demand response.
  • the embodiment of the present application defines a QoE requirement reporting protocol and a corresponding QoE management frame structure.
  • the QoE management frame is a newly defined management frame in the 802.11 protocol suite.
  • the QoE requirement reporting protocol is divided into the response of the site to the AP to initiate the QoE requirement and the AP to the QoE requirement initiated by the site. For the specific process, refer to steps 202 and 203 above.
  • the frames of the 802.11 protocol family contain management frames, control frames, and data frames.
  • the management frame is responsible for supervision and is mainly used to join or quit the wireless network and handle the transfer of associations between access points.
  • the format of the MAC header (English: MAC Header) of the traditional 802.11 media access control (English: Media Access Control; MAC address) frame can be as shown in Figure 2-2.
  • the MAC header includes: frame control (English: Frame Control), life cycle/identity (English: Duration/ID), address (English: Address), sequence control (English: Sequence Control), frame entity (English: Frame Body) And frame check sequence (English: Frame Check Sequence; FCS for short), the length from frame control to frame check sequence is: 2bytes, 2bytes, 6bytes, 2bytes, 0-2312bytes and 4bytes.
  • the frame control includes: protocol version (English: Protocol Version), frame type (English: Type), and frame subtype (English: Subtype), and sends to the distribution system (English: To DS), and the distribution system sends (English: From DS), fragmentation mark (English: More Frag), retransmission (English: Retry), power saving mode (English: Pwr Mgt), more data (English: More Data), protected frame flag (English: Protected Frame ), serial number (English: Order), the length of the protocol version to the serial number is: 2bits (Chinese: bit), 2bits, 4bits, 1bit, 1bit, 1bit, 1bit, 1bit, 1bit, 1bit and 1bit.
  • the frame type field in the frame control When the value of the frame type field in the frame control is 00, it means that the frame is a management frame, and the frame subtype determines the type of the management frame.
  • the data of the frame entity of the management frame carries site-related information, and its element (English: element) is divided into a fixed length (English: fix field) element and a length non-fixed element, also called an information element (information element).
  • the embodiment of the present application defines a new management frame based on the existing 802.11 protocol family. Specifically, it includes: QoE demand frame and QoE demand response frame. Due to the elements of the traditional management frame of the frame entity, element ID 17-31 is not used in the 802.11 protocol family. Therefore, the QoE demand frame and the QoE demand response frame are as follows:
  • the QoE demand frame is used to transmit the application portrait.
  • the frame type of the QoE demand frame is the management frame.
  • the value of the frame subtype field of the management frame is 0111 or 1111.
  • the specific structure of the frame control may refer to FIG. 2-2 above in addition to the frame subtype.
  • the element of the frame entity of the QoE requirement frame includes two sets of elements, and the element ID of the first group element has a value of 17 and a length of X bytes (abbreviated as B in FIG. 2-4).
  • the content carried is the application identifier.
  • the element ID of the second group of elements is 18, the length is N bytes, the content carried is QoE demand, X is a constant within 1-255, and N is a constant within 1-255. .
  • the frame type of the QoE demand response frame is the management frame.
  • the value of the frame subtype field of the management frame is 0111 or 1111.
  • Figure 2-5 shows 1111 as an example. Refer to Figure 2-5.
  • the specific structure of its frame control can refer to Figure 2-2 above except for the frame subtype.
  • the structure of the frame entity of the QoE requirement response frame may be the same as the structure of the frame entity of the QoE requirement frame, and the elements of the frame entity of the QoE requirement response frame include two sets of elements, the first group of elements.
  • the value of the element ID is 19, and the length is X bytes (abbreviated as B in Figure 2-6).
  • the content carried is the application identifier.
  • the element ID of the second group element is 20, the length is N bytes, and the content is carried.
  • X is a constant within 1-255
  • N is a constant within 1-255.
  • the values of the frame subtype fields of the demand frame and the demand response frame may be the same or different.
  • the element ID values of the elements of the demand frame and the demand response frame may be set differently. To distinguish; when the values of the frame subtypes are different, the element ID values of the elements of the demand frame and the demand response frame may be set to be the same or different.
  • an application layer protocol may be added to perform transmission of a demand frame or a demand response frame, or an 802.11 protocol (similar to 802.11e) may be added to perform transmission of a demand frame or a demand response frame.
  • 802.11 protocol similar to 802.11e
  • Step 204 The first AP acquires a target requirement format corresponding to the first application identifier, where the target requirement format is used to represent an analysis manner of the content carried in the first application.
  • the first AP may further receive the requirement format table sent by the controller to obtain the requirement format table, and the requirement format table.
  • the requirement format table may be as shown in Table 1.
  • the requirement format recorded in the requirement format table includes at least one set of format information, and each group format information includes: a parameter name, a data type, and a length, and the specific format is (parameter name, Data type, length; parameter name, data type, length).
  • the number of groups of the above format information is preset by the application service provider, and the length of each required format may be defined according to a specific usage scenario.
  • the parameter name is the name of the QoE parameter specified by the application vendor.
  • the parameter name is a string (English: string) type
  • the data type can be a known data type in the C language
  • the length unit is byte.
  • Table 1 the first behavior example in Table 1 is used.
  • the QoE requirement involves two parameters, namely MOS value and delay requirement, where the first 4 bytes are float type.
  • the MOS value, the last 4 bytes are the delay type of the float type (English: delay), and the QoE requirement format is ("MOS", float, 4; "delay", float, 4).
  • the specific parameters in the QoE requirement format are agreed by the application service provider and the network service provider, and are stored in the first AP.
  • the first AP may query the requirement format table to obtain a target requirement format corresponding to the first application identifier.
  • the process of the first AP querying the requirement format table and obtaining the target requirement format corresponding to the first application identifier may include:
  • Step 2041 The first AP detects whether the first application identifier is recorded in the requirement format table.
  • step 2042 the first application identifier is recorded in the requirement format table, and the first AP obtains the target requirement format corresponding to the first application identifier.
  • the first application is a Sohu video
  • the first application identifier is da73292b2b0351b1c5ce1ce7b275448c.
  • the query table 1 indicates that the first application identifier is recorded in the first application identifier. Therefore, the target application requirement format corresponding to the first application identifier can be obtained: MOS", float, 4; "delay”, float, 4).
  • Step 2043 When the first application identifier is not recorded in the requirement format table, the first AP sends the application portrait of the first application to the controller.
  • Step 2044 The controller acquires a target requirement format according to the application portrait.
  • the controller can maintain multiple demand format tables, and each requirement format table corresponds to an AP, and records the correspondence between the application identifier and the requirement format; the controller can also maintain a demand format summary table, where the controller records the controller management. Correspondence between the application identifier and the required format corresponding to all APs.
  • the controller queries the requirement format table corresponding to the first AP by using the first application identifier carried in the portrait. When the first application identifier exists in the requirement format table, the corresponding target requirement format is obtained. When the controller does not query the first application identifier, the action is stopped.
  • Step 2045 The controller sends a target requirement format to the first AP.
  • the target requirement format is sent to the first AP.
  • Step 205 The first AP parses the first QoE requirement by using a target requirement format, and obtains content in the first QoE requirement.
  • the first application is Sohu video
  • the target application requirement format is obtained: ("MOS”, float, 4; “delay”, float, 4)
  • the first QoE requirement is parsed by using the target application requirement format.
  • the content of the application requirements is ("MOS”, 3.75, "delay”, 100).
  • the application requirements indicate that there are two indicators for the QoE demand of Sohu video, namely MOS and delay, the demand of MOS is 3.72, and the minimum delay requirement is 100 milliseconds (English: ms).
  • the content may be stored in the storage component.
  • the content may be stored in the form of a QoE requirement table, as shown in Table 2.
  • the corresponding relationship between the application identifier and the content of the QoE requirement is recorded in the QoE requirement table.
  • the first behavior example in Table 2 is described. It can be seen that the QoE requirement content corresponding to the application with the application identifier da73292b2b0351b1c5ce1ce7b275448c is ("MOS", 3.75, "delay", 100), indicates that the demand for MOS is 3.72, and the minimum delay requirement is 100ms. According to the table, it is convenient to execute the corresponding network policy.
  • Step 206 The first AP acquires a target network policy corresponding to the first application according to the content of the first application identifier and the first QoE requirement.
  • the first AP may further receive the network policy table sent by the controller to obtain the network policy table, and the network policy table. Used to record the correspondence between application identifiers and network policies.
  • the network policy recorded in the network policy table is agreed by the application service provider and the network service provider, and is stored in the first AP.
  • the network policy table can be as shown in Table 3. Each application identifier can correspond to at least one network policy.
  • the first AP may obtain the target network policy corresponding to the first application according to the content of the first application identifier and the first QoE requirement. Specifically, the first AP may query the network policy table to obtain the corresponding corresponding to the first application identifier. At least one alternative network policy; determining, in the at least one alternative network policy, a network policy that matches content in the first QoE requirement as a target network policy, the matched policy being a policy that satisfies the QoE requirement to a maximum extent . In an actual application, determining, in the at least one alternative network policy, the network policy that matches the content in the first QoE requirement as the target network policy may adopt a preset evaluation algorithm to evaluate to obtain the maximum satisfaction of the QoE requirement. Strategy.
  • the specific process of querying the network policy table to obtain the at least one candidate network policy corresponding to the first application identifier includes: detecting whether the first application identifier is recorded in the network policy table; and recording the first application in the network policy table And identifying, by the identifier, the at least one candidate network policy corresponding to the first application identifier; when the first application identifier is not recorded in the network policy table, sending the first application identifier to the controller; An alternative network strategy.
  • the content of the QoE requirement corresponding to the application of the first application identifier da73292b2b0351b1c5ce1ce7b275448c is ("MOS”, 3.75, "delay”, 100), and the first application identifier query table 3 can obtain at least one preparation.
  • Select network policies priority scheduling policy, channel allocation strategy, mobility management strategy and network selection strategy.
  • the first AP may select a policy that best satisfies the QoE requirement ("MOS", 3.75, "delay", 100) from among these alternative network policies.
  • the delay of the service with the priority of 1 is less than or equal to 100 ms, and the priority scheduling policy can meet the QoE requirement, and the priority scheduling policy can be determined as the target network by using a preset evaluation algorithm. Strategy.
  • Step 207 The first AP performs a target network policy on the first application.
  • the first AP performs a target network policy on the first application, that is, the adjustment granularity corresponding to the target network policy is an application, and in actual application, each network policy recorded in the network policy table is configured. There is a corresponding execution method, and the execution method may be recorded in the network policy table, or may be preset in another location. After the target network policy is determined, the execution method corresponding to the target network policy may be obtained to execute the target network policy.
  • the foregoing target network policy is a priority scheduling policy
  • the corresponding execution method is: adjusting the priority of the application to 1.
  • the first AP can set the priority of the first application to 1 according to the execution method.
  • the requirement format table and the network policy table are centrally managed by the controller, so the first AP needs to update its corresponding requirement format table and Network policy table for obtaining network policies.
  • the embodiment of the present application specifically describes the update process of the requirement format table in the following two aspects.
  • the first AP may initiate an update of the requirement format table of the first AP.
  • the update process may be performed when the first AP is started, or periodically initiated by the first AP. As shown in Figure 2-8, the update process is as follows:
  • Step 301 The first AP sends a format table update request to the controller, where the format table update request includes: an identifier of the first AP.
  • Step 302 After receiving the format table update request, the controller checks whether there is a demand format table corresponding to the identifier of the first AP in the controller. When the required format table corresponding to the identifier of the first AP exists in the controller, step 303 is performed. When there is no requirement format table corresponding to the identifier of the first AP in the controller, step 306 is performed.
  • the controller may send the entire requirement format table on the controller to each AP, but since each AP management application drives some sites in the network, in order to reduce the load of each AP, each AP only needs to obtain
  • the corresponding requirement format table may be, and the corresponding requirement format table records the requirement format of the application of the terminal served by the AP.
  • Step 303 The controller acquires a requirement format table corresponding to the identifier of the first AP. Go to step 304.
  • the controller may be configured with a correspondence table between the AP identifier and the requirement format table, where the correspondence relationship table records the identifier of the AP managed by the controller, and the corresponding requirement format table, and the controller may query the corresponding information according to the identifier of the first AP.
  • the relationship table obtains the corresponding requirement format table when the identifier of the first AP is recorded in the correspondence table.
  • Step 304 The controller sends a requirement format table to the first AP. Go to step 305.
  • Step 305 After receiving the requirement format table, the first AP updates the requirement format table.
  • Step 306 The controller sends a deletion indication to the first AP, where the deletion indication is used to indicate that the controller does not record the requirement format table corresponding to the identifier of the first AP. Go to step 307.
  • the application service provider may not be equipped with the required format table for the site served by the first AP, and on the other hand, the application service provider may not be the first The demand format table of the site of the AP service is recorded. Therefore, the controller can send a delete indication. In practical applications, the controller can send a blank request format table to indicate the purpose of deletion.
  • Step 307 After receiving the deletion indication, the first AP deletes the requirement format table of the first AP.
  • the corresponding requirement format table may be set to an empty table, that is, all contents in the entry are cleared, and this method may also be considered as a requirement.
  • the deletion of the format table may be set to an empty table, that is, all contents in the entry are cleared, and this method may also be considered as a requirement.
  • the controller can initiate an update of the demand format table of the first AP.
  • the update process is as follows:
  • Step 401 After updating the requirement format table, the controller sends a format table update request to the first AP, where the format table update request includes the updated requirement format table.
  • the controller records the new requirement format definition in the requirement format table to implement the update of the requirement format table.
  • Step 402 After receiving the format table update request, the first AP updates the requirement format table.
  • the controller may also delete the requirement format table. For example, when the controller detects that a certain requirement format table is invalid, the controller deletes the requirement format table and sends a deletion indication to the first AP. The deletion indicates that the requirement format table is deleted. In the actual application, the controller can send a blank requirement format table to indicate the purpose of deleting. Accordingly, the first AP can set the corresponding requirement format table to an empty table, that is, All the contents of the entry are cleared, which can also be considered as the deletion of the required format table.
  • the embodiment of the present application specifically describes the update process of the network policy table in the following two aspects.
  • the first AP may initiate an update of the network policy table of the first AP.
  • the update process may be performed when the first AP is started, or periodically initiated by the first AP. As shown in Figure 2-10, the update process is as follows:
  • Step 501 The first AP sends a network policy table update request to the controller, where the network policy table update request includes: an identifier of the first AP.
  • Step 502 After receiving the network policy table update request, the controller checks whether the network policy table corresponding to the identifier of the first AP exists in the controller. When the network policy table corresponding to the identifier of the first AP exists in the controller, step 503 is performed. When the network policy table corresponding to the identifier of the first AP does not exist in the controller, step 506 is performed.
  • the controller may send the entire network policy table on the controller to each AP, but since each AP management application drives some sites in the network, in order to reduce the load of each AP, each AP only needs to obtain its
  • the corresponding network policy table may be, and the corresponding network policy table records the network policy of the application of the terminal served by the AP.
  • Step 503 The controller acquires a network policy table corresponding to the identifier of the first AP. Go to step 504.
  • the controller may be configured with a correspondence table between the AP identifier and the network policy table, where the correspondence relationship table records the identifier of the AP managed by the controller, and the corresponding network policy table, and the controller may query the corresponding according to the identifier of the first AP.
  • the relationship table acquires the corresponding network policy table when the identifier of the first AP is recorded in the correspondence table.
  • Step 504 The controller sends a network policy table to the first AP. Go to step 505.
  • Step 505 After receiving the network policy table, the first AP updates the network policy table.
  • Step 506 The controller sends a deletion indication to the first AP, where the deletion indication is used to indicate that the controller does not record the network policy table corresponding to the identifier of the first AP. Go to step 507.
  • the application service provider may not be equipped with the network policy table for the site served by the first AP, and on the other hand, the application service provider may not be the first The network policy table of the AP service site is recorded. Therefore, the controller can send a delete indication. In practical applications, the controller can send a blank network policy table to indicate the purpose of deletion.
  • Step 507 After receiving the deletion indication, the first AP deletes the network policy table of the first AP.
  • the corresponding network policy table may be set to an empty table, that is, all the contents in the entry are cleared, and the method may also be considered as a network.
  • the deletion of the policy table may be set to an empty table, that is, all the contents in the entry are cleared, and the method may also be considered as a network. The deletion of the policy table.
  • the controller may initiate an update of the network policy table of the first AP.
  • the update process is as follows:
  • Step 601 After updating the network policy table, the controller sends a network policy table update request to the first AP, where the network policy table update request includes the updated network policy table.
  • the controller records the new network policy definition in the network policy table to implement the update of the network policy table.
  • Step 602 After receiving the network policy table update request, the first AP updates the network policy table.
  • the controller may also delete the network policy table. For example, when the controller detects that a certain network policy table is invalid, the controller deletes the network policy table and sends a deletion indication to the first AP. The deletion indicates that the network policy table is deleted. In the actual application, the controller can send a blank network policy table to indicate the purpose of deleting. Accordingly, the first AP can set the corresponding network policy table to an empty table, that is, Cleared the contents of the entry There is content, this way can also be considered as the deletion of the network policy table.
  • the method for obtaining the network policy provided by the embodiment of the present application, after the application of the first AP is started, queries the requirement format table, and obtains a corresponding target requirement format to parse the first QoE of the first application.
  • the requirements are to obtain the corresponding target network policy. Therefore, each network policy is a customized network policy for different applications, realizing the customization of QoE requirements, refining the service granularity, and realizing dynamic adjustment of services, thereby effectively improving user QoE.
  • QoE demand refers to the user's demand for the quality and performance of the application or service.
  • the QoE requirements of different applications are different. QoE reflects the subjective characteristics of the user using the application, and it is difficult to have a unified quantitative indicator.
  • the QoE requirement is determined by the application service provider. Even with the same type of service, such as video, different application providers can still make different QoE demand parameters.
  • Application providers can customize different demand formats for different applications to provide different network policies. Increased flexibility in QoE requirements management. Due to the customization of the requirements format, the parameters of the service type and the QoE requirements reported by the site are well scalable.
  • FIG. 3 is a block diagram of an acquisition device 300 for a network policy, where the acquisition device 300 of the network policy is applied to a first access point AP of an application-driven network, and the application-driven network includes at least one AP, according to an exemplary embodiment.
  • the first AP is any one of the at least one AP.
  • the acquiring device 300 of the network policy may include:
  • the first receiving module 301 is configured to receive an application portrait of the first application sent by the site served by the first AP, where the application portrait is sent by the site to the first AP after the first application is opened, and the application portrait includes: the first application identifier And the first QoE requirement, the first application is any application installed in the site.
  • the first obtaining module 302 is configured to obtain a target requirement format corresponding to the first application identifier, where the target requirement format is used to represent a parsing manner of the content carried in the first application.
  • the processing module 303 is configured to parse the first QoE requirement by using a target requirement format to obtain content in the first QoE requirement.
  • the second obtaining module 304 is configured to obtain a target network policy corresponding to the first application according to the content of the first application identifier and the first QoE requirement.
  • the acquiring device of the network policy receives the application portrait of the first application sent by the site by using the first receiving module, and the first acquiring module acquires the target requirement format corresponding to the first application identifier, and the processing module The first QoE requirement is parsed by using the target requirement format, and the second obtaining module obtains the corresponding target network policy corresponding to the first application. Therefore, each network policy is a customized network policy for different applications, and then the QoE requirement is customized. Granular service granularity, realizing dynamic adjustment of services, thus effectively improving user QoE.
  • the application driver network includes a controller for managing an AP in the application driver network.
  • the network device acquiring device 300 may further include:
  • the second receiving module 305 is configured to receive a requirement format table sent by the controller, where the requirement format table is used to record a correspondence between the application identifier and the requirement format.
  • the first obtaining module 302 may include:
  • the first query sub-module 3021 is configured to query the requirement format table to obtain a target requirement format corresponding to the first application identifier.
  • the first query submodule 3021 can be used to:
  • the target requirement format corresponding to the first application identifier is obtained.
  • the application portrait of the first application is sent to the controller.
  • the acquiring device 300 of the network policy may further include:
  • the third receiving module 306 is configured to receive a network policy table sent by the controller, where the network policy table is used to record a correspondence between the application identifier and the network policy.
  • the second obtaining module 304 may include:
  • the second query sub-module 3041 is configured to query the network policy table to obtain at least one candidate network policy corresponding to the first application identifier.
  • the determining sub-module 3042 is configured to determine, in the at least one alternative network policy, a network policy that matches content in the first QoE requirement as the target network policy.
  • the second query submodule 3041 can be used to:
  • the at least one candidate network policy corresponding to the first application identifier is obtained.
  • the first application identifier is not recorded in the network policy table, the first application identifier is sent to the controller.
  • the application identifier is an identifier obtained by binary conversion of the application signature.
  • the application signature is an application name; when the application driver network is a public network, the application signature is composed of an application service provider identifier and an application name.
  • the acquiring device 300 of the network policy may further include:
  • the sending module 307 is configured to send a QoE demand response to the station, where the QoE demand response is used to indicate that the AP receives the application portrait.
  • the requirement format recorded in the requirement format table includes at least one set of format information, and each set of format information includes: a parameter name, a data type, and a length.
  • the acquiring device 300 of the network policy may further include:
  • the executing module 308 is configured to execute a target network policy for the first application.
  • the first receiving module 301 is configured to:
  • the QoE demand frame sent by the receiving station the QoE demand frame carries the application portrait.
  • the frame type of the QoE requirement frame is a management frame, and the value of the frame subtype field of the management frame is 0111 or 1111, and the element of the frame entity of the QoE requirement frame includes two sets of elements, and the value of the element identity ID of the first group element It is 17 and the length is X bytes.
  • the content carried is the application identifier.
  • the element ID of the second group of elements is 18, the length is N bytes, the content carried is QoE demand, and X is a constant within 1-255. N is a constant within 1-255.
  • the sending module 307 is configured to:
  • the QoE demand response frame is sent to the site, and the QoE demand response frame carries the QoE demand response.
  • the frame type of the QoE demand response frame is a management frame, and the value of the frame subtype field of the management frame is 0111 or 1111, and the element of the frame entity of the QoE demand response frame includes two sets of elements, and the value of the element ID of the first group of elements Is 19,
  • the length is X bytes, and the content carried is the application identifier.
  • the element ID of the second group of elements is 20, the length is N bytes, the content carried is QoE demand, X is a constant within 1-255, and N is 1 Constant within -255.
  • the acquiring device of the network policy receives the application portrait of the first application sent by the site by using the first receiving module, and the first acquiring module acquires the target requirement format corresponding to the first application identifier, and the processing module The first QoE requirement is parsed by using the target requirement format, and the second obtaining module obtains the corresponding target network policy corresponding to the first application. Therefore, each network policy is a customized network policy for different applications, and then the QoE requirement is customized. Granular service granularity, realizing dynamic adjustment of services, thus effectively improving user QoE.
  • FIG. 10 is a schematic structural diagram of a network device acquiring device 20 according to an exemplary embodiment of the present application.
  • the acquiring device 20 of the network policy may include: a processor 22 and a network interface 24 .
  • Processor 22 includes one or more processing cores.
  • the processor 22 executes various functional applications and data processing by running software programs and modules.
  • the processor 22 can include a QoE management module 222.
  • the network policy acquisition device 20 further includes components such as a memory 26, a bus 28, and the like.
  • the memory 26 and the network interface 24 are connected to the processor 22 via a bus 28, respectively.
  • Memory 26 can be used to store software programs as well as modules.
  • memory 26 may store operating system 262 and application modules 264 required for at least one function.
  • the operating system 262 can be an operating system such as Real Time eXecutive (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • the memory can be used to store the QoE Demand Format Table 266 and the Network Policy Table 268.
  • the application module 264 can include:
  • the receiving unit 2641 has the same or similar function as the first receiving module 301.
  • the first obtaining unit 2642 has the same or similar function as the first obtaining module 302.
  • Processing unit 2643 has the same or similar functionality as processing module 303.
  • the second obtaining unit 2644 has the same or similar function as the second acquiring module 304.
  • the QoE management module 222 can execute the application program corresponding to the foregoing receiving unit 2641 to the second obtaining unit 2644 to implement the network policy obtaining method provided by the embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network device acquiring device 30 according to an exemplary embodiment of the present application.
  • the acquiring device 30 of the network policy may include: a processor 32 and a network interface 34 .
  • Processor 32 includes one or more processing cores.
  • the processor 32 executes various functional applications and data processing by running software programs and modules.
  • the processor 32 can include a QoE management module 322.
  • the network policy acquisition device 30 further includes components such as a memory 36, a bus 38, and the like.
  • the memory 36 and the network interface 34 are connected to the processor 32 via a bus 38, respectively.
  • Memory 36 can be used to store software programs as well as modules. Specifically, the memory 36 can store the operating system 362 and At least one function required by the application module 364.
  • the operating system 362 can be an operating system such as Real Time eXecutive (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • the memory can be used to store the QoE Demand Format Table 366 and the Network Policy Table 368.
  • the QoE management module 322 can execute a program corresponding to the application module 364 to manage APs in the application-driven network.
  • the QoE management module 322 can execute a program corresponding to the application module 364 to manage APs in the application-driven network.
  • FIG. 12 is a schematic structural diagram of a network device acquiring device 40 according to an exemplary embodiment of the present application.
  • the acquiring device 40 of the network policy may include: a processor 42 and a network interface 44.
  • Processor 42 includes one or more processing cores.
  • the processor 42 executes various functional applications and data processing by running software programs and modules.
  • processor 42 may include QoE management module 422.
  • the network policy acquisition device 40 further includes components such as a memory 46, a bus 48, and the like.
  • the memory 46 and the network interface 44 are connected to the processor 42 via a bus 48, respectively.
  • Memory 46 can be used to store software programs as well as modules.
  • memory 46 may store operating system 462 and application modules 464 required for at least one function.
  • the operating system 462 can be an operating system such as Real Time eXecutive (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • the first application 4641 is included in the application module 464.
  • the QoE management module 422 can execute the code corresponding to the application module 464, and the application portrait of the first application sent to the first AP after the first application 4641 is started.
  • the specific implementation steps reference may be made to the above steps 201-202 and the like.
  • the embodiment of the present application provides an application driving network, where the application driving network includes: at least one AP and at least one site, and the AP includes the acquiring device 300 of the foregoing network policy.
  • the application driving network further includes: a controller, configured to manage the AP in the application driving network.
  • the application driven network can be a centralized application driven network.
  • An embodiment of the present application provides an application driving network, where the application driving network includes: at least one AP and at least one site, the AP includes the foregoing network policy acquiring device 20, and the site includes the foregoing network policy acquiring device 40.
  • the application driving network further includes: a controller, configured to manage the AP in the application driving network.
  • the controller includes the acquisition device 30 of the network policy described above.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本申请公开了一种网络策略的获取方法、设备及应用驱动网络，属于通信领域。所述方法应用于应用驱动网络的第一接入点AP，所述方法包括：接收所述第一AP所服务的站点发送的第一应用的应用肖像，所述应用肖像是站点在所述第一应用开启后发送给所述第一AP的，所述应用肖像包括：第一应用标识和第一QoE需求，所述第一应用为所述站点中安装的任一应用；获取所述第一应用标识对应的目标需求格式，所述目标需求格式用于表征所述第一应用中携带的内容的解析方式；采用所述目标需求格式解析所述第一QoE需求，得到所述第一QoE需求中的内容；根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略。本申请有效提升了用户QoE。

Description

网络策略的获取方法、设备及应用驱动网络
本申请要求于2016年11月25日提交中国专利局、申请号为201611056710.1、发明名称为“网络策略的获取方法、设备及应用驱动网络”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，特别涉及一种网络策略的获取方法、设备及应用驱动网络。
背景技术
应用驱动网络(英文：Application Driven Network；简称：ADN)，是一种能够根据不同业务类型和需求调整网络参数的网络，该网络可以提升用户体验质量(英文：Quality of Experience；简称：QoE)。
目前的应用驱动网络可以包括接入点(英文：Access Point；简称：AP)和站(英文：Station；简称：STA)点，AP和站点的交互基于802.11e协议。在802.11e协议中，所有业务被分为4种业务类型(背景流，视频，语音以及尽力而为的数据)，并相应设置4个优先级，也即是，不同的业务类型对应不同的优先级。一个AP能够要求其管理的每个站点为每个业务类型的访问发送一个传输规范请求。这个请求用于指示该站点的每个业务类型的访问的数据量以及可以承受的时延阈值。AP根据每个申请对应的业务类型确定相应的优先级，高优先级业务获得更多的信道竞争机会。
但是，目前的网络策略的实施力度是根据预先定义的业务类型，服务粒度较粗，无法有效地提升用户的QoE。
发明内容
为了解决现有技术中无法有效地提升用户的QoE的问题，本申请实施例提供了一种网络策略的获取方法、设备及应用驱动网络。所述技术方案如下：
本申请实施例提供了一种网络策略的获取方法所涉及的应用驱动网络的网络环境，该应用驱动网络是一种能够根据不同业务类型和需求调整网络参数的网络，该应用驱动网络包括至少一个AP和至少一个站点(也称站点)，每个AP为至少一个站点提供服务。
在该应用驱动网络中，站点可以在开启应用时，向服务于该站点的AP发送携带QoE需求的应用肖像，AP确定相应的需求格式来解析QoE需求，从而获取针对该应用的网络策略。在本申请实施例中，网络策略为网络中业务或数据传输时所基于的策略，示例的，可以包括优先级调度，信道分配，移动性管理和网络选择等等。
本申请实施例提供了一种网络策略的获取方法所涉及的非集中式的应用驱动网络，AP存储的需求格式和网络策略需要预先配置，可以由人工或其他专有装置定期更新，但是更新效率较低，为了方便各个AP的需求格式和网络策略的管理和更新，本申请实施例提供另一种网络策略的获取方法所涉及的应用驱动网络的网络环境，该应用驱动网络是一种集中式的应用驱动网络，相较于非集中式的应用驱动网络，该集中式应用驱动网络还可以包括 控制器，该控制器用于管理应用驱动网络中的AP。该控制器可以是本地控制器，也可以是云端(也称远端)控制器。
第一方面，本申请实施例提供了一种网络策略的获取方法，应用于应用驱动网络的第一接入点AP，所述应用驱动网络包括至少一个AP，所述第一AP为所述至少一个AP中的任一AP，所述方法包括：
接收所述第一AP所服务的站点发送的第一应用的应用肖像，所述应用肖像是站点在所述第一应用开启后发送给所述第一AP的，所述应用肖像包括：第一应用标识和第一QoE需求，所述第一应用为所述站点中安装的任一应用；
获取所述第一应用标识对应的目标需求格式，所述目标需求格式用于表征所述第一应用中携带的内容的解析方式；
采用所述目标需求格式解析所述第一QoE需求，得到所述第一QoE需求中的内容；
根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略。
需要说明的是，由于第一AP在站点的应用开启后，查询需求格式表，得到相应的目标需求格式，以解析该第一应用的第一QoE需求，从而获取相应的目标网络策略，因此，每个网络策略是针对不同应用的定制网络策略，实现QoE需求的定制化，细化服务粒度，实现服务的动态调整，从而有效提升用户QoE。
可选地，所述应用驱动网络包括控制器，所述控制器用于管理所述应用驱动网络中的AP，在所述接收所述第一AP所服务的站点发送的第一应用的应用肖像之前，所述方法还包括：
接收所述控制器发送的需求格式表，所述需求格式表用于记录应用标识与需求格式的对应关系；
所述获取所述第一应用标识对应的目标需求格式，包括：
查询所述需求格式表，得到所述第一应用标识对应的目标需求格式。
需要说明的是，通过查询需求格式表得到第一应用标识对应的目标需求格式，是获取第一应用标识对应的目标需求格式的一种可实现方式。
可选地，所述查询所述需求格式表，得到所述第一应用标识对应的目标需求格式，包括：
检测所述需求格式表中是否记录有所述第一应用标识；
当所述需求格式表中记录有所述第一应用标识，获取所述第一应用标识对应的目标需求格式；
当所述需求格式表中未记录所述第一应用标识，向所述控制器发送所述第一应用的应用肖像；
接收所述控制器发送的所述目标需求格式。
需要说明的是，在查询需求格式表时，第一AP的需求格式表中可能没有记录第一应用标识，若没有记录该第一应用标识，第一AP向控制器发送第一应用的应用肖像，控制接收该应用肖像后，在控制器的需求格式表中进行查询，并将对应的目标需求格式发送给第一AP，以保证能够得到第一应用标识对应的目标需求格式。
可选地，在所述接收所述第一AP所服务的站点发送的第一应用的应用肖像之前，所述 方法还包括：
接收所述控制器发送的网络策略表，所述网络策略表用于记录应用标识与网络策略的对应关系；
所述根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略，包括：
查询所述网络策略表，得到所述第一应用标识对应的至少一种备选网络策略；
在所述至少一种备选网络策略中确定与所述第一QoE需求中的内容相匹配的网络策略作为所述目标网络策略。
需要说明的是，通过查询网络策略表得到第一应用标识对应的至少一种备选网络策略，并将至少一种备选网络策略中与第一QoE需求中的内容相匹配的网络策略作为目标网络策略，是获取第一应用对应的目标网络策略的一种可实现方式。
可选地，所述查询所述网络策略表，得到所述第一应用标识对应的至少一种备选网络策略，包括：
检测所述网络策略表中是否记录有所述第一应用标识；
当所述网络策略表中记录有所述第一应用标识，获取所述第一应用标识对应的至少一种备选网络策略；
当所述网络策略表中未记录所述第一应用标识，向所述控制器发送所述第一应用标识；
接收所述控制器发送的所述第一应用标识对应的至少一种备选网络策略。
需要说明的是，在查询网络策略表时，第一AP的网络策略表中可能没有记录第一应用标识，若没有记录该第一应用标识，第一AP向控制器发送该第一应用标识，控制接收该第一应用标识后，在控制器的需求格式表中进行查询，并将对应的至少一种备选网络策略发送给第一AP，以保证能够得到第一应用标识对应的至少一种备选网络策略。
可选地，所述应用标识为应用签名经过二进制转换得到的标识；当所述应用驱动网络为私有网络时，所述应用签名为应用名称；当所述应用驱动网络为公有网络时，所述应用签名由应用服务商标识和应用名称组成。
需要说明的是，应用服务商标识用于唯一标识提供应用的服务商，当应用驱动网络为公有网络时，应用签名由应用服务商标识和应用名称组成；当应用驱动网络为公有网络时，不同应用的应用签名以及QoE需求由该网络管理者定义，不需要应用服务商标识信息，即应用签名为应用名称。
可选地，在所述接收站点发送的第一应用的应用肖像之后，所述方法还包括：
向所述站点发送QoE需求响应，所述QoE需求响应用于表示所述AP接收到所述应用肖像。
可选地，需求格式表中记录的需求格式包括至少一组格式信息，每组所述格式信息包括：参数名称、数据类型和长度。
可选地，在所述获取所述第一应用对应的目标网络策略之后，所述方法还包括：
对所述第一应用执行所述目标网络策略。
可选地，所述接收所述第一AP所服务的站点发送的第一应用的应用肖像，包括：
接收所述站点发送的QoE需求帧，所述QoE需求帧携带有所述应用肖像；
其中，所述QoE需求帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111 或1111，所述QoE需求帧的帧实体的元素包括两组元素，第一组元素的元素身份标识ID的数值为17，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为18，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
可选地，所述向所述站点发送QoE需求响应，包括：
向所述站点发送QoE需求响应帧，所述QoE需求响应帧携带有所述QoE需求响应；
其中，所述QoE需求响应帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111或1111，所述QoE需求响应帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为19，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为20，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
需要说明的是，上述QoE需求帧和QoE需求响应帧为本申请实施例基于现有的802.11协议族，定义的新的管理帧，以保证能够实现QoE需求的定制化，继而有效地提升用户的QoE。
第二方面，本申请实施例提供了一种网络策略的获取设备，应用于应用驱动网络的第一接入点AP，所述应用驱动网络包括至少一个AP，所述第一AP为所述至少一个AP中的任一AP，所述设备用于执行上述第一方面提供的网络策略的获取方法。
上述第二方面提供的网络策略的获取设备可以包括：处理器和网络接口。
处理器包括一个或者一个以上处理核心。处理器通过运行软件程序以及模块，从而执行各种功能应用以及数据处理。处理器可以包括QoE管理模块。
网络接口可以为多个，该网络接口用于与其它存储设备或者网络设备进行通信。
可选的，网络策略的获取设备还包括存储器、总线等部件。其中，存储器与网络接口分别通过总线与处理器相连。
存储器可用于存储软件程序以及模块。具体的，存储器可存储操作系统、至少一个功能所需的应用程序模块。操作系统可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。QoE管理模块用于执行程序代码，以实现上述第一方面的相关步骤。
可选地，存储器可用于存储QoE需求格式表和网络策略表。
上述本申请第二方面所获得的技术效果与第一方面中对应的技术手段获得的技术效果近似，在这里不再赘述。
第三方面，本申请实施例提供了一种应用驱动网络，所述应用驱动网络包括：至少一个AP和至少一个站点，所述AP包括上述第二方面任一所述的网络策略的获取设备。
可选的，所述应用驱动网络还包括：控制器，所述控制器用于管理所述应用驱动网络中的AP。这样该应用驱动网络可以为集中式的应用驱动网络。
本申请实施例提供的网络策略的获取方法、设备及应用驱动网络，由于第一AP在站点的应用开启后，查询需求格式表，得到相应的目标需求格式，以解析该第一应用的第一QoE需求，从而获取相应的目标网络策略，因此，每个网络策略是针对不同应用的定制网络策略，实现QoE需求的定制化，细化服务粒度，实现服务的动态调整，从而有效提升用户QoE。
附图说明
图1-1是本申请实施例提供的一种网络策略的获取方法所涉及的应用驱动网络的网络环境的示意图；
图1-2是本申请实施例提供的另一种网络策略的获取方法所涉及的应用驱动网络的网络环境的示意图；
图2-1是本申请实施例提供的一种网络策略的获取方法的流程图；
图2-2是本申请实施例提供的一种传统的802.11的MAC头的帧格式的示意图；
图2-3是本申请实施例提供的一种QoE需求帧的帧控制的示意图；
图2-4是本申请实施例提供的一种QoE需求帧的帧实体的示意图；
图2-5是本申请实施例提供的一种QoE需求响应帧的帧控制的示意图；
图2-6是本申请实施例提供的一种QoE需求响应帧的帧实体的示意图；
图2-7是本申请实施例提供的一种第一AP获取第一应用标识对应的目标需求格式的方法的流程图；
图2-8是本申请实施例提供的一种第一AP主动发起第一AP的需求格式表的更新方法的流程图；
图2-9是本申请实施例提供的一种控制器主动发起第一AP的需求格式表的更新方法的流程图；
图2-10是本申请实施例提供的一种第一AP主动发起第一AP的网络策略表的更新方法的流程图；
图2-11是本申请实施例提供的一种控制器主动发起第一AP的网络策略表的更新方法的流程图；
图3是本申请实施例提供的一种网络策略的获取设备300的框图；
图4是本申请实施例提供的另一种网络策略的获取设备300的框图；
图5是本申请实施例提供的一种网络策略的获取设备中的第一获取模块302的框图；
图6是本申请实施例提供的又一种网络策略的获取设备300的框图；
图7是本申请实施例提供的一种网络策略的获取设备中的第二获取模块304的框图；
图8是本申请实施例提供的还一种网络策略的获取设备300的框图；
图9是本申请实施例提供的再一种网络策略的获取设备300的框图；
图10是本申请实施例提供的一种网络策略的获取设备20的框图；
图11是本申请实施例提供的一种网络策略的获取设备30的框图；
图12是本申请实施例提供的一种网络策略的获取设备40的框图。
具体实施方式
图1-1提供了本申请实施例提供的一种网络策略的获取方法所涉及的应用驱动网络0的网络环境，该应用驱动网络是一种能够根据不同业务类型和需求调整网络参数的网络。该应用驱动网络0包括至少一个AP01和至少一个站点(也称站点)02，每个AP01为至少一个站点02提供服务。
在该应用驱动网络中，站点可以在开启应用时，向服务于该站点的AP发送携带QoE需求的应用肖像，AP确定相应的需求格式来解析QoE需求，从而获取针对该应用的网络策 略。在本申请实施例中，网络策略为网络中业务或数据传输时所基于的策略，示例的，可以包括优先级调度，信道分配，移动性管理和网络选择等等。
其中，AP，也称之为无线访问接入点或热点等，是移动用户进入有线网络的接入点，主要部署于家庭、大楼内部以及园区内部，典型覆盖半径为几十米至上百米，当然，也可以部署于户外。AP相当于一个连接有线网络和无线网络的桥梁，其主要作用是将各个无线网络的客户端连接到一起，然后将无线网络接入有线网络中。具体地，AP可以是带有无线保真(英文：Wireless Fidelity；简称：WiFi)芯片的站点设备或者网络设备。可选地，AP可以为支持802.11ax制式的设备，进一步可选地，该AP可以为支持802.11n、802.11g、802.11b、802.11a及802.11ac等多种制式的设备。
STA可以是无线通讯芯片、无线传感器或无线通信站点，例如：移动电话、平板电脑、机顶盒、智能电视、智能可穿戴设备、车载通信设备和计算机。可选地，STA可以支持802.11ax制式，进一步可选地，该STA也可以支持802.11ac、802.11n、802.11g、802.11b及802.11a等多种制式。
图1-1提供的是一种非集中式的应用驱动网络，AP存储的需求格式和网络策略需要预先配置，可以由人工或其他专有装置定期更新，但是更新效率较低，为了方便各个AP的需求格式和网络策略的管理和更新，本申请实施例提供另一种网络策略的获取方法所涉及的应用驱动网络0的网络环境，如图1-2所示，该应用驱动网络0是一种集中式的应用驱动网络，相较于图1-1所示的非集中式应用驱动网络上，该集中式应用驱动网络0还可以包括控制器03，该控制器03用于管理应用驱动网络0中的AP01。该控制器03可以是本地控制器，也可以是云端(也称远端)控制器。本地控制器适用于企业网等私有网络，而云端控制器适用于公有网络，例如家庭网络，商场或超市中使用的无线网络。应用QoE需求和网络策略的映射表由控制器下发。可选的，控制器的一端通过通信接口与AP相连，该控制器可以下发需求格式表和网络策略表，需求格式表用于记录应用标识与需求格式的对应关系，网络策略表用于记录应用标识与网络策略的对应关系；控制器的另一端为应用服务商提供应用程序编程接口(英文：Application Programming Interface；简称：API)，由应用服务商更新需求格式表和网络策略表，以实现应用对应的网络策略的定制化。
由于应用驱动网络0包括至少一个AP，本申请实施例以第一AP为例进行说明，该第一AP为应用驱动网络0所包括的至少一个AP中的任一AP，假设该应用驱动网络0为图1-2所示的集中式的应用驱动网络，图2-1是根据一示例性实施例示出的一种网络策略的获取方法的流程图，如图2-1所示，该方法包括：
步骤201、站点在第一应用开启后获取应用肖像(英文：Application Profile)。
站点可安装的每个应用都携带有应用肖像，当站点开启第一应用后，站点会识别其应用肖像。站点识别得到的应用肖像通常包括：应用签名和QoE需求，应用签名用于唯一标识相应的应用。实际应用中，由于站点识别功能的限制或者应用未携带应用肖像，站点可能无法获取应用肖像，当站点无法获取应用肖像时，站点即结束动作。
在本申请实施例中，应用驱动网络可以为私有网络，也可以为公有网络。
当应用驱动网络为私有网络时，由于私有网络中的不同应用的应用签名通常为由该私有网络的管理者定义，因此，应用签名可以为应用名称，无需增加如应用服务商标识之类的标识来区分应用签名，示例的，当该私有网络为企业网络，相应的应用可以为企业应用， 则应用签名为应用名称即可，例如，该私有网络为“AA医药公司”的网络，相应的，该网络中的某一应用的应用名称为“AA医药”，则应用签名“AA医药”即可唯一标识该应用，该应用的签名为“AA医药”。
当应用驱动网络为公有网络时，为了对应用进行有效标识，其应用签名可以由应用服务商标识和应用名称组成。示例的，该应用签名的格式可以为“应用服务商标识(英文：venderID)_应用名称(英文：name)”以及应用服务商标识和应用名称均可以为除“_”之外的字符组成的字符串，具体内容可以由应用服务商定义，例如，应用：搜狐视频的应用服务商标识为“sohu”，应用名称为“video”，因此应用签名为“sohu_video”；又例如，应用：微信的应用服务商标识为“tencent”，应用名称为“wechat”，因此，应用签名为“tencent_wechat”；再例如，应用：qq的应用服务商标识为“tencent”，应用名称为“qq”，因此，应用签名为“tencent_qq”。
步骤202、站点向第一AP发送应用肖像。
由于应用驱动网络中传输的数据通常为二进制数据，而应用签名不是二进制数据，因此在应用肖像传输前，需要对其携带的应用签名进行相应的二进制转换，经过二进制转换后的应用签名称为应用标识，也称应用身份标识(英文：Identification；简称：ID)。并且，为了保证数据传输的安全性，该应用肖像在传输前需要进行加密，示例的，可以采用消息摘要算法第五版(英文：Message DigestAlgorithm；简称：MD5算法)进行加密和二进制转换，具体的，可以采用MD5算法将应用签名转化为128位二进制(占用128bits(中文：比特))数据，最终得到了加密且为二进制的应用标识。例如，搜狐视频的应用签名为“sohu_video”，经MD5算法加密得到应用标识为da73292b2b0351b1c5ce1ce7b275448c(此处以由十六进制表示的128比特加密数据为例进行说明)。
由上可知，第一应用发送的应用肖像可以包括：第一应用标识和第一QoE需求。该第一应用标识用于唯一标识该第一应用，该第一QoE需求为第一应用的QoE需求，该第一应用为站点可安装的应用中的任一应用。该应用可以是支持不同业务类型的应用，例如可以是站点管理应用等管理类应用，还可以是qq应用或微信应用等聊天应用，还可以是搜狐视频等视频类应用。
实际应用中，第一应用的应用肖像是通过站点和第一AP之间的通信接口上报至第一AP的。可选的，站点可以通过发送携带有应用肖像的QoE需求帧来向第一AP传输应用肖像。
需要说明的是，QoE需求在上述QoE需求帧中的长度在0-255bytes(中文：字节，简称：B)范围内，具体含义由应用服务商定义。例如某直播应用的QoE需求长度为8bytes，其中前4个bytes为浮点类型的平均意见得分(英文：mean opinion score；简称：MOS)值，后4个bytes为浮点类型的需求流畅度。
步骤203、第一AP向站点发送QoE需求响应，该QoE需求响应用于表示AP接收到应用肖像。
实际应用中，第一AP会周期性检测是否收到应用肖像，在接收到该应用肖像后向站点发送QoE需求响应，在未接收的应用肖像后继续进行检测。
示例的，第一AP检测是否收到应用肖像的检测周期为T，T可以为小于5分钟的时间，例如T＝5分钟，第一AP上可以设置定时器，通过该定时器触发该第一AP的周期性检测。
实际应用中，QoE需求响应是通过第一AP和站点之间的通信接口下发至站点的。可选的，第一AP可以通过发送携带有QoE需求响应的QoE需求响应帧来向站点传输QoE需求响应。也即是，第一AP向站点发送QoE需求响应帧，该QoE需求响应帧携带有QoE需求响应。
本申请实施例定义了一种QoE需求上报协议和相应的QoE管理帧结构，QoE管理帧是在802.11协议族中新定义的一种管理帧。QoE需求上报协议分为站点向AP发起QoE需求和AP对站点发起的QoE需求的响应，其具体过程可以参考上述步骤202和203。
802.11协议族的帧包含管理帧、控制帧以及数据帧。管理帧负责监督，主要用来加入或者退出无线网络以及处理接入点之间的关联的转移事宜。传统的802.11的媒体访问控制(英文：MediaAccess Control；简称：MAC)帧(也称为物理地址或硬件地址帧)的MAC头(英文：MAC Header)的格式可以如图2-2所示。该MAC头包括：帧控制(英文：Frame Control)、生存周期/标识(英文：Duration/ID)、地址(英文：Address)、序列控制(英文：Sequence Control)、帧实体(英文：Frame Body)和帧校验序列(英文：Frame Check Sequence；简称：FCS)，从帧控制到帧校验序列占用的长度分别为：2bytes、2bytes、6bytes、2bytes、0-2312bytes和4bytes。其中，帧控制包括：协议版本(英文：Protocol Version)、帧类型(英文：Type)和帧子类型(英文：Subtype)、向分配系统发送(英文：To DS)、分配系统发送(英文：From DS)、分片标志(英文：More Frag)、重传(英文：Retry)、省电模式(英文：Pwr Mgt)、更多数据(英文：More Data)、被保护帧标志(英文：Protected Frame)、序号(英文：Order)，协议版本到序号占用的长度分别为：2bits(中文：比特)、2bits、4bits、1bit、1bit、1bit、1bit、1bit、1bit、1bit和1bit。帧控制中的帧类型字段的数值为00时，代表该帧为管理帧，帧子类型决定管理帧的类型。管理帧的帧实体的数据携带站点相关信息，其元素(英文：element)分为长度固定(英文：fix field)元素和长度不固定元素，也称信息元素(information element)。
本申请实施例基于现有的802.11协议族，定义了新的管理帧。具体包括：QoE需求帧和QoE需求响应帧。由于传统的管理帧的帧实体的元素中，元素ID 17-31在802.11协议族未使用。因此，QoE需求帧和QoE需求响应帧分别如下：
如图2-3所示，QoE需求帧用于传输应用肖像，QoE需求帧的帧类型为管理帧，管理帧的帧子类型字段的数值为0111或1111(图2-3以0111为例进行说明)，参考图2-3，其帧控制的具体结构除帧子类型之外可以参考上述图2-2。进一步的，如图2-4所示，QoE需求帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为17，长度为X字节(图2-4中简称B)，携带的内容为应用标识，第二组元素的元素ID的数值为18，长度为N字节，携带的内容为QoE需求，X为1-255内的常数，N为1-255内的常数。
如图2-5所示，QoE需求响应帧的帧类型为管理帧，管理帧的帧子类型字段的数值为0111或1111(图2-5以1111为例进行说明)，参考图2-5，其帧控制的具体结构除帧子类型之外可以参考上述图2-2。进一步的，请参考图2-6，QoE需求响应帧的帧实体的结构可以和QoE需求帧的帧实体的结构相同，QoE需求响应帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为19，长度为X字节(图2-6中简称B)，携带的内容为应用标识，第二组元素的元素ID的数值为20，长度为N字节，携带的内容为QoE需求，X为1-255内的常数，N为1-255内的常数。
实际应用中，上述需求帧和需求响应帧的帧子类型字段的数值可以相同也可以不同，在帧子类型字段的数值相同时，可以设置需求帧和需求响应帧的元素的元素ID数值不同，以进行区分；在帧子类型的数值不同时，可以设置需求帧和需求响应帧的元素的元素ID数值相同或不同。
需要说明的是，本申请实施例中也可以新增应用层协议以进行需求帧或者需求响应帧的传输，或者新增802.11协议(类似于802.11e)以进行需求帧或者需求响应帧的传输。本申请实施例对此不作限定。
步骤204、第一AP获取第一应用标识对应的目标需求格式，目标需求格式用于表征第一应用中携带的内容的解析方式。
实际应用中，在集中式应用驱动网络中，由于控制器用于管理需求格式表，因此，在步骤202之前，第一AP还可以接收控制器发送的需求格式表以获取需求格式表，需求格式表用于记录应用标识与需求格式的对应关系。示例的，该需求格式表可以如表1所示，需求格式表中记录的需求格式包括至少一组格式信息，每组格式信息包括：参数名称、数据类型和长度，具体格式为(参数名称，数据类型，长度；参数名称，数据类型，长度......)。上述格式信息的组数是应用服务商预先设定的，且每个需求格式的长度可以根据具体使用场景定义。该参数名称是应用服务商指定的QoE参数的名称。例如，参数名称为字符串(英文：string)类型，数据类型可以为C语言中已知数据类型，长度单位为byte。如表1所示，以表1中第一行为例进行说明，假设搜狐视频的应用标识为da73292b2b0351b1c5ce1ce7b275448c，QoE需求涉及两个参数，分别为MOS值和时延要求，其中前4个bytes为float类型的MOS值，后4个bytes为float类型的时延(英文：delay)要求，则QoE需求格式为(“MOS”,float，4；“delay”,float，4)。该QoE需求格式中具体参数，由应用服务商和网络服务商协定完成，并且存储在第一AP中。
表1
Figure PCTCN2017107155-appb-000001
相应的，第一AP可以查询需求格式表，得到第一应用标识对应的目标需求格式。如图2-7所示，第一AP查询需求格式表，得到第一应用标识对应的目标需求格式的过程可以包括：
步骤2041、第一AP检测需求格式表中是否记录有第一应用标识。
步骤2042、当需求格式表中记录有第一应用标识，第一AP获取第一应用标识对应的目标需求格式。
示例的，假设第一应用为搜狐视频，第一应用标识为da73292b2b0351b1c5ce1ce7b275448c，查询表1可知，表1记录有第一应用标识，因此，可以获取该第一应用标识对应的目标应用需求格式：(“MOS”,float，4；“delay”,float，4)。
步骤2043、当需求格式表中未记录第一应用标识，第一AP向控制器发送第一应用的应用肖像。
步骤2044、控制器根据该应用肖像获取目标需求格式。
控制器中可以维护有多个需求格式表，每个需求格式表对应一个AP，记录应用标识与需求格式的对应关系；控制器也可以维护一需求格式总表，该表中记录控制器管理的所有AP所对应的应用标识与需求格式的对应关系。控制器通过应用肖像中携带的第一应用标识查询第一AP所对应的需求格式表，在该需求格式表中存在第一应用标识时，获取相应的目标需求格式。当控制器未查询到第一应用标识时，停止动作。
步骤2045、控制器向第一AP发送目标需求格式。
若控制器获取了目标需求格式，则向第一AP发送目标需求格式。
步骤205、第一AP采用目标需求格式解析第一QoE需求，得到第一QoE需求中的内容。
参考步骤2042，假设第一应用为搜狐视频，获取的目标应用需求格式：(“MOS”,float，4；“delay”,float，4)，则采用该目标应用需求格式对第一QoE需求解析得到应用需求的内容为(“MOS”，3.75，“delay”，100)，该应用需求表示搜狐视频的QoE需求存在两个指标，分别是MOS和delay，MOS的需求是3.72，最小delay需求为100毫秒(英文：ms)。
在本申请实施例中，第一AP解析得到第一QoE需求中的内容后，可以将该内容存储在存储组件中，示例的，可以以QoE需求表的形式进行存储，如表2所示，在该QoE需求表中记录了应用标识和QoE需求的内容的对应关系，以表2中第一行为例进行说明，可知应用标识为da73292b2b0351b1c5ce1ce7b275448c的应用对应的QoE需求内容为(“MOS”，3.75，“delay”，100)，表示MOS的需求是3.72，最小delay需求为100ms。根据该表可以便于执行相应的网络策略。
表2
Figure PCTCN2017107155-appb-000002
步骤206、第一AP根据第一应用标识和第一QoE需求中的内容，获取第一应用对应的目标网络策略。
实际应用中，在集中式应用驱动网络中，由于控制器用于管理网络策略表，因此，在步骤202之前，第一AP还可以接收控制器发送的网络策略表以获取网络策略表，网络策略表用于记录应用标识与网络策略的对应关系。该网络策略表中记录的网络策略，由应用服务商和网络服务商协定完成，并且存储在第一AP中。该网络策略表可以如表3所示，每个应用标识可以对应至少一个网络策略。
表3
Figure PCTCN2017107155-appb-000003
相应的，第一AP可以根据第一应用标识和第一QoE需求中的内容，获取第一应用对应的目标网络策略，具体的，第一AP可以查询网络策略表，得到第一应用标识对应的至少一种备选网络策略；在至少一种备选网络策略中确定与第一QoE需求中的内容相匹配的网络策略作为目标网络策略，该相匹配的策略是最大程度满足该QoE需求的策略。在实际应用中，在至少一种备选网络策略中确定与第一QoE需求中的内容相匹配的网络策略作为目标网络策略可以采用预设的评估算法，以评估得到最大程度满足该QoE需求的策略。
其中，查询网络策略表，得到第一应用标识对应的至少一种备选网络策略，的具体过程包括：检测网络策略表中是否记录有第一应用标识；当网络策略表中记录有第一应用标识，获取第一应用标识对应的至少一种备选网络策略；当网络策略表中未记录第一应用标识，向控制器发送第一应用标识；接收控制器发送的第一应用标识对应的至少一种备选网络策略。
示例的，由表2可知第一应用标识为da73292b2b0351b1c5ce1ce7b275448c的应用对应的QoE需求的内容为(“MOS”，3.75，“delay”，100)，采用第一应用标识查询表3可以得到至少一种备选网络策略：优先级调度策略，信道分配策略，移动性管理策略和网络选择策略。第一AP可以从这些备选的网络策略中选择最大程度满足该QoE需求(“MOS”，3.75，“delay”，100)的策略。假设在优先级调度策略中，优先级为1的业务的时延小于或者等于100ms，该优先级调度策略能够满足该QoE需求，采用预设的评估算法可以将该优先级调度策略确定为目标网络策略。
步骤207、第一AP对第一应用执行目标网络策略。
在本申请实施例中，第一AP对第一应用执行目标网络策略，也即是该目标网络策略所对应的调整粒度为应用，实际应用中，网络策略表中记录的每个网络策略都配置有其对应的执行方法，该执行方法可以记录在网络策略表中，也可以预先设置在其他位置，在确定了目标网络策略后，可以获取该目标网络策略对应的执行方法来执行该目标网络策略，例如，上述目标网络策略为优先级调度策略，其对应的执行方法为：调整该应用的优先级为1。相应的，第一AP即可按照该执行方法，将第一应用的优先级设置为1。
需要说明的是，由于在如图1-2所示的集中式的应用驱动网络中，需求格式表和网络策略表由控制器集中管理，因此，第一AP需要更新其对应的需求格式表和网络策略表，以进行网络策略的获取。
本申请实施例以以下两方面对需求格式表的更新过程进行具体说明。
第一方面，第一AP可以主动发起第一AP的需求格式表的更新，示例的，该更新过程可以在第一AP启动时执行，或者由第一AP周期性地发起。如图2-8所示，该更新过程如下：
步骤301、第一AP向控制器发送格式表更新请求，该格式表更新请求包括：第一AP的标识。
步骤302、控制器收到该格式表更新请求后，检查该控制器中是否存在与第一AP的标识对应的需求格式表。当该控制器中存在与第一AP的标识对应的需求格式表时，执行步骤303，当该控制器中不存在与第一AP的标识对应的需求格式表时，执行步骤306。
在本申请实施例中，控制器可以将控制器上整体的需求格式表发送给各个AP，但是由于每个AP管理应用驱动网络中的部分站点，为了减少各个AP的负载，各个AP只需要获得其相应的需求格式表即可，其相应的需求格式表，记录该AP所服务的终端的应用的需求格式。
步骤303、控制器获取第一AP的标识对应的需求格式表。执行步骤304。
控制器可以设置有AP标识与需求格式表的对应关系表，该对应关系表中记录控制器所管理的AP的标识，以及相应的需求格式表，控制器可以根据第一AP的标识查询该对应关系表，在该对应关系表中记录有该第一AP的标识时，获取相应的需求格式表。
步骤304、控制器向第一AP发送需求格式表。执行步骤305。
步骤305、第一AP在接收到需求格式表后，更新需求格式表。
步骤306、控制器向第一AP发送删除指示，该删除指示用于指示该控制器未记录第一AP的标识对应的需求格式表。执行步骤307。
当该对应关系表中未记录该第一AP的标识时，一方面，可能应用服务商未对该第一AP服务的站点配备需求格式表，另一方面，可能应用服务商未对该第一AP服务的站点的需求格式表进行记录。因此，控制器可以发送删除指示。实际应用中，控制器可以通过发送空白的需求格式表以达到指示删除的目的。
步骤307、第一AP在接收到删除指示后，删除第一AP的需求格式表。
实际应用中，若第一AP接收的是空白的需求格式表，则可以将相应的需求格式表设置为空表，也即是清除了表项中的所有内容，这种方式也可以认为是需求格式表的删除。
第二方面，控制器可以主动发起第一AP的需求格式表的更新。如图2-9所示，该更新过程如下：
步骤401、控制器在需求格式表更新后，向第一AP发送格式表更新请求，该格式表更新请求包括更新后的需求格式表。
示例的，应用服务商向网络服务商提供了新的需求格式定义时，控制器将该新的需求格式定义记录在需求格式表中，以实现该需求格式表的更新。
步骤402、第一AP在接收到格式表更新请求后，更新需求格式表。
需要说明的是，控制器还可以进行需求格式表的删除，例如，在控制器检测到某一需求格式表无效时，删除该需求格式表，并向第一AP发送删除指示，第一AP根据该删除指示删除需求格式表，实际应用中，控制器可以通过发送空白的需求格式表以达到指示删除的目的，相应的，第一AP可以将相应的需求格式表设置为空表，也即是清除了表项中的所有内容，这种方式也可以认为是需求格式表的删除。
本申请实施例以以下两方面对网络策略表的更新过程进行具体说明。
第一方面，第一AP可以主动发起第一AP的网络策略表的更新，示例的，该更新过程可以在第一AP启动时执行，或者由第一AP周期性地发起。如图2-10所示，该更新过程如下：
步骤501、第一AP向控制器发送网络策略表更新请求，该网络策略表更新请求包括：第一AP的标识。
步骤502、控制器收到该网络策略表更新请求后，检查该控制器中是否存在与第一AP的标识对应的网络策略表。当该控制器中存在与第一AP的标识对应的网络策略表时，执行步骤503，当该控制器中不存在与第一AP的标识对应的网络策略表时，执行步骤506。
在本申请实施例中，控制器可以将控制器上整体的网络策略表发送给各个AP，但是由于每个AP管理应用驱动网络中部分站点，为了减少各个AP的负载，各个AP只需要获得其相应的网络策略表即可，其相应的网络策略表，记录该AP所服务的终端的应用的网络策略。
步骤503、控制器获取第一AP的标识对应的网络策略表。执行步骤504。
控制器可以设置有AP标识与网络策略表的对应关系表，该对应关系表中记录控制器所管理的AP的标识，以及相应的网络策略表，控制器可以根据第一AP的标识查询该对应关系表，在该对应关系表中记录有该第一AP的标识时，获取相应的网络策略表。
步骤504、控制器向第一AP发送网络策略表。执行步骤505。
步骤505、第一AP在接收到网络策略表后，更新网络策略表。
步骤506、控制器向第一AP发送删除指示，该删除指示用于指示该控制器未记录第一AP的标识对应的网络策略表。执行步骤507。
当该对应关系表中未记录该第一AP的标识时，一方面，可能应用服务商未对该第一AP服务的站点配备网络策略表，另一方面，可能应用服务商未对该第一AP服务的站点的网络策略表进行记录。因此，控制器可以发送删除指示。实际应用中，控制器可以通过发送空白的网络策略表以达到指示删除的目的。
步骤507、第一AP在接收到删除指示后，删除第一AP的网络策略表。
实际应用中，若第一AP接收的是空白的网络策略表，则可以将相应的网络策略表设置为空表，也即是清除了表项中的所有内容，这种方式也可以认为是网络策略表的删除。
第二方面，控制器可以主动发起第一AP的网络策略表的更新。如图2-11所示，该更新过程如下：
步骤601、控制器在网络策略表更新后，向第一AP发送网络策略表更新请求，该网络策略表更新请求包括更新后的网络策略表。
示例的，应用服务商向网络服务商提供了新的网络策略定义时，控制器将该新的网络策略定义记录在网络策略表中，以实现该网络策略表的更新。
步骤602、第一AP在接收到网络策略表更新请求后，更新网络策略表。
需要说明的是，控制器还可以进行网络策略表的删除，例如，在控制器检测到某一网络策略表无效时，删除该网络策略表，并向第一AP发送删除指示，第一AP根据该删除指示删除网络策略表，实际应用中，控制器可以通过发送空白的网络策略表以达到指示删除的目的，相应的，第一AP可以将相应的网络策略表设置为空表，也即是清除了表项中的所 有内容，这种方式也可以认为是网络策略表的删除。
需要说明的是，本申请实施例提供的网络策略的获取方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本申请的保护范围之内，因此不再赘述。
综上所述，本申请实施例提供的网络策略的获取方法，由于第一AP在站点的应用开启后，查询需求格式表，得到相应的目标需求格式，以解析该第一应用的第一QoE需求，从而获取相应的目标网络策略，因此，每个网络策略是针对不同应用的定制网络策略，实现QoE需求的定制化，细化服务粒度，实现服务的动态调整，从而有效提升用户QoE。
QoE需求是指用户对应用或业务的质量和性能的需求，不同应用的QoE需求不尽相同。QoE反映用户使用应用的主观特性，很难有统一的量化指标，而在本申请实施例中QoE需求由应用服务商制定。即使相同的业务类型，例如视频，不同的应用服务商仍可制定不同的QoE需求参数。由于应用服务商可以针对不同应用定制不同的需求格式，以提供不同的网络策略。增加了QoE需求管理的灵活性。由于需求格式的可定制化，从而使得业务类型以及站点上报的QoE需求的参数具有良好的可扩展性。
图3是根据一示例性实施例示出的一种网络策略的获取设备300的框图，该网络策略的获取设备300应用于应用驱动网络的第一接入点AP，应用驱动网络包括至少一个AP，第一AP为至少一个AP中的任一AP，如图3所示，该网络策略的获取设备300可以包括：
第一接收模块301，用于接收第一AP所服务的站点发送的第一应用的应用肖像，应用肖像是站点在第一应用开启后发送给第一AP的，应用肖像包括：第一应用标识和第一QoE需求，第一应用为站点中安装的任一应用。
第一获取模块302，用于获取第一应用标识对应的目标需求格式，目标需求格式用于表征第一应用中携带的内容的解析方式。
处理模块303，用于采用目标需求格式解析第一QoE需求，得到第一QoE需求中的内容。
第二获取模块304，用于根据第一应用标识和第一QoE需求中的内容，获取第一应用对应的目标网络策略。
综上所述，本申请实施例提供的网络策略的获取设备，通过第一接收模块接收站点发送的第一应用的应用肖像，第一获取模块获取第一应用标识对应的目标需求格式，处理模块采用目标需求格式解析第一QoE需求，第二获取模块获取相应的第一应用对应的目标网络策略，因此，每个网络策略是针对不同应用的定制网络策略，继而实现QoE需求的定制化，细化服务粒度，实现服务的动态调整，从而有效提升用户QoE。
可选地，应用驱动网络包括控制器，控制器用于管理应用驱动网络中的AP。如图4所示，网络策略的获取设备300还可以包括：
第二接收模块305，用于接收控制器发送的需求格式表，需求格式表用于记录应用标识与需求格式的对应关系。
可选地，如图5所示，第一获取模块302，可以包括：
第一查询子模块3021，用于查询需求格式表，得到第一应用标识对应的目标需求格式。
可选地，该第一查询子模块3021，可以用于：
检测需求格式表中是否记录有第一应用标识。
当需求格式表中记录有第一应用标识，获取第一应用标识对应的目标需求格式。
当需求格式表中未记录第一应用标识，向控制器发送第一应用的应用肖像。
接收控制器发送的目标需求格式。
可选地，如图6所示，网络策略的获取设备300还可以包括：
第三接收模块306，用于接收控制器发送的网络策略表，网络策略表用于记录应用标识与网络策略的对应关系。
可选地，如图7所示，第二获取模块304，可以包括：
第二查询子模块3041，用于查询网络策略表，得到第一应用标识对应的至少一种备选网络策略。
确定子模块3042，用于在至少一种备选网络策略中确定与第一QoE需求中的内容相匹配的网络策略作为目标网络策略。
可选地，第二查询子模块3041，可以用于：
检测网络策略表中是否记录有第一应用标识。
当网络策略表中记录有第一应用标识，获取第一应用标识对应的至少一种备选网络策略。
当网络策略表中未记录第一应用标识，向控制器发送第一应用标识。
接收控制器发送的第一应用标识对应的至少一种备选网络策略。
可选地，应用标识为应用签名经过二进制转换得到的标识。
当应用驱动网络为私有网络时，应用签名为应用名称；当应用驱动网络为公有网络时，应用签名由应用服务商标识和应用名称组成。
可选地，如图8所示，网络策略的获取设备300还可以包括：
发送模块307，用于向站点发送QoE需求响应，QoE需求响应用于表示AP接收到应用肖像。
可选地，需求格式表中记录的需求格式包括至少一组格式信息，每组格式信息包括：参数名称、数据类型和长度。
可选地，如图9所示，网络策略的获取设备300还可以包括：
执行模块308，用于对第一应用执行目标网络策略。
可选地，第一接收模块301，用于：
接收站点发送的QoE需求帧，QoE需求帧携带有应用肖像。
其中，QoE需求帧的帧类型为管理帧，管理帧的帧子类型字段的数值为0111或1111，QoE需求帧的帧实体的元素包括两组元素，第一组元素的元素身份标识ID的数值为17，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为18，长度为N字节，携带的内容为QoE需求，X为1-255内的常数，N为1-255内的常数。
可选地，发送模块307，用于：
向站点发送QoE需求响应帧，QoE需求响应帧携带有QoE需求响应。
其中，QoE需求响应帧的帧类型为管理帧，管理帧的帧子类型字段的数值为0111或1111，QoE需求响应帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为19， 长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为20，长度为N字节，携带的内容为QoE需求，X为1-255内的常数，N为1-255内的常数。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的设备、模块和子模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
综上所述，本申请实施例提供的网络策略的获取设备，通过第一接收模块接收站点发送的第一应用的应用肖像，第一获取模块获取第一应用标识对应的目标需求格式，处理模块采用目标需求格式解析第一QoE需求，第二获取模块获取相应的第一应用对应的目标网络策略，因此，每个网络策略是针对不同应用的定制网络策略，继而实现QoE需求的定制化，细化服务粒度，实现服务的动态调整，从而有效提升用户QoE。
请参考图10，其示出了本申请示例性实施例涉及的一种网络策略的获取设备20的结构示意图，该网络策略的获取设备20可以包括：处理器22和网络接口24。
处理器22包括一个或者一个以上处理核心。处理器22通过运行软件程序以及模块，从而执行各种功能应用以及数据处理。
可选地，处理器22可以包括QoE管理模块222。
网络接口24可以为多个，该网络接口24用于与其它存储设备或者网络设备进行通信。
可选的，网络策略的获取设备20还包括存储器26、总线28等部件。其中，存储器26与网络接口24分别通过总线28与处理器22相连。
存储器26可用于存储软件程序以及模块。具体的，存储器26可存储操作系统262和至少一个功能所需的应用程序模块264。操作系统262可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
可选地，存储器可用于存储QoE需求格式表266和网络策略表268。
其中，该应用程序模块264可以包括：
接收单元2641，具有与第一接收模块301相同或相似的功能。
第一获取单元2642，具有与第一获取模块302相同或相似的功能。
处理单元2643，具有与处理模块303相同或相似的功能。
第二获取单元2644，具有与第二获取模块304相同或相似的功能。
QoE管理模块222可以执行上述接收单元2641至第二获取单元2644所对应的应用程序，以实现本申请实施例提供的网络策略的获取方法。
请参考图11，其示出了本申请示例性实施例涉及的一种网络策略的获取设备30的结构示意图，该网络策略的获取设备30可以包括：处理器32和网络接口34。
处理器32包括一个或者一个以上处理核心。处理器32通过运行软件程序以及模块，从而执行各种功能应用以及数据处理。
可选地，处理器32可以包括QoE管理模块322。
网络接口34可以为多个，该网络接口34用于与其它存储设备或者网络设备进行通信。
可选的，网络策略的获取设备30还包括存储器36、总线38等部件。其中，存储器36与网络接口34分别通过总线38与处理器32相连。
存储器36可用于存储软件程序以及模块。具体的，存储器36可存储操作系统362和 至少一个功能所需的应用程序模块364。操作系统362可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
可选地，存储器可用于存储QoE需求格式表366和网络策略表368。
QoE管理模块322可以执行应用程序模块364所对应的程序，以管理应用驱动网络中的AP。其具体执行的步骤可以参考上述步骤2044，步骤302-304，步骤306，步骤401，步骤502-504，步骤506，步骤601。
请参考图12，其示出了本申请示例性实施例涉及的一种网络策略的获取设备40的结构示意图，该网络策略的获取设备40可以包括：处理器42和网络接口44。
处理器42包括一个或者一个以上处理核心。处理器42通过运行软件程序以及模块，从而执行各种功能应用以及数据处理。
可选地，处理器42可以包括QoE管理模块422。
网络接口44可以为多个，该网络接口44用于与其它存储设备或者网络设备进行通信。
可选的，网络策略的获取设备40还包括存储器46、总线48等部件。其中，存储器46与网络接口44分别通过总线48与处理器42相连。
存储器46可用于存储软件程序以及模块。具体的，存储器46可存储操作系统462和至少一个功能所需的应用程序模块464。操作系统462可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
可选地，应用程序模块464中包括第一应用4641。
QoE管理模块422可以执行应用程序模块464所对应的代码，在第一应用4641启动后向第一AP发送的第一应用的应用肖像。其具体执行的步骤可以参考上述步骤201-202等。
本申请实施例提供了一种应用驱动网络，该应用驱动网络包括：至少一个AP和至少一个站点，该AP包括上述网络策略的获取设备300。
可选的，该应用驱动网络还包括：控制器，该控制器用于管理该应用驱动网络中的AP。这样该应用驱动网络可以为集中式的应用驱动网络。
本申请实施例提供了一种应用驱动网络，该应用驱动网络包括：至少一个AP和至少一个站点，该AP包括上述网络策略的获取设备20，该站点包括上述的网络策略的获取设备40。
可选的，该应用驱动网络还包括：控制器，该控制器用于管理该应用驱动网络中的AP。该控制器包括上述的网络策略的获取设备30。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (24)

  1. 一种网络策略的获取方法，其特征在于，应用于应用驱动网络的第一接入点AP，所述应用驱动网络包括至少一个AP，所述第一AP为所述至少一个AP中的任一AP，所述方法包括：
    接收所述第一AP所服务的站点发送的第一应用的应用肖像，所述应用肖像是站点在所述第一应用开启后发送给所述第一AP的，所述应用肖像包括：第一应用标识和第一体验质量QoE需求，所述第一应用为所述站点中安装的任一应用；
    获取所述第一应用标识对应的目标需求格式，所述目标需求格式用于表征所述第一应用中携带的内容的解析方式；
    采用所述目标需求格式解析所述第一QoE需求，得到所述第一QoE需求中的内容；
    根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略。
  2. 根据权利要求1所述的方法，其特征在于，所述应用驱动网络包括控制器，所述控制器用于管理所述应用驱动网络中的AP，
    在所述接收所述第一AP所服务的站点发送的第一应用的应用肖像之前，所述方法还包括：
    接收所述控制器发送的需求格式表，所述需求格式表用于记录应用标识与需求格式的对应关系；
    所述获取所述第一应用标识对应的目标需求格式，包括：
    查询所述需求格式表，得到所述第一应用标识对应的目标需求格式。
  3. 根据权利要求2所述的方法，其特征在于，所述查询所述需求格式表，得到所述第一应用标识对应的目标需求格式，包括：
    检测所述需求格式表中是否记录有所述第一应用标识；
    当所述需求格式表中记录有所述第一应用标识，获取所述第一应用标识对应的目标需求格式；
    当所述需求格式表中未记录所述第一应用标识，向所述控制器发送所述第一应用的应用肖像；
    接收所述控制器发送的所述目标需求格式。
  4. 根据权利要求2或3所述的方法，其特征在于，
    在所述接收所述第一AP所服务的站点发送的第一应用的应用肖像之前，所述方法还包括：
    接收所述控制器发送的网络策略表，所述网络策略表用于记录应用标识与网络策略的对应关系；
    所述根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略，包括：
    查询所述网络策略表，得到所述第一应用标识对应的至少一种备选网络策略；
    在所述至少一种备选网络策略中确定与所述第一QoE需求中的内容相匹配的网络策略作为所述目标网络策略。
  5. 根据权利要求4所述的方法，其特征在于，
    所述查询所述网络策略表，得到所述第一应用标识对应的至少一种备选网络策略，包括：
    检测所述网络策略表中是否记录有所述第一应用标识；
    当所述网络策略表中记录有所述第一应用标识，获取所述第一应用标识对应的至少一种备选网络策略；
    当所述网络策略表中未记录所述第一应用标识，向所述控制器发送所述第一应用标识；
    接收所述控制器发送的所述第一应用标识对应的至少一种备选网络策略。
  6. 根据权利要求1所述的方法，其特征在于，所述应用标识为应用签名经过二进制转换得到的标识；
    当所述应用驱动网络为私有网络时，所述应用签名为应用名称；当所述应用驱动网络为公有网络时，所述应用签名由应用服务商标识和应用名称组成。
  7. 根据权利要求1所述的方法，其特征在于，在所述接收站点发送的第一应用的应用肖像之后，所述方法还包括：
    向所述站点发送QoE需求响应，所述QoE需求响应用于表示所述AP接收到所述应用肖像。
  8. 根据权利要求2所述的方法，其特征在于，
    所述需求格式表中记录的需求格式包括至少一组格式信息，每组所述格式信息包括：参数名称、数据类型和长度。
  9. 根据权利要求1所述的方法，其特征在于，在所述获取所述第一应用对应的目标网络策略之后，所述方法还包括：
    对所述第一应用执行所述目标网络策略。
  10. 根据权利要求1所述的方法，其特征在于，
    所述接收所述第一AP所服务的站点发送的第一应用的应用肖像，包括：
    接收所述站点发送的QoE需求帧，所述QoE需求帧携带有所述应用肖像；
    其中，所述QoE需求帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111或1111，所述QoE需求帧的帧实体的元素包括两组元素，第一组元素的元素身份标识ID的数值为17，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为18，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
  11. 根据权利要求7所述的方法，其特征在于，
    所述向所述站点发送QoE需求响应，包括：
    向所述站点发送QoE需求响应帧，所述QoE需求响应帧携带有所述QoE需求响应；
    其中，所述QoE需求响应帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111或1111，所述QoE需求响应帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为19，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为20，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
  12. 一种网络策略的获取设备，其特征在于，应用于应用驱动网络的第一接入点AP，所述应用驱动网络包括至少一个AP，所述第一AP为所述至少一个AP中的任一AP，所述设备包括：
    第一接收模块，用于接收所述第一AP所服务的站点发送的第一应用的应用肖像，所述应用肖像是站点在所述第一应用开启后发送给所述第一AP的，所述应用肖像包括：第一应用标识和第一QoE需求，所述第一应用为所述站点中安装的任一应用；
    第一获取模块，用于获取所述第一应用标识对应的目标需求格式，所述目标需求格式用于表征所述第一应用中携带的内容的解析方式；
    处理模块，用于采用所述目标需求格式解析所述第一QoE需求，得到所述第一QoE需求中的内容；
    第二获取模块，用于根据所述第一应用标识和所述第一QoE需求中的内容，获取所述第一应用对应的目标网络策略。
  13. 根据权利要求12所述的设备，其特征在于，所述应用驱动网络包括控制器，所述控制器用于管理所述应用驱动网络中的AP，所述设备还包括：
    第二接收模块，用于接收所述控制器发送的需求格式表，所述需求格式表用于记录应用标识与需求格式的对应关系；
    所述第一获取模块，包括：
    第一查询子模块，用于查询所述需求格式表，得到所述第一应用标识对应的目标需求格式。
  14. 根据权利要求13所述的设备，其特征在于，所述第一查询子模块，用于：
    检测所述需求格式表中是否记录有所述第一应用标识；
    当所述需求格式表中记录有所述第一应用标识，获取所述第一应用标识对应的目标需求格式；
    当所述需求格式表中未记录所述第一应用标识，向所述控制器发送所述第一应用的应用肖像；
    接收所述控制器发送的所述目标需求格式。
  15. 根据权利要求13或14所述的设备，其特征在于，所述设备还包括：
    第三接收模块，用于接收所述控制器发送的网络策略表，所述网络策略表用于记录应用 标识与网络策略的对应关系；
    所述第二获取模块，包括：
    第二查询子模块，用于查询所述网络策略表，得到所述第一应用标识对应的至少一种备选网络策略；
    确定子模块，用于在所述至少一种备选网络策略中确定与所述第一QoE需求中的内容相匹配的网络策略作为所述目标网络策略。
  16. 根据权利要求15所述的设备，其特征在于，
    所述第二查询子模块，用于：
    检测所述网络策略表中是否记录有所述第一应用标识；
    当所述网络策略表中记录有所述第一应用标识，获取所述第一应用标识对应的至少一种备选网络策略；
    当所述网络策略表中未记录所述第一应用标识，向所述控制器发送所述第一应用标识；
    接收所述控制器发送的所述第一应用标识对应的至少一种备选网络策略。
  17. 根据权利要求12所述的设备，其特征在于，所述应用标识为应用签名经过二进制转换得到的标识；
    当所述应用驱动网络为私有网络时，所述应用签名为应用名称；当所述应用驱动网络为公有网络时，所述应用签名由应用服务商标识和应用名称组成。
  18. 根据权利要求12所述的设备，其特征在于，所述设备还包括：
    发送模块，用于向所述站点发送QoE需求响应，所述QoE需求响应用于表示所述AP接收到所述应用肖像。
  19. 根据权利要求13所述的设备，其特征在于，
    所述需求格式表中记录的需求格式包括至少一组格式信息，每组所述格式信息包括：参数名称、数据类型和长度。
  20. 根据权利要求12所述的设备，其特征在于，所述设备还包括：
    执行模块，用于对所述第一应用执行所述目标网络策略。
  21. 根据权利要求12所述的设备，其特征在于，
    所述第一接收模块，用于：
    接收所述站点发送的QoE需求帧，所述QoE需求帧携带有所述应用肖像；
    其中，所述QoE需求帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111或1111，所述QoE需求帧的帧实体的元素包括两组元素，第一组元素的元素身份标识ID的数值为17，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为18，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
  22. 根据权利要求18所述的设备，其特征在于，
    所述发送模块，用于：
    向所述站点发送QoE需求响应帧，所述QoE需求响应帧携带有所述QoE需求响应；
    其中，所述QoE需求响应帧的帧类型为管理帧，所述管理帧的帧子类型字段的数值为0111或1111，所述QoE需求响应帧的帧实体的元素包括两组元素，第一组元素的元素ID的数值为19，长度为X字节，携带的内容为应用标识，第二组元素的元素ID的数值为20，长度为N字节，携带的内容为QoE需求，所述X为1-255内的常数，所述N为1-255内的常数。
  23. 一种应用驱动网络，其特征在于，所述应用驱动网络包括：至少一个AP和至少一个站点，所述AP包括所述如权利要求12至22任一所述的网络策略的获取设备。
  24. 根据权利要求23所述的系统，其特征在于，所述应用驱动网络还包括：控制器，所述控制器用于管理所述应用驱动网络中的AP。
PCT/CN2017/107155 2016-11-25 2017-10-20 网络策略的获取方法、设备及应用驱动网络 WO2018095172A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611056710.1 2016-11-25
CN201611056710.1A CN108112023B (zh) 2016-11-25 2016-11-25 网络策略的获取方法、设备及应用驱动网络

Publications (1)

Publication Number Publication Date
WO2018095172A1 true WO2018095172A1 (zh) 2018-05-31

Family

ID=62195282

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107155 WO2018095172A1 (zh) 2016-11-25 2017-10-20 网络策略的获取方法、设备及应用驱动网络

Country Status (2)

Country Link
CN (1) CN108112023B (zh)
WO (1) WO2018095172A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104067588A (zh) * 2011-09-26 2014-09-24 高通股份有限公司 用于业务检测网络控制的系统和方法
WO2016096625A1 (en) * 2014-12-17 2016-06-23 Thomson Licensing Wlan user quality of experience control in a multi-access point environment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104067588A (zh) * 2011-09-26 2014-09-24 高通股份有限公司 用于业务检测网络控制的系统和方法
WO2016096625A1 (en) * 2014-12-17 2016-06-23 Thomson Licensing Wlan user quality of experience control in a multi-access point environment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GENG, YANG ET AL.: "QoE Assessment and Prediction Method for High-Definition Video Stream Using Image Damage Accumulation", IMAGE DETECTION AND ANALYSIS TECHNIQUE, 31 July 2016 (2016-07-31), XP011621682 *
KSENTINI, ADLEN ET AL.: "QoE-based energy conservation for VoIP over WLAN", 2012 IEEE WIRELESS COMMUNICATIONS AND NETWORKING CONFERENCE: MAC AND CROSS-LAYER DESIGN, 31 December 2012 (2012-12-31), XP055487460 *

Also Published As

Publication number Publication date
CN108112023A (zh) 2018-06-01
CN108112023B (zh) 2020-03-20

Similar Documents

Publication Publication Date Title
US11290932B2 (en) Communication method, access network device, and core network device
KR101526637B1 (ko) 무선 액세스 포인트에 의한 복수의 서비스 네트워크에 대한 지원의 애드버타이즈
WO2018205150A1 (zh) 网络切片选择策略更新方法、及装置
RU2520380C2 (ru) Способ и система для динамического согласования обслуживания с однородной защитной плоскостью контроля в беспроводной сети
WO2020020263A1 (zh) 一种数据收集方法、设备及系统
TWI430633B (zh) 在無線區域網路中與外部網路交互作用之程序及其訊息格式
US11388661B2 (en) Network slice configuration update
US9088904B2 (en) Bundled charging for over-the-top and hosted services in IP wireless networks
WO2021093438A1 (zh) 一种接入网络的方法及通信装置
WO2019062498A1 (zh) 获取特征参数的方法和装置
CN106465251B (zh) 利用存储的高层信息的系统和方法
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2020199761A1 (zh) 一种通信方法和装置
WO2016197809A2 (zh) 接入点切换方法及装置
WO2019233442A1 (zh) 一种终端能力的获取方法及装置、计算机存储介质
US8315600B2 (en) Method and device for setting user-side white list and paging user equipment
WO2015157981A1 (zh) 一种无线局域网用户侧设备及信息处理方法
WO2018095172A1 (zh) 网络策略的获取方法、设备及应用驱动网络
CN114691734B (zh) 缓存管控方法、装置、计算机可读介质及电子设备
WO2019136925A1 (zh) 一种数据传输方法及装置、计算机存储介质
RU2560817C2 (ru) Способ, система и связанное устройство для передачи информации типа услуги
WO2021169644A1 (zh) 家庭网关接入网络的方法和通信装置
US11184839B2 (en) Wireless dynamic file exchange
WO2019140650A1 (zh) 一种终端上报信息的方法及装置、计算机存储介质
WO2018126483A1 (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: 17874321

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: 17874321

Country of ref document: EP

Kind code of ref document: A1