Charging interval authorizations according to the techniques disclosed herein provide for credit reservation and charging of whole charging intervals across two or more credit containers(36) in or linked to a subscriber account (34), without the need for redefining the charging interval size, even where the types of credit units differ between or among the credit containers (36) used to authorize the charging interval. Among the various advantages, the disclosed techniques preserve the original charging interval size, which may be defined for reasons of signaling efficiency, while simultaneously allowing the reservation or consumption of credit units from credit containers (36) having insufficient remaining credit for authorization of the full charging interval.

The embodiments herein relate to optimized procedure for Packet Flow Description (PFD) management. In one embodiment, there proposes a method (800) for managing Packet Flow Description (PFD), comprising: receiving (S801) from a Session Management Function (SFM) (201) or a User Plane Function (UPF) (302) a demand message indicating the demand for at least one PFD mle for an application; detecting (S802) the at least one PFD mle for the application; and notifying (S803) information regarding the at least one PFD rule to the SMF (201) or the UPF (302). The embodiments herein may achieve an optimized procedure for PFD Management which optimizes the delivery of PFD rules, by reducing the amount of signaling and by reducing the number of hops between the producer (AF) and the consumer (UPF).

A method for an access network of a telecommunications network includes: in a first step, a first authentication, authorization and accounting (AAA)-related message is sent by an authentication server entity and received by an access orchestrator entity, the first AAA-related message comprising: at least one standardized message attribute according to an access protocol; and at least one vendor-specific message attribute; in a second step, subsequent to the first step, the access orchestrator entity sends a second AAA-related message to a service edge entity, the second AAA-related message solely comprising the at least one standardized message attribute according to the access protocol; and in a third step, subsequent to the first step and prior to, during or after the second step, the access orchestrator entity sends at least one third AAA-related message to the service edge entity, the at least one third AAA-related message corresponding to a message according to an application programming interface (API) or to a further access protocol.

Embodiments of the present invention relate to a centralized network analytic device, the centralized network analytic device efficiently uses on-chip memory to flexibly perform counting, traffic rate monitoring and flow sampling. The device includes a pool of memory that is shared by all cores and packet processing stages of each core. The counting, the monitoring and the sampling are all defined through software allowing for greater flexibility and efficient analytics in the device. In some embodiments, the device is a network switch.

A data volume exchange server includes a terminal IF unit configured to receive an exchange request for a contract data volume of an own country and a contract data volume of another country from terminals of subscribers having contract data volumes of telecommunication carriers of countries different from each other, a data volume exchange unit configured to perform matching of a pair in which another country that requests a contract data volume in one of the received exchange requests matches the own country that provides a contract data volume in another of the received exchange requests, and a server IF unit configured to instruct the communication servers of the telecommunication carriers in the countries to transfer a contract data volume of a matched subscriber of the own country as an exchanged data volume of a subscriber of the other country who is a matching partner.

This disclosure provides an event subscription method. A policy control entity receives information about a first event from a session management entity, where the information about the first event includes subscription indication information of the first event and first data description information of the first event. The policy control entity determines that second data description information of a second policy and charging control (PCC) rule is the same as the first data description information, where the second data description information is data description information of a second event, and the second PCC rule includes second indication second information indicating to detect the second event. The policy control entity, based on the subscription indication information, updates the second PCC rule obtain a first PCC rule, and sends, the first PCC rule comprising the second indication information and first indication information indicating to detect the first event, to the session management entity.

A processing system may maintain a communication graph that includes nodes representing a plurality of phone numbers including a first phone number and edges between the nodes representing a plurality of communications between the plurality of phone numbers and may generate at least one vector via a graph embedding process applied to the communication graph, the at least one vector representing features of at least a portion of the communication graph. The processing system may then apply the at least one vector to a prediction model that is implemented by the processing system and that is configured to predict whether the first phone number is associated with a type of network activity associated with a telecommunication network and may implement a remedial action in response to an output of the prediction model indicating that the first phone number is associated with the type of network activity.

A processing system may maintain a relationship graph that includes nodes and edges representing phone numbers and device identifiers having associations with the phone numbers. The processing system may obtain an identification of a first phone number or a first device identifier for a fraud evaluation and extract features from the relationship graph associated with at least one of the first phone number or the first device identifier. The plurality of features may include one or more device identifiers associated with the first phone number, or one or more phone numbers associated with the first device identifier. The processing system may then apply the features to a prediction model that is implemented by the processing system and that is configured to output a fraud risk value of the first phone number or the first device identifier and implement at least one remedial action in response to the fraud risk value.

A base station sends, to a wireless device, a system information block (SIB) indicating that restricted local operator services (RLOS) are supported by a public land mobile network, and receives, from the wireless device and based on the SIB indicating support for the RLOS, a preamble. The base station sends a random access response to the preamble and receives at least one first radio resource control (RRC) message comprising a first information element indicating that an RRC connection of the wireless device is for the RLOS and a second information element comprising an attach request message indicating, to a mobility management entity (MME) configured with an RLOS access point name, that an attach request of the wireless device is for the RLOS. The base station sends to the wireless device a second RRC message comprising an attach accept message indicating acceptance of the RLOS by the MME.

A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.