WO2017101516A1 - 一种获取、下发应用信息的方法和设备 - Google Patents

一种获取、下发应用信息的方法和设备 Download PDF

Info

Publication number
WO2017101516A1
WO2017101516A1 PCT/CN2016/097707 CN2016097707W WO2017101516A1 WO 2017101516 A1 WO2017101516 A1 WO 2017101516A1 CN 2016097707 W CN2016097707 W CN 2016097707W WO 2017101516 A1 WO2017101516 A1 WO 2017101516A1
Authority
WO
WIPO (PCT)
Prior art keywords
application information
application
cme
management entity
response message
Prior art date
Application number
PCT/CN2016/097707
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 WO2017101516A1 publication Critical patent/WO2017101516A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method and an apparatus for acquiring and delivering information.
  • 5G networks need to provide a variety of services, such as virtual reality, low-cost large-scale machine communication and car networking V2X, all of which have different requirements for mobile networks including data transmission rate, delay, reliability and mobility.
  • 5G networks such as IMT2020, Metis and other organizations have proposed to support the following three services: xMBB: providing high-speed low-latency communication to provide improved quality of experience; M-MTC: providing scalable links for massive devices; U-MTC: Provides ultra-reliable and low-latency communication for network services.
  • xMBB providing high-speed low-latency communication to provide improved quality of experience
  • M-MTC providing scalable links for massive devices
  • U-MTC Provides ultra-reliable and low-latency communication for network services.
  • the applications built on these businesses will also be diverse in the future.
  • the application service provider's link requirements for the mobile network are also diverse.
  • the current wireless resource allocation strategy generally allocates user-level resources according to user types, service types, and quality of service requirements, such as Qos, and cannot be refined for different applications.
  • Service depth identification is proposed to identify the service to achieve the above objectives, but there are also problems in that the application service provider continuously introduces new services, resulting in untimely updates, low recognition accuracy, and low recognition efficiency.
  • a method of obtaining application information including:
  • the wireless node management entity RMN sends a request message for the application information to the central management entity CME, carrying the application name;
  • the RNM receives the response message sent by the CME, and acquires application information corresponding to the application name carried in the response message.
  • a method for delivering application information including:
  • the configuration message is sent to the RMN, and the application information list is carried;
  • the application information list is sent to the RNM by using the response message.
  • a method of obtaining application information including:
  • the central management entity CME sends a request message to the application service provider for the application information
  • the CME receives a response message sent by the application service provider, where the response message carries application information.
  • a method of obtaining application information including:
  • the wireless node management entity RMN sends a request message for the application information to the central management entity CME, carrying the application name;
  • the CME After receiving the request message, the CME sends a request message for the application information to the application service provider, and carries the application name;
  • the application service provider After receiving the request message, the application service provider sends a response message to the CME, and carries the application information corresponding to the application name;
  • the CME After receiving the response message, the CME sends a response message to the RMN, and carries the application information corresponding to the application name;
  • the RNM receives the response message sent by the CME, and acquires application information corresponding to the application name.
  • a wireless node management entity includes an application information acquiring module, where the application information acquiring module includes:
  • a requesting unit configured to send a request message to the central management entity CME, where the request message carries an application name;
  • the receiving unit is configured to receive the response message sent by the CME, and obtain the application information corresponding to the application name carried in the response message.
  • a central management entity which includes an application information delivery module, where the application information delivery module includes:
  • a receiving unit configured to receive a request message for application information sent by the wireless node management entity RNM, where the request message carries an application name;
  • An obtaining unit configured to obtain application information corresponding to the application name
  • the sending unit is configured to send the application information to the RNM by using a response message.
  • a central management entity includes an application information acquiring module, where the application information acquiring module includes:
  • a requesting unit configured to send a request message to the application service provider for the application information
  • the receiving unit is configured to receive the response message sent by the application service provider, obtain the application information carried in the response message, and save the application information.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the configuration message is sent to the RMN, and the application information list is carried; or the CME and the RNM are connected to the RNM, and the application information list sent by the RNM is received.
  • the request message sends a list of application information to the RNM through the response message.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the network device such as the wireless node management entity and the central management entity, can obtain accurate application information directly or indirectly from the application service provider, so that the wireless resource can be allocated according to the application requirement, and the application experience and the resource allocation efficiency are improved. .
  • 1 is an architectural diagram of a 5G network access side
  • FIG. 2 is a flowchart of a wireless node management entity acquiring application information according to an embodiment of the present invention
  • FIG. 3 is a block diagram of a wireless node management entity according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a list of application information delivered by a central management entity according to Embodiment 2 of the present invention.
  • FIG. 5 is another flowchart of sending a list of application information by a central management entity according to Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of sending application information by a central management entity according to Embodiment 2 of the present invention.
  • FIG. 7 is a flowchart of acquiring application information by a central management entity according to Embodiment 2 of the present invention.
  • FIG. 8 is a block diagram of a central management entity according to Embodiment 2 of the present invention.
  • FIG. 9 is a flowchart of acquiring application information according to Embodiment 3 of the present invention.
  • FIG. 10 is a signaling flowchart of obtaining an application information according to an application name according to an example of the present invention.
  • FIG. 11 is a flowchart of an example 2 wireless node management entity of the present invention acquiring application information from a message;
  • FIG. 12 is a signaling flowchart of an example three-center management entity of the present invention actively sending an application information list to a wireless node management entity;
  • FIG. 13 is a signaling flowchart of an example four-center management entity of the present invention transmitting a list of application information according to a request of a wireless node management entity;
  • FIG. 14 is a flow diagram of resource adjustment by an example wireless node management entity in accordance with application information in accordance with an embodiment of the present invention.
  • a 5G network is taken as an example.
  • the functions of the 5G access side are generally divided into several parts: a Central Management Entities (CME), and a Radio Node Management (RNM). Air Interface (AI Management) and Reliable Service Composition.
  • CME Central Management Entities
  • RPM Radio Node Management
  • AI Management Air Interface
  • Reliable Service Composition Reliable Service Composition
  • the application information includes information related to service data transmission provided by the application service provider.
  • application service providers such as QQ, WeChat and other instant messaging service providers can also provide services for IoT terminals. Provider, and so on.
  • the specific application corresponding to the specific application name does not care for the wireless node management entity, and the specific application classification is ultimately identified by the application service provider.
  • the wireless node management entity may allocate radio resources to the terminal according to the saved application information, thereby maximally utilizing the resources while ensuring the requirements of the service for transmission.
  • the application information may include one or more of the following information: service type, application protocol, service data size, whether there is downlink data, and the like.
  • the application name may include application URL information, such as mail.google.com, attachment.fbsbx.com, etc.;
  • the business type includes a session class, a stream class, an interaction class, and a background class;
  • the application protocol refers to FTP, POP3, HTTP/HTTPS.
  • the protocol can be optimized according to the type of the protocol;
  • the service data size includes the number of bytes of the service data and the duration; whether the downlink data indicates whether there is only uplink data, and the uplink and downlink radio resources are saved for only the reported service.
  • the method for obtaining application information in this embodiment includes:
  • Step 110 The wireless node management entity RMN sends a request message for the application information to the central management entity CME, carrying the application name.
  • the RN Before the RN sends the request message to the CME to the CME, the RN may obtain the application name from the uplink message sent by the terminal, and determine whether the application information corresponding to the application name is saved locally, if not saved. And sending a request message to the CME to the application information.
  • the RMN may obtain the application name from the uniform resource locator URL information of the uplink packet if the uplink packet is not a DNS packet of the domain name system: if the uplink packet is a DNS packet, The RMN may obtain the application name from the domain name information of the DNS packet.
  • the application name (or application identifier) is used to find application information, and the present invention does not impose any restrictions on the form of the application name.
  • Step 120 The RNM receives the response message sent by the CME, and acquires application information corresponding to the application name carried in the response message.
  • the RN may further include: the RMN acquiring the application information carried in the response message, and according to the application information Calculating a radio resource requirement of the terminal; and determining, by the RN, whether the allocated radio resource of the terminal satisfies the radio resource requirement, and if not, performing resource re-adjustment, and adjusting the radio by using an air interface entity Resources are assigned to the terminal.
  • the RNM can obtain application information corresponding to a specific application name from the CME, and thus is used for resource segmentation or re-adjustment.
  • the RNM can obtain a list of application information of these applications from the CME in advance to save it for subsequent use. specifically:
  • the application information list is obtained from the configuration message sent by the CME.
  • the RN and the CME After the connection between the RN and the CME, the RN and the CME actively send a request message to the CME, and obtain a list of application information from the response message sent by the CME.
  • the embodiment further provides a wireless node management entity.
  • the application information acquiring module 10 includes:
  • a requesting unit configured to send a request message to the central management entity CME, where the request message carries an application name;
  • the receiving unit is configured to receive the response message sent by the CME, and obtain the application information corresponding to the application name carried in the response message.
  • the application information may include one or more of the following information: a service type; an application protocol; a service data size; and whether there is downlink data.
  • the wireless node management entity further includes a decision module 20, the decision module 20 including:
  • the obtaining unit is configured to obtain an application name from an uplink packet sent by the terminal;
  • the determining unit is configured to determine whether the application information corresponding to the application name is saved locally, and if not, notify the information requesting module to send a request message for the application information to the CME.
  • the obtaining unit obtains the application name from the uplink packet sent by the terminal, including: the uplink packet is not a domain name system DNS packet, and the acquiring unit is configured from the uniform resource locator URL information of the uplink packet.
  • the uplink packet is not a domain name system DNS packet
  • the acquiring unit is configured from the uniform resource locator URL information of the uplink packet.
  • Obtaining the application name: or the uplink packet is a DNS packet
  • the acquiring unit acquires the application name from the domain name information of the DNS packet.
  • the wireless node management entity further includes a resource adjustment module 30, where the resource adjustment module 30 includes:
  • a computing unit configured to acquire the application information carried in the response message, and calculate a radio resource requirement of the terminal according to the application information
  • an adjusting unit configured to determine whether the allocated radio resource of the terminal satisfies the radio resource requirement, and if not, perform resource re-adjustment, and assign the adjusted radio resource to the terminal by using an air interface entity.
  • the wireless node management entity further includes an application information list obtaining module 40;
  • the application information list obtaining module 40 includes:
  • a requesting unit configured to send a request message to the CME to the CME after establishing a connection with the CME
  • the receiving unit is configured to receive a list of application information delivered by the CME by using a response message.
  • the application information list obtaining module 40 includes:
  • the receiving unit is configured to obtain a list of application information from a configuration message sent by the CME after establishing a connection with the CME.
  • the wireless node management entity further includes: a storage module 50 configured to save the acquired application information.
  • the embodiment provides the interface signaling for the wireless node management entity to obtain the application information from the central management entity, so that the wireless node management entity can obtain the accurate application information provided by the application service provider through the central management entity, and can be applied to the application.
  • This embodiment also provides a method for delivering application information by using a 5G network as an example.
  • the application information of this embodiment is the same as that of the first embodiment, and may include one or more of the following information: service type, application protocol, service data size, and whether there is downlink data.
  • the CME is configured to form an application information list for the most commonly used applications, and is sent to the RNM.
  • this embodiment is an active delivery mode, including:
  • Step 210 the central management entity CME and the wireless node management entity RMN establish a connection
  • Step 220 The CME actively sends a configuration message to the RRM, and carries a list of application information.
  • the application information list is delivered to the RN in the manner of requesting delivery, as shown in FIG. 5, including:
  • Step 310 the central management entity CME and the wireless node management entity RMN establish a connection
  • Step 320 After receiving the request message for the application information list sent by the RNM, the CME sends the application information list to the RNM by using the response message.
  • the CME also delivers specific application information to the RNM for the request of the RNM. As shown in Figure 6, it includes:
  • Step 410 The CME receives a request message for application information sent by the RNM, where the request message carries an application name.
  • Step 420 The CME obtains application information corresponding to the application name, and sends the application information to the RNM by using a response message.
  • the CME obtains the application information corresponding to the application name, including: the CME obtains the application information from a local application information list; or the CME sends the application to the application service provider.
  • the request message of the information is obtained from the response message sent by the application service provider.
  • This embodiment further provides a method for a CME to obtain application information from an application service provider, as shown in FIG. 7, including:
  • Step 510 The central management entity CME sends a request message for application information to the application service provider.
  • the request message in this step may be specific to the application information.
  • the request message carries the application name, that is, the application information corresponding to the application name is requested.
  • the request message in this step may also be for the application information list, and may be indicated by the message type or the information unit agreed in the message.
  • Step 520 The CME receives a response message sent by the application service provider, where the response message carries application information.
  • the application information carried in the response message sent by the application service provider is the application information corresponding to the application name; the request message is a request message to the application information list, and the application service provides The application information carried in the response message sent by the quotient is a list of application information.
  • These application information lists can be composed of some commonly used application information.
  • the embodiment further provides a central management entity, including an application information sending module 70 and an application information acquiring module 80, as shown in FIG. 8.
  • the application information sending module 80 includes:
  • a receiving unit configured to receive the application information sent by the wireless node management entity RMN a request message, where the request message carries an application name;
  • An obtaining unit configured to obtain application information corresponding to the application name
  • the sending unit is configured to send the application information to the RNM by using a response message.
  • the acquiring, by the acquiring unit, the application information corresponding to the application name the acquiring unit: acquiring the application information from a local application information list; or sending the application information to an application service provider
  • the request message acquires the application information from a response message sent by the application service provider.
  • the application information obtaining module 90 includes:
  • a requesting unit configured to send a request message to the application service provider for the application information
  • the receiving unit is configured to receive the response message sent by the application service provider, obtain the application information carried in the response message, and save the application information.
  • the request message sent by the requesting unit carries an application name
  • the application information carried in the response message received by the receiving unit is application information corresponding to the application name
  • the request message sent by the requesting unit is a request message to the application information list, and the application information carried in the response message received by the receiving unit is an application information list.
  • the central management entity further includes: an application information list sending module 90, configured to: after establishing a connection with the RMN, actively sending a configuration message to the RRM, carrying an application information list; or setting a connection with the RMN After receiving the request message for the application information list sent by the RNM, the application information list is sent to the RNM by using the response message.
  • an application information list sending module 90 configured to: after establishing a connection with the RMN, actively sending a configuration message to the RRM, carrying an application information list; or setting a connection with the RMN After receiving the request message for the application information list sent by the RNM, the application information list is sent to the RNM by using the response message.
  • the embodiment provides that the central management entity sends the application information to the wireless node management entity, and the central management entity obtains the interface signaling of the application information from the application service provider, so that the application information provided by the application service provider can be sent through the central management entity. Send to the wireless node management entity. Therefore, the wireless node management entity can utilize the accurate application information to allocate resources to the terminal, thereby improving the application experience and resource allocation efficiency.
  • This embodiment provides a signaling flow for the RNM to obtain application information provided by the application service provider through the CME. Assuming that the application information of the RNM request is not saved on the CME, the corresponding process is as shown in FIG. 9, including:
  • Step 610 The wireless node management entity (RNM) sends a request message for the application information to the central management entity CME, carrying the application name.
  • RPM wireless node management entity
  • Step 620 After receiving the request message, the CME sends a request message for the application information to the application service provider, and carries the application name.
  • Step 630 After receiving the request message, the application service provider sends a response message to the CME, and carries the application information corresponding to the application name.
  • Step 640 After receiving the response message, the CME sends a response message to the RMN, and carries the application information corresponding to the application name.
  • Step 650 The RNM receives the response message sent by the CME, and acquires application information corresponding to the application name.
  • This example provides the signaling flow of application information acquisition, as shown in Figure 10, including:
  • Step S102 The central management entity delivers the application information list to the wireless node management entity.
  • the central management entity only delivers a list of application information consisting of basic or commonly used application information to the wireless node management entity, such as The message is delivered through the application information list configuration. If the wireless node management entity discovers the new application name, the application information corresponding to the application name is obtained from the central management entity.
  • Step S104 The terminal sends uplink data (such as an uplink packet) to the wireless management entity, and carries Application Name;
  • Step S106 The wireless node management entity acquires an application name from the uplink packet.
  • Step S108 The wireless node management entity determines whether to initiate an application information request.
  • the wireless node management entity may send a request message for the application information if the application information corresponding to the application name is not locally searched.
  • Step S110 When needed, the wireless node management entity sends an application information request message to the central management entity, carrying the application name;
  • Step S112 When the central management entity does not save the application information corresponding to the application name, the central management entity sends an application information request to the application service provider.
  • Step S114 The central management entity receives the application information response message sent by the application service provider, and saves the application information corresponding to the application name carried therein;
  • Step S116 The central management entity responds to the request message of the wireless node management entity, and sends an application information response message to the wireless node management entity, and carries the application information corresponding to the application name;
  • Step S118 The wireless node management entity obtains the application information corresponding to the application name from the response message of the application information, determines whether the resource re-adjustment needs to be performed on the terminal, and sends a radio resource assignment message to the terminal side if necessary.
  • the central management entity maintains the service application information, is responsible for obtaining the application name and corresponding application information from the application service provider, and sends the application information to the wireless node management entity in response to the application information request message.
  • the wireless node management entity stores application information acquired by the central management entity for use as an allocation policy input when the wireless resource is allocated.
  • This example provides a process for a wireless node management entity to obtain an application name from a mobile phone upstream message. As shown in Figure 11, the process includes:
  • Step S202 The wireless node management entity obtains the report message of the mobile phone, and solves the message. To determine whether there is URL information, if it exists, step S206 is performed, if the URL information is not found, step S204 is performed;
  • Step S204 The packet is further parsed to determine whether the packet is a Domain Name System (DNS) message. If the packet is a DNS packet, step S206 is performed. Otherwise, the packet is directly terminated.
  • DNS Domain Name System
  • Step S206 The wireless node management entity acquires the application name and ends.
  • the URL information can be directly applied to the application name of the reported packet.
  • the present invention may also use other information in the message that can be used to search for application information as an application name. If the packet is a DNS packet, the specific content of the DNS packet is parsed, and the application name of the reported packet is obtained, for example, the domain name information is used as the application name, and the like.
  • This example provides a signaling flow for a wireless node management entity to obtain application information from a central management entity. As shown in Figure 12, it includes:
  • Step S302 The wireless node management entity and the central management entity perform the power-on handshake.
  • Step S304 The central management entity delivers an application information list configuration message to the wireless node management entity.
  • Step S306 The wireless node management entity sends an application information list configuration response message to the central management entity.
  • the central management entity actively delivers the application information list to the wireless node management entity, and the application information includes basic or commonly used application information, which may be specified by the central management entity or the application service provider.
  • This example is a signaling flow in which a wireless node management entity acquires application information from a central management entity. As shown in Figure 13, it includes:
  • Step S402 The wireless node management entity and the central management entity perform the power-on handshake.
  • Step S404 The wireless node management entity actively initiates an application information list request message to the central management entity.
  • Step S406 The central management entity sends an application information list response message to the wireless node management entity, and the wireless node management entity saves the application information list in the response message.
  • the wireless node management entity actively obtains the application information list from the central management entity.
  • This example is a signaling procedure for a radio node management entity to perform resource adjustment according to application information. As shown in FIG. 14, the method includes:
  • Step S502 The wireless node management entity obtains application information according to the application name.
  • Step S504 The wireless node management entity calculates the radio resource requirement of the terminal according to the application information, and compares with the allocated radio resources of the terminal, according to the application information, considering the terminal capability, the cell load, the cell interference, and the like. If the allocated radio resources of the terminal cannot meet the calculated radio resource requirements, the resource re-adjustment needs to be performed; if the allocated radio resources exceed the radio resource requirements, the existing radio resources may be maintained, and even the deferred service may be performed. The operation, such as delaying software updates when busy.
  • the foregoing application information includes, but is not limited to, information including a service type, an application protocol, a service data size, and downlink data.
  • a cell type such as a business cell, an entertainment cell, etc.
  • a service type may be considered.
  • Step S506 If re-adjustment is required to meet the new radio resource requirement, the radio node management entity assigns the adjusted and latest radio resource to the terminal through the air interface entity.
  • the service type is finally identified by the application service provider and the application information is given, and the wireless node management can accurately obtain the application from the application service provider.
  • Information targeted at the needs of the application Optimize the allocation of wireless resources to improve the application experience and resource allocation efficiency.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the network device such as the wireless node management entity and the central management entity, can obtain accurate application information directly or indirectly from the application service provider, so that the wireless resource can be allocated according to the application requirement, and the application experience and resource allocation efficiency are improved. Effect.

Abstract

一种获取、下发应用信息的方法和设备，所述获取应用信息的方法包括：无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；所述RNM接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。所述下发应用信息的方法包括：CME和RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者，所述CME和RNM建立连接后，如接收到所述RNM发送的对应用信息列表的请求消息，则通过响应消息向所述RNM下发应用信息列表。本申请的RNM、CME可以直接或间接地从应用服务提供商获取准确的应用信息，针对应用的需求分配无线资源。

Description

一种获取、下发应用信息的方法和设备 技术领域
本发明涉及移动通信领域，尤其涉及一种获取、下发信息的方法和设备。
背景技术
随着未来移动通讯的发展，用户的需求越来越广泛，网络需求已经从人的需求，扩展到万物互联。5G网络需要提供多样化的服务，如虚拟现实，低成本大规模机器通信和车联网V2X等，所有这些服务对移动网络包括数据传输速率、延迟、可靠性和移动性等方面提出了不同需求。
5G网络在如IMT2020，Metis等组织提出需要支持如下3种业务：xMBB：提供高速低时延通讯，提供改进的体验质量；M-MTC：为海量的设备提供可扩展的链接；U-MTC：为网络服务提供超可靠和低时延通讯。建立在这些业务上的应用未来也将会是多种多样的。同时，为保证用户体验，应用服务提供商对移动网络的链路要求也是多样的。
在移动通信系统中，无线资源的分配和使用是一个非常重要的组成部分。如何最大化地利用无线资源是资源管理的不懈追求。现在的无线资源分配策略一般都是根据用户类型、业务类型和服务质量要求Qos等进行用户级资源分配，对不同应用不能做到精细化运作。业务深度识别被提议用于对业务进行识别以达到上述目的，但也存在着应用服务提供商不断推出新的业务导致更新不及时、识别准确率不高，识别效率低等问题。
发明内容
有鉴于此，本发明实施例提供了以下技术方案。
一种获取应用信息的方法，包括：
无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
所述RNM接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
一种下发应用信息的方法，包括：
中心管理实体CME和无线节点管理实体RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者
所述CME和RNM建立连接后，如接收到所述RNM发送的对应用信息列表的请求消息，则通过响应消息向所述RNM下发应用信息列表。
一种获取应用信息的方法，包括：
中心管理实体CME向应用服务提供商发送对应用信息的请求消息；
所述CME接收所述应用服务提供商发送的响应消息，所述响应消息中携带应用信息。
一种获取应用信息的方法，包括：
无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
所述CME收到所述请求消息后，向应用服务提供商发送对应用信息的请求消息，携带所述应用名称；
所述应用服务提供商收到所述请求消息后，向所述CME发送响应消息，携带所述应用名称对应的应用信息；
所述CME收到所述响应消息后，向所述RNM发送响应消息，携带所述应用名称对应的应用信息；
所述RNM接收所述CME发送的响应消息，获取所述应用名称对应的应用信息。
一种无线节点管理实体，其中，包括应用信息获取模块，所述应用信息获取模块包括：
请求单元，设置为向中心管理实体CME发送对应用信息的请求消息，所述请求消息中携带应用名称；
接收单元，设置为接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
一种中心管理实体，其中，包括应用信息下发模块，所述应用信息下发模块包括：
接收单元，设置为接收无线节点管理实体RNM发送的对应用信息的请求消息，所述请求消息中携带应用名称；
获取单元，设置为获取所述应用名称对应的应用信息；
下发单元，设置为将所述应用信息通过响应消息下发给所述RNM。
一种中心管理实体，其中，包括应用信息获取模块，所述应用信息获取模块包括：
请求单元，设置为向应用服务提供商发送对应用信息的请求消息；
接收单元，设置为接收所述应用服务提供商发送的响应消息，获取所述响应消息中携带的应用信息并保存。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
向中心管理实体CME发送对应用信息的请求消息，携带应用名称；接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
中心管理实体CME和无线节点管理实体RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者所述CME和RNM建立连接后，如接收到所述RNM发送的对应用信息列表的请求消息，则通过响应消息向所述RNM下发应用信息列表。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
向应用服务提供商发送对应用信息的请求消息；接收所述应用服务提供商发送的响应消息，所述响应消息中携带应用信息。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
向中心管理实体CME发送对应用信息的请求消息，携带应用名称；收到所述请求消息后，向应用服务提供商发送对应用信息的请求消息，携带所述应用名称；提供商收到所述请求消息后，向所述CME发送响应消息，携带所述应用名称对应的应用信息；收到所述响应消息后，向所述RNM发送响应消息，携带所述应用名称对应的应用信息；接收所述CME发送的响应消息，获取所述应用名称对应的应用信息。
通过上述方案，无线节点管理实体、中心管理实体等网络设备可以直接或间接地从应用服务提供商获取准确的应用信息，从而可以针对应用的需求分配无线资源，提升应用体验和资源分配效率的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是5G网络接入侧的架构图；
图2是本发明实施例一无线节点管理实体获取应用信息的流程图；
图3是本发明实施例一无线节点管理实体的模块图；
图4是本发明实施例二中心管理实体下发应用信息列表的流程图；
图5是本发明实施例二中心管理实体下发应用信息列表的另一流程图；
图6是本发明实施例二中心管理实体下发应用信息的流程图；
图7是本发明实施例二中心管理实体获取应用信息的流程图；
图8是本发明实施例二中心管理实体的模块图；
图9是本发明实施例三获取应用信息的流程图；
图10是本发明示例一根据应用名称获取应用信息的信令流程图；
图11是本发明示例二无线节点管理实体从报文中获取应用信息的流程图；
图12是本发明示例三中心管理实体主动向无线节点管理实体下发应用信息列表的信令流程图；
图13是本发明示例四中心管理实体根据无线节点管理实体的请求下发应用信息列表的信令流程图；
图14是根据本发明示例五无线节点管理实体根据应用信息进行资源调整的流程图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚明白，下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
实施例一
本实施例以5G网络为例，如图1所示，5G接入侧的功能大体分为几个部分：中心管理实体(CME，Central Management Entities)，无线节点管理(RNM：Radio Node Management)、空中接口(AI Management)和可信任的服务组件(Reliable Service Composition)。
本实施例提供一种获取应用信息的方法。本申请中，应用信息包括应用服务提供商提供的与业务数据传输相关的信息。这里的应用服务提供商如QQ、微信等即时通信服务的提供商，也可以是为物联网终端提供服务 的提供商，等等。具体应用名称对应的具体应用，无线节点管理实体不关心，具体的应用分类最终由应用服务提供商负责识别。但无线节点管理实体可以根据保存的应用信息，为终端分配无线资源，从而在保证业务对传输的要求的前提下，最大化地利用资源。
应用信息可以包括以下信息中的一种或多种：业务类型，应用协议，业务数据大小，是否有下行数据等。其中，应用名称可以包括应用网址信息，如mail.google.com,attachment.fbsbx.com等；业务类型包括会话类、流类、交互类、背景类；应用协议是指FTP、POP3、HTTP/HTTPS等协议，可以根据协议类型进行优化调度；业务数据大小包括业务数据字节数与持续时间；是否存在下行数据是指是否只有上行数据，对只有上报类业务节省上下行无线资源。
如图2所示，本实施例获取应用信息的方法包括：
步骤110，无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
本步骤RNM向CME发送对应用信息的请求消息之前，还可以包括：所述RNM从终端发送的上行报文中获取应用名称，判断本地是否保存有所述应用名称对应的应用信息，如没有保存，则向所述CME发送对应用信息的请求消息。其中，如果所述上行报文非域名系统DNS报文，所述RNM可以从所述上行报文的统一资源定位符URL信息中获取所述应用名称：如果所述上行报文为DNS报文，所述RNM可以从所述DNS报文的域名信息中获取所述应用名称。应用名称(或称为应用标识)用于查找应用信息，对于应用名称的形式，本发明不做任何限制，
步骤120，所述RNM接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
本步骤RNM接收所述CME发送的响应消息之后，还可以包括：所述RNM获取所述响应消息中携带的所述应用信息，并根据所述应用信息 计算所述终端的无线资源需求；及，所述RNM判断所述终端已分配的无线资源是否满足所述无线资源需求，如不满足，则进行资源重调整，通过空中接口实体将调整后的无线资源指派给所述终端。
通过上述流程，RNM可以从CME中获取到特定应用名称对应的应用信息，从而用于资源分段或重调整。
对于一些基本的、常用的应用，RNM可以预先从CME获取这些应用的应用信息列表，以保存下来方便后续使用。具体地：
所述RNM和CME建立连接后，从所述CME主动发送的配置消息中获取应用信息列表；和/或
所述RNM和CME建立连接后，主动向所述CME发送对应用信息列表的请求消息，从所述CME发送的响应消息中获取应用信息列表。
本实施例还提供了一种无线节点管理实体，如图3所示，包括应用信息获取模块10，所述应用信息获取模块10包括：
请求单元，设置为向中心管理实体CME发送对应用信息的请求消息，所述请求消息中携带应用名称；
接收单元，设置为接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
所述应用信息可以包括以下信息中的一种或多种：业务类型；应用协议；业务数据大小；及，是否有下行数据。
可选地，
所述无线节点管理实体还包括决策模块20，所述决策模块20包括：
获取单元，设置为从终端发送的上行报文中获取应用名称；
决策单元，设置为判断本地是否保存有所述应用名称对应的应用信息，如没有，则通知所述信息请求模块向所述CME发送对应用信息的请求消息。
其中，所述获取单元从终端发送的上行报文中获取应用名称，包括：所述上行报文非域名系统DNS报文，所述获取单元从所述上行报文的统一资源定位符URL信息中获取所述应用名称：或者，所述上行报文为DNS报文，所述获取单元从所述DNS报文的域名信息中获取所述应用名称。
可选地，
所述无线节点管理实体还包括资源调整模块30，所述资源调整模块30包括：
计算单元，设置为获取所述响应消息中携带的所述应用信息，根据所述应用信息计算所述终端的无线资源需求；及
调整单元，设置为判断所述终端已分配的无线资源是否满足所述无线资源需求，如不满足，则进行资源重调整，通过空中接口实体将调整后的无线资源指派给所述终端。
可选地，
所述无线节点管理实体还包括应用信息列表获取模块40；
所述应用信息列表获取模块40包括：
请求单元，设置为与CME建立连接后，主动向所述CME发送对应用信息列表的请求消息；及
接收单元，设置为接收所述CME通过响应消息下发的应用信息列表。
或者，所述应用信息列表获取模块40包括：
接收单元，设置为与CME建立连接后，从所述CME主动发送的配置消息中获取应用信息列表。
可选地，
所述无线节点管理实体还包括：存储模块50，设置为保存获取的应用信息。
本实施例提供了无线节点管理实体从中心管理实体之间获取应用信息的接口信令，使得无线节点管理实体可以通过中心管理实体获取应用服务提供商提供的准确的应用信息，并可以针对应用的需求分配无线资源，提升应用体验和资源分配效率的效果。
实施例二
本实施例也以5G网络为例，提供一种下发应用信息的方法。本实施例的应用信息和实施例一相同，可以包括以下信息中的一种或多种：业务类型、应用协议、业务数据大小，及是否有下行数据。
本实施例中，CME针对一些最常用的应用，将其应用信息组成应用信息列表，下发给RNM。
如图4所示，本实施例为主动下发方式，包括：
步骤210，中心管理实体CME和无线节点管理实体RNM建立连接；
本步骤中，CME与RNM上电、握手完成后建立连接。
步骤220，所述CME主动向所述RNM发送配置消息，携带应用信息列表。
在另一实施例，采用请求下发的方式向RNM下发应用信息列表，如图5所示，包括：
步骤310，中心管理实体CME和无线节点管理实体RNM建立连接；
步骤320，所述CME接收到所述RNM发送的对应用信息列表的请求消息后，通过响应消息向所述RNM下发应用信息列表。
本实施例中，CME还针对RNM的请求，下发特定的应用信息给RNM。如图6所示，包括：
步骤410，CME接收所述RNM发送的对应用信息的请求消息，所述请求消息中携带应用名称；
步骤420，所述CME获取所述应用名称对应的应用信息，将所述应用信息通过响应消息下发给所述RNM。
本步骤中，所述CME获取所述应用名称对应的应用信息，包括：所述CME从本地的应用信息列表中获取所述应用信息；或者，所述CME向应用服务提供商发送对所述应用信息的请求消息，从所述应用服务提供商发送的响应消息中获取所述应用信息。
本实施例还提供了一种CME从应用服务提供商获取应用信息的方法，如图7所示，包括：
步骤510，中心管理实体CME向应用服务提供商发送对应用信息的请求消息；
本步骤中的请求消息可以是针对特定应用信息的，此时，所述请求消息中携带有应用名称，即请求所述应用名称对应的应用信息。本步骤中的请求消息也可以是针对应用信息列表的，可以通过消息类型或消息中约定的信息单元来指示。
步骤520，所述CME接收所述应用服务提供商发送的响应消息，所述响应消息中携带应用信息。
所述请求消息中携带有应用名称时，应用服务提供商发送的响应消息中携带的应用信息为所述应用名称对应的应用信息；所述请求消息为对应用信息列表的请求消息，应用服务提供商发送的响应消息中携带的应用信息为应用信息列表。这些应用信息列表可以由一些常用的应用信息组成。
本实施例还提供了一种中心管理实体，包括应用信息下发模块70和应用信息获取模块80，如图8所示。
所述应用信息下发模块80包括：
接收单元，设置为接收无线节点管理实体RNM发送的对应用信息的 请求消息，所述请求消息中携带应用名称；
获取单元，设置为获取所述应用名称对应的应用信息；
下发单元，设置为将所述应用信息通过响应消息下发给所述RNM。
可选地，所述获取单元获取所述应用名称对应的应用信息，包括：所述获取单元从本地的应用信息列表中获取所述应用信息；或者，向应用服务提供商发送对所述应用信息的请求消息，从所述应用服务提供商发送的响应消息中获取所述应用信息。
所述应用信息获取模块90包括：
请求单元，设置为向应用服务提供商发送对应用信息的请求消息；
接收单元，设置为接收所述应用服务提供商发送的响应消息，获取所述响应消息中携带的应用信息并保存。
可选地，所述请求单元发送的请求消息中携带有应用名称，所述接收单元接收的响应消息中携带的应用信息为所述应用名称对应的应用信息；或者
所述请求单元发送的请求消息为对应用信息列表的请求消息，所述接收单元接收的所述响应消息中携带的应用信息为应用信息列表。
可选地，所述中心管理实体还包括：应用信息列表下发模块90，设置为与RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者，设置为与RNM建立连接且接收到所述RNM发送的对应用信息列表的请求消息后，再通过响应消息向所述RNM下发应用信息列表。
本实施例提供了中心管理实体向无线节点管理实体下发应用信息，以及中心管理实体从应用服务提供商获取应用信息的接口信令，使得应用服务提供商提供的应用信息可以经由中心管理实体下发给无线节点管理实体。从而使无线节点管理实体可以利用准确的应用信息来为终端分配资源，提升应用体验和资源分配效率的效果。
实施例三
本实施例从整体上提供RNM通过CME获取应用服务提供商提供的应用信息的信令流程。假定CME上没有保存RNM请求的应用信息时，相应流程如图9所示，包括：
步骤610，无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
步骤620，所述CME收到所述请求消息后，向应用服务提供商发送对应用信息的请求消息，携带所述应用名称；
步骤630，所述应用服务提供商收到所述请求消息后，向所述CME发送响应消息，携带所述应用名称对应的应用信息；
步骤640，所述CME收到所述响应消息后，向所述RNM发送响应消息，携带所述应用名称对应的应用信息；
步骤650，所述RNM接收所述CME发送的响应消息，获取所述应用名称对应的应用信息。
下面再通过应用中的几个示例进行说明。
示例一
本示例提供了应用信息获取的信令流程，如图10所示，包括：
步骤S102：中心管理实体下发应用信息列表给无线节点管理实体；
考虑到不断有新应用类型产生和/或无线节点管理实体的存储空间受限，故在初始时，中心管理实体只下发基本或者常用的应用信息组成的应用信息列表到无线节点管理实体，如通过应用信息列表配置消息下发。如果无线节点管理实体发现新应用名称，再向中心管理实体获取该应用名称对应的应用信息。
步骤S104：终端向无线管理实体发送上行数据(如上行报文)，携带 应用名称；
步骤S106：无线节点管理实体从上行报文中获取应用名称；
步骤S108：无线节点管理实体判断是否发起应用信息请求；
无线节点管理实体如果在本地搜索不到所述应用名称对应的应用信息，即可发送针对应用信息的请求消息。
步骤S110：当需要时，无线节点管理实体向中心管理实体发送应用信息请求消息，携带所述应用名称；
步骤S112：中心管理实体也没有保存所述应用名称对应的应用信息时，向应用服务提供商发送应用信息请求；
步骤S114：中心管理实体接收应用服务提供商发送的应用信息响应消息，保存其中携带的所述应用名称对应的应用信息；
步骤S116：中心管理实体响应无线节点管理实体的请求消息，下发应用信息响应消息给无线节点管理实体，携带所述应用名称对应的应用信息；
步骤S118：无线节点管理实体从应用信息的响应消息中获取所述应用名称对应的应用信息，判断是否需要对所述终端进行资源重调整，如果需要，发送无线资源指派消息给终端侧。
其中，中心管理实体维护服务应用信息，负责从应用服务提供商获取应用名称和相应的应用信息，并对应用信息请求消息做出响应向无线节点管理实体发送应用信息。无线节点管理实体存储中心管理实体获取的应用信息，用于在无线资源分配时作为分配策略输入使用。
示例二
本示例提供了无线节点管理实体从手机上行报文获取应用名称的流程。如图11所示，该流程包括：
步骤S202：无线节点管理实体得到手机的上报报文，对报文进行解 析，判断是否存在URL信息，如果存在，执行步骤S206，如未发现URL信息，执行步骤S204；
步骤S204：进一步解析报文，判断该报文是否是域名系统(DNS：Domain Name System)报文，如果是DNS报文，执行步骤S206，否则，直接结束；
步骤S206：无线节点管理实体获取应用名称，结束。
如果报文中存在URL信息，可以将URL信息直接作用上报报文的应用名称。但本发明也可以将报文中其他可以用于搜索应用信息的信息作为应用名称。如果报文是DNS报文，则解析DNS报文具体内容，从中获取上报报文的应用名称，如将其中的域名信息作为应用名称，等等。
示例三
本示例提供了无线节点管理实体从中心管理实体获取应用信息的信令流程。如图12所示，包括：
步骤S302：无线节点管理实体和中心管理实体上电握手完成；
步骤S304：中心管理实体下发应用信息列表配置消息给无线节点管理实体；
步骤S306：无线节点管理实体发送应用信息列表配置响应消息给中心管理实体。
在该示例中，中心管理实体主动下发应用信息列表给无线节点管理实体，应用信息包括基本或者常用的应用信息，具体可以由中心管理实体或者应用业务提供商指定。
示例四
本示例是无线节点管理实体从中心管理实体获取应用信息的信令流程。如图13所示，包括：
步骤S402：无线节点管理实体和中心管理实体上电握手完成；
步骤S404：无线节点管理实体主动发起应用信息列表请求消息给中心管理实体；
步骤S406：中心管理实体发下应用信息列表响应消息给无线节点管理实体，无线节点管理实体保存响应消息中的应用信息列表。
本示例中，由无线节点管理实体主动从中心管理实体获取应用信息列表。
示例五
本示例是无线节点管理实体根据应用信息进行资源调整的信令流程，如图14所示，包括：
步骤S502：无线节点管理实体根据应用名称得到应用信息；
步骤S504：无线节点管理实体根据该应用信息，在考虑终端能力、小区负荷、小区干扰等基础上，根据所述应用信息计算出终端的无线资源需求，与终端已分配的无线资源进行比较，假如终端已分配的无线资源不能满足计算出的无线资源需求，则需要进行资源重调整；假如已分配的无线资源超出所述无线资源需求，则可以保持现有的无线资源，甚至可以做出延缓业务的操作，如忙时延缓软件更新。
上述应用信息包括且不限于包括业务类型，应用协议，业务数据大小，是否有下行数据等信息，在计算无线资源需求时，可以考虑小区类型(如商务小区，娱乐小区等)与业务类型对应关系。
步骤S506：假如需要重调整以满足新的无线资源需求，无线节点管理实体通过空中接口实体把调整后即最新的无线资源指派给终端。
从以上的描述中，可以看出，采用上述实施例和示例所提供的技术方案，业务类型最终由应用服务提供商进行识别并给出应用信息，无线节点管理可以从应用服务提供商准确获取应用信息，针对应用的需求进行针对 性的无线资源分配优化，从而达到提升应用体验和资源分配效率的效果。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
通过本发明实施例，无线节点管理实体、中心管理实体等网络设备可以直接或间接地从应用服务提供商获取准确的应用信息，从而可以针对应用的需求分配无线资源，提升应用体验和资源分配效率的效果。

Claims (25)

  1. 一种获取应用信息的方法，包括：
    无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
    所述RNM接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
  2. 如权利要求1所述的方法，其中：
    所述RNM向所述CME发送对应用信息的请求消息之前，还包括：
    所述RNM从终端发送的上行报文中获取应用名称，判断本地是否保存有所述应用名称对应的应用信息，如没有保存，则向所述CME发送对应用信息的请求消息。
  3. 如权利要求2所述的方法，其中：
    所述RNM从终端发送的上行报文中获取应用名称，包括：
    所述上行报文非域名系统DNS报文，所述RNM从所述上行报文的统一资源定位符URL信息中获取所述应用名称：或者
    所述上行报文为DNS报文，所述RNM从所述DNS报文的域名信息中获取所述应用名称。
  4. 如权利要求1或2或3所述的方法，其中：
    所述RNM接收所述CME发送的响应消息之后，还包括：
    所述RNM获取所述响应消息中携带的所述应用信息，并根据所述应用信息计算所述终端的无线资源需求；
    所述RNM判断所述终端已分配的无线资源是否满足所述无线资源需求，如不满足，则进行资源重调整，通过空中接口实体将调整后的无线资源指派给所述终端。
  5. 如权利要求1所述的方法，其中：
    所述方法还包括：
    所述RNM和CME建立连接后，从所述CME主动发送的配置消息中获取应用信息列表；和/或
    所述RNM和CME建立连接后，主动向所述CME发送对应用信息列表的请求消息，从所述CME发送的响应消息中获取应用信息列表。
  6. 如权利要求1-3、5中任一所述的方法，其中：
    所述RNM保存获取的应有信息，根据保存的应用信息，为终端分配无线资源。
  7. 如权利要求1-3、5中任一所述的方法，其中：
    所述应用信息包括以下信息中的一种或多种：
    业务类型；
    应用协议；
    业务数据大小；及
    是否有下行数据。
  8. 一种下发应用信息的方法，包括：
    中心管理实体CME和无线节点管理实体RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者
    所述CME和RNM建立连接后，如接收到所述RNM发送的对应用信息列表的请求消息，则通过响应消息向所述RNM下发应用信息列表。
  9. 如权利要求8所述的方法，其中：
    所述方法还包括：
    所述CME接收所述RNM发送的对应用信息的请求消息，所述请 求消息中携带应用名称；
    所述CME获取所述应用名称对应的应用信息，将所述应用信息通过响应消息下发给所述RNM。
  10. 如权利要求9所述的方法，其中：
    所述CME获取所述应用名称对应的应用信息，包括：
    所述CME从本地的应用信息列表中获取所述应用信息；或者，所述CME向应用服务提供商发送对所述应用信息的请求消息，从所述应用服务提供商发送的响应消息中获取所述应用信息。
  11. 一种获取应用信息的方法，包括：
    中心管理实体CME向应用服务提供商发送对应用信息的请求消息；
    所述CME接收所述应用服务提供商发送的响应消息，所述响应消息中携带应用信息。
  12. 如权利要求11所述的方法，其中：
    所述请求消息中携带有应用名称，所述响应消息中携带的应用信息为所述应用名称对应的应用信息；或者
    所述请求消息为对应用信息列表的请求消息，所述响应消息中携带的应用信息为应用信息列表。
  13. 一种获取应用信息的方法，包括：
    无线节点管理实体RNM向中心管理实体CME发送对应用信息的请求消息，携带应用名称；
    所述CME收到所述请求消息后，向应用服务提供商发送对应用信息的请求消息，携带所述应用名称；
    所述应用服务提供商收到所述请求消息后，向所述CME发送响应消息，携带所述应用名称对应的应用信息；
    所述CME收到所述响应消息后，向所述RNM发送响应消息，携带所述应用名称对应的应用信息；
    所述RNM接收所述CME发送的响应消息，获取所述应用名称对应的应用信息。
  14. 一种无线节点管理实体，其中，包括应用信息获取模块，所述应用信息获取模块包括：
    请求单元，设置为向中心管理实体CME发送对应用信息的请求消息，所述请求消息中携带应用名称；
    接收单元，设置为接收所述CME发送的响应消息，获取所述响应消息中携带的所述应用名称对应的应用信息。
  15. 如权利要求14所述的无线节点管理实体，其中：
    所述无线节点管理实体还包括决策模块，所述决策模块包括：
    获取单元，设置为从终端发送的上行报文中获取应用名称；
    决策单元，设置为判断本地是否保存有所述应用名称对应的应用信息，如没有，则通知所述信息请求模块向所述CME发送对应用信息的请求消息。
  16. 如权利要求15所述的无线节点管理实体，其中：
    所述获取单元从终端发送的上行报文中获取应用名称，包括：
    所述上行报文非域名系统DNS报文，所述获取单元从所述上行报文的统一资源定位符URL信息中获取所述应用名称：或者
    所述上行报文为DNS报文，所述获取单元从所述DNS报文的域名信息中获取所述应用名称。
  17. 如权利要求14或15或16所述的无线节点管理实体，其中：
    所述无线节点管理实体还包括资源调整模块，所述资源调整模块 包括：
    计算单元，设置为获取所述响应消息中携带的所述应用信息，根据所述应用信息计算所述终端的无线资源需求；及
    调整单元，设置为判断所述终端已分配的无线资源是否满足所述无线资源需求，如不满足，则进行资源重调整，通过空中接口实体将调整后的无线资源指派给所述终端。
  18. 如权利要求14所述的无线节点管理实体，其中：
    所述无线节点管理实体还包括应用信息列表获取模块；
    所述应用信息列表获取模块包括：
    接收单元，设置为与CME建立连接后，从所述CME主动发送的配置消息中获取应用信息列表；
    或者
    所述应用信息列表获取模块包括：
    请求单元，设置为与CME建立连接后，主动向所述CME发送对应用信息列表的请求消息；及
    接收单元，设置为接收所述CME通过响应消息下发的应用信息列表。
  19. 如权利要求14-16、18中任一所述的无线节点管理实体，其中：
    所述无线节点管理实体还包括：存储模块，设置为保存获取的应用信息。
  20. 如权利要求14-16、18中任一所述的无线节点管理实体，其中：
    所述应用信息包括以下信息中的一种或多种：
    业务类型；
    应用协议；
    业务数据大小；及
    是否有下行数据。
  21. 一种中心管理实体，其中，包括应用信息下发模块，所述应用信息下发模块包括：
    接收单元，设置为接收无线节点管理实体RNM发送的对应用信息的请求消息，所述请求消息中携带应用名称；
    获取单元，设置为获取所述应用名称对应的应用信息；
    下发单元，设置为将所述应用信息通过响应消息下发给所述RNM。
  22. 如权利要求21所述的中心管理实体，其中：
    所述获取单元获取所述应用名称对应的应用信息，包括：所述获取单元从本地的应用信息列表中获取所述应用信息；或者，向应用服务提供商发送对所述应用信息的请求消息，从所述应用服务提供商发送的响应消息中获取所述应用信息。
  23. 如权利要求21或22所述的中心管理实体，其中：
    所述中心管理实体还包括：应用信息列表下发模块，设置为与RNM建立连接后，主动向所述RNM发送配置消息，携带应用信息列表；或者，设置为与RNM建立连接且接收到所述RNM发送的对应用信息列表的请求消息后，再通过响应消息向所述RNM下发应用信息列表。
  24. 一种中心管理实体，其中，包括应用信息获取模块，所述应用信息获取模块包括：
    请求单元，设置为向应用服务提供商发送对应用信息的请求消息；
    接收单元，设置为接收所述应用服务提供商发送的响应消息，获取所述响应消息中携带的应用信息并保存。
  25. 如权利要求24所述的中心管理实体，其中：
    所述请求单元发送的请求消息中携带有应用名称，所述接收单元接收的响应消息中携带的应用信息为所述应用名称对应的应用信息；或者
    所述请求单元发送的请求消息为对应用信息列表的请求消息，所述接收单元接收的所述响应消息中携带的应用信息为应用信息列表。
PCT/CN2016/097707 2015-12-18 2016-08-31 一种获取、下发应用信息的方法和设备 WO2017101516A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510956920.5A CN106900060B (zh) 2015-12-18 2015-12-18 一种获取、下发应用信息的方法和设备
CN201510956920.5 2015-12-18

Publications (1)

Publication Number Publication Date
WO2017101516A1 true WO2017101516A1 (zh) 2017-06-22

Family

ID=59055678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097707 WO2017101516A1 (zh) 2015-12-18 2016-08-31 一种获取、下发应用信息的方法和设备

Country Status (2)

Country Link
CN (1) CN106900060B (zh)
WO (1) WO2017101516A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104254129A (zh) * 2013-06-25 2014-12-31 中兴通讯股份有限公司 临近业务发现的资源配置方法及装置
WO2015094943A1 (en) * 2013-12-19 2015-06-25 Chicago Mercantile Exchange Inc. Deterministic and efficient message packet management
CN104811922A (zh) * 2014-01-29 2015-07-29 中兴通讯股份有限公司 一种相邻节点注册方法和装置、跨节点注册方法和系统
CN104980980A (zh) * 2014-04-10 2015-10-14 电信科学技术研究院 一种建立连接的方法、系统和设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101304330B (zh) * 2008-06-28 2010-12-08 华为技术有限公司 一种资源配置方法、服务器、及网络系统
CN101729363B (zh) * 2008-10-21 2012-05-30 华为技术有限公司 一种资源初始化的方法、装置和系统
CN101909362A (zh) * 2009-06-02 2010-12-08 中兴通讯股份有限公司 一种实现业务释放的方法、系统及演进节点b
US9955348B2 (en) * 2012-09-12 2018-04-24 Lg Electronics Inc. Method and device for requesting for specific right acquisition on specific resource in wireless communication system
CN104955171A (zh) * 2014-03-26 2015-09-30 中兴通讯股份有限公司 移动通信网络连接创建的控制方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104254129A (zh) * 2013-06-25 2014-12-31 中兴通讯股份有限公司 临近业务发现的资源配置方法及装置
WO2015094943A1 (en) * 2013-12-19 2015-06-25 Chicago Mercantile Exchange Inc. Deterministic and efficient message packet management
CN104811922A (zh) * 2014-01-29 2015-07-29 中兴通讯股份有限公司 一种相邻节点注册方法和装置、跨节点注册方法和系统
CN104980980A (zh) * 2014-04-10 2015-10-14 电信科学技术研究院 一种建立连接的方法、系统和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
POPOVSKI, PETAR ET AL.: "Final report on the METIS 5G system concept and technology roadmap", ICT-317669-METIS/D6. 6''METIS, 30 April 2015 (2015-04-30), XP055391721 *

Also Published As

Publication number Publication date
CN106900060A (zh) 2017-06-27
CN106900060B (zh) 2021-07-13

Similar Documents

Publication Publication Date Title
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US11917498B2 (en) Communication method and communications apparatus
CN109863789B (zh) 在移动通信系统中基于可适用网络信息将终端连接到网络的方法及设备
CN106060900B (zh) 网络切片的接入控制方法及装置、终端化小区和sdn控制器
WO2018161850A1 (en) System and method of network policy optimization
WO2018171375A1 (zh) 一种网络切片选择方法、用户设备及网络设备
EP3509336A1 (en) Method and device for terminal attaching and creating home-routed pdu session in roaming environment supporting network slice
CN110830925B (zh) 一种用户群组的会话管理方法及装置
CN113841432A (zh) 用于提供与终端的连接以便使用边缘计算服务的方法和设备
KR20180134685A (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
CN110381162B (zh) 一种业务处理的方法以及相关装置
US20110113146A1 (en) Dynamic quality of service (qos) setup over wired and wireless networks
WO2019184784A1 (zh) 一种通信方法及相关设备
US20200228618A1 (en) Content delivery method, device, and system
CN113572835B (zh) 一种数据处理方法、网元设备以及可读存储介质
WO2019095381A1 (zh) 业务配置方法及相关产品
CN114615154A (zh) 服务质量管理的方法及装置、通信系统
WO2019153124A1 (zh) 数据传输控制方法及相关产品
KR20160076163A (ko) 이동 통신 시스템에서 전송 차별화를 제공하는 방법 및 장치
WO2023000936A1 (zh) 一种数据处理方法、网元设备以及可读存储介质
US10764411B2 (en) Stream control transmission protocol SCTP-based communications method and system, and apparatus
US20220263879A1 (en) Multicast session establishment method and network device
CN113329276B (zh) 数据传输方法、装置、网关、芯片及存储介质
CN108574965B (zh) 一种进行请求处理的方法及设备
WO2022052875A1 (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: 16874576

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

Country of ref document: EP

Kind code of ref document: A1