WO2018142021A1

WO2018142021A1 - Counting traffic when split between two accesses

Info

Publication number: WO2018142021A1
Application number: PCT/FI2018/050031
Authority: WO
Inventors: Maryse Gardella; Laurent Thiebaut; Nicolas Drevon; Devaki Chandramouli
Original assignee: Nokia Technologies Oy
Priority date: 2017-02-06
Filing date: 2018-01-17
Publication date: 2018-08-09

Abstract

Methods and apparatus, including computer program products, are provided for counting traffic. In some example embodiments, there may be provided a method that includes receiving at least one downlink packet including at least one counter identifier; and incrementing at least one counter associated with the at least one counter identifier, when the at least one downlink packet is sent to a user equipment over an access type associated with the at least one counter identifier. Related systems, methods, and articles of manufacture are also described.

Description

COUNTING TRAFFIC WHEN SPLIT BETWEEN TWO ACCESSES

Field

The subject matter described herein relates to counting mechanisms to enable charging for cellular wireless.

Background

The use of unlicensed spectrum, such as WiFi, TV white space, and/or other portions of the spectrum that are not licensed like cellular, has become increasingly popular. For example, a service provider may allow a user equipment to receive a stream of Internet traffic from a cellular link as well as a wireless local area network link. The use of the unlicensed spectrum enables the service provider to off-load some traffic, which increases the overall network capacity. Moreover, it has been generally agreed in 3 GPP standards organization that non- standalone 3GPP access will be specified as part of 5G radio work in release 15 to allow dual connectivity (e.g., connectivity via different radio access technologies), and multi- connectivity may be supported as part of 5G radio access.

Summary

Methods and apparatus, including computer program products, are provided for counting traffic.

In some example embodiments, there may be provided a method that includes receiving at least one downlink packet including at least one counter identifier; and incrementing at least one counter associated with the at least one counter identifier, when the at least one downlink packet is sent to a user equipment over an access type associated with the at least one counter identifier.

In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The access type may be indicated by the at least one counter identifier, the at least one counter identifier further comprising an access type identifier. The at least one downlink packet may include a measurement type. The measurement type may indicate whether the increment is based on data volume and/or amount of packets. The access type may include an unlicensed access type. The access type may include an E-UTRAN access type. The access type may include a fifth generation radio access type. A counter value may be reported to a core network node to enable the core network node to determine the data volume and/or the amount of packets for a flow including the at least one downlink packet carried by the access type to the user equipment. At least one condition for reporting the counter value may be received from the core network node. At least one uplink packet may be received from the user equipment and over a corresponding access type, an access type identifier indicative of the corresponding access type may be inserted in the at least uplink packet, and the at least one uplink packet including the access type identifier may be sent to a core network node. The corresponding access type may include an unlicensed access. The corresponding access type may include a licensed access. The corresponding access type may include an E-UTRAN access. The corresponding access type may include a fifth generation access. A request may be received to insert the access type identifier in the at least uplink packet being sent to the core network. Report trigger information may be received, when a session is created and/or a bearer is created. The report trigger information may include at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity.

In some example embodiments, there may be provided a method that includes receiving at least one uplink packet including an access type identifier; and incrementing, based on the access type identifier of the received at least one uplink packet, at least one counter associated with the at least one uplink packet and the access type identifier.

In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The at least one counter may be incremented based on a data volume and/or an amount of packets. At least one downlink packet may be received and at least one counter identifier may be inserted in the at least one downlink packet being forwarded towards a user equipment, at least one counter identifier. The access type identifier associated with the at least one counter identifier may be inserted in the at least one downlink packet being forwarded towards the user equipment. A measurement type associated with the at least one counter identifier may be inserted. An identity of the apparatus associated with the at least one counter identifier may be inserted. Report trigger information for the access network may be sent, when a session connection is created and/or at a bearer is created. The report trigger information may include at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity. At least one policy and charging control rule for a service data flow including at least one rating group associated with an access type may be received from another node. The at least one counter may be associated to the at least one rating group and access type and/or associated to the at least one rating group, access type and service identifier of the received at least one policy and charging control rule for the service data flow the at least one uplink packet is associated with. The at least one counter may be associated to a bearer or a quality of service flow related to the service data flow handled by the apparatus. In some example embodiments, there may be provided a method that includes sending, to a core network node via signaling, an access type identifier representing the access type carrying the traffic, when the apparatus operates bearer and/or quality of service flow switching from an access type to another.

In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. An indication that a split bearer and/or split quality of service flow mode of operation is not allowed may be received from the core network node. The access type identifier may include an identifier of an access type used to convey at least one downlink packet to a user equipment.

The above-noted aspects and features may be implemented in systems, apparatus, methods, and/or articles depending on the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

Description of Drawings

In the drawings,

FIG. 1 depicts an example of a system including a charging mechanism, in accordance with some example embodiments;

FIG. 2 depicts an example of a system including a counting mechanism for handling uplink traffic over unlicensed access, in accordance with some example embodiments;

FIG. 3 depicts an example of a system including a counting mechanism for handling downlink traffic over unlicensed access, in accordance with some example embodiments;

FIGs. 4A-4B depict examples of signaling diagrams for counting mechanisms, in accordance with some example embodiments;

FIG. 5A depicts an example of a system including a core network node, a master base station, and a secondary base station, in accordance with some example embodiments;

FIGs. 5B-5C depict examples of signaling diagrams for switched bearer counting mechanism, in accordance with some example embodiments; and

FIG. 6 depicts an example of an apparatus, in accordance with some example embodiments. Like labels are used to refer to same or similar items in the drawings. Detailed Description

In some example embodiments, there is provided differentiated counting for traffic carried over the licensed spectrum and for traffic carried over the unlicensed spectrum.

In some example embodiments, there is provided differentiated counting for traffic carried over 3 GPP RAT E-UTRA and traffic carried over 3 GPP RAT New Radio.

In some example embodiments, the differentiated counting may include traffic carried in the uplink direction and/or the downlink direction. In some example embodiments, the counting may enable (1) online or offline charging and/or (2) flow based or bearer based charging. Moreover, the counting may enable charging, when the licensed and unlicensed traffic are carried by a flow under a common connection, such as a packet data network connection. In some example embodiments, a flow based charging function (which may use Policy and Charging Control per 3GPP TS 23.203 by which a service data flow is associated to a rating group such as a rating group defined in accordance with 3GPP TS 23.203) and/or a bearer charging function (by which a bearer is associated to a rating group or a bearer container) may be extended with an additional rating group (for example, a charging key) and/or an additional bearer (or quality of service, QoS, type) container or rating group. The additional rating group associated to the service data flow represents the rating associated with the traffic carried by this service data flow over an access type different from the access type associated with the existing rating group. The additional bearer container and/or rating group represent the rating associated with the traffic carried by the bearer (or QoS type) over an access type different from the access type associated with the existing bearer container or rating group. The existing rating group and/or bearer container may be used for the collection of traffic transported over one access type, and the additional rating group and/or bearer container may be used for the collection of traffic transported over another access type. When this is the case, PCC (Policy and Charging Control rules may be updated to allow a policy controller (e.g., a policy and charging rules function (PCRF)/policy charging function (PCF) defined in accordance with 3GPP TS 23.501) to specify different rating groups for the same traffic flow depending on whether the traffic flow has been carried over one access type or over another different access type, such as the licensed spectrum versus unlicensed spectrum or new 3 GPP RAT versus a E- UTRAN.

In the case of uplink traffic, the access network (which may comprise a radio access network such as a 3 GPP radio access network or other type of access network) may insert in each packet the access type identifier or some other type of indicator, in accordance with some example embodiments. This access type identifier may identify the access type over which a packet has been received by the access network. It may identify licensed spectrum or unlicensed spectrum or a 3GPP access technology (e.g., a specific 3GPP RAT).

Based on the access type identifier carried in one or more uplink packets, a network node, such as a packet gateway (PGW) or in the case of 5G a session management function (SMF) node, may collect uplink data usage in corresponding uplink counts associated with access type identifier received within uplink packets, per a PCC rule governing the service data flow. Alternatively or additionally, when the data collection is governed by bearer charging instead of, or in addition to, the PCC rule at service data flow level, the PGW and/or SMF may collect the uplink data usage in uplink bearer counts associated with access type identifier received within uplink packets. Additionally, a network node, such as a serving gateway (SGW) or the SMF of the visited public land mobile network (VPLMN), may collect the uplink data usage in uplink bearer counts associated with access type identifier received within uplink packets. This may be used for roaming scenarios as well.

In the case of downlink traffic, a network node such as the PGW (or user plane function, UPF) may insert, in packet(s) sent towards the access network, a list of one or more counter identifiers so that the access network can increment the counter identifier(s) when the packet is sent over the access type identifier indicated by, or associated with, the counter identifier, in accordance with some example embodiments. When the packet has been sent on the corresponding access type, the access network may then increase the counters identified in the packet. The access network may subsequently report the value of the counters.

In some example embodiments, the network may also include (which may be in each packet) a measurement type regarding whether counting should be on the volume/quantity of packets.

With roaming, a network node such as a SGW (or UPF) may insert, in the downlink packet(s) sent towards the access network, a list of one or more counter identifiers to be incremented by the access network when the packet is sent over the access type indicated by, or associated with, the counter identifier, in accordance with some example embodiments. The SGW or SMF of the VPLMN may generate the list of counter identifiers based on required measurements (as determined by the network for roaming such as the bearer containers, and/or the like) for downlink traffic over the access type selected for the measurements. For the downlink traffic, the access network may obtain the trigger information for reporting the counters to other network node from a network node, such as a packet gateway (PGW) or in the case of 5G a session management function (SMF) node. The reporting trigger information may be sent by a network node, such as a packet gateway (PGW) or in the case of 5G a session management function (SMF) node to the access network, at PDN connection creation and/or bearer creation. The reporting trigger information may indicate time and/or volume and/or amount of packets thresholds, and a periodicity for reporting.

In some example embodiments, the counter identifiers may be reported to other nodes, such as a mobility management entity (MME), SGW/PGW, SMF, and/or the like, to enable the other nodes to perform data collection for downlink traffic differentiated per access type. This differentiation enables taking into account charging for traffic carried over one access type even when the traffic from the same flow and packet data network connection at the network is carried over multiple access types.

In some example embodiments, the counting mechanisms described herein may be applicable to scenarios in which there is traffic separation (e.g., between accesses such as licensed spectrum and unlicensed spectrum or between radio accesses/spectra occurring within the access network while the core network is not aware of the traffic split due to the same radio access technology type and the same bearer being used by the core network). For example, if the core network is not aware of the split/separation occurring at the access network, the core network may not be aware of the count of packets being carried via one of the legs of the split. To illustrate further, if the base station or access point makes the decision regarding offloading packets to an unlicensed spectrum, the core network node (although it may know the total count of packets being carried by both legs) may not be able to differentiate the count of packets being carried via a certain access such as the unlicensed spectrum, unless the differentiated counting disclosed herein is used. Although some of the examples refer to differentiated counting with respect to licensed spectrum and unlicensed spectrum, the differentiated counting disclosed herein may be used with other access types as well. For example, differentiated counting may be used if traffic is split/separated between an LTE radio access technology (e.g., 3GPP E-UTRA) and a 5G radio access technology (e.g., 3GPP New Radio (NR) access technology). Moreover, the counting mechanisms described herein may be applicable when charging models include a volume based model as well. FIG. 1 depicts an example of a system 100 including a user equipment 102 configured with two access types via a base station 110 (labeled eNB) and a wireless access point 112 (labeled WiFi). The system 100 may also include other network nodes including a mobility management entity 120 (MME), a home subscriber server 122 (HSS), a serving gateway 124 (SGW), a packet data network gateway 126 (PGW), a policy and rules charging function node 128 (PCRF), online charging system 130 (OCS), offline charging system 132 (OFCS), and/or other nodes as well, and the system 100 may couple to IP services 134 and/or other networks as well.

Although some of the examples refer to certain nodes in a 3GPP network including the 3GPP evolved packet core (EPC), the subject matter disclosed herein may be used with other types of networks and/or nodes including the Next Gen core (5G) system architecture in which the SMF and 5G-radios are employed, for example.

In the example of FIG. 1, the licensed access and unlicensed access may represent split radio accesses carried on different portions of the spectrum, wherein the splitting occurs in the network such as at the access node/radio access node. In some example embodiments, the decision to split may be performed by the access node, such as base station 110, in which case the core network including the PGW/SGW may not have knowledge of which packets are being split.

In the example of FIG. 1, the base station 110 may operate using a licensed portion of the spectrum (e.g., LTE or cellular licensed spectrum) serving as one access type, while the unlicensed spectrum (e.g., WLAN, licensed assisted access (LAA) and/or the like) may be provided as another access type via the wireless access point 112. The access network/radio access network may route data packets of a given service data flow for a packet data network (PDN) connection (uplink and/or downlink packets) using the licensed spectrum cell and the unlicensed spectrum cell, but the differentiated counting mechanism disclosed herein enables differentiating the traffic carried by the unlicensed access from the licensed access. This routing may be performed on a per PDN connection basis, per bearer basis, and/or per packet basis. However, the PDN connection may need to be authorized for use in the each access type, including access type such as the unlicensed spectrum.

For downlink traffic, the PGW node 126 (or UPF node) may insert, in the packet(s) sent towards the base station 110, a list of one or more counter identifiers and/or associated access type(s) indicating for example "unlicensed." In some example embodiments, the counter identifiers may expressly indicate the access type, although the access type may be implied by the presence of the counter identifier as well. In some example embodiments, the eNB base station 110 may increment the counter identifiers associated with a packet, when that packet is sent over the corresponding access type which is unlicensed in this example. This list may be generated by the SGW/PGW 123/126 (or the SMF) based on required measurements for downlink traffic over the access type unlicensed spectrum. The required measurements may be determined by the PGW (e.g., PCC rules, bearer, and/or the like), SGW, SMF, and/or the like. Alternatively or additionally, there may be provided standard values per access type (for example, PDL-bearer-count-ATl= 0) for bearer level counter identifiers (per volume/per packet) which may be inserted by the PGW, UPF, or SGW, when bearer level counters are required.

For uplink traffic, the access network/radio access network 110/112 may, as noted, insert in each packet the access type identifier which may be used to identify the access type over which the packet is received by the access network. When a packet for a given service data flow is received at the PGW, the PGW may update an appropriate counter for that service data flow.

In some example embodiments, flow based charging may be extended to separately collect data regarding the same flow sent and/or received over different access types to enable the network's offline and online charging to distinguish between access types (e.g., between unlicensed traffic from the licensed traffic and/or other access types).

In some example embodiments, a PCC rule definition per 3GPP TS 23.203 (e.g., service data flow detection, policy control, charging key, and/or the like) may be extended so that an additional charging key (or, e.g., a rating group) can be defined, and so that a policy controller, such as the PCRF, can define this additional charging key to discriminate measurements between access types. To illustrate further, a first charging key (charging key 1) may be defined so that it is applicable to the packets of a service data flow sent/received over the licensed spectrum, while a second charging key (charging key 2) may be defined so that it is applicable to the packets of the service data flow sent/received over the unlicensed spectrum. Traffic count measurements may be defined independently from the charging key/rating groups.

In some example embodiments, there may be provided per-packet access type differentiation for uplink traffic and downlink traffic.

In the case of the uplink traffic, each packet received over one access type by the access network may be marked, by the base station 110 or access point 112, with an access type identifier (ATI), such as "ATx" (e.g., Access Type x, wherein x indicates the access type). The PGW 126 may perform, based on the access type identifier(s) within uplink packets received from the access network, the data collection under an appropriate Rating Groups, Rating Group (RG) and Service Identifier (SI) combinations (e.g., Rating Group + Service Identifier), and/or bearer containers. The SGW 124 may perform, based on the access type identifier(s) within uplink packets received from the access network, the data collection under an appropriate bearer level counting (e.g. with different containers for licensed and unlicensed).

Table 1 below depicts examples of PCC rules. In this table the "Service identifier level reporting" indicates the level reporting to the charging system which is part of the PCC Rule definition in accordance with 3GPP TS 23.203. For example, a PCC Rule 1 for a given service data flow 1 related to video is defined. In this example, the ratings group 1 (RG1) is for traffic carried by the access type for licensed spectrum, ratings group 2 (RG2) is for traffic carried by the access type for unlicensed spectrum, and service level reporting is required for the service data flow 1.

Table 1

FIG. 2 depicts a portion of system 100 including packet marking for the uplink, in accordance with some example embodiments. At 205, if a packet is received over the access type unlicensed access, the network node 110 and/or access point 112 may mark the packet with an access type identifier, such as the "ATu" indicating access type unlicensed, in accordance with some example embodiments. If a packet is received over the access type licensed access, the network node 110 and/or access pointl 12 may mark the packet with an the access type identifier, such as the "ATI" indicating access type licensed, in accordance with some example embodiments. Although the previous example indicates marking each access type, only a single access type may be marked as well (e.g., only explicitly marking the packets with ATu and those packets not carrying ATu are presumed to be licensed access).

As noted above, the indication may also be used to indicate that the uplink traffic was carried by another access type, such as LTE access, 5G access, and/or any other type of RAT for which differentiated counting is performed for split traffic. For example, base station 110 may be a 5G NR access point serving UE 102, while access point 110 (or access point 112) may serve UE 102 using a LTE radio access technology. In this example, the access type identifier such as "ATe" (indicating for example, access type E-UTRAN) may be added to packets carried on the downlink via E-UTRAN.

At 210, a network node such as the PGW 126 may maintain counters to accumulate measurements for the uplink, in accordance with some example embodiments. The counts, or measurements, may be based on PCC rules installed (as described below at 230) by the PCRF 128 (and/or based on bearer counts), in accordance with some example embodiments. For example, for a given service data flow 1 , a packet including the ATu access type identifier may be collected at the counter associated with RG2 and SI, and a packet including the ATI access type identifier, may be collected at the counter RG1 + SI1. As shown at FIG. 2, the PCC rules may dictate the counters, and the PCC rules may be installed at 230, as explained below. To illustrate further, 3 counters may be maintained at the PGW 126 for unlicensed uplink: one for RG2+SI1, one for RG4, one for RG4+SI4. Likewise, 3 counters maintained for the licensed uplink: one for RG1+SI1, one for R3, one for RG3+SI4.

At 230, a network node such as the PCRF 128 may install the policy rules at the network node such as PGW 126, in accordance with some example embodiment. The installed rules at 230 may enable the PGW to determine the counts/measurements to be collected for the unlicensed and licensed traffic. In the example of FIG. 2, the rules are similar to those found at Table 1 above. In some example embodiments, the PCC rules may be installed at the outset to enable the PGW 126 to measure/count packets carrying the access identifiers, such as ATI and/or ATu. FIG. 3 depicts a portion of system 100 including counter incrementing for the downlink, in accordance with some example embodiments.

At 230, the PCC rules for the service data flows may be provided to a node, in accordance with some example embodiments. For example, the PCRF 128 may provide the PCC rules to the PGW 126. The PCC rules enable the PGW 126 to determine what measurements, or counts, it needs to accumulate and in what service data flows it needs to insert counter identifiers, such as PDL-count-ATu-1, PDL-count-ATu-2, and/or the like. In the case of the downlink, when the PGW 126 determines a specific count or measurement is needed for traffic carried via a specific access type (based on activated PCC rules, Rating Group level, combination of Rating Group and Service Identity (Rating Group + Service Identifier) level, offline charging, online charging, from charging characteristics, for bearer charging, and/or the like), the PGW may create, for each specific measurement, a corresponding counter identifier, such as PDL-count-ATx-n. In this example the PGW selects the unlicensed access type as the one to be counted by the access network as shown at 230 and by the indicators by PDL-count-ATu-1 for the unlicensed packets in service data flow 1, PDL- count-ATu-2 for the unlicensed packets in service data flow 2, and PDL-count-ATu-3 for the unlicensed packets in service data flow 3.

For the packet sent in the downlink direction, a network node such as the PGW 126 may, as noted, insert a list of one or more count identifiers, such PDL-count-ATx-1, 2, 3, n, and/or the like, associated with the service data flow and/or with the bearer the packet belongs to. In this example, the PDL-count represents the count identifier which can be incremented by the access point when the packet is split to an indicated access type, while ATx-1 identifies that access type. Additionally, for each packet sent in downlink direction, a network node such as the SGW 124 may insert a list of one or more identifiers (SDL-count-ATx-n) associated to the bearer the packet belongs to. Alternatively or additionally, there may be standard values for "bearer level" counter identifiers (per volume/per packet) which can be inserted by the SGW or by the PGW. For each packet received by the base station 110 and sent via the downlink over the access type unlicensed spectrum, the base station 110 may increment each of the PDL- count- ATx-n/SDL-count-ATx-n in the list contained in the packet where access type identifier, such as ATx, identifies unlicensed access type (if present). At 305, the PGW 126 may maintain counters, in accordance with some example embodiments. As shown in FIG. 3, the PGW may construct 3 counters in this example. The first counter corresponds to service data flow 1. Specifically, PDL-count-ATu-1 is mapped to service data flow 1 as the unlicensed rate group (RG2 and SI1), PDL-count-ATu-2 is mapped to service data flow 2 as the unlicensed rate group (RG4), and PDL-count-ATu-3 is mapped to service data flow 3 as the unlicensed rate group (RG4 and SI4). At 310, the PGW 126 may insert the PDL-count-ATx-n list in a packet, in accordance with some example embodiments. Referring to 310, a packet "p" associated with service data flow 1 would have a counter identifier, PDL-count-ATu-1, inserted therein, while a packet "q" associated with service data flow 2 would have a counter identifier, PDL-count-ATu-2, both of which are for the access type unlicensed.

When a packet is to be carried in downlink to the UE 102 by the unlicensed spectrum, the base station 110 may increment, at 320, the PDL-count-ATx-n associated with the packet, in accordance with some example embodiments. For the downlink traffic, the network node, such as a packet gateway (PGW) or in the case of 5G a session management function (SMF) node, may send reporting trigger information to the access network at PDN connection creation, bearer creation, and/or other times as well. The reporting trigger information may indicate time and/or volume and/or amount of packets thresholds, and a periodicity for reporting.

The base station 110 may report counters values to another node to allow the PGW 126 to update counters for the traffic sent by the access network over a specific access type to enable the EPC charging process. For example, the base station 110 may report counters (which may correspond to the packets carried by the unlicensed access). Examples of the reported counters include a counter identified by PDL-count-ATu-n, and a counter identified by SDL-count- ATu-n.

Table 2 depicts examples of the PDL-count-ATu-n list created by the PGW 126. In Table 2, the "Service identifier level reporting" indicates the level reporting to the charging system which is part of the PCC Rule definition in accordance with 3GPP TS 23.203

Example 1 • PCC Rulel for SDF1 related to video: (RG2 + SI1) level reporting

=> PDL-count-ATx-1 for unlicensed

• PCC Rule2 for SDF2 related to web browsing, and to Chat

session: RG4 level reporting => PDL-count-ATx-2 for

unlicensed. • PCC Rule4 for SDF4 related to Facebook: (RG4 + SI4) level

reporting => PDL-count-ATx-3 for unlicensed.

In some example embodiments, the Gx interface defined in 3GPP TS 29.203 and 3GPP TS 29.212 may be extended so that the PCC rule definition includes an additional charging key associated with the additional access type. In some example embodiments, the Sx interface defined in 3 GPP TS 29.244 (or the N4 in the case of 5G which is defined at 3 GPP TS 23.501) may be extended so that the list of SDL-count-ATx-nx/PDL-count-ATx-n determined by SGW-C/PGW-C (SMF in case of 5G) is conveyed towards SGW-U/PGW-U (UPF in case of 5G). FIGs. 4A-4B depict signaling diagrams 400/499 for counting mechanism taking place, in accordance with some example embodiment.

At 402A the UE may send an attach request to the eNB 101, in accordance with some example embodiments. In turn the base station 110 may send at 402B an attach request to the MME 120, in accordance with some example embodiments. In response, the MME 120 may send, at 404, a create session request to the SGW 124, which in response forwards, at 406, the create session request to the PGW 126, in accordance with some example embodiments. At 408, the PGW 126 may send a session establishment message to the PCRF 128, and in response receive, at 410, an acknowledgement which may include PCC rules, and for each PCC rule a rating group for the licensed access and a rating group for the unlicensed access, in accordance with some example embodiments. At 412, the PGW 124 may send to a charging system, such as OCS 130, a request to check whether that the session being established is authorized to use rating groups, including the rating group associated to the unlicensed access, in accordance with some example embodiments. At 414, the charging system may authorize the session, in accordance with some example embodiments. At 416, a session answer may be sent to the SGW 124 indicating whether or not the session is authorized, and/or whether the "split bearer" option disclosed herein (e.g., at 400/499) is authorized, in accordance with some example embodiments. The context set up request provided, at 417, to the base station 110 may also include an indication that the split bearer is allowed.

At 452, the PGW 126 may create counter identifiers for downlink traffic sent over an access type such as the unlicensed access type based the corresponding rating groups in the PCC rules, when the "split bearer" option is authorized, in accordance with some example embodiments. For example, PGW 126 may create for a given flow and PDN connection, a counter identifier associated to the unlicensed rating group for metering unlicensed traffic.

At 455, downlink traffic may be received by the PGW 126, in accordance with some example embodiments.

At 474, the PGW 126 may identify that a downlink packet in a given flow is governed by a PCC rule associated with a counter identifier, and insert this counter identifier, as noted above, into the downlink traffic packets, in accordance with some example embodiments. The PGW 126 may also insert at 474 in the downlink packet, the access type the counter identifier relates to and/or the measurement type indicating whether volume and/or amount of packets is to be measured, in accordance with some example embodiments. For example, each counter identifier may have a corresponding access type and/or measurement or reporting type as well. At 460, the connection to a user equipment may be established with access network in "split bearer" mode, so the attachment may be signaled at 424 as complete, in accordance with some example embodiments. The connection may carry downlink traffic to the user equipment and/or uplink traffic from the user equipment. At 465, uplink traffic may be received by the base station 110, in accordance with some example embodiments. At 467, a network node such as the base station 110 may insert into the uplink packet, the access type over which the packet is received (e.g., by inserting "access type unlicensed" as noted above). At 469, the traffic may be provided to the PGW 126, in accordance with some example embodiments.

At 470, the PGW 126 may have for the same service data flow, counters associated to one access type, and counters associated to another access type, in accordance with some example embodiments. For example, the PGW 126 may maintain counters for the licensed traffic and counters for the unlicensed traffic. The PGW 126 may increment for each packet of a given service data flow received with the access type identifier, the counts associated to the access type for the service data flow. For example, the PGW 126 may increment for each packet of a given service data flow received with an access type identifier, the counts associated to the access type for this service data flow. At 472, upon reception of the attach complete message, the MME may send a modify bearer request message to the serving gateway. At 475, the downlink traffic may be received by the base station 110, in accordance with some example embodiments. At 480, the base station 110 (or access point 112) may increment the counters identified by the counter identifiers included in the packet, when the packet is sent over the access type associated with the counter identifier, indicated in the packet, in accordance with some example embodiments. In some example embodiments, there may be provided a switched bearer option. FIGs. 5A-5C described below refer to this switched bearer option.

In the case of the switched bearer option, the access network may provide dual connectivity using separate bearers established between the access network and the core network wherein the bearers are entirely served by a single access technology (and thus by only one of the master base station or secondary base station depicted in FIG. 5A). FIG. 5A depicts a block diagram of a system including a core network including a core network node such as SGW 124 and the access network 510, which may include a master base station (labeled MeNB) 110 and a secondary base station 112 (labeled SeNB) configured to provide dual connectivity to at least one user equipment. In the example of FIG. 5 A, one bearer is provided per access type, such that the MeNB 110 has a bearer for a first access type and the SeNB has another bearer for the second access type.

FIG. 5B depicts a signaling diagram 500 for the PGW to be able to prevent the access network from using dual connectivity in a split bearer mode (e.g., by sending an indication that a split bearer is not allowed at the access network), in accordance with some example. FIG. 5B depicts the process used when a PDN connection set-up is performed simultaneously with an attach procedure. A similar mechanism may occur for a stand-alone PDN connection set-up. A similar indication (that a split bearer is not allowed) may also be sent in other signaling request from the PGW such as the dedicated bearer creation request. In case of a 5G core, the SMF may send an indication that a split bearer is not allowed via N2 signaling sent to the access network via the AMF.

At 502, the PGW 126 may determine that a split bearer is not allowed at the access network, in accordance with some example embodiments. This may be for example related with operator policies or due to the capability of the PGW. When this is the case, the PGW 126 may send, at 504 A, a message such as a session response including an indication that dual connectivity in the split bearer mode is not allowed at the access network. The session response at 504A may be provided (e.g., sent) to the SGW 124, which may, at 504B, send to the MME 120 the session creation response including the indication that the split bearer mode is not allowed, and the MME 120 may provide, at 504C, to the base station 110 an initial context set up including the indication that the split bearer mode is not allowed. As such, the base station 110 knows at 506 that a split bearer mode is not allowed for this bearer and that dual connectivity can only be used in switched bearer mode as described above at for example FIG. 4. The initial context set up request 504C may include core network requests to create one or more radio access bearers (RABs). The RAN 110 may indicate the access type of the bearers it has established (e.g., in the bearer activation information sent) within the initial context setup response message at 508A. This information may then be forwarded to other nodes such as the SGW 124, and PGW 126 at 508B-C. At 510, the indicated access type traffic may be carried to SGW 124. In the example of FIG. 5B, the SGW 124 may count the downlink and uplink traffic under the received/indicated access type for the bearer, and the PGW 126 may also count at 520 the downlink and uplink traffic under the received/indicated access type for this bearer. In other words, the indicated access type at 508A-C may enable the SGW, PGW, and/or other network nodes to count the packets for that access type.

FIG. 5C depicts another signaling diagram 599, in accordance with some example embodiments.

At 530 the access network decides to use dual connectivity in the switched mode, in accordance with some example embodiments, in order to switch a bearer between access types (e.g., between the licensed spectrum and the unlicensed spectrum or between different access types). When this is the case, the base station 110 may send to the MME 120, at 532A, a message such as an enhanced-radio access bearer (RAB) modification indication carrying, in accordance with some example embodiments, a new indication of the access type supporting the RAB. At 532B, the MME may add (that configures the SGW with the new transport address to be associated with the RAB) the indication of the new access type supporting the RAB. As it has received an indication of change of access type for the RAB, the SGW may initiate a modify bearer request (MBR) 532C towards the PGW. This MBR may carry the indication of the new access type supporting the Bearer. As a consequence, the SGW may count the downlink and uplink traffic under the received new access type, and the PGW may count at 540 the downlink and uplink traffic under the new/changed access type. In other words, the change to the indicated access type at 532A-C may enable the SGW, PGW, and/or other network nodes to count the packets for that access type.

FIG. 6 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments. The apparatus 10 may represent a user equipment, although portions of the apparatus 10 may be used to provide a base station 110 or wireless access point 112. Moreover, some of the nodes, such as the PGW, SGW, MME, and/or the like, may include at least one processor and at least one memory including program code to provide the operations disclosed herein with respect to those nodes.

The apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively transmit and receive antennas may be separate. The apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus. Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory. The processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 6 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.

The apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like.

For example, the apparatus 10 and/or a cellular modem therein may be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP) and/or the like. For example, the apparatus 10 may be capable of operating in accordance with 2G wireless communication protocols IS- 136, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-95, Code Division Multiple Access, CDMA, and/or the like. In addition, for example, the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division- Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed.

It is understood that the processor 20 may include circuitry for implementing audio/video and logic functions of apparatus 10. For example, the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the apparatus 10 may be allocated between these devices according to their respective capabilities. The processor 20 may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the processor 20 may include functionality to operate one or more software programs, which may be stored in memory. In general, processor 20 and stored software instructions may be configured to cause apparatus 10 to perform actions. For example, processor 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the apparatus 10 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, and/or the like. Apparatus 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20. The display 28 may, as noted above, include a touch sensitive display, where a user may touch and/or gesture to make selections, enter values, and/or the like. The processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like. The processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like. The apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices. As shown in FIG. 6, apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data. For example, the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The apparatus 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth™ Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and/or any other short-range radio technology. Apparatus 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example. The apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber. In addition to the SIM, the apparatus 10 may include other removable and/or fixed memory. The apparatus 10 may include volatile memory 40 and/or non-volatile memory 42. For example, volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like. Non-volatile memory 42, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may include a cache area for temporary storage of data. At least part of the volatile and/or non-volatile memory may be embedded in processor 20. The memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. In the example embodiment, the processor 20 may be configured using computer code stored at memory 40 and/or 42 to control and/or provide one or more aspects disclosed herein (see, for example, process 200, 300, 400, 499, 500, and/or 599).

Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware may reside on memory 40, the control apparatus 20, or electronic components, for example. In some example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer- readable media. In the context of this document, a "computer-readable medium" may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 6, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is a more accurate count of split traffic carried via a an unlicensed spectrum.

