Using events to identify a user and enforce policies
US-9215235-B1 · Dec 15, 2015 · US
US9363227B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9363227-B2 |
| Application number | US-201213588129-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 17, 2012 |
| Priority date | Aug 17, 2012 |
| Publication date | Jun 7, 2016 |
| Grant date | Jun 7, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure provides a source specific multicast service that maps multicast group addresses to corresponding source addresses. A boundary routing element can be configured to determine whether a received join request includes a mapped group address. If the join request does not include a mapped group address, boundary routing element can be configured to perform normal join request processing of the join request. If the join request includes a mapped group address, the boundary routing element can be configured to generate a corresponding source address using the mapped group address. The boundary routing element can also be configured to perform alternative join request processing as if the join request were an SSM join request that specified both a source address and a multicast group address.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving a join request from a receiving device, wherein the join request comprises a group address partitioned into one or more octets; determining whether the group address requires source address generation by comparing at least a portion of the group address with one or more entries in a prefix list; in response to the at least a portion of the group address matching an entry in the prefix list, generating a source address, wherein the group address is used to generate the source address by combining one or more pre-configured octet values with the one or more octets of the group address according to an octet assignment, and the octet assignment assigns the one or more pre-configured octet values to a first portion of the source address, and the octet assignment assigns the one or more octets of the group address to a second portion of the source address; and upon producing the source address generating an outgoing loin message, wherein the outgoing join message comprises the source address and the group address, and performing source specific multicast processing using the source address and the group address, wherein a source corresponding to the source address is configured to provide a datastream to the group address on a channel, the source address and the group address together uniquely identify the channel, and the performing the specific source multicast processing comprises transmitting the outgoing loin message to a network element. 2. The method of claim 1 , further comprising: selecting the one or more pre-configured octet values from a selector table, wherein at least one octet of the group address is used to select the one or more pre-configured octet values. 3. The method of claim 1 , wherein the group address is a source specific multicast group address. 4. The method of claim 1 , wherein the receiving device does not support source specific multicast. 5. The method of claim 1 , wherein the join request does not comprise information identifying a source. 6. The method of claim 1 , further comprising: in response to a determination that the group address does not require source address generation, generating an outgoing join request without generating the source address. 7. A boundary routing element comprising: a memory device configured to store program instructions; a processor coupled to the memory device configured to execute the program instructions; a port, wherein the port receives a join request from a receiving device, and the join request comprises a group address partitioned into one or more octets; a routing module, executable by the processor, wherein the routing module determines whether the group address requires source address generation by comparing at least a portion of the group address with one or more entries in a prefix list; and a source address generator, executable by the processor, and configured to, in response to the at least a portion of the group address matching an entry in the prefix list, generate a source address, wherein the group address is used to generate the source address by combining one or more pre-configured octet values with the one or more octets of the group address according to an octet assignment, the octet assignment assigns the one or more pre-configured octet values to a first portion of the source address, and the octet assignment assigns the one or more octets of the group address to a second portion of the source address, and generating the source address enables the routing module to: generate an outgoing join message, wherein the outgoing join message comprises the source address and the group address, and perform source specific multicast processing using the source address and the group address wherein a source corresponding to the source address is configured to provide a datastream to the group address on a channel, the source address and the group address together uniquely identify the channel, and performing the specific source multicast processing comprises transmitting the outgoing join message to a network element. 8. The boundary routing element of claim 7 , wherein the source address generator selects the one or more pre-configured octet values from a selector table, wherein at least one octet of the group address is used to select the one or more pre-configured octet values. 9. The boundary routing element of claim 7 , wherein the loin request received by the port does not comprise information identifying a source. 10. The boundary routing element of claim 7 , wherein in response to a determination by the routing module that the group address does not require source address generation, generating an outgoing loin request without generating the source address. 11. The boundary routing element of claim 7 , wherein the group address is a source specific multicast address. 12. The boundary routing element of claim 7 , wherein the receiving device does not support source specific multicast. 13. A non-transitory computer readable storage medium configured to store program instructions that, when executed on a processor, are configured to cause the processor to perform a method comprising: receiving a join request from a receiving device, wherein the join request comprises a group address partitioned into one or more octets; determining whether the group address requires source address generation by comparing at least a portion of the group address with one or more entries in a prefix list; and in response to the group address matching an entry in the prefix list, generating a source address, wherein the group address is used to generate the source address by combining one or more pre-configured octet values with the one or more octets of the group address according to an octet assignment, and the octet assignment assigns the one or more pre-configured octet values to a first portion of the source address, and the octet assignment assigns the one or more octets of the group address to a second portion of the source address; and upon producing the source address generating an outgoing join message, wherein the outgoing join message comprises the source address and the group address, and performing source specific multicast processing using the source address and the group address wherein a source corresponding to the source address is configured to provide a datastream to the group address on a channel, the source address and the group address together uniquely identify the channel, and the performing the specific source multicast processing comprises transmitting the outgoing join message to a network element. 14. The non-transitory computer readable storage medium of claim 13 , wherein the method further comprises: selecting the one or more pre-configured octet values from a selector table, wherein at least one octet of the group address is used to select the one or more pre-configured octet values. 15. The non-transitory computer readable storage medium of claim 13 , wherein the method further comprises wherein the loin request does not comprise information identifying a source. 16. The non-transitory computer readable storage medium of claim 13 , wherein the method further comprises in response to a determination that the group address does not require source address generation, generating an outgoing loin request without generating the source address. 17. The non-transitory computer readable storage medium of claim 13 , wherein the method further comprises wherein the
for broadcast or conference {, e.g. multicast} · CPC title
with management of multicast group membership · CPC title
with non-centralised forwarding system, e.g. chaincast · CPC title
Electricity · mapped topic
Multipoint routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.