Charging over a user-deployed relay
Network entities in a wireless network cooperate to account and charge for data communicated over the wireless network. Accounting and charging enable the network entities to properly allocate charges to a second user equipment that communicates through a first user equipment, which acts as a relay in the wireless network. A network entity receives a request from the first user equipment related to a packet data network connection relating to the second user equipment. The network entity establishes or modifies a connection between a gateway and the first user equipment in response to the request. Charges for the data may be allocated to the second user equipment for data communicated with the identifier of the second user equipment.
1. A method of wireless communication by a user equipment (UE), comprising:
establishing a wireless communication with a Terminal User Equipment (TUE), wherein the UE provides a packet data network (PDN) connection to a packet data gateway (PGW) for the TUE;
identifying the TUE based on a traffic flow template (TFT) to determine an identifier associated with the TUE;
identifying a service flow corresponding to the TFT by the identifier, wherein the service flow associated with the identifier is charged based on the identifier;
sending a TUE information report by the UE directly to a mobility management entity (MME) identifying the TUE as having made the connection, wherein the TUE information report comprises information descriptive of the identifier and the associated service flow, wherein the information is further conveyed to the PGW in a request to modify bearer; and
receiving, by the UE in response to the request to modify bearer, a TUE information acknowledgement (ACK) message to enable charging for the TUE,
wherein the UE is provided a credit for communications relayed by the UE between the TUE and the PDN.
2. The method of claim 1 , further comprising:
including the information in an information element (IE) of a non access stratum (NAS) message to the MME.
3. The method of claim 1 , wherein identifying the TUE based on the TFT comprises:
determining the TUE using Internet Protocol (IP) header information of packet data corresponding to the TFT.
4. The method of claim 1 , wherein the identifier is an international mobile subscriber identity (IMSI) of the TUE.
5. An apparatus for wireless communication, comprising:
means for establishing a wireless communication with a Terminal User Equipment (TUE), wherein a user equipment (UE) provides a packet data network (PDN) connection to a packet data gateway (PGW) for the TUE;
means for identifying the TUE based on a traffic flow template (TFT) to determine an identifier associated with the TUE;
means for identifying a service flow corresponding to the TFT by the identifier, wherein the service flow associated with the identifier is charged based on the identifier;
means for sending a TUE information report by the UE directly to a mobility management entity (MME) identifying the TUE as having made the connection, wherein the TUE information report comprises information descriptive of the identifier and the associated service flow, wherein the information is further conveyed to the PGW in a request to modify bearer; and
means for receiving, by the UE in response to the request to modify bearer, a TUE information acknowledgement (ACK) message to enable charging for the TUE,
wherein the UE is provided a credit for communications relayed by the UE between the TUE and the PDN.
6. The apparatus of claim 5 , wherein the information is included in an information element (IE) of a non access stratum (NAS) message to the MME.
7. The apparatus of claim 5 , wherein means for identifying the TUE based on the TFT comprises:
means for determining the TUE using Internet Protocol (IP) header information of packet data corresponding to the TFT.
8. The apparatus of claim 5 , wherein the identifier is an international mobile subscriber identity (IMSI) of the TUE.
9. An apparatus for wireless communication, comprising:
a memory; and
at least one processor coupled to the memory and configured to:
establish a wireless communication with a Terminal User Equipment (TUE), wherein a user equipment (UE) provides a packet data network (PDN) connection to a packet data gateway (PGW) for the TUE;
identify the TUE based on a traffic flow template (TFT) to determine an identifier associated with the TUE;
identify a service flow corresponding to the TFT by the identifier, wherein the service flow associated with the identifier is charged based on the identifier;
send a TUE information report by the UE directly to a mobility management entity (MME) identifying the TUE as having made the connection, wherein the report comprises information descriptive of the identifier and the associated service flow, wherein the information is further conveyed to the PGW in a request to modify bearer; and
receive, by the UE in response to the request to modify bearer, a TUE information acknowledgement (ACK) message to enable charging for the TUE,
wherein the UE is provided a credit for communications relayed by the UE between the TUE and the PDN.
10. The apparatus of claim 9 , further comprising:
including the information in an information element (IE) of a non access stratum (NAS) message to the MME.
11. The apparatus of claim 9 , wherein identifying the TUE based on the TFT comprises:
determining the TUE using Internet Protocol (IP) header information of packet data corresponding to the TFT.
12. The apparatus of claim 9 , wherein the identifier is an international mobile subscriber identity (IMSI) of the TUE.
13. A non-transitory computer-readable medium storing computer executable code, comprising code to:
establish a wireless communication with a Terminal User Equipment (TUE), wherein a user equipment (UE) provides a packet data network (PDN) connection to a packet data gateway (PGW) for the TUE;
identify the TUE based on a traffic flow template (TFT) to determine an identifier associated with the TUE;
identify a service flow corresponding to the TFT by the identifier, wherein the service flow associated with the identifier is charged based on the identifier;
send a TUE information report by the UE directly to a mobility management entity (MME) identifying the TUE as having made the connection, wherein the report comprises information descriptive of the identifier and the associated service flow, wherein the information is further conveyed to the PGW in a request to modify bearer; and
receive, by the UE in response to the request to modify bearer, a TUE information acknowledgement (ACK) message to enable charging for the TUE,
wherein the UE is provided a credit for communications relayed by the UE between the TUE and the PDN.
14. The non-transitory computer-readable medium of claim 13 , further comprising code to:
include the information in an information element (IE) of a non access stratum (NAS) message to the MME.
15. The non-transitory computer-readable medium of claim 13 , wherein the code to identify the TUE based on the TFT comprises code to:
determine the TUE using Internet Protocol (IP) header information of packet data corresponding to the TFT.
16. The non-transitory computer-readable medium of claim 13 , wherein the identifier is an international mobile subscriber identity (IMSI) of the TUE.