CN109787849B - O L T logic network testing method - Google Patents

Abstract

The application provides an O L T logic network testing method which comprises the steps that a first device sends a service flow to an ONU, when the O L T device receives the service flow sent by the ONU in any network slice, the service flow carries a first identification and a second identification, and the service flow is sent to a second device, wherein the first identification comprises an ONU identification, the second identification is a globally unique network slice user identification distributed for each network slice, when the second device receives the service flow sent by the O L T, the first identification and the second identification carried in the service flow are obtained, whether the first identification and the second identification correspond to each other is determined according to the corresponding relation of the first identification and the second identification, if yes, the network slice is determined to realize isolation, otherwise, the network slice is determined not to realize isolation.

Description

O L T logic network testing method

Technical Field

The invention relates to the technical field of communication, in particular to a method for testing an optical line terminal (O L T) logic network.

Background

With the scale construction of the optical fiber broadband access network, the broadband access network gradually evolves to a full-service access bearer network for bearing various service types such as home users, government and enterprise private lines, mobile base station backhaul and the like. The broadband access network supports differentiated services for different clients and different types of services during full-service operation, provides an independent and isolated service forwarding function and an equipment management function, and avoids resource competition and occupation caused by resource coupling in different service operations.

Therefore, from the perspective of better adapting to more complicated application scenarios in the future, the future network architecture must require the opening and standardization of a network capability interface, and the scheduling and customization of network resources and capabilities for service-oriented services are realized through a software defined network technology, and meanwhile, the network programming capability is provided for further accelerating the platform of the network capability, and the deep opening of the network service is really realized.

Referring to fig. 1, fig. 1 is a schematic diagram of a conventional network slice for implementing O L T, in fig. 1, a single physical O L T device can be logically divided into multiple network slices by using a network slice technology, and independent isolation and differentiated setting of service resources, service planning, service operation, service maintenance and slice management among the network slices are implemented, so that the use efficiency of the device is improved.

The network slice is implemented by a programmable technology, for example, an OpenFlow flow table is used to implement data flow forwarding between logical interfaces. Programmable technology improves the flexibility of the device, but this approach relies on manual configuration, which may cause confusion in the data flow of each network slice if the configuration is wrong or the chip fails. Therefore, it is important to verify the isolation between independent network slices, so as to ensure the security of different clients and different kinds of services.

In the existing implementation, a technical scheme capable of effectively verifying whether each network slice realizes isolation is not provided yet.

Disclosure of Invention

In view of this, the present application provides a method for testing an O L T logic network, which can effectively determine whether each network slice implements isolation.

In order to solve the technical problem, the technical scheme of the application is realized as follows:

a method for testing an O L T logic network, the method comprising:

the first equipment sends a service stream to the ONU;

when receiving a service flow sent by an ONU in any network slice, the O L T equipment carries a first identifier and a second identifier in the service flow and sends the service flow to second equipment, wherein the first identifier comprises the ONU identifier;

and when receiving the service flow sent by O L T, the second device obtains the first identifier and the second identifier carried in the service flow, and determines whether the obtained first identifier and the obtained second identifier correspond to each other according to the configured corresponding relationship between the first identifier and the second identifier, if so, the network slice is determined to realize isolation, otherwise, the network slice is determined not to realize isolation.

According to the technical scheme, the first service identification and the second service identification are marked on the O L T, whether the identification carried by the corresponding service flow received by the connection port of the O L T is matched with the corresponding relation between the configured first identification and the configured second identification is checked, and whether the isolation of each network slice is realized is determined.

Drawings

FIG. 1 is a schematic diagram of a network slice of a conventional implementation of O L T;

FIG. 2 is a system for testing an O L T logic network according to an embodiment of the present invention;

FIG. 3 is a schematic diagram illustrating a test flow of an O L T logic network according to an embodiment of the present invention;

FIG. 4 is a diagram of the frame format of Option 82;

FIG. 5 is a schematic diagram of Sub-Option format in Option 82;

FIG. 6 is a schematic structural diagram of sub-option in the embodiment of the present application;

fig. 7 is a schematic diagram illustrating a testing process of an O L T logic network according to a second embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more clearly apparent, the technical solutions of the present invention are described in detail below with reference to the accompanying drawings and examples.

The application provides a method for testing an O L T logic network, which is characterized in that a first service identifier and a second service identifier are marked on service flow information on O L T, whether the identifier carried by the corresponding service flow received by an upper port of O L T is matched with the corresponding relation between the configured first identifier and the configured second identifier is checked, and whether each network slice is isolated or not is determined.

Referring to fig. 2, a network system applied in the embodiment of the present application is shown in fig. 2, where fig. 2 is an O L T logic network test system in the embodiment of the present application, in fig. 2, a first device user sends data, and a second device is used to receive the data, and in a specific implementation, the first device and the second device may be a data network analyzer, or may be a device capable of receiving, sending, and analyzing the data, and the first device and the second device may be integrated into one device or may be implemented independently as two devices.

In fig. 2, three O L T devices are virtualized for O L T devices, and three Network slices are divided, where the division of Network slices can be implemented according to the existing implementation manner, such as logging in an EMS client, opening a Network slice management view on a Network slice management interface, creating a Network slice 1, a Network slice 2, and a Network slice 3, and adding Optical Network Units (ONUs) under the Network slices, respectively, where each Network slice includes one or more ONUs.

The O L T device configures a globally unique network slice identification for each network slice, with the scope shown as virtual domain 1, virtual domain 2, and virtual domain 3 in fig. 2 being one network slice.

And configuring the corresponding relation between the first identifier and the second identifier of each network slice on the second device, namely which first identifier corresponds to which second identifier.

In a specific implementation of the present application, the first identifier may only include an ONU identifier, or may also include an ONU identifier, an O L T device identifier, a slot number, a Passive Optical Network (PON) port number, and the like.

The O L T logic network test procedure in the embodiment of the present application is described in detail below with reference to the accompanying drawings.

Example one

Referring to fig. 3, fig. 3 is a schematic diagram of a testing process of an O L T logic network according to an embodiment of the present application, and the specific steps are as follows:

step 301, the first device sends a traffic stream to the ONU.

Step 302, when the O L T device receives a service flow sent by an ONU in any network slice, the service flow carries the first identifier and the second identifier, and sends the service flow to the second device.

When receiving a service stream sent by an ONU, the O L T device performs related processing according to the existing implementation, including carrying a first identifier, and what needs to be added in the application is to carry a second identifier while carrying the first identifier.

Wherein the second identifier is a globally unique network slice user identifier assigned to each network slice.

In a specific implementation of the present application, the second identifier is carried in a field of a user access line (port) identifier.

When the second identifier is carried in the field of the subscriber access line identifier, the second identifier may be carried in the field of option82, or may be carried in the field of PPPoE, which is not limited to this.

In the embodiment of the present application, the field in option82 is implemented as an example:

option82 of Dynamic Host Configuration Protocol (DHCP) is a field applied to a subscriber access line (port) identifier, which can be used to identify the physical location information of a subscriber accessing the internet. And the fault can be tracked and judged according to the user name, the IP address, the port number and the like carried by the Option 82. The frame format of Option82 is shown in fig. 4, and fig. 4 is a schematic diagram of the frame format of Option 82.

The frame format of Option82 conforms to the specification of RFC 3046. Wherein, the Code: the sequence number indicating the relay agent information option, rfc3046 is defined as 82.

L en is the number of bytes of the Agent Information Field (Agent Information Field), excluding the two bytes of the Code and L en fields.

The Option82 may be composed of a plurality of sub-options, and each Option82 has at least one sub-Option. Referring to FIG. 5, FIG. 5 is a schematic diagram of the Sub-Option format in Option 82.

In fig. 5, the content of Sub0pt indicates the Sub-option number.

The sub-option Value indicates the corresponding field identification.

The row standard YD/T2275 & lt & ltidentification of broadband user access line (port) required by access network technology & gt defines 5 sub-options aiming at the Option82 identification, and can realize identification of information such as O L T equipment identification, slot position number, PON port number, ONU identification and the like of each user.

During specific implementation of the embodiment of the application, the O L T DHCP relay agent Option82 function is activated, and two implementation modes are provided for the second identifier carried in Option 82:

one is to add a sub-option to the option82 of the DHCP protocol for carrying the second identifier.

For the implementation manner, a sub-option can be added in addition to the sub-option used by the protocol to carry the second identifier.

Referring to fig. 6, fig. 6 is a schematic structural diagram of sub-option increase in the embodiment of the present application. The content of Sub0pt in fig. 6 is denoted by i, and it is shown that a sequence number other than 1-5 specified by the protocol can be used.

One is to add a field to the existing sub-option in the option82 of the DHCP protocol for carrying the second identifier.

Step 303, when the second device receives the service flow sent by the O L T through the O L T uplink port, the first identifier and the second identifier carried in the service flow are obtained.

Step 304, the second device determines whether the obtained first identifier and the second identifier correspond to each other according to the configured corresponding relationship between the first identifier and the second identifier, and if so, executes step 305; otherwise, step 306 is performed.

Step 305, the second device determines that the network slice implements isolation.

In step 306, the second device determines that the network slice does not achieve isolation.

In the specific implementation of the present application, the service flow received and sent may be implemented using a DHCP session request.

Whether the network slice is isolated or not is automatically judged during specific implementation, and in specific application, whether the network slice is isolated or not can be artificially judged after the first identification and the second identification are obtained.

Example two

Referring to fig. 7, fig. 7 is a schematic diagram of a testing process of an O L T logic network according to the second embodiment of the present application, and the specific steps are as follows:

step 701, the second device determines to obtain the correspondence between the first identifier and the second identifier according to the configured correspondence between the first identifier and the second identifier, and accumulates the number of times of isolation.

The initial value of the isolation times is set to 0, and the integration of the isolation times can be realized by the way of accumulation, namely 1 is added each time.

Step 702, the second device determines whether the accumulated isolation times are greater than a preset threshold value, and if so, executes step 703; otherwise, step 704 is performed.

In step 703, the second device determines that the network slice implements isolation.

Step 704, the second device continues to wait for receiving the service flow until the accumulated isolation times is greater than a preset threshold value, and determines that the network slice realizes isolation; or determining that the first identifier and the second identifier do not correspond to each other according to the configured corresponding relationship between the first identifier and the second identifier, and further determining that the network slice does not realize isolation.

In this embodiment, a preset threshold is set, so that when the number of times that each network slice implements isolation reaches the preset threshold, it is determined that the network slice actually implements network isolation, so as to avoid accidental implementation.

The above test is performed for each network slice, and all network slices can be tested simultaneously, one by one, or several first tests are selected, so long as the test is performed for all network slices.

And when the second device determines that all the network slices corresponding to the O L T device are isolated, determining that the O L T device system is isolated.

In summary, the first service identifier and the second service identifier are marked on the O L T, and whether the identifier carried by the corresponding service flow received at the O L T is matched with the corresponding relationship between the configured first identifier and the configured second identifier is checked to determine whether each network slice is isolated.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (9)

1. An optical network terminal O L T logic network testing method is characterized in that the method comprises the following steps:

the first equipment sends a service stream to the ONU;

when receiving a service flow sent by an ONU in any network slice, the O L T equipment carries a first identifier and a second identifier in the service flow and sends the service flow to second equipment, wherein the first identifier comprises the ONU identifier;

when the second device receives a service flow sent by O L T, the first identifier and the second identifier carried in the service flow are obtained, whether the obtained first identifier and the obtained second identifier correspond to each other is determined according to the corresponding relation of the configured first identifier and the configured second identifier, if so, the network slice is determined to realize isolation, otherwise, the network slice is not realized isolation;

wherein the O L T device is logically divided into a plurality of network slices.

2. The method of claim 1, wherein the second identity is carried in a field of a subscriber access line identity.

3. The method of claim 2, wherein the second identifier is carried in a field of a subscriber access line identifier, comprising:

and adding a sub-option in the option82 of the dynamic host configuration protocol DHCP protocol for carrying a second identifier.

4. The method of claim 2, wherein the second identifier is carried in a field of a subscriber access line identifier, comprising:

a field is added in the existing sub-option in option82 of the DHCP protocol for carrying the second identifier.

5. The method of claim 1, wherein the first identifier further comprises an O L T device identifier, a slot number, and a Passive Optical Network (PON) port number.

6. The method of claim 1, further comprising:

according to the configured corresponding relation between the first identification and the second identification, accumulating the isolation times when the first identification and the second identification are obtained to correspond;

determining whether the accumulated isolation times are greater than a preset threshold value, and if so, determining that the network slice realizes isolation; otherwise, continuing to wait for receiving the service flow until the accumulated isolation times is greater than a preset threshold value, or determining that the obtained first identifier and the second identifier are not corresponding according to the configured corresponding relationship of the first identifier and the second identifier.

7. The method according to any one of claims 1-6, wherein the method further comprises:

and when the second device determines that all the network slices corresponding to the O L T device are isolated, determining that the O L T device system is isolated.

8. The method according to any one of claims 1 to 6,

the first device and the second device are one device, or two devices.

9. The method according to any of claims 1-6, wherein the traffic flow is a DHCP session request.

Images