CN112770198B - Channel access method, device, equipment and storage medium for cross-OLT slicing - Google Patents

Channel access method, device, equipment and storage medium for cross-OLT slicing Download PDF

Info

Publication number
CN112770198B
CN112770198B CN202110007539.XA CN202110007539A CN112770198B CN 112770198 B CN112770198 B CN 112770198B CN 202110007539 A CN202110007539 A CN 202110007539A CN 112770198 B CN112770198 B CN 112770198B
Authority
CN
China
Prior art keywords
multicast
slice
content providing
physical
olt
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN202110007539.XA
Other languages
Chinese (zh)
Other versions
CN112770198A (en
Inventor
余运南
丁宇
杨义
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fiberhome Telecommunication Technologies Co Ltd
Original Assignee
Fiberhome Telecommunication Technologies Co Ltd
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 Fiberhome Telecommunication Technologies Co Ltd filed Critical Fiberhome Telecommunication Technologies Co Ltd
Priority to CN202110007539.XA priority Critical patent/CN112770198B/en
Publication of CN112770198A publication Critical patent/CN112770198A/en
Priority to PCT/CN2022/070004 priority patent/WO2022148330A1/en
Application granted granted Critical
Publication of CN112770198B publication Critical patent/CN112770198B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q11/0067—Provisions for optical access or distribution networks, e.g. Gigabit Ethernet Passive Optical Network (GE-PON), ATM-based Passive Optical Network (A-PON), PON-Ring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0086—Network resource allocation, dimensioning or optimisation

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a cross-OLT slice channel access method, a cross-OLT slice channel access device, cross-OLT slice channel access equipment and a cross-OLT slice channel access storage medium. The method comprises the following steps: when a multicast adding request sent by an ONU (optical network unit) corresponding to a logic slice is received, forwarding the multicast adding request to a plurality of content providing platforms corresponding to the logic slice; based on the multicast join request, respectively operating multicast forwarding table entries of a plurality of physical slices corresponding to the plurality of content providing platforms; and when receiving a multicast data stream issued by the target content providing platform based on the multicast adding request, sending the multicast data stream to the ONU based on the multicast forwarding table entry. According to the invention, aiming at the ONU which subscribes a plurality of content providing platforms under the logic slice, when the ONU forwards the multicast data on different content providing platforms, the forwarding surfaces of the physical slices corresponding to different content providing platforms are multiplexed, thereby realizing the business requirement that the same ONU accesses the channels of IPTV servers of different content service providers.

Description

Channel access method, device, equipment and storage medium for cross-OLT slicing
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for accessing a channel across OLT slices.
Background
IPTV (Internet Protocol Television) service is an important service carried by a passive Optical Network, each content service provider sets up its own IPTV server, different IPTV servers reach an OLT (Optical Line Terminal) through different uplink ports or different VLANs (Virtual Local Area networks) of the same uplink port, and the OLT divides the IPTV servers of different content service providers into different OLT slices.
The OLT slicing technology has the characteristic of service isolation, and a user under each OLT slice can only watch a channel of an IPTV server corresponding to the OLT slice. That is, for a user, only the channel of the IPTV server of the same content provider can be accessed, and the service requirement of accessing the channel of the IPTV server of different content providers cannot be met.
Disclosure of Invention
The invention mainly aims to provide a cross-OLT slicing channel access method, a cross-OLT slicing channel access device, cross-OLT slicing channel access equipment and a cross-OLT slicing channel access storage medium, and aims to solve the problem that the service requirement that the same user accesses channels of IPTV servers of different content service providers cannot be met in the prior art.
In a first aspect, the present invention provides a cross-OLT sliced channel access method, where the cross-OLT sliced channel access method includes:
when a multicast adding request sent by an ONU (optical network unit) corresponding to a logic slice is received, forwarding the multicast adding request to a plurality of content providing platforms corresponding to the logic slice;
respectively operating multicast forwarding table entries of a plurality of physical slices corresponding to the plurality of content providing platforms based on the multicast adding request;
and when receiving a multicast data stream issued by the target content providing platform based on the multicast adding request, sending the multicast data stream to the ONU based on the multicast forwarding table entry.
Optionally, before the step of forwarding, when receiving a multicast join request sent by an ONU corresponding to a logical slice, the multicast join request to a plurality of content providing platforms corresponding to the logical slice, the method further includes:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
Optionally, the step of respectively operating multicast forwarding entries of a plurality of physical slices corresponding to the plurality of content providing platforms based on the multicast join request includes:
inquiring multicast forwarding software table entries of each physical slice based on the ID of each physical slice in a plurality of physical slices corresponding to the content providing platforms, the multicast address corresponding to the multicast adding request and the VLAN;
if the query result is empty, respectively writing multicast forwarding software table entries and multicast forwarding hardware table entries of each physical slice based on the multicast adding request;
and if the query result is not null, newly adding the ID of the logical slice in the viewer list of the queried record.
Optionally, if the query result is null, the step of writing the multicast forwarding software entry and the multicast forwarding hardware entry of each physical slice respectively based on the multicast join request includes:
if the query result is null, adding a new record in the multicast forwarding software table entry of each physical slice, wherein the record comprises a viewer list, a multicast address and a VLAN corresponding to the multicast join request and the ID of the physical slice, and the viewer list comprises the ID of the logical slice;
and newly adding a record comprising the ID of the physical slice, the multicast address corresponding to the multicast joining request and the VLAN in the multicast forwarding hardware table entry of each physical slice.
Optionally, after the step of writing the multicast forwarding software entry and the multicast forwarding hardware entry of each physical slice respectively, the method further includes:
when a multicast leaving request sent by the ONU is received, searching a target record formed by a viewer list, a multicast address and a VLAN corresponding to the multicast leaving request and an ID of the physical slice in a multicast forwarding software table entry of each physical slice;
detecting whether only the ID of the logical slice is included in the viewer list in the target record;
if not, deleting the ID of the logical slice from the viewer list in the target record;
and if so, deleting the target record, and deleting a record formed by the ID of the physical slice, the multicast address corresponding to the multicast leaving request and the VLAN in the multicast forwarding hardware table entry of the corresponding physical slice.
Optionally, the cross-OLT sliced channel access method further includes:
when a downlink multicast protocol message sent by a content providing platform is received, the downlink multicast protocol message is forwarded to a physical slice corresponding to the content providing platform, so that the physical slice forwards the downlink multicast protocol message to a logical slice corresponding to the content providing platform.
In a second aspect, the present invention further provides a cross-OLT sliced channel access device, where the cross-OLT sliced channel access device includes:
the forwarding module is used for forwarding a multicast join request to a plurality of content providing platforms corresponding to the logic slices when the multicast join request sent by the ONU corresponding to the logic slices is received;
a write module, configured to operate multicast forwarding entries of multiple physical slices corresponding to the multiple content providing platforms respectively based on the multicast join request;
and the data sending module is used for sending the multicast data stream to the ONU based on the multicast forwarding table item when receiving the multicast data stream issued by the target content providing platform based on the multicast joining request.
Optionally, the cross-OLT sliced channel access apparatus includes a creating module, configured to:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
In a third aspect, the present invention further provides a cross-OLT sliced channel access device, where the cross-OLT sliced channel access device includes a processor, a memory, and a cross-OLT sliced channel access program stored in the memory and executable by the processor, where the cross-OLT sliced channel access program implements the steps of the cross-OLT sliced channel access method described above when executed by the processor.
In a fourth aspect, the present invention further provides a storage medium, where a cross-OLT slice channel access program is stored on the storage medium, where the cross-OLT slice channel access program, when executed by a processor, implements the steps of the cross-OLT slice channel access method as described above.
In the invention, when a multicast adding request sent by an ONU (optical network unit) corresponding to a logic slice is received, the multicast adding request is forwarded to a plurality of content providing platforms corresponding to the logic slice; respectively operating multicast forwarding table entries of a plurality of physical slices corresponding to the plurality of content providing platforms based on the multicast adding request; and when receiving a multicast data stream issued by the target content providing platform based on the multicast adding request, sending the multicast data stream to the ONU based on the multicast forwarding table entry. According to the invention, aiming at the ONU which subscribes a plurality of content providing platforms under the logic slice, when the ONU forwards the multicast data on different content providing platforms, the forwarding surfaces of the physical slices corresponding to different content providing platforms are multiplexed, thereby realizing the business requirement that the same ONU accesses the channels of IPTV servers of different content service providers.
Drawings
Fig. 1 is a schematic hardware structure diagram of a cross-OLT sliced channel access device according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating an embodiment of a cross-OLT-slice channel access method according to the present invention;
FIG. 3 is a diagram illustrating slicing of an OLT according to an embodiment;
fig. 4 is a schematic view of a scenario for issuing a multicast data stream in an embodiment;
FIG. 5 is a diagram illustrating contents of multicast forwarding software entries and multicast forwarding hardware entries in an embodiment;
FIG. 6 is a diagram illustrating a sliced multicast protocol instance write multicast forwarding hardware entry in an embodiment;
FIG. 7 is a flow diagram illustrating arbitration of entries according to an embodiment;
FIG. 8 is a diagram illustrating content changes of multicast forwarding software entries and multicast forwarding hardware entries in a viewing scenario according to an embodiment;
fig. 9 is a diagram illustrating processing of a multicast protocol packet according to an embodiment;
fig. 10 is a functional block diagram of an embodiment of a cross-OLT sliced channel access device according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In a first aspect, an embodiment of the present invention provides a cross-OLT sliced channel access device.
Referring to fig. 1, fig. 1 is a schematic diagram of a hardware structure of a channel access device sliced across an OLT according to an embodiment of the present invention. In an embodiment of the present invention, the channel access device sliced across the OLT may include a processor 1001 (e.g., a Central Processing Unit (CPU)), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used for realizing connection communication among the components; the user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard); the network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WI-FI interface, WI-FI interface); the memory 1005 may be a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as a magnetic disk memory, and the memory 1005 may optionally be a storage device independent of the processor 1001. Those skilled in the art will appreciate that the hardware configuration depicted in FIG. 1 is not intended to be limiting of the present invention, and may include more or less components than those shown, or some components in combination, or a different arrangement of components.
With continued reference to fig. 1, a memory 1005, which is one type of computer storage medium in fig. 1, may include an operating system, a network communication module, a user interface module, and a channel access program that is sliced across the OLT. Among other things, the processor 1001 may call a channel access program stored in the memory 1005 across the OLT slice and execute a channel access method across the OLT slice provided by an embodiment of the present invention.
In a second aspect, an embodiment of the present invention provides a cross-OLT sliced channel access method.
Referring to fig. 2, fig. 2 is a flowchart illustrating a cross-OLT sliced channel access method according to an embodiment of the present invention. As shown in fig. 2, the channel access method across OLT slices includes:
step S10, when receiving a multicast join request sent by an ONU corresponding to a logical slice, forwarding the multicast join request to a plurality of content providing platforms corresponding to the logical slice;
in this embodiment, according to subscription requests of different ONUs (Optical Network units), a physical slice and a logical slice are created on an OLT device, and each ONU is divided into slices created based on the subscription requests. When the subscription request of the ONU requests to subscribe a single content providing platform, a physical slice corresponding to the single content providing platform is created, and the ONU is divided into the physical slices; when the subscription request of the ONU requests to subscribe a plurality of content providing platforms, the logic slices corresponding to the plurality of content providing platforms are created, and the ONU is divided into the logic slices.
When receiving a multicast join request sent by an ONU, if the multicast join request is determined to be divided into a logic slice according to an ONU identifier, forwarding the multicast join request sent by the ONU to a plurality of content providing platforms corresponding to the logic slice, wherein the content providing platforms are IPTV platforms.
Further, in an embodiment, before step S10, the method further includes:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
In this embodiment, when an ONU only subscribes to a single content providing platform, a physical slice corresponding to the single content providing platform is created, and the ONU is divided into the physical slices; when an ONU subscribes to a plurality of content providing platforms, a logic slice corresponding to the plurality of content providing platforms is created, and the ONU is divided into the logic slice. Referring to fig. 3, fig. 3 is a schematic diagram illustrating slicing of an OLT in an embodiment. As shown in fig. 3, ONU1 subscribes only to IPTV platform 1, and creates a physical slice VS1 on the OLT and divides ONU1 to VS 1; the ONU2 only subscribes to the IPTV platform 2, and then creates a physical slice VS2 on the OLT and divides the ONU2 to the VS 2; ONU3 subscribes to IPTV platforms 1 and 2, creates logical slice VS3 on the OLT and divides ONU3 to VS 3.
Step S20, based on the multicast join request, respectively operating multicast forwarding entries of a plurality of physical slices corresponding to the plurality of content providing platforms;
in this embodiment, the logical slice does not have an independent forwarding plane, and the forwarding plane of the physical slice of the content providing platform corresponding to the logical slice needs to be multiplexed. Each IPTV platform corresponds to a different physical slice, for example, IPTV platform 1 corresponds to physical slice VS1, IPTV platform 2 corresponds to physical slice VS2, and logical slice VS3 corresponds to IPTV platform 1 and IPTV platform 2. When the logical slice in step S10 is VS3, in order to implement the forwarding plane of multiplexing the physical slices VS1 and VS2, the multicast forwarding table entries of VS1 and VS2 need to be operated according to the multicast address, VLAN, and other information included in the multicast join request.
Step S30, when receiving the multicast data stream issued by the target content providing platform based on the multicast join request, sending the multicast data stream to the ONU based on the multicast forwarding entry.
In this embodiment, when the multicast join request is multicast data stream 1 on the IPTV platform 1, after the multicast data stream 1 is sent to the OLT device, based on the forwarding plane of the physical slice VS1 in the OLT device and the multicast forwarding table entry of VS1, the multicast data stream 1 may be forwarded to the ONU that sends the multicast join request; similarly, when the multicast join request is the multicast data stream 2 on the IPTV platform 2, after the multicast data stream 2 is sent to the OLT device, the multicast data stream 2 may be forwarded to the ONU that sends the multicast join request based on the forwarding plane of the physical slice VS2 in the OLT device and the multicast forwarding table entry of the VS 2. Namely, the subscriber ONU under VS3 can request the multicast data stream of IPTV platform 1 and IPTV platform 2. Therefore, the service requirement that the same ONU accesses the channels of the IPTV servers of different content service providers can be realized.
Referring to fig. 4, fig. 4 is a schematic view of a scenario for issuing a multicast data stream in an embodiment. In fig. 4, the dotted line indicates a multicast join request, and the solid line indicates a multicast data stream. And sending the multicast join request initiated by each ONU to the IPTV platform subscribed by the ONU by the corresponding slice.
If the user ONU1 under VS1 requests a multicast data stream with a multicast address of 239.1.1.1, the VS1 forwards the request of the ONU1 to the IPTV platform 1, the main control line card of the OLT adds a multicast forwarding entry corresponding to the multicast join request of this time to the VS1, the IPTV platform 1 responds to the request of the ONU1 and issues the multicast data stream with the multicast address of 239.1.1.1, and forwards the multicast data stream to the ONU1 through the multicast forwarding entry of the VS 1.
If the user ONU2 under VS2 requests the multicast data stream with multicast address 238.1.1.1, the VS2 forwards the request of the ONU2 to the IPTV platform 2, the main control line card of the OLT adds the multicast forwarding entry corresponding to the multicast join request of this time to the VS2, the IPTV platform 2 responds to the request of the ONU2 and issues the multicast data stream with multicast address 238.1.1.1, and forwards the multicast data stream to the ONU2 through the multicast forwarding hardware entry of VS 2.
If a user ONU3 under VS3 requests a multicast data stream with a multicast address of 239.1.1.2, VS3 forwards the request of ONU3 to IPTV platforms 1 and 2, the main control and line card simultaneously adds a multicast forwarding table entry corresponding to the multicast join request of this time for VS1 and VS2, IPTV platform 1 responds to the request of ONU3 and issues the multicast data stream with a multicast address of 239.1.1.2, and forwards the multicast data stream to ONU3 through the multicast forwarding table entry of VS 1. The multicast data stream currently requested by the ONU3 does not exist on the IPTV platform 2, and therefore the request of the ONU3 is directly ignored.
Similarly, when a user ONU3 under VS3 requests a 238.1.1.1 multicast data stream or multicast data streams on other IPTV platforms 2, the VS3 forwards the request of the ONU3 to the IPTV platforms 1 and 2, the main controller and the line card simultaneously add a multicast forwarding entry corresponding to the multicast join request for the VS1 and the VS2, and the IPTV platform 2 sends a corresponding multicast data stream and forwards the multicast data stream to the ONU3 through the multicast forwarding entry of the VS 2. Since there is no multicast data stream currently requested by ONU3 on the IPTV1 platform, the request of ONU3 is directly ignored.
In this embodiment, when a multicast join request sent by an ONU corresponding to a logical slice is received, the multicast join request is forwarded to a plurality of content providing platforms corresponding to the logical slice; respectively operating multicast forwarding table entries of a plurality of physical slices corresponding to the plurality of content providing platforms based on the multicast adding request; and when receiving a multicast data stream issued by the target content providing platform based on the multicast adding request, sending the multicast data stream to the ONU based on the multicast forwarding table entry. According to the embodiment, when the ONU which subscribes a plurality of content providing platforms under the logic slice forwards the multicast data on different content providing platforms, the forwarding surfaces of the physical slices corresponding to the different content providing platforms are multiplexed, so that the service requirement that the same ONU accesses the channels of the IPTV servers of different content service providers is realized.
Further, in one embodiment, step S20 includes:
inquiring multicast forwarding software table entries of each physical slice based on the ID of each physical slice in a plurality of physical slices corresponding to the content providing platforms, the multicast address corresponding to the multicast adding request and the VLAN; if the query result is empty, respectively writing multicast forwarding software table entries and multicast forwarding hardware table entries of each physical slice based on the multicast adding request; and if the query result is not null, newly adding the ID of the logical slice in the viewer list of the queried record.
In this embodiment, for a plurality of physical slices associated with a plurality of content providing platforms corresponding to the logical slice, it is considered that the physical slice itself or another logical slice sharing the multicast forwarding hardware entry of the physical slice may have requested the same multicast data stream, and thus the multicast forwarding hardware entry corresponding to the multicast data stream requested by the current multicast join request has been written. In order to avoid duplicating the multicast forwarding hardware entry, it is necessary to detect whether the multicast forwarding hardware entry of the multicast data stream corresponding to the current multicast join request already exists. If the multicast data stream exists, the multicast data stream requested by the multicast join request is already issued to the OLT, the multicast forwarding hardware table entry of the multicast data stream corresponding to the multicast join request is not required to be written again, and only the multicast forwarding software table entries of a plurality of physical slices corresponding to a plurality of content providing platforms are required to be written; if not, the multicast forwarding software table entries and the multicast forwarding hardware table entries of a plurality of physical slices corresponding to a plurality of content providing platforms need to be written based on the multicast join request.
Specifically, the multicast forwarding software table entry of each physical slice is queried based on the ID of each physical slice in the multiple physical slices corresponding to the multiple content providing platforms, the multicast address and the VLAN corresponding to the multicast join request, and if a result can be queried, it indicates that the multicast data stream requested by the multicast join request is already issued to the OLT, and it is not necessary to write the multicast forwarding hardware table entry of the multicast data stream corresponding to the multicast join request again, but only the multicast forwarding software table entries of the multiple physical slices corresponding to the multiple content providing platforms need to be written; if the result is not found, the multicast forwarding software table entries and the multicast forwarding hardware table entries of a plurality of physical slices corresponding to a plurality of content providing platforms need to be written based on the multicast joining request.
Referring to fig. 5, fig. 5 is a diagram illustrating contents of multicast forwarding software entries and multicast forwarding hardware entries in an embodiment. As shown in fig. 5, the multicast forwarding software entry content includes a physical slice ID, a multicast address, a VLAN, and a viewer list, and the multicast forwarding hardware entry content includes a physical slice ID, a multicast address, and a VLAN. It is particularly noted that the physical slice ID + multicast address + VLAN indicates a multicast data stream, and the viewer list in the multicast forwarding software entry indicates which slices are viewing the channel programs corresponding to the multicast data stream. The multicast forwarding software table entry is stored in the memory of the OLT device, and the multicast forwarding hardware table entry is stored in the forwarding chip of the OLT device.
Referring to fig. 6, fig. 6 is a diagram illustrating a sliced multicast protocol instance write multicast forwarding hardware entry in an embodiment. As shown in fig. 6, the processing logics of the multicast protocol instances of the master control and the line cards are completely the same, the multicast protocol instance of the master control writes the multicast forwarding hardware entry of the forwarding chip of the master control disk, and the multicast protocol instance of the line card writes the multicast forwarding hardware entry of the forwarding chip of the line card. The multicast protocol instance of VS1 writes the multicast forwarding hardware entry of VS1 in the forwarding chip through the multicast forwarding table arbitration module, the multicast protocol instance of VS2 writes the multicast forwarding hardware entry of VS2 in the forwarding chip through the multicast forwarding table arbitration module, and the multicast protocol instance of VS3 writes the multicast forwarding hardware entry of VS1 and the multicast forwarding hardware entry of VS2 in the forwarding chip through the multicast forwarding table arbitration module. Specifically, when receiving an operation multicast forwarding hardware table entry instruction of a multicast protocol instance of VS1 or VS3, the multicast forwarding table arbitration module performs table entry arbitration and determines whether to write a multicast forwarding hardware table entry of VS1 in a forwarding chip if the instruction type is addition; when receiving an operation multicast forwarding hardware entry instruction of a multicast protocol instance of VS2 and VS3, if the instruction type is addition, determining whether to write a multicast forwarding hardware entry of VS2 in a forwarding chip or not after performing entry arbitration. Correspondingly, when the multicast forwarding table arbitration module receives an operation multicast forwarding hardware table entry instruction of a multicast protocol instance of VS1 or VS3, if the instruction type is delete, determining whether to delete the multicast forwarding hardware table entry of VS1 in a forwarding chip after performing table entry arbitration; when receiving an operation multicast forwarding hardware entry instruction of a multicast protocol instance of VS2 and VS3, if the instruction type is delete, determining whether to delete the multicast forwarding hardware entry of VS2 in a forwarding chip after the entry arbitration.
Further, in an embodiment, if the query result is null, the step of writing the multicast forwarding software entry and the multicast forwarding hardware entry of each physical slice respectively based on the multicast join request includes:
if the query result is null, adding a new record in the multicast forwarding software table entry of each physical slice, wherein the record comprises a viewer list, a multicast address and a VLAN corresponding to the multicast join request and the ID of the physical slice, and the viewer list comprises the ID of the logical slice; and newly adding a record comprising the ID of the physical slice, the multicast address corresponding to the multicast joining request and the VLAN in the multicast forwarding hardware table entry of each physical slice.
In this embodiment, referring to fig. 7, fig. 7 is a flowchart illustrating a process of performing entry arbitration in an embodiment. As shown in fig. 7, the slice multicast protocol instance issues an operation multicast forwarding hardware entry instruction, and the instruction content includes: a physical slice ID (which refers to an ID of a physical slice corresponding to the multicast forwarding hardware entry instruction), a multicast address and a VLAN corresponding to the multicast join request, a slice multicast protocol instance ID (for example, when a multicast join request sent by an ONU under slice X is currently received, the multicast protocol instance of slice X issues an instruction to operate the multicast forwarding hardware entry, the slice multicast protocol instance ID is an ID of a slice to which the ONU sending the multicast join request belongs, and slice X may be a physical slice or a logical slice), and an instruction type. The multicast forwarding table arbitration module receives the instruction of operating the multicast forwarding hardware table entry and identifies the type of the instruction. And if the instruction type is adding multicast forwarding hardware entries (aiming at the multicast adding request, the instruction type is adding), inquiring multicast forwarding software entries corresponding to the physical slice ID based on the physical slice ID, the multicast address and the VLAN.
And if the query result is null, adding a record in the multicast forwarding software table entry corresponding to the physical slice ID, wherein the record comprises a viewer list, a multicast address, a VLAN (virtual local area network) and the physical slice ID, adding the ID of the slice to which the ONU sending the multicast adding request belongs in the recorded viewer list, and adding a record comprising the physical slice ID, the multicast address and the VLAN in the multicast forwarding hardware table entry of the physical slice in the forwarding chip.
Correspondingly, if the query result is not null, only the ID of the slice to which the ONU sending the multicast join request belongs is newly added in the searched and recorded viewer list.
Further, in an embodiment, after the step of writing the multicast forwarding software entries and the multicast forwarding hardware entries of the plurality of physical slices corresponding to the plurality of content providing platforms respectively, the method further includes:
when a multicast leaving request sent by the ONU is received, searching a target record formed by a viewer list, a multicast address and a VLAN corresponding to the multicast leaving request and an ID of the physical slice in a multicast forwarding software table entry of each physical slice; detecting whether only the ID of the logical slice is included in the viewer list in the target record; if not, deleting the ID of the logic slice from the viewer list in the target record, and keeping a record formed by the ID of the physical slice, a multicast address corresponding to the multicast leaving request and a VLAN in a multicast forwarding hardware table entry of the corresponding physical slice; and if so, deleting the target record, and deleting a record formed by the ID of the physical slice, the multicast address corresponding to the multicast leaving request and the VLAN in the multicast forwarding hardware table entry of the corresponding physical slice.
In this embodiment, after the multicast join request of the ONU under the logical slice writes the multicast forwarding software entries and the multicast forwarding hardware entries of the multiple physical slices, if the multicast leave request of the ONU is received, it needs to determine whether to delete the multicast forwarding hardware entries of each physical slice written based on the multicast join request of the ONU according to an actual situation.
In order to avoid abnormal cutoff of the ONU which has requested the multicast data stream corresponding to the multicast leave request under the physical slice itself or other logical slices due to deletion of the multicast forwarding hardware entry, it is necessary to detect whether the physical slice itself or other logical slices sharing the multicast forwarding hardware entry with the physical slice have requested the multicast data stream corresponding to the multicast leave request. If the request is received, it indicates that other ONU users are watching the channel program corresponding to the multicast join request under the physical slice or other logic slices associated with the physical slice, at this time, only the multicast forwarding software table entry of the physical slice is modified, and a record formed by the ID of the physical slice, the multicast address corresponding to the multicast join request and the VLAN in the multicast forwarding hardware table entry of the physical slice is reserved; if a physical slice itself or other logical slices sharing the multicast forwarding hardware entry do not request the multicast data stream corresponding to the multicast leaving request, deleting the record of the multicast forwarding software entry of the physical slice, which is composed of the viewer list, the multicast address and VLAN corresponding to the multicast leaving request, and the ID of the physical slice, and deleting the record of the multicast forwarding hardware entry of the physical slice, which is composed of the ID of the physical slice, the multicast address and VLAN corresponding to the multicast leaving request.
With reference to fig. 7, the slice multicast protocol instance issues an operation multicast forwarding hardware entry instruction, where the instruction content includes a physical slice ID (which refers to an ID of a physical slice corresponding to the operation multicast forwarding hardware entry instruction), a multicast address and a VLAN corresponding to the multicast leave request, a slice multicast protocol instance ID (for example, when a multicast leave request sent by an ONU under slice X is currently received, the multicast protocol instance of slice X issues an operation multicast forwarding hardware entry instruction, the slice multicast protocol instance ID is an ID of a slice to which the ONU sending the multicast leave request belongs, and slice X may be a physical slice or a logical slice), and an instruction type. The multicast forwarding table arbitration module receives the instruction of operating the multicast forwarding hardware table entry and identifies the type of the instruction. If the instruction type is deleting the multicast forwarding hardware table entry (for the multicast leaving request, the instruction type is deleting), inquiring a target record which is composed of a viewer list, a multicast address and a VLAN which correspond to the multicast leaving request and the ID of the physical slice in the multicast forwarding software table entry which corresponds to the ID of the physical slice, if the viewer list in the target record only comprises the ID of the slice X, deleting the target record from the multicast forwarding software table entry of the physical slice, and deleting a record which is composed of the multicast address and the VLAN which correspond to the multicast leaving request and the ID of the physical slice from the multicast forwarding hardware table entry of the physical slice; if the viewer list in the target record contains the IDs of the slices other than the ID of the slice X, the ID of the slice X is deleted from the viewer list in the target record in the multicast forwarding software entry of the physical slice, and a record composed of the ID of the physical slice, the multicast address corresponding to the multicast leaving request, and the VLAN in the multicast forwarding hardware entry of the physical slice is reserved.
In the above embodiments, the present invention is described by taking the addition and the departure of an ONU in a logical slice as an example. The following describes the present invention by taking the addition and the removal of ONUs under physical slicing as an example.
In an embodiment, when a multicast join request sent by an ONU under a physical slice is received, it is detected whether a logical slice sharing a multicast forwarding hardware entry of the physical slice has requested the same multicast data stream. And if not, writing the multicast forwarding hardware table entry of the physical slice based on the multicast adding request.
In this embodiment, it is considered that the logical slice sharing the multicast forwarding hardware entry with the physical slice may have requested the same multicast data stream, and thus the multicast forwarding hardware entry of the multicast data stream corresponding to the multicast join request has been written. In order to avoid duplicating the multicast forwarding hardware entry, it is necessary to detect whether a multicast forwarding software entry of the multicast data stream corresponding to the multicast join request exists in the physical slice. If the multicast data stream exists, the multicast data stream requested by the multicast join request is already issued to the OLT, and the multicast forwarding hardware table entry of the multicast data stream corresponding to the multicast join request does not need to be written again; and if not, writing a multicast forwarding software table entry and a multicast forwarding hardware table entry of the multicast data stream corresponding to the multicast joining request. The multicast forwarding hardware table entry is stored in a switching chip of the OLT device, and the multicast forwarding hardware table entries of each physical slice are independent.
Further, in an embodiment, when a multicast leave request sent by an ONU under the physical slice is received, it is detected whether a logical slice sharing the multicast forwarding hardware entry of the physical slice has requested a multicast data stream corresponding to the multicast leave request. If so, not deleting the multicast forwarding hardware table entry; otherwise, deleting the multicast forwarding hardware table entry.
In this embodiment, it is considered that the logical slices sharing the multicast forwarding hardware entry of the physical slice may have requested the same multicast data stream, and thus have written the multicast forwarding hardware entry corresponding to the same multicast data stream. In order to avoid abnormal cutoff of the ONU that has requested the same multicast data stream under the logical slice due to deletion of the multicast forwarding hardware entry, it is necessary to detect whether the logical slice sharing the physical slice multicast forwarding hardware entry has requested the same multicast data stream. If the request is made, it indicates that the logic slice associated with the physical slice has the same channel program being watched by the ONU user, and does not delete the multicast forwarding hardware entry; otherwise, deleting the multicast forwarding hardware table entry.
Referring to fig. 8, fig. 8 is a diagram illustrating content changes of multicast forwarding software entries and multicast forwarding hardware entries in a viewing scenario according to an embodiment. As shown in fig. 8:
when no user requests the channel program, the multicast forwarding software table entry and the multicast forwarding hardware table entry are both empty;
when a physical slice VS1 user requests a channel program of 239.1.1.1/VLAN 100, a record of VS1/239.1.1.1/VLAN 100/VS _ ID LIST (VS 1) is newly added to a multicast forwarding software table entry of VS1, and a record of VS1/239.1.1.1/VLAN 100 is newly added to a multicast forwarding hardware table entry of VS 1;
when a physical slice VS1 user requests a channel program of 239.1.1.2/VLAN 100, a record of VS1/239.1.1.2/VLAN 100/VS _ ID LIST (VS 1) is newly added to a multicast forwarding software table entry of VS1, and a record of VS1/239.1.1.2/VLAN 100 is newly added to a multicast forwarding hardware table entry of VS 1;
when a logical slice VS3 user requests a channel program of 239.1.1.2/VLAN 100, a record of VS1/239.1.1.2/VLAN 100/VS _ ID LIST ═ VS3 is newly added to the multicast forwarding software table entry of VS1, and the multicast forwarding software table entry of VS1 VS1/239.1.1.2/VLAN 100/VS _ ID LIST ═ VS1 is updated as follows: VS1/239.1.1.2/VLAN 100/VS _ ID LIST VS1, VS 3; wherein logical slice VS3 shares the forwarding plane of physical slice VS 1;
when a physical slice VS1 user leaves a channel program of 239.1.1.1/VLAN 100, a multicast forwarding software table entry of VS1 deletes a record of VS1/239.1.1.1/VLAN 100/VS _ ID LIST which is VS1, and a multicast forwarding hardware table entry of VS1 deletes a record of VS1/239.1.1.1/VLAN 100;
when a logic slice VS3 user leaves a channel program of request 239.1.1.2/VLAN 100, deleting the record of VS1/239.1.1.2/VLAN 100/VS _ ID LIST (VS 3) in the multicast forwarding software table entry of VS1, and updating the multicast forwarding software table entry of VS1 to VS1/239.1.1.2/VLAN 100/VS _ ID LIST (VS 1);
when the physical slice VS1 user leaves the channel program of 239.1.1.2/VLAN 100, the multicast forwarding software entry at VS1 deletes the record of VS1/239.1.1.2/VLAN 100/VS _ ID LIST ═ VS1, and the multicast forwarding hardware entry at VS1 deletes the record of VS1/239.1.1.2/VLAN 100.
Further, in an embodiment, the method for accessing a channel across OLT slices further includes:
when a downlink multicast protocol message sent by a content providing platform is received, the downlink multicast protocol message is forwarded to a physical slice corresponding to the content providing platform, so that the physical slice forwards the downlink multicast protocol message to a logical slice corresponding to the content providing platform.
In this embodiment, the OLT needs to process multicast protocol packet interaction with the content providing platform, in addition to processing forwarding work of the multicast data stream. Referring to fig. 9, fig. 9 is a schematic diagram illustrating processing of a multicast protocol packet according to an embodiment. As shown in fig. 9, when receiving the downlink multicast protocol packets of the IPTV platform 1 and the IPTV platform 2, the master forwards the downlink multicast protocol packets to the multicast protocol instance of the corresponding slice for processing. The multicast protocol instance of the VS1 receives the downlink multicast protocol message, replies the uplink multicast protocol message to the IPTV platform 1, and copies the downlink multicast protocol message carrying VS3 slice information to the VS3 for processing as shown by a dotted line; the multicast protocol instance of the VS2 receives the downlink multicast protocol message, replies the uplink multicast protocol message to the IPTV platform 2, and copies the downlink multicast protocol message carrying VS3 slice information to the VS3 for processing as shown by the dotted line; the VS3 multicast protocol instance replies an uplink multicast protocol message to the IPTV platform 1 when receiving the downlink multicast protocol message of the IPTV platform 1, and replies an uplink multicast protocol message to the IPTV platform 2 when receiving the downlink multicast protocol message of the IPTV platform 2. The multicast protocol instances of the master VS1, VS2 and VS3 periodically send downlink multicast protocol messages carrying VS ID information to the line card. And when the line card receives the main control downlink multicast protocol message, forwarding the message to a corresponding slice multicast protocol example according to the VS ID for processing. The multicast protocol instance of VS1 receives the downlink multicast protocol message, carries VS1 slice information and forwards the uplink multicast protocol message to the master control; the multicast protocol instance of VS2 receives the downlink multicast protocol message, carries VS2 slice information and forwards the uplink multicast protocol message to the master control; the multicast protocol instance of VS3 receives the downlink multicast protocol message, carries VS3 slice information and forwards the uplink multicast protocol message to the master control.
Of course, as shown in fig. 9, the OLT also processes the multicast protocol message interaction with the ONUs. And when the line card receives the uplink multicast protocol message of the ONU, the line card forwards the uplink multicast protocol message to the multicast protocol instance of the corresponding slice according to the slice to which the ONU belongs to carry out processing. Taking the uplink multicast protocol message as a multicast join request as an example, the multicast protocol instance of the VS1 writes a multicast forwarding hardware table entry of the VS1, and carries VS1 slice information to forward the uplink multicast protocol message to the master control panel; a multicast protocol instance of the VS2 writes a multicast forwarding hardware table entry of the VS2, carries VS2 slice information and forwards an uplink multicast protocol message to a master control panel; the multicast protocol instance of the VS3 writes multicast forwarding hardware entries of the VS1 and the VS2 at the same time, and carries the VS3 slice information to forward the uplink multicast protocol packet to the master control disk. And when receiving the uplink multicast protocol message, the master control forwards the uplink multicast protocol message to the multicast protocol instances of different slices according to the VS ID for processing. A multicast protocol instance of VS1 writes a multicast forwarding hardware table entry of VS1 and forwards an uplink multicast protocol message to the IPTV platform 1; a multicast protocol instance of VS2 writes a multicast forwarding hardware table entry of VS2, and sends an uplink multicast protocol message to an IPTV platform 2; the multicast protocol instance of the VS3 writes multicast forwarding hardware entries of the VS1 and the VS2 at the same time, and forwards the uplink multicast protocol packet to the IPTV platform 1 and the IPTV platform 2 at the same time.
In a third aspect, an embodiment of the present invention further provides a cross-OLT sliced channel access apparatus.
Referring to fig. 10, fig. 10 is a functional block diagram of an embodiment of a cross-OLT sliced channel access device according to the present invention. As shown in fig. 10, in an embodiment, the channel access device sliced across the OLT includes:
a forwarding module 10, configured to forward, when receiving a multicast join request sent by an ONU corresponding to a logical slice, the multicast join request to a plurality of content providing platforms corresponding to the logical slice;
a writing module 20, configured to operate multicast forwarding entries of multiple physical slices corresponding to the multiple content providing platforms respectively based on the multicast join request;
and a data sending module 30, configured to send, when receiving a multicast data stream issued by the target content providing platform based on the multicast join request, the multicast data stream to the ONU based on the multicast forwarding table entry.
Further, in an embodiment, the channel access device across OLT slices includes a creation module configured to:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
Further, in an embodiment, the writing module 20 is configured to:
inquiring multicast forwarding software table entries of each physical slice based on the ID of each physical slice in a plurality of physical slices corresponding to the content providing platforms, the multicast address corresponding to the multicast adding request and the VLAN;
if the query result is empty, respectively writing multicast forwarding software table entries and multicast forwarding hardware table entries of each physical slice based on the multicast adding request;
and if the query result is not null, newly adding the ID of the logical slice in the viewer list of the queried record.
Further, in an embodiment, the writing module 20 is configured to:
if the query result is null, adding a new record in the multicast forwarding software table entry of each physical slice, wherein the record comprises a viewer list, a multicast address and a VLAN corresponding to the multicast join request and the ID of the physical slice, and the viewer list comprises the ID of the logical slice;
and newly adding a record comprising the ID of the physical slice, the multicast address corresponding to the multicast joining request and the VLAN in the multicast forwarding hardware table entry of each physical slice.
Further, in an embodiment, the channel access apparatus sliced across the OLT further includes a deletion module configured to:
when a multicast leaving request sent by the ONU is received, searching a target record formed by a viewer list, a multicast address and a VLAN corresponding to the multicast leaving request and an ID of the physical slice in a multicast forwarding software table entry of each physical slice;
detecting whether only the ID of the logical slice is included in the viewer list in the target record;
if not, deleting the ID of the logical slice from the viewer list in the target record;
and if so, deleting the target record, and deleting a record formed by the ID of the physical slice, the multicast address corresponding to the multicast leaving request and the VLAN in the multicast forwarding hardware table entry of the corresponding physical slice.
Further, in an embodiment, the channel access device across the OLT slice further includes a message processing module, configured to:
when a downlink multicast protocol message sent by a content providing platform is received, the downlink multicast protocol message is forwarded to a physical slice corresponding to the content providing platform, so that the physical slice forwards the downlink multicast protocol message to a logical slice corresponding to the content providing platform.
The function implementation of each module in the cross-OLT sliced channel access device corresponds to each step in the cross-OLT sliced channel access method embodiment, and the functions and implementation processes are not described in detail here.
In a fourth aspect, an embodiment of the present invention further provides a storage medium.
The storage medium of the present invention stores a cross-OLT sliced channel access program, wherein the cross-OLT sliced channel access program, when executed by a processor, implements the steps of the cross-OLT sliced channel access method as described above.
The method for implementing the cross-OLT slice channel access program when executed may refer to various embodiments of the cross-OLT slice channel access method of the present invention, and details are not described herein. The storage medium is a computer-readable storage medium.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or the portions contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) as described above and includes several instructions for causing a terminal device to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A cross-OLT slice channel access method is characterized in that the cross-OLT slice channel access method comprises the following steps:
when a multicast adding request sent by an ONU (optical network unit) corresponding to a logic slice is received, forwarding the multicast adding request to a plurality of content providing platforms corresponding to the logic slice;
respectively operating multicast forwarding table entries of a plurality of physical slices corresponding to the plurality of content providing platforms based on the multicast adding request;
and when receiving a multicast data stream issued by the target content providing platform based on the multicast adding request, sending the multicast data stream to the ONU based on the multicast forwarding table entry.
2. The method for accessing channels across OLT slices according to claim 1, wherein before the step of forwarding the multicast join request to the plurality of content providing platforms corresponding to the logical slice when receiving the multicast join request sent by the ONU corresponding to the logical slice, the method further comprises:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
3. The method according to claim 1, wherein the step of operating multicast forwarding entries of a plurality of physical slices corresponding to the plurality of content providing platforms respectively based on the multicast join request comprises:
querying multicast forwarding software table entries of each physical slice based on the ID of each physical slice in a plurality of physical slices corresponding to the plurality of content providing platforms, the multicast address corresponding to the multicast adding request and the VLAN;
if the query result is empty, respectively writing multicast forwarding software table entries and multicast forwarding hardware table entries of each physical slice based on the multicast adding request;
and if the query result is not null, newly adding the ID of the logical slice in a viewer list of the queried record, wherein the viewer list indicates which slices are requesting the multicast data stream.
4. The method according to claim 3, wherein if the query result is null, the step of writing the multicast forwarding software entry and the multicast forwarding hardware entry of each physical slice respectively based on the multicast join request comprises:
if the query result is null, adding a new record in the multicast forwarding software table entry of each physical slice, wherein the record comprises a viewer list, a multicast address and a VLAN corresponding to the multicast join request and the ID of the physical slice, and the viewer list comprises the ID of the logical slice;
and newly adding a record comprising the ID of the physical slice, the multicast address corresponding to the multicast joining request and the VLAN in the multicast forwarding hardware table entry of each physical slice.
5. The method according to claim 4, wherein after the step of writing the multicast forwarding software entry and the multicast forwarding hardware entry of each physical slice respectively, the method further comprises:
when a multicast leaving request sent by the ONU is received, searching a target record formed by a viewer list, a multicast address and a VLAN corresponding to the multicast leaving request and an ID of the physical slice in a multicast forwarding software table entry of each physical slice;
detecting whether only the ID of the logical slice is included in the viewer list in the target record;
if not, deleting the ID of the logical slice from the viewer list in the target record;
and if so, deleting the target record, and deleting a record formed by the ID of the physical slice, the multicast address corresponding to the multicast leaving request and the VLAN in the multicast forwarding hardware table entry of the corresponding physical slice.
6. The cross-OLT slice channel access method of any of claims 1-5, wherein the cross-OLT slice channel access method further comprises:
when a downlink multicast protocol message sent by a content providing platform is received, the downlink multicast protocol message is forwarded to a physical slice corresponding to the content providing platform, so that the physical slice forwards the downlink multicast protocol message to a logical slice corresponding to the content providing platform.
7. A cross-OLT sliced channel access device, comprising:
the forwarding module is used for forwarding a multicast join request to a plurality of content providing platforms corresponding to the logic slices when the multicast join request sent by the ONU corresponding to the logic slices is received;
a write module, configured to operate multicast forwarding entries of multiple physical slices corresponding to the multiple content providing platforms respectively based on the multicast join request;
and the data sending module is used for sending the multicast data stream to the ONU based on the multicast forwarding table item when receiving the multicast data stream issued by the target content providing platform based on the multicast joining request.
8. The cross-OLT-sliced channel access device of claim 7, wherein the cross-OLT-sliced channel access device comprises a creation module to:
when an ONU subscribes to a single content providing platform, creating a physical slice corresponding to the single content providing platform, and dividing the ONU into the physical slices;
when an ONU subscribes to a plurality of content providing platforms, creating logic slices corresponding to the plurality of content providing platforms, and dividing the ONU into the logic slices.
9. A cross-OLT sliced channel access device comprising a processor, a memory, and a cross-OLT sliced channel access program stored on the memory and executable by the processor, wherein the cross-OLT sliced channel access program when executed by the processor implements the steps of the cross-OLT sliced channel access method of any of claims 1-6.
10. A storage medium having stored thereon a cross-OLT-sliced channel access program, wherein the cross-OLT-sliced channel access program when executed by a processor implements the steps of the cross-OLT-sliced channel access method of any one of claims 1-6.
CN202110007539.XA 2021-01-05 2021-01-05 Channel access method, device, equipment and storage medium for cross-OLT slicing Active CN112770198B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110007539.XA CN112770198B (en) 2021-01-05 2021-01-05 Channel access method, device, equipment and storage medium for cross-OLT slicing
PCT/CN2022/070004 WO2022148330A1 (en) 2021-01-05 2022-01-01 Method, apparatus and device for accessing channels across olt slices, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110007539.XA CN112770198B (en) 2021-01-05 2021-01-05 Channel access method, device, equipment and storage medium for cross-OLT slicing

Publications (2)

Publication Number Publication Date
CN112770198A CN112770198A (en) 2021-05-07
CN112770198B true CN112770198B (en) 2022-05-20

Family

ID=75699256

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110007539.XA Active CN112770198B (en) 2021-01-05 2021-01-05 Channel access method, device, equipment and storage medium for cross-OLT slicing

Country Status (2)

Country Link
CN (1) CN112770198B (en)
WO (1) WO2022148330A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112770198B (en) * 2021-01-05 2022-05-20 烽火通信科技股份有限公司 Channel access method, device, equipment and storage medium for cross-OLT slicing

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102802094A (en) * 2012-09-12 2012-11-28 上海斐讯数据通信技术有限公司 Improvement method used for shortening multicasting traffic stream issued retardation in EPON (ethernet passive optical network) system
CN105591764A (en) * 2015-12-18 2016-05-18 杭州华三通信技术有限公司 Method and device for synchronizing multicast forwarding table items

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090238561A1 (en) * 2008-03-19 2009-09-24 Tellabs Vienna, Inc. Method and apparatus for measuring quality of traffic performance in a passive optical network (PON)
CN111107450A (en) * 2018-10-26 2020-05-05 中兴通讯股份有限公司 Method and device for realizing OLT slicing
CN109450544B (en) * 2018-12-27 2020-10-16 中国移动通信集团江苏有限公司 Optical line terminal OLT equipment and passive optical network PON data transmission method
CN112153493B (en) * 2019-06-27 2022-04-22 华为技术有限公司 Message processing method and device
CN112152899B (en) * 2019-06-28 2023-04-07 中兴通讯股份有限公司 Data processing method and device based on network slice
CN111865671B (en) * 2020-07-07 2022-10-11 烽火通信科技股份有限公司 Dynamic slice management method and device based on network auto-negotiation
CN112770198B (en) * 2021-01-05 2022-05-20 烽火通信科技股份有限公司 Channel access method, device, equipment and storage medium for cross-OLT slicing

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102802094A (en) * 2012-09-12 2012-11-28 上海斐讯数据通信技术有限公司 Improvement method used for shortening multicasting traffic stream issued retardation in EPON (ethernet passive optical network) system
CN105591764A (en) * 2015-12-18 2016-05-18 杭州华三通信技术有限公司 Method and device for synchronizing multicast forwarding table items

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
EPON系统中基于VLAN的组播设计;谭锋等;《广东通信技术》;20090215(第02期);全文 *

Also Published As

Publication number Publication date
WO2022148330A1 (en) 2022-07-14
CN112770198A (en) 2021-05-07

Similar Documents

Publication Publication Date Title
KR102498752B1 (en) Messaging platform for delivering real-time messages
EP1734688B1 (en) Method and apparatus for multicast management of user interface in a network access device
CN110647698B (en) Page loading method and device, electronic equipment and readable storage medium
US20090190587A1 (en) Method for deploying multicast network, multicast network and control server
US20070115975A1 (en) Method and system for controlling the multicast source
CN109067578B (en) Method and device for multicast fast switching
RU2530250C1 (en) Method and device for distribution of virtual local network
EP2457349B1 (en) Method and device for a light host management protocol on multicast capable router
CN109618174B (en) Live broadcast data transmission method, device, system and storage medium
CN101179565B (en) Method of implementing essential service of electric playbill
CN109862437B (en) Forwarding table item creating method and BRAS
WO2017000565A1 (en) User access control method and apparatus, relay device and server
CN112770198B (en) Channel access method, device, equipment and storage medium for cross-OLT slicing
CN111431966B (en) Service request processing method and device, electronic equipment and storage medium
CN111125426B (en) Method and device for storing and inquiring data
CN111107008A (en) Reverse path checking method and device
EP2457348B1 (en) Efficient host management protocol on multicast capable router
US10505811B2 (en) Multi-terminal interaction relation maintenance system and method
CN110737519A (en) theme switching method and device
CN109743585B (en) Method and device for collecting monitoring videos and cloning favorites
CN101924641B (en) Method, device and system for processing multicast source information
CN109787870B (en) Access management method, device, system, initial and target access equipment
CN115051970B (en) Method and device for controlling user to be online, forwarding plane network element and medium
WO2018108168A1 (en) Method for implementing multicast service of packet transmission network, device thereof and communication system
CN101771901B (en) Method of multicast permission control in passive optical network, system and multi-dwelling unit

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant