A novel and useful acknowledgement and adaptive frequency hopping mechanism for use in wireless communication systems such as IO-Link Wireless. One or two additional acknowledgement bits are added to packet transmissions. One is a current acknowledgment bit which indicates whether a packet was successfully received anytime during the current cycle. The second bit is a previous acknowledgment bit which indicates whether packets were received successfully anytime during the previous cycle. An adaptive hopping table is constructed using a greedy algorithm which chooses frequencies with the best PER for transmission of higher priority packets, while equalizing the PER products across cycles. A last resort frequency mechanism further improves transmission success by switching to a better performing channel for the last subcycle when previous attempts to transmit a high priority packet have failed.

A method is disclosed, comprising: receiving a first and a second Internet Protocol (IP) packet at a mesh network node; tagging the first and the second IP packet at the mesh network node based on a type of traffic by adding an IP options header to each of the first and the second IP packet; forwarding the first and the second IP packet toward a mesh gateway node; filtering the first and the second IP packet at the mesh gateway node based on the added IP options header by assigning each of the first and the second IP packet to one of a plurality of message queues, each of the plurality of message queues having a limited forwarding throughput; and forwarding the first and the second IP packet from the mesh gateway node toward a mobile operator core network, thereby providing packet flow filtering based on IP header and traffic type.

Examples described herein relate to a network interface device that includes packet processing circuitry to detect usage of an egress port and report the usage of the egress port to a network interface device driver to cause reallocation of hash-based packet buckets to at least one egress port to provide an allocation of hash-based packet buckets to multiple active egress ports of the network interface device with retention of bucket-to-egress port mappings except for re-allocations of one or more buckets to one or more active egress ports. In some examples, usage of the egress port is based on a count of hash buckets assigned to packets to be transmitted from the egress port or a number of bytes of packets enqueued to be transmitted from the egress port.

An on-chip data packet processing method and corresponding integrated circuit, wherein data packets are received at an ingress port and processed with an on-chip wire-speed engine. The processing comprises adding metadata to the data packets, forwarding the processed data to an on-chip QoS unit, altering the metadata of the data packets and/or providing further metadata to the data packets. The data packets are forwarded from the on-chip QoS unit to an on-chip data consumer. If the data consumer is a processing unit the data packets are processed in a first processing step, redirected from the processing unit to the QoS unit and the step of forwarding the data packets to an on-chip data consumer is repeated.

A communication apparatus includes: a monitor configured to monitor a first communication amount in first communication between a first communication apparatus and a terminal apparatus and/or a second communication amount in second communication between a second communication apparatus and the terminal apparatus, the second communication apparatus performs communication with the terminal apparatus; and a transmitter configured to transmit information relating to monitoring result by the monitor to a communication control apparatus that is able to perform policy control and charging control.

A method of managing default QoS rules for PDU session is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. There can be more than one QoS rule associated with the same QoS flow. A default QoS rule is required to be sent to the UE for every PDU session establishment and it is associated with a QoS flow. Within a PDU session, there should be one and only one default QoS rule. In one novel aspect, UE behavior and error handling for proper QoS rule management is defined for PDU session establishment and modification procedures to enforce the one and only one default QoS rule policy.

Described are platforms, systems, and methods for performing queue scheduling tasks on data packet flows. In one aspect, a method comprises: retrieving a plurality of packet flows from a network stack; reconfiguring the retrieved packet flows into per-flow queues; and performing one or more queue scheduling tasks on the per-flow queues.

A network device obtains service requirements associated with a customer identifier, obtains a first profile describing an infrastructure design of multiple transport domains associated with at least one network slice of a network, and obtains a second profile describing performance characteristics of the multiple transport domains of the at least one network slice. The network device receives training data associated with performance measurements of the multiple transport domains of the at least one network slice, and updates a machine learning model based on the training data. The network device selects at least one of the multiple transport domains for orchestration using the updated machine learning model, the service requirements, the first profile, and the second profile.

A device receives a notification indicating a failure of a first server device responsible for a primary message queue that includes messages at a time of the failure. A second server device is responsible for a standby message queue to which the messages are replicated, where a position in the standby message queue and a message time are assigned to each of the replicated messages. The device obtains a record time that identifies the message time of one of the messages that was last obtained from the primary message queue prior to the failure, compares an adjusted record time and the message time of one or more of the messages of the standby message queue to determine a starting position in the standby message queue, and processes messages obtained from the standby message queue beginning at one of the messages assigned to the position that matches the starting position.

Control logic circuitry stores packets in a queue in an order in which the packets are received. A head entry of the queue corresponds to an oldest packet in the order. The control logic circuitry receives flow control information corresponding to multiple target devices including at least a first target device and a second target device. The control logic circuitry determines, using the flow control information, whether the oldest packet stored in the head entry can be transferred to the first target device, and in response to determining that the oldest packet stored in the head entry cannot be transferred to the first target device, i) selects an other entry with an other packet behind the head entry according to the order, and ii) transfers the other packet to the second target device prior to transferring the oldest packet in the head entry to the first target device.