Method and apparatus for adding notifications related with user equipment multicast group and leave

Methods, apparatuses and computer program products are described that facilitate sending and receiving notifications related to user equipment being added to or leaving a multicast group or multicast stream in a network. A method can include receiving, from a session controller, a request for reporting when protocol data unit (PDU) sessions are added to/removed from a downlink replication tree associated with an internet protocol multicast flow; determining whether said PDU session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow; and, in response to said determining, transmitting a message to a session management function indicative of that said PDU session has been added to or removed from said downlink replication tree. The message can include an internet protocol address associated with a source of said added or removed multicast flow and/or the multicast destination of said internet protocol multicast flow.

BACKGROUND

Third generation partnership project (3GPP) 5thgeneration (5G) technology is a next generation of radio systems and network architecture that can deliver extreme broadband and ultra-robust, low latency connectivity. 5G technology improves a variety of telecommunication services offered to the end users and helps to support massive broadband that delivers gigabytes of bandwidth per second on demand for both the uplink and downlink transmissions. Next generation systems, which utilize the 5G architecture, utilize virtualized radio access network (RAN) functions and core network functions.

In general, a 5G network can provide data connectivity and services for internet protocol services, such as streaming television and provision of other streaming media to user devices. In some embodiments, such service provision can be provided via either roaming or non-roaming scenarios, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and charging, authentication and in general 5G System wide features e.g. SMS, Location Services, Emergency Services, as described herein. One concept used in 5G mobile networks, which is being defined in 3GPP Release 16 under the Parameters for N4 Session Management and is to be documented, for example but not limited to, in 3GPP technical specification (TS) 23.501, is the concept of supporting internet protocol television (IPTV) services, for instance for a 5G Residential Gateway (5G-RG or FN-RG) served by the 5G Core (5GC) such as an L3 device, and support for various IP PDU Session Types, support for an array of suitable wireless or wireline subscription receiving IP Multicast traffic, and/or support for devices including Residential Gateways but also support for devices other than Residential Gateways.

BRIEF SUMMARY

A method, apparatus, and computer program product are provided in accordance with certain example embodiments in order to facilitate the sending and receiving of notifications between components of the 5G System related to user equipment being added to or leaving a multicast group or multicast stream.

In one example embodiment, a method is provided that comprises receiving, from a session controller, a request for reporting when protocol data unit sessions are added to or removed from a downlink replication tree associated with an internet protocol multicast flow; determining whether a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow; and, in response to said determining, transmitting a message to a session management function indicative of that said protocol data unit session has been added to or removed from said downlink replication tree. In some embodiments, the message comprises an internet protocol address associated with a multicast destination of said internet protocol multicast flow. In some embodiments, the message comprises an internet protocol address associated with a source of said added or removed multicast flow and an internet protocol address associated with the multicast destination of said internet protocol multicast flow.

In another example embodiments, a method is provided that comprises causing a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow; receiving, from the user plane function, a message indicative of that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and forwarding the indication that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow to entities that have been requested to be notified of such an event. In some embodiments, causing may comprise causing transmission, to the user plane function, of a request or command that the user plane function reports when a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow. In some embodiments, the method can further comprise, in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening.

In yet another example embodiment, a method is provided that comprises receiving a message indicative of that a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and, in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening and which supports at least one of: storing information related to said particular internet protocol multicast channel in order to generate billing information or statistical information, and controlling one or more times during which a user device may receive said internet protocol multicast flow.

In still another example embodiment, an apparatus is provided that comprises means for receiving, from a session controller, a request for reporting when protocol data unit sessions are added to or removed from a downlink replication tree associated with an internet protocol multicast flow; means for determining whether a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow; and means for, in response to said determining, transmitting a message to a session management function indicative of that said protocol data unit session has been added to or removed from said downlink replication tree. In some embodiments, the message may comprise an internet protocol address associated with a multicast destination of said internet protocol multicast flow. In some embodiments, the message may comprise an internet protocol address associated with a source of said added or removed multicast flow and an internet protocol address associated with the multicast destination of said internet protocol multicast flow.

In another example embodiment, an apparatus is provided that comprises means for causing a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow; means for receiving, from the user plane function, a message indicative of that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and means for forwarding the indication that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow to entities that have been requested to be notified of such an event. In some embodiments, means for causing can comprise means for causing transmission, to the user plane function, of a request or command that the user plane function reports when a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow. In some embodiments, the apparatus can further comprise means for, in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening.

In yet example embodiment, an apparatus is provided that comprises means for receiving a message indicative of that a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and means for, in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening and which supports at least one of: storing information related to said particular internet protocol multicast channel in order to generate billing information or statistical information, and controlling one or more times during which a user device may receive said internet protocol multicast flow.

In another example embodiment, an apparatus is provided that comprises at least one processor and at least one memory including computer program code for one or more programs. In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to: receive, from a session controller, a request for reporting when protocol data unit sessions are added to or removed from a downlink replication tree associated with an internet protocol multicast flow; determine whether a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow; and in response to said determining, transmit a message to a session management function indicative of that said protocol data unit session has been added to or removed from said downlink replication tree. In some embodiments, the message can comprise an internet protocol address associated with a multicast destination of said internet protocol multicast flow. In some embodiments, the message can comprise an internet protocol address associated with a source of said added or removed multicast flow and an internet protocol address associated with the multicast destination of said internet protocol multicast flow.

In still another example embodiment, an apparatus is provided that comprises at least one processor and at least one memory including computer program code for one or more programs. In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to: cause a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow; receive, from the user plane function, a message indicative of that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and forward the indication that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow to entities that have been requested to be notified of such an event. In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: cause transmission, to the user plane function, of a request or command that the user plane function reports when a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow. In some embodiments, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: in response to receiving said message, determine from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening.

In yet another example embodiment, an apparatus is provided that comprises at least one processor and at least one memory including computer program code for one or more programs. In some embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to: receive a message indicative of that a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and, in response to receiving said message, determine from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening and which supports at least one of: storing information related to said particular internet protocol multicast channel in order to generate billing information or statistical information, and controlling one or more times during which a user device may receive said internet protocol multicast flow.

In yet another example embodiment, a computer program product is provided that comprises at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein. In some embodiments, the computer-executable program code instructions can comprise program code instructions configured, upon execution, to: receive, from a session controller, a request for reporting when protocol data unit sessions are added to or removed from a downlink replication tree associated with an internet protocol multicast flow; determine whether a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow; and, in response to said determining, transmit a message to a session management function indicative of that said protocol data unit session has been added to or removed from said downlink replication tree. In some embodiments, the message may comprise an internet protocol address associated with a multicast destination of said internet protocol multicast flow. In some embodiments, the message may comprise an internet protocol address associated with a source of said added or removed multicast flow and an internet protocol address associated with the multicast destination of said internet protocol multicast flow.

In another example embodiment, a computer program product is provided that comprises at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein. In some embodiments, the computer-executable program code instructions can comprise program code instructions configured, upon execution, to: cause a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow; receive, from the user plane function, a message indicative of that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and forward the indication that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow to entities that have been requested to be notified of such an event. In some embodiments, the program code instructions are further configured, upon execution, to: cause transmission, to the user plane function, of a request or command that the user plane function reports when a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow. In some embodiments, the program code instructions can be further configured, upon execution, to, in response to receiving said message, determine from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening.

In still another example embodiment, a computer program product is provided that comprises at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein. In some embodiments, the computer-executable program code instructions can comprise program code instructions configured, upon execution, to: receive a message indicative of that a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow; and, in response to receiving said message, determine from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening and which supports at least one of: storing information related to said particular internet protocol multicast channel in order to generate billing information or statistical information, and controlling one or more times during which a user device may receive said internet protocol multicast flow.

DETAILED DESCRIPTION

Additionally, as used herein, the term ‘circuitry’ refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term ‘circuitry’ also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As defined herein, a “computer-readable storage medium,” which refers to a physical storage medium (e.g., volatile or non-volatile memory device), may be differentiated from a “computer-readable transmission medium,” which refers to an electromagnetic signal.

Under the planned and/or forthcoming 5G system, at least some of the hurdles to implementation and practical application at scale include the complexity of naming and system architecture in the 5G System, the varied array of parameters for L1, the dual connectivity options, base station naming, and the like. In terms of resource and service delivery to user equipment, the appropriate parameters and notifications related to connectivity and streaming content delivery can lead to a wired and/or wireless network that covers a broader scope and more types of entities.

In the context of wireline access to the 3GPP 5G Core (5GC), such as described in 3GPP TS 23.316, Release 16, Residential Gateways (RGs) can be served by the 5GC, some of which can include but are not limited to RGs, 5G Residential Gateways, such as a RG that has been modified for the sake of accessing to 5GC, 5G-RG that acts as a full 3GPP User Equipment that is assumed to terminate 3GPP NAS signaling and to support URSP policy rules sent by the 5GC to User Equipment, a Fixed Network RG (FN-RG) that is un-modified for the sake of accessing the 5GC, a wireline access entity (W-AGF) terminates 3GPP NAS signaling (including the NAS signaling carrying URSP rules) on behalf of unmodified FN-RGs, and the like.

Referring now toFIGS. 1 and 2, the architecture for connecting a 5G-RG and FN-RG is illustrated. In some embodiments, the Y4 and Y5 termination at RG side may correspond to any wireline technology (e.g., DSL, PON, Cable, etc.). As illustrated, the disclosed 5G-RG and FN-RG systems may be operable to support multiple services, such as IPTV. In some embodiments, IPTV can be defined as multimedia services, such as television, video, audio, textual media, graphics, data, combinations thereof, and the like that are delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity, and/or reliability. In some embodiments, usage of IP multicast may be an important or essential component of the delivery of IPTV content. In some embodiments, IPTV television channels or the like may be associated with an IP Multicast delivery. In some embodiments, the IPTV service may act as an AF, which can set authorization rights per user or group of users.

In some embodiments, the 5G system architecture may consist of some or all of the following network functions (NF): Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Data Network (DN), e.g. operator services, Internet access or 3rd party services, Unstructured Data Storage Function (UDSF), Network Exposure Function (NEF), Network Repository Function (NRF), Network Slice Selection Function (NSSF), Policy Control Function (PCF), Session Management Function (SMF), Unified Data Management (UDM), Unified Data Repository (UDR), User Plane Function (UPF), UE radio Capability Management Function (UCMF), Application Function (AF), User Equipment (UE), Next Generation-Radio Access Network (NG-RAN), 5G-Equipment Identity Register (5G-EIR), Network Data Analytics Function (NWDAF), and Charging Function (CHF). The 5G system architecture may further comprise the following network entities: Service Communication Proxy (SCP) and Security Edge Protection Proxy (SEPP).

Moreover, although the foregoing descriptions and the associated drawings describe certain example embodiments in the context of an improved 5G communication system, it should be appreciated that other communication systems may be provided by alternative embodiments without departing from the scope of the appended claims. Although 5G technology and 5G systems are employed herein, they are used in an illustrative and descriptive sense only and not for purposes of limitation.

According to some embodiments, the parameters for N4 session management can be used to monitor and control the functionality of the UPF as well as to inform the SMF about events occurring at the UPF, such as the joining or leaving of a user device from a media content stream. The N4 session management procedures defined in TS 23.502 will use the relevant parameters in the same way for all N4 reference points: the N4 Session Establishment procedure as well as the N4 Session Modification procedure provide the control parameters to the UPF, the N4 Session Release procedure removes all control parameters related to an N4 session, and the N4 Session Level Reporting procedure informs the SMF about events related to the PDU Session that are detected by the UPF.

The parameters over N4 reference point provided from SMF to UPF comprises an N4 Session ID and may also contain (i) Packet Detection Rules (PDR) that contain information to classify traffic (PDU(s)) arriving at the UPF; (ii) Forwarding Action Rules (FAR) that contain information on whether forwarding, dropping or buffering is to be applied to a traffic identified by PDR(s); (iii) Multi-Access Rules (MAR) that contain information on how to handle traffic steering, switching and splitting for a MA PDU Session; (iv) Usage Reporting Rules (URR) contains information that defines how traffic identified by PDR(s) shall be accounted as well as how a certain measurement shall be reported; (v) QoS Enforcement Rules (QER), that contain information related to QoS enforcement of traffic identified by PDR(s); (vi) Trace Requirements.

In some embodiments, the N4 Session ID is assigned by the SMF and uniquely identifies an N4 session. If the UPF indicated support of Trace, the SMF may activate a trace session during a N4 Session Establishment or a N4 Session Modification procedure. In that case it provides Trace Requirements to the UPF. The SMF may deactivate an on-going trace session using a N4 Session Modification procedure. There shall be at most one trace session activated per N4 Session at a time.

For the MA PDU Session, the SMF may add an additional access tunnel information during an N4 Session Modification procedure by updating MAR with addition of an FAR ID which refers to an FAR containing the additional access tunnel information for the MA PDU session for traffic steering in the UPF.

N4 Session Context is identified by an N4 Session ID. An N4 Session Context is generated by SMF and UPF respectively to store the parameters related to an N4 session, including N4 session ID, all PDRs, URRs, QERs and FARs or MARs used for this N4 session.

Table 1 describes the Packet Detection Rule (PDR) containing information required to classify a packet arriving at the UPF. Every PDR is used to detect packets in a certain transmission direction, e.g. UL direction or DL direction.

TABLE 1AttributeDescriptionCommentN4 Session IDIdentifies the N4 session associated to this PDR.NOTE 5.Rule IDUnique identifier to identify this rule.PrecedenceDetermines the order, in which the detectioninformation of all rules is applied.PacketSourceContains the values “access side”, “core side”,Combination of UE IP addressinterface“SMF”, “N6-LAN”, “5G VN internal”.(together with Network instance,if necessary), CN tunnel info,DetectionUE IP addressOne IPv4 address and/or one IPv6 prefixpacket filter set, application ID,Information.with prefix length (NOTE 3).Ethernet PDU SessionNOTE 4.NetworkIdentifies the Network instance associatedInformation and QFI are used forinstancewith the incoming packet.traffic detection.(NOTE 1)Source interface identifies theCN tunnel infoCN tunnel info on N3, N9 interfaces,interface for incoming packetsi.e. F-TEID.where the PDR applies, e.g. fromPacket FilterDetails see clause 5.7.6, TS 23.501.access side (i.e. up-link),Setfrom core side (i.e. down-link),Application IDfrom SMF, from N6-LANQoS Flow IDContains the value of 5QI or(i.e. the DN or the localnon-standardized QFI.DN), or from “5GEthernet PDURefers to all the (DL) EthernetVN internal” (i.e. local switch).Sessionpackets matching anInformationEthernet PDU session, as further described inclause 5.6.10.2 and in TS 29.244 [65].Framed RouteRefers to Framed Routes defined inDetails like all the combinationInformationclause 5.6.14.possibilities on N3, N9 interfacesare left for stage 3 decision.Outer header removalInstructs the UP function to removeAny extension header shall beone or more outer header(s) (e.g. IP +stored for this packet.UDP + GTP, IP + possiblyUDP, VLAN tag), from the incoming packet.Forwarding ActionThe Forwarding Action Rule ID identifies aRule ID (NOTE 2)forwarding action that can or shall be applied.Multi-Access Rule IDThe Multi-Access Rule ID identifies an(NOTE 2)action to be applied for handling forwardingfor a MA PDU Session.List of Usage ReportingEvery Usage Reporting Rule ID identifies aRule ID(s)measurement action that can or shall be applied.List of QoS EnforcementEvery QoS Enforcement Rule IDRule ID(s)identifies a QoS enforcement actionthat can or shall be applied.NOTE 1:Needed e.g. in case: UPF supports multiple DNN with overlapping IP addresses; UPF is connected to other UPF or AN node in different IP domains. UPF “local switch”, N6-based forwarding and N19 forwarding is used for different 5G LAN groups.NOTE 2:Either a FAR ID or a MAR ID is included, not both.NOTE 3:The SMF may provide an indication asking the UPF to allocate one IPv4 address and/or IPv6 prefix. When asking to provide an IPv6 Prefix the SMF provides also an IPv6 prefix length.NOTE 4:When in the architecture defined in clause 5.34, a PDR is sent over N16a from SMF to I-SMF, the Packet Detection Information may indicate that the I-SMF is to locally determine CN tunnel info in order to build the N4 PDR sent to the actual UPF controlled by the I-SMF. This is further defined in clause 5.34.6.NOTE 5:In the architecture defined in clause 5.34, the rules exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with a N16a association.

Table 2 describes the QoS Enforcement Rule (QER) that defines how a packet shall be treated in terms of bit rate limitation and packet marking for QoS purposes. All Packet Detection Rules that refer to the same QER share the same QoS resources, e.g. MFBR.

TABLE 2AttributeDescriptionCommentN4 Session IDIdentifies the N4 sessionassociated to this QERRule IDUnique identifier toidentify this information.QoS EnforcementAn identity allowing theIs used to correlate QoS Enforcement Rules forRule correlationUP function to correlateAPN-AMBR enforcement.ID (NOTE 1)multiple Sessions for thesame UE and APN.Gate statusInstructs the UP functionValues are: open, close, close after measurementUL/DLto let the flow pass or toreport (for termination action “discard”).block the flow.Maximum bitrateThe uplink/downlinkThis field may e.g. contain any one of:maximum bitrate to beAPN-AMBR (for a QER that is referenced by allenforced for the packets.relevant Packet Detection Rules of all PDNConnections to an APN) (NOTE 1).Session-AM BR (for a QER that is referenced by allrelevant Packet Detection Rules of the PDU Session)QoS Flow MBR (for a QER that is referenced by allPacket Detection Rules of a QoS Flow)SDF MBR (for a QER that is referenced by theuplink/downlink Packet Detection Rule of a SDF)Bearer MBR (for a QER that is referenced by allrelevant Packet Detection Rules of a bearer)(NOTE 1).Guaranteed bitrateThe uplink/downlinkThis field contains:guaranteed bitrateQoS Flow GBR (for a QER that is referenced by allauthorized for thePacket Detection Rules of a QoS Flow)packets.Bearer GBR (for a QER that is referenced by allrelevant Packet Detection Rules of a bearer)(NOTE 1).AveragingThe time duration overThis is for counting the packets receivedwindowwhich the Maximum andduring the time duration.Guaranteed bitrate shallbe calculated.Down-link flowFlow level packetFor UPF, this is for controlling thelevel markingmarking in the downlink.setting of the RQI in the encapsulationheader as described in clause 5.7.5.3.Packet rateNumber of packets perThis field contains any one of:(NOTE 1)time interval to bedownlink packet rate for Servingenforced.PLMN Rate Control (the QER isreferenced by all PDRs of the UEbelonging to PDN connections using CloT EPSOptimizations as described in TS 23.401 [26]).uplink/downlink packet rate for APNRate Control (the QER is referencedby all PDRs of the UE belongingto PDN connections to the same APN using CloTEPS Optimizations as described in TS 23.401 [26]).Note 1:At least these parameters may be used for interworking with EPC.

Table 3 describes the Usage Reporting Rule (URR) that defines how a packet shall be accounted as well as when and how to report the measurements.

TABLE 3AttributeDescriptionCommentN4 Session IDIdentifies the N4 session associated to this URRRule IDUnique identifier to identify this information.Used by UPF when reportingusage.Reporting triggersOne or multiple of the events can be activatedApplicable events include:for the generation and reporting of the usageStart/stop of traffic detectionreport.with/without applicationinstance identifier and deducedSDF filter reporting; Deletion oflast PDR for a URR; Periodicmeasurement thresholdreached; Volume/Time/Eventmeasurement thresholdreached; Immediate reportrequested; Measurement ofincoming UL traffic;Measurement of discarded DLtraffic; MAC address reportingin the UL traffic; unknowndestination MAC/IP address.PeriodicDefines the point in time for sending a periodicThis allows generation of periodicmeasurementreport for this URR (e.g. time of day).usage report for e.g. offlinethresholdcharging.It can also be used for realizing theMonitoring time of the usagemonitoring feature.It can also be used for realizing theQuota-Idle-Timeout, i.e. to enablethe CP function to check whetherany traffic has passed during thistime.VolumeValue in terms of uplink and/or downlink and/ormeasurementtotal byte-count when the measurement reportthresholdis to be generated.Time measurementValue in terms of the time duration (e.g. inthresholdseconds) when the measurement report is to begenerated.Event measurementNumber of events (identified according to athresholdlocally configured policy) after which themeasurement report is to be generated.Inactivity detectionDefines the period of time after which the timeTimer corresponding to thistimemeasurement shall stop, if no packets areduration is restarted at the end ofreceived.each transmitted packet.Event basedPoints to a locally configured policy which isreportingidentifies event(s) trigger for generating usagereport.Linked URR ID(s)Points to one or more other URR ID.This enables the generation of acombined Usage Report for thisand other URRs by triggering theirreporting. See clause 5.2.2.4,TS 29.244 [65].MeasurementIndicates the method for measuring the networkMethodresources usage, i.e. the data volume, duration,combined volume/duration, or event.MeasurementIndicates specific conditions to be applied forIt is used to request:informationmeasurementsmeasurement before QoSenforcement, and/orto pause or set to active ameasurement as for the Pauseof charging described inclause 4.4.4 of TS 23.502 [3],and/orto request reduced reporting forapplication start/stop events.

Table 4 describes the Forwarding Action Rule (FAR) that defines how a packet shall be buffered, dropped or forwarded, including packet encapsulation/decapsulation and forwarding destination.

TABLE 4AttributeDescriptionCommentN4 Session IDIdentifies the N4 session associated to thisNOTE 9.FAR.Rule IDUnique identifier to identify this information.ActionIdentifies the action to apply to the packetIndicates whether the packet is to beforwarded, duplicated, dropped orbuffered.When action indicates forwarding orduplicating, a number of additionalattributes are included in the FAR.For buffering action, a Buffer ActionRule is also included.Network instanceIdentifies the Network instance associatedNOTE 8.(NOTE 2)with the outgoing packet (NOTE 1).Destination interfaceContains the values “access side”, “coreIdentifies the interface for outgoing(NOTE 3)side”, “SMF”, “N6-LAN”, “5G VN internal”packets towards the access side(NOTE 7)or “5G VN N19.(i.e. down-link), the core side (i.e.up-link), the SMF, the N6-LAN (i.e.the DN or the local DN), to 5G VNinternal (i.e. local switch), or to 5GVN N19 (i.e. N19 interface).Outer header creationInstructs the UP function to add an outerContains the CN tunnel info, N6(NOTE 3)header (e.g. IP + UDP + GTP + QFI, VLANtunnel info or AN tunnel info of peertag), IP + possibly UDP to the outgoingentity (e.g. NG-RAN, another UPF,packet.SMF, local access to a DNrepresented by a DNAI) (NOTE 8).Any extension header stored for thispacket shall be added.May contain a list of outer headersfor forwarding multicast data. Thiscan be used to e.g. support 5G VNgroupSend end marker packet(s)Instructs the UPF to construct end markerThis parameter should be sent(NOTE 2)packet(s) and send them out as describedtogether with the “outer headerin clause 5.8.1.creation” parameter of the new CNtunnel info.Transport level markingTransport level packet marking in theNOTE 8.(NOTE 3)uplink and downlink, e.g. setting theDiffServ Code Point.Forwarding policyReference to a preconfigured trafficContains one of the following(NOTE 3)steering policy or http redirectionpolicies identified by a TSP ID:(NOTE 4).an N6-LAN steering policy to steerthe subscriber's traffic to theappropriate N6 service functionsdeployed by the operator, ora local N6 steering policy toenable traffic steering in the localaccess to the DN according to therouting information provided by anAF as described in clause 5.6.7.or a Redirect Destination and valuesfor the forwarding behaviour(always, after measurement report(for termination action “redirect”)).Request for Proxying in UPFIndicates that the UPF shall perform ARPApplies to the Ethernet PDUproxying and/or IPv6 NeighbourSession type.Solicitation Proxying as specified inclause 5.6.10.2.Container for headerContains information to be used by theOnly relevant for the uplink direction.enrichmentUPF for header enrichment.(NOTE 2)Buffering Action RuleReference to a Buffering Action Rule ID(NOTE 5)defining the buffering instructions to beapplied by the UPF(NOTE 6)NOTE 1:Needed e.g. in case:UPF supports multiple DNN with overlapping IP addresses;UPF is connected to other UPF or NG-RAN node in different IP domains;UPF “local switch” and N19 forwarding is used for different 5G LAN groups.NOTE 2:These attributes may be required for FAR action set to forwarding.NOTE 3:These attributes may be required for FAR action set to forwarding or duplicating.NOTE 4:The TSP ID is preconfigured in the SMF and included in the FAR according to the description in clauses 5.6.7 and 6.1.3.14 of 23.503 for local N6 steering and 6.1.3.14 of 23.503 for N6-LAN steering. The TSP ID action is enforced before the Outer header creation actions.NOTE 5:This attribute is present for FAR action set to buffering.NOTE 6:The buffering action rule is created by the SMF and associated with the FAR in order to apply a specific buffering behaviour for DL packets requested to be buffered, as described in clause 5.8.3 and clause 5.2.4 in TS 29.244.NOTE 7:The use of “5G VN internal” instructs the UPF to send the packet back for another round of ingress processing using the active PDRs pertaining to another N4 session of the same 5G VN group.NOTE 8:When in architectures defined in clause 5.34, a FAR is sent over N16a from SMF to I-SMF, the FAR sent by the SMF may indicate that the I-SMF is to locally determine the value of this attribute in order to build the N4 FAR rule sent to the actual UPF controlled by the I-SMF. This is further defined in clause 5.34.6.NOTE 9:In the architecture defined in clause 5.34, the rules exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with a N16a association.

The UPF sends the usage report to inform the SMF about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the usage report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final usage report is sent for a URR when it is no longer active, i.e. either the URR is removed or all the references to this URR in any of the Packet Detection Rules belonging to the N4 session.

In some embodiments, attributes that can be included in the usage report may include, but are not limited to, one or more of the attributes in Table 5.

TABLE 5AttributeDescriptionCommentN4 Session IDUniquely identifies a session.Identifies the N4 sessionassociated to this Usage ReportRule IDUniquely identifies the Packet Detection RulePacket Detection Rule is onlyor Usage Reporting Rule within a sessionindicated when Reporting triggerwhich triggered the report.is Detection of 1st DL packet fora QoS Flow or Start/stop oftraffic detection.Usage Reporting Rule isindicated for all other Reportingtriggers.Reporting triggerIdentifies the trigger for the usage report.Applicable values are:Detection of 1st DL packet for aQoS Flow; Start/stop of trafficdetection with/withoutapplication instance identifierand deduced SDF filterreporting; Deletion of last PDRfor a URR; Periodicmeasurement thresholdreached; Volume/Time/Eventmeasurement thresholdreached; Immediate reportrequested; Measurement ofincoming UL traffic;Measurement of discarded DLtraffic; MAC address reporting inthe UL traffic; reporting ofunknown destination MAC/IPaddress.Start timeProvides the timestamp, in terms of absoluteNot sent when Reporting triggertime, when the collection of the informationis Start/stop of traffic detection.provided within Usage-Information is started.End timeProvides the timestamp, in terms of absoluteNot sent when Reporting triggertime, when the information provided withinis Start/stop of traffic detection.Usage-Information is generated.Measurement informationDefines the measured volume/time/events forDetails refer to TS 29.244 [65].this URR.

Table 6 describes the Multi-Access Rule (MAR) that includes the association to the two FARs for both 3GPP access and non-3GPP access in the case of supporting ATSSS.

In some embodiments, the Registration Procedure can be used to register to 5GS and the PDU Session Establishment Procedure is used to establish the PDU Session used for IPTV Service. In some embodiments, the IPTV Access Procedure may, depending on the deployment, be used to access the IPTV network, e.g., completing the IPTV Authentication and IP allocation function. In some embodiments, a Unicast/Multicast Packets transmission procedure may specify how to transmit unicast/multicast packets related with IPTV service over 5GCS.

In some embodiments, a 5G-RG can perform a Registration procedure, such as described in TS 23.502. In some embodiments, the user equipment may be replaced by 5G-RG. In some embodiments, the 5G-RG may perform a PDU Session establishment procedure, such as described in TS 23.502. In some embodiments, the 5G-RG may indicate within the Protocol Configuration Options element that the UE requests to obtain the IPv4 address with DHCPv4. In some embodiments, the 5G-RG may or shall establish the IP-based PDU Session with a specific DNN for IPTV network. In some embodiments, the PCF may or shall provide PCC Rules, e.g., including information related to IPTV Service. In some embodiments, the SMF may send notifications and/or requests to the UPF acting as PSA N4 rules such as PDR, FAR, or the like that relate with allowed IPTV service for the PDU Session; such as the N4 rules further described herein.

In some embodiments, the corresponding PDR may refer to IP Multicast Addressing information related with allowed IPTV services for the PDU Session. In the case Source Specific Multicast is configured to be used on the PDU Session, both IP Multicast address and Source IP address shall be used to identify the TV services allowed on the PDU Session.

In some embodiments, a set of N4 rules may or shall be sent by the SMF for IP Multicast traffic related with an allowed IPTV service may correspond to, for UL traffic (Internet Group Management Protocol; hereinafter “IGMP”), a PDR identifying the IGMP Join together with the corresponding IP Multicast Addressing information, a FAR with an “IP Multicast Router Accept” action, and/or possibly a URR with a Reporting Trigger set to “IGMP reporting”.

In some embodiments, for DL traffic, actual IP Multicast traffic may be related to or comprise a PDR identifying the IP Multicast Addressing information, a FAR asking to add outer header=GTP-u tunnel related with the PDU Session, and/or a QER indicating the target QoS Towards the RG. In some embodiments, the interactions between STB and 5G-RG are described in but not limited by Broadband Forum (hereinafter “BBF”) specification TR-124, entitled “Functional Requirements for Broadband Residential Gateway Devices,” the entire contents of which are hereby incorporated herein by reference in their entirety for all purposes.

In case of IPTV network access control based on the DHCP procedure, 5G-RG is configured to retrieve the IP address for IPTV service via DHCP. The DHCP procedure described in TS 23.501 is carried out. In some embodiments, when the SMF receives the Uplink DHCP message, the SMF may be configured to insert the IPTV access control information as received in subscription data from UDM to the uplink DHCP message, e.g. subscriber ID. In some embodiments, the IPTV access control information such as the subscriber ID can be represented by and/or include a line ID, such as described in Internet Engineering Task Force (IETF) Request For Comments (RFC) 3046 the entire contents of which are hereby incorporated herein by reference in their entirety for all purposes, or any other identifier which can be used to identify the IPTV subscriber. This is based on IPTV deployment and 3GPP doesn't define the IPTV access control information subscriber ID that the SMF copies from subscription data to DHCP signaling.

In some embodiments, the interactions between STB and 5G-RG is going to be specified in BBF TR-124 and not described in further detail herein. In some embodiments, the interactions among the IPTV network is out of 3GPP scope and not described in this procedure.

In some embodiments, a 5GS can support Unicast Service from IPTV network directly.

In order to obtain the multicast service from IPTV network, the Multicast Packets transmission procedure should be performed.

The SMF sends to UPF N4 rules such as PDR, FAR, and/or the like.

1. The 5G-RG send an IGMP Join message via the user plane.

2. When UPF detects the IGMP Join, the UPF may identify the IGMP Join packets based on PDR received over N4 as described in 3GPP TS 23.316, clause 4.6.3 and handle the IGMP Join accordingly based on FAR as described in 3GPP TS 23.316, clause 4.6.4. An example is given as below:If the IP Multicast Addressing information included in the IGMP Join message is allowed to be accessed via the PDU Session, the UPF shall add the PDU Session to the requested multicast group.If the IP Multicast Addressing information included in the IGMP Join message is not allowed to be accessed via the PDU Session, the UPF shall drop the IGMP Join message.

The UPF acts as a Multicast Router as defined in IETF RFC 2236: “Internet Group Management Protocol, Version 2 and IETF RFC 3376: “Internet Group Management Protocol, Version 3”. This may include following actions:if the IGMP Join message is the first IGMP request the UPF has received about the target IP multicast traffic (IP Multicast Addressing information): the UPF exchanges N6 signaling such as PIM (Protocol-Independent Multicast) in order to connect to the N6 multicast distribution tree related with this IP multicast traffic; This ensures that the UPF receives the DL multicast traffic.The IP multicast related signaling protocol used on N6 (e.g. Sparse Mode PIM-SM) to be supported over N6 is defined by local policies on the UPF.

3-4. When the UPF receives multicast packets from multicast server in IPTV network, the UPF select the PDU Session(s) where to transmit the multicast packets based on the multicast group, constructed in step 2.

In some embodiments, the interactions between STB and 5G-RG are specified in BBF TR-124 and are not described in further detail herein.

To create a new request, the AF invokes a Nnef_IPTV_configuration service operation. The request contains the Multicast Access Control List, and a GPSI, or an External Group Id, DNN, S-NNSAI, AF Transaction Id and may contain a DNN and/or a S-NNSAI. To update or remove an existing request, the AF invokes Nnef_IPTV_configuration_Update or Nnef_IPTV_configuration_Delete service operation providing the corresponding AF Transaction.

2. The AF sends its request to the NEF. The NEF ensures the necessary authorization control, including throttling of AF requests and mapping from the information provided by the AF into information needed by the 5GC.

3. (in the case of Nnef_IPTV_configuration_Create or Update): The NEF stores the AF request information in the UDR (Data Set=Application Data; Data Subset=IPTV_configuration, Data Key=AF Transaction Internal ID, S-NSSAI and DNN and/or SUPI/Internal-Group-Id).

(in the case of Nnef_IPTV_configuration_Delete): The NEF deletes the AF requirements in the UDR (Data Set=Application Data; Data Subset=IPTV_configuration, Data Key=AF Transaction Internal ID).

The NEF responds to the AF.

4. The PCF(s) that have subscribed to modifications of AF requests (Data Set=Application Data; Data Subset=IPTV_configuration, Data Key=SUPI/Internal-Group-Id) receive, a Nudr_DM_Notify notification of data change from the UDR.

5. The PCF determines if existing PDU Sessions are potentially impacted by the AF request. For each of these PDU Sessions, the PCF updates the SMF with corresponding new PCC rule(s) by invoking Npcf_SMPolicyControl_UpdateNotify service operation as described in steps 5 and 6 in TS 23.502.

In some embodiments, a Multicast Access Control list can be provided by the AF in the IPTV domain to the NEF. The Multicast Access Control List defines the access right status (e.g., fully allowed, preview allowed, not allowed) of each of the Multicast channels per subscriber identified by a GPSI.

With regard to policy and charging control rules for PDU Sessions, e.g., used to support Residential Gateways (RGs), a PCF may take a Multicast Access Control list as input to policy decision(s) in cases where the PDU Session is used for IPTV service. In some embodiments, the PCC rules may be sent to SMF and may indicate allowed IP Multicast Addressing information. In some embodiments, a “gate status” may or may not be applicable to IGMP messages transmitted over PDU Sessions used for IPTV Service.

In some embodiments, a Policy Control Request Trigger (PCRT) relevant for SMF may be used to ask the SMF or another similar component of the 5G system to report to the PCF when some event has occurred and to allow the PCF to act upon this event by, for instance, providing new policies. In some embodiments, a PCRT may indicate when a user equipment joins or leaves a multicast group or multicast stream. In some embodiments, when the SMF reports this condition, it may indicate the corresponding IP Multicast Addressing information.

In some embodiments, a Packet Detection Rule (PDR) may be used to support PDU Sessions used for IPTV service. In some embodiments, packets filter set may support Packet Filters fir IGMP, including both IGMPv2 and IGMPv3, specified respectively in IETF RFC 2236 and IETF RFC 3376, the entire contents of each of which are hereby incorporated herein by reference in their entireties for all purposes.

In some embodiments, for PDU Sessions used for IPTV service, following additional “action” values are used to support IPTV service. In some embodiments, an “action” indicating “IP Multicast Router Accept” may indicate whether to accept the multicast join and add the PDU Session to the requested multicast group distribution. In some embodiments, this may also imply acting as an IP Multicast Router. In some embodiments, an “action” indicating “IP Multicast Router Reject” may request to drop the IGMP join message. In some embodiments, when the UPF detects the IGMP leave message via the PDU Session, an “action” may indicate whether to ensure that the PDU Session is removed from the requested multicast group distribution.

In some embodiments, a Forwarding Action Rule (FAR) can be used to support PDU Sessions for RG. In some embodiments, for PDU Sessions used for IPTV Service, following additional “Action” values are used to support IPTV service. In some embodiments, an “action” comprising “IP Multicast Router Accept” may indicate whether to accept the multicast join and add the PDU Session to the requested multicast group distribution. In some embodiments, this may also imply acting as an IP Multicast Router. In some embodiments, an “action” comprising “IP Multicast Router Reject” may request to drop the IGMP join message. In some embodiments, when UPF detects the IGMP leave message via the PDU Session, an “action” may indicate whether to ensure that the PDU Session is removed from the requested multicast group distribution.

In some embodiments, a Usage Reporting Rule may be used to support PDU Sessions for RG. In some embodiments, for PDU Sessions used for IPTV service, a URR may indicate a Reporting Trigger with a value “IGMP notify” in which the UPF is to report to the SMF when it adds a PDU Session to the downlink (DL) replication tree associated with an IP Multicast flow or it removes a PDU Session from the DL replication tree associated with the IP Multicast flow. In some embodiments, the corresponding notification can or shall contain at least one of the Source IP of the DL multicast flow and the Destination IP address of the DL Multicast flow.

Referring now toFIG. 3, a policy control function (PCF) may send corresponding policy and charging control (PCC) rule(s), such as over the N7 interface, to the session management function (SMF) and/or the SMF sends N4 rules to the user plane function (UPF) over the N4 interface. In some embodiments, the user equipment, such as a Set Top box deployed in a customer's premises behind a Residential Gateway(s), can attempt to access an IP Multicast content by sending an IP Multicast Join request, such as defined in IETF RFC 3376 and/or IETF RFC 2236.

In some embodiments, a N4 Packet Detection Rule (PDR) may have already been defined to define Packets Filter Set support Packet Filters for Internet Group Management Protocol (IGMP), including both IGMPv2 signaling specified in IETF RFC 2236 and IGMPv3 signaling specified in IETF RFC 3376.

In some embodiments, a N4 Forwarding Action Rule (FAR) have already been defined to indicate whether to add the PDU Session to the requested multicast group or to drop the IGMP join message.

However, nothing has been defined, according to conventional systems and approaches, for the User Plane Function (UPF) to notify the Session Management Function (SMF) and for the SMF to notify the Policy Control Function (PCF) that a UE (a Residential Gateway) is joining (or is leaving) an IP Multicast distribution tree.

