WO2014161104A1 - Procédé et appareil de chargement trafic appareil à appareil - Google Patents

Procédé et appareil de chargement trafic appareil à appareil Download PDF

Info

Publication number
WO2014161104A1
WO2014161104A1 PCT/CN2013/000378 CN2013000378W WO2014161104A1 WO 2014161104 A1 WO2014161104 A1 WO 2014161104A1 CN 2013000378 W CN2013000378 W CN 2013000378W WO 2014161104 A1 WO2014161104 A1 WO 2014161104A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging data
message
receiving
charging
transmitting
Prior art date
Application number
PCT/CN2013/000378
Other languages
English (en)
Inventor
Kenan Xu
Zhenhong Li
Fei YIN
Sami-Jukka Hakola
Xianjun FENG
Wei Zou
Haifeng Wang
Original Assignee
Broadcom Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Broadcom Corporation filed Critical Broadcom Corporation
Priority to PCT/CN2013/000378 priority Critical patent/WO2014161104A1/fr
Publication of WO2014161104A1 publication Critical patent/WO2014161104A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/65—Off-line charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present invention relates to charging device to device traffic. More specifically, the present invention exemplarily relates to measures (including methods, apparatuses and computer program products) for realizing charging device to device traffic. Background
  • the present specification generally relates to the field of device to device (device-to-device, D2D) data communication.
  • D2D data communication is within the scope of 3 rd Generation Partnership Project (3GPP) Proximity Service (ProSe).
  • ProSe is a highly active topic in Long Term Evolution (LTE) Release 12 (Rel-12).
  • PS domain charging standard charging information in the PS domain network is collected for each mobile station (MS)/user equipment (UE) by packet switched core network (PCN) nodes including e.g. serving GPRS support nodes (SGSN), serving gateways (S-GW) and packet data network gateways (P-GW), which are serving that MS/UE.
  • PCN packet switched core network
  • SGSN serving GPRS support nodes
  • S-GW serving gateways
  • P-GW packet data network gateways
  • the SGSN and the S-GW collect charging information for each MS/UE related to the radio network usage
  • the P-GW collects charging information for each MS related to the external data network usage.
  • the S-GW is taken as an example.
  • the problems addressed herein also apply to other PCN nodes, including SGSN and P-GW. Accordingly, the solutions proposed herein also apply or can be easily extended to SGSN and P-GW.
  • an S-GW should collect a set of charging information for a UE.
  • One piece thereof is usage information of the radio interface.
  • the information includes the amount of data transmitted in mobile-originated and mobile-terminated directions categorized with quality of service (QoS) and user protocols.
  • QoS quality of service
  • S-GW may simply implement a solution to collect this information, as UE-originated and/or UE-terminated data traffic goes through the S-GW node.
  • Figure 4 shows a simplified illustration of data communication between two UEs under the simplifying assumption that they are served by the same evolved Node B (eNodeB, eNB) via 3GPP network.
  • eNodeB evolved Node B
  • a packet When a packet is generated from a UE1 , it flows through eNodeB, S-GW, P-GW, S-GW, eNodeB, and arrives at a UE2. It is straightforward for the S-GW to collect the incoming and outgoing data volume of UE1 and UE2.
  • FIG. 5 shows a simplified illustration of D2D data communication between two UEs.
  • data packets are exchanged directly over the radio, thereby bypassing the network.
  • the network including the S-GW
  • D2D data communication may offer great benefit of reducing radio interface load, and it is therefore highly attractive to service operators.
  • D2D data communication should support the volume-based billing.
  • the new charging method should be transparent to the end user.
  • the billing should use the same form no matter whether D2D data communication is adopted or not.
  • the billing for UE1 and UE2 should be of the same form no matter if they are far away or close to each other (D2D communication takes place).
  • the users usually have no interest to know whether their traffic has gone through a D2D path (according to Figure 5) and a traditional public land mobile network (PLMN) path (according to Figure 4).
  • PLMN public land mobile network
  • a fixed billing or a flat-rate contract is applied.
  • a time-based charging is proposed. Namely, the billing is a rate times the duration of D2D connections (collected by a PCN node).
  • the UE may locally maintain billing information and forward it when the D2D connection ends.
  • the third option points out the direction of a volume-based billing solution, i.e., that a UE may collect the inbound and outbound traffic in case of D2D data communication and feed the charging information to the S-GW, the document handles that option only peripherally and the design challenges are left unresolved.
  • a method comprising receiving a nas connection establishment confirmation message comprising charging related information, and collecting charging data regarding a device to device communication based on said charging related information.
  • a method comprising receiving a charging delegation request message comprising charging related information for an upcoming device to device communication connection establishment, and transmitting a nas connection establishment confirmation message comprising said charging related information.
  • a method comprising receiving a connection establishment indication message indicative of an upcoming device to device communication connection establishment, and transmitting a charging delegation request message comprising charging related information for said upcoming device to device communication connection establishment.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a nas connection establishment confirmation message comprising charging related information, and collecting charging data regarding a device to device communication based on said charging related information.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a charging delegation request message comprising charging related information for an upcoming device to device communication connection establishment, and transmitting a nas connection establishment confirmation message comprising said charging related information.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and at least one interface configured for communication with at least another apparatus, the at least one processor, with the at least one memory and the computer program code, being configured to cause the apparatus to perform receiving a connection establishment indication message indicative of an upcoming device to device communication connection establishment, and transmitting a charging delegation request message comprising charging related information for said upcoming device to device communication connection establishment.
  • a computer program product comprising computer-executable computer program code which, when the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related exemplary aspects of the present invention), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related exemplary aspects of the present invention.
  • Such computer program product may comprise (or be embodied) a (tangible) computer-readable (storage) medium or the like on which the computer-executable computer program code is stored, and/or the program may be directly loadable into an internal memory of the computer or a processor thereof.
  • Any one of the above aspects enables an efficient determination of relevant charging information related to device to device communications to thereby solve at least part of the problems and drawbacks identified in relation to the prior art.
  • charging device to device traffic More specifically, by way of exemplary embodiments of the present invention, there are provided measures and mechanisms for realizing charging device to device traffic.
  • Figure 1 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 2 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 3 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • Figure 4 is a schematic diagram of signaling sequences of a simplified data communication not implementing device to device mechanisms
  • Figure 5 is a schematic diagram of signaling sequences of a simplified data communication implementing device to device mechanisms
  • Figure 6 shows a schematic diagram illustrating charging design options
  • Figure 7 shows a schematic diagram illustrating charging design options according to exemplary embodiments of the present invention
  • Figure 8 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 9 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 10 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 11 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 12 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 13 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 14 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 15 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 16 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention
  • Figure 17 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 18 shows a schematic block diagram illustrating exemplary apparatuses according to exemplary embodiments of the present invention. Detailed description of drawings and embodiments of the present invention
  • the 3GPP PS domain offline charging architecture for D2D data communication is enhanced.
  • a D2D charging agent module residing in UEs
  • collects charging-relevant information and feeds the information to PCN nodes.
  • the PCN nodes process the collected charging information for charging service, such as generating Charging Data Record (CDR).
  • CDR Charging Data Record
  • offline charging solutions for D2D data communications are provided.
  • a solution for volume-based charging of D2D data communication is provided. Specifically, the following aspects are provided.
  • the S-GW delegates the task of collecting charging- relevant info to UEs before data is/ are exchanged.
  • respective signaling for several scenarios is proposed.
  • the 3GPP PS domain offline charging architecture includes four important logical charging functions, namely, charging trigger function (CTF), charging data function (CDF), charging gateway function (CGF), and billing domain.
  • CTF charging trigger function
  • CDF charging data function
  • CGF charging gateway function
  • billing domain billing domain
  • the S-GW may include the CTF to generate charging events and forward them to the CDF.
  • the CDF in turn, may generate CDRs which may then be transferred to the CGF.
  • the CGF may create CDR files and may forward them to the billing domain.
  • the above mentioned architecture may be modified in that the S-GW may integrate CDF and/or CGF function as shown in Figure 6.
  • S-GW collects charging information including received and transmitted data volume of individual UEs.
  • the S-GW may collect charging information for D2D data communication between UEs, as the data traffic does not go through S-GW in the D2D communication mode, i.e. bypassing the network.
  • an architectural enhancement for D2D data communication offline charging is proposed as illustrated in Figure 7.
  • a D2D charging gateway (GW) module is implemented in S-GW, and a D2D charging agent function is implemented in UE.
  • the D2D charging GW may delegate the task of collecting charging information to the charging agent function within a UE.
  • the D2D charging agent is responsible for collecting charging data, including but not limited to, received data volume, transmitted data volume and connection duration. It further reports the charging data to the D2D charging GW.
  • a UE may report the charging data periodically, upon event/condition, or at the end of D2D communication. The charging data may be used to generate billing information at a later time.
  • an S-GW may assign the charging task to a charging agent (in a UE).
  • a D2D charging GW arranges a charging agent to conduct a charging task during the D2D connection setup procedure.
  • the D2D connection setup procedure may vary, depending on a number of factors, such as whether UEs are under 3GPP network coverage, whether network control exists during the D2D communication setup, which device (UE or eNB) initiates the D2D connection setup, how D2D radio resource is configured (eNB configured or UE configured), etc.
  • the D2D establishment signaling (signaling sequence, signaling parameters) may also vary from one technical proposal to another.
  • eNB detects the opportunities for D2D communications, and initiates the setup process, and the network nodes control the communication setup process, and further, the UEs are under 3GPP network coverage, and under continuous network control.
  • 3GPP ProSe feasibility studies A person skilled in the art will, however, appreciate that exemplary embodiments of the present invention are by no means limited to these D2D communication scenarios, and may be applied/extended to other D2D communication scenarios beyond the conditions above.
  • Figure 1 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • a procedure according to exemplary embodiments of the present invention comprises an operation of receiving (S11) a nas (non- access stratum (NAS)) connection establishment confirmation message comprising charging related information, and an operation of collecting (S12) charging data regarding a device to device communication based on said charging related information.
  • Figure 2 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • a procedure according to exemplary embodiments of the present invention comprises an operation of receiving (S21) a charging delegation request message comprising charging related information for an upcoming device to device communication connection establishment, and an operation of transmitting (S22) a nas connection establishment confirmation message comprising said charging related information.
  • Figure 3 is a schematic diagram of a procedure according to exemplary embodiments of the present invention.
  • a procedure according to exemplary embodiments of the present invention comprises an operation of receiving (S31) a connection establishment indication message indicative of an upcoming device to device communication connection establishment, and an operation of transmitting (S32) a charging delegation request message comprising charging related information for said upcoming device to device communication connection establishment.
  • Figure 8 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 8 depicts a D2D radio bearer setup initiated by the eNodeB that detects potential D2D traffic within the cell served by the eNodeB.
  • UE1 and UE2 are served by the same eNodeB (wherein the eNB configures the UE1 and the UE2 for D2D setup) and are within the D2D range.
  • the setup process has four stages (a description of a non-D2D communication setup process is omitted for reasons of legibility).
  • UE1 and UE2 exchange data via the core network.
  • S-GW directly collects various charging relevant information, including UE1- originated, UE1 -term inated, UE2-originated, and UE2-term inated traffic volume.
  • the eNodeB detects the presence of internet protocol (IP) traffic between devices in its cell and requests measurements from the UE1 to determine whether they are within D2D range (and whether both of them are D2D capable).
  • IP internet protocol
  • the eNodeB may request the UE2 to conduct the measurement too.
  • the eNodeB decides to set up D2D connection based on the D2D measurement response from UEs and/or local policy.
  • the eNodeB sends D2D RADIO BEARER EST REQ (establishment request) message to UE1.
  • the REQ message may include some parameters of UE2.
  • UE1 sends NAS: D2D CONNECTION EST IND (establishment indication) message to mobility management entity (MME).
  • MME mobility management entity
  • This message informs that MME that a D2D bearer is to be established for UE1. It may contain information including the identifier (ID) of the corresponding non- D2D session.
  • the MME further notifies S-GW about the D2D bearer by sending a D2D CONNECTION EST IND message.
  • the S-GW responds with a D2D CHARGING DG REQ (delegation request) message.
  • the message may include a charging ticket.
  • the charging ticket describe the charging related information, including the charging ticket number, IDs of relevant (non- D2D) sessions, the ID of involved UEs, the method and policy for reporting charging data, etc.
  • the MME then sends NAS: D2D CONNECTION CONF (confirmation) message to UE1.
  • the message should at least include the charging ticket information.
  • an UE may report its charging data to the S-GW for example as session-end report, proactive report, reactive report, or piggyback report, as explained later.
  • stage 4 The steps in stage 4 are similar to steps in stage 3, except that it applies to UE2.
  • UE1 and UE2 are ready to collect charging information for their inbound and outbound D2D traffic.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a nas connection establishment indication message indicative of an upcoming device to device communication connection establishment.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method may comprise an operation of receiving a nas connection establishment indication message indicative of said upcoming device to device communication connection establishment, and an operation of transmitting a connection establishment indication message including at least part of information of said nas connection establishment indication message.
  • Figure 9 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 9 depicts a D2D radio bearer setup initiated by the eNodeB that detects potential D2D traffic within the cell served by the eNodeB.
  • the steps are similar to those described in relation to Figure 8 except the way UE2 is configured for D2D communication.
  • both UEs are configured by the same eNodeB.
  • the eNodeB configures UE1 first, and UE1 configures UE2 at the stage 4.
  • Figure 10 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 10 depicts a D2D radio bear setup initiated by the eNodeB.
  • UE1 is served by eNodeBI
  • UE2 is served by eNodeB2 with eNodel and eNode2 serving neighboring cells.
  • Figure 10 shows an additional step, in which eNodeBI finds (determines) its neighboring eNodeB2, as depicted by stage 1.1 ENodeBI detects IP traffic between devices in the same subnet (e.g. by sniffing IP packets).
  • the eNodeBI contacts the S-GW to determine whether UE2 is served by a neighboring eNodeB2. If the device is served by a neighboring eNodeB2, as indicated in the response, the eNodeBI sends a request for D2D setup to the eNodeB2.
  • the setup request contains at least the IP address (or other identifier that is known to the eNodeBI) of UE2. If the eNodeB2 agrees to the request, it sends an affirmative response.
  • stagel stage 2
  • stage 3 stage 4
  • an UE may report its charging data to the S-GW for example as session-end report, proactive report, reactive report, or piggyback report.
  • an S-GW may indicate to the UE how it would like to receive the charging data in the charging ticket.
  • a UE may also decide its report method according to its local policy.
  • a UE may also adopt a combination of multiple methods.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting said collected charging data.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving charging data, and an operation of forwarding said charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving charging data.
  • Session-end charging data report means that a UE reports its charging data when a session ends.
  • Figure 11 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 11 depicts the process of UE1 and UE2 updating charging data to the S-GW at the end of session, assuming that UE1 initiates the connection release.
  • UE1 first sends NAS: D2D CONNECTION DEL IND (deletion indication) message to MME.
  • the message includes the charging data information.
  • the MME forwards the charging data to S-GW by sending a D2D CONNECTION DEL IND message.
  • the S-GW sends a D2D CONNECTION DEL RSP (deletion response) message to MME, and then MME sends NAS: D2D CONNECTION DEL CONF (deletion confirmation) message to UE1.
  • the UE1 continues to release the radio bearer resource by sending a D2D RADIO BEARER DEL REQ (deletion request) message to eNodeB, and eNodeB responds by sending a D2D RADIO BEARER DEL RSP message. Further, the eNodeB sends a D2D RADIO BEARER DEL REQ message to UE2.
  • UE2 sends a NAS: D2D CONNECTION DEL IND message with its charging data to MME. The MME forwards the charging data to the S-GW by sending a D2D CONNECTION DEL IND message.
  • the S-GW sends a D2D CONNECTION DEL RSP message to the MME, and MME sends a NAS: D2D CONNECTION DEL CONF message to UE2.
  • the UE2 then sends a D2D RADIO BEARER DEL RSP message.
  • the D2D connection release is completed.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a nas connection deletion confirmation message.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a device to device radio bearer deletion request message, and an operation of receiving a device to device radio bearer deletion response message.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a device to device radio bearer deletion request message, and an operation of transmitting a device to device radio bearer deletion response message.
  • Such exemplary receiving operation may comprise an operation of receiving a nas connection deletion indication message indicative of termination of a device to device communication including said charging data.
  • Such exemplary forwarding operation may comprise an operation of transmitting a connection deletion indication message including at least said charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a connection deletion response message, and an operation of transmitting a nas connection deletion confirmation message.
  • exemplary details of the receiving operation (receiving said charging data) are given, which are inherently independent from each other as such.
  • Such exemplary receiving operation may comprise an operation of receiving a connection deletion indication message indicative of termination of a device to device communication including said charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a connection deletion response message.
  • a simple design for reporting charging data can be provided.
  • Figure 12 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Proactive report means that a UE decides when to report the charging data autonomously. Reports may take place periodically or when certain conditions are satisfied (e.g. when certain amount of traffic volume has received/sent since the last report). The conditions and/or the report period may be defined in the charging ticket received from the S-SW.
  • Figure 12 depicts the process of UE1 updating charging data to the S-GW proactively. The update is conducted in the following steps. First, UE1 sends NAS: D2D CONNECTION STATUS UPDATE message to the MME. The message includes the charging data. The MME then sends the charging data to S-GW in the D2D CONNECTION STATUS UPDATE message.
  • the S-GW may optionally send a D2D CONNECTION STATUS UPDATE CONF message to the MME.
  • the MME may send a NAS: D2D CONNNECTION STATUS UPDATE CONF message to UE1.
  • Such exemplary transmitting operation may comprise an operation of transmitting, upon a predetermined update condition, a nas connection status update message indicative of an update of said collected charging data including said collected charging data.
  • the predetermined update condition may be at least one of an elapsed predetermined period of time, a received predetermined amount of traffic volume, and a transmitted predetermined amount of traffic volume.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a nas connection status update confirmation message.
  • Such exemplary receiving operation may comprise an operation of receiving a nas connection status update message indicative of an update of said charging data including said charging data.
  • Such exemplary forwarding operation may comprise an operation of transmitting a connection status update message including at least said charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a connection status update confirmation message, and an operation of transmitting a nas connection status update confirmation message including at least part of information of said connection status update confirmation message.
  • Such exemplary receiving operation may comprise an operation of receiving a connection status update message indicative of an update of said charging data including said charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a connection status update confirmation message.
  • FIG. 13 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Reactive report means that a UE report its charging data upon receiving an S-GW inquiry.
  • FIG 13 depicts the process of UE1 updating charging data to the S-GW reactively.
  • the S-GW initiates a charging data update process by sending a D2D CONNECTION STATUS POLL message to MME, and the MME then sends a NAS: D2D CONNNECTION STATUS POLL message to UE1.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a nas connection status poll message indicative of a request for said collected charging data, wherein said predetermined update condition is a receipt of said connection status poll message.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a connection status poll message indicative of a request for said charging data, and an operation of transmitting a nas connection status poll message including at least part of information of said connection status poll message.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a connection status poll message indicative of a request for said charging data. This solution is also safer against accidental data loss and additionally offers chances to the S-GW to obtain/request charging data proactively.
  • Figure 14 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • a UE may also send its charging data to the S-GW by piggyback the charging data in other NAS messages exchanged between UE and MME.
  • a UE may embed its charging data in the messages exchanged for tracking area update (TAU) procedure.
  • TAU tracking area update
  • FIG 14 depicts a process of piggybacking charging data in TAU signaling exchange.
  • the UE inserts the charging data in NAS: TAU Request message.
  • the MME exchanges the TAU Request and TAU Accept messages with the HSS to update the tracking area of UE.
  • the MME may send D2D CONNECTION STATUS UPDATE message to S-GW.
  • the S-GW may optionally send a D2D CONNECTION STATUS UPDATE CONF message to the MME.
  • the MME may send a NAS: TAU Accept message to UE.
  • the message may include a confirmation with regard to charging data.
  • Such exemplary transmitting operation may comprise an operation of embedding said collected charging data into a scheduled control message, and an operation of transmitting said control message according to its schedule.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a response message corresponding to said control message including charging data confirmation information.
  • Such exemplary receiving operation may comprise an operation of receiving a control message including said charging data, and an operation of extracting said charging data from said control message.
  • Such exemplary forwarding operation may comprise an operation of transmitting a connection status update message indicative of an update of said charging data including said charging data.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method may comprise an operation of receiving a connection status update confirmation message, an operation of embedding charging data confirmation information into a response message corresponding to said control message, and an operation of transmitting said response message.
  • This solution updates charging data in the middle of the session, and incurs much less traffic load compared the two recently discussed solutions.
  • the ongoing 3GPP ProSe standardization effort may require the evolved packet system (EPS) be able to collect charging data for ProSe discovery features including the ability of a ProSe-enabled UE to be discoverable (including based on the range class), the ability to discover other ProSe- enabled UEs (including based on the range class), and the event of discovering a ProSe-enabled UE (including based on the range class).
  • EPS evolved packet system
  • Figure 15 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 15 depicts how an EPS may collect ProSe feature related charging data according to exemplary embodiments of the present invention.
  • a MME updates its record of ProSe capability and configuration for a UE from time to time.
  • the update may be caused by a UE device is turned on/off.
  • the update may take place when a UE enables ProSe UE discovery capability.
  • the update may also incur when a ProSe UE enables its being discoverable feature.
  • the MME get a new update it may send UE D2D CAPABILITY UPDATE message to S-GW.
  • the S-GW may generate charging data according to the charging policy.
  • the message may send a D2D EVENT CHARGING DG REQ message to MME.
  • the message includes a charging ticket.
  • the MME further sends a NAS:D2D EVENT ACCOUNTING REQ (UE CHARGING TICKET) message to the UE.
  • the UE may account the UE discovery events according to the charging ticket.
  • an exemplary method may comprise an operation of receiving a device to device event accounting request message indicative of an instruction to collect device to device event charging data, said device to device event accounting request message comprising said charging related information, and an operation of collecting device to device event charging data based on said charging related information.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a device to device capability update message indicative of device to device capability of a communication endpoint. Further, according to a variation of the procedure shown in Figure 2, exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method may comprise an operation of receiving a device to device event charging delegation request message indicative of an instruction to collect device to device event charging data, said device to device event charging delegation request message comprising said charging related information, and an operation of transmitting a device to device event accounting request message comprising said charging related information.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a device to device capability update message indicative of device to device capability of a communication endpoint.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a device to device event charging delegation request message indicative of an instruction to collect device to device event charging data, said device to device event charging delegation request message comprising said charging related information.
  • the UE may report the D2D discovery charging data to the network proactively.
  • the report may take place periodically or when certain conditions are satisfied (e.g. when certain amount of discovery events has been counted since the last report).
  • the conditions and/or the report period may be defined in the charging ticket received from the S-SW.
  • the report may also take place when a UE is disabled of ProSe UE discovery capability (by the user, or the operator).
  • the report may also take place when a UE is turned off. Accordingly, Figure 16 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • Figure 16 depicts the process of UE reporting D2D discovery charging data to the S-GW proactively.
  • the report is conducted in the following steps.
  • UE1 sends NAS: D2D EVENT CHARGING DATA UPDATE message to the MME.
  • the message includes the charging data.
  • the charging data may include the number of UE discovery events.
  • the MME then sends the charging data to S-GW in the D2D EVENT CHARGING DATA UPDATE message.
  • the S-GW may optionally send a D2D EVENT CHARGING DATA UPDATE CONF message to the MME.
  • the MME may send a NAS: D2D EVENT CHARING DATA UPDATE CONF message to UE.
  • an exemplary method may comprise an operation of transmitting, upon a predetermined event report condition, a nas device to device event charging data update message indicative of an update of said collected device to device event charging data.
  • the predetermined event report condition may be at least one of an elapsed predetermined period of time, a counted predetermined amount of device to device discovery events, a disabling of a proximity service discovery capability of a communication endpoint, and a turning off of a communication endpoint.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a nas device to device event charging data update confirmation message.
  • an exemplary method may comprise an operation of receiving a nas device to device event charging data update message indicative of an update of said device to device event charging data, and an operation of transmitting a device to device event charging data update message including at least part of information of said nas device to device event charging data update message.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method may comprise an operation of receiving a device to device event charging data update confirmation message, and an operation of transmitting a nas device to device event charging data update confirmation message including at least part of information of said device to device event charging data update confirmation message.
  • exemplary additional operations are given, which are inherently independent from each other as such.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a device to device event charging data update message indicative of an update of said device to device event charging data.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a device to device event charging data update confirmation message.
  • the UE may report the D2D discovery charging data to the network in a reactive manner.
  • Figure 17 shows a schematic diagram of signaling sequences according to exemplary embodiments of the present invention.
  • FIG 17 depicts the process of the UE updating charging data to the S-GW reactively.
  • the S-GW initiates a charging data update process by sending a D2D EVENT CHARGING DATA POLL message to MME, and the MME then sends a NAS: D2D EVENT CHARGING DATA POLL message to UE.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of receiving a nas device to device event charging data poll message indicative of a request for said collected device to device event charging data, wherein said predetermined event report condition is a receipt of said device to device event charging data poll message.
  • an exemplary method may comprise an operation of receiving a device to device event charging data poll message indicative of a request for said device to device event charging data, and an operation of transmitting a nas device to device event charging data poll message including at least part of information of said device to device event charging data poll message.
  • an exemplary method according to exemplary embodiments of the present invention may comprise an operation of transmitting a device to device event charging data poll message indicative of a request for said device to device event charging data.
  • said charging data is at least one of a received data volume, a transmitted data volume, and a device to device connection duration, a number of UE discovery events, and/or said charging related information is at least one of a charging ticket number, an identifier of at least one corresponding non device to device session, identifiers of communication endpoints involved in said device to device communication, and information regarding reporting said charging data
  • said connection establishment indication message comprises an identifier of at least one corresponding non device to device session
  • said predetermined update condition is at least one of an elapsed predetermined period of time, a received predetermined amount of traffic volume, and a transmitted predetermined amount of traffic volume
  • said predetermined event report condition is at least one of an elapsed predetermined period of time, a counted predetermined amount of device to device discovery events, a disabling of a proximity service discovery capability of a communication endpoint, and a turning off of a communication
  • the CTF function may be introduced into UE and CDF function into S-GW, and a new Rf reference point may be introduced between the UE and S-GW using control plane.
  • CTF may collect ProSe specific events in the UE and forward the events to the CDF.
  • the number of exemplary embodiments of the present invention provides multiple technical alternatives supporting different standardization strategies.
  • S-GW is taken only as an example, and the solution according to exemplary embodiments of the present invention may also be applied/extended to P-GW and SGSN.
  • a potential problem raised because UEs are not as robust and safe as PCN nodes (charging data may possibly be lost when exception occurs at UEs) is overcome by reporting charging data in the middle of D2D session according to exemplary embodiments of the present invention.
  • FIG. 18 which is noted to represent a simplified block diagram, the solid line blocks are basically configured to perform respective operations as described above.
  • the entirety of solid line blocks are basically configured to perform the methods and operations as described above, respectively.
  • the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively.
  • Such functional blocks are implementation-independent, i.e. may be implemented by means of any kind of hardware or software, respectively.
  • the arrows and lines interconnecting individual blocks are meant to illustrate an operational coupling there-between, which may be a physical and/or logical coupling, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional entities not shown.
  • the direction of arrow is meant to illustrate the direction in which certain operations are performed and/or the direction in which certain data is transferred.
  • only those functional blocks are illustrated, which relate to any one of the above-described methods, procedures and functions.
  • a skilled person will acknowledge the presence of any other conventional functional blocks required for an operation of respective structural arrangements, such as e.g. a power supply, a central processing unit, respective memories or the like.
  • memories are provided for storing programs or program instructions for controlling the individual functional entities to operate as described herein.
  • Figure 18 shows a schematic block diagram illustrating exemplary apparatuses according to exemplary embodiments of the present invention.
  • the thus described apparatus 10 may represent a (part of a) device or terminal such as a mobile station MS or user equipment UE (for example a mobile phone) or a modem (which may be installed as part of a MS or UE, but may be also a separate module, which can be attached to various devices), and may be configured to perform a procedure and/or functionality as described in conjunction with Figure 1.
  • the thus described apparatus 20 may represent a (part of a) network entity, such as a base station or access node or any network-based controller, e.g. an eNB, and may be configured to perform a procedure and/or functionality as indicated above, while no further details thereof are given.
  • the thus described apparatus 30 may represent a (part of a) network node such as a mobile management entity MME or a modem (which may be installed as part of a MME, but may be also a separate module, which can be attached to various devices), and may be configured to perform a procedure and/or functionality as described in conjunction with Figure 2.
  • the thus described apparatus 40 may represent a (part of a) network node such as a serving gateway S-GW or a modem (which may be installed as part of a S-GW, but may be also a separate module, which can be attached to various devices), and may be configured to perform a procedure and/or functionality as described in conjunction with Figure 3.
  • the apparatus 10 comprises a processor 15, a memory 16 and an interface 17, which are connected by a bus 18 or the like.
  • the apparatus 20 comprises a processor 25, a memory 26 and an interface 27, which are connected by a bus 28 or the like.
  • the apparatus 30 comprises a processor 35, a memory 36 and an interface 37, which are connected by a bus 38 or the like.
  • the apparatus 40 comprises a processor 45, a memory 46 and an interface 47, which are connected by a bus 48 or the like.
  • the apparatuses may be connected via links 40, 41, 42 and/or 43.
  • the processor 15/25/35/45 and/or the interface 17/27/37/47 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively.
  • the interface 17/27/37/47 may include a suitable transceiver coupled to one or more antennas or communication means for (hardwire or wireless) communications with the linked or connected device(s), respectively.
  • the interface 17/27/37/47 is generally configured to communicate with at least one other apparatus, i.e. the interface thereof.
  • the memory 16/26/36/46 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the exemplary embodiments of the present invention.
  • the respective devices/ apparatuses may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.
  • the processor or some other means
  • the processor is configured to perform some function
  • this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as "means for xxx-ing").
  • an apparatus representing the terminal 10 comprises at least one processor 15, at least one memory 16 including computer program code, and at least one interface 17 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 15, with the at least one memory 16 and the computer program code
  • the processor is configured to perform receiving a nas connection establishment confirmation message comprising charging related information, and to perform collecting charging data regarding a device to device communication based on said charging related information.
  • the apparatus 10 may thus comprise respective means for receiving and means for collecting.
  • an apparatus representing the network node 30 comprises at least one processor 35, at least one memory 36 including computer program code, and at least one interface 37 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 35, with the at least one memory 36 and the computer program code
  • the processor is configured to perform receiving a charging delegation request message comprising charging related information for an upcoming device to device communication connection establishment, and to perform transmitting a nas connection establishment confirmation message comprising said charging related information.
  • the apparatus 30 may thus comprise respective means for receiving and means for transmitting. As outlined above, the apparatus 30 may further comprise one or more of respective means for forwarding, means for extracting, and means for embedding.
  • an apparatus representing the network node 40 comprises at least one processor 45, at least one memory 46 including computer program code, and at least one interface 47 configured for communication with at least another apparatus.
  • the processor i.e. the at least one processor 45, with the at least one memory 46 and the computer program code
  • the processor is configured to perform receiving a connection establishment indication message indicative of an upcoming device to device communication connection establishment, and to perform transmitting a charging delegation request message comprising charging related information for said upcoming device to device communication connection establishment.
  • the apparatus 40 may thus comprise respective means for receiving and means for transmitting.
  • a system may comprise any conceivable combination of the thus depicted devices/ apparatuses and other network elements, which are configured to cooperate with any one of them.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor- Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field-programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means e.g. the above-defined network entity or network register, or any one of their respective units/means
  • an apparatus like the user equipment and the network entity /network register may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • the present invention also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
  • Such measures exemplarily comprise receiving a nas connection establishment confirmation message comprising charging related information, and collecting charging data regarding a device to device communication based on said charging related information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil de chargement de trafic appareil à appareil. Le procédé consiste : à recevoir un message de confirmation de création de connexion de strate de non accès (NAS) comprenant des informations relatives à un chargement, et à collecter des données de chargement concernant une communication appareil à appareil basée sur lesdites informations relatives au chargement.
PCT/CN2013/000378 2013-04-01 2013-04-01 Procédé et appareil de chargement trafic appareil à appareil WO2014161104A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000378 WO2014161104A1 (fr) 2013-04-01 2013-04-01 Procédé et appareil de chargement trafic appareil à appareil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000378 WO2014161104A1 (fr) 2013-04-01 2013-04-01 Procédé et appareil de chargement trafic appareil à appareil

Publications (1)

Publication Number Publication Date
WO2014161104A1 true WO2014161104A1 (fr) 2014-10-09

Family

ID=51657370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/000378 WO2014161104A1 (fr) 2013-04-01 2013-04-01 Procédé et appareil de chargement trafic appareil à appareil

Country Status (1)

Country Link
WO (1) WO2014161104A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100009675A1 (en) * 2008-07-14 2010-01-14 Nokia Corporation Setup of device-to-device connection
WO2011147462A1 (fr) * 2010-05-28 2011-12-01 Nokia Siemens Networks Oy Procédé et appareil permettant des communications de dispositif à dispositif
CN102714861A (zh) * 2010-01-19 2012-10-03 诺基亚公司 演进型节点b控制的用于设备到设备和蜂窝用户的集中式资源重用

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100009675A1 (en) * 2008-07-14 2010-01-14 Nokia Corporation Setup of device-to-device connection
CN102714861A (zh) * 2010-01-19 2012-10-03 诺基亚公司 演进型节点b控制的用于设备到设备和蜂窝用户的集中式资源重用
WO2011147462A1 (fr) * 2010-05-28 2011-12-01 Nokia Siemens Networks Oy Procédé et appareil permettant des communications de dispositif à dispositif

Similar Documents

Publication Publication Date Title
EP2952056B1 (fr) Sélection de passerelle mobile au moyen d'une connexion directe entre un noeud pcrf et un noeud de gestion de mobilité
EP2918094B1 (fr) Surveillance réseau d'événements d'équipement utilisateur
KR101340496B1 (ko) 차징 시스템 및 방법
US9591560B2 (en) Temporary credential assignment when connecting to roaming wireless networks
CN106658601B (zh) 数据传输的处理方法及装置
WO2021156771A1 (fr) Extension de npcf_eventexposure avec événement de surveillance d'utilisation
EP2482567B1 (fr) Procede et appareil pour la transition de statut
CN102075894A (zh) 策略和计费规则功能实体的选择方法及系统
US9830214B1 (en) Diameter routing agent detection of policy server communication failure
US20130279336A1 (en) Communication system
US20160198049A1 (en) Wireless communication system and method for charging control
EP2787768B1 (fr) Procédé et système d'accès
CN105516952A (zh) 一种策略和计费规则功能的选择方法及装置
EP3335372B1 (fr) Amélioration du contrôle de congestion par redémarrage sélectif de sessions de contrôle de crédit
EP3289793B1 (fr) Procédé, centre de commutation mobile, msc, et produit-programme informatique permettant de détecter un contournement d'interconnexion
CN101998515B (zh) 控制pcrf负载均衡的实现方法和实现系统
CN101730151B (zh) 实现dhcp模式协商的方法、系统及接入服务网网关
WO2014134819A1 (fr) Procédé de facturation, dispositif de réseau d'accès et dispositif de passerelle
KR20130015602A (ko) 이동통신 서비스 시스템에서의 선택적 호 처리 방법, 선택적 호 처리를 위한 게이트웨이 장치 및 과금 장치
US20150350455A1 (en) Proximity service
US20150280926A1 (en) Charging control method and system in communication network
WO2013091705A1 (fr) Procédés et appareils pour établissement de session avec commande de politique entre réseaux mobiles et fixes
KR20130022964A (ko) Ｅｐｃ망에서 ｃｓｆｂ 음성 서비스를 위한 페이징 시스템, 장치 및 방법
WO2014161104A1 (fr) Procédé et appareil de chargement trafic appareil à appareil
WO2023062548A1 (fr) Désenregistrement d'un ue déclenché par une fonction de commande d'admission de tranche de réseau (nsacf)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13881237

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13881237

Country of ref document: EP

Kind code of ref document: A1