US20200336320A1 - Charging for mtc small data transmission and trigger at mtc-iwf - Google Patents
Charging for mtc small data transmission and trigger at mtc-iwf Download PDFInfo
- Publication number
- US20200336320A1 US20200336320A1 US16/921,608 US202016921608A US2020336320A1 US 20200336320 A1 US20200336320 A1 US 20200336320A1 US 202016921608 A US202016921608 A US 202016921608A US 2020336320 A1 US2020336320 A1 US 2020336320A1
- Authority
- US
- United States
- Prior art keywords
- network node
- mtc
- message
- iwf
- cdr
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title description 12
- 238000000034 method Methods 0.000 claims description 8
- 238000010295 mobile communication Methods 0.000 claims 4
- 230000004044 response Effects 0.000 claims 2
- 238000012546 transfer Methods 0.000 abstract description 9
- 238000004891 communication Methods 0.000 description 9
- 238000012795 verification Methods 0.000 description 7
- NRNCYVBFPDDJNE-UHFFFAOYSA-N pemoline Chemical compound O1C(N)=NC(=O)C1C1=CC=CC=C1 NRNCYVBFPDDJNE-UHFFFAOYSA-N 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000004353 relayed correlation spectroscopy Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- 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/1425—Charging, metering or billing arrangements for data wireline or wireless communications involving dedicated fields in the data packet for billing purposes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
-
- 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/1432—Metric aspects
-
- 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
-
- 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/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
-
- 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/64—On-line charging system [OCS]
-
- 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
- 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/8221—Message based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
Definitions
- the present invention relates to charging for SDT (Small Data Transmission) and device trigger in MTC (Machine-Type-Communication).
- NPL 1 there are few descriptions of an MME (Mobility Management) or an MTC-IWF (MTC Inter-Working Function) generating a CDR (Charging Data Record) for SDT and MTC device trigger.
- MME Mobility Management
- MTC-IWF MTC Inter-Working Function
- NPL 2 discloses charging over user plane, but does not at all disclose the charging over the control plane.
- an exemplary object of the present invention is to provide a solution for charging SDT and MTC device trigger over control plane.
- a network node includes: relay means for relaying messages over a control plane between an MTC device and an SCS (Service Capability Server); count means for counting the number of messages successfully relayed; and generation means for generating a CDR in accordance with the counted number.
- the messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- a communication system includes: an MTC device; an SCS; and a network node that relays messages over a control plane between the MTC device and the SCS.
- the network node is configured to: count the number of messages successfully relayed; and generate a CDR in accordance with the counted number.
- the messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- a method according to third exemplary aspect of the present invention provides a method of controlling operations in a network node that relays messages over a control plane between an MTC device and an SCS.
- This method includes: counting the number of messages successfully relayed; and generating a CDR in accordance with the counted number.
- the messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- FIG. 1 is a block diagram showing a configuration example of a communication system according to an exemplary embodiment of the present invention.
- FIG. 2 is a sequence diagram showing an operation example of the communication system according to the exemplary embodiment.
- FIG. 3 is a sequence diagram showing another operation example of the communication system according to the exemplary embodiment.
- FIG. 4 is a block diagram showing a configuration example of a network node according to the exemplary embodiment.
- the SDT supports the message size of up to 1 kB.
- Some typical examples of small data include a measurement value of a sensor or meter, and sales in a vending machine.
- the MTC device trigger is a message for causing an MTC device to communicate with an SCS.
- the MTC device is a UE equipped for MTC, which will be sometimes referred to as “MTC UE” or “UE” in the following explanation.
- the MTC-IWF can generate CDRs for SDT and MTC device trigger.
- This exemplary embodiment introduces the solution for the MTC-IWF to generate and deliver CDRs.
- the architecture is shown in FIG. 1 .
- a communication system includes a core network (3GPP network), one or more MTC UEs 10 which connect to the core network through a RAN (Radio Access Network), and an SCS 50 which is placed outside the core network.
- a core network 3GPP network
- MTC UEs 10 which connect to the core network through a RAN (Radio Access Network)
- an SCS 50 which is placed outside the core network.
- the RAN is formed by a plurality of base stations (e.g., eNBs (evolved Node Bs)).
- the MTC UE 10 attaches to the core network.
- the MTC UE 10 can host one or multiple MTC Applications.
- the corresponding MTC Applications in the external network are hosted on the SCS 50 .
- the SCS 50 connects to the core network to communicate with the MTC UE 10 .
- the core network includes, as a part of its network nodes, an MME 20 , an OCF (Online Charging Function) 31 for online charging, a CDF (Charging Data Function) 32 for offline charging, and an MTC-IWF 40 .
- the core network also includes, as other network nodes, an SGSN (Serving GPRS (General Packet Radio Service) Support Node), an HSS (Home Subscriber Server), a CGF (Charging Gateway Function) and the like.
- the HSS manages subscription information on the MTC UE 10 , and the like.
- the MME 20 relays traffic between the RAN and the MTC-IWF 40 .
- the SGSN functions as with the MME 20 .
- the OCF 31 and the CDF 32 are connected to the CGF. Note that in the following description, the OCF 31 and the CDF 32 are sometimes referred to as “OCF/CDF”, and collectively denoted by the symbol 30 .
- the MTC-IWF 40 serves as an entering point to the core network for the SCS 50 , and relays messages over control plane (reference points “T 5 ” and “Tsp”) between the MTC UE 10 and the SCS 50 .
- the MTC-IWF 40 records MTC device trigger, and MO (Mobile Originated) and MT (Mobile Terminated) SDT.
- the MTC-IWF 40 generates and transfers the CDRs to the OCF 31 for online charging or to the CDF 32 for offline charging.
- a reference point “Roi” resides between the MTC-IWF 40 and the OCF 31 for online charging.
- a reference point “Rfi” resides between the MTC-IWF 40 and the CDF 32 for offline charging.
- the MTC-IWF 40 is configured with the address of the OCF 31 or the CDF 32 , this can be decided by the operator such that the MTC-IWF 40 can distinguish whether it is online or offline charging.
- the MTC-IWF 40 Upon receiving a SDT message or an MTC device trigger message, the MTC-IWF 40 verifies whether the message carries SD (Small Data) or device trigger, and the payload size, in order to generate CDR properly.
- SD Small Data
- the MTC-IWF 40 is configured with a counter for charging purpose.
- uplink SD from UE MO-SD
- MT-SD downlink SD
- TAGGER MTC device trigger
- the CDRs are defined according to the event trigger: MO-SD-CDR, MT-SD-CDR and TRIGGER-CDR.
- the generation of the CDRs is triggered by successful delivery of small data in MO or MT direction and MTC device trigger.
- the MO-SD-CDR is used to collect charging information related to the transmission of SD in MO direction via the MTC-IWF 40 on behalf of the MTC UE 10 .
- the event trigger for MO-SD-CDR generation is when the MTC-IWF 40 receives MO SD transmission ACK (Acknowledgement) from the SCS 50 .
- the MO-SD-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available.
- the MT-SD-CDR is used to collect charging information related to the transmission of SD in MT direction via the MTC-IWF 40 on behalf of the SCS 50 .
- the event trigger for MT-SD-CDR generation is when the MTC-IWF 40 receives MT SD transmission ACK from the MTC UE 10 .
- the MT-SD-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available.
- the TRIGGER-CDR is used to collect charging information related to the delivery of MTC device trigger in downlink direction via the MTC-IWF 40 on behalf of the SCS 50 .
- the event trigger for TRIGGER-CDR generation is when the MTC-IWF 40 receives MTC device trigger delivery ACK from the eNB.
- the TRIGGER-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available.
- a Record Type field indicates which ones of MO SD messages, MT SD messages and MTC device triggers are counted for generating the CDR.
- a UE Identifier field indicates an identifier of the MTC UE 10 .
- An Online/offline field indicates that the CDR is delivered for online or offline.
- An SCS info field indicates information and/or an address of the SCS 50 .
- a Serving Node (MTC-IWF) field indicates information and/or an address of the MTC-IWF 40 .
- a User Location Information field indicates user location information from which the message is originated.
- a Message Reference field indicates a reference for uniquely identifying the CDR.
- An Event Time Stamp field indicates the time at which the message is received by the MTC-IWF 40 .
- a Counter field indicates a value of the counter.
- the MTC-IWF in VPLMN may be configured to record and count MTC device trigger, MO and MT SDT, generate and deliver CDRs.
- the mechanism is the same as the non-roaming case.
- the MTC-IWF 40 is configured with charging conditions for MO SDT, which includes the SD payload size, counter computation timing, CDR generation and transfer timing.
- Step S 1 configuration for charging condition and timing is performed in the MTC-IWF 40 (Step S 1 ).
- the MTC-IWF can generate a COUNTER for the UE subscribed service.
- An initial value of the COUNTER is set with “0”.
- the MTC-IWF 40 receives SDT message from the MTC UE 10 (Step S 2 ).
- the MTC-IWF 40 verifies whether or not the received message should be charged (Step S 3 ).
- the MTC-IWF 40 performs the verification based on an indicator which is included in the received message, and which indicates that the received message is the MO SD message, the MT SD message, the MTC device trigger or a different message. In this case, it is possible to simply perform the verification.
- the MTC-IWF 40 may perform the verification further based on the actual size of the received message. As described above, the size of SD message is less than or equal to 1 kB. Therefore, the MTC-IWF 40 determines that the received message should be charged when the actual size is less than or equal to 1 kB. In this case, it is prevent a malicious user from falsifying an indicator in a large size message, which should be charged at a metered rate, for the purpose of receiving services at low cost.
- the MTC-IWF 40 may perform the verification further based on whether or not the MTC device 10 and the SCS 50 are authorized to communicate with each other.
- the MTC-IWF 40 determines that the received message should be charged when both of the MTC device 10 and the SCS 50 have been authorized. In this case, it is possible to prevent charging due to malicious attacks or the like.
- the MTC-IWF 40 delivers the SDT message to the SCS 50 (Step S 4 ).
- the SCS 50 responds a Small Data Transmission ACK message, upon successfully receiving the SDT message (Step S 5 ).
- the MTC-IWF 40 performs counter computation upon receiving the Small Data Transmission ACK message from the SCS 50 (Step 6 ). Specifically, the MTC-IWF 40 increments the COUNTER by “1”.
- Step S 7 The above-mentioned Steps S 2 to S 6 are repeated if any small data transmission needed.
- the MTC-IWF 40 After that, the MTC-IWF 40 generates the MO-SD-CDR, at pre-configured timing (Step S 8 ).
- the MTC-IWF 40 transfers the generated CDR to OCF/CDF 30 at pre-configured timing (Step S 9 ).
- Step S 11 configuration for charging condition and timing is performed in the MTC-IWF 40 (Step S 11 ).
- the MTC-IWF can generate a COUNTER for the UE subscribed service.
- An initial value of the COUNTER is set with “0”.
- the MTC-IWF 40 receives a MTC device trigger message or a SDT message from the SCS 50 (Step S 12 ).
- the MTC-IWF 40 verifies whether or not the received message should be charged (Step S 13 ). This verification can be performed in a similar manner to that in FIG. 2 .
- the MTC-IWF 40 delivers the MTC device trigger message or the SDT message to the MTC UE 10 (Step S 14 ).
- the MTC UE 10 responds a MTC device trigger ACK message or a Small Data Transmission ACK message, upon successfully receiving the MTC device trigger message or the SDT message (Step S 15 ).
- the MTC-IWF 40 performs counter computation upon receiving the MTC device trigger ACK message or the Small Data Transmission ACK message from the MTC UE 10 (Step 16 ). Specifically, the MTC-IWF 40 increments the COUNTER by “1”.
- Step S 12 to S 16 are repeated if any MTC device trigger or Small Data Transmission needed (Step S 17 ).
- the MTC-IWF 40 After that, the MTC-IWF 40 generates the MT-SD-CDR or the TRIGGER-CDR, at pre-configured timing (Step S 18 ).
- the MTC-IWF 40 transfers the generated CDR to OCF/CDF 30 at pre-configured timing (Step S 19 ).
- the MTC-IWF it is possible to provide the solution for the MTC-IWF to generate and deliver CDRs for charging of SDT and MTC device trigger. Since small data and MTC device triggers packets only have limited size, there is no need to charge the MTC UE based on packet size but numbers of how many SDT or MTC device trigger are being successfully delivered.
- the MTC-IWF can simply have a counter for MO/MT SDT and MTC device trigger charging.
- the MTC-IWF 40 includes a relay unit 41 , a count unit 42 , and a generation unit 43 .
- the relay unit 41 relays MO SD messages, MT SD messages or MTC device trigger messages over the control plane between the MTC UE 10 and the SCS 50 .
- the count unit 42 counts the number of messages successfully relayed by using e.g., the abovementioned COUNTER.
- the generation unit 43 generates the MO-SD-CDR, the MT-SD-CDR or the TRIGGER-CDR in accordance with the counted number.
- the MTC-IWF 40 can include a transfer unit 44 which transfers the generated CDR to the OCF/CDF 30 .
- these units 41 to 44 are mutually connected with each other through a bus or the like.
- These units 41 to 44 can be configured by, for example, transceivers which conduct communication with the MTC UE 10 , the SCS 50 , the OCF/CDF 30 and other network nodes within the core network, and a controller such as a CPU (Central Processing Unit) which controls these transceivers.
- a controller such as a CPU (Central Processing Unit) which controls these transceivers.
- New interfaces (Roi and Rfi) between MTC-IWF and OCF/CDF are defined for CDRs delivery.
- MTC-IWF is configured with address of OCF or CDF.
- the counters are defined and configured in MTC-IWF for MO and MT SDT or MTC device trigger delivery charging.
- MTC-IWF records the information for charging.
- MTC-IWF is configured with event triggers for CDRs generation such that it determines which CDR to generate.
- New CDRs are defined: MO-SD-CDR for MO SDT charging, MT-SD-CDR for MT SDT charging and TRIGGER-CDR for MTC device trigger delivery charging.
- MTC-IWF delivers the CDR type, Counter, UE identifier and subscriber ID if available in CDRs to OCF or CDF for online and offline charging separately, over the newly defined interfaces.
Abstract
Description
- The present application is a continuation of U.S. application Ser. No. 16/518,805 filed Jul. 22, 2019, which is a continuation of U.S. application Ser. No. 15/021,492 filed Mar. 11, 2016, which is a U.S. National Phase of International Application No. PCT/JP2014/004073 filed Aug. 4, 2014, which is based upon and claims the benefit of priority from Japanese Application No. 2013-189776 filed Sep. 12, 2013, the disclosure of all of which are incorporated by reference herein in its entirety.
- The present invention relates to charging for SDT (Small Data Transmission) and device trigger in MTC (Machine-Type-Communication).
- In NPL 1, the study of SDT has a high priority. Moreover, SDT over control plane has been agreed in 3GPP (3rd Generation Partnership Project). Therefore, Charging the SDT over control plane becomes an issue.
-
- NPL 1: 3GPP TR 23.887, “Machine-Type and other Mobile Data Applications Communications Enhancements (Release 12)”, V1.0.0, 2013-06, Clauses 5.1.1.3.3.1.4 and 5.2.2.3.1.1.2, pp. 23 and 76
- NPL 2: 3GPP TS 32.240, “Telecommunication management; Charging management; Charging architecture and principles (Release 12)”, V12.0.0, 2013-03, Clauses 4.1.1 and 4.1.2, pp. 16
- In NPL 1, there are few descriptions of an MME (Mobility Management) or an MTC-IWF (MTC Inter-Working Function) generating a CDR (Charging Data Record) for SDT and MTC device trigger.
- However, in NPL 1, there is no detail of how the CDR can be generated and transferred.
- Note that NPL 2 discloses charging over user plane, but does not at all disclose the charging over the control plane.
- Accordingly, an exemplary object of the present invention is to provide a solution for charging SDT and MTC device trigger over control plane.
- In order to achieve the above-mentioned object, a network node according to first exemplary aspect of the present invention includes: relay means for relaying messages over a control plane between an MTC device and an SCS (Service Capability Server); count means for counting the number of messages successfully relayed; and generation means for generating a CDR in accordance with the counted number. The messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- Further, a communication system according to second exemplary aspect of the present invention includes: an MTC device; an SCS; and a network node that relays messages over a control plane between the MTC device and the SCS. The network node is configured to: count the number of messages successfully relayed; and generate a CDR in accordance with the counted number. The messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- Furthermore, a method according to third exemplary aspect of the present invention provides a method of controlling operations in a network node that relays messages over a control plane between an MTC device and an SCS. This method includes: counting the number of messages successfully relayed; and generating a CDR in accordance with the counted number. The messages are: first messages delivered from the MTC device to the SCS, the size of the first message being equal to or smaller than a predetermined size; second messages delivered from the SCS to the MTC device, the size of the second message being equal to or smaller than the predetermined size; or trigger messages delivered from the SCS to the MTC device, the trigger message being for causing the MTC device to communicate with the SCS.
- According to the present invention, it is possible to solve the above-mentioned problems, and thus to provide a solution for charging SDT and MTC device trigger over control plane.
-
FIG. 1 is a block diagram showing a configuration example of a communication system according to an exemplary embodiment of the present invention. -
FIG. 2 is a sequence diagram showing an operation example of the communication system according to the exemplary embodiment. -
FIG. 3 is a sequence diagram showing another operation example of the communication system according to the exemplary embodiment. -
FIG. 4 is a block diagram showing a configuration example of a network node according to the exemplary embodiment. - Hereinafter, an exemplary embodiment of the present invention will be described with the accompany drawings.
- In this exemplary embodiment, there will be proposed solutions for charging SDT and MTC device trigger for both non-roaming and roaming UEs (User Equipments). The solutions can also be applied to other communications that are transferred through an MTC-IWF. Moreover, there will be introduced new interfaces for charging. This can also be applied to any other data delivered over T5 that an operator wants to charge.
- For example in 3GPP, the SDT supports the message size of up to 1 kB. Some typical examples of small data include a measurement value of a sensor or meter, and sales in a vending machine. The MTC device trigger is a message for causing an MTC device to communicate with an SCS. The MTC device is a UE equipped for MTC, which will be sometimes referred to as “MTC UE” or “UE” in the following explanation.
- As disclosed in NPL 1, the MTC-IWF can generate CDRs for SDT and MTC device trigger. This exemplary embodiment introduces the solution for the MTC-IWF to generate and deliver CDRs. The architecture is shown in
FIG. 1 . - As shown in
FIG. 1 , a communication system according to this exemplary embodiment includes a core network (3GPP network), one or more MTC UEs 10 which connect to the core network through a RAN (Radio Access Network), and anSCS 50 which is placed outside the core network. Note that although the illustration is omitted, the RAN is formed by a plurality of base stations (e.g., eNBs (evolved Node Bs)). - The MTC UE 10 attaches to the core network. The MTC UE 10 can host one or multiple MTC Applications. The corresponding MTC Applications in the external network are hosted on the
SCS 50. The SCS 50 connects to the core network to communicate with the MTC UE 10. - Further, the core network includes, as a part of its network nodes, an
MME 20, an OCF (Online Charging Function) 31 for online charging, a CDF (Charging Data Function) 32 for offline charging, and an MTC-IWF 40. The core network also includes, as other network nodes, an SGSN (Serving GPRS (General Packet Radio Service) Support Node), an HSS (Home Subscriber Server), a CGF (Charging Gateway Function) and the like. The HSS manages subscription information on the MTC UE 10, and the like. - The
MME 20 relays traffic between the RAN and the MTC-IWF 40. The SGSN functions as with theMME 20. - The OCF 31 and the CDF 32 are connected to the CGF. Note that in the following description, the
OCF 31 and theCDF 32 are sometimes referred to as “OCF/CDF”, and collectively denoted by thesymbol 30. - As with a typical MTC-IWF, the MTC-IWF 40 serves as an entering point to the core network for the
SCS 50, and relays messages over control plane (reference points “T5” and “Tsp”) between the MTC UE 10 and theSCS 50. Meanwhile, different from the typical MTC-IWF, the MTC-IWF 40 records MTC device trigger, and MO (Mobile Originated) and MT (Mobile Terminated) SDT. Moreover, the MTC-IWF 40 generates and transfers the CDRs to theOCF 31 for online charging or to theCDF 32 for offline charging. - A reference point “Roi” resides between the MTC-
IWF 40 and theOCF 31 for online charging. A reference point “Rfi” resides between the MTC-IWF 40 and theCDF 32 for offline charging. In order to deliver the CDRs, the MTC-IWF 40 is configured with the address of theOCF 31 or theCDF 32, this can be decided by the operator such that the MTC-IWF 40 can distinguish whether it is online or offline charging. - There is proposed to pre-configure rules for charging in the MTC-
IWF 40. Upon receiving a SDT message or an MTC device trigger message, the MTC-IWF 40 verifies whether the message carries SD (Small Data) or device trigger, and the payload size, in order to generate CDR properly. - MTC device trigger and small data have limited packet size, thus the charging should depend on how many MTC device triggers or SD are being successfully delivered. Thus, the MTC-
IWF 40 is configured with a counter for charging purpose. - There is proposed to create three kinds of event: uplink SD from UE (MO-SD), downlink SD (MT-SD), and MTC device trigger (TRIGGER).
- The CDRs are defined according to the event trigger: MO-SD-CDR, MT-SD-CDR and TRIGGER-CDR. The generation of the CDRs is triggered by successful delivery of small data in MO or MT direction and MTC device trigger.
- The MO-SD-CDR is used to collect charging information related to the transmission of SD in MO direction via the MTC-
IWF 40 on behalf of theMTC UE 10. The event trigger for MO-SD-CDR generation is when the MTC-IWF 40 receives MO SD transmission ACK (Acknowledgement) from theSCS 50. The MO-SD-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available. - The MT-SD-CDR is used to collect charging information related to the transmission of SD in MT direction via the MTC-
IWF 40 on behalf of theSCS 50. The event trigger for MT-SD-CDR generation is when the MTC-IWF 40 receives MT SD transmission ACK from theMTC UE 10. The MT-SD-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available. - The TRIGGER-CDR is used to collect charging information related to the delivery of MTC device trigger in downlink direction via the MTC-
IWF 40 on behalf of theSCS 50. The event trigger for TRIGGER-CDR generation is when the MTC-IWF 40 receives MTC device trigger delivery ACK from the eNB. The TRIGGER-CDR includes details such as CDR type, Counter, UE identifier and subscriber ID if available. - The following Table. 1 gives an example of fields in the CDR.
-
TABLE 1 Field Description Record Type MO SD; MT SD; MTC device trigger UE Identifier Identifier of MTC UE Online/offline Being delivered online or offline SCS info Information/address of SCS Serving Node (MTC-IWF) Information/address of MTC-IWF User Location User Location Information from Information which message originated Message Reference Reference provided uniquely identifying CDR Event Time Stamp Time at which message is received by MTC-IWF Counter Value of counter - In the Table. 1, a Record Type field indicates which ones of MO SD messages, MT SD messages and MTC device triggers are counted for generating the CDR. A UE Identifier field indicates an identifier of the
MTC UE 10. An Online/offline field indicates that the CDR is delivered for online or offline. An SCS info field indicates information and/or an address of theSCS 50. A Serving Node (MTC-IWF) field indicates information and/or an address of the MTC-IWF 40. A User Location Information field indicates user location information from which the message is originated. A Message Reference field indicates a reference for uniquely identifying the CDR. An Event Time Stamp field indicates the time at which the message is received by the MTC-IWF 40. A Counter field indicates a value of the counter. - Note that in a case of using Diameter message for charging, same as other PCNs (Packet switched Core network Nodes), new field of MTC-information may be added to Service-Information (see 3GPP TS 32.299) in Diameter Credit Control and Accounting-Request Message.
- In a case where there is an MTC-IWF in VPLMN (Visited PLMN (Public Land Mobile Network)), the MTC-IWF in VPLMN (V-MTC-IWF) may be configured to record and count MTC device trigger, MO and MT SDT, generate and deliver CDRs. The mechanism is the same as the non-roaming case.
- Next, operation examples of this exemplary embodiment will be described in detail with reference to
FIGS. 2 and 3 . Note that a configuration example of theMTC 40 will be described later with reference toFIG. 4 . - In a case of generating a CDR for MO SDT, the MTC-
IWF 40 is configured with charging conditions for MO SDT, which includes the SD payload size, counter computation timing, CDR generation and transfer timing. - Specifically, as shown in
FIG. 2 , configuration for charging condition and timing is performed in the MTC-IWF 40 (Step S1). When theMTC UE 10 is attached and authenticated to the core network and the MTC-IWF 40, the MTC-IWF can generate a COUNTER for the UE subscribed service. An initial value of the COUNTER is set with “0”. - After that, the MTC-
IWF 40 receives SDT message from the MTC UE 10 (Step S2). - At this time, the MTC-
IWF 40 verifies whether or not the received message should be charged (Step S3). - For example, the MTC-
IWF 40 performs the verification based on an indicator which is included in the received message, and which indicates that the received message is the MO SD message, the MT SD message, the MTC device trigger or a different message. In this case, it is possible to simply perform the verification. - The MTC-
IWF 40 may perform the verification further based on the actual size of the received message. As described above, the size of SD message is less than or equal to 1 kB. Therefore, the MTC-IWF 40 determines that the received message should be charged when the actual size is less than or equal to 1 kB. In this case, it is prevent a malicious user from falsifying an indicator in a large size message, which should be charged at a metered rate, for the purpose of receiving services at low cost. - The MTC-
IWF 40 may perform the verification further based on whether or not theMTC device 10 and theSCS 50 are authorized to communicate with each other. The MTC-IWF 40 determines that the received message should be charged when both of theMTC device 10 and theSCS 50 have been authorized. In this case, it is possible to prevent charging due to malicious attacks or the like. - If the MTC-
IWF 40 has succeeded in the verification, the MTC-IWF 40 delivers the SDT message to the SCS 50 (Step S4). - The
SCS 50 responds a Small Data Transmission ACK message, upon successfully receiving the SDT message (Step S5). - The MTC-
IWF 40 performs counter computation upon receiving the Small Data Transmission ACK message from the SCS 50 (Step 6). Specifically, the MTC-IWF 40 increments the COUNTER by “1”. - The above-mentioned Steps S2 to S6 are repeated if any small data transmission needed (Step S7).
- After that, the MTC-
IWF 40 generates the MO-SD-CDR, at pre-configured timing (Step S8). - Then, the MTC-
IWF 40 transfers the generated CDR to OCF/CDF 30 at pre-configured timing (Step S9). - In a case of generating a CDR for MTC device trigger or MT SDT, as shown in
FIG. 3 , configuration for charging condition and timing is performed in the MTC-IWF 40 (Step S11). When theMTC UE 10 is attached and authenticated to the core network and the MTC-IWF 40, the MTC-IWF can generate a COUNTER for the UE subscribed service. An initial value of the COUNTER is set with “0”. - After that, the MTC-
IWF 40 receives a MTC device trigger message or a SDT message from the SCS 50 (Step S12). - At this time, the MTC-
IWF 40 verifies whether or not the received message should be charged (Step S13). This verification can be performed in a similar manner to that inFIG. 2 . - If the MTC-
IWF 40 has succeeded in the verification, the MTC-IWF 40 delivers the MTC device trigger message or the SDT message to the MTC UE 10 (Step S14). - The
MTC UE 10 responds a MTC device trigger ACK message or a Small Data Transmission ACK message, upon successfully receiving the MTC device trigger message or the SDT message (Step S15). - The MTC-
IWF 40 performs counter computation upon receiving the MTC device trigger ACK message or the Small Data Transmission ACK message from the MTC UE 10 (Step 16). Specifically, the MTC-IWF 40 increments the COUNTER by “1”. - The above-mentioned Steps S12 to S16 are repeated if any MTC device trigger or Small Data Transmission needed (Step S17).
- After that, the MTC-
IWF 40 generates the MT-SD-CDR or the TRIGGER-CDR, at pre-configured timing (Step S18). - Then, the MTC-
IWF 40 transfers the generated CDR to OCF/CDF 30 at pre-configured timing (Step S19). - According to this exemplary embodiment, it is possible to provide the solution for the MTC-IWF to generate and deliver CDRs for charging of SDT and MTC device trigger. Since small data and MTC device triggers packets only have limited size, there is no need to charge the MTC UE based on packet size but numbers of how many SDT or MTC device trigger are being successfully delivered. The MTC-IWF can simply have a counter for MO/MT SDT and MTC device trigger charging.
- Next, a configuration example of the MTC-
IWF 40 according to this exemplary embodiment will be described with reference toFIG. 4 . - As show in
FIG. 4 , the MTC-IWF 40 includes arelay unit 41, acount unit 42, and ageneration unit 43. Therelay unit 41 relays MO SD messages, MT SD messages or MTC device trigger messages over the control plane between theMTC UE 10 and theSCS 50. Thecount unit 42 counts the number of messages successfully relayed by using e.g., the abovementioned COUNTER. Thegeneration unit 43 generates the MO-SD-CDR, the MT-SD-CDR or the TRIGGER-CDR in accordance with the counted number. The MTC-IWF 40 can include atransfer unit 44 which transfers the generated CDR to the OCF/CDF 30. Note that theseunits 41 to 44 are mutually connected with each other through a bus or the like. Theseunits 41 to 44 can be configured by, for example, transceivers which conduct communication with theMTC UE 10, theSCS 50, the OCF/CDF 30 and other network nodes within the core network, and a controller such as a CPU (Central Processing Unit) which controls these transceivers. - Note that the present invention is not limited to the above-mentioned exemplary embodiment, and it is obvious that various modifications can be made by those of ordinary skill in the art based on the recitation of the claims.
- The whole or part of the exemplary embodiment disclosed above can be described as, but not limited to, the following supplementary notes.
- New interfaces (Roi and Rfi) between MTC-IWF and OCF/CDF are defined for CDRs delivery.
- MTC-IWF is configured with address of OCF or CDF.
- The counters are defined and configured in MTC-IWF for MO and MT SDT or MTC device trigger delivery charging.
- MTC-IWF records the information for charging.
- MTC-IWF is configured with event triggers for CDRs generation such that it determines which CDR to generate.
- New CDRs are defined: MO-SD-CDR for MO SDT charging, MT-SD-CDR for MT SDT charging and TRIGGER-CDR for MTC device trigger delivery charging.
- MTC-IWF delivers the CDR type, Counter, UE identifier and subscriber ID if available in CDRs to OCF or CDF for online and offline charging separately, over the newly defined interfaces.
- This application is based upon and claims the benefit of priority from Japanese patent application No. 2013-189776, filed on Sep. 12, 2013, the disclosure of which is incorporated herein in its entirety by reference.
-
- 10 MTC UE
- 20 MME
- 30 OCF/CDF
- 31 OCF
- 32 CDF
- 40 MTC-IWF
- 41 RELAY UNIT
- 42 COUNT UNIT
- 43 GENERATION UNIT
- 44 TRANSFER UNIT
- 50 SCS
Claims (6)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/921,608 US20200336320A1 (en) | 2013-09-12 | 2020-07-06 | Charging for mtc small data transmission and trigger at mtc-iwf |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-189776 | 2013-09-12 | ||
JP2013189776 | 2013-09-12 | ||
PCT/JP2014/004073 WO2015037181A1 (en) | 2013-09-12 | 2014-08-04 | Charging for mtc small data transmission and trigger at mtc-iwf |
US201615021492A | 2016-03-11 | 2016-03-11 | |
US16/518,805 US20200014548A1 (en) | 2013-09-12 | 2019-07-22 | Charging for mtc small data transmission and trigger at mtc-iwf |
US16/921,608 US20200336320A1 (en) | 2013-09-12 | 2020-07-06 | Charging for mtc small data transmission and trigger at mtc-iwf |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/518,805 Continuation US20200014548A1 (en) | 2013-09-12 | 2019-07-22 | Charging for mtc small data transmission and trigger at mtc-iwf |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200336320A1 true US20200336320A1 (en) | 2020-10-22 |
Family
ID=51626116
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/021,492 Active US10404479B2 (en) | 2013-09-12 | 2014-08-04 | Charging for MTC small data transmission and trigger at MTC-IWF |
US16/518,805 Abandoned US20200014548A1 (en) | 2013-09-12 | 2019-07-22 | Charging for mtc small data transmission and trigger at mtc-iwf |
US16/921,608 Pending US20200336320A1 (en) | 2013-09-12 | 2020-07-06 | Charging for mtc small data transmission and trigger at mtc-iwf |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/021,492 Active US10404479B2 (en) | 2013-09-12 | 2014-08-04 | Charging for MTC small data transmission and trigger at MTC-IWF |
US16/518,805 Abandoned US20200014548A1 (en) | 2013-09-12 | 2019-07-22 | Charging for mtc small data transmission and trigger at mtc-iwf |
Country Status (5)
Country | Link |
---|---|
US (3) | US10404479B2 (en) |
EP (1) | EP3044946B1 (en) |
JP (5) | JP6489121B2 (en) |
CN (3) | CN111314093B (en) |
WO (1) | WO2015037181A1 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10805830B2 (en) * | 2015-08-14 | 2020-10-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Systems and methods for regulating user data traffic in a wireless network |
CN106851526B (en) * | 2015-12-07 | 2022-09-09 | 阿尔卡特朗讯 | Method and equipment for processing MTC (machine type communication) message |
US10805036B2 (en) | 2016-02-18 | 2020-10-13 | Telefonaktiebolaget Lm Ericsson (Publ) | System, methods, and apparatuses for managing data rate for control plane optimization |
US10959066B2 (en) | 2017-02-23 | 2021-03-23 | Nokia Technologies Oy | Method and system for access protocol optimization for narrow band Internet-of-Things devices within a network environment |
WO2020074054A1 (en) * | 2018-10-08 | 2020-04-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatuses for balancing utilization of computer resources |
WO2020177852A1 (en) * | 2019-03-04 | 2020-09-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and systems for rule based charging for internet of things (iot) support |
WO2023039732A1 (en) * | 2021-09-14 | 2023-03-23 | Nec Corporation | Method, device and computer storage medium of communication |
WO2023115350A1 (en) * | 2021-12-21 | 2023-06-29 | Lenovo (Beijing) Limited | Enhanced mechanism on uu interface for mt sdt |
WO2024020991A1 (en) * | 2022-07-29 | 2024-02-01 | Qualcomm Incorporated | Resource configuration and selection for downlink small data transmissions |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130303206A1 (en) * | 2012-05-11 | 2013-11-14 | Interdigital Patent Holdings, Inc. | Service capability server (scs) terminated short message service (sms) systems and methods |
US20140092808A1 (en) * | 2012-09-28 | 2014-04-03 | Puneet K. Jain | Machine type communication monitoring framework for 3gpp systems |
US20150172909A1 (en) * | 2012-06-22 | 2015-06-18 | Nokia Solutions And Networks Oy | Machine type communication interworking function |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8982790B2 (en) * | 2009-11-24 | 2015-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Overcharging prevention by unsent downlink data volume record |
CN102111739A (en) | 2009-12-24 | 2011-06-29 | 中兴通讯股份有限公司 | MTC charging method and system |
CN102238520B (en) * | 2010-04-26 | 2014-12-31 | 中兴通讯股份有限公司 | Method and system for transmitting small data packets |
KR20110121977A (en) | 2010-05-03 | 2011-11-09 | 삼성전자주식회사 | Mobile communication and method for managing signaling message thereof |
MX2013002587A (en) | 2010-09-09 | 2013-11-04 | Headwater Partners I Llc | Wireless network service interfaces. |
GB201117072D0 (en) | 2011-10-04 | 2011-11-16 | Vodafone Ip Licensing Ltd | Use of non e.164 msisdns |
MX336515B (en) * | 2011-10-28 | 2016-01-22 | Nec Corp | Secure method for mtc device triggering. |
CN103327464B (en) * | 2012-03-22 | 2018-08-24 | 中兴通讯股份有限公司 | A kind of charging method and system, information processing entity of MTC communication |
WO2013189708A1 (en) * | 2012-06-22 | 2013-12-27 | Nokia Siemens Networks Oy | Machine type communication interworking function |
US9699323B2 (en) * | 2013-06-28 | 2017-07-04 | Alcatel Lucent | Separate charging for supplemental content in a data flow |
-
2014
- 2014-08-04 CN CN202010101238.9A patent/CN111314093B/en active Active
- 2014-08-04 WO PCT/JP2014/004073 patent/WO2015037181A1/en active Application Filing
- 2014-08-04 CN CN201480050377.6A patent/CN105532022B/en active Active
- 2014-08-04 CN CN202010100819.0A patent/CN111147267B/en active Active
- 2014-08-04 JP JP2016512145A patent/JP6489121B2/en active Active
- 2014-08-04 US US15/021,492 patent/US10404479B2/en active Active
- 2014-08-04 EP EP14776744.6A patent/EP3044946B1/en active Active
-
2019
- 2019-02-28 JP JP2019035061A patent/JP7088554B2/en active Active
- 2019-02-28 JP JP2019035059A patent/JP2019146170A/en active Pending
- 2019-02-28 JP JP2019035060A patent/JP2019146171A/en active Pending
- 2019-07-22 US US16/518,805 patent/US20200014548A1/en not_active Abandoned
-
2020
- 2020-07-06 US US16/921,608 patent/US20200336320A1/en active Pending
-
2021
- 2021-02-19 JP JP2021025710A patent/JP7188475B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130303206A1 (en) * | 2012-05-11 | 2013-11-14 | Interdigital Patent Holdings, Inc. | Service capability server (scs) terminated short message service (sms) systems and methods |
US20150172909A1 (en) * | 2012-06-22 | 2015-06-18 | Nokia Solutions And Networks Oy | Machine type communication interworking function |
US20140092808A1 (en) * | 2012-09-28 | 2014-04-03 | Puneet K. Jain | Machine type communication monitoring framework for 3gpp systems |
Also Published As
Publication number | Publication date |
---|---|
JP7188475B2 (en) | 2022-12-13 |
CN105532022A (en) | 2016-04-27 |
CN111314093A (en) | 2020-06-19 |
JP2019146171A (en) | 2019-08-29 |
JP2019146172A (en) | 2019-08-29 |
US10404479B2 (en) | 2019-09-03 |
US20200014548A1 (en) | 2020-01-09 |
JP7088554B2 (en) | 2022-06-21 |
JP2021078161A (en) | 2021-05-20 |
EP3044946A1 (en) | 2016-07-20 |
CN111147267B (en) | 2022-06-07 |
EP3044946B1 (en) | 2020-06-17 |
JP2016535467A (en) | 2016-11-10 |
JP2019146170A (en) | 2019-08-29 |
JP6489121B2 (en) | 2019-03-27 |
US20160226668A1 (en) | 2016-08-04 |
WO2015037181A1 (en) | 2015-03-19 |
CN105532022B (en) | 2020-07-10 |
CN111314093B (en) | 2022-10-04 |
CN111147267A (en) | 2020-05-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200336320A1 (en) | Charging for mtc small data transmission and trigger at mtc-iwf | |
WO2017088501A1 (en) | Charging method and device | |
EP2957096B1 (en) | Method, apparatus and system for aggregating charging information | |
EP2599340B1 (en) | Machine-type communication subscription control | |
KR20170094333A (en) | Charging in the integrated small cell/wi-fi networks (iswn) | |
US20180183938A1 (en) | Charging for usage of radio resources that are shared between mtc traffic and non-mtc traffic | |
CN107925908B (en) | System and method for managing user data traffic in a wireless network | |
CN103517245B (en) | A kind of charging method and system of D2D communications | |
KR20170077172A (en) | Methods and apparatuses for service layer charging correlation with underlying networks | |
EP2314039B1 (en) | Communication system | |
WO2015022764A1 (en) | Wireless communication system and method for fee charging control | |
US20150071128A1 (en) | Mobile communication system, gateway device, charging policy control method, and non-transitory computer readable medium storing program | |
KR20110121977A (en) | Mobile communication and method for managing signaling message thereof | |
JP6488405B2 (en) | Method and apparatus for performing online charging to GCS | |
KR101964431B1 (en) | System and method for charging loaming data for preventing billing error |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |