Patent classifications
H04L41/5045
Method and terminal for acquiring information on service function chain in next-generation mobile communication network
Disclosed in the present specification is a method by which a terminal acquires service function chain (SFC) information. The method comprises the steps of: transferring, to a controller, the terminal state information and/or the terminal configuration information; and receiving the SFC information, determined by the controller, by considering the terminal state information and/or the terminal configuration information, wherein the SFC information includes logical path information of a virtualized network function (VNF). The method can also include a step for receiving sub-chain information, determined by the controller, on the basis of the SFC information, or determining the sub-chain information on the basis of the SFC information.
Data transmission system with network service decentralization and method thereof
The present disclosure discloses a data transmission system with network service decentralization and a method thereof. A business service node is connected with a business service lite agent, a consumption service node is connected with a consumption service lite agent, the business service lite agent is connected with the consumption service lite agent, registration and change of service nodes are realized through lite agents, the service nodes realize data transmission of requests and responses through the lite agents, and when the connection to part of the lite agents fails, the data transmission of the requests and the responses can still be realized through other lite agents. Therefore, a technical effect of data transmission with network service decentralization can be achieved.
VIRTUAL NETWORK INTERFACE OBJECTS
Methods and apparatus for interfaces to manage virtual network interface objects. A system may include resource instances and a network interface virtualization coordinator. Responsive to a record creation request, the coordinator creates an interface records that may include an IP address, subnet information and security properties. The coordinator may, in response to a request to attach the record to a resource instance, enable traffic directed to the IP address to flow to the resource instance. In response to a subsequent detach request, the traffic to the IP address may be disabled at the resource instance. The same interface record may be attached to another resource instance in response to another attach request, enabling traffic directed to the IP address to flow to the second resource instance.
SECURE CREATION OF APPLICATION CONTAINERS FOR FIFTH GENERATION CELLULAR NETWORK SLICES
Systems, methods, and computer-readable media for the secure creation of application containers for 5G slices. A MEC application in a MEC layer of a 5G network can be associated with a specific network slice of the 5G network. A backhaul routing policy for the MEC application can be defined based on the association of the MEC application with the specific network slice of the 5G network. Further, a SID for the MEC application that associates the MEC application with a segment routing tunnel through a backhaul of the 5G network can be generated. A MEC layer access policy for the MEC application can be defined based on the SID for the MEC application. As follows, access to the MEC application through the 5G network can be controlled based on both the backhaul routing policy for the MEC application and the MEC layer access policy for the application.
RACK-AWARE AND NETWORK PERFORMANCE-AWARE SERVICE DEPLOYMENT
The disclosure provides an approach for service deployment. Embodiments include receiving an indication of user intent for deployment of one or more services in a network from a user that is not an administrator of the network, wherein the indication of the user intent comprises a domain specific language (DSL). Embodiments include parsing the indication of the user intent to determine one or more constraints for deploying the one or more services. Embodiments include receiving topology information for the network, wherein the topology information comprises associations between racks and machines in the network. Embodiments include receiving network performance information for the network. Embodiments include determining one or more deployment rules for the one or more services based on the one or more constraints, the topology information, and the network performance information. Embodiments include deploying the one or more services in the network based on the one or more deployment rules.
Service level agreement-based multi-hardware accelerated inference
Various systems and methods for implementing a service-level agreement (SLA) apparatus receive a request from a requester via a network interface of the gateway, the request comprising an inference model identifier that identifies a handler of the request, and a response time indicator. The response time indicator relates to a time within which the request is to be handled indicates an undefined time within which the request is to be handled. The apparatus determines a network location of a handler that is a platform or an inference model to handle the request consistent with the response time indicator, and routes the request to the handler at the network location.
Network data aligning
Methods, computer program products, and systems are presented. The method, computer program products, and systems can include for instance: obtaining sensor output data from a user, wherein the sensor output data from the user includes voice data of the user; generating, during an interactive voice response session, vocal response data for presentment by a virtual agent to the user in response to the voice data, wherein the generating includes performing data access queries on one or more storage system; and prioritizing certain asset data of the one or more storage system, wherein the prioritizing is performed in dependence on data of the sensor output data.
Configuration generation for virtual network functions (VNFs) with requested service availability
A Virtual Network Function (VNF) is provided for deployment in a Network Function Virtualization Infrastructure (NFVI). First, an input is obtained that includes a description of available software components, configuration requirements specifying service types to be provided by the VNF, and infrastructure information specifying resources provided by the NFVI. The infrastructure information includes characteristics of virtual machines (VMs). For each service type, a VNF component (VNFC) configuration is generated. The generated VNFC configuration optimizes usage of the resources and satisfies requested service availability. A VNF configuration is formed that includes a collection of VNFC configurations created for the service types. The VNF configuration is delivered to a Network Function Virtualization (NFV) system for the deployment of VNFC instances on the VMs thereby providing the VNF.
Cost estimation for a cloud-based infrastructure provisioning system
A cost estimator system receives a plan, a configuration or proposed changes for a cloud-based infrastructure, and which include data representing one or more computing resources needed for a cloud-based application. A new configuration is generated for the cloud-based infrastructure incorporating the plan, configuration or proposed changes. A price resolver resolves a price of the resources that are part of the new configuration, and requests, from one or more cloud providers associated with the new configuration, price data for the resolved resources. The cost estimator system then generates, based on the price data received by the price resolver, a cost estimate for the new configuration of the cloud-based infrastructure.
SELECTING A NETWORK SLICE IDENTIFIER
During PDN connection establishment in the EPC, a UE and a session managment entity (SME) (e.g., PGW-C+SMF) exchange information. In case the SME supports more than one S-NSSAI, before the SME provides an S-NSSAI to the UE, the SME should check such that the selected S-NSSAI is among the UE's subscribed S-NSSAIs by retrieving the Subscribed S-NSSAI from a UDM using, for example, the Nudm_SDM_Get service operation.