A network control method relates to the communications field, includes receiving, by a controller, a packet forwarded by a forwarder, detecting, by the controller, a status of a virtual currency identifier of the packet, querying, by the controller according to a user identifier in the packet, whether the user has permission to improve service quality when the status of the virtual currency identifier of the packet indicates that a user is willing to pay virtual currency to raise a network priority, and raising, by the controller, the network priority of the user, starting charging, and sending a network priority of the user to the forwarder when the user has the permission to improve the service quality such that the forwarder forwards a packet of the user according to the network priority of the user.

A vehicle to everything application function (V2X AF) transmits a DIAMETER AA-request command to a policy and charging rule function (PCRF). The DIAMETER AA-request command comprises: an attribute value pairs (AVP) identifying a V2X application, and one of more quality of service (QoS) parameters. The one of more quality of service (QoS) parameters indicate a QoS of a V2X bearer for the V2X application employed by a wireless device. The PCRF decides one or more policy and charging control (PCC) provisions for the QoS provided for the V2X application identified by the AVP. The PCRF transmits a DIAMETER command to a policy charging enforcement function (PCEF). The DIAMETER command comprises the one or more PCC provisions for the QoS. The PCEF enforces the one or more PCC provisions for the QoS on a plurality of packets transmitted via the V2X bearer to the wireless device.

An on-board network system includes at least one processor. Plural relay devices that temporarily retain received data and relay the retained data in descending order of relay priority levels include a first relay device. For each set of data retained at the first relay device, the processor measures a retention duration for which the data is retained without being relayed. Data whose measured retention duration exceeds a predetermined threshold is congested data. A second relay device is a different relay device from the first relay device among the plurality of relay devices, and is capable of relaying the congested data. The processor requests the second relay device to raise the relay priority level of the congested data.

This disclosure relates to methods for adjusting network transmission service levels, data terminals, and network servers. The method for adjusting a network transmission service level, used in a data terminal, comprises: obtaining data to be transmitted; inserting the data into specified queues or assigning priorities to the data according to one or more data characteristics selected from importance, instantaneity, data resources, and data types; transmitting a transmission service request to a network server, wherein the transmission service request includes information about the network transmission service level requested and corresponding network configuration parameters; and using the network transmission service provided by the network server according to the transmission service request to transmit the data in queues or the data whose priorities correspond to the network transmission service level provided. The data terminal could ask the network transmission service provider to provide different network transmission service to improve the instantaneity and stability of data transmission.

A first device transmits a first Fibre Channel frame with a first priority to a second device. The first device receives a second Fibre Channel frame from the second device, where the second Fibre Channel frame has a second priority indicated by the second device. The first device determines whether to adopt the second priority indicated by the second device or whether to continue to use the first priority for transmitting subsequent Fibre Channel frames to the second device.

A method is provided in one example embodiment and includes determining whether a packet received at a network node in a communications network is a high priority packet; determining whether a low priority queue of the network node has been deemed to be starving; if the packet is a high priority packet and the low priority queue has not been deemed to be starving, adding the packet to a high priority queue, wherein the high priority queue has strict priority over the low priority queue; and if the packet is a high priority packet and the low priority queue has been deemed to be starving, adding the packet to the low priority queue.

A device is configured to receive packet timing data, from multiple network devices, for subscriber application traffic over an Internet Protocol (IP) wireless access network and to calculate, based on the packet timing data, timing latencies for a particular subscriber flow. The device is configured to retrieve Quality of Service (QoS) timing specifications for the particular subscriber flow and to determine when the calculated timing latencies for the particular subscriber flow fail to meet the QoS timing specifications for the particular subscriber flow. The device is configured to identify one or more of the network devices that are causing the particular subscriber flow to fail to meet the QoS timing specifications and to instruct the one or more of the network devices to modify QoS parameters for the particular subscriber flow to improve timing latency for the particular subscriber flow.

A method, operational at a device, includes receiving at least one packet belonging to a first set of packets of a packet flow marked with an identification value, determining that the at least one packet is marked with the identification value, determining to change a quality of service (QoS) treatment of packets belonging to the first set of packets marked with the identification value that are yet to be received, and sending a request to change the QoS treatment of packets belonging to the first set of packets marked with the identification value that are yet to be received to trigger a different QoS treatment of packets within the packet flow, responsive to determining to change the QoS treatment. Other aspects, embodiments, and features are also claimed and described.

In one embodiment, a next set of packets in a first flow may be identified. A counter may be incremented, where the counter indicates a first number of initial sets of packets in first flow that have been identified. The identified next set of packets may be prioritized such that the first number of initial sets of packets in the first flow are prioritized and a sequential order of all packets in the first flow is maintained. The identifying, incrementing, and prioritizing may be repeated until no further sets of packets in the first flow remain to be identified or the first number of initial sets of packets is equal to a first predefined number.

Methods and apparatus for memory allocation and reallocation in networking stack infrastructures. Unlike prior art monolithic networking stacks, the exemplary networking stack architecture described hereinafter includes various components that span multiple domains (both in-kernel, and non-kernel). For example, unlike traditional “socket” based communication, disclosed embodiments can transfer data directly between the kernel and user space domains. A user space networking stack is disclosed that enables extensible, cross-platform-capable, user space control of the networking protocol stack functionality. The user space networking stack facilitates tighter integration between the protocol layers (including TLS) and the application or daemon. Exemplary systems can support multiple networking protocol stack instances (including an in-kernel traditional network stack). Due to this disclosed architecture, physical memory allocations (and deallocations) may be more flexibly implemented.