Operation and architecture of a central office point of delivery within a broadband access network of a telecommunications network

Patent metadata

Field	Value
Publication number	US-11456916-B2
Application number	US-202017422454-A
Country	US
Kind code	B2
Filing date	Jan 15, 2020
Priority date	Jan 15, 2019
Publication date	Sep 27, 2022
Grant date	Sep 27, 2022

Abstract

A central office point of delivery within a broadband access network of a telecommunications network includes: access network facing nodes; and a control function and/or a switching fabric and/or service edge nodes. Execution of network attachment tasks and/or further functional or configuration tasks within the central office point of delivery involves using an execution state database as well as stateless execution service functionalities being assigned to different execution stages realized within the central office point of delivery, and a message bus connecting the different execution stages, wherein the execution stages comprise at least an access stage, a processing stage, and a device stage, wherein the execution service functionalities—in order to process or execute the network attachment tasks and/or further functional or configuration tasks—generate a plurality of messages on the message bus and consume a plurality of messages from the message bus.

First claim

The invention claimed is:

1. A method for operation of a central office point of delivery within a broadband access network of a telecommunications network and/or for execution of network attachment tasks and/or further functional or configuration tasks within the central office point of delivery,
wherein the central office point of delivery and/or the broadband access network comprises
access network facing nodes, and
a control function and/or a switching fabric and/or service edge nodes,

wherein execution of the network attachment tasks and/or the further functional or configuration tasks within the central office point of delivery involves using an execution state database as well as stateless execution service functionalities being assigned to different execution stages realized within the central office point of delivery, and a message bus connecting the different execution stages,
wherein the execution stages comprise at least an access stage, a processing stage, and a device stage,
wherein the execution service functionalities—in order to process or execute the network attachment tasks and/or the further functional or configuration tasks—generate and consume messages on and from the message bus,
wherein the method comprises the following steps:
in a first step, receiving, by a first execution service functionality assigned to or part of the access stage, a trigger request regarding a network attachment task and/or a further functional or configuration task, and in response to receiving the trigger request, generating, by the first execution service functionality, at least a first message on the message bus;
in a second step, consuming, by a second execution service functionality assigned to or part of the processing stage, the first message on the message bus, and in response to consuming the first message, generating, by the second execution service functionality, at least a second message on the message bus; and
in a third step, consuming, by a third execution service functionality assigned to or part of the device stage, the second message on the message bus, and in response to consuming the second message, configuring, by the third execution service functionality, the control function and/or the switching fabric and/or the access network facing nodes and/or the service edge nodes.

2. The method according to claim 1 , wherein the processing stage comprises a customer stage, a service stage, and a setup and configuration stage, the customer stage comprising a fourth execution service functionality, the service stage comprising a fifth execution service functionality, and the setup and configuration stage comprising a sixth execution service functionality, and wherein the method further comprises:
in a fourth step, consuming, by the fourth execution service functionality, the first message on the message bus, and generating, by the fourth execution service functionality, at least a fourth message on the message bus;
in a fifth step, consuming, by the fifth execution service functionality, the fourth message on the message bus, and generating, by the fifth execution service functionality, at least a fifth message on the message bus; and
in a sixth step, consuming, by the sixth execution service functionality, the fifth message on the message bus, and generating, by the sixth execution service functionality, at least the second message on the message bus to be consumed, in the third step, by the third execution service functionality.

3. The method according to claim 2 , wherein upon the reception—by the first execution service functionality—of the trigger request regarding the network attachment task and/or regarding the further functional or configuration task, and upon the generation of at least the first message, the implemented sequence of stages are run through even in case that a stage is not actively involved in processing respective messages related to a specific type of trigger request.

4. The method according to claim 2 , wherein the first message comprises all necessary pieces of information for the processing stage or for the customer stage; and/or
wherein the second message comprises all necessary pieces of information for the device stage; and/or
wherein the fourth message comprises all necessary pieces of information for the service stage; and/or
wherein the fifth message comprises all necessary pieces of information for the setup and configuration stage.

5. The method according to claim 2 , wherein a respective trigger request regarding a network attachment task corresponds to a port-up message, especially regarding an access network facing node, which is received by the first execution service functionality, wherein the first execution service functionality generates generic data from the port-up message;
wherein the fourth execution service functionality determines a user or customer, and wherein generating at least the fourth message comprises generating at least the fourth message comprising all available customer data of a customer database;
wherein the sixth execution service functionality generating at least the second message comprises the sixth execution service functionality generating at least the second message comprising service edge information; and
wherein the second message being consumed by the third execution service functionality corresponds to configuring the access network facing nodes.

6. The method according to claim 2 , wherein a respective trigger request regarding a Radius request or regarding accounting data or regarding a change-of-authorization event is received by the first execution service functionality, corresponding to a service edge, wherein the first execution service functionality generates generic data regarding the respective trigger request;
wherein the fourth execution service functionality determines a user or customer, and wherein generating at least the fourth message comprises generating at least the fourth message comprising all available customer data of a customer database;
wherein the sixth execution service functionality generating at least the second message comprises the sixth execution service functionality generating at least the second message comprising a request to send a Radius response corresponding to the Radius request; and
wherein the second message being consumed by the third execution service functionality corresponds to sending a Radius response corresponding to the respective trigger request.

7. The method according to claim 1 , wherein the network attachment task prepares and configures the central office point of delivery and the access network facing nodes to enable IP session setup; and
wherein the further functional or configuration task is to:
process an external control plane request, especially a Radius request in view of or during an IP session setup, or a change of authorization request especially regarding an access network facing node of the broadband access network; and/or
send accounting data related to a user of the broadband access network or to a plurality of users.

8. The method according to claim 1 , wherein the switching fabric comprises a plurality of spine network nodes and a plurality of leaf network nodes, wherein at least part of the leaf network nodes realize one or a plurality of functionalities of one or a plurality of the service edge nodes.

9. The method according to claim 1 , wherein the messages are transmitted or generated, on the message bus, as part of an array of messages or as part of a transaction of messages.

10. A system for operation of a central office point of delivery within a broadband access network of a telecommunications network and/or for execution of network

Assignees

• Deutsche Telekom Ag

Inventors

• Haag Thomas
• Kolbe Hans-Joerg
• Hurst Wolfgang

Classifications

• H04L12/2892

  characterised by the access multiplexer architecture · CPC title

• H04L41/5041 Primary

  characterised by the time relationship between creation and deployment of a service · CPC title

• H04L12/4625

  Single bridge functionality, e.g. connection of two networks over a single bridge · CPC title

• H04L12/44

  Star or tree networks · CPC title

• H04L41/20

  Network management software packages · CPC title