US11082307B2 - E-Line service control - Google Patents
E-Line service control Download PDFInfo
- Publication number
- US11082307B2 US11082307B2 US16/391,688 US201916391688A US11082307B2 US 11082307 B2 US11082307 B2 US 11082307B2 US 201916391688 A US201916391688 A US 201916391688A US 11082307 B2 US11082307 B2 US 11082307B2
- Authority
- US
- United States
- Prior art keywords
- change
- network
- service
- service provider
- cir
- 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, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
- H04L47/748—Negotiation of resources, e.g. modification of a request
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5077—Network service management, e.g. ensuring proper service fulfilment according to agreements wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/25—Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
- H04L47/785—Distributed allocation of resources, e.g. bandwidth brokers among multiple network domains, e.g. multilateral agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
Definitions
- Ethernet services providers often provide services to customers within a particular region.
- Ethernet services may be desired across regions associated with different service providers.
- a company may have office locations in different areas (e.g., different cities, states or countries) that are serviced by two different service providers.
- the Metro Ethernet Forum MEF has defined wholesale Ethernet Access Ethernet Line (E-Line) services for service providers that provide connectivity to subscriber locations.
- E-Line Ethernet Access Ethernet Line
- MEF has defined E-Line services providing point-to-point Ethernet Virtual Connections (EVCs) between subscriber locations where an Access E-Line service can be a segment of an end-to-end E-Line service.
- EECs Ethernet Virtual Connections
- E-Line Access Ethernet Line
- OVCs point-to-point operator virtual connections
- FIG. 1 illustrates an exemplary environment in which systems and methods described herein may be implemented
- FIG. 2 illustrates an exemplary connection implemented in a portion of the environment of FIG. 1 ;
- FIG. 3 illustrates an exemplary configuration of logic components associated with implementing a change to an Ethernet service provided in the environment of FIG. 1 ;
- FIG. 4 illustrates an exemplary configuration of logic components associated with one or more of the devices of FIG. 1 and/or FIG. 3 ;
- FIGS. 5 and 6 are flow diagrams illustrating processing by various components in the environment of FIGS. 1 and 3 in accordance with an exemplary implementation
- FIGS. 7A and 7B are signal flow diagrams associated with the processing of FIGS. 5 and 6 ;
- FIG. 8 is a signal flow diagram associated with updating service level objectives associated with an E-Line modification.
- Implementations described herein relate to providing for modification of E-Line services in an “on-demand” manner. For example, implementations described herein allow a customer to request a change to an E-Line parameter without having to submit a new order and without the service provider having to re-provision a new E-Line.
- the service providers associated with the E-Line may determine whether adequate resources are available and may implement the change when adequate resources exist. Implementations described herein also provide for efficient signaling/message exchange between one service provider servicing the party requesting the change and a partner service provider servicing, for example, the destination location for the E-Line.
- the signaling and message exchange advantageously provide each service provider with necessary information regarding the requested change and ensure that the requested change can be implemented prior to accepting the change request.
- the service providers may automatically implement the change in service. In this manner, the user may be able to make changes in an on-demand manner and be informed of results of the E-Line service change request without having to submit a new service order and wait a long time before the change is implemented.
- FIG. 1 is a block diagram of an exemplary environment 100 in which systems and methods described herein may be implemented.
- Environment 100 may include user devices 110 - 1 and 110 - 2 , user network interface (UNI) 120 - 1 , UNI 120 - 2 , service provider network 130 (also referred to herein as network 130 ), partner network 140 and external network-to-network interface (ENNI) 150 .
- UNI user network interface
- ENNI external network-to-network interface
- User devices 110 - 1 and 110 - 2 may include any computing device, such as a personal computer (PC), a server, a tablet computer, a notebook, a netbook, a mobile device, such as wireless or cellular telephone device (e.g., a conventional cell phone with data processing capabilities), a smart phone, a personal digital assistant (PDA) that can include a radiotelephone, any type of mobile computer device or system, a game playing device, a music playing device, a home appliance device, a home monitoring device, a virtualized system, etc., that includes communication functionality.
- PC personal computer
- PDA personal digital assistant
- User device 110 - 1 may connect to network 130 via UNI 120 - 1 and user device 110 - 2 may connect to partner network 140 via UNI 120 - 2 .
- User devices 110 may also connect to other devices in environment 100 via any conventional technique, such as wired, wireless, optical connections or a combination of these techniques.
- User device 110 and the person associated with user device 110 e.g., the party holding or using user device 110
- UNI 120 - 1 and 120 - 2 may include a network interface to which a subscriber connects to transmit and receive information.
- UNI 120 may include one or more computing devices or systems used to facilitate the transmission of information to/from a subscriber.
- UNI 120 may act as an interface from a subscriber (e.g., a computer, such as a subscriber at user device 110 ) to allow the subscriber to Ethernet services, such as E-Line services from a service provider associated with network 130 and 140 .
- Service provider network 130 may include one or more wired, wireless and/or optical networks that are capable of receiving and transmitting data, voice and/or video signals.
- service provider network 130 may include one or more Ethernet networks, packet switched networks such as Internet Protocol/Multi-Protocol Label Switching (IP/MPLS) networks, Software Defined Networks (SDNs) or other type of packet network.
- IP/MPLS Internet Protocol/Multi-Protocol Label Switching
- SDNs Software Defined Networks
- Service provider network 130 may also include one or more wireless networks and may include a number of transmission towers for receiving wireless signals and forwarding the wireless signals toward the intended destination.
- Service provider network 130 may further include one or more satellite networks, one or more packet switched networks, such as an Internet protocol (IP) based network, a local area network (LAN), a personal area network (PAN), a WiFi network, a Bluetooth network, a wide area network (WAN), a long term evolution (LTE) network, a fourth generation (4G) network, a 4G LTE Advanced network, a fifth generation (5G) network, an intranet, the Internet, or another type of network that is capable of transmitting data.
- Service provider network 130 may provide packet-switched services and wireless Internet protocol (IP) connectivity to user devices 110 to provide, for example, data, voice, and/or multimedia services.
- IP Internet protocol
- service provider network 130 may provide E-Line services to user device 110 - 1 communicating with user device 110 - 2 via partner network 140 .
- Partner network 140 may include similar elements as network 130 . However, partner network 140 may be associated with a different service provider than network 130 .
- partner network may include one or more wired, wireless and/or optical networks that are capable of receiving and transmitting data, voice and/or video signals, such as one or more Ethernet networks, packet switched networks such as IP/MPLS networks, SDNs or other type of packet switched network that is operated by a different service provider/entity than network 130 .
- Partner network 140 may also include one or more wireless networks which may include a number of transmission towers for receiving wireless signals and forwarding the wireless signals toward the intended destination, one or more satellite networks, one or more packet switched networks, such as an IP based network, a LAN, a PAN, a WiFi network, a Bluetooth network, a WAN, an LTE network, a 4G network, a 4G LTE Advanced network, a 5G network, an intranet, the Internet, or another type of network that is capable of transmitting data.
- Partner network 140 may also provide wireless packet-switched services and wireless IP connectivity to user devices 110 to provide, for example, data, voice, and/or multimedia services.
- partner network 140 may provide E-Line services to user device 110 - 1 communicating with user device 110 - 2 via network 130 and partner network 140 .
- ENNI 150 represents the interface or boundary between network 130 and partner network 140 .
- ENNI 150 may include one or more computing devices that provide interoperability for data transmitted between network 130 and partner network 140 , such as formatting frames transmitted to and received by ENNI 150 , enforcing bandwidth profiles, performing switching, etc.
- FIG. 1 The exemplary configuration illustrated in FIG. 1 is provided for simplicity. It should be understood that a typical environment may include more or fewer devices than illustrated in FIG. 1 .
- environment 100 may include a large number (e.g., thousands or more) of user devices 110 , hundreds of UNIs 120 , additional networks and corresponding ENNIs 150 , internal network-to-network interfaces (INNIs), etc.
- network 130 and partner network 140 may include additional elements, such as eNodeBs, base stations, switches, gateways, routers, monitoring devices, etc., that aid in routing data.
- various functions are described below as being performed by particular components in environment 100 .
- various functions described as being performed by one device may be performed by another device or multiple other devices, and/or various functions described as being performed by multiple devices may be combined and performed by a single device.
- a party at user device 110 - 1 may wish to communicate with the party at user device 110 - 2 .
- a connection may traverse the networks of two different service providers, such as a service provider associated with network 130 and a different service provider associated with partner network 140 .
- a service provider also referred to herein as an operator
- a service provider associated with network 130 may provide an operator virtual connection (OVC) from UNI 120 - 1 to ENNI 150 and the service provider/operator associated with partner network 140 may also form an OVC from UNI 120 - 2 to ENNI 150 .
- OVC operator virtual connection
- FIG. 2 illustrates an OVC from UNI 120 - 1 (referred to herein as an on-net location) to ENNI 150 , labeled OVC-A, and an OVC from UNI 120 - 2 (referred to herein as an off-net location) to ENNI 150 , labeled OVC-B.
- OVC-A an OVC from UNI 120 - 1
- OVC- 2 an OVC from UNI 120 - 2
- OVC-B OVC from UNI 120 - 2
- Different operators associated with network 130 and partner network 140 may set up the OVCs in their respective networks and the connection from UNI 120 - 1 to UNI 120 - 2 may correspond to an E-Line service that traverses or engages both operators' networks.
- a customer associated with user device 110 - 1 may wish to change one or more attributes, such as a committed information rate (CIR), an excess information rate (EIR), committed burst size (CBS), excess burst size (EBS), etc., associated with an E-Line service.
- CIR committed information rate
- EIR excess information rate
- CBS committed burst size
- EBS excess burst size
- FIG. 3 illustrates a network infrastructure 300 associated with and/or implemented in environment 100 in accordance with an exemplary implementation.
- a portion of environment 300 may be associated with the operator of network 130 and a portion of infrastructure 300 may be associated with the operator of partner network 140 .
- customer domain 305 and service provider domain 315 may be associated with the operator of network 130 and partner domain 355 may be associated with the operator of partner network 140 .
- customer domain 305 includes customer application coordinator 310 .
- Customer application coordinator 315 may represent a portal or website associated with the operator of network 130 .
- Customer application coordinator 310 may be configured to receive a request from a customer, such as a request to change a parameter associated with a service provided by the operator of network 130 (e.g., an E-Line service) and process the request in an on-demand manner without requiring processing of a new order and provisioning a new OVC, as described in detail below.
- a service e.g., an E-Line service
- Service provider (SP) domain 315 may include business applications 320 , Service Orchestrator 330 , infrastructure control and management (ICM) 340 , and element control and management (ECM) 350 .
- Business applications 320 may include an operations support system (OSS)/billing support system (BSS) (also referred to herein as OSS/BSS 320 ) that includes logic and/or software associated with billing a customer for services provided by the operator of network 130 . For example, if a customer changes a rate associated with an E-Line service, OSS/BSS 320 may receive information associated with the new rate and bill the customer the appropriate amount.
- OSS operations support system
- BSS billing support system
- Service Orchestrator 330 may include one or more processing devices, logic and/or software to handle service requests and initiate processing for handling change requests in an on-demand manner. For example, Service Orchestrator 330 may interface with resources in network 130 to determine whether adequate resources are available to service the requested change. Service Orchestrator 330 may also interface with ICM 340 and ECM 350 , as described in detail below.
- ICM 340 may include one or more processing devices, logic and/or software to determine whether portions of network 130 include adequate resources to handle a requested service change. For example, ICM 340 may determine whether network interfaces, such as UNIs, NNIs, ENNIs, are adequately configured to handle a requested service change.
- network interfaces such as UNIs, NNIs, ENNIs
- ECM 350 may include one or more processing devices, logic and/or software to determine whether other portions of network 130 include adequate resources to handle a requested service change. For example, ECM 350 may determine whether the endpoints are adequately configured to handle a requested service change.
- Partner domain 355 may be associated with the service provider operating partner network 140 .
- Partner domain 355 may include business applications 320 -P (e.g., OSS/BSS 320 -P), service orchestrator 330 -P, ICM 340 -P and ECM 350 -P.
- Business applications 320 -P, Service Orchestrator 330 -P, ICM 340 -P and ECM 350 -P may be similar to elements 320 , 330 , 340 and 350 described above with respect to service provider domain 315 , with the difference being that elements 320 -P, 330 -P, 340 -P and 350 -P perform the same or similar processing with respect to partner network 140 , as described in detail below.
- FIG. 3 shows exemplary components of network infrastructure 300
- network infrastructure 300 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 3 .
- functions described as being performed by one of the components in FIG. 3 may alternatively be performed by another one or more of the components of network infrastructure 300 .
- FIG. 4 illustrates a device 400 which includes an exemplary configuration of elements used to implement one or more devices of environment 100 and/or implement one or more components illustrated in network infrastructure 300 .
- device 400 may include elements used to implement elements in service provider domain 315 and/or elements within service partner domain 355 , such as business applications 320 , Service Orchestrator 330 / 330 -P, ICM 340 / 340 -P and/or ECM 350 / 350 -P.
- Device 400 may also include elements used to implement devices in environment 100 , such as user device 110 , UNI 120 and/or ENNI 150 .
- device 400 may include bus 410 , processor 420 , memory 430 , input device 440 , output device 450 and communication interface 460 .
- Bus 410 may include a path that permits communication among the elements of device 400 .
- Processor 420 may include one or more processors, microprocessors, or processing logic that may interpret and execute instructions.
- Memory 430 may include a random access memory (RAM) or another type of dynamic storage device that may store information and instructions for execution by processor 420 .
- Memory 430 may also include a read only memory (ROM) device or another type of static storage device that may store static information and instructions for use by processor 420 .
- Memory 430 may further include a solid state drive (SDD).
- SDD solid state drive
- Memory 430 may also include a magnetic and/or optical recording medium (e.g., a hard disk) and its corresponding drive.
- Input device 440 may include a mechanism that permits a user to input information to device 400 , such as a keyboard, a keypad, a mouse, a pen, a microphone, a touch screen, voice recognition and/or biometric mechanisms, etc.
- Output device 450 may include a mechanism that outputs information to the user, including a display (e.g., a liquid crystal display (LCD)), a printer, a speaker, etc.
- a touch screen display may act as both an input device and an output device.
- Communication interface 460 may include one or more transceivers that device 400 uses to communicate with other devices via wired, wireless or optical mechanisms.
- communication interface 460 may include one or more radio frequency (RF) transmitters, receivers and/or transceivers and one or more antennas for transmitting and receiving RF data via network 130 and/or partner network 140 .
- Communication interface 460 may also include a modem or an Ethernet interface to a LAN, or other mechanisms for communicating with elements in a network, such as network 130 or partner network 140 .
- device 400 may include more or fewer devices (e.g., a global positioning system (GPS) chipset) than illustrated in FIG. 4 .
- device 400 may perform operations in response to processor 420 executing sequences of instructions contained in a computer-readable medium, such as memory 430 .
- a computer-readable medium may be defined as a physical or logical memory device.
- the software instructions may be read into memory 430 from another computer-readable medium (e.g., a hard disk drive (HDD), SSD, etc.), or from another device via communication interface 460 .
- HDD hard disk drive
- SSD etc.
- hard-wired circuitry may be used in place of or in combination with software instructions to implement processes consistent with the implementations described herein.
- implementations described herein are not limited to any specific combination of hardware circuitry and software.
- FIGS. 5 and 6 are flow diagrams illustrating exemplary processing associated with on-demand modifications and testing for an Ethernet service.
- FIGS. 7A and 7B are signal flow diagrams associated with the processing shown in FIGS. 5 and 6 .
- customer 110 may modify a parameter of an E-Line service, such as the committed information rate (CIR) parameter without having to negotiate with the service provider.
- customer 110 may modify the CIR up to the UNI physical (PHY) layer rate minus the bandwidth for Ethernet frame overhead for an E-Line service without having to negotiate the new CIR with the service provider.
- customer 110 may modify the CIR up to, for example, the UNI PHY layer rate minus the bandwidth for Ethernet frame overhead for an E-Line service via a negotiation process with the service provider associated with network 130 .
- customer 110 requests a modification of the CIR and that the modification is processed via a negotiation with the service provider associated with network 130 .
- Processing may begin with a user at user device 110 - 1 (also referred to herein as a customer, customer 110 , subscriber or subscriber 110 ) transmitting a request for modifying, for example, a CIR parameter for an Ethernet virtual connection (EVC).
- EVC Ethernet virtual connection
- the EVC may be provided by the operator associated with network 130 , which implements a segment of the EVC, such as OVC-A illustrated in FIG. 2 .
- customer 110 may transmit a request for a CIR change to a portal or website associated with the service provider (SP) operating network 130 .
- the SP portal may route the request to SP Service Orchestrator 330 ( FIG. 7A, 710 ).
- SP Service Orchestrator 330 receives the request ( FIG. 5 , block 510 ).
- SP Service Orchestrator 330 may validate the customer, based on, for example, a user/customer identifier, password, etc. SP Service Orchestrator 330 may also validate the location associated with the customer (e.g., ensure that the customer is at a location serviced by the operator of service provider network 130 ) and that the E-Line service is between location A and location B. SP Service Orchestrator 330 may also validate that the customer is currently subscribing to the E-Line service associated with the CIR change request (block 520 ; FIG. 7, 712 ). In some implementations, SP Service Orchestrator 330 may access OSS/BSS 320 associated with the operator of service provider network 130 to validate the customer.
- OSS/BSS 320 associated with the operator of service provider network 130 to validate the customer.
- SP Service Orchestrator 330 may also determine if the requested CIR change is within limits or bounds provided by the operator associated with network 130 (block 530 ). For example, SP Service Orchestrator 330 may access a CIR list or table that provides information regarding available CIRs for the service provider. In some implementations, SP Service Orchestrator 330 may access OSS/BSS 320 to determine if the CIR change is within limits or bounds set by the operator of network 130 . In some implementations, SP Service Orchestrator 330 may also determine if network 130 includes adequate resources to provide the modified CIR at the current time based on network load, expected load, resources in service/out of service, etc.
- SP Service Orchestrator 330 may further determine if partner network 140 includes adequate resources to provide the modified CIR, if such information is available to the operator of network 130 . In the description below, assume that the SP associated with network 130 does not have access to information regarding resources in partner network 140 .
- SP Service Orchestrator 330 forwards the CIR change request to partner network 140 (block 540 ). For example, SP Service Orchestrator 330 may forward the CIR change request to partner Service Orchestrator 330 -P ( FIG. 7A, 715 ). SP Service Orchestrator 330 may also transmit a request in progress message to the customer 110 ( FIG. 7A, 720 ).
- SP Service Orchestrator 330 may determine that the rate is not allowed/available (block 550 ). SP Service Orchestrator 330 may also transmit a signal to customer 110 indicating the request is invalid or resources are unavailable at the present time.
- partner Service Orchestrator 330 -P receives the CIR change request, validates the CIR request and determines whether adequate resources are available to service the requested CIR in partner network 140 (block 560 ; FIG. 7A, 722 ). If the validation is successful and the resources are available at partner network 140 , partner service orchestrator 330 -P may send a request in progress message to SP Service Orchestrator 330 , which relays the request in progress message to customer 110 ( FIG. 7A, 725 ).
- SP Service Orchestrator 330 and Service Orchestrator 330 -P may each initiate the validation regarding availability of network resources at the interfaces and endpoints in network 130 and partner network 140 , respectively ( FIG. 5, 570 ).
- Service Orchestrator 330 may send a message to SP ICM 340 to validate the service and resource availability in network 130 at the network interfaces ( FIG. 7A, 730 ). As part of the validation, SP ICM 340 may determine if the EVC associated with the CIR change is associated with ENNI 150 , UNI 120 - 1 and INNIs within service provider network 130 . SP ICM 340 may also determine whether there is enough capacity at these interfaces to support the requested CIR ( FIG. 7A, 732 ). Concurrently or substantially concurrently with SP ICM 340 validating the service and resource availability at the interfaces in service provider network 130 , Service Orchestrator 330 -P may send a similar CIR change message to ICM 340 -P ( FIG.
- ICM 340 -P may validate service and resource availability at the network interfaces (ENNI, UNI, INNIs) in partner network 140 ( FIG. 7A, 742 ). That is, ICM 340 -P may determine if the EVC associated with the CIR change is associated with ENNI 150 , UNI 120 - 2 and INNIs associated with partner network 140 and whether these network interfaces have enough capacity to support the requested CIR.
- SP ICM 340 and partner ICM 340 -P may forward a request in progress message, an invalid request or a resources unavailable message based on the validations ( FIG. 7A, 740 ). For example, assume that the request is valid and resources are available at the network interfaces in partner network 140 . In this case, Service Orchestrator 330 -P sends a request in progress message to service orchestrator 330 . Assume that resources are also available in service provider network 130 . Service Orchestrator 330 forwards the request in progress message to customer 110 . If the resources are unavailable at either service provider network 130 or partner network 140 , SP ICM 340 and/or ICM 340 -P may send a resources unavailable message, which is forwarded to customer 110 ( FIG. 7A, 740 ).
- SP ICM 340 may forward the CIR change to SP ECM 350 to modify the CIR to the customer requested value at the EVC end point of the on-net UNI (i.e., UNI 120 - 1 ) ( FIG. 7A, 745 ).
- SP ECM 350 receives the CIR change request and validates the service and resource availability at the on-net UNI ( FIG. 7A, 752 ).
- ICM 340 -P forwards the CIR change to partner ECM 350 -P to modify the CIR to the customer requested value at the EVC end point of the off-net UNI (i.e., UNI 120 - 2 ) ( FIG. 7A, 750 ).
- ECM 350 -P validates the service and resource availability at the off-net UNI 120 - 2 ( FIG. 7A, 762 ).
- Partner ECM 350 -P may then send a message confirming or denying the CIR change at the endpoints to partner ICM 340 -P ( FIG. 7B, 760 ).
- Partner ICM 340 -P may also forward a message confirming or denying the CIR change at the network interfaces to partner service orchestrator 330 -P ( FIG. 7B, 765 ).
- service orchestrator 330 -P, ICM 340 -P, Service Orchestrator 330 -P may each send separate messages to service provider network 130 upon completion of the validations.
- SP ECM 350 and SP ICM 340 may send messages confirming or denying the CIR change at the endpoints and network interfaces to SP Service Orchestrator 330 ( FIG. 7B, 770, 775 ).
- Service Orchestrator 330 -P may send a message confirming or denying the CIR change request to SP Service Orchestrator 330 ( FIG. 7B, 780 ).
- Service Orchestrator 330 may also determine if adequate resources are available at the endpoints and interfaces in network 130 based on received messages 770 and 775 and signal customer 110 with the status of the CIR request ( FIG. 7B, 782 ). For example, if adequate resources are available in both service provider network 130 and partner network 140 , SP Service Orchestrator 330 may then send a message to customer 110 indicating that the CIR change request is approved.
- SP Service Orchestrator 330 may send a message to customer 110 indicating that resources are unavailable at the present time and the CIR change is denied (block 550 ; FIG. 7B, 782 ).
- the operator associated with service provider network 130 may initiate a test of the E-line with the modified CIR parameter.
- SP Service Orchestrator 330 may test OVC-A ( FIG. 2 ) in service provider network 130 according to the new CIR ( FIG. 6, 610 ; FIG. 7B, 784 ).
- Service Orchestrator 330 -P may test OVC-B ( FIG. 2 ) in partner network 140 based on the new CIR (block 620 ; FIG. 7B, 786 ).
- the initiation of the test of OVC-B in partner network 140 may be based on, for example, a contract/agreement between the parties associated with service provider network 130 and partner network 140 .
- the test in each of networks 130 and 140 may include sending test packets from customer 110 location to an end point location to test the CIR (i.e., test OVC throughput).
- CIR i.e., test OVC throughput
- Service Orchestrator 330 may send test packets from UNI 120 - 1 to ENNI 150 and determine if the throughput meets the new CIR.
- partner Service Orchestrator 330 -P may send test packets from ENNI 150 to UNI 120 - 2 and determine whether the throughput meets the new CIR.
- Service Orchestrator 350 -P After Service Orchestrator 330 -P completes testing of OVC-B, Service Orchestrator 350 -P sends a message to Service Orchestrator 330 indicating a pass or failure of the test ( FIG. 7, 790 ).
- Service Orchestrator 330 may then determine if the tests passed (block 630 ) (i.e., tests of OVC-A and OVC-B). In some implementations, if Service Orchestrator 330 determines that the tests passed in both partner network 140 and service provider network 130 (i.e., the data throughput meets or exceeds the new CIR) (block 630 —yes), the operator associated with service provider network 130 may initiate an end-to-end test of the entire EVC to ensure that the entire circuit throughput meets the new CIR ( FIG.
- SP Service Orchestrator 330 may transmit test packets from UNI 120 - 1 to UNI 120 - 2 and determine if the end-to-end throughput of the EVC meets the new CIR. In other implementations, the end-to-end test of the entire EVC may be bypassed.
- Service Orchestrator 330 forwards a message indicating that the CIR service change request has been completed ( FIG. 7B, 794 ). In this case, the new CIR for the E-line service is automatically implemented for customer 110 (block 650 ).
- Service Orchestrator 330 forwards a message to customer 110 indicating that the resources are unavailable at the current time (block 660 ).
- FIG. 8 is a signal flow diagram associated with providing billing changes and service level objective (SLO) updates for an implemented CIR change. For example, if testing is successful (i.e., the data throughput meets or exceeds the new CIR) and the CIR change is implemented, SP Service Orchestrator 330 initiates a new billing procedure. For example, SP Service Orchestrator 330 sends a message to OSS/BSS 320 indicating that CIR is changed from “x” to “y” (e.g., from a first rate to a second rate) ( FIG. 8, 810 ). Similarly, Service Orchestrator 330 -P sends a message to its OSS/BSS 320 -P indicating that the CIR is changed from x to y ( FIG. 8, 820 ).
- SLO service level objective
- the service level objectives (SLOs) between the service provider associated with network 130 and partner network 140 may be updated ( FIG. 8, 830 ).
- the percentage of valid CIR modification requests that are accepted may be updated.
- the percentage of valid modification requests may correspond to the total number of modification requests accepted for an elastic service instance (i.e., CIR in this example) during a measurement interval (TAR) divided by the total number of valid CIR modification requests received during the measurement interval (TVR) (i.e., TAR/TVR).
- the term “elastic” indicates the capability to modify an active service by changing the value of one or more service attributes (e.g., CIR value in this example).
- the percentage of accepted requests that are fulfilled may also be updated.
- the percentage of accepted requests that are fulfilled may correspond to the total number of CIR modification requests fulfilled during a measurement interval (TFR) divided by the total number of CIR modification requests accepted during the measurement interval (TAR) (i.e., TFR/TAR).
- TFR measurement interval
- TAR total number of CIR modification requests accepted during the measurement interval
- SP Service Orchestrator 330 sends a message to OSS/BSS 320 indicating that a valid request was not fulfilled. This allows OSS/BSS 320 to update the percentage of accepted requests that were fulfilled (TFR/TAR).
- Partner network 140 may similarly update its SLO parameters, including the percentage of valid requests accepted (TAR/TVR) and the percentage of accepted requests that have been fulfilled (TFR/TAR) ( FIG. 8, 840 ).
- the service provider associated with service provider network 130 may confirm the CIR change without end-to-end testing of the EVC (e.g., the EVC from UNI 120 - 1 to UNI 120 - 2 shown in FIG. 2 ).
- SP Service Orchestrator 330 sends a message to OSS/BSS 320 to initiate new billing requirements associated with the new CIR and update on-demand SLO parameters, such as the percentage of valid requests accepted (TAR/TVR) and the percentage of accepted requests fulfilled (TFR/TAR).
- the service provider associated with partner network 140 may similarly update its billing requirements and update the on-demand SLO parameters without performing end-to-end testing of the EVC.
- service provider network 130 and partner network 140 may support on-demand modifications of CIR.
- SP Service Orchestrator 330 and Service Orchestrator 330 -P may exchange timing information and/or timing requirements associated with implementing the on-demand modifications.
- SP Service Orchestrator 330 and Service Orchestrator 330 -P may exchange the following parameters: CIR elastic which corresponds to the CIR value after the on-demand modification; CIR lb which corresponds to a lower bound or minimum value for CIR; CIR ub which corresponds to an upper bound or maximum value for CIR; N max,CIR which corresponds to the maximum number of increments to increase CIR from CIR lb to CIR ub ; CIR next which corresponds to a subscriber defined value for the CIR after the end time of an immediate CIR change request or a CIR change request scheduled for a future date and time; CIR increment which corresponds to a granularity which is the minimum incremental value for CIR; T r-sp-part which corresponds to the time interval for partner network 140 delivery of elastic E-line attribute modification request; and T c-m-sp-part which corresponds to the time interval for the subscriber modification or cancellation of an on-demand subscriber modification of an elastic E-line
- SP Service Orchestrator 330 may also measure the following parameters: T r-sp-sab which corresponds to the time interval for service provider delivery of elastic E-line attribute modification requests by a subscriber; T r-sp-part ; T c-m-sp-sub which corresponds to the time interval for subscriber modification or cancellation of an on-demand subscriber modification of an elastic E-line attribute requested for a future date and time; and T c-m-sp-part . Measuring these parameters enable the operator of service provider network 130 (and partner network 140 ) to ensure that SLOs are being met.
- the operators of network 130 and partner network 140 make modifications to an E-Line service in an on-demand manner without requiring processing of new service orders and provisioning of new OVCs and/or EVC.
- billing parameters are updated in a real-time manner.
- customer 110 may request modification of other parameters associated with an E-Line service.
- customer 110 may request a modification of an excess information rate (EIR) parameter for an E-Line service.
- EIR excess information rate
- processing associated with the requested EIR may proceed in a manner similar to that described above for the CIR change request. That is, the operator of network 130 may perform an on-demand modification and determine if capacity is available for the requested change without having to process a new order and, for example, without requiring the provisioning of a new OVC or EVC.
- partner network 140 may perform an on-demand modification and determine if capacity is available for the requested EIR change in partner network 140 . If successful (e.g., adequate resources exist at both network 130 and partner network 140 ), the change is automatically implemented.
- customer 110 may request modification of other parameters associated with an E-Line service.
- customer 110 may request a modification of a committed burst size (CBS) parameter or an excess burst size (EBS) parameter for an E-Line service.
- CBS committed burst size
- EBS excess burst size
- processing associated with the requested CBS or EBS may proceed in a manner similar to that described above for the CIR change request. That is, the operator of network 130 may perform an on-demand modification and determine if capacity is available for the requested change without having to process a new order and without requiring the provisioning of a new OVC.
- partner network 140 may perform an on-demand modification and determine if capacity is available for the requested CBS/EBS change in partner network 140 . If successful (e.g., adequate resources exist at both network 130 and partner network 140 ), the change is automatically implemented.
- SP Service Orchestrator 330 -P may notify OSS/BSS 320 to allow for proper billing associated with the attribute modification.
- SP Service Orchestrator 330 and Service Orchestrator 330 -P may exchange attribute information, such as upper and lower bounds for the attribute, granularity information, values after the modification, etc., similar to that discussed above with respect to CIR modification requests to ensure that SLOs are being met.
- Implementations described herein provide for modification of E-Line services on-demand.
- a customer may request a change to an E-Line service and operators associated with networks over which the E-Line is provisioned determine whether adequate resources are available to service the requested change. If such resources are available, operators automatically implement the change with respect to the E-Line, and without the customer having to submit a new service order and wait a long time before the change is implemented.
- logic may include hardware, such as one or more processors, microprocessor, application specific integrated circuits, field programmable gate arrays or other processing logic, software, or a combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/391,688 US11082307B2 (en) | 2018-12-19 | 2019-04-23 | E-Line service control |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862781899P | 2018-12-19 | 2018-12-19 | |
US16/391,688 US11082307B2 (en) | 2018-12-19 | 2019-04-23 | E-Line service control |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200204462A1 US20200204462A1 (en) | 2020-06-25 |
US11082307B2 true US11082307B2 (en) | 2021-08-03 |
Family
ID=71097895
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/391,688 Active 2039-05-09 US11082307B2 (en) | 2018-12-19 | 2019-04-23 | E-Line service control |
Country Status (1)
Country | Link |
---|---|
US (1) | US11082307B2 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11843673B2 (en) * | 2021-12-20 | 2023-12-12 | Verizon Patent And Licensing Inc. | Systems and methods for modifying connectivity and cloud services |
US11831714B2 (en) * | 2022-03-16 | 2023-11-28 | International Business Machines Corporation | Programmatically mapping workloads to networked object storage |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090122811A1 (en) * | 2006-12-21 | 2009-05-14 | Zhiping Wu | Method and apparatus for modifying bandwidth in bandwidth on demand services |
US20090287809A1 (en) * | 2007-01-31 | 2009-11-19 | Jie Chen | Service bandwidth configuring method and network management system |
US20120123829A1 (en) * | 2009-07-30 | 2012-05-17 | CENX, Inc. | Independent carrier ethernet interconnection platform |
US8379656B2 (en) * | 2009-09-04 | 2013-02-19 | Equinix, Inc. | Real time configuration and provisioning for a carrier ethernet exchange |
US8392509B1 (en) * | 2004-03-26 | 2013-03-05 | Cisco Technology, Inc. | Ethernet local management interface (E-LMI) |
US20130194932A1 (en) * | 2012-01-30 | 2013-08-01 | Verizon Patent And Licensing Inc. | Carrier ethernet service bandwidth allocation systems and methods |
US8582630B2 (en) * | 2003-08-07 | 2013-11-12 | At&T Intellectual Property I, L.P. | Methods and systems for providing an asymmetric Ethernet service |
US20160050119A1 (en) * | 2014-08-14 | 2016-02-18 | Ciena Corporation | Systems and methods for setting up end-to-end traffic engineered ethernet line services |
US10015115B2 (en) * | 2015-06-01 | 2018-07-03 | Ciena Corporation | Software defined networking service control systems and methods of remote services |
-
2019
- 2019-04-23 US US16/391,688 patent/US11082307B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8582630B2 (en) * | 2003-08-07 | 2013-11-12 | At&T Intellectual Property I, L.P. | Methods and systems for providing an asymmetric Ethernet service |
US8392509B1 (en) * | 2004-03-26 | 2013-03-05 | Cisco Technology, Inc. | Ethernet local management interface (E-LMI) |
US20090122811A1 (en) * | 2006-12-21 | 2009-05-14 | Zhiping Wu | Method and apparatus for modifying bandwidth in bandwidth on demand services |
US20090287809A1 (en) * | 2007-01-31 | 2009-11-19 | Jie Chen | Service bandwidth configuring method and network management system |
US20120123829A1 (en) * | 2009-07-30 | 2012-05-17 | CENX, Inc. | Independent carrier ethernet interconnection platform |
US8379656B2 (en) * | 2009-09-04 | 2013-02-19 | Equinix, Inc. | Real time configuration and provisioning for a carrier ethernet exchange |
US20130194932A1 (en) * | 2012-01-30 | 2013-08-01 | Verizon Patent And Licensing Inc. | Carrier ethernet service bandwidth allocation systems and methods |
US20160050119A1 (en) * | 2014-08-14 | 2016-02-18 | Ciena Corporation | Systems and methods for setting up end-to-end traffic engineered ethernet line services |
US10015115B2 (en) * | 2015-06-01 | 2018-07-03 | Ciena Corporation | Software defined networking service control systems and methods of remote services |
Also Published As
Publication number | Publication date |
---|---|
US20200204462A1 (en) | 2020-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11202240B2 (en) | Systems and methods for managing and monitoring communication sessions | |
JP7047113B2 (en) | Methods, Devices and Systems for Guaranteeing Service Level Agreements for Applications | |
US11196803B2 (en) | Edge cloud broker and method therein for allocating edge cloud resources | |
US11234158B2 (en) | System and method for deferred delivery of content based on congestion in a network environment | |
US11272333B2 (en) | Convergent charging method and device | |
US20190230484A1 (en) | Policy control with mobile edge computing | |
US20170118616A1 (en) | Distributed and Localized Policy and Charging Control in Cellular Networks to Enable Route Flexibility | |
US12022576B2 (en) | Cloud-based interworking gateway service | |
EP3837805B1 (en) | Methods, apparatus and computer-readable mediums supporting subscriptions to events in a core network | |
US12010538B2 (en) | Method and apparatus to support performance data streaming end-to-end (E2E) procedures | |
JP2020506625A (en) | Choosing sustainable services | |
US11082307B2 (en) | E-Line service control | |
US9986104B2 (en) | Routing of diameter protocol messages based on a subscriber policy | |
US20230362604A1 (en) | Charging function fallback | |
WO2020109853A1 (en) | Optimized resource management based on predictive analytics | |
US20190208450A1 (en) | Policy state propagation system | |
WO2013061115A1 (en) | Method and apparatus for supporting usage of a multipath transport protocol | |
US10666526B2 (en) | Method and apparatus for measuring end-to-end accessibility in voice over long term evolution networks | |
Peng et al. | Multipath mobile data offloading of deadline assurance with policy and charging control in cellular/WiFi networks | |
CN113170379A (en) | Apparatus, method and computer program | |
US11843673B2 (en) | Systems and methods for modifying connectivity and cloud services | |
US20230232283A1 (en) | Resource balancing | |
US20230354165A1 (en) | System and method for dynamic network slice subscription and creation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TOY, MEHMET;REEL/FRAME:048969/0397 Effective date: 20190423 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |