WO2021218231A1 - 业务接口的创建方法、装置、***、设备及介质 - Google Patents

业务接口的创建方法、装置、***、设备及介质 Download PDF

Info

Publication number
WO2021218231A1
WO2021218231A1 PCT/CN2021/070352 CN2021070352W WO2021218231A1 WO 2021218231 A1 WO2021218231 A1 WO 2021218231A1 CN 2021070352 W CN2021070352 W CN 2021070352W WO 2021218231 A1 WO2021218231 A1 WO 2021218231A1
Authority
WO
WIPO (PCT)
Prior art keywords
time slot
interface
communication device
service interface
target protocol
Prior art date
Application number
PCT/CN2021/070352
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 WO2021218231A1 publication Critical patent/WO2021218231A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1682—Allocation of channels according to the instantaneous demands of the users, e.g. concentrated multiplexers, statistical multiplexers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device, system, equipment, and medium for creating a service interface.
  • FlexE Flexible Ethernet
  • 5G bearers require larger interface bandwidth and finer network slicing. Therefore, FlexE is particularly important in the context of 5G networks.
  • FlexE technology decouples customer bandwidth and physical interface bandwidth to meet more flexible Ethernet bandwidth requirements, so that network devices no longer need to be subject to the physical interface rate system determined by the IEEE802.3 standard when transmitting customer streams.
  • the embodiment of the present application provides a method for creating a service interface, which is applied to a first communication device, and includes: receiving service interface configuration information for a target protocol interface binding group, and then acquiring the first communication corresponding to the target protocol interface binding group Time slot resource information on the device side and time slot resource information on the second communication device side; wherein the first communication device establishes a communication connection with the second communication device; according to the service interface configuration information, the first communication device Terminal time slot resource information and the second communication device terminal time slot resource information, determine the interface time slot preselection result; send the interface time slot preselection result to the second communication device, the interface time slot preselection result Used by the second communication device to create a service interface for the target protocol interface bundling group; if it is determined that the second communication device has completed the preselection result of the interface timeslot for the target protocol interface bundling group For the creation operation of the matching service interface, the creation operation of the service interface matching the interface time slot preselection result is performed for the target protocol interface bundling group.
  • the embodiment of the present application provides a method for creating a service interface, which is applied to a second communication device, and includes: receiving an interface time slot preselection result sent by the first communication device; wherein the interface time slot preselection result is the first A communication device determines according to the received service interface configuration information for the target protocol interface bundling group, and the first communication device side time slot resource information and the second communication device side time slot resource information corresponding to the target protocol interface bundling group , The first communication device establishes a communication connection with the second communication device; for the target protocol interface bundling group, the creation operation of the service interface matching the interface time slot preselection result is executed, and the execution result is created Feedback to the first communication device; wherein the creation execution result is used by the first communication device to determine that the second communication device has completed preselection with the interface time slot for the target protocol interface bundling group During the creation operation of the service interface matching the result, the creation operation of the service interface matching the interface time slot preselection result is performed for the target protocol interface bundling group.
  • the embodiment of the present application provides an apparatus for creating a service interface, which is applied to a first communication device, and includes: a time slot resource information acquisition module, which is configured to receive service interface configuration information for a target protocol interface bundling group, and then acquire the information related to the target protocol interface binding group.
  • the creation operation of the service interface; the creation module of the service interface is configured to, if it is determined that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, then for all The target protocol interface bundling group executes the creation operation of the service interface matching the
  • the embodiment of the present application provides an apparatus for creating a service interface, which is applied to a second communication device, and includes: an interface time slot preselection result receiving module configured to receive the interface time slot preselection result sent by the first communication device; wherein, The interface time slot preselection result is that the first communication device receives the service interface configuration information for the target protocol interface bundling group according to the received service interface configuration information, and the first communication device side time slot resource information corresponding to the target protocol interface bundling group Determined by the time slot resource information of the second communication device, the first communication device establishes a communication connection with the second communication device; The creation operation of the service interface matching the interface time slot preselection result, and the creation execution result is fed back to the first communication device; wherein the creation execution result is used by the first communication device to determine the second communication When the device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, executes the service matching the interface time slot preselection result for the target protocol interface bundling group The creation operation of the interface.
  • the embodiment of the present application provides a communication device, including: one or more processors; a memory, used to store one or more programs; when the one or more programs are executed by the one or more processors, so that The one or more processors implement the method for creating a service interface applied to the first communication device as described in any embodiment of the present application.
  • the embodiment of the present application provides a communication device, including: one or more processors; a memory, used to store one or more programs; when the one or more programs are executed by the one or more processors, so that The one or more processors implement the method for creating a service interface applied to the second communication device as described in any embodiment of the present application.
  • An embodiment of the present application provides a storage medium that stores a computer program that, when executed by a processor, implements the method for creating a service interface as described in any embodiment of the present application.
  • Figure 1 is a schematic flow diagram of a method for creating a business interface provided by this application
  • Figure 2 is a schematic flowchart of a method for creating a business interface provided by this application
  • FIG. 3 is a schematic flowchart of a method for creating a business interface provided by this application.
  • FIG. 4 is a schematic flowchart of a method for negotiating time slot granularity provided by this application
  • Figure 5 is a schematic flowchart of a method for creating a FlexE Client interface provided by this application
  • FIG. 6 is a schematic diagram of the module structure of a device for creating a service interface provided by this application.
  • FIG. 7 is a schematic diagram of the module structure of an apparatus for creating a service interface provided by this application.
  • FIG. 8 is a schematic structural diagram of a service interface creation system provided by this application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by this application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by this application.
  • N 100G physical links are aggregated into a FlexE Group
  • one is the master device that is, one end device that actively initiates service interface creation under the user's service interface configuration information, which includes
  • the target protocol interface bundling group is the target protocol interface master bundling group, and the other is a slave device, and the target protocol interface bundling group included therein is the target protocol interface slave bundling group.
  • the master device obtains the local time slot resource information and the remote time slot resource information corresponding to the target protocol interface binding group, it selects the available time slots at both ends according to the user's service interface configuration information, and obtains the interface time slot preselection result, and Send the interface time slot preselection result to the slave device.
  • the slave device After the slave device receives the interface time slot preselection result, if the local resources are satisfied, it executes the creation operation of the service interface matching the interface time slot preselection result from the binding group for the target protocol interface, and feeds back the creation execution result to the master equipment. If the master device determines that the slave device has completed the creation of a service interface matching the interface time slot preselection result for the target protocol interface slave bundle group, it will perform the matching with the interface time slot preselect result on the target protocol interface master bundle group at the local end The creation operation of the service interface of the master device and the slave device realize the self-negotiation creation of the service interface in the target protocol interface binding group between the master device and the slave device.
  • FIG. 1 is a schematic flowchart of a method for creating a service interface provided by this application.
  • This method is suitable for the creation of a service interface for time slot binding on a target protocol interface bundling group at both ends of the link, for example, creating a FlexE Client interface for a FlexE Group.
  • This method may be executed by the apparatus for creating a service interface provided in the first communication device provided by the present application, and the apparatus for creating a service interface may be implemented by software and/or hardware and integrated in the communication device.
  • the target protocol interface bundling group refers to the aggregation of multiple interfaces with the interface protocol as the target protocol into an interface bundling group.
  • the target protocol is FlexE
  • the target protocol interface bundling group is FlexE Group
  • MTN Micro Transpot Network
  • the target protocol interface bundling group is MTN Group.
  • the target protocol is not specifically limited.
  • the corresponding service interface is the FlexE Client interface.
  • the corresponding service interface is the MTN Client interface.
  • the target protocol interface bundling group corresponding to the first communication device and the second communication device is created before implementing the service interface creation method provided in this embodiment, and the creation method is not specified in this embodiment. limited. Multiple links can be created between the first communication device and the second communication device, and the group identifiers of the target protocol interface bundling groups corresponding to the same link in the devices at both ends are the same.
  • Service interface configuration information refers to the simplified configuration information of a target protocol interface bundling group by users according to actual application requirements. For example, it can be the bandwidth size of the service interface that is expected to be created in the target protocol interface bundling group, and such service interfaces quantity.
  • multiple sets of service interfaces with different bandwidth sizes can be configured in the service interface configuration information.
  • the method for creating business interfaces provided in this embodiment can be a method for creating any one of the business interfaces in the target protocol interface bundling group. Repeated execution can achieve multiple sets of business interfaces in the target protocol interface bundling group. create. Assume that it is expected to create 5 service interfaces with a bandwidth of 10G, and it is expected to create 10 service interfaces with a bandwidth of 20G, and so on.
  • the bandwidth of the service interface configured by the user should be an integer multiple of the granularity of the implemented time slot (or the granularity of the default time slot).
  • the service interface configuration information may also include a time slot allocation strategy, which refers to the requirements for time slot selection, for example, it can be selected in the order of time slot numbers from small to large, and selected based on cross-physical interfaces.
  • a time slot allocation strategy refers to the requirements for time slot selection, for example, it can be selected in the order of time slot numbers from small to large, and selected based on cross-physical interfaces.
  • the first communication device receives the service interface configuration information for the target protocol interface bundling group issued by the user
  • the first communication device is the master device that initiates service interface creation for the target protocol interface bundling group.
  • the target protocol interface bundling group included is the target protocol interface main bundling group.
  • the second communication device that establishes a communication connection with the first communication device (which can be a direct physical interface connection through multiple optical fibers) is the slave device created in response to the service interface, and the target protocol interface bundling group it includes is the target protocol The interface is from the bundle group.
  • the time slot resource information on the first communication device side includes an unused time slot list, a used time slot list, and an unusable time slot list in the target protocol interface bundling group on the first communication device side.
  • the first communication device may calculate the time slot resource information of the first communication device corresponding to the target protocol interface bundling group based on the time slot resource information of its local physical port.
  • the time slot resource information on the second communication device side includes an unused time slot list, a used time slot list, and an unusable time slot list in the target protocol interface bundling group on the second communication device side.
  • the first communication device can extract the second communication device side time slot corresponding to the target protocol interface bundling group based on the calendar information in the peer overhead frame received by the bottom layer Resource information. Among them, the extraction method should be based on the definition of client calendar in the overhead frame.
  • the client calendar of the slot (Slot) is marked as 0x0000 to indicate that it is not used, and the client calendar of the slot is marked as 0xFFFF to indicate that it cannot be used (the specific reason may be bandwidth limitation, etc.)
  • the Client calendar of the slot is marked with other values, it means that it has been occupied by other service interfaces (FlexE Client) (for details, please refer to the OIF FlexE standard).
  • the time slot resource information of the second communication device acquired by the first communication device may also be advertised by the second communication device, which is not specifically limited in this embodiment.
  • the second communication device can calculate the time slot resource information of the second communication device corresponding to the target protocol interface bundling group based on the time slot resource information of its local physical port, that is, the second communication device side target protocol interface bundling group is not in the target protocol interface bundling group. Used time slot list, used time slot list and unusable time slot list.
  • the representation of a single time slot resource can be (PHY Number, Slot Number).
  • PHY Number represents the physical interface number of the target protocol interface bundling group.
  • the PHY Number of the interfaces at both ends of the same physical link is the same. This information is configured when the target protocol interface bundling group is established;
  • Slot Number represents the number of the time slot in the physical interface. Allocate when the slot is divided.
  • the information of each time slot in the unused time slot list, the used time slot list, and the unusable time slot list can be identified by the foregoing single time slot resource representation.
  • the implementation time slot granularity is sent to the second communication device, and the implementation time slot granularity is used to indicate the first time slot granularity.
  • the communication device performs time slot division and switching for the target protocol interface bundling group;
  • the second communication device If it is determined that the second communication device has completed the time slot division switching operation matching the implementation time slot granularity for the target protocol interface binding group, then executes the time slot division switching operation matching the implementation time slot granularity for the target protocol interface binding group.
  • the first communication device sends the implementation time slot granularity corresponding to the target protocol interface bundling group to the second communication device, and the second communication device receives the implementation time slot granularity and judges whether it is consistent with the local default time slot granularity. If they are consistent, there is no need to switch. If they are inconsistent, it is necessary to determine whether the local target protocol interface bundling group supports the time slot division corresponding to the implementation time slot granularity. If it supports, the target protocol interface bundling group will be based on the implementation time slot granularity. Re-divide the time slots within, and feed back the execution result of the time slot division and switching to the first communication device.
  • the target protocol interface binding group is subject to the implementation time slot granularity.
  • the time slots are re-divided to realize the negotiation of the time slot granularity in the dual-terminal target protocol interface bundling group.
  • the target protocol interface master bundle group of the first communication device sends a time slot negotiation request message to the target protocol interface slave bundle group of the second communication device, and the time slot negotiation request message may carry: implement time slot Granularity and negotiated serial number.
  • the second communication device receives the time slot negotiation request message, finds the corresponding target protocol interface slave bundling group, and determines whether it is allowed to implement the time slot according to the realization ability of the time slot granularity of all physical ports in the target protocol interface from the bundling group The granularity is divided into time slots.
  • the time slot negotiation request response message is sent according to the judgment result.
  • the time slot negotiation request response message can carry: negotiation sequence number (same as the time slot negotiation request message), and negotiation success status or negotiation failure status.
  • the first communication device receives the time slot negotiation request response message. If the time slot negotiation request response message carries the negotiation success status, it sends a time slot switch message.
  • the time slot switch message can carry: implement time slot granularity , Negotiation sequence number (same as the time slot negotiation request response message).
  • the second communication device receives the time slot switch message and checks whether the sequence number carried in the time slot switch message is consistent with the sequence number of the latest time slot negotiation request response message. The agreement indicates that it has been negotiated before. If successful, immediately divide the target protocol interface from all physical ports in the bundling group according to the granularity of the implemented time slot. After the second communication device re-divides the target protocol interface from all physical port time slots in the bundling group, it sends a time slot switch response message.
  • the time slot switch response message can carry: implement the time slot granularity, negotiate the sequence number (and The time slot switching message is the same), the switching success state or the switching failure state.
  • the first communication device receives the time slot switching response message. If the switching success status is carried in the time slot switching response message, it means that the second communication device has completed the switching of the target protocol interface from the time slot granularity in the bundle group and starts to check All physical ports in the main binding group of the target protocol interface execute the time slot granularity corresponding to the granularity of the implemented time slot. When the time slot granularity in the target protocol interface bundling group at both ends is successfully switched, the physical link is re-divided according to the expected time slot granularity.
  • the first communication device may prompt the user, for example, "the two ends of the link do not support the time slot granularity negotiation".
  • the time slot negotiation request response message fed back to the first communication device may also carry: time slot granularity support information
  • the time slot granularity support information may exist in the form of a time slot granularity support list.
  • the first communication device parses and obtains the time slot granularity support information of the second communication device, it can also prompt the user of the time slot granularity support information, so that the user can perform implementation based on the time slot granularity support information of the second communication device Reconfiguration operation of time slot granularity.
  • the first communication device can also start a timer when sending the time slot negotiation request message and/or the time slot switching message. If the timer expires, the second communication device has not received the corresponding feedback time slot negotiation message. To request a response message and/or a time slot switching response message, the first communication device can reassign a negotiation sequence number and re-initiate a time slot negotiation request.
  • the negotiation messages between the first communication device and the second communication device can be sent based on the target protocol interface bundling group.
  • the target protocol interface bundling group as the FlexE Group as an example
  • these negotiation messages can be encapsulated in the Section layer management channel field of the FlexE overhead frame structure and sent based on the FlexE Group.
  • S120 Determine an interface time slot preselection result according to the service interface configuration information, the time slot resource information at the first communication device side, and the time slot resource information at the second communication device side.
  • the interface time slot preselection result refers to the time slot combination that is actively decided for the creation of one or more service interfaces in the target protocol interface bundling group. Specifically, it can be composed of multiple single time slot resources, that is ( PHY Number, Slot Number) collection.
  • the service interface configuration information includes at least the expected bandwidth of the service interface and the time slot allocation strategy; correspondingly, according to the service interface configuration information, the time slot resource information of the first communication device, and the time slot resource information of the second communication device To determine the pre-selection result of the interface time slot, which can be specifically:
  • the unused interface time slot intersection can be specifically determined according to the unused time slot list corresponding to the first communication device and the target protocol interface bundling group and the unused time slot list corresponding to the second communication device and the target protocol interface bundling group.
  • the first communication device selects multiple time slots equal to the required number of time slots as the interface time slot preselection result according to the time slot allocation strategy, and can also preselect the interface time slot results at the same time Assign a client ID (CLIENT ID) as the service interface ID to identify a target protocol interface binding group client.
  • a client ID CLIENT ID
  • the target protocol interface master bundling group of the first communication device sends the interface time slot preselection result to the target protocol interface slave bundling group of the second communication device, and the target protocol interface of the second communication device receives it from the bundling group and executes the interface time slot Preselect the creation operation of the service interface corresponding to the result, and send the creation execution result to the target protocol interface master binding group of the first communication device.
  • the first communication device determines that the target protocol interface of the second communication device from the bundling group has completed the creation operation of the service interface matching the interface time slot preselection result at the remote end, it executes the target protocol interface master bundling group at the local end The creation operation of the service interface that matches the interface time slot preselection result.
  • the first communication device determines that the target protocol interface of the second communication device from the bundling group has not completed the creation operation of the service interface matching the interface time slot preselection result at the remote end, it will not bind the target protocol interface at the local end.
  • the group executes the creation operation of the service interface that matches the preselected result of the interface time slot, so as to avoid the problem of false creation of the service interface.
  • the first communication device that receives the service interface configuration information for the target protocol interface bundling group actively initiates the creation process of the service interface, and obtains the time slot of the first communication device corresponding to the target protocol bundling group.
  • the resource information and the time slot resource information on the second communication device side determine the preselection result of the outgoing interface time slot based on the service interface configuration information, the time slot resource information on the first communication device side, and the time slot resource information on the second communication device side, and Send to the second communication device.
  • the second communication device executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result to the first communication device.
  • the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, it will perform and interface time slot preselection for the target protocol interface bundling group at the local end
  • the creation operation of the matching service interface realizes the auto-negotiation dynamic creation of the service interface in the target protocol interface bundling group between the first communication device and the second communication device, which overcomes the manual configuration of massive time slots.
  • the O&M work is complicated, cumbersome, error-prone, and problems that affect device docking, reducing O&M costs, improving O&M efficiency, and the ease of use and reliability of the time slot bundling service interface technology.
  • the first communication device sends the interface time slot preselection result to the second communication device, which may be specifically: sending the interface time slot preselection result to the second communication device through a service interface negotiation request message;
  • the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, which may specifically be:
  • the target protocol interface master bundling group of the first communication device encapsulates the interface time slot preselection result in a service interface negotiation request message and sends it to the target protocol interface of the second communication device from the bundling group. After the second communication device receives it, it parses the report. The message obtains the interface time slot preselection result, and judges whether the local resource meets the interface time slot preselection result, and encapsulates the judgment result in the service interface negotiation request response message fed back to the service interface negotiation request message and sends it to the first The main binding group of the target protocol interface of a communication device. Among them, the service interface negotiation request response message carries the negotiation success status or the negotiation failure status.
  • the primary binding group of the target protocol interface of the first communication device After the primary binding group of the target protocol interface of the first communication device receives the service interface negotiation request response message, it parses the message to determine whether the response status is the negotiation successful state or the negotiation failed state. If it is the negotiation failure state, the process of creating the service interface this time At the end, if the negotiation is successful, the service interface creation message corresponding to the service interface negotiation request response message is immediately initiated.
  • the target protocol interface of the second communication device After the target protocol interface of the second communication device receives the service interface creation message from the binding group, it executes the creation operation of the service interface corresponding to the interface time slot preselection result, and encapsulates the creation result (successful creation or creation failure) in the and The service interface creation response message corresponding to the service interface creation message is fed back to the first communication device.
  • the primary binding group of the target protocol interface of the first communication device After the primary binding group of the target protocol interface of the first communication device receives the service interface creation response message, it parses the response status. If the creation fails, the service interface creation process ends. If the creation is successful, it immediately The local end executes the creation operation of the service interface corresponding to the interface time slot preselection result. So far, the negotiation and creation of a service interface of the target protocol interface bundling group between the first communication device and the second communication device is completed.
  • the negotiation message between the first communication device and the second communication device can be sent based on the target protocol interface binding group.
  • the target protocol interface bundling group as the FlexE Group
  • these negotiation messages can be encapsulated in the Section layer management channel field of the FlexE overhead frame structure and sent based on the FlexE Group.
  • both ends of device A and device B create a series of service interfaces (FlexE Client) in the FlexE Group according to user expectations, where device A reads the service interface configuration information and time slot allocation configured by the user
  • the policy as the active party, triggers the creation of dynamic negotiation of the service interface, and takes the negotiation to create the first FlexE Client interface with a bandwidth of Y as an example for explanation.
  • the number of time slots required by the FlexE Client interface with a bandwidth of Y bandwidth Y/time slot granularity.
  • Device A selects the time slot from the common intersection of the unused time slot list of FlexEGroup_A (FlexE Group in Device A) and the unused time slot list of FlexEGroup_B (FlexE Group in Device B) according to the time slot allocation strategy algorithm, and Assign the Client ID information as the FlexE Client interface identifier to identify a FlexE Group client.
  • the service interface negotiation request response message can carry: the Client ID of the FlexE Client interface that is expected to be created, and the time slot of the FlexE Client interface that is expected to be created Combination (multiple (PHYNumber, Slot Number) set), and negotiation sequence number.
  • the Device B receives the service interface negotiation request message and finds the corresponding FlexEGroup_B. According to the local unused time slot list of FlexEGroup_B, determine whether the local end can create a FlexE Client interface with the desired time slot combination, and whether the Client ID is not occupied by other FlexE Client interfaces. If the local end can create a FlexE with the desired time slot combination If the Client interface and the Client ID are not occupied, the negotiation content is agreed, and the service interface negotiation request response message is sent.
  • the service interface negotiation request response message can carry: negotiation sequence number (consistent with the service interface negotiation request message), Negotiation success status or negotiation failure status.
  • the service interface creation message can carry: negotiation sequence number ( Consistent with the service interface negotiation request response message), Client ID, create a time slot combination (multiple (PHY Number, Slot Number) set) of the FlexE Client interface, etc.
  • Device B receives the service interface creation message and checks whether the negotiation sequence number it carries is consistent with the last service interface negotiation request response message sent. If they are consistent, it immediately starts to create the FlexE Client interface, the FlexE Client interface Create the Client ID specified in the message corresponding to the service interface, configure the FlexEShim logic layer of the underlying chip, update the Client calendar information, and modify the Client calendar of the allocated slot from 0x0000 to the Client ID, indicating that these time slots are used Transmit the client traffic corresponding to the Client ID. If the FlexE Client interface is successfully created, it sends a service interface creation response message to device A.
  • the service interface creation response message can carry: negotiation sequence number (the same as the service interface creation message), creation success status or creation failure status, if The creation failure can also carry the reason for the creation failure.
  • the FlexE Client interface corresponds to the Client ID specified in the service interface creation message and responds to the FlexEShim logic layer of the underlying chip. Configure, update the Client calendar information, and modify the Client calendar of the allocated slot from 0x0000 to Client ID, indicating that these time slots are used to transmit the client traffic corresponding to the Client ID.
  • an extra logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture is used to implement time slot mapping.
  • PCS sublayer PCS sublayer
  • it refers to the FlexE Shim layer. Slot distribution mechanism to realize the core architecture of FlexE technology.
  • the above technical solution no longer needs to manually specify the complicated time slot binding relationship during configuration; compared with the traditional solution that both ends of the link need to be configured, the above technical solution only requires the user to log in to the device configuration at one end to complete the link dual Collaborative creation of end business interfaces.
  • the control plane protocol is extended to complete the negotiation of the time slot granularity, the negotiation of the binding relationship between the service interface and the time slot member, the manual configuration is converted into automatic negotiation creation, and the parameter consistency negotiation at both ends is carried out through the control plane protocol.
  • the automated creation of business interfaces also improves the ease of use and reliability of FlexE technology.
  • FIG. 2 is a schematic flowchart of a method for creating a service interface provided by this application.
  • This method is suitable for the creation of a service interface for time slot binding on a target protocol interface bundling group at both ends of the link, for example, creating a FlexE Client interface for a FlexE Group.
  • This method may be executed by the apparatus for creating a service interface applied to the second communication device provided by the present application, and the apparatus for creating a service interface may be implemented by software and/or hardware and integrated in the communication device.
  • the method for creating a service interface applied to a second communication device includes:
  • S210 Receive the interface time slot pre-selection result sent by the first communication device; wherein the interface time slot pre-selection result is the first communication device according to the received service interface configuration information for the target protocol interface bundling group, and the interface with the target protocol If the time slot resource information on the first communication device side and the time slot resource information on the second communication device side corresponding to the bundling group are determined, the first communication device establishes a communication connection with the second communication device.
  • the target protocol interface bundling group refers to the aggregation of multiple interfaces with the interface protocol as the target protocol into an interface bundling group.
  • the target protocol is FlexE
  • the target protocol interface bundling group is FlexE Group
  • MTN Micro Transpot Network
  • the target protocol interface bundling group is MTN Group.
  • the target protocol is not specifically limited.
  • the corresponding service interface is the FlexE Client interface.
  • the corresponding service interface is the MTN Client interface.
  • Service interface configuration information refers to the simplified configuration information of a target protocol interface bundling group by users according to actual application requirements. For example, it can be the bandwidth size of the service interface that is expected to be created in the target protocol interface bundling group, and such service interfaces quantity.
  • the service interface configuration information may also include the implementation time slot granularity, which refers to the user's requirements for the time slot granularity, which can be consistent with the default time slot granularity or inconsistent with the default time slot granularity. If the implementation time slot granularity is consistent with the default time slot granularity of the communication device, the user may not configure the implementation time slot granularity.
  • the service interface configuration information may also include a time slot allocation strategy, which refers to the requirements for time slot selection, for example, it can be selected in the order of time slot numbers from small to large, and selected based on cross-physical interfaces.
  • a time slot allocation strategy refers to the requirements for time slot selection, for example, it can be selected in the order of time slot numbers from small to large, and selected based on cross-physical interfaces.
  • the first communication device receives the service interface configuration information for the target protocol interface bundling group issued by the user
  • the first communication device is the master device that initiates service interface creation for the target protocol interface bundling group.
  • the target protocol interface bundling group included is the target protocol interface main bundling group.
  • the second communication device that establishes a communication connection with the first communication device (which can be a direct physical interface connection through multiple optical fibers) is the slave device created in response to the service interface, and the target protocol interface bundling group it includes is the target protocol The interface is from the bundle group.
  • the time slot resource information on the first communication device side includes an unused time slot list, a used time slot list, and an unusable time slot list in the target protocol interface bundling group on the first communication device side.
  • the first communication device may calculate the time slot resource information of the first communication device corresponding to the target protocol interface bundling group based on the time slot resource information of its local physical port.
  • the time slot resource information on the second communication device side includes an unused time slot list, a used time slot list, and an unusable time slot list in the target protocol interface bundling group on the second communication device side.
  • the first communication device can extract the second communication device side time slot corresponding to the target protocol interface bundling group based on the calendar information in the peer overhead frame received by the bottom layer Resource information. Among them, the extraction method should be based on the definition of the client calendar in the overhead frame.
  • the client calendar of the slot (Slot) is marked as 0x0000 to indicate that it is not used, and the client calendar of the slot is marked as 0xFFFF to indicate that it cannot be used (the specific reason may be bandwidth limitation, etc.)
  • the Client calendar of the Slot is marked with other values, it means that it has been occupied by other service interfaces (FlexE Client) (for details, please refer to the OIF FlexE standard).
  • the time slot resource information of the second communication device acquired by the first communication device may also be advertised by the second communication device, which is not specifically limited in this embodiment.
  • the second communication device can calculate the time slot resource information of the second communication device corresponding to the target protocol interface bundling group based on the time slot resource information of its local physical port, that is, the second communication device side target protocol interface bundling group is not in the target protocol interface bundling group. Used time slot list, used time slot list and unusable time slot list.
  • the representation of a single time slot resource can be (PHY Number, Slot Number).
  • PHY Number represents the physical interface number of the target protocol interface bundling group.
  • the PHY Number of the interfaces at both ends of the same physical link is the same. This information is configured when the target protocol interface bundling group is established;
  • Slot Number represents the number of the time slot in the physical interface. Allocate when the slot is divided.
  • the service interface configuration information includes at least the expected bandwidth of the service interface and the time slot allocation strategy; correspondingly, the first communication device according to the service interface configuration information, the time slot resource information of the first communication device, and the second communication device
  • the time slot resource information which determines the pre-selection result of the interface time slot, can be specifically:
  • the first communication device determines the intersection of unused interface timeslots corresponding to the first communication device and the second communication device and the target protocol interface bundling group according to the time slot resource information on the first communication device side and the time slot resource information on the second communication device side; According to the expected value of the service interface bandwidth and the time slot allocation strategy, the pre-selection result of the interface time slot is determined in the intersection of the unused interface time slots.
  • the target protocol interface master bundling group of the first communication device sends the interface time slot preselection result to the target protocol interface slave bundling group of the second communication device, and the target protocol interface of the second communication device receives the interface time slot preselection result from the bundling group .
  • the implementation time slot granularity is that the first communication device determines the service interface configuration information including the implementation time slot granularity and the implementation time slot granularity and the default time slot Sent at different granularity;
  • the target protocol interface bundling group For the target protocol interface bundling group, perform the time slot division switching operation that matches the implementation time slot granularity, and feedback the switching execution result back to the first communication device; wherein the switching execution result is used by the first communication device to determine the second communication device
  • the target protocol interface bundling group performs the time slot division switching operation matching the implementation time slot granularity.
  • the first communication device sends the implementation time slot granularity corresponding to the target protocol interface bundling group to the second communication device, and the second communication device receives the implementation time slot granularity and judges whether it is consistent with the local default time slot granularity. If they are consistent, there is no need to switch. If they are inconsistent, it is necessary to determine whether the local target protocol interface bundling group supports the time slot division corresponding to the implementation time slot granularity. If it supports, the target protocol interface bundling group will be based on the implementation time slot granularity. Re-divide the time slots within, and feed back the execution result of the time slot division and switching to the first communication device.
  • the target protocol interface binding group is subject to the implementation time slot granularity.
  • the time slots are re-divided to realize the negotiation of the time slot granularity in the dual-terminal target protocol interface bundling group.
  • the switching execution result indicates that the second communication device has not completed the time slot division switching operation that matches the implementation time slot granularity for the target protocol interface bundling group
  • the time slot granularity support information of the second communication device is combined with The switching execution result is fed back to the first communication device together; wherein the time slot granularity support information is used to instruct the first communication device to perform the reconfiguration prompt operation for implementing the time slot granularity.
  • the first communication device and the second communication device can negotiate the time slot granularity based on negotiation messages, where the negotiation messages can all be based on the target protocol interface binding group. Sent. Taking the target protocol interface bundling group as the FlexE Group as an example, these negotiation messages can be encapsulated in the Section layer management channel field of the FlexE overhead frame structure and sent based on the FlexE Group.
  • S220 For the target protocol interface binding group, execute the creation operation of the service interface matching the interface time slot preselection result, and feed back the creation execution result back to the first communication device; wherein the creation execution result is used by the first communication device to determine the first communication device Second, when the communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface binding group, it executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface binding group.
  • the first communication device determines that the target protocol interface of the second communication device from the binding group has completed the creation operation of the service interface matching the interface time slot preselection result at the remote end, it executes the target protocol interface master binding group at the local end The creation operation of the service interface that matches the interface time slot preselection result.
  • the first communication device determines that the target protocol interface of the second communication device from the bundling group has not completed the creation operation of the service interface matching the interface time slot preselection result at the remote end, it will not bind the target protocol interface at the local end.
  • the group executes the creation operation of the service interface that matches the preselected result of the interface time slot, so as to avoid the problem of false creation of the service interface.
  • the first communication device that receives the service interface configuration information for the target protocol interface bundling group actively initiates the creation process of the service interface, and obtains the time slot of the first communication device corresponding to the target protocol bundling group.
  • the resource information and the time slot resource information on the second communication device side determine the preselection result of the outgoing interface time slot based on the service interface configuration information, the time slot resource information on the first communication device side, and the time slot resource information on the second communication device side, and Send to the second communication device.
  • the second communication device executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result to the first communication device.
  • the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, it will perform and interface time slot preselection for the target protocol interface bundling group at the local end
  • the creation operation of the matching service interface realizes the auto-negotiation dynamic creation of the service interface in the target protocol interface bundling group between the first communication device and the second communication device, which overcomes the manual configuration of massive time slots.
  • the O&M work is complicated, cumbersome, error-prone, and problems that affect device docking, reducing O&M costs, improving O&M efficiency, and the ease of use and reliability of the time slot bundling service interface technology.
  • the second communication device receives the interface time slot preselection result sent by the first communication device, which may be specifically:
  • the second communication device executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result back to the first communication device, which may be specifically:
  • the creation operation of the service interface matching the interface time slot preselection result is executed for the target protocol interface bundling group, and the creation execution result is passed through the creation message for the service interface
  • the feedback service interface creation response message is sent to the first communication device.
  • the negotiation message between the first communication device and the second communication device can be sent based on the target protocol interface binding group.
  • the target protocol interface bundling group as the FlexE Group
  • these negotiation messages can be encapsulated in the Section layer management channel field of the FlexE overhead frame structure and sent based on the FlexE Group.
  • FIG. 3 is a schematic flowchart of a method for creating a service interface provided by this application.
  • a method for creating a business interface provided by this application specifically includes:
  • the first communication device receives the service interface configuration information for the target protocol interface bundling group, and then obtains the first communication device side time slot resource information and the second communication device side time slot resource information corresponding to the target protocol interface bundling group.
  • the first communication device establishes a communication connection with the second communication device.
  • the first communication device sends the implementation time slot granularity to the second communication device.
  • the second communication device receives the implementation time slot granularity sent by the first communication device, performs a time slot division switching operation that matches the implementation time slot granularity for the target protocol interface bundling group, and feeds back the switching execution result to the first communication equipment.
  • the local end performs and implements the time slot granularity for the target protocol interface bundling group.
  • the matching time slot divides the switching operation.
  • the first communication device determines, according to the time slot resource information on the first communication device side and the time slot resource information on the second communication device side, the unused interface time slots corresponding to the first communication device and the second communication device and the target protocol interface bundling group Intersection.
  • the first communication device determines the interface time slot preselection result in the intersection of the unused interface time slots according to the service interface bandwidth expected value and the time slot allocation strategy, and sends the interface time slot preselection result to the second communication device.
  • the second communication device receives the interface time slot preselection result sent by the first communication device, executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result to the first One communication equipment.
  • the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, then perform the interface time slot preselection for the target protocol interface bundling group. Take the creation operation of the matching business interface.
  • a flexible configuration module (virtual function module) can be configured on device A and device B, which is responsible for realizing the dynamic negotiation and creation of service interfaces on the target protocol interface bundling group. After the device is powered on, it starts to load the module. Virtual function module.
  • One end of the target protocol interface bundling group at both ends of the link is the target protocol interface master bundling group, and the other end is the target protocol interface slave bundling group.
  • the user selects FlexEGroup_A as the target protocol interface master bundling group, and FlexEGroup_B as the target protocol interface slave bundling group.
  • the user performs simplified configuration of the service interface based on FlexEGroup_A: 1) Configure the expected implementation time slot granularity as 1G; 2) Expect to create 20 FlexE Client interfaces with a bandwidth of 10G; 3) The time slot allocation strategy of each FlexE Client interface is cross-physical Port allocation to play a link protection function.
  • the device A Upon receiving the service interface configuration information simply configured by the user, the device A starts to enter the active negotiation process. Among them, all negotiation messages between device A and device B are encapsulated in the section layer management channel field of the FlexE overhead frame structure and sent based on the FlexE Group. FlexEGroup_A and FlexEGroup_B, as the two ends of the bundled link, have the same FlexE Group Number information. When sending a message, the sender fills the FlexE Group Number information in the fixed field FlexE Group Number in the overhead frame structure, and the receiver uses the FlexE Group Number information. The information is checked against the local FlexE Group for processing. It is worth noting that the key information of all negotiation messages between device A and device B can be based on existing control plane protocols such as LLDP (Link Layer Discovery Protocol) extensions to add corresponding negotiation information, It can also add a new control plane protocol separately.
  • LLDP Link Layer Discovery Protocol
  • device A and device B negotiate the time slot granularity of physical ports in the FlexE Group.
  • a method for implementing time slot granularity negotiation specifically includes:
  • Device A sends a time slot negotiation request message to device B, requesting the peer FlexEGroup_B to configure the physical ports in the group according to the desired time slot granularity of 1G.
  • the key information carried in the time slot negotiation request message can be as shown in Table 1.
  • Time slot negotiation request message 0x01
  • Expected implementation time slot granularity The expected time slot particle size of the physical port 1G Negotiation sequence number Used to identify this negotiation.
  • serial number is incremented 0x0001
  • device B After receiving the time slot negotiation request message, device B finds the local FlexEGroup_B through the fixed field FlexE Group Number of the overhead frame structure, and prejudges whether it can meet the expected time slot granularity of all physical ports in FlexEGroup_B. Implement time slot granularity for time slot division. Suppose, after device B resource check and confirmation, all physical ports in FlexEGroup_B can support 1G time slot granularity division.
  • Device B agrees to the negotiation content according to the pre-judgment result, and sends a time slot negotiation request response message.
  • the key information carried in the time slot negotiation request response message can be as shown in Table 2.
  • Device A receives the time slot negotiation request response message and confirms that it carries the successful status, and immediately sends the time slot switching message to trigger the actual switching of the time slot.
  • the key information carried in the time slot switching message can be as shown in Table 3.
  • Time slot switch message 0x03 Implement slot granularity
  • the physical ports in the bundling group are required to divide time slots according to the required time slot granularity 1G Negotiation sequence number
  • Device B receives the time slot switching message and checks whether it is consistent with the negotiation sequence number of the most recently sent time slot negotiation request response message. If they are consistent, it means that the negotiation content has been agreed before. Re-divide the time slot granularity according to 1G.
  • Device B succeeds in re-dividing all physical port time slots in FlexEGroup_B, and immediately sends a time slot switching response message.
  • the key information carried in the time slot switch response message can be as shown in Table 4.
  • Time slot switch response message 0x04 Implement slot granularity
  • the physical ports in the bundling group are required to divide time slots according to the required time slot granularity 1G Negotiation sequence number
  • the sequence number in the simultaneous switching request message 0x0001 Switch result Success status or failure status Success status
  • S470 Device A receives the time slot switching response message and confirms that it carries the successful status, which indicates that the time slot switching of device B has been successful, and immediately performs time slot switching on the local FlexEGroup_A, and all physical ports are divided into time slot granularity according to 1G.
  • the time slot granularity of the physical ports in the two-end bundling group on device A and device B is successfully switched, and the physical links are divided according to the expected implementation time slot granularity.
  • the device A side can give a prompt message "The two ends of the link do not support the time slot granularity negotiation".
  • the user can reconfigure the expected implementation time slot granularity value according to the supported time slot granularity division capability list sent back by the device B and the time slot granularity division capability list of the device A; if the device B end packet response timeout occurs , Device A allocates a new negotiation sequence number and re-initiates a time slot switching negotiation.
  • PHY Number represents the physical port number in the FlexE Group. This information is configured when the FlexE Group is established, and Slot Number represents the physical port number of the time slot. Allocate when the slot is divided.
  • device A calculates time slot resources based on FlexEGroup_A:
  • the local time slot resource table includes: a list of unused time slots, a list of used time slots, and a list of unusable time slots.
  • the local time slot resource table can be generated based on the time slot resource information of the local physical port.
  • the remote time slot resource table includes: a list of unused time slots, a list of used time slots, and a list of unusable time slots.
  • the remote time slot resource table can be extracted based on the calendar information in the overhead frame structure of the opposite end received by the bottom layer.
  • the extraction method is based on the definition of Client calendar in the overhead frame. For example, if the Client calendar of Slot is marked as 0x0000, it means not used, and Client calendar of Slot is not used. The value marked as 0xFFFF means that it cannot be used. The specific reason may be bandwidth limitation and other reasons.
  • the Client calendar of the Slot marked with other values means it has been occupied by other FlexE Client interfaces. For details, please refer to the OIF FlexE standard.
  • device B calculates time slot resources based on FlexEGroup_B:
  • the local time slot resource table includes: a list of unused time slots, a list of used time slots, and a list of unusable time slots.
  • the local time slot resource table can be generated based on the time slot resource information of the local physical port.
  • device A continues to act as the active party to trigger the dynamic negotiation creation of the FlexE Client interface, so that both devices A and B create a series of FlexE Client interfaces according to user expectations.
  • a method for creating a FlexE Client interface specifically includes:
  • Device A reads the FlexE Client interface configuration information configured by the user, including the desired bandwidth, quantity, and time slot allocation strategy for creating the FlexE Client interface.
  • the number of time slots required by the FlexE Client interface with a bandwidth of 10G is bandwidth 10G/time slot granularity 1G, so 10 time slots need to be selected.
  • device A From the common intersection of the unused time slot list of the FlexEGroup_A time slot resource table and the unused time slot list of the FlexEGroup_B remote time slot resource table, device A selects the algorithm according to the cross-physical port allocation strategy, and allocates Client ID information As the FlexE Client interface identifier created by both ends.
  • Device A sends a service interface negotiation request message.
  • the key information carried in the service interface negotiation request message may be as shown in Table 7.
  • Device B receives the service interface negotiation request message, finds the local FlexEGroup_B through the fixed field FlexE Group Number of the overhead frame structure, and judges that it is allowed to create a new FlexE with the desired time slot combination based on the FlexEGroup_B local time slot resource table information Client, and determine whether the Client ID is not occupied by other FlexE Clients.
  • Device B agrees to the content of this negotiation and sends a service interface negotiation request response message.
  • the key information carried in the service interface negotiation request response message may be as shown in Table 8.
  • Device A receives the service interface negotiation request response message, which carries the success status, and sends a service interface creation message to device B.
  • the key information carried in the service interface creation message may be as shown in Table 9.
  • Device B receives the service interface creation message, and verifies whether the negotiation sequence number it carries is consistent with the negotiation sequence number of the most recently sent service interface negotiation request response message. If they agree, it immediately starts to create the FlexE Client interface.
  • the Client interface corresponds to the specified Client ID, and configures the FlexEShim logic layer of the underlying chip, updates the Client calendar information, and changes the Client calendar of the allocated slot from 0x0000 to the Client ID, indicating that these time slots are used to transmit the Client ID corresponding to the client ID. Customer traffic.
  • device B After the creation of the FlexE Client interface is completed, device B sends a service interface creation response message to device A.
  • the key information carried in the service interface creation response message can be as shown in Table 10.
  • device A When device A receives the service interface creation response message and carries the success status, it starts to locally create the FlexE Client interface, which corresponds to the specified Client ID, configures the FlexEShim logic layer of the underlying chip, and updates the Client calendar information , Modify the Client calendar of the allocated slot from 0x0000 to Client ID, indicating that these time slots are used to transmit the client traffic corresponding to the Client ID.
  • the first pair of FlexE Client interfaces with a bandwidth of 10G are created on device A and device B. Repeat S520-S590 until all 20 10G FlexE Client interfaces are created successfully, which is not repeated here.
  • FIG. 6 is a schematic structural diagram of an apparatus for creating a service interface provided by this application.
  • the device for creating a service interface applied to the first communication device provided by the embodiment of the present application may be implemented by software and/or hardware and integrated in the communication device.
  • the device includes: a time slot Resource information acquisition module 610, interface time slot preselection result determination module 620, interface time slot preselection result transmission module 630, and service interface creation module 640. in,
  • the time slot resource information obtaining module 610 is configured to receive service interface configuration information for the target protocol interface bundling group, and then obtain the first communication device side time slot resource information and the second communication device side corresponding to the target protocol interface bundling group Time slot resource information; wherein the first communication device establishes a communication connection with the second communication device;
  • the interface time slot preselection result determining module 620 is configured to determine the interface time slot preselection based on the service interface configuration information, the time slot resource information on the first communication device side, and the time slot resource information on the second communication device side result;
  • the interface time slot preselection result sending module 630 is configured to send the interface time slot preselection result to the second communication device, and the interface time slot preselection result is used by the second communication device for the target protocol interface Bundling group to create business interface;
  • the service interface creation module 640 is configured to target the target protocol if it is determined that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group
  • the interface bundling group executes the creation operation of the service interface matching the interface time slot preselection result.
  • the first communication device that receives the service interface configuration information for the target protocol interface bundling group actively initiates the creation process of the service interface, and obtains the time slot of the first communication device corresponding to the target protocol bundling group.
  • the resource information and the time slot resource information on the second communication device side determine the preselection result of the outgoing interface time slot based on the service interface configuration information, the time slot resource information on the first communication device side, and the time slot resource information on the second communication device side, and Send to the second communication device.
  • the second communication device executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result to the first communication device.
  • the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, it will perform and interface time slot preselection for the target protocol interface bundling group at the local end
  • the creation operation of the matching service interface realizes the auto-negotiation dynamic creation of the service interface in the target protocol interface bundling group between the first communication device and the second communication device, which overcomes the manual configuration of massive time slots.
  • the O&M work is complicated, cumbersome, error-prone, and problems that affect device docking, reducing O&M costs, improving O&M efficiency, and the ease of use and reliability of the time slot bundling service interface technology.
  • the above-mentioned apparatus further includes: a time slot division negotiation module, configured to determine the interface based on the service interface configuration information, the time slot resource information of the first communication device, and the time slot resource information of the second communication device.
  • a time slot division negotiation module configured to determine the interface based on the service interface configuration information, the time slot resource information of the first communication device, and the time slot resource information of the second communication device.
  • time slot division negotiation module is further configured to: if it is determined that the second communication device has not completed the time slot division switching operation that matches the implementation time slot granularity for the target protocol interface bundling group, then according to the The time slot granularity support information fed back by the second communication device executes the reconfiguration prompt operation for implementing the time slot granularity.
  • the service interface configuration information includes at least a service interface bandwidth expected value and a time slot allocation strategy; correspondingly, the interface time slot preselection result determination module 620 is specifically set to be based on the time slot resource information of the first communication device And the time slot resource information of the second communication device, determine the intersection of the unused interface time slots corresponding to the first communication device and the second communication device and the target protocol interface bundling group; according to the expected service interface bandwidth and The time slot allocation strategy determines the preselection result of the interface time slot in the intersection of the unused interface time slots.
  • the interface time slot preselection result sending module 630 is specifically configured to send the interface time slot preselection result to the second communication device through a service interface negotiation request message;
  • the service interface creation module 640 is specifically configured to receive a service interface negotiation request response message fed back by the second communication device in response to the service interface negotiation request message; if the service interface negotiation request response message indicates If the local resource of the second communication device satisfies the interface time slot preselection result, a service interface creation message is sent to the second communication device, and the service interface creation message is used to instruct the second communication
  • the device performs, for the target protocol interface bundling group, a service interface creation operation that matches the interface time slot preselection result; receiving a service interface creation response message fed back by the second communication device for the service interface creation message If the service interface creation response message indicates that the second communication device has completed the service interface creation operation for the target protocol interface bundling group, it is determined that the second communication device has completed the service interface creation operation for the target protocol interface bundling group Complete the creation operation of the service interface matching the interface time slot preselection result.
  • the target protocol interface bundling group includes: a flexible Ethernet FlexE group; and the service interface includes: a FlexEClient interface.
  • the apparatus for creating a service interface applied to the first communication device provided in this embodiment is used to implement the method for creating a service interface applied to the first communication device as described in the embodiment of this application.
  • the implementation principle and technical effect of the apparatus for creating a service interface in the first communication device are similar to the method for creating a service interface in the first communication device described in the embodiment of the present application, and will not be repeated here.
  • FIG. 7 is a schematic structural diagram of an apparatus for creating a service interface provided by this application. As shown in FIG. 7, the apparatus for creating a service interface applied to the second communication device provided by the embodiment of the present application may be implemented by software and/or hardware and integrated in the communication device.
  • the apparatus includes: interface time slot preselection Take the result receiving module 710 and the service interface creation module 720. in,
  • the interface time slot pre-selection result receiving module 710 is configured to receive the interface time slot pre-selection result sent by the first communication device; wherein the interface time slot pre-selection result is the target protocol received by the first communication device.
  • the service interface configuration information of the interface bundling group and the time slot resource information of the first communication device and the time slot resource information of the second communication device corresponding to the target protocol interface bundling group are determined.
  • the second communication device establishes a communication connection;
  • the service interface creation module 720 is configured to perform the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feed back the creation execution result back to the first communication device; wherein The creation execution result is used when the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, For the target protocol interface bundling group, a creation operation of a service interface matching the interface time slot preselection result is performed.
  • the first communication device that receives the service interface configuration information for the target protocol interface bundling group actively initiates the creation process of the service interface, and obtains the time slot of the first communication device corresponding to the target protocol bundling group.
  • the resource information and the time slot resource information on the second communication device side determine the preselection result of the outgoing interface time slot based on the service interface configuration information, the time slot resource information on the first communication device side, and the time slot resource information on the second communication device side, and Send to the second communication device.
  • the second communication device executes the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, and feeds back the creation execution result to the first communication device.
  • the first communication device determines that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, it will perform and interface time slot preselection for the target protocol interface bundling group at the local end
  • the creation operation of the matching service interface realizes the auto-negotiation dynamic creation of the service interface in the target protocol interface bundling group between the first communication device and the second communication device, which overcomes the manual configuration of massive time slots.
  • the O&M work is complicated, cumbersome, error-prone, and problems that affect device docking, reducing O&M costs, improving O&M efficiency, and the ease of use and reliability of the time slot bundling service interface technology.
  • the above-mentioned device further includes: a time slot division negotiation module, configured to receive the implementation time slot granularity sent by the first communication device before receiving the interface time slot preselection result sent by the first communication device; wherein, the The implementation time slot granularity is sent when the first communication device determines that the service interface configuration information includes the implementation time slot granularity and the implementation time slot granularity is different from the default time slot granularity; for the target The protocol interface bundling group executes the time slot division switching operation that matches the granularity of the implemented time slot, and feeds back the switching execution result back to the first communication device; wherein the switching execution result is used for the first communication device When it is determined that the second communication device has completed the time slot division and switching operation that matches the implementation time slot granularity for the target protocol interface bundling group, executes and the implementation time slot for the target protocol interface bundling group.
  • the time slot with matching granularity divides the switching operation.
  • the time slot division negotiation module is further configured to: if the switching execution result indicates that the second communication device has not completed the time slot division switching operation that matches the implementation time slot granularity for the target protocol interface bundling group , The time slot granularity support information of the second communication device and the handover execution result are fed back to the first communication device; wherein the time slot granularity support information is used to indicate the first communication The device executes the reconfiguration prompt operation of implementing the time slot granularity.
  • the interface time slot preselection result receiving module 710 is specifically configured to receive a service interface negotiation request message encapsulating the interface time slot preselection result sent by the first communication device;
  • the service interface creation module 720 is specifically configured to feed back a service interface negotiation request response message to the first communication device for the service interface negotiation request message, wherein the service interface negotiation request response message is Indicate whether the local resource of the second communication device meets the interface time slot pre-selection result; if a service interface creation message sent by the first communication device is received, execute and The interface time slot pre-selection result matches the service interface creation operation, and the creation execution result is sent to the first communication device through a service interface creation response message fed back to the service interface creation message.
  • the target protocol interface bundling group includes: a FlexE group; the service interface includes: a FlexE Client interface.
  • the apparatus for creating a service interface applied to a second communication device provided in this embodiment is used to implement the method for creating a service interface applied to a second communication device as described in the embodiment of this application.
  • the implementation principle and technical effect of the apparatus for creating a service interface in the second communication device are similar to the method for creating a service interface in the second communication device described in the embodiment of the present application, and will not be repeated here.
  • FIG. 8 is a schematic structural diagram of a system for creating a business interface provided by this application.
  • a service interface creation system provided by an embodiment of the present application includes: a first communication device 810 and a second communication device 820.
  • first communication device 810 and the second communication device 820 establish a communication connection, for example, a direct physical interface connection may be performed through multiple optical fibers 830.
  • the first communication device 810 executes the method for creating a service interface applied to the first communication device as described in any embodiment of the present application;
  • the second communication device 820 executes the method for creating a service interface applied to the second communication device as described in any embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by this application.
  • the communication device provided by this application includes: one or more processors 910 and a memory 920;
  • the processor 910 of the communication device may be one or more.
  • one processor 910 is taken as an example; the memory 920 is used to store one or more programs; the one or more programs are used by the one or
  • the multiple processors 910 execute, so that the one or more processors 910 implement the method for creating a service interface applied to the first communication device as described in the embodiment of the present application.
  • the processor 910 and the memory 920 in the communication device may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the memory 920 can be configured to store software programs, computer-executable programs, and modules, such as the program instructions/program instructions corresponding to the method for creating a service interface in the first communication device as described in the embodiments of the present application. Modules (for example, the time slot resource information acquisition module 610, the interface time slot preselection result determination module 620, the interface time slot preselection result sending module 630, and the service interface Create module 640).
  • the memory 920 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 920 may further include a memory remotely provided with respect to the processor 910, and these remote memories may be connected to a communication node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • FIG. 10 is a schematic structural diagram of a communication device provided by this application.
  • the communication device provided by this application includes: one or more processors 1010 and a memory 1020;
  • the processor 1010 of the communication device may be one or more.
  • one processor 1010 is taken as an example; the memory 1020 is used to store one or more programs; the one or more programs are used by the one or The multiple processors 1010 execute, so that the one or more processors 1010 implement the method for creating a service interface applied to the second communication device as described in the embodiment of the present application.
  • the processor 1010 and the memory 1020 in the communication device may be connected through a bus or in other ways.
  • the connection through a bus is taken as an example.
  • the memory 1020 can be configured to store software programs, computer-executable programs, and modules, such as the program instructions corresponding to the method for creating a service interface in the second communication device as described in the embodiments of the present application.
  • Module for example, the interface time slot pre-selection result receiving module 710 and the service interface creation module 720 applied to the device for creating a service interface in the second communication device.
  • the memory 1020 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 1020 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 1020 may further include a memory remotely provided with respect to the processor 1010, and these remote memories may be connected to a communication node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • An embodiment of the present application further provides a storage medium that stores a computer program that, when executed by a processor, realizes the creation of the service interface applied to the first communication device in the embodiment of the present application Method, or implement the method for creating a service interface applied to the second communication device described in the embodiment of the present application.
  • the method for creating a service interface applied to the first communication device includes:
  • the first communication device side time slot resource information and the second communication device side time slot resource information corresponding to the target protocol interface bundling group are acquired; wherein, the first communication device side time slot resource information A communication device establishes a communication connection with the second communication device;
  • the second communication device If it is determined that the second communication device has completed the creation operation of the service interface matching the interface time slot preselection result for the target protocol interface bundling group, then executes the interface time for the target protocol interface bundling group.
  • the creation operation of the service interface that matches the preselected result of the slot.
  • the method for creating a service interface applied to the second communication device includes:
  • the interface time slot pre-selection result is the first communication device according to the received service interface configuration information for the target protocol interface bundling group, and communication with all If the time slot resource information of the first communication device and the time slot resource information of the second communication device corresponding to the target protocol interface bundling group are determined, the first communication device establishes a communication connection with the second communication device;
  • For the target protocol interface bundling group execute the creation operation of the service interface matching the interface time slot preselection result, and feed back the creation execution result back to the first communication device; wherein the creation execution result is used for all
  • executes the target protocol interface bundling group The creation operation of the service interface that matches the pre-selected result of the interface time slot.
  • the computer-executable instructions when executed by a computer processor, they can also be used to implement the method for creating a service interface applied to the first communication device in any of the embodiments of this application, or to implement the implementation of this application.
  • the method for creating a service interface applied to the second communication device described in any one of the examples.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • FLASH flash memory
  • hard disk or optical disk etc., including several instructions to enable a communication device (which can be a personal computer, server, or Network equipment, etc.) execute the methods described in the various embodiments of the present application.
  • the various units and modules included are only in accordance with the functional logic
  • the division is not limited to the above division, as long as the corresponding function can be realized; in addition, the specific names of each functional unit are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the present application.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Object code.
  • ISA instruction set architecture
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) DVD or CD) etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FGPA programmable logic devices

Landscapes

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

Abstract

本申请提出一种业务接口的创建方法、装置、***、设备及介质。该方法包括：接收针对目标协议接口捆绑组的业务接口配置信息，则获取与目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息；确定接口时隙预选取结果，并发送至第二通信设备；如果确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则针对目标协议接口捆绑组执行匹配的业务接口的创建操作。

Description

业务接口的创建方法、装置、***、设备及介质
相关申请的交叉引用
本申请基于申请号为202010364459.5、申请日为2020年4月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请涉及通信技术领域，具体涉及一种业务接口的创建方法、装置、***、设备及介质。
背景技术
FlexE(Flex Ethernet，灵活以太)是基于高速以太(Ethernet)接口进行改进后的技术，满足了高速传送、带宽灵活配置等需求。5G承载相对于传统承载需要更大的接口带宽和更加精细的网络切片，因此FlexE在5G网络背景下显得尤为重要。
FlexE技术核心思想为：首先将多个物理口捆绑形成大的逻辑通道FlexE组(FlexE Group)，再把FlexE Group中的每个物理口划分成独立的时隙颗粒，最后将时隙按照任意数量组合，形成不同带宽的数据承载通道FlexE Client(FlexE客户)，以实现更加灵活的多速率承载。FlexE接口转发时，发送端FlexE设备使用FlexE Client对应的时隙组合发送该客户报文，接收端FlexE设备从FlexEClient对应的时隙组合中提取恢复报文。FlexE技术使客户带宽和物理接口带宽解耦，满足了更灵活的以太网带宽需求，进而网络设备传输客户流时无需再受制于IEEE802.3标准所确定的物理接口速率体系。
发明内容
本申请实施例提供一种业务接口的创建方法，应用于第一通信设备，包括：接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；根据所述业务接口配置信息、所述第一通信设备端时隙资源信 息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本申请实施例提供一种业务接口的创建方法，应用于第二通信设备，包括：接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本申请实施例提供一种业务接口的创建装置，应用于第一通信设备，包括：时隙资源信息获取模块，设置为接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；接口时隙预选取结果确定模块，设置为根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；接口时隙预选取结果发送模块，设置为将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；业务接口的创建模块，设置为如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本申请实施例提供一种业务接口的创建装置，应用于第二通信设备，包括：接口时隙预选取结果接收模块，设置为接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信 设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；业务接口的创建模块，设置为针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本申请实施例提供业务接口的创建***，包括：第一通信设备和至少一个第二通信设备；其中，所述第一通信设备和所述第二通信设备建立通信连接；所述第一通信设置执行如本申请任意实施例所述的应用于第一通信设备中的业务接口的创建方法；所述第二通信设备执行如本申请任意实施例所述的应用于第二通信设备中的业务接口的创建方法。
本申请实施例提供一种通信设备，包括：一个或多个处理器；存储器，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例所述的应用于第一通信设备中的业务接口的创建方法。
本申请实施例提供一种通信设备，包括：一个或多个处理器；存储器，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例所述的应用于第二通信设备中的业务接口的创建方法。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如本申请任意实施例所述的业务接口的创建方法。
关于本申请的以上实施例和其他方面以及其实现方式，在附图说明、具体实施方式和权利要求中提供更多说明。
附图说明
图1为本申请提供的一种业务接口的创建方法的流程示意图；
图2为本申请提供的一种业务接口的创建方法的流程示意图；
图3为本申请提供的一种业务接口的创建方法的流程示意图；
图4为本申请提供的一种实施时隙颗粒度的协商方法的流程示意图；
图5为本申请提供的一种FlexE Client接口的创建方法的流程示意图；
图6为本申请提供的一种业务接口的创建装置的模块结构示意图；
图7为本申请提供的一种业务接口的创建装置的模块结构示意图；
图8为本申请提供的一种业务接口的创建***的结构示意图；
图9为本申请提供的一种通信设备的结构示意图；
图10为本申请提供的一种通信设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
本申请中的术语“第一”、“第二”是用于区别不同的对象，而不是用于描述特定顺序。
为了便于理解，将本申请实施例的主要发明构思以业务接口为FlexE Client为例进行简述。
发明人发现：现有各网络设备商在支持FlexE技术时，普遍采用静态配置的方式来实现客户流承载接口创建。此种静态配置的方式虽然简化了软件上的实现，但随着FlexE技术的广泛应用，却使运维工作变得日益复杂繁琐且极易出错。因此，如何简化接口时隙配置流程，减少人工配置操作，提高运维效率，是当前亟待解决的问题。
基于此，本申请提供一种业务接口的创建方法、装置、***、设备及介质，以克服由于人工进行海量时隙配置而导致的运维工作复杂繁琐易出错、影响设备对接的问题，实现业务接口的动态协商创建，降低运维成本，提升运维效率以及业务接口技术的易用性和可靠性。
目前，FlexE技术使用时，基于Group/Client接口结构，需要进行层次化接口配置。当多个物理口捆绑形成大逻辑通道FlexE Group后，会进一步的通过静态配置，指定时隙和FlexE Client的绑定关系。配置流程如下：
1)N条100G物理链路聚合成一个FlexE Group；
2)在链路两端的FlexE Group接口上配置相同的时隙颗粒度5G(标准中的时隙默认值)，保证链路两端时隙切割颗粒度一致。此时，每个100G物理口中时隙个数为20个，FlexE Group下时隙数量共计为20*N个；
3)进一步在链路两端创建FlexE Client接口。假设客户带宽需要40G接口，根据5G时隙颗粒度计算则需要8个时隙承载流量，因此在20*N的总时隙资源中，选取8个空闲可用时隙和FlexE Client接口绑定。由于同一客户流的发送端和接收端需要使用同样的时隙通道组合，故链路两端选取的时隙信息需要保持一致。在FlexE Client接口绑定时隙成功后，即 可作为用户流承载的实际业务接口，分配给客户使用。
在本申请中，针对某个目标协议接口捆绑组进行业务接口创建的两端设备中，一个是主设备，也即在用户的业务接口配置信息下主动发起业务接口创建的一端设备，其包括的目标协议接口捆绑组为目标协议接口主捆绑组，另一个是从设备，其包括的目标协议接口捆绑组为目标协议接口从捆绑组。主设备获取到与目标协议接口捆绑组对应的本端时隙资源信息以及远端时隙资源信息之后，根据用户的业务接口配置信息选取两端的可用时隙，得到接口时隙预选取结果，并将接口时隙预选取结果发送至从设备。从设备接收到接口时隙预选取结果之后，如果本端资源满足，则针对目标协议接口从捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈给主设备。主设备如果确定从设备针对目标协议接口从捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口主捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以此实现了主设备和从设备之间目标协议接口捆绑组中的业务接口的自协商创建。
在一个示例性实施方式中，图1为本申请提供的一种业务接口的创建方法的流程示意图。该方法适用于链路双端针对一个目标协议接口捆绑组进行时隙绑定的业务接口创建的情况，例如是针对FlexE Group创建FlexE Client接口等。该方法可以由本申请提供的应用于第一通信设备中的业务接口的创建装置执行，该业务接口的创建装置可以由软件和/或硬件实现，并集成在通信设备中。
如图1所示，本申请提供的应用于第一通信设备中的业务接口的创建方法，包括：
S110、接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接。
目标协议接口捆绑组，指的是由接口协议为目标协议的多个接口聚合成一个接口捆绑组。当目标协议为FlexE时，目标协议接口捆绑组为FlexE Group；当目标协议为MTN(Metro Transpot Network)时，目标协议接口捆绑组为MTN Group。在本实施方式中对目标协议不做具体限定。
在一示例中，目标协议接口捆绑组为FlexE组时，对应的业务接口为FlexE Client接口。在另一示例中，目标协议接口捆绑组为MTN组时，对应的业务接口为MTN Client接口。
其中，第一通信设备和第二通信设备中对应的目标协议接口捆绑组是在实施本实施方 式提供的业务接口的创建方法之前就已将创建好的，关于其创建方式本实施方式不做具体限定。第一通信设备和第二通信设备之间可以创建多条链路，两端设备中同一链路对应的目标协议接口捆绑组的组标识是一致的。
业务接口配置信息，指的是用户根据实际应用需求对一个目标协议接口捆绑组的简化配置信息，例如可以是在这个目标协议接口捆绑组中期望创建的业务接口的带宽大小，以及此类业务接口的数量。
在一示例中，业务接口配置信息中可以配置多组带宽大小不同的业务接口。值得指出的是，本实施方式中提供的业务接口的创建方法，可以是针对目标协议接口捆绑组中任意一个业务接口的创建方法，重复执行即可实现目标协议接口捆绑组中多组业务接口的创建。假设，期望创建5个带宽为10G业务接口，期望创建10个带宽为20G业务接口，等等。
同时，业务接口配置信息中，还可以包括实施时隙颗粒度，指的是用户对时隙颗粒度的要求，可以与默认时隙颗粒度一致，也可以与默认时隙颗粒度不一致。如果实施时隙颗粒度与通信设备的默认时隙颗粒度一致，用户也可以不配置实施时隙颗粒度。
值得注意的是，用户配置的业务接口的带宽大小应该为实施时隙颗粒度(或者默认时隙颗粒度)的整数倍。
另外，业务接口配置信息中，还可以包括时隙分配策略，指的是用于对时隙选取的要求，例如可以是按照时隙号由小到大的顺序选取、按照跨物理接口选取等。
在本实施方式中，假设第一通信设备接收到用户下发的针对目标协议接口捆绑组的业务接口配置信息，则第一通信设备即为针对目标协议接口捆绑组发起业务接口创建的主设备，其包括的目标协议接口捆绑组为目标协议接口主捆绑组。对应的，与第一通信设备建立通信连接(可以是通过多根光纤进行物理接口直连)的第二通信设备即为响应业务接口创建的从设备，其包括的目标协议接口捆绑组为目标协议接口从捆绑组。
与目标协议接口捆绑组对应的第一通信设备端时隙资源信息，即为针对目标协议接口捆绑组的第一通信设备的本端时隙资源信息；与目标协议接口捆绑组对应的第二通信设备端时隙资源信息，即为针对目标协议接口捆绑组的第一通信设备的远端时隙资源信息。其中，时隙资源信息指的是通信设备中目标协议接口捆绑组中各个物理接口的时隙信息，具体可以以时隙资源表的形式存在。
在一示例中，第一通信设备端时隙资源信息包括第一通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。具体的，第一通信设备可以基于 其本地物理口时隙资源信息计算得到与目标协议接口捆绑组对应的第一通信设备端时隙资源信息。
在一示例中，第二通信设备端时隙资源信息包括第二通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。以目标协议接口捆绑组为FlexE Group为例，第一通信设备可以基于底层接收到的对端开销帧中的日历(calendar)信息中提取与目标协议接口捆绑组对应的第二通信设备端时隙资源信息。其中，提取方式要基于开销帧中client calendar的定义，例如，时隙(Slot)的Client calendar标记为0x0000表示未使用，Slot的Client calendar标记为0xFFFF表示无法使用(具体原因可能为带宽限制等)，slot的Client calendar标记为其他值表示已被其他业务接口(FlexE Client)占用(具体可以参考OIF FlexE标准)。在另一示例中，第一通信设备获取的第二通信设备端时隙资源信息也可以是由第二通信设备通告的，对此本实施方式不做具体限定。
同时，第二通信设备可以基于其本地物理口时隙资源信息计算得到与目标协议接口捆绑组对应的第二通信设备端时隙资源信息，也即第二通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。
其中，单个时隙资源的表示方式可以为(PHY Number，Slot Number)。PHY Number表示目标协议接口捆绑组的物理接口编号，同一物理链路两端接口PHY Number相同，此信息在目标协议接口捆绑组建立时配置；Slot Number表示物理接口内时隙编号，此信息在时隙划分时分配。
具体的，未使用时隙列表、已使用时隙列表和不可使用时隙列表中的每个时隙的信息可以通过上述单个时隙资源的表示方式来标识。
在一示例中，在S120之前，还包括：
如果业务接口配置信息中包括实施时隙颗粒度，且实施时隙颗粒度与默认时隙颗粒度不同，则将实施时隙颗粒度发送至第二通信设备，实施时隙颗粒度用于指示第二通信设备针对目标协议接口捆绑组进行时隙划分切换；
如果确定第二通信设备针对目标协议接口捆绑组已完成与实施时隙颗粒度匹配的时隙划分切换操作，则针对目标协议接口捆绑组执行与实施时隙颗粒度匹配的时隙划分切换操作。
在正式进行业务接口创建之前，可以首先进行双端目标协议接口捆绑组内时隙颗粒度的协商，如果业务接口配置信息中包括的实施时隙颗粒度与默认时隙颗粒度相同，则无需进行进行双端目标协议接口捆绑组内时隙颗粒度的协商。
第一通信设备将与目标协议接口捆绑组对应的实施时隙颗粒度发送至第二通信设备，第二通信设备接收到的该实施时隙颗粒度，判断与本端默认时隙颗粒度是否一致，若一致则无需切换，若不一致则需判断本端目标协议接口捆绑组内是否支持与实施时隙颗粒度对应的时隙划分，若支持则将根据实施时隙颗粒度对目标协议接口捆绑组内的时隙重新划分，并将时隙划分切换执行结果反馈给第一通信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与实施时隙颗粒度匹配的时隙划分切换操作，则在本端根据实施时隙颗粒度对目标协议接口捆绑组内的时隙重新划分，以此实现双端目标协议接口捆绑组内时隙颗粒度的协商。
在一具体示例中，第一通信设备的目标协议接口主捆绑组发送时隙协商请求报文给第二通信设备的目标协议接口从捆绑组，时隙协商请求报文中可以携带：实施时隙颗粒度以及协商序列号。
第二通信设备接收到时隙协商请求报文，查找到对应的目标协议接口从捆绑组，根据目标协议接口从捆绑组中所有物理口时隙颗粒度的实现能力，确定是否允许以实施时隙颗粒度进行时隙划分。根据判断结果发送时隙协商请求应答报文，时隙协商请求应答报文中可以携带：协商序列号(与时隙协商请求报文相同)，以及协商成功状态或协商失败状态。
第一通信设备收到时隙协商请求应答报文，如果时隙协商请求应答报文中携带协商成功状态，则发送时隙切换报文，时隙切换报文中可以携带：实施时隙颗粒度，协商序列号(与时隙协商请求应答报文相同)。
第二通信设备收到时隙切换报文，并校验时隙切换报文中携带的序列号是否与最近一次发出的时隙协商请求应答报文的序列号是否一致，一致则表明之前已经协商成功，立即对目标协议接口从捆绑组内所有物理口按照实施时隙颗粒度划分。第二通信设备重新划分目标协议接口从捆绑组内所有物理口时隙成功后，发送时隙切换应答报文，时隙切换应答报文中可以携带：实施时隙颗粒度，协商序列号(与时隙切换报文相同)，切换成功状态或者切换失败状态。
第一通信设备收到时隙切换应答报文，如果时隙切换应答报文中携带切换成功状态，说明第二通信设备端已经完成目标协议接口从捆绑组中的时隙颗粒度切换，开始对目标协议接口主捆绑组内所有物理口执行与实施时隙颗粒度对应的时隙颗粒划分。两端目标协议接口捆绑组内时隙颗粒度均切换成功时，物理链路按照期望的实施时隙颗粒度重新划分。
进一步的，在一示例中，如果确定第二通信设备针对目标协议接口捆绑组未完成与实 施时隙颗粒度匹配的时隙划分切换操作，则根据第二通信设备反馈的时隙颗粒度支持信息，执行实施时隙颗粒度的重配提示操作。
如果第二通信设备反馈的时隙协商请求应答报文中携带的是协商失败状态，第一通信设备可以向用户进行提示，例如“链路双端不支持该时隙颗粒度协商”。
进一步的，第二通信设备在确定其不允许以实施时隙颗粒度进行时隙划分时，向第一通信设备反馈的时隙协商请求应答报文中还可以携带：时隙颗粒度支持信息，时隙颗粒度支持信息可以以时隙颗粒度支持列表的形式存在。
第一通信设备在解析得到第二通信设备的时隙颗粒度支持信息时，还可以将时隙颗粒度支持信息提示给用户，提示用户可以基于第二通信设备的时隙颗粒度支持信息进行实施时隙颗粒度的重配操作。
另外，第一通信设备在发出时隙协商请求报文和/或时隙切换报文的同时，还可以开启一个定时器，如果定时器超时还未接收到第二通信设备对应反馈的时隙协商请求应答报文和/或时隙切换应答报文，第一通信设备则可以重新分配一个协商序列号，重新发起一个时隙协商请求。
值得指出的是，在时隙颗粒度协商阶段，第一通信设备与第二通信设备之间的协商报文均可以基于目标协议接口捆绑组发送的。以目标协议接口捆绑组为FlexE Group为例，这些协商报文均可以封装在FlexE开销帧结构的Section层管理通道字段中，基于FlexE Group发送。
S120、根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定接口时隙预选取结果。
接口时隙预选取结果，指的是针对所述目标协议接口捆绑组中一个或多个业务接口的创建主动决策出的时隙组合，具体可以是多个单个时隙资源构成的，也即(PHY Number，Slot Number)的集合。
在一示例中，业务接口配置信息中至少包括业务接口带宽期望值和时隙分配策略；对应的，根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定接口时隙预选取结果，可以具体为：
根据第一通信设备端时隙资源信息和第二通信设备端时隙资源信息，确定第一通信设备和第二通信设备与目标协议接口捆绑组对应的未使用接口时隙交集；根据业务接口带宽期望值和时隙分配策略，在未使用接口时隙交集中确定接口时隙预选取结果。
未使用接口时隙交集，具体可以根据第一通信设备与目标协议接口捆绑组对应的未使用时隙列表以及第二通信设备与目标协议接口捆绑组对应的未使用时隙列表确定。
假设业务接口带宽期望值为Y，带宽为Y的业务接口所需要的时隙数量＝带宽Y/实施时隙颗粒度。第一通信设备在未使用接口时隙交集中按照时隙分配策略，选择与所需要的时隙数量相等的多个时隙作为接口时隙预选取结果，同时还可以为接口时隙预选取结果分配一个客户标识(CLIENT ID)作为业务接口标识，标识一个目标协议接口捆绑组客户。
S130、将接口时隙预选取结果发送至第二通信设备，接口时隙预选取结果用于第二通信设备针对目标协议接口捆绑组进行业务接口的创建操作。
第一通信设备的目标协议接口主捆绑组将接口时隙预选取结果发送至第二通信设备的目标协议接口从捆绑组，第二通信设备的目标协议接口从捆绑组接收后执行与接口时隙预选取结果对应的业务接口的创建操作，并将创建执行结果发送至第一通信设备的目标协议接口主捆绑组。
S140、如果确定第二通信设备针对所述目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作。
第一通信设备如果确定第二通信设备的目标协议接口从捆绑组已在远端完成了与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口主捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作。
至此，完成了第一通信设备与第二通信设备之间针对目标协议接口捆绑组的一个业务接口的协商创建。
第一通信设备如果确定第二通信设备的目标协议接口从捆绑组未在远端完成了与接口时隙预选取结果匹配的业务接口的创建操作，则在本端不会针对目标协议接口主捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以免造成业务接口误创建的问题。
本实施方式提供的技术方案中，针对目标协议接口捆绑组接收到业务接口配置信息的第一通信设备主动发起业务接口的创建流程，在获取与目标协议捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息之后，根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定出接口时隙预选取结果，并发送至第二通信设备。第二通信设备接收到接口时隙预选取结果之后，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈给第一通 信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以此实现了第一通信设备和第二通信设备之间目标协议接口捆绑组中的业务接口的自协商动态创建，克服了由于人工进行海量时隙配置而导致的运维工作复杂繁琐易出错、影响设备对接的问题，降低了运维成本，提升了运维效率以及时隙捆绑业务接口技术的易用性和可靠性。
在一示例中，第一通信设备将接口时隙预选取结果发送至第二通信设备，可以具体为：将接口时隙预选取结果通过业务接口协商请求报文发送至第二通信设备；
对应的，确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，可以具体为：
接收第二通信设备针对业务接口协商请求报文反馈的业务接口协商请求应答报文；如果业务接口协商请求应答报文指示第二通信设备的本端资源满足接口时隙预选取结果，则向第二通信设备发送业务接口创建报文，业务接口创建报文用于指示第二通信设备针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作；接收第二通信设备针对业务接口创建报文反馈的业务接口创建应答报文；如果业务接口创建应答报文指示第二通信设备针对目标协议接口捆绑组已完成业务接口的创建操作，则确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作。
第一通信设备的目标协议接口主捆绑组将接口时隙预选取结果封装在业务接口协商请求报文中发送给第二通信设备的目标协议接口从捆绑组，第二通信设备接收后，解析报文得到接口时隙预选取结果，并判断本端资源是否满足该接口时隙预选取结果，并将判断结果封装在针对业务接口协商请求报文反馈的业务接口协商请求应答报文中发送给第一通信设备的目标协议接口主捆绑组。其中，业务接口协商请求应答报文中携带协商成功状态或协商失败状态。
第一通信设备的目标协议接口主捆绑组接收到业务接口协商请求应答报文之后，解析报文确定应答状态为协商成功状态还是协商失败状态，若是协商失败状态，则此次业务接口的创建流程结束，若是协商成功状态，则立即发起与业务接口协商请求应答报文对应的业务接口创建报文。
第二通信设备的目标协议接口从捆绑组接收到业务接口创建报文之后，执行与接口时隙预选取结果对应的业务接口的创建操作，并将创建结果(创建成功还是创建失败)封装在 与业务接口创建报文对应的业务接口创建应答报文中，反馈给第一通信设备。
第一通信设备的目标协议接口主捆绑组接收到业务接口创建应答报文之后，解析应答状态，如果为创建失败状态，则此次业务接口的创建流程结束，如果为创建成功状态，则立即在本端执行与接口时隙预选取结果对应的业务接口的创建操作。至此，完成了第一通信设备与第二通信设备之间针对目标协议接口捆绑组的一个业务接口的协商创建。
值得指出的是，在业务接口的创建阶段，第一通信设备与第二通信设备之间的协商报文均可以基于目标协议接口捆绑组发送的。以目标协议接口捆绑组为FlexE Group为例，这些协商报文均可以封装在FlexE开销帧结构的Section层管理通道字段中，基于FlexE Group发送。
在一个具体实施方式中，设备A、设备B两端按照用户期望创建出一系列的FlexE Group中的业务接口(FlexE Client)，其中，设备A读取用户配置的业务接口配置信息和时隙分配策略，作为主动方触发业务接口的动态协商创建，以协商创建第一个带宽为Y的FlexE Client接口为例进行解释说明。
带宽为Y的FlexE Client接口所需时隙数＝带宽Y/时隙颗粒度。设备A从FlexEGroup_A(设备A中的FlexE Group)的未使用时隙列表和FlexEGroup_B(设备B中的FlexE Group)的未使用时隙列表的公共交集中，按照时隙分配策略算法选择时隙，并分配Client ID信息作为FlexE Client接口标识，标识一个FlexE Group客户。
设备A发送携带接口时隙预选取结果的业务接口协商请求报文，具体的，业务接口协商请求应答报文中可以携带：期望创建的FlexE Client接口的Client ID，期望创建FlexE Client接口的时隙组合(多条(PHYNumber，Slot Number)集合)，以及协商序列号。
设备B接收到业务接口协商请求报文，查找到对应的FlexEGroup_B。根据FlexEGroup_B本地的未使用时隙列表，判断本端是否可以以期望的时隙组合创建FlexE Client接口，同时Client ID是否未被其他FlexE Client接口占用，如果本端可以以期望的时隙组合创建FlexE Client接口，Client ID也未被占用则同意本次协商内容，发送业务接口协商请求应答报文，业务接口协商请求应答报文中可以携带：协商序列号(同业务接口协商请求报文一致)，协商成功状态或协商失败状态。
设备A收到业务接口协商请求应答报文，若业务接口协商请求应答报文中携带协商成功状态，继续发送业务接口创建报文到设备B，业务接口创建报文中可以携带：协商序列号(同业务接口协商请求应答报文一致)，Client ID，创建FlexE Client接口的时隙组合(多条 (PHY Number，Slot Number)集合)等。
设备B收到业务接口创建报文，并校验其携带的协商序列号是否和最近一次发出的业务接口协商请求应答报文中的一致，若一致则立即开始创建FlexE Client接口，该FlexE Client接口对应业务接口创建报文中指定的Client ID，并对底层芯片的FlexEShim逻辑层进行配置，更新Client calendar信息，将分配使用的Slot的Client calendar可以从0x0000修改为Client ID，表明使用这些时隙中传送Client ID对应的客户流量。如果FlexE Client接口创建成功，向设备A发送业务接口创建应答报文，业务接口创建应答报文中可以携带：协商序列号(同业务接口创建报文一致)，创建成功状态或创建失败状态，如果创建失败还可以携带创建失败的原因。
设备A收到业务接口创建应答报文，若携带创建成功状态，则开始本地FlexE Client接口创建操作，该FlexE Client接口对应业务接口创建报文中指定的Client ID，并对底层芯片的FlexEShim逻辑层进行配置，更新Client calendar信息，将分配使用的Slot的Client calendar可以从0x0000修改为Client ID，表明使用这些时隙中传送Client ID对应的客户流量。
至此，设备A和设备B上创建出第一对带宽为Y的FlexE Client接口。循环执行上述步骤，直至用户需求的所有FlexE Client接口协商并创建完成，在此不再赘述。
上述实施方式中，在传统以太网架构的MAC与PHY(PCS子层)中间***的一个额外逻辑层，用于实现时隙映射，具体的，在FlexE技术中是指FlexE Shim层，通过基于Calendar的Slot分发机制来实现FlexE技术的核心架构。
上述技术方案不再需要人工在配置时指定复杂的时隙捆绑关系；与传统的链路双端均需要配置的方案相比，上述技术方案只需要用户登陆一端设备配置，就可以完成链路双端业务接口的协同创建。在上述技术方案中，扩展控制面协议，完成时隙颗粒度协商、业务接口与时隙成员绑定关系协商，将人工配置转换成自动协商创建，通过控制面协议进行两端参数一致性协商和业务接口的自动化创建，也提升了FlexE技术的易用性和可靠性。
在一个示例性实施方式中，图2为本申请提供的一种业务接口的创建方法的流程示意图。该方法适用于链路双端针对一个目标协议接口捆绑组进行时隙绑定的业务接口创建的情况，例如是针对FlexE Group创建FlexE Client接口等。该方法可以由本申请提供的应用于第二通信设备中的业务接口的创建装置执行，该业务接口的创建装置可以由软件和/或硬件实现，并 集成在通信设备中。
如图2所示，本申请提供的应用于第二通信设备中的业务接口的创建方法，包括：
S210、接收第一通信设备发送的接口时隙预选取结果；其中，接口时隙预选取结果是第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，第一通信设备与第二通信设备建立通信连接。
目标协议接口捆绑组，指的是由接口协议为目标协议的多个接口聚合成一个接口捆绑组。当目标协议为FlexE时，目标协议接口捆绑组为FlexE Group；当目标协议为MTN(Metro Transpot Network)时，目标协议接口捆绑组为MTN Group。在本实施方式中对目标协议不做具体限定。
在一示例中，目标协议接口捆绑组为FlexE组时，对应的业务接口为FlexE Client接口。在另一示例中，目标协议接口捆绑组为MTN组时，对应的业务接口为MTN Client接口。
业务接口配置信息，指的是用户根据实际应用需求对一个目标协议接口捆绑组的简化配置信息，例如可以是在这个目标协议接口捆绑组中期望创建的业务接口的带宽大小，以及此类业务接口的数量。
同时，业务接口配置信息中，还可以包括实施时隙颗粒度，指的是用户对时隙颗粒度的要求，可以与默认时隙颗粒度一致，也可以与默认时隙颗粒度不一致。如果实施时隙颗粒度与通信设备的默认时隙颗粒度一致，用户也可以不配置实施时隙颗粒度。
另外，业务接口配置信息中，还可以包括时隙分配策略，指的是用于对时隙选取的要求，例如可以是按照时隙号由小到大的顺序选取、按照跨物理接口选取等。
在本实施方式中，假设第一通信设备接收到用户下发的针对目标协议接口捆绑组的业务接口配置信息，则第一通信设备即为针对目标协议接口捆绑组发起业务接口创建的主设备，其包括的目标协议接口捆绑组为目标协议接口主捆绑组。对应的，与第一通信设备建立通信连接(可以是通过多根光纤进行物理接口直连)的第二通信设备即为响应业务接口创建的从设备，其包括的目标协议接口捆绑组为目标协议接口从捆绑组。
在一示例中，第一通信设备端时隙资源信息包括第一通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。具体的，第一通信设备可以基于其本地物理口时隙资源信息计算得到与目标协议接口捆绑组对应的第一通信设备端时隙资源信息。
在一示例中，第二通信设备端时隙资源信息包括第二通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。以目标协议接口捆绑组为FlexE Group为例，第一通信设备可以基于底层接收到的对端开销帧中的日历(calendar)信息中提取与目标协议接口捆绑组对应的第二通信设备端时隙资源信息。其中，提取方式要基于开销帧中Client calendar的定义，例如，时隙(Slot)的Client calendar标记为0x0000表示未使用，Slot的client calendar标记为0xFFFF表示无法使用(具体原因可能为带宽限制等)，Slot的Client calendar标记为其他值表示已被其他业务接口(FlexE Client)占用(具体可以参考OIF FlexE标准)。在另一示例中，第一通信设备获取的第二通信设备端时隙资源信息也可以是由第二通信设备通告的，对此本实施方式不做具体限定。
同时，第二通信设备可以基于其本地物理口时隙资源信息计算得到与目标协议接口捆绑组对应的第二通信设备端时隙资源信息，也即第二通信设备侧目标协议接口捆绑组中未使用时隙列表、已使用时隙列表和不可使用时隙列表。
其中，单个时隙资源的表示方式可以为(PHY Number，Slot Number)。PHY Number表示目标协议接口捆绑组的物理接口编号，同一物理链路两端接口PHY Number相同，此信息在目标协议接口捆绑组建立时配置；Slot Number表示物理接口内时隙编号，此信息在时隙划分时分配。
在一示例中，业务接口配置信息中至少包括业务接口带宽期望值和时隙分配策略；对应的，第一通信设备根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定接口时隙预选取结果，可以具体为：
第一通信设备根据第一通信设备端时隙资源信息和第二通信设备端时隙资源信息，确定第一通信设备和第二通信设备与目标协议接口捆绑组对应的未使用接口时隙交集；根据业务接口带宽期望值和时隙分配策略，在未使用接口时隙交集中确定接口时隙预选取结果。
第一通信设备的目标协议接口主捆绑组将接口时隙预选取结果发送至第二通信设备的目标协议接口从捆绑组，第二通信设备的目标协议接口从捆绑组接收接口时隙预选取结果。
在一示例中，在S210之前，还包括：
接收第一通信设备发送的实施时隙颗粒度；其中，实施时隙颗粒度是所述第一通信设备在确定业务接口配置信息中包括实施时隙颗粒度且实施时隙颗粒度与默认时隙颗粒度不同时发送的；
针对目标协议接口捆绑组执行与实施时隙颗粒度匹配的时隙划分切换操作，并将切换 执行结果反馈回第一通信设备；其中，切换执行结果用于第一通信设备在确定第二通信设备针对目标协议接口捆绑组已完成与实施时隙颗粒度匹配的时隙划分切换操作时，针对目标协议接口捆绑组执行与实施时隙颗粒度匹配的时隙划分切换操作。
在正式进行业务接口创建之前，可以首先进行双端目标协议接口捆绑组内时隙颗粒度的协商，如果业务接口配置信息中包括的实施时隙颗粒度与默认时隙颗粒度相同，则无需进行进行双端目标协议接口捆绑组内时隙颗粒度的协商。
第一通信设备将与目标协议接口捆绑组对应的实施时隙颗粒度发送至第二通信设备，第二通信设备接收到的该实施时隙颗粒度，判断与本端默认时隙颗粒度是否一致，若一致则无需切换，若不一致则需判断本端目标协议接口捆绑组内是否支持与实施时隙颗粒度对应的时隙划分，若支持则将根据实施时隙颗粒度对目标协议接口捆绑组内的时隙重新划分，并将时隙划分切换执行结果反馈给第一通信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与实施时隙颗粒度匹配的时隙划分切换操作，则在本端根据实施时隙颗粒度对目标协议接口捆绑组内的时隙重新划分，以此实现双端目标协议接口捆绑组内时隙颗粒度的协商。
在一示例中，如果切换执行结果指示第二通信设备针对目标协议接口捆绑组未完成与实施时隙颗粒度匹配的时隙划分切换操作，则将第二通信设备的时隙颗粒度支持信息与切换执行结果一同反馈回第一通信设备；其中，时隙颗粒度支持信息用于指示第一通信设备执行所述实施时隙颗粒度的重配提示操作。
值得指出的是，在时隙颗粒度协商阶段，第一通信设备与第二通信设备之间可以基于协商报文进行时隙颗粒度的协商，其中，协商报文均可以基于目标协议接口捆绑组发送的。以目标协议接口捆绑组为FlexE Group为例，这些协商报文均可以封装在FlexE开销帧结构的Section层管理通道字段中，基于FlexE Group发送。
S220、针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回第一通信设备；其中，创建执行结果用于第一通信设备在确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作时，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作。
第二通信设备的目标协议接口从捆绑组接收后执行与接口时隙预选取结果对应的业务接口的创建操作，并将创建执行结果发送至第一通信设备的目标协议接口主捆绑组。
第一通信设备如果确定第二通信设备的目标协议接口从捆绑组已在远端完成了与接口 时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口主捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作。
至此，完成了第一通信设备与第二通信设备之间针对目标协议接口捆绑组的一个业务接口的协商创建。
第一通信设备如果确定第二通信设备的目标协议接口从捆绑组未在远端完成了与接口时隙预选取结果匹配的业务接口的创建操作，则在本端不会针对目标协议接口主捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以免造成业务接口误创建的问题。
本实施方式提供的技术方案中，针对目标协议接口捆绑组接收到业务接口配置信息的第一通信设备主动发起业务接口的创建流程，在获取与目标协议捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息之后，根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定出接口时隙预选取结果，并发送至第二通信设备。第二通信设备接收到接口时隙预选取结果之后，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈给第一通信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以此实现了第一通信设备和第二通信设备之间目标协议接口捆绑组中的业务接口的自协商动态创建，克服了由于人工进行海量时隙配置而导致的运维工作复杂繁琐易出错、影响设备对接的问题，降低了运维成本，提升了运维效率以及时隙捆绑业务接口技术的易用性和可靠性。
在一示例中，第二通信设备接收第一通信设备发送的接口时隙预选取结果，可以具体为：
接收所述第一通信设备发送的封装有接口时隙预选取结果的业务接口协商请求报文；
对应的，第二通信设备针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回第一通信设备，可以具体为：
针对业务接口协商请求报文向第一通信设备反馈业务接口协商请求应答报文，其中，业务接口协商请求应答报文中指示第二通信设备的本端资源是否满足接口时隙预选取结果；
如果接收到第一通信设备发送的业务接口创建报文，则针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果通过针对业务接口创建报文反馈的业务接口创建应答报文发送至第一通信设备。
值得指出的是，在业务接口的创建阶段，第一通信设备与第二通信设备之间的协商报文均可以基于目标协议接口捆绑组发送的。以目标协议接口捆绑组为FlexE Group为例，这些协商报文均可以封装在FlexE开销帧结构的Section层管理通道字段中，基于FlexE Group发送。
本实施方式未尽详细解释之处请参见前述实施方式，在此不再赘述。
在一个具体实施方式中，图3为本申请提供的一种业务接口的创建方法的流程示意图。如图3所示，本申请提供的一种业务接口的创建方法，具体包括：
S310、第一通信设备接收针对目标协议接口捆绑组的业务接口配置信息，则获取与目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息。
其中，第一通信设备与第二通信设备建立通信连接。
S320、如果业务接口配置信息中包括实施时隙颗粒度，且实施时隙颗粒度与默认时隙颗粒度不同，第一通信设备则将实施时隙颗粒度发送至第二通信设备。
S330、第二通信设备接收第一通信设备发送的实施时隙颗粒度，针对目标协议接口捆绑组执行与实施时隙颗粒度匹配的时隙划分切换操作，并将切换执行结果反馈回第一通信设备。
S340、第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与实施时隙颗粒度匹配的时隙划分切换操作，则本端针对目标协议接口捆绑组执行与实施时隙颗粒度匹配的时隙划分切换操作。
S350、第一通信设备根据第一通信设备端时隙资源信息和第二通信设备端时隙资源信息，确定第一通信设备和第二通信设备与目标协议接口捆绑组对应的未使用接口时隙交集。
S360、第一通信设备根据业务接口带宽期望值和时隙分配策略，在未使用接口时隙交集中确定接口时隙预选取结果，并将接口时隙预选取结果发送至第二通信设备。
S370、第二通信设备接收第一通信设备发送的接口时隙预选取结果，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回第一通信设备。
S380、第一通信设备如果确定第二通信设备针对所述目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作。
至此，完成了第一通信设备与第二通信设备之间针对目标协议接口捆绑组的一个业务接口的协商创建。
本实施方式未尽详细解释之处请参见前述实施方式，在此不再赘述。
本申请还提供了一个具体实施方式。在本实施方式中，设备A和设备B上可以配置一个灵活配置模块(虚拟功能模块)，负责实现目标协议接口捆绑组上的进行业务接口的动态协商和创建，在设备上电后启动加载该虚拟功能模块。
假设，设备A存在物理接口1、2、3，设备B存在物理接口1、2、3，均为100G端口，处于FlexE工作模式，两两接口对应直连。在设备A端创建目标协议接口捆绑组FlexEGroup_A，并将物理接口1、2、3配置加入FlexEGroup_A；在设备B端创建目标协议接口捆绑组FlexEGroup_B，并将物理接口1、2、3配置加入FlexEGroup_B。其中，各接口加入目标协议接口捆绑组时按标准建议的5G时隙进行划分。
链路两端的目标协议接口捆绑组一端为目标协议接口主捆绑组，另一端为目标协议接口从捆绑组。在本实施方式中，用户选取FlexEGroup_A作为目标协议接口主捆绑组，FlexEGroup_B作为目标协议接口从捆绑组。
用户基于FlexEGroup_A进行业务接口简化配置：1)配置期望的实施时隙颗粒度为1G；2)期望创建20个带宽为10G的FlexE Client接口；3)各FlexE Client接口的时隙分配策略为跨物理端口分配，以起到链路保护功能。
接收到用户简单配置的业务接口配置信息，设备A开始进入主动协商流程。其中，设备A与设备B之间的所有协商报文，均封装在FlexE开销帧结构的Section层管理通道字段中，基于FlexE Group发送。FlexEGroup_A和FlexEGroup_B作为捆绑链路的两端，具有一样的FlexE Group Number信息，发送报文时，发送端将FlexE Group Number信息填入开销帧结构中的固定字段FlexE Group Number，接收端根据FlexE Group Number信息反查本地FlexE Group进行处理。值得指出的是，设备A与设备B之间的所有协商报文的关键信息可以是基于已有的控制面协议如LLDP(Link Layer Discovery Protocol，链路层发现协议)扩展增加相应的协商信息，也可以是单独新增一种控制面协议。
首先，设备A和设备B对FlexE Group中物理口的时隙颗粒度进行协商。
如图4所示，本申请提供的一种实施时隙颗粒度的协商方法，具体包括：
S410、设备A发送时隙协商请求报文给设备B，请求对端FlexEGroup_B按照期望的时 隙颗粒度1G对组内物理口进行配置。
时隙协商请求报文携带的关键信息可以如表1所示。
表1
关键信息 说明 报文携带值
报文类型 时隙协商请求报文 0x01
期望的实施时隙颗粒度 期望的物理口的时隙颗粒大小 1G
协商序列号 用于标识本次协商，重新开启新协商时，序列号递增 0x0001
S420、设备B接收到时隙协商请求报文之后，通过开销帧结构的固定字段FlexE Group Number，找到本地FlexEGroup_B，根据FlexEGroup_B中所有物理口时隙颗粒度的划分能力，预判断是否能以期望的实施时隙颗粒度进行时隙划分。假设，经设备B资源检查确认，FlexEGroup_B中所有物理口均可以支持1G时隙颗粒度划分。
S430、设备B根据预判断结果同意本次协商内容，发送时隙协商请求应答报文。
时隙协商请求应答报文中携带的关键信息可以如表2所示。
表2
Figure PCTCN2021070352-appb-000001
S440、设备A收到时隙协商请求应答报文，确认携带成功状态，则立即发送时隙切换报文，触发时隙的实际切换。
时隙切换报文中携带的关键信息可以如表3所示。
表3
关键信息 说明 报文携带值
报文类型 时隙切换报文 0x03
实施时隙颗粒度 要求捆绑组内物理口按照要求的时隙颗粒度进行时隙划分 1G
协商序列号 同时隙协商请求应答报文中的序列号 0x0001
S450、设备B收到时隙切换报文，并校验和最近一次发出的时隙协商请求应答报文的 协商序列号是否一致，一致则说明之前已同意协商内容，立即对FlexEGroup_B内所有物理口重新按照1G进行时隙颗粒度划分。
S460、设备B重新划分FlexEGroup_B内所有物理口时隙成功，立即发送时隙切换应答报文。
时隙切换应答报文中携带的关键信息可以如表4所示。
表4
关键信息 说明 报文携带值
报文类型 时隙切换应答报文 0x04
实施时隙颗粒度 要求捆绑组内物理口按照要求的时隙颗粒度进行时隙划分 1G
协商序列号 同时隙切换请求报文中的序列号 0x0001
切换结果 成功状态或失败状态 成功状态
S470、设备A收到时隙切换应答报文，确认携带成功状态，则表明设备B时隙切换已经成功，立即对本地FlexEGroup_A进行时隙切换，所有物理口按照1G进行时隙颗粒度划分。
至此，设备A和设备B上的两端捆绑组内物理口的时隙粒度切换成功，物理链路按照期望的实施时隙颗粒度进行划分。
在上述流程中，如果出现设备B的FlexEGroup_B协商失败、时隙切换失败，设备A端可以给出提示信息“链路双端不支持该时隙颗粒度协商”。用户可以根据设备B端发回的支持的时隙颗粒度划分能力列表和设备A端时隙颗粒度划分能力列表，重新配置期望的实施时隙颗粒度值；如果出现设备B端报文应答超时，设备A端则分配新的协商序列号，重新发起一次时隙切换协商。
接下来，设备A和设备B开始进行时隙资源计算与维护。单个时隙资源的表示方式为(PHY Number，Slot Number)，其中PHY Number表示FlexE Group内的物理口编号，此信息在FlexE Group建立时配置，Slot Number表示物理口内时隙编号，该信息在时隙划分时分配。
具体的，设备A基于FlexEGroup_A计算时隙资源：
其中，本地时隙资源表包含：未使用时隙列表、已用时隙列表以及不可使用时隙列表。本地时隙资源表可以基于本地物理口时隙资源信息生成。
远端时隙资源表包含：未使用时隙列表、已用时隙列表以及不可使用时隙列表。远端 时隙资源表可以基于底层收到的对端开销帧结构中的calendar信息提取，提取方式基于开销帧中Client calendar的定义，如Slot的Client calendar标记为0x0000表示未使用，Slot的Client calendar标记为0xFFFF表示无法使用，具体原因可能为带宽限制等原因，Slot的Client calendar标记为其他值表示已被其他FlexE Client接口占用，具体可以参考OIF FlexE标准。
假设设备A得到的本地时隙资源表和远端时隙资源表如表5所示。
表5
Figure PCTCN2021070352-appb-000002
同时，设备B基于FlexEGroup_B计算时隙资源：
本地时隙资源表包含：未使用时隙列表、已用时隙列表以及不可使用时隙列表。本地时隙资源表可以基于本地物理口时隙资源信息生成。
假设设备B得到的本地时隙资源表如表6所示。
表6
Figure PCTCN2021070352-appb-000003
Figure PCTCN2021070352-appb-000004
接下来，设备A继续作为主动方触发FlexE Client接口的动态协商创建，使得设备A、B两端按照用户期望创建出一系列的FlexE Client接口。
如图5所示，本申请提供的一种FlexE Client接口的创建方法，具体包括：
S510、设备A读取用户配置的FlexE Client接口配置信息，包括期望创建FlexE Client接口的带宽、数量，以及时隙分配策略。
如前所示，期望创建20个带宽为10G的FlexE Client接口，各FlexE Client接口的时隙分配策略为跨物理端口分配。
下面开始创建第一个10G的FlexE Client接口。其中，带宽为10G的FlexE Client接口所需时隙数为带宽10G/时隙颗粒度1G，因此需要选取10个时隙。
S520、设备A从FlexEGroup_A时隙资源表的未使用时隙列表和FlexEGroup_B远端时隙资源表的未使用时隙列表的公共交集中，按照跨物理端口分配策略进行算法选择，并分配Client ID信息作为双端创建的FlexE Client接口标识。
S530、设备A发送业务接口协商请求报文。
业务接口协商请求报文中携带的关键信息可以如表7所示。
表7
Figure PCTCN2021070352-appb-000005
S540、设备B接收到业务接口协商请求报文，通过开销帧结构的固定字段FlexE Group Number，找到本地的FlexEGroup_B，根据FlexEGroup_B本地时隙资源表信息，判断允许以期望的时隙组合创建新的FlexE Client，同时判断Client ID是否未被其他FlexE Client占用。
假设设备B判断出本地时隙资源允许以期望的时隙组合创建新的FlexE Client，同时 Client ID未被其他FlexE Client占用。
S550、设备B同意本次协商内容，发送业务接口协商请求应答报文。
业务接口协商请求应答报文中携带的关键信息可以如表8所示。
表8
Figure PCTCN2021070352-appb-000006
S560、设备A收到业务接口协商请求应答报文，携带成功状态，则发送业务接口创建报文到设备B。
业务接口创建报文中携带的关键信息可以如表9所示。
表9
Figure PCTCN2021070352-appb-000007
S570、设备B收到业务接口创建报文，并校验其携带协商序列号是否和最近一次发出的业务接口协商请求应答报文的协商序列号一致，一致则立即开始创建FlexE Client接口，该FlexE Client接口对应指定的Client ID，并对底层芯片的FlexEShim逻辑层进行配置，更新Client calendar信息，将分配使用的Slot的Client calendar从0x0000修改为Client ID，表明使用这些时隙中传送Client ID对应的客户流量。
S580、在FlexE Client接口创建完成后，设备B向设备A发送业务接口创建应答报文。
业务接口创建应答报文中携带的关键信息可以如表10所示。
表10
Figure PCTCN2021070352-appb-000008
S590、设备A收到业务接口创建应答报文，携带成功状态，则开始本地创建FlexE Client接口，该FlexE Client接口对应指定的Client ID，并对底层芯片的FlexEShim逻辑层进行配置，更新Client calendar信息，将分配使用的Slot的Client calendar从0x0000修改为Client ID，表明使用这些时隙中传送Client ID对应的客户流量。
此时，设备A和设备B上对应创建出第一对带宽为10G的FlexE Client接口。重复S520-S590，直至20个10G的FlexE Client接口全部创建成功，在此不再赘述。
至此，双端FlexE Client接口的动态协商与创建流程结束。
本实施例还提供了一种业务接口的创建装置，图6为本申请提供的一种业务接口的创建装置的结构示意图。如图6所示，本申请实施例提供的应用于第一通信设备中的一种业务接口的创建装置，可以由软件和/或硬件实现，并集成在通信设备中，该装置包括：时隙资源信息获取模块610、接口时隙预选取结果确定模块620、接口时隙预选取结果发送模块630和业务接口的创建模块640。其中，
时隙资源信息获取模块610，设置为接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备 端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；
接口时隙预选取结果确定模块620，设置为根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；
接口时隙预选取结果发送模块630，设置为将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；
业务接口的创建模块640，设置为如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本实施方式提供的技术方案中，针对目标协议接口捆绑组接收到业务接口配置信息的第一通信设备主动发起业务接口的创建流程，在获取与目标协议捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息之后，根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定出接口时隙预选取结果，并发送至第二通信设备。第二通信设备接收到接口时隙预选取结果之后，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈给第一通信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以此实现了第一通信设备和第二通信设备之间目标协议接口捆绑组中的业务接口的自协商动态创建，克服了由于人工进行海量时隙配置而导致的运维工作复杂繁琐易出错、影响设备对接的问题，降低了运维成本，提升了运维效率以及时隙捆绑业务接口技术的易用性和可靠性。
进一步，上述装置还包括：时隙划分协商模块，设置为在根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果之前，如果所述业务接口配置信息中包括实施时隙颗粒度，且所述实施时隙颗粒度与默认时隙颗粒度不同，则将所述实施时隙颗粒度发送至第二通信设备，所述实施时隙颗粒度用于指示所述第二通信设备针对所述目标协议接口捆绑组进行时隙划分切换；如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作。
进一步的，时隙划分协商模块，还设置为如果确定所述第二通信设备针对所述目标协议接口捆绑组未完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则根据所述第二通信设备反馈的时隙颗粒度支持信息，执行所述实施时隙颗粒度的重配提示操作。
进一步的，所述业务接口配置信息中至少包括业务接口带宽期望值和时隙分配策略；对应的，接口时隙预选取结果确定模块620，具体设置为根据所述第一通信设备端时隙资源信息和所述第二通信设备端时隙资源信息，确定所述第一通信设备和第二通信设备与所述目标协议接口捆绑组对应的未使用接口时隙交集；根据所述业务接口带宽期望值和所述时隙分配策略，在所述未使用接口时隙交集中确定所述接口时隙预选取结果。
在一示例中，接口时隙预选取结果发送模块630，具体设置为将所述接口时隙预选取结果通过业务接口协商请求报文发送至第二通信设备；
对应的，业务接口的创建模块640，具体设置为接收所述第二通信设备针对所述业务接口协商请求报文反馈的业务接口协商请求应答报文；如果所述业务接口协商请求应答报文指示所述第二通信设备的本端资源满足所述接口时隙预选取结果，则向所述第二通信设备发送业务接口创建报文，所述业务接口创建报文用于指示所述第二通信设备针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作；接收所述第二通信设备针对所述业务接口创建报文反馈的业务接口创建应答报文；如果所述业务接口创建应答报文指示所述第二通信设备针对所述目标协议接口捆绑组已完成业务接口的创建操作，则确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作。
在一示例中，所述目标协议接口捆绑组包括：灵活以太FlexE组；所述业务接口包括：FlexEClient接口。
本实施例提供的应用于第一通信设备中的业务接口的创建装置用于实现如本申请实施例所述的应用于第一通信设备中的业务接口的创建方法，本实施例提供的应用于第一通信设备中的业务接口的创建装置实现原理和技术效果与本申请实施例所述的应用于第一通信设备中的业务接口的创建方法类似，此处不再赘述。
本实施例还提供了一种业务接口的创建装置，图7为本申请提供的一种业务接口的创建装置的结构示意图。如图7所示，本申请实施例提供的应用于第二通信设备中的业务接口的创建装置，可以由软件和/或硬件实现，并集成在通信设备中，该装置包括：接口时隙预选取 结果接收模块710和业务接口的创建模块720。其中，
接口时隙预选取结果接收模块710，设置为接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；
业务接口的创建模块720，设置为针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
本实施方式提供的技术方案中，针对目标协议接口捆绑组接收到业务接口配置信息的第一通信设备主动发起业务接口的创建流程，在获取与目标协议捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息之后，根据业务接口配置信息、第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息，确定出接口时隙预选取结果，并发送至第二通信设备。第二通信设备接收到接口时隙预选取结果之后，针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈给第一通信设备。第一通信设备如果确定第二通信设备针对目标协议接口捆绑组已完成与接口时隙预选取结果匹配的业务接口的创建操作，则在本端针对目标协议接口捆绑组执行与接口时隙预选取结果匹配的业务接口的创建操作，以此实现了第一通信设备和第二通信设备之间目标协议接口捆绑组中的业务接口的自协商动态创建，克服了由于人工进行海量时隙配置而导致的运维工作复杂繁琐易出错、影响设备对接的问题，降低了运维成本，提升了运维效率以及时隙捆绑业务接口技术的易用性和可靠性。
进一步，上述装置还包括：时隙划分协商模块，设置为在接收第一通信设备发送的接口时隙预选取结果之前，接收所述第一通信设备发送的实施时隙颗粒度；其中，所述实施时隙颗粒度是所述第一通信设备在确定所述业务接口配置信息中包括实施时隙颗粒度且所述实施时隙颗粒度与默认时隙颗粒度不同时发送的；针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作，并将切换执行结果反馈回所述第一通信设备；其中，所述切换执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接 口捆绑组已完成与所述实施时隙颗粒度匹配的时隙划分切换操作时，针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作。
进一步的，时隙划分协商模块，还设置为如果所述切换执行结果指示所述第二通信设备针对所述目标协议接口捆绑组未完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则将所述第二通信设备的时隙颗粒度支持信息与所述切换执行结果一同反馈回所述第一通信设备；其中，所述时隙颗粒度支持信息用于指示所述第一通信设备执行所述实施时隙颗粒度的重配提示操作。
在一示例中，接口时隙预选取结果接收模块710，具体设置为接收所述第一通信设备发送的封装有接口时隙预选取结果的业务接口协商请求报文；
对应的，业务接口的创建模块720，具体设置为针对所述业务接口协商请求报文向所述第一通信设备反馈业务接口协商请求应答报文，其中，所述业务接口协商请求应答报文中指示所述第二通信设备的本端资源是否满足所述接口时隙预选取结果；如果接收到所述第一通信设备发送的业务接口创建报文，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果通过针对业务接口创建报文反馈的业务接口创建应答报文发送至所述第一通信设备。
在一示例中，所述目标协议接口捆绑组包括：FlexE组；所述业务接口包括：FlexE Client接口。
本实施例提供的应用于第二通信设备中的业务接口的创建装置用于实现如本申请实施例所述的应用于第二通信设备中的业务接口的创建方法，本实施例提供的应用于第二通信设备中的业务接口的创建装置实现原理和技术效果与本申请实施例所述的应用于第二通信设备中的业务接口的创建方法类似，此处不再赘述。
本申请实施例还提供了一种业务接口的创建***，图8为本申请提供的一种业务接口的创建***的结构示意图。如图8所示，本申请实施例提供的一种业务接口的创建***，包括：第一通信设备810和第二通信设备820。
其中，第一通信设备810和第二通信设备820建立通信连接，例如可以是通过多条光纤830进行物理接口直连。
第一通信设备810执行如本申请任意实施例所述的应用于第一通信设备中的业务接口的创建方法；
第二通信设备820执行如本申请任意实施例所述的应用于第二通信设备中的业务接口的创建方法。
本实施方式未尽详细解释之处请参见前述实施方式，在此不再赘述。
本申请实施例提供了一种通信设备，图9为本申请提供的一种通信设备的结构示意图，如图9所示，本申请提供的通信设备，包括：一个或多个处理器910和存储器920；该通信设备的处理器910可以是一个或多个，图9中以一个处理器910为例；存储器920用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器910执行，使得所述一个或多个处理器910实现如本申请实施例中所述的应用于第一通信设备中的业务接口的创建方法。
通信设备中的处理器910、存储器920可以通过总线或其他方式连接，图9中以通过总线连接为例。
存储器920作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于第一通信设备中的业务接口的创建方法对应的程序指令/模块(例如，应用于第一通信设备中的业务接口的创建装置中的时隙资源信息获取模块610、接口时隙预选取结果确定模块620、接口时隙预选取结果发送模块630和业务接口的创建模块640)。存储器920可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器920可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器920可进一步包括相对于处理器910远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例提供了一种通信设备，图10为本申请提供的一种通信设备的结构示意图，如图10所示，本申请提供的通信设备，包括：一个或多个处理器1010和存储器1020；该通信设备的处理器1010可以是一个或多个，图10中以一个处理器1010为例；存储器1020用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器1010执行，使得所述一个或多个处理器1010实现如本申请实施例中所述的应用于第二通信设备中的业务接口的创建方法。
通信设备中的处理器1010、存储器1020可以通过总线或其他方式连接，图10中以通过 总线连接为例。
存储器1020作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于第二通信设备中的业务接口的创建方法对应的程序指令/模块(例如，应用于第二通信设备中的业务接口的创建装置中的接口时隙预选取结果接收模块710和业务接口的创建模块720)。存储器1020可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器1020可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器1020可进一步包括相对于处理器1010远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中所述的应用于第一通信设备中的业务接口的创建方法，或者实现本申请实施例中所述的应用于第二通信设备中的业务接口的创建方法。
其中，应用于第一通信设备中的业务接口的创建方法，包括：
接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；
根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；
将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；
如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
应用于第二通信设备中的业务接口的创建方法，包括：
接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目 标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；
针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
可选的，该计算机可执行指令在由计算机处理器执行时还可以用于实现本申请实施例中任一所述的应用于第一通信设备中的业务接口的创建方法，或者实现本申请实施例中任一所述的应用于第二通信设备中的业务接口的创建方法。
通过以上关于实施方式的描述，所属领域的技术人员可以清楚地了解到，本申请可借助软件及必需的通用硬件来实现，当然也可以通过硬件实现，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、闪存(FLASH)、硬盘或光盘等，包括若干指令用以使得一台通信设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
值得注意的是，上述应用于第一通信设备中的业务接口的创建装置，或者应用于第二通信设备中的业务接口的创建装置的实施例中，所包括的各个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能单元的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、 或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和***(数码多功能光碟DVD或CD光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、可编程逻辑器件(FGPA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本申请的范围。因此，本申请的恰当范围将根据权利要求确定。

Claims (16)

  1. 一种业务接口的创建方法，其中，应用于第一通信设备，包括：
    接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；
    根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；
    将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；
    如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
  2. 根据权利要求1所述的方法，其中，在根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果之前，还包括：
    如果所述业务接口配置信息中包括实施时隙颗粒度，且所述实施时隙颗粒度与默认时隙颗粒度不同，则将所述实施时隙颗粒度发送至第二通信设备，所述实施时隙颗粒度用于指示所述第二通信设备针对所述目标协议接口捆绑组进行时隙划分切换；
    如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作。
  3. 根据权利要求2所述的方法，其中，还包括：
    如果确定所述第二通信设备针对所述目标协议接口捆绑组未完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则根据所述第二通信设备反馈的时隙颗粒度支持信息，执行所述实施时隙颗粒度的重配提示操作。
  4. 根据权利要求1所述的方法，其中，所述业务接口配置信息中至少包括业务接口带宽期望值和时隙分配策略；
    根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果，包括：
    根据所述第一通信设备端时隙资源信息和所述第二通信设备端时隙资源信息，确定所述第一通信设备和第二通信设备与所述目标协议接口捆绑组对应的未使用接口时隙交集；
    根据所述业务接口带宽期望值和所述时隙分配策略，在所述未使用接口时隙交集中确定所述接口时隙预选取结果。
  5. 根据权利要求1所述的方法，其中，将所述接口时隙预选取结果发送至第二通信设备，包括：
    将所述接口时隙预选取结果通过业务接口协商请求报文发送至第二通信设备；
    确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，包括：
    接收所述第二通信设备针对所述业务接口协商请求报文反馈的业务接口协商请求应答报文；
    如果所述业务接口协商请求应答报文指示所述第二通信设备的本端资源满足所述接口时隙预选取结果，则向所述第二通信设备发送业务接口创建报文，所述业务接口创建报文用于指示所述第二通信设备针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作；
    接收所述第二通信设备针对所述业务接口创建报文反馈的业务接口创建应答报文；
    如果所述业务接口创建应答报文指示所述第二通信设备针对所述目标协议接口捆绑组已完成业务接口的创建操作，则确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作。
  6. 根据权利要求1所述的方法，其中，所述目标协议接口捆绑组包括：灵活以太FlexE组；所述业务接口包括：FlexE客户Client接口。
  7. 一种业务接口的创建方法，其中，应用于第二通信设备，包括：
    接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；
    针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预 选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
  8. 根据权利要求7所述的方法，其中，在接收第一通信设备发送的接口时隙预选取结果之前，还包括：
    接收所述第一通信设备发送的实施时隙颗粒度；其中，所述实施时隙颗粒度是所述第一通信设备在确定所述业务接口配置信息中包括实施时隙颗粒度且所述实施时隙颗粒度与默认时隙颗粒度不同时发送的；
    针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作，并将切换执行结果反馈回所述第一通信设备；其中，所述切换执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述实施时隙颗粒度匹配的时隙划分切换操作时，针对所述目标协议接口捆绑组执行与所述实施时隙颗粒度匹配的时隙划分切换操作。
  9. 根据权利要求8所述的方法，其中，还包括：
    如果所述切换执行结果指示所述第二通信设备针对所述目标协议接口捆绑组未完成与所述实施时隙颗粒度匹配的时隙划分切换操作，则将所述第二通信设备的时隙颗粒度支持信息与所述切换执行结果一同反馈回所述第一通信设备；其中，所述时隙颗粒度支持信息用于指示所述第一通信设备执行所述实施时隙颗粒度的重配提示操作。
  10. 根据权利要求7所述的方法，其中，接收第一通信设备发送的接口时隙预选取结果，包括：
    接收所述第一通信设备发送的封装有接口时隙预选取结果的业务接口协商请求报文；
    针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备，包括：
    针对所述业务接口协商请求报文向所述第一通信设备反馈业务接口协商请求应答报文，其中，所述业务接口协商请求应答报文中指示所述第二通信设备的本端资源是否满足所述接口时隙预选取结果；
    如果接收到所述第一通信设备发送的业务接口创建报文，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果通过针对业务接口创建报文反馈的业务接口创建应答报文发送至所述第一通信设备。
  11. 根据权利要求7所述的方法，其中，所述目标协议接口捆绑组包括：FlexE组；所 述业务接口包括：FlexE Client接口。
  12. 一种业务接口的创建装置，其中，应用于第一通信设备，包括：
    时隙资源信息获取模块，设置为接收针对目标协议接口捆绑组的业务接口配置信息，则获取与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息以及第二通信设备端时隙资源信息；其中，所述第一通信设备与所述第二通信设备建立通信连接；
    接口时隙预选取结果确定模块，设置为根据所述业务接口配置信息、所述第一通信设备端时隙资源信息以及所述第二通信设备端时隙资源信息，确定接口时隙预选取结果；
    接口时隙预选取结果发送模块，设置为将所述接口时隙预选取结果发送至第二通信设备，所述接口时隙预选取结果用于所述第二通信设备针对所述目标协议接口捆绑组进行业务接口的创建操作；
    业务接口的创建模块，设置为如果确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作，则针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
  13. 一种业务接口的创建装置，其中，应用于第二通信设备，包括：
    接口时隙预选取结果接收模块，设置为接收第一通信设备发送的接口时隙预选取结果；其中，所述接口时隙预选取结果是所述第一通信设备根据接收到的针对目标协议接口捆绑组的业务接口配置信息，以及与所述目标协议接口捆绑组对应的第一通信设备端时隙资源信息和第二通信设备端时隙资源信息确定的，所述第一通信设备与所述第二通信设备建立通信连接；
    业务接口的创建模块，设置为针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作，并将创建执行结果反馈回所述第一通信设备；其中，所述创建执行结果用于所述第一通信设备在确定所述第二通信设备针对所述目标协议接口捆绑组已完成与所述接口时隙预选取结果匹配的业务接口的创建操作时，针对所述目标协议接口捆绑组执行与所述接口时隙预选取结果匹配的业务接口的创建操作。
  14. 一种业务接口的创建***，其中，包括：第一通信设备和第二通信设备；
    其中，所述第一通信设备和所述第二通信设备建立通信连接；
    所述第一通信设置执行如权利要求1-6任一项所述的业务接口的创建方法；
    所述第二通信设备执行如权利要求7-11任一项所述的业务接口的创建方法。
  15. 一种通信设备，其中，包括：
    一个或多个处理器；
    存储器，用于存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-6任一所述的业务接口的创建方法，或者实现如权利要求7-11任一所述的业务接口的创建方法。
  16. 一种存储介质，其中，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-6任一所述的业务接口的创建方法，或者实现如权利要求7-10任一所述的业务接口的创建方法。
PCT/CN2021/070352 2020-04-30 2021-01-05 业务接口的创建方法、装置、***、设备及介质 WO2021218231A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010364459.5 2020-04-30
CN202010364459.5A CN113595670A (zh) 2020-04-30 2020-04-30 业务接口的创建方法、装置、***、设备及介质

Publications (1)

Publication Number Publication Date
WO2021218231A1 true WO2021218231A1 (zh) 2021-11-04

Family

ID=78237251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070352 WO2021218231A1 (zh) 2020-04-30 2021-01-05 业务接口的创建方法、装置、***、设备及介质

Country Status (2)

Country Link
CN (1) CN113595670A (zh)
WO (1) WO2021218231A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023116284A1 (zh) * 2021-12-24 2023-06-29 华为技术有限公司 一种灵活以太网FlexE中小颗粒业务的时隙协商及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006270A (zh) * 2009-08-28 2011-04-06 华为技术有限公司 链路能力信息的协商方法、网络设备和通信***
CN106357421A (zh) * 2015-07-17 2017-01-25 华为技术有限公司 传输灵活以太网的业务流的方法和装置
CN106452812A (zh) * 2015-08-10 2017-02-22 华为技术有限公司 灵活以太网子链路的自协商方法及装置
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置
US20180013511A1 (en) * 2016-07-07 2018-01-11 Infinera Corp. Flexe gmpls signaling extensions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006270A (zh) * 2009-08-28 2011-04-06 华为技术有限公司 链路能力信息的协商方法、网络设备和通信***
CN106357421A (zh) * 2015-07-17 2017-01-25 华为技术有限公司 传输灵活以太网的业务流的方法和装置
CN106452812A (zh) * 2015-08-10 2017-02-22 华为技术有限公司 灵活以太网子链路的自协商方法及装置
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置
US20180013511A1 (en) * 2016-07-07 2018-01-11 Infinera Corp. Flexe gmpls signaling extensions

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023116284A1 (zh) * 2021-12-24 2023-06-29 华为技术有限公司 一种灵活以太网FlexE中小颗粒业务的时隙协商及装置

Also Published As

Publication number Publication date
CN113595670A (zh) 2021-11-02

Similar Documents

Publication Publication Date Title
EP3720050A1 (en) Method and apparatus for deploying network slice
US20220368610A1 (en) Control Method, Apparatus, and System for Collecting Traffic Statistics
WO2018113692A1 (zh) 控制网络切片的方法、转发设备、控制设备和通信***
US5946311A (en) Method for allowing more efficient communication in an environment wherein multiple protocols are utilized
US20200052919A1 (en) Evolved Multimedia Broadcast/Multicast Service (EMBMS) System and EMBMS System Management Method
US11394607B2 (en) Method and system for network configuration
WO2018018409A1 (zh) 一种承载建立的方法、相关装置以及***
WO2015117385A1 (zh) 网络虚拟化处理方法、装置及***
WO2015021629A1 (zh) 一种资源发放方法
WO2015096005A1 (zh) 消息处理方法和网关
US10797986B2 (en) Link discovery method and apparatus
US11616724B2 (en) Packet transmission method and apparatus
CN109561054B (zh) 一种数据传输方法、控制器及接入设备
WO2021022806A1 (zh) 一种网络业务集中处理的网络***、方法及通信设备
CN111083061B (zh) 一种确定组播流的df的方法、设备及***
JP2023520800A (ja) メディアストリーミングタスクの伝送を制御する方法、電子機器、ユーザー端末、ネットワークノード、システム及びコンピュータプログラム
WO2021218231A1 (zh) 业务接口的创建方法、装置、***、设备及介质
CN114205282A (zh) SRv6 Policy的调度方法、***、路由器和控制器
CN110688237B (zh) 转发报文的方法、中间设备和计算机设备
CN113825251A (zh) 会话建立方法、装置、***及计算机存储介质
EP3713184A1 (en) Data transmission method and related device
WO2012155571A1 (zh) 一种基站自配置的方法及装置
WO2023284231A1 (zh) 报文处理方法和报文处理***
WO2021218230A1 (zh) FlexE组创建方法、装置、***、通信设备及介质
CN110636083B (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: 21796081

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 31.03.23)

122 Ep: pct application non-entry in european phase

Ref document number: 21796081

Country of ref document: EP

Kind code of ref document: A1