The subject matter described herein may be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. For example, the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that may include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein.

Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations may be provided in addition to those set forth herein. Moreover, the implementations described above may be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. Other embodiments may be within the scope of the following claims.

If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Although various aspects of some of the embodiments are set out in the independent claims, other aspects of some of the embodiments comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes example embodiments, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of some of the embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term "based on" includes "based on at least." The use of the phase "such as" means "such as for example" unless otherwise indicated.

Claims

1. An apparatus comprising:

at least one processor; and

at least one memory including program code which when executed causes the apparatus to at least:

receive at least one downlink packet including at least one counter identifier; and

increment at least one counter associated with the at least one counter identifier, when the at least one downlink packet is sent to a user equipment over an access type associated with the at least one counter identifier.

2. The apparatus of claim 1, wherein the access type is indicated by the at least one counter identifier, the at least one counter identifier further comprising an access type identifier.

3. The apparatus of any of claims 1 and 2, wherein the at least one downlink packet includes a measurement type.

4. The apparatus of claim 3, wherein the measurement type indicates whether the increment is based on data volume and/or amount of packets.

5. The apparatus of any of claims 1 through 4, wherein the access type comprises an unlicensed access type.

6. The apparatus of any of claims 1 through 5, wherein the access type comprises an E-UTRAN access type.

7. The apparatus of any of claims 1 through 6, wherein the access type comprises a fifth generation radio access type.

8. The apparatus of any of claims 1 through 7, wherein the apparatus is further caused to at least report a counter value to a core network node to enable the core network node to determine the data volume and/or the amount of packets for a flow including the at least one downlink packet carried by the access type to the user equipment.

9. The apparatus of any of claims 1 through 8, wherein the apparatus is further caused to at least receive, from the core network node, at least one condition for reporting the counter value.

10. The apparatus of claim 1, wherein the apparatus is further caused to at least: receive, from the user equipment and over a corresponding access type, at least one uplink packet;

insert, in the at least uplink packet, an access type identifier indicative of the corresponding access type; and

send the at least one uplink packet including the access type identifier to a core network node.

11. The apparatus of claim 10, wherein the corresponding access type comprises an unlicensed access.

12. The apparatus of claim 10, wherein the corresponding access type comprises a licensed access.

13. The apparatus of claim 10, wherein the corresponding access type comprises an E-UTRAN access.

14. The apparatus of claim 10, wherein the corresponding access type comprises a fifth generation access.

15. The apparatus of any of claims 11 through 14, wherein the apparatus is further caused to at least receive, from the core network node, a request to insert the access type identifier in the at least uplink packet being sent to the core network.

16. The apparatus of any of claims 1 through 15, wherein the apparatus is further caused to at least receive report trigger information, when a session is created and/or a bearer is created.

17. The apparatus of claim 16, wherein the report trigger information comprises at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity.

18. An apparatus comprising:

at least one processor; and

receive at least one uplink packet including an access type identifier; and increment, based on the access type identifier of the received at least one uplink packet, at least one counter associated with the at least one uplink packet and the access type identifier.

19. The apparatus of claim 18, wherein the at least one counter is incremented based on a data volume and/or an amount of packets.

20. The apparatus of any of claims 18 through 19, wherein the apparatus is further caused to at least:

receive at least one downlink packet; and

insert, in the at least one downlink packet being forwarded towards a user equipment, at least one counter identifier.

21. The apparatus of claim 20, wherein the apparatus is further caused to at least insert, in the at least one downlink packet being forwarded towards the user equipment, the access type identifier associated with the at least one counter identifier.

22. The apparatus of any of claims 20 through 21, wherein the apparatus is further caused to at least insert a measurement type associated with the at least one counter identifier.

23. The apparatus of any of claims 20 through 22, wherein the apparatus is further caused to at least insert an identity of the apparatus associated with the at least one counter identifier.

24. The apparatus of any of claims 20 through 23, wherein the apparatus is further caused to at least send report trigger information for the access network, when a session connection is created and/or at a bearer is created.

25. The apparatus of claim 24, wherein the report trigger information comprises at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity.

26. The apparatus of any of claims 18 through 25, wherein the apparatus is further caused to at least receive, from another node, at least one policy and charging control rule for a service data flow including at least one rating group associated with an access type.

27. The apparatus of any of claims 18 through 26, wherein the at least one counter is associated to the at least one rating group and access type and/or associated to the at least one rating group, access type and service identifier of the received at least one policy and charging control rule for the service data flow the at least one uplink packet is associated with.

28. The apparatus of any of claims 18 through 27, wherein the at least one counter is associated to a bearer or a quality of service flow related to the service data flow handled by the apparatus.

29. An apparatus comprising:

at least one processor; and

send, to a core network node via signaling, an access type identifier representing the access type carrying the traffic, when the apparatus operates bearer and/or quality of service flow switching from an access type to another.

30. The apparatus of claim 29, wherein the apparatus is further caused to receive, from the core network node, an indication that a split bearer and/or split quality of service flow mode of operation is not allowed.

31. The apparatus of any of claims 29 and 30, wherein the access type identifier comprises an identifier of an access type used to convey at least one downlink packet to a user equipment.

32. An apparatus comprising:

at least one processor; and

send an indication that a split bearer and/or a split quality of service flow mode of operation is not allowed at the access network.

33. The apparatus of claim 32, wherein the apparatus is further caused to at least receive, from the access network, an access type identifier representative of an access type used to carry, from and/or to the user equipment, the traffic within a bearer and/or a quality of service flow.

34. The apparatus of claim 33, wherein the apparatus is further caused to at least forward to another core network entity the access type identifier received from the access network.

35. A method comprising :

receiving at least one downlink packet including at least one counter identifier; and incrementing at least one counter associated with the at least one counter identifier, when the at least one downlink packet is sent to a user equipment over an access type associated with the at least one counter identifier.

36. The method of claim 35, wherein the access type is indicated by the at least one counter identifier, the at least one counter identifier further comprising an access type identifier.

37. The method of any of claims 35 and 36, wherein the at least one downlink packet includes a measurement type.

38. The method of claim 37, wherein the measurement type indicates whether the increment is based on data volume and/or amount of packets.

39. The method of any of claims 35 through 38, wherein the access type comprises an unlicensed access type.

40. The method of any of claims 35 through 39, wherein the access type comprises an E-UTRAN access type.

41. The method of any of claims 35 through 40, wherein the access type comprises a fifth generation radio access type.

42. The method of any of claims 35 through 41, further comprising: reporting a counter value to a core network node to enable the core network node to determine the data volume and/or the amount of packets for a flow including the at least one downlink packet carried by the access type to the user equipment.

43. The method of any of claims 35 through 42, further comprising: receiving, from the core network node, at least one condition for reporting the counter value.

44. The method of claim 35, further comprising:

receiving, from the user equipment and over a corresponding access type, at least one uplink packet;

inserting, in the at least uplink packet, an access type identifier indicative of the corresponding access type; and

sending the at least one uplink packet including the access type identifier to a core network node.

45. The method of claim 44, wherein the corresponding access type comprises an unlicensed access.

46. The method of claim 44, wherein the corresponding access type comprises a licensed access.

47. The method of claim 44, wherein the corresponding access type comprises an E-UTRAN access.

48. The method of claim 44, wherein the corresponding access type comprises a fifth generation access.

49. The method of any of claims 44 through 48, further comprising: receiving, from the core network node, a request to insert the access type identifier in the at least uplink packet being sent to the core network.

50. The method of any of claims 35 through 49, further comprising receiving report trigger information, when a session is created and/or a bearer is created.

51. The method of claim 50, wherein the report trigger information comprises at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity.

52. An apparatus comprising:

means for receiving at least one downlink packet including at least one counter identifier; and

means for incrementing at least one counter associated with the at least one counter identifier, when the at least one downlink packet is sent to a user equipment over an access type associated with the at least one counter identifier.

53. The apparatus of claim 52 further comprising means for performing any of claims 36 through 51.

54. A non-transitory computer-readable storage medium including program code which when executed causes operations comprising:

55. A method comprising :

receiving at least one uplink packet including an access type identifier; and incrementing, based on the access type identifier of the received at least one uplink packet, at least one counter associated with the at least one uplink packet and the access type identifier.

56. The method of claim 55, wherein the at least one counter is incremented based on a data volume and/or an amount of packets.

57. The method of any of claims 55 through 56, further comprising:

receiving at least one downlink packet; and

inserting, in the at least one downlink packet being forwarded towards a user equipment, at least one counter identifier.

58. The method of claim 57, further comprising: inserting, in the at least one downlink packet being forwarded towards the user equipment, the access type identifier associated with the at least one counter identifier.

59. The method of any of claims 57 through 58, further comprising: inserting a measurement type associated with the at least one counter identifier.

60. The method of any of claims 57 through 59, further comprising: inserting an identity of the apparatus associated with the at least one counter identifier.

61. The method of any of claims 57 through 59, further comprising: sending report trigger information for the access network, when a session connection is created and/or at a bearer is created.

62. The method of claim 61, wherein the report trigger information comprises at least one of the following parameters: a time reached threshold, a volume reached threshold, an amount of packets reached threshold, and/or a periodicity.

63. The method of any of claims 55 through 62, further comprising: receiving, from another node, at least one policy and charging control rule for a service data flow including at least one rating group associated with an access type.

64. The method of any of claims 55 through 63, wherein the at least one counter is associated to the at least one rating group and access type and/or associated to the at least one rating group, access type and service identifier of the received at least one policy and charging control rule for the service data flow the at least one uplink packet is associated with.

65. The method of any of claims 55 through 64, wherein the at least one counter is associated to a bearer or a quality of service flow related to the service data flow handled by the apparatus.

66. An apparatus comprising:

means for receiving at least one uplink packet including an access type identifier; and means for incrementing, based on the access type identifier of the received at least one uplink packet, at least one counter associated with the at least one uplink packet and the access type identifier.

67. The apparatus of claim 65 further comprising means for performing any of claims 56 through 65.

68. A non-transitory computer-readable storage medium including program code which when executed causes operations comprising: receiving at least one uplink packet including an access type identifier; and incrementing, based on the access type identifier of the received at least one uplink packet, at least one counter associated with the at least one uplink packet and the access type identifier.

69. A method comprising

sending, to a core network node via signaling, an access type identifier representing the access type carrying the traffic, when the apparatus operates bearer and/or quality of service flow switching from an access type to another.

70. The method of claim 69, further comprising:

receiving, from the core network node, an indication that a split bearer and/or split quality of service flow mode of operation is not allowed.

71. The method of any of claim 69 and 70, wherein the access type identifier comprises an identifier of an access type used to convey at least one downlink packet to a user equipment.

72. An apparatus comprising:

means for sending, to a core network node via signaling, an access type identifier representing the access type carrying the traffic, when the apparatus operates bearer and/or quality of service flow switching from an access type to another.

73. The apparatus of claim 72 further comprising means for performing any of claims 70 through 71.

74. A non-transitory computer-readable storage medium including program code which when executed causes operations comprising:

75. A method comprising :

sending an indication that a split bearer and/or a split quality of service flow mode of operation is not allowed at the access network.

76. The method of claim 75, further comprising: receiving, from the access network, an access type identifier representative of an access type used to carry, from and/or to the user equipment, the traffic within a bearer and/or a quality of service flow.

77. The method of claim 76, further comprising: forwarding to another core network entity the access type identifier received from the access network.

78. An apparatus comprising:

mean for sending an indication that a split bearer and/or a split quality of service flow mode of operation is not allowed at the access network.

79. The apparatus of claim 78 further comprising means for performing any of claims 76 through 77.

80. A non-transitory computer-readable storage medium including program code which when executed causes operations comprising: