WO2016078450A1 - 一种业务链中的数据处理方法及设备、存储介质 - Google Patents

一种业务链中的数据处理方法及设备、存储介质 Download PDF

Info

Publication number
WO2016078450A1
WO2016078450A1 PCT/CN2015/086957 CN2015086957W WO2016078450A1 WO 2016078450 A1 WO2016078450 A1 WO 2016078450A1 CN 2015086957 W CN2015086957 W CN 2015086957W WO 2016078450 A1 WO2016078450 A1 WO 2016078450A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
service
enabler
data flow
identifier
Prior art date
Application number
PCT/CN2015/086957
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 WO2016078450A1 publication Critical patent/WO2016078450A1/zh

Links

Images

Definitions

  • the present invention relates to network data processing technologies, and in particular, to a data processing method and device, and a storage medium in a service chain.
  • the current carrier network is divided into a mobile network domain and a mobile service domain behind the Gi interface.
  • the basic network that carries the service and the network that handles the service are deployed separately, which makes it easier for the operator to operate and maintain the network.
  • Figure 1 shows the deployment status of the mobile service network.
  • multiple service enablers Service Enabler
  • GW, GateWay such as the Gateway GPRS Support Node (GGSN) or the Packet Data Network (P-GW, Packet Data Network), based only on the access point name (APN, Access Point) Name) Simple and coarse-grained classification of service data.
  • GGSN Gateway GPRS Support Node
  • P-GW Packet Data Network
  • APN Access Point
  • APN Access Point
  • Service Enabler Packet Data Network
  • the complexity of the manual configuration is high, and the failure of a single service enabler causes the entire service chain to be invalid, and the processing delay and the expansion cost are relatively high.
  • the embodiment of the present invention provides a data processing method and device, and a storage medium in a service chain, to solve at least one problem existing in the prior art.
  • the technical solution of the embodiment of the present invention is implemented by: receiving a first service data flow including a link identifier from the service switch SW; recording a correspondence between the link identifier and a medium access control MAC translation address; The enabler sends a second service data stream, where the second service data stream includes a MAC translation address.
  • the recording the correspondence between the link identifier and the MAC address including: converting the source MAC address included in the first service data stream according to the setting rule to obtain a MAC address; and recording the link
  • the correspondence between the identifier and the MAC translation address is identified.
  • the method before the sending, by the service enabler, the second service data flow, the method further includes: deleting a link identifier included in the first service data flow, and generating a second service data flow.
  • the method before the generating the second service data stream, the method further includes: deleting the service enabler identifier included in the first service data stream.
  • the sending, by the service enabler, the second service data flow includes: a correspondence between the configured self-link interface and the service enabler, and a service enabler identifier included in the first service data flow. Transmitting, by the corresponding link interface, a second service data flow to the service enabler.
  • the method before the receiving, by the SW, the first service data stream that includes the link identifier, the method further includes: recording a correspondence between the configured self-link interface and the service enabler.
  • the method further includes: receiving a third service data flow from the service enabler; and corresponding to the MAC address according to the recorded link identifier And determining, by the relationship, a link identifier corresponding to the MAC translation address included in the third service data stream; and transmitting, to the SW, a fourth service data flow including the link identifier.
  • the method before the sending, by the SW, the fourth service data flow that includes the link identifier, the method further includes: inversely converting the MAC address included in the third service data stream according to the setting rule. The address is obtained as the MAC address of the destination MAC address of the service data.
  • the method before the sending, by the SW, the fourth service data flow that includes the link identifier, the method further includes: performing, according to the configured link interface, a correspondence between the link interface and the service enabler, and receiving the third service The link interface of the data stream determines the corresponding service enabler identifier.
  • the sending, by the SW, the fourth service data flow that includes the link identifier includes: sending a fourth service data flow to the SW, where the fourth service data flow includes a link identifier, a service enabler identifier, and a MAC Address and business data.
  • a storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations described above.
  • a data processing method in a service chain comprising: receiving a third service data flow from a service enabler; determining, corresponding to a third service, according to a correspondence between a recorded link identifier and a medium access control MAC translation address A link identifier of a MAC address translated in the data stream; sending a fourth service data stream including the link identifier to the SW.
  • the method before the sending, by the SW, the fourth service data stream that includes the link identifier, the method further includes: inversely converting the MAC address translated in the third service data stream according to the setting rule, and obtaining the data as the service data. MAC address of the destination MAC address.
  • the method before the sending, by the SW, the fourth service data flow that includes the link identifier, the method further includes: performing, according to the configured link interface, a correspondence between the link interface and the service enabler, and receiving the third service The link interface of the data stream determines the corresponding service enabler identifier.
  • the sending, by the SW, the fourth service data flow that includes the link identifier includes: sending a fourth service data flow to the SW, where the fourth service data flow includes a link identifier, a service enabler identifier, and a MAC Address and business data.
  • a storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations described above.
  • a processing device comprising:
  • a first receiving unit configured to receive a first service data flow that includes a link identifier from the service switch SW;
  • a recording unit configured to record a correspondence between the link identifier and a medium access control MAC translation address
  • the first sending unit is configured to send a second service data flow to the service enabler, where the second service data flow includes a MAC translation address.
  • the recording unit includes:
  • the conversion module is configured to convert the source MAC address included in the first service data stream according to the setting rule to obtain a MAC translation address
  • a recording module configured to record a correspondence between a link identifier included in the first service data flow and the MAC translation address
  • Deleting a module, configured to delete the link identifier and the enabler identifier included in the first service data flow;
  • the first generation module is configured to generate a second service data flow, where the second service data flow includes a MAC translation address.
  • the recording module is further configured to: record a correspondence between a service enabler identifier included in the first service data flow and the configured link interface and the service enabler.
  • the device further includes:
  • a second receiving unit configured to receive a third service data flow from the service enabler
  • the matching unit is configured to determine, according to the correspondence between the recorded link identifier and the MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream;
  • a second sending unit configured to send, to the SW, a fourth service data flow that includes the link identifier.
  • the matching unit includes:
  • the matching module is configured to correspond to the correspondence between the recorded link identifier and the MAC translation address. Determining a link identifier corresponding to a MAC translation address included in the third service data stream;
  • the inverse conversion module is configured to reverse convert the MAC address translated in the third service data stream according to the setting rule, to obtain a MAC address as a destination MAC address of the service data;
  • Adding a module configured to add a link identifier and an enabler identifier corresponding to the service data in the third service data flow;
  • the second generation module is configured to generate a fourth service data flow, where the fourth service data flow includes a link identifier, an enabler identifier, a MAC address, and service data.
  • the matching module is further configured to: determine a corresponding service enabler identifier according to a correspondence between the recorded link interface and the service enabler, and a link interface that receives the third service data flow.
  • a processing device comprising:
  • a receiving unit configured to receive a third service data flow from the service enabler
  • a matching unit configured to determine, according to a correspondence between the recorded link identifier and the medium access control MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream;
  • a sending unit configured to send, to the SW, a fourth service data flow that includes the link identifier.
  • the matching unit includes:
  • a matching module configured to determine, according to a correspondence between the recorded link identifier and the MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream;
  • the inverse conversion module is configured to reverse convert the MAC address translated in the third service data stream according to the setting rule, to obtain a MAC address as a destination MAC address of the service data;
  • Adding a module configured to add a link identifier and an enabler identifier corresponding to the service data in the third service data flow;
  • the generating module is configured to generate a fourth service data flow, where the fourth service data flow includes a link identifier, an enabler identifier, a MAC address, and service data.
  • the matching module is further configured to: determine a corresponding service enabler identifier according to a correspondence between the recorded link interface and the service enabler, and a link interface that receives the third service data flow.
  • the link identifier is completely unnecessary in the service data stream sent by the processing entity to the service enabler, and the service identifier is not required to identify the link identifier, which reduces the complexity of the service enabler.
  • the service data flow sent by the processing entity to the SW includes the link identifier, the SW can correctly find the corresponding service chain according to the link identifier, and there is no problem that the execution relationship of the service chain is disordered.
  • FIG. 1 is a schematic structural diagram of a mobile operation network deployment
  • FIG. 2 is a schematic diagram of a dynamic service chain
  • FIG. 3 is a schematic diagram of a service chain structure
  • Figure 4 is a schematic diagram 1 of the execution relationship of the service chain
  • Figure 5 is a schematic diagram 2 of the execution relationship of the service chain
  • FIG. 6 is a schematic diagram 1 of a data processing flow in a service chain according to an embodiment of the present invention.
  • FIG. 7 is a second schematic diagram of data processing in a service chain according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a data processing interaction process in a service chain according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram 1 of a processing device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram 2 of a processing device according to an embodiment of the present invention.
  • the demand for the dynamic service chain is proposed. It is hoped that the service enabler can be flexibly used according to the current needs, so as to reduce the cost of deploying the service enabler and improve the resource utilization rate.
  • the flexible and flexible service chain can select different value-added service chains for different access types, such as 2G/3G/4G, in order to provide different optimization measures. For example, the access mode with lower bandwidth can provide more video compression optimization services; for example, the corresponding value-added service chain is selected for different applications, and the service data without any added value can be directly bypassed without occupying the service.
  • Enabler resources for example, differentiated value-added services can be provided for different levels of paying users, and different service chains can be selected and established for the business data of gold, silver and bronze users; for example, for wireless access networks
  • Signal quality changes provide real-time optimization measures, such as when the network is congested, a service chain that provides acceleration for the business data.
  • FIG 2 shows the service chain that needs to be traversed by the service switch (SW, Service Switch) under the control of the service controller (SC), and the SC can be dynamically updated according to the policy.
  • Adjust the business chain that is, the business path that business data needs to go through.
  • the SC can control the SW by using the OpenFlow protocol.
  • the Openflow protocol uses the matching forwarding control logic to format the service path that the service data needs to pass.
  • the link ID (Chain ID) is used to identify the combination of the functional modules in the service chain, that is, the service path through which the service data needs to pass.
  • the link identifier 1 is used to identify the service path of the service chain 1, that is, the service data 1 shown in FIG. 2, as shown by the solid line in FIG. 2;
  • the identifier 2 is used to identify the service path of the service chain 2, that is, the service data 2 shown in FIG. 2, as shown by the dotted line in FIG.
  • the SC may send the service chain including the link identifier to the SW involved in the service chain in a flow table, so that the SW routes the service data according to the flow table.
  • the service chain identified by the service chain X indicates that the service data needs to pass through the SW1 and the SW2 in sequence, and the service data in the SW1 needs to pass through the service enabler 1, the service enabler 2, and the service in sequence. 3.
  • the service data needs to pass through the service enabler 4.
  • the service chain identified by the service chain Y indicates that the service data needs to pass through SW1, SW2, and then through SW1 in sequence.
  • the SW determines the location of the service data in the service processing according to the correspondence between the link identifier and the service enabler identifier, and further determines the next hop position of the service data.
  • the service enabler identifier here can be used to identify the service enabler or to identify the service that represents the function of the service enabler.
  • the link identifier can facilitate the SW to identify the service path of the service data. If the header information is retained during the transmission and processing of the service data stream, the SW can always obtain the obtained information. The header information correctly determines the service path of the service data flow.
  • the SW can only delete the header information before transmitting the service data stream to the service enabler to avoid the service enabler to the service data flow. Unpredictable processing errors occur when processing.
  • the link information of the service data flow does not include the link identifier.
  • the execution relationship of the service chain may be disordered. .
  • FIG. 4 and FIG. 5 after the service data flow is sent from the service enabler 2 to the SW1, if the link identifier does not exist in the header information of the service data flow, then the SW1 is based on the service data flow. It is not determined whether the service data stream is continually routed to the service enabler 3 in the service chain identified by the service chain X or to the service enabler 5 of the SW2 in the service chain identified by the service chain Y.
  • the service data refers to the data content corresponding to a specific service
  • the service data stream includes the service data, and also includes the link identifier, the service enabler identifier, and the like, and the information may be included in the service data flow.
  • the header information In the header information.
  • the first service data flow including the link identifier is received, and the correspondence between the link identifier and the media access control (MAC) conversion address is recorded;
  • the energy device sends a second service data stream, and the second service data stream includes a MAC address.
  • the third service data stream sent by the service enabler determines the link identifier corresponding to the destination MAC address included in the third service data stream according to the correspondence between the recorded link identifier and the MAC address.
  • FIG. 6 is a schematic diagram of a data processing process in a service chain according to an embodiment of the present invention. As shown in FIG. 6, data processing in a service chain includes the following steps:
  • Step 101 The processing entity receives the first service data stream from the SW that includes the link identifier.
  • the SC allocates the service chain identified by the link identifier according to the specific service type, and delivers the service chain to the SW involved in the service chain by sending the flow table.
  • the service chain includes the link identifier, the execution order of the SC, and the execution order of the service enablers in each SC.
  • the execution relationship in the flow table can be as shown in FIG. 4 and FIG. 5.
  • the SW determines the service enabler that the service data needs to pass, and sends the first service data flow including the link identifier, the service enabler identifier, and the service data to the processing entity.
  • the service enabler that the service data needs to pass through is the first service enabler that the SW needs to pass according to the service data determined by the service chain delivered by the SC, as shown in Figure 4 and Figure 5;
  • the SW may also be the next enabler that the determined service data needs to pass according to the link identifier included in the second service data stream processed by the processing entity sent by the processing entity, such as the service in FIG.
  • the processing entity in the embodiment of the present invention may be a physical device that is separately set in the mobile operation network, or may be a logical entity that is located in the same physical device as the SW.
  • the physical device can be a switch.
  • the processing entity and the SW are on the same physical device, the processing entity may be a separate process running in the physical device.
  • Step 102 The processing entity records a correspondence between the link identifier and a MAC translation address.
  • the processing entity After receiving the first service data flow from the SW, the processing entity converts the source MAC address included in the first service data flow according to the setting rule to obtain a MAC address, and records the link identifier included in the first service data stream.
  • the MAC translates the correspondence between the addresses, and deletes the link identifier included in the first service data stream to generate a second service data stream.
  • the setting rule may be a set conversion algorithm, such as selecting a setting bit of the source MAC address, such as a low 24 bits, adding a random number of the set number of bits before the selected partial MAC address, thereby forming a MAC conversion address; For another example, the setting bit of the source MAC address, such as the lower 24 bits, is selected, and the setting bit of the service enabler identifier is added before the selected partial MAC address, thereby forming a MAC translation address.
  • the source MAC address is the MAC address of the physical device where the processing entity is located.
  • the source MAC address is the MAC address of the physical device; if the processing entity and the SW are co-located on the same physical device, The source MAC address is the MAC address of the physical device where the processing entity and the SW are co-located.
  • the first service data stream received by the processing entity further includes a service enabler identifier, where the service enabler identifier is used to identify a service enabler that the service data currently needs to pass, and the processing entity further deletes the first step in step 102.
  • the service enabler identifier included in the service data flow to obtain a second service data flow that does not include the link identifier and the service enabler identifier.
  • the operation of deleting the service enabler identifier may be performed in the same manner as the foregoing operation of deleting the link identifier, that is, the link identifier and the service enabler included in the first service data flow are simultaneously deleted in one deletion operation.
  • Step 103 The processing entity sends a second service data flow to the service enabler, where the second service data flow includes a MAC translation address.
  • the MAC address translated in the second service data stream is a source MAC address of the service data.
  • the processing entity sends the second service data flow to the corresponding service enabler according to the service enabler identifier included in the received first service data flow.
  • the network administrator can configure different link interfaces of the processing entity to correspond to different service enablers, and store configuration information of the correspondence between the link interface and the service enabler to the processing entity.
  • the physical device so that the processing entity can send the second service data stream to the corresponding service through the corresponding link interface according to the corresponding relationship between the configured link interface and the service enabler and the corresponding service enabler identifier.
  • the link interface is a port or interface on the processing entity for transmitting service data to the service enabler.
  • a storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations corresponding to FIG. 6 above.
  • FIG. 7 is a schematic diagram 2 of a data processing flow in a service chain according to an embodiment of the present invention. As shown in FIG. 7, data processing in a service chain includes the following steps:
  • Step 201 The processing entity receives the third service data flow from the service enabler.
  • the processing entity sends the second service data stream to the corresponding service enabler according to the service enabler identifier included in the received first service data stream; after the service enabler receives the second service data stream, After processing the service data included in the second service data stream, the third service data stream is formed and sent to the processing entity, where the third service data stream includes the destination MAC address, and the destination MAC address is the second service data stream.
  • Source MAC address and MAC address translation included.
  • the network administrator can configure each service enabler to correspond to a different link interface of the processing entity, and
  • the link interface of the processing entity corresponding to the service enabler is stored to the service enabler, and when the service enabler sends the third service data flow to the processing entity, the third service data flow may be sent to the processing entity.
  • the link interface corresponding to the service enabler is stored to the service enabler, and when the service enabler sends the third service data flow to the processing entity, the third service data flow may be sent to the processing entity.
  • Step 202 The processing entity determines, according to the correspondence between the recorded link identifier and the MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream.
  • the third service data stream received by the processing entity includes the destination MAC address, and the processing entity records the link between the link identifier and the MAC translation address included in the first service data stream when receiving the first service data stream from the SW. Correspondence relationship, therefore, the processing entity can determine the link corresponding to the destination MAC address included in the third service data stream, that is, the MAC translation address, according to the correspondence between the recorded link identifier and the MAC translation address. logo.
  • the processing entity reverse-converts the destination MAC address, that is, the MAC address, included in the third service data flow according to the setting rule, and obtains the MAC address as the destination MAC address of the service data, where the MAC address is the processing entity.
  • the MAC address of the physical device is the MAC address of the physical device.
  • Step 203 The processing entity sends a fourth service data flow including the link identifier to the SW.
  • the link identifier is added to the third service data stream to form a fourth service data stream, and then the fourth service data stream is sent to the SW.
  • the processing entity may determine the corresponding service enabler identifier according to the corresponding relationship between the configured link interface and the service enabler and the link interface that receives the third service data flow. After the processing entity determines the service enabler identifier, the service enabler identifier is added to the third service data stream to form a fourth service data stream, and then the fourth service data stream is sent to the SW.
  • the operation of adding the service enabler identifier may be performed in the same manner as the foregoing operation of adding the link identifier, that is, adding the link identifier and the service enabler identifier in the third service data flow in one add operation. Forming a fourth business data stream.
  • the reversed translated MAC address may also be included in the fourth service data stream.
  • the SW can be based on the fourth service data.
  • the link identifier, or the link identifier, and the service enabler identifier included in the flow determine the next hop of the service data on the service chain. If the service data still needs to be processed in the SW, the SW sends the processing entity to the processing entity. Another first service data stream containing the link identifier; if the service data needs to be processed in another SW, triggering another SW to process the service data.
  • the processing entity may be in one-to-one correspondence with the SW, and the processing entities corresponding to the different SWs are processed according to the foregoing steps 101 to 103 or steps 201 to 203.
  • a storage medium comprising a set of instructions that, when executed, cause at least one processor to perform the operations corresponding to FIG. 7 above.
  • FIG. 8 is a schematic diagram of a data processing interaction process in a service chain according to an embodiment of the present invention. As shown in FIG. 8 , in combination with the service chain shown in FIG. 4 and FIG. 5, the data processing interaction process in the service chain includes the following steps:
  • Step 301 The SC arranges the service chain identified by the link identifier according to the specific service type, and delivers the service chain to the SW involved in the service chain by sending the flow table, as shown in FIG. 4 and FIG. 5, SW1 and SW2. .
  • the service chain includes the link identifier, the execution order of the SC, and the execution order of the service enablers in each SC.
  • the execution relationship in the flow table can be as shown in FIG. 4 and FIG. 5.
  • Steps 302 to 303 After receiving the service chain in the form of a flow table, the SW1 determines that the service enabler that is currently required to pass the service data, that is, the service enabler 1, generates the first service data flow, and the first service data flow includes the chain.
  • the road identifier and the service enabler identifier are the identifier of the service enabler 1, the source MAC address, and the service data.
  • the source MAC address is the MAC address of the physical device where the processing entity resides.
  • Step 304 SW1 sends a first service data stream to the processing entity.
  • Step 305 The processing entity receives the first service data stream, converts the source MAC address included in the first service data stream according to the setting rule to obtain a MAC address, and records the link identifier and MAC address included in the first service data stream. Corresponding relationship between addresses, deleting the link identifier and service enabler identifier included in the first service data flow, and using the MAC address as the number of services According to the source MAC address, the second service data stream is obtained, and the second service data stream includes the MAC address and the service data.
  • Step 306 The processing entity according to the corresponding relationship between the configured self-link interface and the service enabler, and the service enabler identifier included in the first service data flow, through the link interface of the corresponding service enabler 1
  • the service enabler 1 sends a second service data stream.
  • Step 307 The service enabler 1 receives the second service data stream, processes the service data included in the second service data stream, and uses the MAC address as the destination MAC address of the service data to obtain the third service data stream.
  • the three service data streams contain MAC translation addresses and service data.
  • Step 308 The service enabler 1 sends a third service data flow to the link interface of the corresponding service enabler 1 on the processing entity.
  • Step 309 The processing entity receives the third service data stream, and determines, according to the correspondence between the link identifier and the MAC address translated in step 305, the destination MAC address, that is, the MAC address translated in the third service data stream.
  • Link identifier
  • the processing entity reversely converts the destination MAC address, that is, the MAC address, according to the setting rule, to obtain a MAC address;
  • the processing entity determines the corresponding service enabler identifier according to the corresponding relationship between the configured self-link interface and the service enabler and the link interface that receives the third service data flow.
  • Step 310 The processing entity generates a fourth service data stream and sends the message to the SW1.
  • the fourth service data stream includes the link identifier, the service enabler identifier, and the destination MAC address, that is, the obtained MAC address and service data in step 309.
  • Step 311 The SW1 receives the fourth service data flow, and determines the next hop of the service data on the service chain, that is, the service enabler 2, according to the link identifier and the enabler identifier included in the fourth service data flow, to generate another
  • the first service data stream includes a link identifier, a service enabler identifier, that is, an identifier of the service enabler 2, a source MAC address, and service data.
  • Step 312 is the same as steps 304 to 310 described above.
  • Step 313 SW1 receives another fourth service data flow, and determines a next hop of the service data on the service chain according to the link identifier and the enabler identifier included in the fourth service data flow, that is, the service enablement in FIG. 3 or SW2 in FIG.
  • next hop of the service data on the service chain is the service enabler 3 in FIG. 4, the SW1 subsequently generates another first service data stream, and continues to send the first service data stream to the processing entity, and the processing entity continues.
  • the foregoing related processing if the next hop of the service data on the service chain is SW2 in FIG. 5, SW1 subsequently sends the service data to SW2, and SW2 sends the service data stream to the processing entity corresponding thereto, and the processing corresponding to SW2
  • the entity performs the aforementioned related processing.
  • FIG. 9 is a schematic structural diagram of a processing device according to an embodiment of the present invention. As shown in FIG. 9, the processing device includes: a first receiving unit 11, a recording unit 12, and a first sending unit 13, where
  • the first receiving unit 11 is configured to receive a first service data flow from the SW that includes a link identifier.
  • the recording unit 12 is configured to record a correspondence between the link identifier and a MAC translation address
  • the first sending unit 13 is configured to send a second service data stream to the service enabler, where the second service data stream includes a MAC address.
  • the recording unit 12 includes: a conversion module 121, a recording module 122, a deletion module 123, and a first generation module 124, where
  • the conversion module 121 is configured to convert the source MAC address included in the first service data stream according to the setting rule to obtain a MAC translation address
  • the recording module 122 is configured to record a correspondence between a link identifier included in the first service data flow and the MAC translation address;
  • the deleting module 123 is configured to delete the link identifier and the enabler identifier included in the first service data stream.
  • the first generating module 124 is configured to generate a second service data stream, where the second service data stream is encapsulated Includes MAC address translation.
  • the recording module 122 is further configured to record a correspondence between the configured link interface and the service enabler.
  • FIG. 10 is a schematic structural diagram of a processing device according to an embodiment of the present invention. As shown in FIG. 10, the processing device includes: a second receiving unit 21, a matching unit 22, and a second sending unit 23, where
  • the second receiving unit 21 is configured to receive a third service data flow from the service enabler
  • the matching unit 22 is configured to determine, according to the correspondence between the recorded link identifier and the MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream;
  • the second sending unit 23 is configured to send, to the SW, a fourth service data flow including the link identifier.
  • the matching unit 22 includes: a matching module 221, an inverse conversion module 222, an adding module 223, and a second generating module 224, where
  • the matching module 221 is configured to determine, according to the correspondence between the recorded link identifier and the MAC translation address, a link identifier corresponding to the MAC translation address included in the third service data stream;
  • the inverse conversion module 222 is configured to reverse convert the MAC address translated in the third service data stream according to the setting rule to obtain a MAC address as the destination MAC address of the service data.
  • the adding module 223 is configured to add a link identifier and an enabler identifier corresponding to the service data in the third service data stream.
  • the second generation module 224 is configured to generate a fourth service data flow, where the fourth service data flow includes a link identifier, an enabler identifier, a MAC address, and service data.
  • the matching module 221 is further configured to determine a corresponding service enabler identifier according to the correspondence between the recorded link interface and the service enabler and the link interface that receives the third service data flow.
  • the structure of the processing device shown in FIG. 9 and the structure of the processing device shown in FIG. 10 can be combined, that is, based on the structure of the processing device shown in FIG. 9, each unit described in FIG. Can be consistent with the above, no longer repeat them.
  • each of the above units and modules may be a central processing unit (CPU), or a digital signal processor (DSP), or a field programmable gate array (FPGA, Field Programmable Gate). Array) implementation.
  • CPU central processing unit
  • DSP digital signal processor
  • FPGA Field Programmable Gate array
  • the disclosed apparatus and method may be implemented in other manners.
  • the embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Integrate into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units; they may be located in one place or distributed on multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a removable storage device, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
  • the medium of the program code includes: a removable storage device, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
  • the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种业务链中的数据处理方法及设备、存储介质，接收来自SW的包含链路标识的第一业务数据流；记录所述链路标识与MAC转换地址之间的对应关系；向业务使能器发送第二业务数据流，所述第二业务数据流中包含MAC转换地址。

Description

一种业务链中的数据处理方法及设备、存储介质 技术领域
本发明涉及网络数据处理技术，尤其涉及一种业务链中的数据处理方法及设备、存储介质。
背景技术
当前运营商网络分为移动网络域和Gi接口之后的移动业务域，将承载业务的基础网络和处理业务的网络分开部署，使得运营商运营维护网络较为简单。
图1所示为移动运营网络的部署现状，为了提高用户体验，实现运营商差异化的服务并为之提供相应的计费策略，在移动业务域中部署有多种业务使能器(Service Enabler)，例如传输压缩(traffic compression)、视频优化(video optimization)、缓存(cache)、超文本传送协议(HTTP，HyperText Transfer Protocol)代理(HTTP proxy)、防火墙(Fire Wall)等来为运营商管道提供增值业务。移动网络域的网关(GW，GateWay)，如网关GPRS支持节点(GGSN，Gateway GPRS Support Node)或者分组数据网关(P-GW，Packet Data Network))，仅依据接入点名称(APN，Access Point Name)对业务数据进行简单粗粒度的分类，每类业务数据经过多个业务使能器，由这些业务使能器组成的业务路径形成了固定业务链(Service Chain)。每条业务链是由业务使能器固定串联的，且与网络拓扑绑定。
这种实现方式，人工配置复杂度高，单个业务使能器失效会导致整条业务链失效，并且处理时延和扩容成本都比较高。
发明内容
有鉴于此，本发明实施例为解决现有技术中存在的至少一个问题而提供一种业务链中的数据处理方法及设备、存储介质。
本发明实施例的技术方案是这样实现的：接收来自业务交换机SW的包含链路标识的第一业务数据流；记录所述链路标识与介质访问控制MAC转换地址之间的对应关系；向业务使能器发送第二业务数据流，所述第二业务数据流中包含MAC转换地址。
其中，所述记录所述链路标识与MAC转换地址之间的对应关系，包括：根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址；记录所述链路标识与所述MAC转换地址之间的对应关系。
一个实施例中，所述向业务使能器发送第二业务数据流之前，还包括：删除第一业务数据流中包含的链路标识，生成第二业务数据流。
一个实施例中，所述生成第二业务数据流之前，还包括：删除第一业务数据流中包含的业务使能器标识。
其中，所述向业务使能器发送第二业务数据流，包括：根据配置的自身链路接口与业务使能器之间的对应关系、及第一业务数据流中包含的业务使能器标识，通过对应链路接口向业务使能器发送第二业务数据流。
一个实施例中，所述接收来自SW的包含链路标识的第一业务数据流之前，还包括：记录配置的自身链路接口与业务使能器之间的对应关系。
一个实施例中，所述向业务使能器发送第二业务数据流之后，还包括：接收来自业务使能器的第三业务数据流；根据记录的链路标识与MAC转换地址之间的对应关系，确定对应于第三业务数据流中包含的MAC转换地址的链路标识；向SW发送包含所述链路标识的第四业务数据流。
一个实施例中，所述向SW发送包含所述链路标识的第四业务数据流之前，还包括：根据设定规则反向转换第三业务数据流中包含的MAC转换 地址，得到作为业务数据目的MAC地址的MAC地址。
一个实施例中，所述向SW发送包含所述链路标识的第四业务数据流之前，还包括：根据配置的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
其中，所述向SW发送包含所述链路标识的第四业务数据流，包括：向SW发送第四业务数据流，所述第四业务数据流包含链路标识、业务使能器标识、MAC地址和业务数据。
一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上文所述的操作。
一种业务链中的数据处理方法，包括：接收来自业务使能器的第三业务数据流；根据记录的链路标识与介质访问控制MAC转换地址之间的对应关系，确定对应于第三业务数据流中包含的MAC转换地址的链路标识；向SW发送包含所述链路标识的第四业务数据流。
一个实施例中，所述向SW发送包含所述链路标识的第四业务数据流之前，还包括：根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址。
一个实施例中，所述向SW发送包含所述链路标识的第四业务数据流之前，还包括：根据配置的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
其中，所述向SW发送包含所述链路标识的第四业务数据流，包括：向SW发送第四业务数据流，所述第四业务数据流包含链路标识、业务使能器标识、MAC地址和业务数据。
一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上文所述的操作。
一种处理设备，包括：
第一接收单元，配置为接收来自业务交换机SW的包含链路标识的第一业务数据流；
记录单元，配置为记录所述链路标识与介质访问控制MAC转换地址之间的对应关系；
第一发送单元，配置为向业务使能器发送第二业务数据流，第二业务数据流中包含MAC转换地址。
其中，所述记录单元包括：
转换模块，配置为根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址；
记录模块，配置为记录第一业务数据流中包含的链路标识与所述MAC转换地址之间的对应关系；
删除模块，配置为删除第一业务数据流中包含的链路标识和使能器标识；
第一生成模块，配置为生成第二业务数据流，第二业务数据流中包含MAC转换地址。
其中，所述记录模块，还配置为：记录第一业务数据流中包含的业务使能器标识与配置的链路接口与业务使能器之间的对应关系。
一个实施例中，所述设备还包括：
第二接收单元，配置为接收来自业务使能器的第三业务数据流；
匹配单元，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
第二发送单元，配置为向SW发送包含所述链路标识的第四业务数据流。
其中，所述匹配单元包括：
匹配模块，配置为根据记录的链路标识与MAC转换地址之间的对应关 系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
逆转换模块，配置为根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址；
添加模块，配置为在第三业务数据流中添加业务数据对应的链路标识和使能器标识；
第二生成模块，配置为生成第四业务数据流，第四业务数据流中包含链路标识、使能器标识、MAC地址和业务数据。
其中，所述匹配模块，还配置为：根据记录的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
一种处理设备，包括：
接收单元，配置为接收来自业务使能器的第三业务数据流；
匹配单元，配置为根据记录的链路标识与介质访问控制MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
发送单元，配置为向SW发送包含所述链路标识的第四业务数据流。
其中，所述匹配单元包括：
匹配模块，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
逆转换模块，配置为根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址；
添加模块，配置为在第三业务数据流中添加业务数据对应的链路标识和使能器标识；
生成模块，配置为生成第四业务数据流，第四业务数据流中包含链路标识、使能器标识、MAC地址和业务数据。
其中，所述匹配模块，还配置为：根据记录的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
根据本发明实施例，处理实体向业务使能器发送的业务数据流中完全不需要链路标识，无需业务使能器对链路标识进行识别，降低了业务使能器实现的复杂度。另外，由于处理实体向SW发送的业务数据流会包含链路标识，因此，能够使SW依据链路标识正确找到相应的业务链，不会出现业务链的执行关系发生混乱的问题。
附图说明
在附图(其不一定是按比例绘制的)中，相似的附图标记可在不同的视图中描述相似的部件。具有不同字母后缀的相似附图标记可表示相似部件的不同示例。附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为移动运营网络部署的结构示意图；
图2为动态业务链示意图；
图3为业务链结构示意图；
图4为业务链的执行关系示意图一；
图5为业务链的执行关系示意图二；
图6为本发明实施例业务链中的数据处理流程示意图一；
图7为本发明实施例业务链中的数据处理流程示意图二；
图8为本发明实施例业务链中的数据处理交互流程示意图；
图9为本发明实施例处理设备结构示意图一；
图10为本发明实施例处理设备结构示意图二。
具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。
为了解决现有固定业务链存在的缺陷，提出了对动态业务链的需求，希望能够按当前需要灵活使用业务使能器，以便降低业务使能器部署成本，提高资源使用率。弹性灵活的业务链可以针对不同的接入类型、如2G/3G/4G，选取不同的增值业务链，以便提供不同的优化措施。例如，对带宽较低的接入方式可以提供更多的视频压缩优化服务；又如，为不同的应用选取相应的增值业务链，对于没有任何增值价值的业务数据可以直接旁路，不占用业务使能器资源；再如，可以为不同等级的付费用户提供差异化的增值服务，为金牌、银牌、铜牌用户的业务数据选取和建立不同的业务链；再如，可以针对无线接入网的信号质量的变化情况提供实时的优化措施，如当网络拥塞时，将为业务数据选取可提供加速能力的业务链。
图2所示为按需配置的业务链，业务交换机(SW，Service Switch)在业务控制器(SC，Service Controller)的控制下，编排业务数据需要经过的业务使能器，SC可以根据策略动态调整业务链、即业务数据需要经过的业务路径。SC对SW的控制可以采用开放流(Openflow)协议。Openflow协议采用匹配转发的控制逻辑来编排业务数据需要经过的业务路径，使用链路标识(Chain ID)统一标识业务链中功能模块的组合方式、即业务数据需要经过的业务路径。
图3为业务链结构示意图，结合图2所示，链路标识1用于标识业务链1、即图2所示的业务数据1经过的业务路径，如图2中实线所示；链路标识2用于标识业务链2、即图2所示的业务数据2经过的业务路径，如图2中虚线所示。SC可以将包含链路标识的业务链以流表的方式下发到业务链所涉及的SW上，以使SW根据该流表进行业务数据的路由。
SC基于业务链进行业务数据的业务路径的编排时需要考虑两个因素： SW之间的路由关系，以及每一SW内部业务使能器之间的路由关系，这在生成下发到SW的流表时便需要依照所需要的执行关系设置好。如图4所示，业务链X标识的业务链表示业务数据需要按顺序依次经过SW1和SW2，在SW1中业务数据需要按顺序依次经过业务使能器1、业务使能器2和业务使能器3，在SW2中业务数据需要经过业务使能器4。如图5所示，业务链Y标识的业务链表示业务数据需要按顺序依次经过SW1、SW2、然后再次经过SW1，第一次经过SW1时，在SW1中业务数据需要按顺序依次经过业务使能器1和业务使能器2；再次经过SW1时，在SW1中业务数据需要经过业务使能器3。
SW根据链路标识以及业务使能器标识的对应关系来确定业务数据在业务处理中的位置，进而确定业务数据的下一跳位置。这里的业务使能器标识，可以用于标识业务使能器，也可以用于标识代表业务使能器功能的业务。链路标识作为业务数据流的头部信息的一部分，可以方便SW识别业务数据的业务路径，如果该头部信息在业务数据流传输和处理过程中一直保留，那么SW便能够一直依据获取到的头部信息正确的确定业务数据流的业务路径。但是，对于传统的、不能识别该头部信息的业务使能器，SW只能在将业务数据流传输至业务使能器之前删除掉该头部信息，以避免业务使能器对业务数据流进行处理时产生不可预知的处理错误。而业务使能器对业务数据进行处理之后，业务数据流的头部信息中同样不会包含链路标识，SW收到这样的业务数据流后，必然会出现业务链的执行关系发生混乱的现象。以图4和图5所示为例，当业务数据流从业务使能器2发送至SW1后，如果业务数据流的头部信息中已经不存在链路标识，那么SW1根据该业务数据流则无法确定后续是将业务数据流继续路由至业务链X标识的业务链中的业务使能器3，还是跳转到业务链Y标识的业务链中的SW2的业务使能器5。
本发明实施例中，业务数据是指对应于某一具体业务的数据内容，而业务数据流除包含业务数据，还包含链路标识、业务使能器标识等，这些信息可以包含在业务数据流的头部信息中。
基于以上描述，本发明实施例中，接收包含链路标识的第一业务数据流，记录所述链路标识与介质访问控制(MAC，Media Access Control)转换地址之间的对应关系；向业务使能器发送第二业务数据流，第二业务数据流中包含MAC转换地址。进一步地，接收业务使能器发送的第三业务数据流，根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的目的MAC地址的链路标识，发送包含所述链路标识的第四业务数据流。
图6为本发明实施例业务链中的数据处理流程示意图，如图6所示，业务链中的数据处理包括以下步骤：
步骤101：处理实体接收来自SW的包含链路标识的第一业务数据流。
步骤101之前，SC依照具体业务类型编排以链路标识予以标识的业务链，通过下发流表的方式将业务链下发至业务链中涉及的SW。业务链包括链路标识、SC的执行顺序以及各SC内业务使能器的执行顺序。流表中的执行关系可以如图4、图5所示。SW收到流表形式的业务链后，确定业务数据当前需要经过的业务使能器，将包含链路标识、业务使能器标识和业务数据的第一业务数据流发送至处理实体。业务数据当前需要经过的业务使能器，可以是SW根据SC下发的业务链确定的业务数据需要经过的第一个业务使能器，如图4、图5中的业务使能器1；也可以是SW根据处理实体发送的经某一业务使能器处理过的第二业务数据流中包含的链路标识，确定的业务数据需要经过的下一个使能器，如图4中的业务使能器2或业务使能器3、图5中的业务使能器2；还可以是SW根据上一SW的触发确定的业务数据在该SW中需要经过的第一个使能器，如图4中的业务使能 器4、或图5中的业务使能器5或业务使能器3。
本发明实施例中的处理实体可以是在移动运营网络中单独设置的物理设备，也可以是与SW位于同一物理设备的逻辑实体。处理实体与SW位于相同的物理设备时，该物理设备可以是交换机。处理实体与SW位于同一物理设备时，处理实体可以是该物理设备中运行的独立的进程。
步骤102：处理实体记录所述链路标识与MAC转换地址之间的对应关系。
处理实体接收到来自SW的第一业务数据流后，根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址，记录第一业务数据流中包含的链路标识与MAC转换地址之间的对应关系，并删除第一业务数据流中包含的链路标识生成第二业务数据流。
其中，设定规则可以是设定的转换算法，如选取源MAC地址的设定位、如低24位，在选取的部分MAC地址之前添加设定位数的随机数，从而形成MAC转换地址；又如，选取源MAC地址的设定位、如低24位，在选取的部分MAC地址之前添加业务使能器标识的设定位，从而形成MAC转换地址。所述源MAC地址是处理实体所在的物理设备的MAC地址，如果处理实体是单独设置的物理设备，则源MAC地址是该物理设备的MAC地址；如果处理实体与SW合设在同一物理设备，则源MAC地址是处理实体与SW共同所在的物理设备的MAC地址。
处理实体接收到的第一业务数据流中进一步包含业务使能器标识，该业务使能器标识用于标识业务数据当前需要经过的业务使能器，处理实体在步骤102中还会删除第一业务数据流中包含的业务使能器标识，以得到不包含链路标识和业务使能器标识的第二业务数据流。其中，删除业务使能器标识的操作可与前述删除链路标识的操作在一次删除操作中完成，即一次删除操作中同时删除第一业务数据流中包含的链路标识和业务使能器 标识。
步骤103：处理实体向业务使能器发送第二业务数据流，所述第二业务数据流中包含MAC转换地址。
其中，第二业务数据流中包含的MAC转换地址为业务数据的源MAC地址。
处理实体根据接收到的第一业务数据流中包含的业务使能器标识向对应的业务使能器发送第二业务数据流。
本发明一个实施例中，网络管理员可配置处理实体的不同链路接口与不同的业务使能器相对应，并将链路接口与业务使能器的对应关系的配置信息存储至处理实体所在的物理设备，这样处理实体根据配置的链路接口与业务使能器之间的对应关系、及相应业务使能器标识，便能够通过对应链路接口将第二业务数据流发送到对应的业务使能器。所述链路接口是处理实体上用来向业务使能器传输业务数据的端口或接口。
一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上文图6对应的所述操作。
图7为本发明实施例业务链中的数据处理流程示意图二，如图7所示，业务链中的数据处理包括以下步骤：
步骤201：处理实体接收来自业务使能器的第三业务数据流。
步骤201之前，处理实体根据接收到的第一业务数据流中包含的业务使能器标识向对应的业务使能器发送第二业务数据流；业务使能器接收到第二业务数据流后，对第二业务数据流中包含的业务数据进行处理后，形成第三业务数据流并发送至处理实体，第三业务数据流中包含目的MAC地址，该目的MAC地址即为第二业务数据流中包含的源MAC地址、MAC转换地址。
网管人员可配置各业务使能器与处理实体的不同链路接口相对应，并 将与业务使能器相对应的处理实体的链路接口存储至业务使能器，业务使能器向处理实体发送第三业务数据流时，可以是将第三业务数据流发送至处理实体上与该业务使能器相对应的链路接口。
步骤202：处理实体根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识。
处理实体接收到的第三业务数据流中包含目的MAC地址，并且处理实体之前在接收到来自SW的第一业务数据流时会记录第一业务数据流包含的链路标识与MAC转换地址之间的对应关系，因此，这里，处理实体能够根据记录的链路标识与MAC转换地址之间的对应关系，确定出对应于第三业务数据流中包含的目的MAC地址、即MAC转换地址的链路标识。
一个实施例中，处理实体根据设定规则反向转换第三业务数据流中包含的目的MAC地址、即MAC转换地址，得到作为业务数据目的MAC地址的MAC地址，该MAC地址是处理实体所在的物理设备的MAC地址。
步骤203：处理实体向SW发送包含所述链路标识的第四业务数据流。
处理实体确定出链路标识后，在第三业务数据流中添加链路标识形成第四业务数据流，然后将第四业务数据流发送至SW。
一个实施例中，处理实体可根据配置的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。处理实体确定出业务使能器标识后，还会在第三业务数据流中添加业务使能器标识形成第四业务数据流，然后将第四业务数据流发送至SW。其中，添加业务使能器标识的操作可与前述添加链路标识的操作在一次添加操作中完成，即一次添加操作中同时在第三业务数据流中添加链路标识和业务使能器标识，形成第四业务数据流。
第四业务数据流中还可包含反向转换后的MAC地址。
步骤203之后，SW收到第四业务数据流后，便能够根据第四业务数据 流中包含的链路标识、或链路标识和业务使能器标识确定业务数据在业务链上的下一跳，如果业务数据仍然是需要在该SW中进行处理，则该SW向处理实体发送包含链路标识的另一第一业务数据流；如果业务数据需要到另一SW中进行处理，则触发另一SW对业务数据进行处理。
以上所述处理实体可与SW一一对应，各对应于不同SW的处理实体按照上述步骤101～步骤103或步骤201～步骤203进行处理。
一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上文图7对应的所述操作。
图8为本发明实施例业务链中的数据处理交互流程示意图，如图8所示，结合图4、图5所示的业务链，业务链中的数据处理交互流程包括以下步骤：
步骤301：SC依照具体业务类型编排以链路标识予以标识的业务链，通过下发流表的方式将业务链下发至业务链中涉及的SW，如图4、图5中的SW1和SW2。业务链包括链路标识、SC的执行顺序以及各SC内业务使能器的执行顺序。流表中的执行关系可如图4、图5所示。
步骤302～步骤303：SW1收到流表形式的业务链后，确定业务数据当前需要经过的业务使能器、即业务使能器1，生成第一业务数据流，第一业务数据流包含链路标识、业务使能器标识即业务使能器1的标识、源MAC地址和业务数据。其中，源MAC地址为处理实体所在物理设备的MAC地址。
步骤304：SW1向处理实体发送第一业务数据流。
步骤305：处理实体接收第一业务数据流，根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址，记录第一业务数据流中包含的链路标识与MAC转换地址之间的对应关系，删除第一业务数据流中包含的链路标识、业务使能器标识，并将MAC转换地址作为业务数 据的源MAC地址，得到第二业务数据流，第二业务数据流包含MAC转换地址和业务数据。
步骤306：处理实体根据配置的自身链路接口与业务使能器之间的对应关系、及第一业务数据流中包含的业务使能器标识，通过对应业务使能器1的链路接口向业务使能器1发送第二业务数据流。
步骤307：业务使能器1接收第二业务数据流，对第二业务数据流中包含的业务数据进行处理，并将MAC转换地址作为业务数据的目的MAC地址，得到第三业务数据流，第三业务数据流包含MAC转换地址和业务数据。
步骤308：业务使能器1向处理实体上对应业务使能器1的链路接口发送第三业务数据流。
步骤309：处理实体接收第三业务数据流，根据步骤305中记录的链路标识与MAC转换地址之间的对应关系，确定对应于第三业务数据流中包含的目的MAC地址、即MAC转换地址的链路标识；
处理实体根据设定规则反向转换目的MAC地址、即MAC转换地址，得到MAC地址；
处理实体根据配置的自身链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
步骤310：处理实体生成第四业务数据流并向SW1发送，第四业务数据流包含链路标识、业务使能器标识、目的MAC地址即步骤309在得到的MAC地址和业务数据。
步骤311：SW1接收第四业务数据流，根据第四业务数据流中包含的链路标识和使能器标识确定业务数据在业务链上的下一跳、即业务使能器2，生成另一第一业务数据流，该第一业务数据流包含链路标识、业务使能器标识即业务使能器2的标识、源MAC地址和业务数据。
步骤312与前述步骤304～步骤310相同。
步骤313：SW1接收另一第四业务数据流，根据第四业务数据流中包含的链路标识和使能器标识确定业务数据在业务链上的下一跳、即图4中的业务使能器3或图5中的SW2。
如果业务数据在业务链上的下一跳为图4中的业务使能器3，SW1后续将生成再一第一业务数据流，继续将第一业务数据流发送至处理实体，处理实体继续进行前述相关处理；如果业务数据在业务链上的下一跳为图5中的SW2，SW1后续将业务数据发送至SW2，SW2将业务数据流发送至与其对应的处理实体，由对应于SW2的处理实体进行前述相关处理。
图9为本发明实施例处理设备结构示意图一，如图9所示，该处理设备包括：第一接收单元11、记录单元12和第一发送单元13，其中，
第一接收单元11，配置为接收来自SW的包含链路标识的第一业务数据流；
记录单元12，配置为记录所述链路标识与MAC转换地址之间的对应关系；
第一发送单元13，配置为向业务使能器发送第二业务数据流，第二业务数据流中包含MAC转换地址。
其中，记录单元12包括：转换模块121、记录模块122、删除模块123和第一生成模块124，其中，
转换模块121，配置为根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址；
记录模块122，配置为记录第一业务数据流中包含的链路标识与所述MAC转换地址之间的对应关系；
删除模块123，配置为删除第一业务数据流中包含的链路标识和使能器标识；
第一生成模块124，配置为生成第二业务数据流，第二业务数据流中包 含MAC转换地址。
所述记录模块122，还配置为记录配置的链路接口与业务使能器之间的对应关系。
图10为本发明实施例处理设备结构示意图二，如图10所示，该处理设备包括：第二接收单元21、匹配单元22和第二发送单元23，其中，
第二接收单元21，配置为接收来自业务使能器的第三业务数据流；
匹配单元22，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
第二发送单元23，配置为向SW发送包含所述链路标识的第四业务数据流。
其中，匹配单元22包括：匹配模块221、逆转换模块222、添加模块223和第二生成模块224，其中，
匹配模块221，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
逆转换模块222，配置为根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址；
添加模块223，配置为在第三业务数据流中添加业务数据对应的链路标识和使能器标识；
第二生成模块224，配置为生成第四业务数据流，第四业务数据流中包含链路标识、使能器标识、MAC地址和业务数据。
所述匹配模块221，还配置为根据记录的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
图9所示的处理设备结构与图10所示的处理设备结构可结合在一起，即以图9所示的处理设备结构为基础，增加图10中所述各单元，各部分功 能与前述一致，不再赘述。
在本发明实施例中，上述各单元及模块均可由中央处理器(CPU，Central Processing Unit)、或数字信号处理器(DSP，Digital Signal Processor)、或现场可编程门阵列(FPGA，Field Programmable Gate Array)实现。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。以上所描述的实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元；既可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、只读存储器(Read Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
或者，本发明上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：移动存储设备、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种业务链中的数据处理方法，所述方法包括：
    接收来自业务交换机SW的包含链路标识的第一业务数据流；
    记录所述链路标识与介质访问控制MAC转换地址之间的对应关系；
    向业务使能器发送第二业务数据流，所述第二业务数据流中包含MAC转换地址。
  2. 根据权利要求1所述的方法，其中，所述记录所述链路标识与MAC转换地址之间的对应关系，包括：
    根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址；
    记录所述链路标识与所述MAC转换地址之间的对应关系。
  3. 根据权利要求1所述的方法，其中，所述向业务使能器发送第二业务数据流之前，该方法还包括：
    删除第一业务数据流中包含的链路标识，生成第二业务数据流。
  4. 根据权利要求3所述的方法，其中，所述生成第二业务数据流之前，该方法还包括：
    删除第一业务数据流中包含的业务使能器标识。
  5. 根据权利要求1至4任一所述的方法，其中，所述向业务使能器发送第二业务数据流，包括：
    根据配置的自身链路接口与业务使能器之间的对应关系、及第一业务数据流中包含的业务使能器标识，通过对应链路接口向业务使能器发送第二业务数据流。
  6. 根据权利要求5所述的方法，其中，所述接收来自SW的包含链路标识的第一业务数据流之前，该方法还包括：
    记录配置的自身链路接口与业务使能器之间的对应关系。
  7. 根据权利要求1至4任一所述的方法，其中，所述向业务使能器发送第二业务数据流之后，该方法还包括：
    接收来自业务使能器的第三业务数据流；
    根据记录的链路标识与MAC转换地址之间的对应关系，确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    向SW发送包含所述链路标识的第四业务数据流。
  8. 根据权利要求7所述的方法，其中，所述向SW发送包含所述链路标识的第四业务数据流之前，该方法还包括：
    根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址。
  9. 根据权利要求7所述的方法，其中，所述向SW发送包含所述链路标识的第四业务数据流之前，该方法还包括：
    根据配置的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
  10. 根据权利要求7所述的方法，其中，所述向SW发送包含所述链路标识的第四业务数据流，包括：
    向SW发送第四业务数据流，所述第四业务数据流包含链路标识、业务使能器标识、MAC地址和业务数据。
  11. 一种业务链中的数据处理方法，所述方法包括：
    接收来自业务使能器的第三业务数据流；
    根据记录的链路标识与介质访问控制MAC转换地址之间的对应关系，确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    向SW发送包含所述链路标识的第四业务数据流。
  12. 根据权利要求11所述的方法，其中，所述向SW发送包含所述链 路标识的第四业务数据流之前，该方法还包括：
    根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址。
  13. 根据权利要求11所述的方法，其中，所述向SW发送包含所述链路标识的第四业务数据流之前，该方法还包括：
    根据配置的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
  14. 根据权利要求11、12或13所述的方法，其中，所述向SW发送包含所述链路标识的第四业务数据流，包括：
    向SW发送第四业务数据流，所述第四业务数据流包含链路标识、业务使能器标识、MAC地址和业务数据。
  15. 一种处理设备，所述处理设备包括：
    第一接收单元，配置为接收来自业务交换机SW的包含链路标识的第一业务数据流；
    记录单元，配置为记录所述链路标识与介质访问控制MAC转换地址之间的对应关系；
    第一发送单元，配置为向业务使能器发送第二业务数据流，第二业务数据流中包含MAC转换地址。
  16. 根据权利要求15所述的处理设备，其中，所述记录单元包括：
    转换模块，配置为根据设定规则对第一业务数据流中包含的源MAC地址进行转换得到MAC转换地址；
    记录模块，配置为记录第一业务数据流中包含的链路标识与所述MAC转换地址之间的对应关系；
    删除模块，配置为删除第一业务数据流中包含的链路标识和使能器标识；
    第一生成模块，配置为生成第二业务数据流，第二业务数据流中包含MAC转换地址。
  17. 根据权利要求16所述的处理设备，其中，所述记录模块，还配置为：
    记录第一业务数据流中包含的业务使能器标识与配置的链路接口与业务使能器之间的对应关系。
  18. 根据权利要求15、16或17所述的处理设备，其中，所述设备还包括：
    第二接收单元，配置为接收来自业务使能器的第三业务数据流；
    匹配单元，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    第二发送单元，配置为向SW发送包含所述链路标识的第四业务数据流。
  19. 根据权利要求18所述的处理设备，其中，所述匹配单元包括：
    匹配模块，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    逆转换模块，配置为根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址；
    添加模块，配置为在第三业务数据流中添加业务数据对应的链路标识和使能器标识；
    第二生成模块，配置为生成第四业务数据流，第四业务数据流中包含链路标识、使能器标识、MAC地址和业务数据。
  20. 根据权利要求19所述的处理设备，其中，所述匹配模块，还配置为：
    根据记录的链路接口与业务使能器之间的对应关系、以及接收到第三 业务数据流的链路接口，确定对应的业务使能器标识。
  21. 一种处理设备，所述处理设备包括：
    接收单元，配置为接收来自业务使能器的第三业务数据流；
    匹配单元，配置为根据记录的链路标识与介质访问控制MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    发送单元，配置为向SW发送包含所述链路标识的第四业务数据流。
  22. 根据权利要求21所述的处理设备，其中，所述匹配单元包括：
    匹配模块，配置为根据记录的链路标识与MAC转换地址之间的对应关系确定对应于第三业务数据流中包含的MAC转换地址的链路标识；
    逆转换模块，配置为根据设定规则反向转换第三业务数据流中包含的MAC转换地址，得到作为业务数据目的MAC地址的MAC地址；
    添加模块，配置为在第三业务数据流中添加业务数据对应的链路标识和使能器标识；
    生成模块，配置为生成第四业务数据流，第四业务数据流中包含链路标识、使能器标识、MAC地址和业务数据。
  23. 根据权利要求22所述的处理设备，其中，所述匹配模块，还配置为：
    根据记录的链路接口与业务使能器之间的对应关系、以及接收到第三业务数据流的链路接口，确定对应的业务使能器标识。
  24. 一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行权利要求1-10所述的操作。
  25. 一种存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行权利要求11-14所述的操作。
PCT/CN2015/086957 2014-11-21 2015-08-14 一种业务链中的数据处理方法及设备、存储介质 WO2016078450A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410675580.4A CN105681230A (zh) 2014-11-21 2014-11-21 一种业务链中的数据处理方法及设备
CN201410675580.4 2014-11-21

Publications (1)

Publication Number Publication Date
WO2016078450A1 true WO2016078450A1 (zh) 2016-05-26

Family

ID=56013249

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086957 WO2016078450A1 (zh) 2014-11-21 2015-08-14 一种业务链中的数据处理方法及设备、存储介质

Country Status (2)

Country Link
CN (1) CN105681230A (zh)
WO (1) WO2016078450A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111597777A (zh) * 2020-05-15 2020-08-28 上海电机系统节能工程技术研究中心有限公司 物料数据处理方法、装置和电子设备
US11502988B2 (en) 2021-01-21 2022-11-15 Cisco Technology, Inc. Stable MAC address change process

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110798288B (zh) * 2019-01-28 2021-01-15 通号城市轨道交通技术有限公司 一种冗余通信方法及装置
CN111163004B (zh) * 2019-12-31 2023-03-31 奇安信科技集团股份有限公司 服务链数据处理方法、装置和计算机设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102244688A (zh) * 2010-05-11 2011-11-16 华为技术有限公司 一种报文转发的方法、装置及系统
CN102571602A (zh) * 2012-02-13 2012-07-11 华为技术有限公司 业务路由网络及业务处理的方法、设备
CN103581018A (zh) * 2013-07-26 2014-02-12 北京华为数字技术有限公司 报文发送方法、路由器以及业务交换器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102244688A (zh) * 2010-05-11 2011-11-16 华为技术有限公司 一种报文转发的方法、装置及系统
CN102571602A (zh) * 2012-02-13 2012-07-11 华为技术有限公司 业务路由网络及业务处理的方法、设备
CN103581018A (zh) * 2013-07-26 2014-02-12 北京华为数字技术有限公司 报文发送方法、路由器以及业务交换器

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111597777A (zh) * 2020-05-15 2020-08-28 上海电机系统节能工程技术研究中心有限公司 物料数据处理方法、装置和电子设备
CN111597777B (zh) * 2020-05-15 2023-06-02 上海电机系统节能工程技术研究中心有限公司 物料数据处理方法、装置和电子设备
US11502988B2 (en) 2021-01-21 2022-11-15 Cisco Technology, Inc. Stable MAC address change process

Also Published As

Publication number Publication date
CN105681230A (zh) 2016-06-15

Similar Documents

Publication Publication Date Title
US11863448B2 (en) Method and apparatus for traffic optimization in virtual private networks (VPNs)
TWI643477B (zh) 軟體定義網路控制器、服務功能鏈系統及路徑追蹤方法
WO2015149624A1 (zh) 业务链路选择控制方法以及设备
WO2015165312A1 (zh) 业务链负载均衡方法及其装置、系统
WO2016062106A1 (zh) 报文处理方法、装置及系统
WO2016078450A1 (zh) 一种业务链中的数据处理方法及设备、存储介质
JP2013141232A (ja) ゲートウェイでインターネットプロトコルベースネットワークを用いてコンテンツ中心ネットワークを実現する方法及びそのゲートウェイ並びにインターネットプロトコルをコンテンツ中心ネットワーク互換可能なパケットに変換するルータ
US9641420B1 (en) Methods and apparatus for assessing the quality of a data path including both layer-2 and layer-3 devices
WO2018036254A1 (zh) 报文转发方法及装置
JP7294578B2 (ja) ユーザプレーンのリルーティング方法および装置
WO2018036173A1 (zh) 一种网络负载均衡方法、设备及系统
US20170201466A1 (en) Data packet processing apparatus and method
JP2010088080A (ja) 通信装置および通信方法
WO2018103613A1 (zh) 一种业务数据处理的方法和装置
WO2015192705A1 (zh) 接入装置及其执行的将用户设备接入网络的方法
JP2004159112A (ja) 通信制御システム、通信制御方法、これらに用いて好適なルーティング制御装置及びルータ装置
US8923303B2 (en) Method, system and installation for forwarding data transmission frames
CN105027515B (zh) 用于在内容传输系统中处理数据的设备和方法
US20220094620A1 (en) Quality-of-service in cellular information centric network
CN111988221B (zh) 数据传输方法、数据传输装置、存储介质与电子设备
JP2017523721A (ja) サービスノード能力処理方法、装置、サービス分類器及びサービスコントローラ
TW202249464A (zh) 使用網際網路協定網路於蜂巢式資料封包路由的方法
TW202249466A (zh) 封包轉發控制協定（ｐｆｃｐ）會話負載平衡器運作系統及其運作方法
WO2017157127A1 (zh) 访问记录回传方法、设备和系统
KR101363338B1 (ko) 오픈플로우(OpenFlow)를 이용하여 사용자 단말 장치 사이의 통신을 지원하기 위한 방법, 장치, 시스템 및 컴퓨터 판독 가능한 기록 매체

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

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

Country of ref document: EP

Kind code of ref document: A1