Patent classifications
H04W40/24
Routing Information Transmission Method and Apparatus
A routing information transmission method includes before forwarding a service traffic packet, a first network device receives first Border Gateway Protocol (BGP) routing information from a second network device to determine a first forwarding table entry based on a service identifier and an identifier of a first network slice that are in the first BGP routing information. The first forwarding table entry indicates to forward, to the second network device using the first network slice, the service traffic. When receiving the service traffic packet corresponding to the service identifier, the first network device determines the first network slice based on the first forwarding table entry, and then sends the service traffic to the second network device using the first network slice.
RELAY DEVICE AND RELAY METHOD
A relay device includes: a storage unit storing a correspondence table that correlates header information with a relay resource, the relay resource implementing a communication request class defined based on the header information; a data acquisition unit acquiring the data transmitted from the transmission source device as acquired data; a relay resource determination unit determining a relay resource for the acquired data based on header information included in the acquired data and the correspondence table; and a data transmission unit transmitting the acquired data to the destination device using the relay resource determined by the relay resource determination unit.
Multi-connectivity restriction for services demanding single-path or single access
A method for restricting multi-connectivity functionality of a user equipment (UE) includes: storing a mapping table on a memory of the UE, wherein the mapping table provides assignment information about a respective single access mode assigned to a service requestable by the UE, wherein the respective single access mode is one of multiple access modes; receiving service information about a requested service via a network interface of the UE; comparing, by a process of the UE, the service information to entries of the mapping table, and selecting a single access mode assigned to the requested service; wherein the multi-connectivity functionality of the UE is restricted by: a bypass entity redirecting data traffic associated with the requested service directly to the selected single access mode; or a multipath scheduler scheduling data traffic associated with the requested service to a communication link that corresponds to the selected single access mode.
Dynamic mapping of nodes responsible for monitoring traffic of an evolved packet core
Introduced here are visibility platforms able to process the traffic handled by the gateways of an Evolved Packet Core (EPC) with Control and User Plane Separation (CUPS). A visibility platform can include a control processing node (CPN) and one or more user processing nodes (UPNs). The visibility platform may populate a data structure in which the CPN and UPNs are associated with locations along an interface on which Sx/N4 traffic is exchanged between the control and user planes. Each location may be representative of the point on the Sx/N4 interface at which Sx/N4 traffic processed by the corresponding node is acquired. The CPN can use the data structure to program session flows that impact how user traffic is handled by the UPNs.
ROUTING PACKETS IN A DATA NETWORK
Packets are routed in a data network comprising a wireless mesh network and a controller providing IPv6 management traffic to nodes of the wireless network. A monitor function and a route table manager are used to generate a route table relating IPv6 addresses to each of the nodes via a respective one of a plurality of POP nodes, by accessing a pre-configured topology file, determining the reachability of each of the plurality of POP nodes from the controller by periodically sending test messages from the monitor function to each POP and detecting acknowledgement of the test messages. If a POP node is not reachable, the route table is updated to relate the IPv6 subnet of the POP that is not reachable to the address of a POP node that is reachable. A Layer 2 network is used to direct the IPv6 management traffic according to the amended route table.
Ethernet bridging in SDN-based wireless mesh networks
The present technology enables inter-network routing by dynamically optimizing data paths for traffic destined for wired clients attached to a wireless access point in a wireless mesh network with a plurality of wireless access points. The present technology can also influence steering of wireless device connections within the wireless mesh network when high amounts of data traffic are exchanged between nearby mesh wireless access points.
COMMUNICATIONS SYSTEM RECONFIGURABLE TO DIFFERENT TOPOLOGIES AND ASSOCIATED METHODS
A communications system may include mobile communications nodes operating according to a current topology and reconfigurable to a new topology. Each mobile communications node may include a wireless transceiver, and a controller configured to transmit spectral performance data to adjacent nodes and receive spectral performance data from the adjacent nodes. The controller may identify potential topologies for the adjacent nodes based on the spectral performance data, select a subset of potential topologies from among the potential topologies, generate a respective performance score for each potential topology of the subset of potential topologies, and switch to a new topology from among the subset of potential topologies based upon the performance scores.
Network parameter provisioning for instantiation of a network entity
A method, an apparatus, an electronic device, and a storage medium for network communication are provided. A first network entity sends a first request message to a second network entity. The first request message includes at least one piece of first network parameter type information, and is used to enable the second network entity to be triggered to send a first message to a third network entity according to a preset event. The first message includes at least one portion of network parameter information corresponding to the first network parameter type information. The first network entity receives a first reply message returned by the second network entity in response to the first request message. Using the present disclosure, the first network entity can dynamically manage an instantiation of the third network entity, and the authority of the third network entity to obtain network parameters.
Network parameter provisioning for instantiation of a network entity
A method, an apparatus, an electronic device, and a storage medium for network communication are provided. A first network entity sends a first request message to a second network entity. The first request message includes at least one piece of first network parameter type information, and is used to enable the second network entity to be triggered to send a first message to a third network entity according to a preset event. The first message includes at least one portion of network parameter information corresponding to the first network parameter type information. The first network entity receives a first reply message returned by the second network entity in response to the first request message. Using the present disclosure, the first network entity can dynamically manage an instantiation of the third network entity, and the authority of the third network entity to obtain network parameters.
Systems and methods for configuring and deploying multi-access edge computing applications
A device may include a processor configured to determine a plurality of requirements for a Multi-Access Edge Computing (MEC) application requested by a customer; select a solution blueprint for the MEC application, from a set of solution blueprints, based on the determined plurality of requirements, wherein the solution blueprint includes an application deployment blueprint and a connectivity blueprint; and receive approval of the selected solution blueprint from the customer. The processor may be further configured to configure at least one transport network device based on the connectivity blueprint, in response to receiving the approval of the selected solution blueprint from the customer; and deploy at least one component of the MEC application on a MEC device in a MEC network based on the application deployment blueprint, in response to receiving the approval of the selected solution blueprint from the customer.