In some embodiments, over the N4 interface, update the definition Usage Reporting Rule (URR) as follows—URR used to support PDU Sessions for Residential Gateway (RG) follow the specifications in TS 23.501.

In some embodiments, for Protocol Data Unit (PDU) Sessions used for IPTV service, a Usage Reporting Rule (URR) may indicate a new Reporting Trigger (defined in TS 23.501) with a value “IGMP notify” where the User Plane Function (UPF) is to report to the Session Management Function (SMF) when it adds a PDU session to the downlink (DL) replication tree associated with an IP Multicast flow. In some embodiments, for Protocol Data Unit (PDU) Sessions used for IPTV service, a Usage Reporting Rule (URR) may indicate a new Reporting Trigger (defined in TS 23.501) with a value “IGMP notify” where the User Plane Function (UPF) is to report to the Session Management Function (SMF) when it removes a PDU session from the downlink (DL) replication tree associated with an IP Multicast flow.

In some embodiments, the corresponding notification shall contain the (Source IP of the DL multicast flow, Destination IP address of the DL multicast flow). In some embodiments, the URR may optionally include the IP Multicast Address(es) for which reporting is requested, e.g., for a specific IP Multicast Channel with Preview Allowed.

Referring now toFIGS. 4 and 5, possible apparatuses are schematically illustrated for carrying out the methods and processes disclosed herein. In some embodiments, the apparatus of an example embodiment includes, is associated with or is otherwise in communication with one or more of a processor12, one or more of an associated memory14and one or more of a communication interface16.

The UE700may also include a housing that contains one or more transmitters and one or more receivers to allow transmission and reception of data. The transmitter(s) and receiver(s) may be combined into one or more transceivers708. One or more antennas722are attached to the housing and electrically coupled to the transceiver708. The UE700may also include a digital signal processor (DSP)710for use in processing signals.

Referring now toFIGS. 6 and 7, illustrated are approaches for messaging and/or a notification protocol for sending, such as from the SMF to the UPF, a PFCP Session Establishment/Modification Request (e.g., a Create URR message), for example by using means such as the processor702, such as through a radio access network (RAN) or the like. In some embodiments, means such as the processor702, can be used to transmit or cause transmission of a PFCP Session Establishment/Modification Response, from the UPF to the SMF, such as in response to the UPF receiving the PFCP Session Establishment/Modification Request. In some embodiments, the SMF sends the PFCP Session Establishment/Modification Request to the UPF to request the UPF to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow.

Additionally or alternatively, the UE700receives, for example by using means such as the processor702, a registration request message, an attach request message, a tracking area update request message, or the like. These messages can comprise information related to user equipment that connect to or disconnect from a IP multicast flow. As such, a session controller can send a request for reporting when a PDU Session is added to or removed from a downlink replication tree associated with an internet protocol multicast flow. In some embodiments, the processor12, the processor702, or the like can be used to identify PDU Sessions added to or removed from a downlink replication tree associated with an IP multicast flow. Likewise, the processor12, the processor702and/or the like can be configured to, in response to receiving an indication related to whether a protocol data unit session has been added to or removed from the downlink replication tree added to or removed from the downlink replication tree associated with the IP multicast flow. In some embodiments, the processor12, the processor702, and/or the like can be configured to transmit a message related to the addition or removal of PDU Sessions to or from a downlink replication tree for an IP Multicast flow to a session management function.

In some embodiments, such as inFIG. 7, the UPF may indicate or otherwise determine that a user equipment joins or leaves an IP multicast flow and sends a PFCP Session Report Request to a SMF. In some embodiments, the SMF may then respond to the UPF with a PFCP Session Report Response.

Referring now toFIGS. 8-10, embodiments of methods are disclosed and illustrated as block flow diagrams. In particular,FIG. 8illustrates a method10comprising receiving, from a session controller, a request for reporting when protocol data unit sessions are added to or removed from a downlink replication tree associated with an internet protocol multicast flow, at11. In some embodiments, the method10can further comprise determining whether a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, at12. In some embodiments, the method10can further comprise, in response to said determining, transmitting a message to a session management function indicative of that said protocol data unit session has been added to or removed from said downlink replication tree, at13.

In some embodiments, such as illustrated inFIG. 9, a method20can comprise causing a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, at21or causing transmission of a request or command for a user plane function to report when a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, at21′. In some embodiments, the method20can further comprise receiving, from the user plane function, a message indicative of that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow, at22. In some embodiments, the method20can further comprise forwarding the indication that a protocol data unit session has been added to or removed from the downlink replication tree associated with the internet protocol multicast flow to entities that have been requested to be notified of such an event, at23. In some embodiments, the method20can further comprise optionally, in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening, at24.

In some embodiments, such as illustrated inFIG. 10, a method30can comprise receiving a message indicative of that a protocol data unit session has been added to or removed from a downlink replication tree associated with an internet protocol multicast flow, said message comprising at least an internet protocol address associated with a multicast destination of said internet protocol multicast flow, at31. In some embodiments, the method30can further comprise in response to receiving said message, determining from among a plurality of internet protocol multicast channels a particular internet protocol multicast channel to which a user equipment is listening, at32. In some embodiments, the particular IP multicast channel may support at least one of storing information related to said particular internet protocol multicast channel in order to generate billing information or statistical information, at33, and/or controlling one or more times during which a user device may receive said internet protocol multicast flow, at34.

A computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above, such as in conjunction with the flowchart ofFIG. 3. In other embodiments, the computer program instructions, such as the computer-readable program code portions, need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but may, instead, be embodied by a transitory medium with the computer program instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.