WO2017020203A1 - 路由规则的获取方法、设备和*** - Google Patents

路由规则的获取方法、设备和*** Download PDF

Info

Publication number
WO2017020203A1
WO2017020203A1 PCT/CN2015/085805 CN2015085805W WO2017020203A1 WO 2017020203 A1 WO2017020203 A1 WO 2017020203A1 CN 2015085805 W CN2015085805 W CN 2015085805W WO 2017020203 A1 WO2017020203 A1 WO 2017020203A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
path
data bus
routing rule
information
Prior art date
Application number
PCT/CN2015/085805
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 华为技术有限公司
Priority to PCT/CN2015/085805 priority Critical patent/WO2017020203A1/zh
Priority to JP2018500770A priority patent/JP6494150B2/ja
Priority to EP15899978.9A priority patent/EP3313027B1/en
Priority to CN202010256137.9A priority patent/CN111654433B/zh
Priority to CN201580042653.9A priority patent/CN106576074B/zh
Publication of WO2017020203A1 publication Critical patent/WO2017020203A1/zh
Priority to US15/883,732 priority patent/US20180159765A1/en
Priority to US16/917,053 priority patent/US20200336410A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method, device, and system for acquiring routing rules.
  • Mobile Edge Computing (English: Mobile Edge Computing, MEC for short) means providing an Internet service environment and cloud computing capabilities on a wireless access network close to mobile users, creating a highly distributed environment for deploying applications and services, and The MEC can store and process data; it can also open real-time wireless network information to provide personalized, context-sensitive business experiences for mobile users.
  • FIG. 1 is a schematic diagram of an architecture of an MEC system.
  • the MEC system includes an MEC infrastructure, an MEC application platform, and multiple virtual MEC applications (English: application, referred to as APP), and the basis of the MEC.
  • the facility includes MEC hardware resources and MEC virtual layer for providing hardware support and services for the MEC application platform.
  • the MEC application platform includes a manager and multiple virtual application services, such as data stream distribution (English: Traffic Offload Function, referred to as TOF) ), wireless network information open services, communication services and service registration, etc., these services can be called by the MEC's APP to achieve the corresponding functions.
  • data packets need to be transmitted between different services or applications according to a pre-configured forwarding path, so that data can be transmitted to the correct service or application according to user requirements, and processed correctly.
  • the virtual application or service can be changed continuously. How to dynamically determine the path to be transmitted by the data has not been solved yet.
  • routing data in the MEC the data is forwarded according to the configured path, resulting in data routing errors.
  • the embodiment of the invention provides a method, a device and a system for acquiring a routing rule, which are used to solve the problem that the virtual application or service can be changed continuously.
  • the data transmission path cannot be dynamically determined, and the path is forwarded according to the configured path. The problem that caused data routing errors.
  • a first aspect of the present invention provides a method for obtaining a routing rule, which is applied to a mobile edge computing MEC system, where the MEC system includes a data bus controller and a data bus, and the method includes:
  • the data bus controller acquires service information of at least one service in the MEC system; the service information of each service includes a service type and a service identifier;
  • the data bus controller generates a routing rule according to the service information of the at least one service, where the routing rule is used to indicate at least one path through which the data packet can pass, and each path includes a service identifier of the at least one service;
  • the data bus controller sends the routing rule to a data bus to cause the data bus to forward the received data packet to a service corresponding to the data packet according to the routing rule.
  • the data bus controller generates a routing rule according to the service information of the at least one service, including:
  • the data bus controller obtains the routing rule according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and each filter corresponding to Path information; each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • each filter is further configured to indicate a base station address and/or a gateway address of the corresponding path.
  • the data bus controller acquires at least one of the MEC systems Business information of the business, including:
  • the data bus controller receives service information reported by each service in the MEC system
  • the data bus controller receives service information of at least one service in the MEC system sent by the service manager.
  • the routing rule further includes: a path identifier a list and at least one path information; the path identification list includes each filter and path identifier Corresponding relationship; the path information includes a service identifier of the at least one service corresponding to the path identifier.
  • the data bus includes a classifier and a service repeater, and the data bus controller routes the route The rule is sent to the data bus, so that the data bus forwards the data packet to each service in the service list according to the routing rule, including:
  • the data bus controller transmits the at least one filter and the path identification list to the classifier to cause the classifier to determine the received data packet based on the at least one filter and path identification list And the first path identifier is added, and the first path identifier is added to the data packet, and the data packet after the first path identifier is added is sent to the service forwarder.
  • a second aspect of the present invention provides a data bus controller, including:
  • An obtaining module configured to obtain service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier;
  • a processing module configured to generate, according to the service information of the at least one service, a routing rule, where the routing rule is used to indicate at least one path that the data packet can pass, and each path includes a service identifier of the at least one service;
  • a sending module configured to send the routing rule to the data bus, so that the data bus forwards the received data packet to a service corresponding to the data packet according to the routing rule.
  • the processing module is specifically configured to:
  • routing rule Obtaining the routing rule according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter; The filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the acquiring module includes:
  • a first receiving unit configured to receive service information of at least one service in the MEC system sent by the service registration device;
  • a second receiving unit configured to receive service information reported by each service in the MEC system
  • the third receiving unit is configured to receive service information of at least one service in the MEC system sent by the service manager.
  • the routing rule generated by the processing module further includes: a path And the at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; the path information includes a service identifier of the at least one service corresponding to the path identifier.
  • the data bus includes a classifier and a service forwarder
  • the sending module includes:
  • a first sending unit configured to send the at least one filter and the path identifier list to the classifier, so that the classifier determines the received data according to the at least one filter and the path identifier list a first path identifier of the packet, and adding the first path identifier to the data packet, and sending the data packet that is added by the first path identifier to the service forwarder;
  • a second sending unit configured to send the path identifier list and the at least one path information to the service forwarder, so that the service forwarder according to the path identifier list, the at least one path information, and the A path identifier forwards the received data packet sent by the filter to a corresponding service.
  • a third aspect of the present invention provides a data bus controller, including:
  • a receiver configured to obtain service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier;
  • a processor configured to generate, according to the service information of the at least one service, a routing rule, where the routing rule is used to indicate at least one path that the data packet can pass, and each path includes a service identifier of the at least one service;
  • a transmitter configured to send the routing rule to the data bus, so that the data bus forwards the received data packet to a service corresponding to the data packet according to the routing rule.
  • a fourth aspect of the present invention provides a system for acquiring a routing rule, including: a data bus controller and a data bus;
  • the data bus controller obtains service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier;
  • the data bus controller generates a routing rule according to the service information of the at least one service, where the routing rule is used to indicate at least one path through which the data packet can pass, and each path includes a service identifier of the at least one service;
  • the data bus controller sends the routing rule to a data bus
  • the data bus receives the routing rule sent by the data bus controller, and forwards the received data packet to a service corresponding to the data packet according to the routing rule.
  • the data bus controller is specifically configured to:
  • routing rule Obtaining the routing rule according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter; The filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • system further includes: at least one service, service registration device;
  • Each service in the MEC system sends service information of the service to the service registration device;
  • the service registration device transmits service information of the at least one service to the data bus controller
  • the data bus controller receives service information of the at least one service sent by the service registration device.
  • system further includes: at least one service
  • Each service in the MEC system sends service information of the service to the data bus controller
  • the data bus controller receives the service information reported by each service
  • system further includes: a service manager;
  • the service manager acquires service information of at least one service in the MEC system, and sends service information of the at least one service to the data bus controller;
  • the data bus controller receives service information of at least one service sent by the service manager.
  • the routing rule generated by the data bus controller The method further includes: a path identifier list and at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; and the path information includes a service identifier of the at least one service corresponding to the path identifier.
  • the data bus includes a classifier and a service repeater, and the data bus controller uses the route
  • the rules sent to the data bus include:
  • the data bus controller transmits the at least one filter and the path identification list to the classifier
  • the data bus receives the routing rule sent by the data bus controller, and forwards the received data packet to the service corresponding to the data packet according to the routing rule, including:
  • the classifier receives the at least one filter and the path identifier list sent by the data bus controller;
  • the identified data packet is sent to the service forwarder;
  • the service forwarder forwards the received data packet sent by the filter to the corresponding service according to the path identifier list, the at least one path information, and the first path identifier.
  • the method, device and system for acquiring a routing rule provided by the present invention are applied to an MEC system, and the data bus controller acquires service information of at least one service in the MEC system, and according to at least one industry Business information, generating a routing rule, indicating at least one path through which the data packet can pass, each path including a service identifier of at least one service; sending the routing rule to the data bus, so that the data bus updates the new routing rule, and will receive
  • the obtained data packet is forwarded to the service corresponding to the data packet, and the service information of all the services is dynamically obtained, the path indicated in the routing rule is updated, the path of the service is added, and the data can be forwarded according to the new routing rule after receiving the data.
  • the data is correctly routed to the corresponding service to ensure the correctness of the data routing.
  • Figure 1 is a schematic diagram of an architecture of an MEC system
  • FIG. 2 is a schematic diagram of an MEC architecture provided by the present invention.
  • Embodiment 3 is a flowchart of Embodiment 1 of a method for obtaining a routing rule according to the present invention
  • Embodiment 4 is a flowchart of Embodiment 2 of a method for obtaining a routing rule according to the present invention
  • FIG. 5 is an interaction diagram of Embodiment 1 of an acquisition rule of a routing rule according to the present invention.
  • Embodiment 6 is an interaction diagram of Embodiment 2 of an acquisition rule of a routing rule according to the present invention.
  • FIG. 7 is an interaction diagram of Embodiment 3 of an acquisition rule of a routing rule according to the present invention.
  • Embodiment 8 is an interaction diagram of Embodiment 4 of an acquisition rule of a routing rule according to the present invention.
  • Embodiment 9 is an interaction diagram of Embodiment 5 of an acquisition rule of a routing rule according to the present invention.
  • Embodiment 1 of a data bus controller according to the present invention
  • Embodiment 11 is a schematic structural diagram of Embodiment 2 of a data bus controller according to the present invention.
  • Embodiment 3 of a data bus controller is a schematic structural diagram of Embodiment 3 of a data bus controller according to the present invention.
  • FIG. 13 is a schematic diagram of an embodiment of a data bus controller entity of the present invention.
  • the present invention will provide a method for routing data in an MEC system.
  • the main implementation process is a data bus (English Traffic Bus, TB for short) controller in the MEC.
  • Service or application English: Service/App
  • service registration English: Service Registry, abbreviated as: SR
  • Operation Support System English: Operation Support System, OSS
  • Business Support System English: Business Support System, BSS for short
  • service or application business information also called For the status information
  • FIG. 2 is a schematic diagram of the MEC architecture provided by the present invention. As shown in FIG. 2, the architecture includes a TB controller and a data bus connection (the data bus includes a data forwarder and a classifier).
  • Service bus Service registry (also known as service registration device) and at least one service or application that can be improved, such as gateway (English: Gateway, GW for short, user card (English: User Plane, UP: UP) Service, core network information service (English: Core Network Information Service, referred to as: CNIS), wireless network information open service (English: Radio Network Information Service, referred to as: RNIS and other services or applications (English: application, referred to as: APP
  • the TB controller can directly interact with the registry, application or service via the data bus and the service bus.
  • the classifier is used to receive the data packet, select the path of the data route, and the data forwarder is used to determine the data according to the classifier.
  • the routing path forwards the data packet to the correct service or application, and the TB controller is used to deliver the data, including Routing rules for path information to classifiers and/or data forwarders.
  • FIG. 3 is a flowchart of Embodiment 1 of a method for obtaining a routing rule according to the present invention. As shown in FIG. 3, the method is applied to an MEC system. On the basis of the MEC architecture shown in FIG. 2, the execution body of the solution is a data bus. The controller, the specific steps of the method for obtaining the routing rule include:
  • the data bus controller acquires service information of at least one service in the MEC system; the service information of each service includes a service type and a service identifier.
  • the service includes a service or an application (Service/App).
  • Service/App an application or service
  • the data bus controller needs to obtain information about the application or the service, for example, the MEC adds a Service ( Or deleting a service), the service information of the service needs to be re-acquired, and the service information of each service includes the service identifier (English: identity, abbreviation: ID) and the service type.
  • ID an application deleting a service
  • ID service identifier
  • the manner in which the specific data bus controller obtains the service information includes at least the following.
  • the data bus controller receives service information of at least one service in the MEC system sent by the service registration device.
  • the instance of the service or application is registered with the service registration device (also known as the service registry), and the parameters carried include the identity and type of the service or application.
  • the service registration device actively transmits the service information of the newly registered service or application to the data bus controller.
  • the data bus controller receives the service information reported by each service in the MEC system.
  • the address of the data bus controller is obtained at the time of service or application installation; after the installation is complete, the service or application sends an update message to the data bus controller, including the service identification or service type of the application or service.
  • the data bus controller receives service information of at least one service in the MEC system sent by the service manager.
  • the management manager of the management MEC sends the information of the newly installed service or application to the data bus controller, requesting to update the available services or applications in the data bus controller, and the service message includes the service identifier. And business type.
  • the foregoing provides a manner in which the three data bus controllers obtain the service information of the service or the application in the MEC, but the method is not limited to the foregoing, and the service information of all the available services in the current MEC system can be obtained by any means.
  • the specific implementation does not limit.
  • the data bus controller generates a routing rule according to the service information of the at least one service, where the routing rule is used to indicate at least one path that the data packet can pass, and each path includes a service identifier of the at least one service.
  • the data bus controller generates a protocol and a service type and a service identifier of the at least one service according to a preset routing rule, and obtains the routing rule, in a specific protocol. Specific rules for obtaining corresponding filters based on service identifiers and/or service types are specified.
  • the routing rule is used to indicate at least one path through which the data packet can pass, and each path includes a service identifier of at least one service.
  • the meaning of "passable" here refers to all possible paths, not limited to one.
  • the data packet here is also a generalized data packet, and is not limited to a specific data packet, and the routing rule includes all paths through which the received data may pass.
  • the obtained routing rule includes: at least one filter and path information corresponding to each filter, where each filter is used to indicate a source address, a destination address, a sending protocol, a source port number, and a destination of the corresponding path.
  • the port number The service identifier of the at least one service included in the path indicated by the path information.
  • each filter may be at least used to indicate a base station address and/or a gateway address of the corresponding path.
  • the data bus controller sends the routing rule to a data bus, so that the data bus forwards the received data packet to a service corresponding to the data packet according to the routing rule.
  • the data bus controller sends the routing rule to the data bus, and the data bus updates the original routing rule, and the update includes all applications or services in the MEC system. New routing rules. If a packet is sent to the data bus, the data is sorted and forwarded according to the new routing rule, and the packet is sent to the target service or application.
  • the method for obtaining the routing rule provided by the embodiment is applied to the MEC system, and the data bus controller obtains the service information of the service in the MEC system, and generates a routing rule according to the service information of the at least one service, indicating that at least the data packet can pass.
  • a path each path includes a service identifier of at least one service; the routing rule is sent to the data bus, and the path indicated in the routing rule is updated by dynamically acquiring the service information, and the path including the changed service is added to ensure that the path is received.
  • Embodiment 4 is a flowchart of Embodiment 2 of a method for obtaining a routing rule according to the present invention. As shown in FIG. 4, the method is applied to an MEC system. On the basis of the MEC architecture shown in FIG. 2, the data bus includes a classifier.
  • the routing rule further includes: a path identifier list and at least one path information; the path identifier list includes each Corresponding relationship between the filter and the path identifier; the path information includes a service identifier of the at least one service corresponding to the path identifier, and the data bus controller sends the routing rule to the data bus in step S103, so that
  • the specific implementation of forwarding, by the data bus, the data packet to each service in the service list according to the routing rule includes the following two steps:
  • the data bus controller sends the at least one filter and the path identifier list to the classifier, so that the classifier determines the received according to the at least one filter and the path identifier list.
  • the first path identifier of the data packet is added, and the first path identifier is added to the data packet, and the data packet after the first path identifier is added is sent to the service forwarder.
  • the routing rule specifically includes several parts, including at least one filter, and further includes a path identifier list and at least one path information.
  • the path identifier list includes a correspondence between each filter and the path identifier
  • the path information includes a service identifier of the at least one service corresponding to the path identifier and the path identifier, and is sent separately when sending the routing rule to the data bus, and finally Corresponding at least one service of the filter and the path by the path identifier.
  • the data bus controller transmits at least one filter and the path identification list to a classifier in the data bus.
  • the classifier determines the first path identifier corresponding to the data packet according to the specific information of the data packet, and adds the first path identifier to the data packet, where the added field indicates the first Path identifier. And sending the data packet with the first path identifier added to the data forwarder.
  • the data bus controller sends the path identifier list and the at least one path information to the service forwarder, so that the service forwarder according to the path identifier list, the at least one path information, and the The first path identifier forwards the received data packet sent by the filter to a corresponding service.
  • the data bus controller sends the path identifier list and the at least one path information to the service forwarder, after the data forwarder receives the data packet sent by the classifier and adds the first path identifier, according to the The first path identifier, the path identifier list, and the at least one path information obtain path information of the data packet, and then forward the data packet to a service, that is, a service or an application, on the corresponding path.
  • the data bus controller obtains the service information of all the services of the MEC system, and generates a routing rule, including a filter, a path information, and a path identifier list, according to the service information of the at least one service. Send the routing rule to the classifier and number separately According to the repeater, the filter and the path information are associated by the path identifier list.
  • the distributor determines the path identifier according to the filter, and then sends the identifier to the data forwarder, and the data forwarder identifies the path according to the data packet.
  • the corresponding path information is obtained, and the data packet is forwarded to the corresponding application or service, and the new routing rule is flexibly customized according to the service information of all the services or applications acquired in real time, and all the service paths are quickly deployed, and the data is received.
  • the data flow direction is correctly controlled, and the data is correctly routed to the corresponding service or application.
  • the execution bodies of the above two embodiments are all directed to the data bus controller.
  • the following is the main system, and the specific implementation process of the technical solution of the present invention is specifically described.
  • the acquisition system of the routing rule includes at least a data bus controller and a data bus; the data bus controller acquires service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier; The data bus controller generates a routing rule according to the service information of the at least one service, where the routing rule is used to indicate at least one path through which the data packet can pass, and each path includes a service identifier of the at least one service; the data The bus controller sends the routing rule to a data bus; the data bus receives the routing rule sent by the data bus controller, and forwards the received data packet to the data packet according to the routing rule Corresponding business.
  • the process of implementing the routing rule acquisition method by the system is specifically described below through several interactive embodiments.
  • FIG. 5 is an interaction diagram of Embodiment 1 of a routing rule obtaining system according to the present invention.
  • the system includes at least one service or application, a service registration center, a TB controller, and a data bus, and each part thereof Referring to FIG. 2, the specific implementation steps of the solution are as follows:
  • S302 Send registration information to the service registration center, including the service identifier and service type of the service/application.
  • the service registration center returns a registration confirmation message to the service or the application.
  • the instance of the Service/App is registered with the service registration center, and the parameters carried include the Service ID and the Service Type.
  • the service registration center After the registration is successful, the service registration center returns a confirmation message to the Service/App to confirm that the application or service registration is successful.
  • the service registration center sends a service/application update message to the TB controller, where the application update message includes a service identifier and a service type.
  • each service in the MEC system sends the service to the service registration device.
  • Service information of the service the service registration device receives service information transmitted by the at least one service; the service registration device transmits service information of the at least one service to the data bus controller; the data bus controller Receiving service information of the at least one service sent by the service registration device. That is, the service registry requests the TB Controller to update the available Service/App, including the Service ID and Service Type.
  • S305 The TB controller generates a routing rule.
  • the routing rule is generated according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter.
  • Each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the data bus classifies and forwards the received data packets according to the new routing rules, and sends the data packets to the destination application or service.
  • Embodiment 2 of a routing rule obtaining system according to the present invention.
  • the system includes at least one service or application, a service registration center, a TB controller, and a data bus, and the data bus includes a classification.
  • the data forwarder, the interaction mode between each part refers to Figure 2, the specific implementation steps of the solution are:
  • S402 Send registration information to the service registration center, including the service identifier and service type of the service/application.
  • S403 The service registry returns a registration confirmation message to the service or application.
  • the service registration center sends a service/application update message to the TB controller, where the application update message includes a service identifier and a service type.
  • the update message may include the following Table 1:
  • Table 1 shows the business information of the APP.
  • the TB controller generates a routing rule, where the routing rule includes at least one filter, a path identifier list, and at least one path information.
  • the routing rule is generated according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter. Each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the routing rule further includes: a path identifier list and at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; the path information includes a path identifier of the at least one service corresponding to the path identifier Logo.
  • Table 2 an example of several filters in the routing rule is shown in Table 2 below, where the source address, destination address, sending protocol, source port number, and destination port number of the path need to be explicitly indicated, and the base station address and gateway are additionally specified.
  • the address can be determined based on actual conditions.
  • Table 2 shows the filter instances in several routing rules.
  • the TB controller sends the at least one filter and path identifier list to the classifier.
  • the path information includes a service identifier of the at least one service corresponding to the path identifier, such as an address of an application of a next hop corresponding to the service chain in Table 3 or an address of the service, so that the data bus can
  • the data packet is forwarded according to the routing rule, and the data packet is delivered to the corresponding application or service.
  • Table 3 shows an example of how path information is represented.
  • the TB controller sends the at least one path information and the path identifier list to the classifier.
  • the data bus controller sends the at least one filter and the path identifier list to the classifier; the data bus controller sends the path identifier list and at least one path information Giving the service forwarder; the classifier receiving the at least one filter and the path identification list sent by the data bus controller; the classifier determining according to the at least one filter and path identification list a first path identifier of the received data packet, and adding the first path identifier to the data packet, and sending the data packet that is added by the first path identifier to the service forwarder; Receiving, by the classifier, a data packet after the first path identifier is added; the service forwarder according to the path identifier list, the at least one path information, and the first path identifier, The data packet sent by the filter is forwarded to the corresponding service.
  • FIG. 7 is an interaction diagram of Embodiment 3 of an acquisition rule of a routing rule according to the present invention.
  • the system includes at least one service or application, a TB controller, and a data bus, a data bus, and between each part.
  • a service or application e.g., a service or application
  • a TB controller e.g., a TB controller
  • a data bus e.g., a data bus, and between each part.
  • Figure 2 for the interaction mode.
  • the specific implementation steps of the solution are as follows:
  • S501 The service/application installs and obtains the address of the TB controller.
  • the service/application instance sends a service/application update message to the TB controller, where the application update message includes a service identifier and a service type.
  • each service in the MEC system sends service information of the service to the data bus controller; the data bus controller receives service information reported by each service.
  • S503 The TB controller generates a routing rule.
  • the routing rule is generated according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter.
  • Each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the routing rule further includes: a path identifier list and at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; the path information includes a path identifier and the path Identify the service identifier of the corresponding at least one service.
  • Routing rules can also be sent to classifiers and data forwarders to classify data packets. And forwarding, the implementation is similar to the scheme shown in Figure 6.
  • FIG. 8 is an interaction diagram of Embodiment 4 of the routing rule obtaining system of the present invention. As shown in FIG. 8 , the system includes a service controller, a TB controller, and a data bus, and the specific implementation steps of the solution are:
  • the service controller sends a service/application update message to the TB controller, where the application update message includes a service identifier and a service type.
  • the service controller (also called the management unit) requests the TB controller to update the available Service/App, and the parameters include the Service ID and the Service Type.
  • the service manager acquires service information of at least one service in the MEC system, and sends service information of the at least one service to the data bus controller; the data bus controller receives a service manager The business information of at least one service sent.
  • S603 The TB controller generates a routing rule.
  • routing rules can also be sent to the classifier and the data forwarder respectively to implement classification and forwarding of the data packets, and the implementation manner is similar to the solution shown in FIG. 6.
  • Embodiment 5 is an interaction diagram of Embodiment 5 of an acquisition rule of a routing rule according to the present invention.
  • the system includes at least one service or application, a service registration center, a TB controller, and a data bus.
  • the specific implementation steps of the solution are as follows:
  • S702 Send registration information to the service registration center, including the service identifier and service type of the service/application.
  • S703 The service registry returns a registration confirmation message including the TB controller address to the service or application.
  • the instance of the Service/App is registered with the service registration center, and the parameters carried include the Service ID and the Service Type.
  • the service registration center After the registration is successful, the service registration center returns a registration confirmation message including the address of the TB controller to the Service/App to confirm that the application or service registration is successful.
  • the service/application instance sends a service/application update message to the TB controller, and the application update The message includes the service identifier and the type of service.
  • each service in the MEC system sends service information of the service to the service registration device; the service registration device receives service information sent by the at least one service; The service information of the at least one service is sent to the data bus controller; the data bus controller receives the service information of the at least one service sent by the service registration device. That is, the service registration center requests the TB controller corresponding to the address of the returned TB controller to update the available Service/App, and the parameters include the Service ID and the Service Type.
  • S705 The TB controller generates a routing rule.
  • the routing rule is generated according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter.
  • Each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the TB controller may obtain the priority of the service or the application in the MEC system from the service manager, and process the priority in the process of generating the routing rule.
  • the data bus classifies and forwards the received data packets according to the new routing rules, and sends the data packets to the destination application or service.
  • the routing rules may be separately sent to the data bus as shown in FIG. 6. The classifier and data forwarder will not be described here.
  • the service controller mentioned may be an OSS/BSS
  • the TB controller may directly access the OSS/BSS to obtain information about the service or the application.
  • the data bus controller 10 is a schematic structural diagram of Embodiment 1 of a data bus controller according to the present invention. As shown in FIG. 10, the data bus controller 10 includes: an obtaining module 11, a processing module 12, and a transmitting module 13;
  • the obtaining module 11 is configured to obtain service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier;
  • the processing module 12 is configured to generate, according to the service information of the at least one service, a routing rule, where the routing rule is used to indicate at least one path that the data packet can pass, and each path includes a service identifier of the at least one service;
  • the sending module 13 is configured to send the routing rule to the data bus, so that the data bus forwards the received data packet to the service corresponding to the data packet according to the routing rule.
  • processing module 12 is specifically configured to:
  • routing rule Obtaining the routing rule according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filter and path information corresponding to each filter; The filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • the routing rule generated by the processing module 12 further includes: a path identifier list and at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; the path information includes a path identifier A service identifier of at least one service corresponding to the path identifier.
  • the data bus controller provided in this embodiment is used to execute the technical solution of the data bus controller in the technical solution shown in any one of FIG. 3 to FIG. 9, and dynamically obtains the service information of all services in the MEC system, and uses the routing rule.
  • the path indicated in the update is updated to increase the path of the service, and the data can be forwarded according to the new routing rule after receiving the data, so as to avoid the problem that some applications cannot receive data or the data is not successfully sent, and the received data is correctly routed. Go to the corresponding app or service.
  • the acquisition module 11 of the data bus controller 10 specifically includes:
  • the first receiving unit 111 is configured to receive service information of at least one service in the MEC system sent by the service registration device;
  • the second receiving unit 112 is configured to receive service information reported by each service in the MEC system
  • the third receiving unit 113 is configured to receive service information of at least one service in the MEC system that is sent by the service manager.
  • the data bus controller provided in this embodiment is used to implement the technical solution of the data bus controller in the technical solution shown in any one of FIG. 3 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.
  • Embodiment 3 of a data bus controller is a schematic structural diagram of Embodiment 3 of a data bus controller according to the present invention.
  • the data bus includes a classifier and a service repeater, and the data bus is used.
  • the sending module 13 of the controller 10 includes:
  • the first sending unit 131 is configured to send the at least one filter and the path identifier list to the classifier, so that the classifier determines the received according to the at least one filter and the path identifier list. a first path identifier of the data packet, and adding the first path identifier to the data packet, and sending the data packet that is added by the first path identifier to the service forwarder;
  • a second sending unit 132 configured to send the path identifier list and the at least one path information to the service forwarder, so that the service forwarder according to the path identifier list, the at least one path information, and the The first path identifier forwards the received data packet sent by the filter to a corresponding service.
  • the data bus controller provided in this embodiment is used to implement the technical solution of the data bus controller in the technical solution shown in any one of FIG. 3 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.
  • FIG. 13 is a schematic diagram of an embodiment of a data bus controller entity of the present invention. As shown in FIG. 13, the data bus controller is specifically implemented as: a receiver 21, a processor 22, and a transmitter 23.
  • the receiver 21 is configured to obtain service information of at least one service in the mobile edge computing MEC system; the service information of each service includes a service type and a service identifier;
  • the processor 22 is configured to generate, according to the service information of the at least one service, a routing rule, where the routing rule is used to indicate at least one path that the data packet can pass, and each path includes a service identifier of the at least one service;
  • the transmitter 23 is configured to send the routing rule to the data bus, so that the data bus forwards the received data packet to the service corresponding to the data packet according to the routing rule.
  • the processor 22 is specifically configured to: obtain the routing rule according to a preset routing rule generation protocol and a service type and a service identifier of the at least one service, where the routing rule includes: at least one filtering Path information corresponding to each filter; each filter is used to indicate the source address, destination address, sending protocol, source port number, and destination port number of the corresponding path.
  • Each filter is also used to indicate the base station address and/or gateway address of the corresponding path.
  • the receiver 21 is specifically configured to: receive service information of at least one service in the MEC system sent by the service registration device;
  • the routing rule further includes: a path identifier list and at least one path information; the path identifier list includes a correspondence between each filter and the path identifier; and the path information includes a path identifier corresponding to the path identifier.
  • the data bus includes a classifier and a service forwarder, and the transmitter 23 is specifically configured to:
  • the data packet sent by the filter is forwarded to the corresponding service.
  • the data bus controller provided in this embodiment is used to implement the scheme of the site in the method embodiment shown in FIG. 2 to FIG. 9 , and the implementation principle and technical effects are similar, and details are not described herein again.
  • the processor may be a central processing unit (English: Central Processing Unit, CPU for short), or other general-purpose processor, digital signal processor (English: Digital) Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the steps including the foregoing method embodiments are performed; and the foregoing storage medium includes: read-only memory (English: read-only memory, abbreviation: ROM), RAM, flash memory, hard disk, solid state hard disk, Magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种路由规则的获取方法、设备和***，该方法应用于MEC***，具体包括：数据总线控制器获取MEC***至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；并根据至少一种业务的业务信息，生成路由规则，路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；将路由规则发送至数据总线，以使数据总线根据路由规则，将接收到的数据包转发至数据包对应的业务。通过动态获取每个业务的业务信息，对路由规则中指示的路径进行更新，增加所有业务的路径，保证在接收到数据后可以根据新的路由规则进行转发，将数据正确路由到对应的应用或服务。

Description

路由规则的获取方法、设备和*** 技术领域
本发明实施例涉及通信技术，尤其涉及一种路由规则的获取方法、设备和***。
背景技术
移动边缘计算(英文：Mobile Edge Computing，简称：MEC)的含义是在靠近移动用户的无线接入网上提供互联网服务环境和云计算能力，创造了一个高度分布的环境用来部署应用和服务，并且MEC可以存储和处理数据；还可以开放实时的无线网络信息，为移动用户提供个性化、上下文相关的业务体验。
图1为MEC***的一种架构示意图，如图1所示，该MEC***包括MEC基础设施、和MEC应用平台，以及多个虚拟的MEC应用(英文：application，简称：APP)，MEC的基础设施包括MEC硬件资源和MEC虚拟层，用于为MEC应用平台提供硬件支撑和服务，MEC应用平台包括管理器和多个虚拟的应用服务，例如数据流分发(英文：Traffic Offload Function，简称：TOF)、无线网信息开放服务、通信服务和服务注册等，这些服务可以被MEC的APP调用，实现对应的功能。在MEC***中，数据包需要根据预先配置的转发路径在不同的服务或者应用之间传输，以使数据能够根据用户需求被传输至正确的服务或者应用，得到正确的处理。
但是，虚拟的应用或者服务可以不断改变，如何动态确定数据将要传输的路径，仍然还没有得到解决，导致在MEC中路由数据时，按照配置的路径去转发，导致数据路由错误。
发明内容
本发明实施例提供一种路由规则的获取方法、设备和***，用于解决虚拟的应用或者服务可以不断改变，在MEC中路由数据时，数据传输路径不能动态确定，按照配置的路径去转发，导致数据路由错误的问题。
本发明第一方面提供一种路由规则的获取方法，应用于移动边缘计算MEC***，所述MEC***包括数据总线控制器和数据总线，所述方法包括：
数据总线控制器获取所述MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
结合第一方面，在第一方面的第一种可能的实施方式中，所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，包括：
所述数据总线控制器根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
结合第一方面的第一种可能的实施方案，在第一方面的第二种可能的实施方式中，每个过滤器还用于指示对应的路径的基站地址和/或网关地址。
结合第一方面、第一方面的第一种或者第二种可能的实施方案，在第一方面的第三种可能的实施方式中，所述数据总线控制器获取所述MEC***中至少一种业务的业务信息，包括：
所述数据总线控制器接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
或者，
所述数据总线控制器接收所述MEC***中每个业务上报的业务信息；
或者，
所述数据总线控制器接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
结合第一方面、第一方面的第一种至第三种中的任一种可能的实施方案，在第一方面的第四种可能的实施方式中，所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识 的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
结合第一方面的第一种可能的实施方案，在第一方面的第五种可能的实施方式中，所述数据总线包括分类器和业务转发器，则所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将所述数据包进行转发至所述服务列表中的每个业务，包括：
所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
本发明第二方面提供一种数据总线控制器，包括：
获取模块，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
处理模块，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
发送模块，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
结合第二方面，在第二方面的第一种可能的实施方式中，所述处理模块具体用于：
根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
结合第二方面或者第二方面的第一种可能的实施方式，在第二方面的第二种可能的实施方式中，所述获取模块包括：
第一接收单元，用于接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
或者，
第二接收单元，用于接收所述MEC***中每个业务上报的业务信息；
或者，
第三接收单元，用于接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
结合第二方面、第二方面的第一种或者第二种可能的实施方案，在第二方面的第三种可能的实施方式中，所述处理模块生成的所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
结合第二方面的第三种可能的实施方案，在第二方面的第四种可能的实施方式中，所述数据总线包括分类器和业务转发器，则所述发送模块包括：
第一发送单元，用于将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
第二发送单元，用于将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
本发明第三方面提供一种数据总线控制器，包括：
接收器，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
处理器，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
发送器，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
本发明第四方面提供一种路由规则的获取***，包括：数据总线控制器、数据总线；
数据总线控制器获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
所述数据总线控制器将所述路由规则发送至数据总线；
所述数据总线接收所述数据总线控制器发送的所述路由规则，并根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
结合第四方面，在第四方面的第一种可能的实施方式中，所述数据总线控制器具体用于：
根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
结合第四方面或者第四方面的第一种可能的实施方式，在第四方面的第二种可能的实施方式中，所述***还包括：至少一个业务、服务注册装置；
所述MEC***中每个业务向所述服务注册装置发送所述业务的业务信息；
所述服务注册装置接收所述至少一个业务发送的业务信息；
所述服务注册装置将所述至少一个业务的业务信息发送至所述数据总线控制器；
所述数据总线控制器接收服务注册装置发送的所述至少一个业务的业务信息。
结合第四方面或者第四方面的第一种可能的实施方式，在第四方面的第三种可能的实施方式中，所述***还包括：至少一个业务；
所述MEC***中每个业务向所述数据总线控制器发送所述业务的业务信息；
所述数据总线控制器接收每个业务上报的业务信息；
结合第四方面或者第四方面的第一种可能的实施方式，在第四方面的第四种可能的实施方式中，所述***还包括：业务管理器；
所述业务管理器获取所述MEC***中至少一个业务的业务信息，并将所述至少一个业务的业务信息发送至所述数据总线控制器；
所述数据总线控制器接收业务管理器发送的至少一个业务的业务信息。
结合第四方面、第四方面的第一种至第四种中的任一种可能的实施方式，在第四方面的第五种可能的实施方式中，所述数据总线控制器生成的路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
结合第四方面的第五种可能的实施方式，在第四方面的第六种可能的实施方式中，所述数据总线包括分类器和业务转发器，则所述数据总线控制器将所述路由规则发送至数据总线包括：
所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器；
所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器；
所述数据总线接收所述数据总线控制器发送的所述路由规则，并根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务，包括：
所述分类器接收所述数据总线控制器发送的所述至少一个过滤器和所述路径标识列表；
所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
所述业务转发器接收所述分类器发送的增加了第一路径标识后的数据包；
所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
本发明提供的路由规则的获取方法、设备和***，应用于MEC***，数据总线控制器获取MEC***中至少一种业务的业务信息，并根据至少一种业 务的业务信息，生成路由规则，指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；将路由规则发送至数据总线，以使数据总线更新新的路由规则，将接收到的数据包转发至数据包对应的业务，通过动态获取所有业务的业务信息，对路由规则中指示的路径进行更新，增加业务的路径，保证在接收到数据后可以根据新的路由规则进行转发，将数据正确路由到对应的业务，保证数据路由的正确性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为MEC***的一种架构示意图；
图2为本发明提供的MEC架构示意图；
图3为本发明路由规则的获取方法实施例一的流程图；
图4为本发明路由规则的获取方法实施例二的流程图；
图5为本发明路由规则的获取***的实施例一的交互图；
图6为本发明路由规则的获取***的实施例二的交互图；
图7为本发明路由规则的获取***的实施例三的交互图；
图8为本发明路由规则的获取***的实施例四的交互图；
图9为本发明路由规则的获取***的实施例五的交互图；
图10为本发明数据总线控制器实施例一的结构示意图；
图11为本发明数据总线控制器实施例二的结构示意图；
图12为本发明数据总线控制器实施例三的结构示意图；
图13为本发明数据总线控制器实体实施例的示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于 本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明将给出一种MEC***中的数据的路由方法，主要实现过程是MEC中的数据总线(英文Traffic Bus，简称：TB)控制器从服务或者应用(英文：Service/App)、服务注册(英文：Service Registry，简称：SR)、运营支撑***(英文：Operation support system，简称：OSS)或者业务支撑***(英文：Business support system，简称：BSS)得到服务或者应用的业务信息(也称为状态信息)；然后根据获取到的所有应用或服务的业务信息，制定路由规则，包括其生成的业务链路径；最后发送至更新TB，对TB中的路由规则进行更新，或者分别更新分类器(即实现分类功能的器件)和业务转发器(英文：Service Function Forwarder，简称：SFF)的规则，以便对数据总线能够按照新的路由规则对接收到数据包进行转发。MEC也被称作mobile edge platform或者mobile edge system。
本发明的技术方案应用于MEC架构中，图2为本发明提供的MEC架构示意图，如图2所示，该架构中包括TB控制器、数据总线连接(数据总线包括数据转发器和分类器)、服务总线、服务注册中心(也称为服务注册装置)以及至少一个可以提高的服务或者应用，例如：网关(英文：Gateway，简称：GW)、用户卡(英文：User Plane，简称：UP)服务、核心网信息开放服务(英文：Core Network Information Service，简称：CNIS)、无线网信息开放服务(英文：Radio Network Information Service，简称：RNIS等各种服务或者应用(英文：application，简称：APP)。TB控制器可以通过数据总线和服务总线直接与注册中心、应用或者服务交互。在该MEC架构中，分类器用于接收数据包，选择数据路由的路径，数据转发器用于根据分类器确定的路由路径转发数据包到正确的服务或者应用，TB控制器用于下发包括各种路径信息的路由规则给分类器和/或数据转发器。
图3为本发明路由规则的获取方法实施例一的流程图，如图3所示，该方法应用于MEC***，在图2所示的MEC架构的基础上，该方案的执行主体为数据总线控制器，该路由规则的获取方法的具体步骤包括：
S101：数据总线控制器获取MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识。
在本实施例中，业务包括服务或者应用(Service/App)，在MEC***中实例化一个应用或者服务时，数据总线控制器需要获取该应用或者服务的信息，例如：MEC新增一个Service(或者删除一个Service)都需要重新获取业务的业务信息，每个Service的业务信息包括Service标识(英文：identity，简称：ID)和Service Type，具体的数据总线控制器获取业务信息的方式至少包括以下几种：
第一种方式，所述数据总线控制器接收服务注册装置发送的所述MEC***中至少一个业务的业务信息。
在服务或者应用安装完成后，服务或者应用的实例向服务注册装置(也称为服务注册中心)进行注册，携带的参数包括该服务或者应用的标识和类型。服务注册装置将新注册的服务或应用的业务信息主动发送给所述数据总线控制器。
第二种方式，所述数据总线控制器接收所述MEC***中每个业务上报的业务信息。
在服务或应用安装时获取所述数据总线控制器的地址；在安装完成后，服务或应用向数据总线控制器发送更新消息，其中包括该应用或服务的业务标识或业务类型。
第三种方式，所述数据总线控制器接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
在服务或应用安装完成后，管理MEC的业务管理器会将新安装的服务或应用的信息发送至数据总线控制器，请求更新数据总线控制器中的可用的服务或应用，业务消息包括业务标识和业务类型。
上述提供了三种数据总线控制器获取MEC中业务或应用的业务信息的方式，但是并不限于只有上述的几种方式，通过任何方式得到目前MEC***中所有的可用的业务的业务信息即可，具体实现不做限制。
S102：所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识。
在本实施例中，数据总线控制器根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，具体的协议中 规定了根据业务标识和/或业务类型得到对应的过滤器的具体规则。路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识。这里的“可通过”的含义是指所有可能实现的路径，并不限于一个。此处的数据包也是广义的数据包，不限于特定的数据包，该路由规则中包括接收到的数据可能通过的所有路径。
具体实现中，得到的所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息，每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。路径信息指示的该路径包括的至少一个业务的业务标识。
可选的，每个过滤器至少还可以用于指示对应的路径的基站地址和/或网关地址。
S103：所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
在本实施例中，数据总线控制器在得到新的路由规则之后，将该路由规则发送给数据总线，数据总线对原有的路由规则进行更新，更新包括了MEC***中所有的应用或服务的新的路由规则。如果有数据包发送到数据总线，则根据新的路由规则，对该数据进行分类和转发，将该数据包发送到目标服务或者应用。
本实施例提供的路由规则的获取方法，应用于MEC***，数据总线控制器获取MEC***中业务的业务信息，并根据至少一种业务的业务信息，生成路由规则，指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；将路由规则发送至数据总线，通过动态获取业务信息，对路由规则中指示的路径进行更新，增加包括改变的业务的路径，保证在接收到数据后可以根据新的路由规则进行转发，避免出现改变了的应用收不到数据的问题，将数据正确路由到对应的服务或应用，保证数据路由的正确性。
图4为本发明路由规则的获取方法实施例二的流程图，如图4所示，该方法应用于MEC***，在图2所示的MEC架构的基础上，可知所述数据总线包括分类器和业务转发器，在上述实施例一的基础上，所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过 滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识，则上述步骤S103中所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将所述数据包进行转发至所述服务列表中的每个业务的具体实现包括以下两个步骤：
S201：所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器。
在本实施例中，路由规则具体包括几个部分，包括至少一个过滤器，还包括路径标识列表和至少一个路径信息。其中，路径标识列表包括每个过滤器和路径标识的对应关系，且路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识，在向数据总线发送路由规则时进行分别发送，最终通过路径标识将过滤器和路径的至少一个业务对应起来。
具体的，所述数据总线控制器将至少一个过滤器和所述路径标识列表发送给数据总线中的分类器。分类器在接收到一个数据包时候，根据数据包的具体信息，确定该数据包对应的第一路径标识，并将该第一路径标识增加到该数据包中，一般为增加字段表示该第一路径标识。并将增加了第一路径标识后的数据包发送给数据转发器。
S202：所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
在本实施例中，数据总线控制器将路径标识列表和至少一个路径信息发送给所述业务转发器，在数据转发器接收到分类器发送的增加了第一路径标识的数据包之后，根据该第一路径标识、路径标识列表和至少一个路径信息，得到该数据包的路径信息，然后将该数据包转发至对应的路径上的业务，即服务或应用。
本实施例提供的路由规则的获取方法，数据总线控制器获取MEC***所有的业务的业务信息，并根据至少一种业务的业务信息，生成路由规则，包括过滤器、路径信息和路径标识列表，将该路由规则分别发送给分类器和数 据转发器，通过路径标识列表关联过滤器和路径信息，当数据总线接收到数据包时，分配器根据过滤器确定路径标识，然后发送给数据转发器，数据转发器根据该数据包的路径标识得到对应的路径信息，并将该数据包转发给对应的应用或服务，根据实时获取的所有业务或应用的业务信息，灵活定制新的路由规则，快速的部署所有的业务路径，在接收到数据包后正确控制数据的流向，将数据正确的路由到对应的服务或应用中。
上述的两个实施例的执行主体针对的都是数据总线控制器，下面以整个***为主体，具体说明本发明的技术方案的具体实现过程。
该路由规则的获取***至少包括数据总线控制器、数据总线；数据总线控制器获取移动边缘计算MEC***中的至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；所述数据总线控制器将所述路由规则发送至数据总线；所述数据总线接收所述数据总线控制器发送的所述路由规则，并根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。下面通过几个交互的实施例具体说明该***实现路由规则的获取方法的过程。
图5为本发明路由规则的获取***的实施例一的交互图，如图5所示，该***中包括至少一个服务或应用，业务注册中心，TB控制器，和数据总线，每个部分之间的交互方式参考图2，则该方案的具体实现步骤为：
S301：安装服务/应用。
S302：向服务注册中心发送注册信息，包括该服务/应用的业务标识和业务类型。
S303：服务注册中心向服务或应用返回注册确认消息。
具体的，在Service/App安装完成后，Service/App的实例向服务注册中心注册，携带的参数包括Service ID和Service Type。注册成功后服务注册中心向Service/App返回确认消息，确认该应用或者服务注册成功。
S304：服务注册中心向TB控制器发送服务/应用更新消息，该应用更新消息包括业务标识和业务类型。
具体的过程为：所述MEC***中每个业务向所述服务注册装置发送所述 业务的业务信息；所述服务注册装置接收所述至少一个业务发送的业务信息；所述服务注册装置将所述至少一个业务的业务信息发送至所述数据总线控制器；所述数据总线控制器接收服务注册装置发送的所述至少一个业务的业务信息。即服务注册中心向TB Controller请求更新可用的Service/App，参数包括Service ID和Service Type。
S305：TB控制器生成路由规则。
具体的，根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
S306：TB控制器将生成的路由规则发送给数据总线。
数据总线对接收到的数据包根据新的路由规则进行分类和转发，将数据包发送至目的应用或服务。
图6为本发明路由规则的获取***的实施例二的交互图，如图6所示，该***中包括至少一个服务或应用，业务注册中心，TB控制器，和数据总线，数据总线包括分类器和数据转发器，每个部分之间的交互方式参考图2，则该方案的具体实现步骤为：
S401：安装服务/应用。
S402：向服务注册中心发送注册信息，包括该服务/应用的业务标识和业务类型。
S403：服务注册中心向服务或应用返回注册确认消息。
具体的，与图5所示的方案类似，在此不再赘述。
S404：服务注册中心向TB控制器发送服务/应用更新消息，该应用更新消息包括业务标识和业务类型。
具体的，该更新消息可以包括如下表1的内容：
表1表示APP的业务信息
APP ID APP type
App IP 网页
App IP 文件
APP IP 通用
S405：TB控制器生成路由规则，所述路由规则包括至少一个过滤器、路径标识列表和至少一个路径信息。
具体的，根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。该路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
继续上述实例，下表2中示出了路由规则中几种过滤器的实例，其中，路径的源地址、目的地址、发送协议、源端口号和目的端口号需要明确指出，另外基站地址和网关地址可根据实际情况确定。
表2表示几种路由规则中过滤器实例
Figure PCTCN2015085805-appb-000001
S406：TB控制器将所述至少一个过滤器和路径标识列表发送至分类器。
根据上述的例子，路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识，如表3中的业务链对应的下一跳的应用的地址或者是服务的地址，以便数据总线能够按照该路由规则进行数据包的转发，将数据包送达对应的应用或服务。
表3表示一种路径信息的表示方式实例
路径标识 Index 下一跳
Path_A 1 应用2(APP IP)
Path_A 0 服务1(地址)
Path_B 1 新应用(IP)
Path_B 0 服务3(地址)
S407：TB控制器将所述至少一个路径信息和路径标识列表发送至分类器。
具体的实现过程中，所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器；所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器；所述分类器接收所述数据总线控制器发送的所述至少一个过滤器和所述路径标识列表；所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；所述业务转发器接收所述分类器发送的增加了第一路径标识后的数据包；所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
图7为本发明路由规则的获取***的实施例三的交互图，如图7所示，该***中包括至少一个服务或应用，TB控制器，和数据总线，数据总线，每个部分之间的交互方式参考图2，则该方案的具体实现步骤为：
S501：服务/应用安装并获取TB控制器的地址。
S502：服务/应用实例向TB控制器发送服务/应用更新消息，该应用更新消息包括业务标识和业务类型。
具体的，所述MEC***中每个业务向所述数据总线控制器发送所述业务的业务信息；所述数据总线控制器接收每个业务上报的业务信息。
S503：TB控制器生成路由规则。
具体的，根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
S504：TB控制器将生成的路由规则发送给数据总线。
在本方案的具体实现中，该路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
也可以将路由规则分别发送给分类器和数据转发器，实现数据包的分类 和转发，实现方式类似于图6所示的方案。
图8为本发明路由规则的获取***的实施例四的交互图，如图8所示，该***中包括服务控制器，TB控制器，和数据总线，则该方案的具体实现步骤为：
S601：控制安装服务/应用。
S602：服务控制器向TB控制器发送服务/应用更新消息，该应用更新消息包括业务标识和业务类型。
具体的，在Service/App安装完成后,服务控制器(也称为管理单元)向TB控制器请求更新可用的Service/App，参数包括Service ID和Service Type。具体步骤：所述业务管理器获取所述MEC***中至少一个业务的业务信息，并将所述至少一个业务的业务信息发送至所述数据总线控制器；所述数据总线控制器接收业务管理器发送的至少一个业务的业务信息。
S603：TB控制器生成路由规则。
S604：TB控制器将生成的路由规则发送给数据总线。
在本方案的具体实现中，与上述实施例类似，在此不再赘述。
也可以将路由规则分别发送给分类器和数据转发器，实现数据包的分类和转发，实现方式类似于图6所示的方案。
图9为本发明路由规则的获取***的实施例五的交互图，如图9所示，该***中包括至少一个服务或应用，业务注册中心，TB控制器，和数据总线，每个部分之间的交互方式参考图2，则该方案的具体实现步骤为：
S701：安装服务/应用。
S702：向服务注册中心发送注册信息，包括该服务/应用的业务标识和业务类型。
S703：服务注册中心向服务或应用返回包括TB控制器地址的注册确认消息。
具体的，在Service/App安装完成后，Service/App的实例向服务注册中心注册，携带的参数包括Service ID和Service Type。注册成功后服务注册中心向Service/App返回包括TB控制器地址的注册确认消息，确认该应用或者服务注册成功。
S704：服务/应用实例向TB控制器发送服务/应用更新消息，该应用更新 消息包括业务标识和业务类型。
具体的过程为：所述MEC***中每个业务向所述服务注册装置发送所述业务的业务信息；所述服务注册装置接收所述至少一个业务发送的业务信息；所述服务注册装置将所述至少一个业务的业务信息发送至所述数据总线控制器；所述数据总线控制器接收服务注册装置发送的所述至少一个业务的业务信息。即服务注册中心向返回的TB控制器的地址对应的TB控制器请求更新可用的Service/App，参数包括Service ID和Service Type。
S705：TB控制器生成路由规则。
具体的，根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
可选的，在本步骤之前，TB控制器还可以从服务管理器中获取MEC***中服务或应用的优先级，在生成路由规则的过程中结合优先级进行处理。
S706：TB控制器将生成的路由规则发送给数据总线。
数据总线对接收到的数据包根据新的路由规则进行分类和转发，将数据包发送至目的应用或服务，具体的实现过程中，也可以像图6所示的将路由规则分别发送给数据总线的分类器和数据转发器，在此不再赘述。
在上述任一实施例中，提及的服务控制器具体实现时可以是OSS/BSS，TB控制器可以直接访问OSS/BSS，获取服务或应用的相关信息。
图10为本发明数据总线控制器实施例一的结构示意图，如图10所示，该数据总线控制器10包括：获取模块11、处理模块12和发送模块13；
获取模块11，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
处理模块12，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
发送模块13，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
可选的，所述处理模块12具体用于：
根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
可选的，所述处理模块12生成的所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
本实施例提供的数据总线控制器，用于执行图3至图9任一所示的技术方案中数据总线控制器的技术方案，通过动态获取MEC***中的所有业务的业务信息，对路由规则中指示的路径进行更新，增加业务的路径，保证在接收到数据后可以根据新的路由规则进行转发，避免出现部分应用收不到数据或者数据没有发送成功等问题，将接收到的数据正确路由到对应的应用或服务。
图11为本发明数据总线控制器实施例二的结构示意图，如图11所示，在上述图10所示的基础上，上述数据总线控制器10的所述获取模块11具体包括：
第一接收单元111，用于接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
或者，
第二接收单元112，用于接收所述MEC***中每个业务上报的业务信息；
或者，
第三接收单元113，用于接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
本实施例提供的数据总线控制器，用于执行图3至图9任一所示的技术方案中数据总线控制器的技术方案，其实现原理和技术效果类似，在此不再赘述。
图12为本发明数据总线控制器实施例三的结构示意图，如图12所示，在上述图10或11所示的基础上，所述数据总线包括分类器和业务转发器，则上述数据总线控制器10的所述发送模块13包括：
第一发送单元131，用于将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
第二发送单元132，用于将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
本实施例提供的数据总线控制器，用于执行图3至图9任一所示的技术方案中数据总线控制器的技术方案，其实现原理和技术效果类似，在此不再赘述。
图13为本发明数据总线控制器实体实施例的示意图，如图13所示，该数据总线控制器具体实现为：接收器21、处理器22和发送器23；
接收器21，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
处理器22，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
发送器23，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
具体实现中，所述处理器22具体用于：根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
每个过滤器还用于指示对应的路径的基站地址和/或网关地址。
所述接收器21具体用于：接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
或者，接收所述MEC***中每个业务上报的业务信息；
或者，接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
可选的，所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
所述数据总线包括分类器和业务转发器，则所述发送器23具体用于：
将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
本实施例提供的数据总线控制器，用于执行图2至图9所示的方法实施例中站点的方案，其实现原理和技术效果类似，在此不再赘述。
在上述数据总线控制器的实施例中，应理解，该处理器可以是中央处理单元(英文：Central Processing Unit，简称：CPU)，还可以是其他通用处理器、数字信号处理器(英文：Digital Signal Processor，简称：DSP)、专用集成电路(英文：Application Specific Integrated Circuit，简称：ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：只读存储器(英文：read-only memory，缩写：ROM)、RAM、快闪存储器、硬盘、固态硬盘、磁带(英文：magnetic tape)、软盘(英文：floppy disk)、光盘(英文：optical disc)及其任意组合。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (18)

  1. 一种路由规则的获取方法，应用于移动边缘计算MEC***，所述MEC***包括数据总线控制器和数据总线，其特征在于，所述方法包括：
    数据总线控制器获取所述MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
    所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
    所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
  2. 根据权利要求1所述的方法，其特征在于，所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，包括：
    所述数据总线控制器根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
  3. 根据权利要求1或2所述的方法，其特征在于，所述数据总线控制器获取所述MEC***中至少一种业务的业务信息，包括：
    所述数据总线控制器接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
    或者，
    所述数据总线控制器接收所述MEC***中每个业务上报的业务信息；
    或者，
    所述数据总线控制器接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
  5. 根据权利要求2所述的方法，其特征在于，所述数据总线包括分类器 和业务转发器，则所述数据总线控制器将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将所述数据包进行转发至所述服务列表中的每个业务，包括：
    所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
    所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
  6. 一种数据总线控制器，其特征在于，包括：
    获取模块，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
    处理模块，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
    发送模块，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
  7. 根据权利要求6所述的数据总线控制器，其特征在于，所述处理模块具体用于：
    根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
  8. 根据权利要求6或7所述的数据总线控制器，其特征在于，所述获取模块包括：
    第一接收单元，用于接收服务注册装置发送的所述MEC***中至少一个业务的业务信息；
    或者，
    第二接收单元，用于接收所述MEC***中每个业务上报的业务信息；
    或者，
    第三接收单元，用于接收业务管理器发送的所述MEC***中至少一个业务的业务信息。
  9. 根据权利要求6至8任一项所述的数据总线控制器，其特征在于，所述处理模块生成的所述路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
  10. 根据权利要求9所述的数据总线控制器，其特征在于，所述数据总线包括分类器和业务转发器，则所述发送模块包括：
    第一发送单元，用于将所述至少一个过滤器和所述路径标识列表发送给所述分类器，以使所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
    第二发送单元，用于将所述路径标识列表和至少一个路径信息发送给所述业务转发器，以使所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
  11. 一种数据总线控制器，其特征在于，包括：
    接收器，用于获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
    处理器，用于根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
    发送器，用于将所述路由规则发送至数据总线，以使所述数据总线根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
  12. 一种路由规则的获取***，其特征在于，包括：数据总线控制器、数据总线；
    数据总线控制器获取移动边缘计算MEC***中至少一种业务的业务信息；每个业务的业务信息包括业务类型和业务标识；
    所述数据总线控制器根据所述至少一种业务的业务信息，生成路由规则，所述路由规则用于指示数据包可通过的至少一个路径，每个路径包括至少一个业务的业务标识；
    所述数据总线控制器将所述路由规则发送至数据总线；
    所述数据总线接收所述数据总线控制器发送的所述路由规则，并根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务。
  13. 根据权利要求12所述的***，其特征在于，所述数据总线控制器具体用于：
    根据预先设置的路由规则生成协议和所述至少一种业务的业务类型和业务标识，获取所述路由规则，所述路由规则包括：至少一个过滤器和每个过滤器对应的路径信息；每个过滤器用于指示对应的路径的源地址、目的地址、发送协议、源端口号和目的端口号。
  14. 根据权利要求12或13所述的***，其特征在于，所述***还包括：至少一个业务、服务注册装置；
    所述MEC***中每个业务向所述服务注册装置发送所述业务的业务信息；
    所述服务注册装置接收所述至少一个业务发送的业务信息；
    所述服务注册装置将所述至少一个业务的业务信息发送至所述数据总线控制器；
    所述数据总线控制器接收服务注册装置发送的所述至少一个业务的业务信息。
  15. 根据权利要求12或13所述的***，其特征在于，所述***还包括：至少一个业务；
    所述MEC***中每个业务向所述数据总线控制器发送所述业务的业务信息；
    所述数据总线控制器接收每个业务上报的业务信息；
  16. 根据权利要求12或13所述的***，其特征在于，所述***还包括：业务管理器；
    所述业务管理器获取所述MEC***中至少一个业务的业务信息，并将所述至少一个业务的业务信息发送至所述数据总线控制器；
    所述数据总线控制器接收业务管理器发送的至少一个业务的业务信息。
  17. 根据权利要求12至16任一项所述的***，其特征在于，所述数据总线控制器生成的路由规则还具体包括：路径标识列表和至少一个路径信息；所述路径标识列表包括每个过滤器和路径标识的对应关系；路径信息包括路径标识与所述路径标识对应的至少一个业务的业务标识。
  18. 根据权利要求17所述的***，其特征在于，所述数据总线包括分类器和业务转发器，则所述数据总线控制器将所述路由规则发送至数据总线包括：
    所述数据总线控制器将所述至少一个过滤器和所述路径标识列表发送给所述分类器；
    所述数据总线控制器将所述路径标识列表和至少一个路径信息发送给所述业务转发器；
    所述数据总线接收所述数据总线控制器发送的所述路由规则，并根据所述路由规则，将接收到的数据包转发至所述数据包对应的业务，包括：
    所述分类器接收所述数据总线控制器发送的所述至少一个过滤器和所述路径标识列表；
    所述分类器根据所述至少一个过滤器和路径标识列表，确定接收到的数据包的第一路径标识，并在所述数据包中增加所述第一路径标识，将增加所述第一路径标识后的数据包发送给所述业务转发器；
    所述业务转发器接收所述分类器发送的增加了第一路径标识后的数据包；
    所述业务转发器根据所述路径标识列表、所述至少一个路径信息和所述第一路径标识，将接收到的所述过滤器发送的数据包转发至对应的业务。
PCT/CN2015/085805 2015-07-31 2015-07-31 路由规则的获取方法、设备和*** WO2017020203A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
PCT/CN2015/085805 WO2017020203A1 (zh) 2015-07-31 2015-07-31 路由规则的获取方法、设备和***
JP2018500770A JP6494150B2 (ja) 2015-07-31 2015-07-31 ルーティング規則取得方法、デバイス、およびシステム
EP15899978.9A EP3313027B1 (en) 2015-07-31 2015-07-31 Routing rule acquisition method and system
CN202010256137.9A CN111654433B (zh) 2015-07-31 2015-07-31 路由规则的获取方法、设备和***
CN201580042653.9A CN106576074B (zh) 2015-07-31 2015-07-31 路由规则的获取方法、设备和***
US15/883,732 US20180159765A1 (en) 2015-07-31 2018-01-30 Routing rule obtaining method, device, and system
US16/917,053 US20200336410A1 (en) 2015-07-31 2020-06-30 Routing rule obtaining method, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/085805 WO2017020203A1 (zh) 2015-07-31 2015-07-31 路由规则的获取方法、设备和***

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/883,732 Continuation US20180159765A1 (en) 2015-07-31 2018-01-30 Routing rule obtaining method, device, and system

Publications (1)

Publication Number Publication Date
WO2017020203A1 true WO2017020203A1 (zh) 2017-02-09

Family

ID=57942293

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/085805 WO2017020203A1 (zh) 2015-07-31 2015-07-31 路由规则的获取方法、设备和***

Country Status (5)

Country Link
US (2) US20180159765A1 (zh)
EP (1) EP3313027B1 (zh)
JP (1) JP6494150B2 (zh)
CN (2) CN106576074B (zh)
WO (1) WO2017020203A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818867A (zh) * 2017-11-21 2019-05-28 华为技术有限公司 一种配置方法及装置

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017020203A1 (zh) * 2015-07-31 2017-02-09 华为技术有限公司 路由规则的获取方法、设备和***
JP6424964B2 (ja) * 2015-08-20 2018-11-21 日本電気株式会社 通信システム、基地局装置、制御装置、及び通信方法
WO2017091934A1 (zh) * 2015-11-30 2017-06-08 华为技术有限公司 一种能力开放的实现方法、***及相关设备
CN109818868B (zh) * 2017-11-20 2021-06-22 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
CN110109931B (zh) * 2017-12-27 2021-08-24 航天信息股份有限公司 一种用于防止rac实例间数据访问发生冲突的方法及***
CN113364610B (zh) * 2018-03-30 2022-08-09 华为技术有限公司 网络设备的管理方法、装置及***
US11431648B2 (en) * 2018-06-11 2022-08-30 Intel Corporation Technologies for providing adaptive utilization of different interconnects for workloads
CN109639698B (zh) * 2018-12-24 2022-02-01 维沃移动通信有限公司 一种数据处理方法及服务器
CN110879819A (zh) * 2019-11-20 2020-03-13 北京明略软件***有限公司 路由信息快速准确识别方法、装置、服务器及存储介质
CN113472660B (zh) * 2020-03-31 2022-07-29 中移物联网有限公司 一种应用信息的路由方法及路由节点
US11284297B2 (en) 2020-04-06 2022-03-22 Cisco Technology, Inc. Secure creation of application containers for fifth generation cellular network slices
CN112153021B (zh) * 2020-09-10 2023-05-19 中国联合网络通信集团有限公司 一种业务数据的获取方法及装置
CN114172842B (zh) * 2020-09-10 2023-09-19 ***通信有限公司研究院 一种数据传输处理方法、装置、设备及可读存储介质
US11456951B1 (en) * 2021-04-08 2022-09-27 Xilinx, Inc. Flow table modification for network accelerators
CN113805975B (zh) * 2021-08-12 2022-06-21 荣耀终端有限公司 业务执行方法、装置和存储介质
CN114650252B (zh) * 2022-03-25 2023-11-21 华润数字科技(深圳)有限公司 基于企业服务总线的路由方法、装置及计算机设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2414626A (en) * 2004-05-20 2005-11-30 Sun Microsystems Inc Dynamic and distributed managed edge computing (MEC) framework
CN101309302A (zh) * 2008-06-30 2008-11-19 华为技术有限公司 一种基于应用服务器的信令分发方法及装置
CN103338206A (zh) * 2013-07-10 2013-10-02 中兴智能交通（无锡）有限公司 一种基于数据总线技术实现数据交换的方法及装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005012468A (ja) * 2003-06-18 2005-01-13 Nippon Telegr & Teleph Corp <Ntt> 双方向パケット転送システム及びパケット転送ルート設定方法
CN100384172C (zh) * 2004-01-20 2008-04-23 华为技术有限公司 基于网络的虚拟专用网中保证服务质量的***及其方法
US9165154B2 (en) * 2009-02-16 2015-10-20 Microsoft Technology Licensing, Llc Trusted cloud computing and services framework
US20120239727A1 (en) * 2011-03-16 2012-09-20 Kddi Corporation Multimedia service network and method for providing the same
US9397950B2 (en) * 2012-11-01 2016-07-19 Telefonaktiebolaget Lm Ericsson (Publ) Downlink service path determination for multiple subscription based services in provider edge network
WO2014186963A1 (zh) * 2013-05-23 2014-11-27 华为技术有限公司 业务路由***、设备和方法
CN104518967B (zh) * 2013-09-30 2017-12-12 华为技术有限公司 路由方法、设备和***
US20150124622A1 (en) * 2013-11-01 2015-05-07 Movik Networks, Inc. Multi-Interface, Multi-Layer State-full Load Balancer For RAN-Analytics Deployments In Multi-Chassis, Cloud And Virtual Server Environments
EP3528439A1 (en) * 2013-12-30 2019-08-21 Huawei Technologies Co., Ltd. Service routing method and system
CN103841022B (zh) * 2014-03-12 2017-04-05 华为技术有限公司 用于建立隧道的方法及装置
US10200258B2 (en) * 2014-08-14 2019-02-05 Juniper Networks, Inc. Transaction integrity for network services configuration
WO2016203798A1 (ja) * 2015-06-19 2016-12-22 ソニー株式会社 装置及び方法
CN108353029B (zh) * 2015-06-25 2021-02-26 Nec实验室欧洲有限公司 用于管理计算网络中的数据业务的方法和***
US20180212962A1 (en) * 2015-07-30 2018-07-26 Interdigital Patent Holdings, Inc. Enabling coordinated identity management between an operator-managed mobile-edge platform and an external network
WO2017020203A1 (zh) * 2015-07-31 2017-02-09 华为技术有限公司 路由规则的获取方法、设备和***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2414626A (en) * 2004-05-20 2005-11-30 Sun Microsystems Inc Dynamic and distributed managed edge computing (MEC) framework
CN101309302A (zh) * 2008-06-30 2008-11-19 华为技术有限公司 一种基于应用服务器的信令分发方法及装置
CN103338206A (zh) * 2013-07-10 2013-10-02 中兴智能交通（无锡）有限公司 一种基于数据总线技术实现数据交换的方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818867A (zh) * 2017-11-21 2019-05-28 华为技术有限公司 一种配置方法及装置
CN109818867B (zh) * 2017-11-21 2020-10-27 华为技术有限公司 一种配置方法及装置
US11570277B2 (en) 2017-11-21 2023-01-31 Huawei Technologies Co., Ltd. Configuration method and apparatus

Also Published As

Publication number Publication date
CN111654433B (zh) 2021-08-31
JP6494150B2 (ja) 2019-04-03
CN111654433A (zh) 2020-09-11
EP3313027A1 (en) 2018-04-25
CN106576074A (zh) 2017-04-19
US20200336410A1 (en) 2020-10-22
CN106576074B (zh) 2020-04-21
US20180159765A1 (en) 2018-06-07
JP2018523404A (ja) 2018-08-16
EP3313027A4 (en) 2018-07-11
EP3313027B1 (en) 2020-02-26

Similar Documents

Publication Publication Date Title
WO2017020203A1 (zh) 路由规则的获取方法、设备和***
Liu et al. A software defined network architecture for geobroadcast in VANETs
US8812726B2 (en) Service insertion in a computer network using internet protocol version 6 techniques
US9094482B2 (en) Apparatus and method for controlling data transmission/reception path between server and mobile terminal in heterogeneous network environment
EP2731313B1 (en) Distributed cluster processing system and message processing method thereof
US11368525B2 (en) Relaying network management tasks using a multi-service receptor network
WO2015139310A1 (zh) 一种业务分配的处理方法及相关装置
EP3253091B1 (en) Data processing method and equipment
CN114143283B (zh) 一种隧道自适应配置方法、装置，中心端设备及通信***
WO2018068588A1 (zh) 提供组播业务的方法和软件定义网络控制器
CN108964961A (zh) 一种管理传输网切片的方法、装置及***
US20180076879A1 (en) Method and apparatus for providing relay service
US20230269164A1 (en) Method and apparatus for sending route calculation information, device, and storage medium
WO2018161795A1 (zh) 一种路由优先级配置方法、设备以及控制器
CN109041086A (zh) 一种OpenFlow实例的配置方法及装置
WO2017124712A1 (zh) 报文生成方法、报文转发方法及装置
CN112187635B (zh) 报文转发方法及装置
CN112751766A (zh) 报文转发方法、装置及计算机存储介质
US20230119919A1 (en) Service realization using a segmented mpls control plane
CN114745375B (zh) 业务功能实现方法、装置及电子设备
WO2017164068A1 (ja) トランスポートネットワーク制御装置、通信システム、転送ノードの制御方法及びプログラム
US8645564B2 (en) Method and apparatus for client-directed inbound traffic engineering over tunnel virtual network links
CN115118544B (zh) 通信方法及设备、通信***
CN116319514B (zh) 一种数据处理方法和相关装置
CN117499327A (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: 15899978

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018500770

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE