A calculating system is provided, which includes at least one enb and a core network. The enb is coupled to two mobile devices. The core network includes two servers. The first mobile device operates as a mobile access point for the second mobile device to access a computer network via the enb and the core network. The enb and the core network provide a charging data record (CDR) of access of the computer network of one of the two mobile devices to the second server. The first server provides separation information indicating binding relationship between a network address of the second mobile device and the other one of the two mobile devices. The second server calculates data volumes of the access of the computer network of the two mobile devices separately according to the CDR and the separation information. The second server may further bill the two mobile devices separately.
|
19. A calculating method for calculating data volume of network access, the calculating method comprising:
providing a charging data record (CDR) of access of a computer network of one of a first mobile device and a second mobile device, wherein the first mobile device operates as a mobile access point (M-AP) for the second mobile device to access the computer network via at least one enb and a core network;
providing separation information, wherein the separation information indicates a binding relationship between a network address of the second mobile device and the other one of the first and second mobile devices; and
calculating data volumes of the access of the computer network of the first and second mobile devices separately according to the CDR and the separation information.
29. A calculating method for calculating data volume of network access, executed by an authentication server, the calculating method comprising:
performing a registration and authentication procedure via a first mobile device with a second mobile device, wherein the first mobile device operates as a mobile access point (M-AP) for the second mobile device to access a computer network via at least one enb and a core network;
acquiring binding information according to the registration and authentication procedure, wherein the binding information indicates a binding relationship between the second mobile device and the first mobile device;
generating a charging data record (CDR) of access of the computer network of the first and second mobile devices; and
separately calculating data volumes of the access of the computer network of the first and second mobile devices according to the CDR and the binding information.
12. An authentication server, comprising:
a communication interface adapted for communicating with a first mobile device and a second mobile device, wherein the first mobile device operates as a mobile access point (M-AP) for the second mobile device to access a computer network via at least one enb, a core network, and the authentication server; and
a processor coupled to the communication interface and performing a registration and authentication procedure via the first mobile device with the second mobile device and acquiring binding information according to the registration and authentication procedure, wherein the binding information indicates a binding relationship between the second mobile device and the first mobile device, and wherein the processor generates a charging data record (CDR) of access of the computer network of the first and second mobile devices and separately calculates data volumes of the access of the computer network of the first and second mobile devices according to the CDR and the binding information.
1. A calculating system for calculating data volume of network access, the calculating system comprising:
at least one enb coupled to a first mobile device and a second mobile device; and
a core network coupled to the at least one enb and a computer network and comprising a first server and a second server, wherein the first mobile device operates as a mobile access point (M-AP) for the second mobile device to access the computer network via the at least one enb and the core network, the at least one enb and the core network provide a charging data record (CDR) of access of the computer network of one of the first and second mobile devices to the second server, the first server provides to the second server separation information that indicates a binding relationship between a network address of the second mobile device and the other one of the first and second mobile devices, and the second server calculates data volumes of the access of the computer network of the first and second mobile devices separately according to the CDR and the separation information.
2. The calculating system according to
3. The calculating system according to
4. The calculating system according to
5. The calculating system according to
6. The calculating system according to
7. The calculating system according to
8. The calculating system according to
9. The calculating system according to
10. The calculating system according to
11. The calculating system according to
13. The authentication server according to
14. The authentication server according to
15. The authentication server according to
16. The authentication server according to
17. The authentication server according to
18. The authentication server according to
20. The calculating method according to
calculating costs incurred by the access of the computer network of the first and second mobile devices separately according to the CDR and the separation information.
21. The calculating method according to
providing binding information that indicates a binding relationship between the second mobile device and the first mobile device; and
accepting a request to establish a bearer for the second mobile device according to the binding information, wherein the bearer is exclusive resources that the core network assigns for connecting the second mobile device and the computer network.
22. The calculating method according to
performing an authentication procedure with the second mobile device, and assigning the network address to the second mobile device, wherein the CDR is the CDR of the first mobile device and comprises the network address of the second mobile device and an identification code of the first mobile device, and the separation information comprises the network address and an identification code of the second mobile device.
23. The calculating method according to
maintaining an M-AP list; and
selecting the first mobile device as the mobile access point of the second mobile device according to the M-AP list, wherein the M-AP list records local network information and position information of each mobile access point, and the position information is a position coordinate of the corresponding mobile access point or an identification code of the enb that serves the corresponding mobile access point.
24. The calculating method according to
assigning the network address to the second mobile device in an attach procedure of the second mobile device.
25. The calculating method according to
providing to the second mobile device a local M-AP scan list according to the position information provided by the second mobile device;
receiving a scan report from the second mobile device, wherein the scan report comprises a scan result of the second mobile device scanning at least one mobile access point in the local M-AP scan list;
selecting one of the mobile access points in the scan report as the first mobile device; and
sending a local connection request to the first mobile device for the second mobile device.
26. The calculating method according to
receiving a scan report generated by an M-AP scan performed by the second mobile device, wherein the scan report comprises a scan result of the second mobile device scanning at least one mobile access point;
selecting one of the mobile access points in the scan report as the first mobile device; and
sending a local connection request to the first mobile device for the second mobile device.
27. The calculating method according to
28. The calculating method according to
30. The calculating method according to
maintaining an M-AP list; and
selecting the first mobile device as the mobile access point of the second mobile device according to the M-AP list, wherein the M-AP list records local network information and position information of each mobile access point, and the position information is a position coordinate of the corresponding mobile access point or an identification code of the enb that serves the corresponding mobile access point.
31. The calculating method according to
providing to the second mobile device a local M-AP scan list according to the position information provided by the second mobile device;
receiving a scan report from the second mobile device, wherein the scan report comprises a scan result of the second mobile device scanning at least one mobile access point in the local M-AP scan list; and
selecting one of the mobile access points in the scan report as the first mobile device.
32. The calculating method according to
receiving a scan report generated by an M-AP scan performed by the second mobile device, wherein the scan report comprises a scan result of the second mobile device scanning at least one mobile access point; and
selecting one of the mobile access points in the scan report as the first mobile device.
33. The calculating method according to
assigning a network address to the second mobile device after the registration and authentication procedure; and
calculating costs incurred by the access of the computer network of the first and second mobile devices separately according to the CDR and the binding information.
34. The calculating method according to
performing an IP in IP tunnel decapsulation of an uplink packet and an IP in IP tunnel encapsulation of a downlink packet.
35. The calculating method according to
|
This application claims the priority benefits of U.S. provisional application Ser. No. 61/721,438, filed on Nov. 1, 2012 and Taiwan application serial no. 102129673, filed on Aug. 19, 2013. The entirety of each of the above-mentioned patent applications is hereby incorporated by reference herein and made a part of this specification.
1. Technical Field
This disclosure relates to a system, a server, and a method for calculating data volume of network access.
2. Description of Related Art
WiFi has become one of the mainstreams in terms of wireless local network communication. At present, there are many types of mobile devices, such as smart phones and tablet computers, having capacity for WiFi connection. However, WiFi network construction is mostly restricted to the urban areas. In remote outdoor areas, mobile devices with only WiFi connection capacity are unable to access the network.
A dual mode mobile device, which has both WiFi connectivity and 3GPP (3rd Generation Partnership Project) connectivity, can be used as a mobile access point (M-AP) to allow other mobile devices that have only WiFi connectivity to access the network.
This disclosure provides a system, a method, and an authentication server for calculating data volume of network access.
In an exemplary embodiment of the disclosure, a calculating system for calculating data volume of network access is provided, which includes at least one eNB and a core network. The at least one eNB is coupled to a first mobile device and a second mobile device. The core network is coupled to the at least one eNB and a computer network, and includes a first server and a second server. The first mobile device operates as a mobile access point for the second mobile device to access the computer network via the at least one eNB and the core network. The at least one eNB and the core network provide a charging data record (CDR) of access of the computer network of one of the first and second mobile devices to the second server. The first server provides separation information to the second server, wherein the separation information indicates a binding relationship between a network address of the second mobile device and the other one of the first and second mobile devices. The second server calculates data volumes of the access of the computer network of the first and second mobile devices separately according to the CDR and the separation information.
In an exemplary embodiment of the disclosure, an authentication server includes a communication interface and a processor. The communication interface is configured to communicate with a first mobile device and a second mobile device. The first mobile device operates as a mobile access point for the second mobile device to access a computer network via at least one eNB, a core network, and the authentication server. The processor of the authentication server is coupled to the communication interface, and performs a registration and authentication procedure via the first mobile device with the second mobile device and acquires binding information according to the registration and authentication procedure. The binding information indicates a binding relationship between the second mobile device and the first mobile device. The processor generates a charging data record (CDR) of access of the computer network of the first and second mobile devices and calculates data volumes of the access of the computer network of the first and second mobile devices separately according to the CDR and the binding information.
In an exemplary embodiment of the disclosure, a calculating method for calculating data volume of network access includes the following steps: providing a charging data record (CDR) of access of a computer network of one of a first mobile device and a second mobile device, wherein the first mobile device operates as a mobile access point for the second mobile device to access the computer network via at least one eNB and a core network; providing separation information indicating a binding relationship between a network address of the second mobile device and the other one of the first and second mobile devices; and separately calculating data volumes of the access of the computer network of the first and second mobile devices according to the CDR and the separation information.
In another exemplary embodiment of the disclosure, a calculating method for calculating data volume of network access is executed by an authentication server and includes the following steps: performing a registration and authentication procedure via a first mobile device with a second mobile device, wherein the first mobile device operates as a mobile access point for the second mobile device to access a computer network via at least one eNB and a core network; acquiring binding information according to the registration and authentication procedure, wherein the binding information indicates a binding relationship between the second mobile device and the first mobile device; generating a charging data record (CDR) of access of the computer network of the first and second mobile devices; and separately calculating data volumes of the access of the computer network of the first and second mobile devices according to the CDR and the binding information.
Several exemplary embodiments accompanied with figures are described in detail below to further describe the disclosure in details.
The accompanying drawings are included to provide further understanding, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments and, together with the description, serve to explain the principles of the disclosure.
The mobile device 110 serves as a mobile access point, which allows the mobile devices 121-123 to access the computer network 150 (to access the application server 151 in the computer network 150, for example) through at least one eNB (131 and/or 132) and the core network 140.
The mobile device 121 includes a processor 210 and a local access interface 220. The local access interface 220 is configured to communicate with the mobile access point 110. The processor 210 controls an operation of the mobile device 121. For example, the steps executed by the mobile device 121 in
The mobile device 122 includes a processor 230, a local access interface 240, and a cellular interface 250. The local access interface 240 is configured to communicate with the mobile access point 110, and the cellular interface 250 is configured to communicate with the eNB 131. The processor 230 controls an operation of the mobile device 122. For example, the steps executed by the mobile device 122 in
The mobile access point 110 includes a processor 260, a local access interface 270, and a cellular interface 280. The local access interface 270 is configured to communicate with the mobile devices 121-123, and the cellular interface 280 is configured to communicate with the eNB 131. The processor 260 controls an operation of the mobile access point 110. For example, the steps executed by the mobile access point 110 in
In
The mobile devices 121-123 respectively represent three types of application situations. The mobile device 121 represents a first application situation, in which the mobile device that includes no cellular interface spontaneously searches for the mobile access point 110 to access the computer network 150.
The authentication server 142 can acquire binding information of the mobile device 121 and the mobile access point 110 by the authentication procedure of Step 315. The binding information indicates that the mobile device 121 will access the computer network 150 via the mobile access point 110. The authentication server 142 can decide a network address AD2, by which the mobile device 121 accesses the computer network 150. In Step 320, the authentication server 142 can provides the binding information to the MME 141 of the core network 140, wherein the binding information indicates a binding relationship between the network address AD2 of the mobile device 121 and an identification code ID1 of the mobile access point 110. In addition, the binding information can further include a user profile of the mobile device 121. The authentication server 142 can assign the network address AD2 to the mobile device 121 in Step 325. Step 320 and Step 325 are exchangeable in sequence.
Next, in Step 330, the mobile access point 110 sends a request to the MME 141 to establish a bearer for the mobile device 121. The bearer is exclusive resources that the core network 140 assigns for connecting the mobile device 121 and the computer network 150. The request for establishing the bearer includes the network address AD2 of the mobile device 121. Since the MME 141 has received the binding information in Step 320 and accepts that the AD2 is the network address of the mobile device 121, the MME 141 can receive the request for establishing the bearer for the mobile device 121 according to the binding information. According to the 3GPP standard, the bearer is called a packet data protocol context, i.e. PDP context. According to the LTE standard, the bearer is called an evolved packet system bearer, i.e. EPS bearer.
Then, in Step 335, the mobile device 121 transmits data via the mobile access point 110, the eNB 131, the core network 140, and the application server 151. In Step 340, the eNB 131 and the core network 140 generate a charging data record (CDR) of the access of the computer network 150 of the mobile access point 110. In Step 345, the eNB 131 and the core network 140 provide the CDR to the billing server 144.
The application server 151 may refer to any server in the computer network 150. The eNB 131 and the core network 140 measure and calculate data volumes of the access of the computer network 150 of the mobile device 121 and the mobile access point 110 together as the data volumes of the mobile access point 110. Therefore, the CDR includes the network address AD2 of the mobile device 121, the identification code ID1 of the mobile access point 110, and the data volume and the time duration of the access of the computer network 150 of the mobile device 121 and the mobile access point 110.
In Step 350, the authentication server 142 provides separation information to the billing server 144. The separation information indicates a binding relationship between the network address AD2 of the mobile device 121 and the mobile device 121, and includes the network address AD2 and an identification code ID2 of the mobile device 121. In Step 355, the billing server 144 can separately calculate data volumes of network access of the mobile access point 110 and the mobile device 121 according to the CDR of Step 345 and the separation information of Step 350, that is, to separately calculate the data volumes of the access of the computer network 150 of the mobile access point 110 and the mobile device 121 in Step 335. In Step 335, the data is packaged as a network packet for transmission. In Step 355, the billing server 144 can further bill the mobile access point 110 and the mobile device 121 separately according to the CDR and the separation information, that is, to separately calculate the costs incurred by the access of the computer network 150 of the mobile access point 110 and the mobile device 121. Accordingly, the billing server 144 can accurately calculate the costs of the access of the computer network 150 of the mobile device 121 to bill the user of the mobile device 121, and the billing server 144 can also accurately accumulate a service provision volume of the mobile access point 110. In the embodiment of
When the user disables the local access point function of the mobile access point 110 in Step 440, the mobile access point 110 transmits the corresponding local AP configuration to the ANDSF 143 in Step 460. The local AP configuration can include the identification code ID1 of the mobile access point 110, a notification of disabling of the local access point function, and the aforementioned relevant information. Then, the ANDSF 143 deletes the record corresponding to the mobile access point 110 from the M-AP list according to the local AF configuration.
In Step 505, the mobile device 122 performs an attach procedure with the core network 140. In the attach procedure, the core network 140 completes the authentication of the mobile device 122 and assigns the network address AD2 to the mobile device 122. In Step 510, the mobile device 122 sends a local connection request to the ANDSF 143, and the local connection request includes the identification code ID2 and position information of the mobile device 122. In Step 515, the ANDSF 143 provides a local M-AP scan list to the mobile device 122 according to the position information provided by the mobile device 122. The ANDSF 143 can check the mobile access points in the M-AP list maintained by the ANDSF 143 and select one mobile access point or more, which is suitable for the mobile device 122, according to factors, such as the position and loading of each mobile access point, and then the ANDSF 143 adds the identification codes of the access points to the local M-AP scan list of Step 515 to notify the mobile device 122.
In Step 520, the mobile device 122 scans each mobile access point in the local M-AP scan list. The mobile device 122 can judge by itself which one (or ones) of the mobile access points is suitable according to a scan result, and generate a scan report from the scan result of the suitable mobile access point. Then, in Step 525, the scan report is sent to the ANDSF 143. The scan report can include the network address AD2 of the mobile device 122 and the scan result of one (or ones) of the mobile access points in the local M-AP scan list. For example, the scan result can include a signal strength of each mobile access point received by the mobile device 122.
After receiving the scan report, the ANDSF 143 selects one of the mobile access points in the scan report as the mobile access point 110 in Step 530. For example, the ANDSF 143 can select the mobile access point according to factors such as the signal strength, position, and loading, etc. Thereafter, in Step 540, the ANDSF 143 sends the local connection request to the mobile access point 110 for the mobile device 122. This request message contains the address AD2 of the mobile device 122. If the mobile access point 110 accepts this request, a local connection response is sent to the mobile device 122 via the ANDSF 143 in Steps 545 and 550. In Step 555, the ANDSF 143 provides the binding information to the MME 141 of the core network 140, wherein the binding information indicates a binding relationship between the identification code ID2 or network address AD2 of the mobile device 122 and the identification code ID1 of the mobile access point 110.
The ANDSF 143 selects one of the mobile access points in the scan report as the mobile access point 110 in Step 620. For example, the ANDSF 143 can select the mobile access point according to factors such as the signal strength, position, and loading, etc. Thereafter, in Step 630, the ANDSF 143 sends the local connection request to the mobile access point 110 for the mobile device 122. Steps 630-645 of
Then, in Step 720, the mobile device 122 transmits data via the mobile access point 110, the eNB 131, the core network 140, and the application server 151. In Step 730, the eNB 131 and the core network 140 generate a charging data record (CDR) of the access of the computer network 150 of the mobile access point 110. In Step 740, the eNB 131 and the core network 140 provide the CDR to the billing server 144.
In the embodiment of
In Step 750, the ANDSF 143 provides the separation information to the billing server 144. The separation information indicates the binding relationship between the network address AD2 of the mobile device 122 and the mobile device 122, and includes the network address AD2 and an identification code ID2 of the mobile device 122. In Step 760, the billing server 144 can separately calculate data volumes and costs for the mobile access point 110 and the mobile device 122 according to the CDR and the separation information, that is, to separately calculate the data volumes of the access of the computer network 150 of the mobile access point 110 and the mobile device 122 and calculate the costs incurred by the access of the computer network 150 of the mobile access point 110 and the mobile device 122. Accordingly, the billing server 144 can accurately calculate the costs of the access of the computer network 150 of the mobile device 122 to bill the user of the mobile device 122, and the billing server 144 can also accurately accumulate the service provision volume of the mobile access point 110.
In Step 850, the ANDSF 143 provides the separation information to the billing server 144. The separation information indicates the binding relationship between the network address AD2 of the mobile device 122 and the mobile access point 110, that is, to indicate that the mobile device 122 accesses the computer network 150 via the mobile access point 110. The separation information includes the network address AD2 of the mobile device 122 and the identification code ID1 of the mobile access point 110. In Step 860, the billing server 144 can calculate data volumes and costs for the mobile access point 110 and the mobile device 122 separately according to the CDR and the separation information, and can also accurately accumulate the service provision volume of the mobile access point 110.
The steps of
Next, in Step 920, the authentication server 905 performs a registration and authentication procedure with the mobile device 902 via the mobile access point 901. The authentication server 905 assigns the network address AD2 to the mobile device 902 in Step 925. In Step 930, the authentication server 905 acquires binding information of the mobile access point 901 and the mobile device 902 according to the registration and authentication procedure, wherein the binding information indicates a binding relationship between the network address AD2 of the mobile device 902 and the identification code ID1 of the mobile access point 901, and this ID1 can be an IP address. In Steps 941, 942, and 943, the mobile device 902 and the application server 151 transmit data to each other via a tunnel of IP in IP. In Step 942, the mobile device 901 manages the IP in IP tunnel encapsulation of uplink packets and the IP in IP tunnel decapsulation of downlink packets. The authentication server 905 manages the IP in IP tunnel decapsulation of uplink packets and the IP in IP tunnel encapsulation of downlink packets, and in this procedure, calculates data volumes of network access of the mobile access point 901 and the mobile device 902 in Steps 941, 942, and 943 to generate a charging data record (CDR).
In Step 955, the authentication server 905 separately calculates data volumes and costs for the mobile access point 901 and the mobile device 902 according to the CDR and the binding information, and also can accurately accumulate the service provision volume of the mobile access point 901.
In this embodiment, the core network 140 is likely to calculate all the data volumes of network access of the mobile access point 901 and the mobile device 902 on the mobile access point 901; however, in that case, the user of the mobile access point 901 can be compensated according to the service provision volume accumulated by the authentication server 905.
In conclusion of the above, this disclosure is adapted for calculating data volumes separately for the core network in the situation that the mobile device accesses the network via the mobile access point. For the mobile device, the mechanism provided by this disclosure enables the mobile device to access the network via the nearby dual mode mobile device, so as to increase available network access points. The user of the mobile device does not need to know the user of the dual mode mobile device nor need to know where the dual mode mobile device is.
For the dual mode mobile device, this disclosure utilizes the local network access interface that is more efficient in power saving to access the network via another nearby dual mode mobile device, so as to save power and prolong the time of network access.
For the dual mode mobile device that provides the network access service, with the mechanism of this disclosure that calculates data volumes separately, the user of the dual mode mobile device is not required to bear the costs incurred by others and furthermore the service provision volume can be accurately accumulated for the user of the dual mode mobile device to earn rewards. Accordingly, the user of the dual mode mobile device will be more willing to provide the service of network access.
For the mobile service providers, the mechanism of this disclosure that automatically calculates data volumes separately increases the number of mobile access points, the number of network users, and operating income.
It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the disclosed embodiments without departing from the scope or spirit of the disclosure. In view of the foregoing, it is intended that the disclosure covers modifications and variations of this disclosure provided they fall within the scope of the following claims and their equivalents.
Patent | Priority | Assignee | Title |
10601932, | Jun 09 2017 | AT&T Intellectual Property I, L.P. | Next generation mobility core network controller for service delivery |
11146645, | Jun 09 2017 | AT&T Intellectual Property I, L.P. | Next generation mobility core network controller for service delivery |
Patent | Priority | Assignee | Title |
6879574, | Jun 24 2002 | Nokia Technologies Oy | Mobile mesh Ad-Hoc networking |
7649872, | Jun 24 2002 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
8085758, | Dec 31 2004 | RIBBON COMMUNICATIONS OPERATING COMPANY, INC | Methods and apparatus for controlling call admission to a network based on call peers |
8144728, | Feb 06 2001 | Nokia Technologies Oy | Access system for a cellular network |
8229440, | Jul 14 2008 | Qualcomm Incorporated | Systems, methods and apparatus to facilitate identification and acquisition of access points |
8627416, | Jul 12 2007 | Wayport, Inc. | Device-specific authorization at distributed locations |
8639248, | Aug 01 2005 | Cisco Technology, Inc | Handover information sent over a public wide area network (e.g. internet) |
8688551, | Nov 03 2008 | Nokia Technologies Oy | Charging control providing correction of charging control information |
8897183, | Oct 05 2010 | Cisco Technology, Inc. | System and method for offloading data in a communication system |
20050153725, | |||
20070121540, | |||
20120011365, | |||
20120260320, | |||
CN102711164, | |||
WO2013000645, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Oct 18 2013 | Industrial Technology Research Institute | (assignment on the face of the patent) | / | |||
Oct 23 2013 | HSU, YU-CHING | Industrial Technology Research Institute | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 031923 | /0010 |
Date | Maintenance Fee Events |
Dec 24 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Dec 23 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Jun 23 2018 | 4 years fee payment window open |
Dec 23 2018 | 6 months grace period start (w surcharge) |
Jun 23 2019 | patent expiry (for year 4) |
Jun 23 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jun 23 2022 | 8 years fee payment window open |
Dec 23 2022 | 6 months grace period start (w surcharge) |
Jun 23 2023 | patent expiry (for year 8) |
Jun 23 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jun 23 2026 | 12 years fee payment window open |
Dec 23 2026 | 6 months grace period start (w surcharge) |
Jun 23 2027 | patent expiry (for year 12) |
Jun 23 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |