CN110876123A

CN110876123A - Flow acquiring, providing, sharing, calibrating and transferring method and equipment

Info

Publication number: CN110876123A
Application number: CN201811005186.4A
Authority: CN
Inventors: 何晏晏; 高昌斌; 郑相贤; 黄俊峰; 赵晶晶; 金君
Original assignee: Beijing Samsung Telecommunications Technology Research Co Ltd; Samsung Electronics Co Ltd
Current assignee: Beijing Samsung Telecom R&D Center; Beijing Samsung Telecommunications Technology Research Co Ltd; Samsung Electronics Co Ltd
Priority date: 2018-08-30
Filing date: 2018-08-30
Publication date: 2020-03-10
Also published as: WO2020046034A1

Abstract

A method and a device for acquiring, providing, sharing, calibrating and transferring traffic are provided, wherein the method for acquiring the traffic comprises the following steps: predicting user behavior; and acquiring data traffic service from the network node according to the predicted user behavior. By adopting the method and the equipment, the functions of the existing data traffic service can be enriched, so that the user can use the data traffic service more conveniently and flexibly.

Description

Flow acquiring, providing, sharing, calibrating and transferring method and equipment

Technical Field

The present invention relates generally to the field of mobile communications, and more particularly, to a traffic acquisition, provisioning, sharing, calibration, transfer method and apparatus.

Background

With the increasingly obvious trend of global communication integrated interconnection, the requirements of terminal devices (e.g., smart phones, tablet computers, smart watches, smart headsets, etc.) on flexibility and convenience of communication (e.g., more convenient replacement of operators and multiple numbers) are higher and higher, and with the pursuit of terminal device manufacturers for simplifying manufacturing processes and making the appearance thinner and more delicate, the traditional physical SIM (Subscriber identity Module) card mode is no longer unique, and accordingly, a plurality of innovative modes and technical means are generated, and a virtual SIM (SOFT Subscriber identity Module) card technology is generated under such an environment.

The SOFTSIM technology applied in the terminal equipment at present obtains code number resources from a cloud service provider (for example, a virtual operator) through a cloud SIM platform, and provides an international roaming data internet access product with a local tariff level for a user with an international roaming demand, so as to solve the problem of high international roaming tariff of a traditional operator. The SOFTSSIM technology is based on the characteristics of software, so that a physical chip does not need to be added, and the SOFTSSIM technology has a wide application scene in the fields of IOT and M2M in the future.

The existing use flow of the SOFTSIM service is as follows: from the terminal device side, purchase traffic package → receive and save SOFTSIM packet information (e.g., IMSI, KI, etc.) → activate package, register network → go online using mobile data traffic service → go offline after traffic is exhausted. From the network side, the network side receives the request of buying the flow package → issues the SOFTSIM data packet information → receives the request of activating the package, registers the network → monitors the flow using condition → informs the terminal side after the flow is exhausted.

The existing SOFTSIM service has the following problems or drawbacks:

firstly, when the terminal device is defaulted and disconnected from the network, the user must go to a business hall or let friends help to recharge to restore the network. When a user goes on a business trip abroad, if the user does not prepare a destination internet access mode in advance, after the user arrives at the destination, the user is disconnected from the outside because the user cannot access the internet. When the user changes the airplane, the user is supposed to fly from the departure place A to the destination B, the airplane is changed to the airplane in the approach place C for a few hours in the middle of the airplane, and the communication in the approach place C is interrupted because the user does not prepare the internet surfing mode in the approach place C in advance.

In the prior art, if a communication service provided by the SOFTSIM packet needs to be used to avoid the above situation, a user of the terminal device needs to actively purchase the SOFTSIM packet, and use the SOFTSIM packet to perform communication after successful purchase. However, if the user does not purchase the SOFTSIM data packet in advance, communication interruption is caused, which brings great inconvenience to the user when going out. In addition, in the prior art, the wireless communication can be realized by presetting a SOFTSIM data packet for each terminal device, but the cost of the method is too high. Moreover, not all terminal devices have the requirement of using the preset SOFTSIM data packet, which easily causes resource waste.

Secondly, currently, the terminal device that activates the SOFTSIM packet is generally set as a mobile hotspot, and requests another device that uses the mobile hotspot to connect to the mobile hotspot after passing identity authentication, and uses the traffic in the SOFTSIM packet of the terminal device that shares the mobile hotspot to connect to and access the internet. In the traffic sharing method, the terminal device serving as the mobile hotspot will become a WLAN access point, i.e. a receiver and a transmitter of a WLAN, and both receiving and transmitting signals will increase power consumption, which may result in increased power consumption of the terminal device serving as the mobile hotspot. In addition, since the terminal device as the mobile hotspot is equivalent to a wireless router, the signal coverage of the terminal device is required to be within a certain range (where, the coverage range is related to the source power of the hotspot, and the effective distance of the mobile hotspot is usually about 100 meters), and if the coverage range of the signal is exceeded, other devices cannot receive the signal and cannot access the internet through the mobile hotspot.

Thirdly, in the prior art, accurate statistics of the traffic usage amount locally at the terminal device cannot be realized. At present, no matter a traditional SIM card data traffic packet or an SOFTSIM data traffic packet, the traffic usage is usually counted locally at the terminal device by monitoring the number of bytes received and sent, but the traffic usage counted locally at the terminal device is different from the traffic usage counted by the network operator, and when the traffic usage counted locally at the terminal device is taken as a reference, the traffic counted by the network operator is used up, the terminal device is disconnected, but the terminal device side still displays the remaining traffic, which causes the mismatch between the display and the actual network condition.

Fourthly, when the data traffic packet purchased by the terminal device is not used up within the specified time limit, the traffic which is not used up can only be reset after the expiration, which causes the waste of traffic resources.

Disclosure of Invention

It is an object of exemplary embodiments of the present invention to provide a traffic acquisition, provisioning, sharing, calibration, transfer method and apparatus that overcome at least one of the disadvantages described above.

In one general aspect, there is provided a traffic acquisition method, including: predicting user behavior; and acquiring data traffic service from the network node according to the predicted user behavior.

Optionally, the user behavior may include any one of: travel plan of the user, communication cost condition of the user and flow use condition of the user.

Optionally, the data traffic service may comprise at least one of: the travel plan comprises a globally available data traffic packet, a data traffic packet available at a destination of the travel plan, a data traffic packet available at a route point of the travel plan, a directional traffic data packet, a free data traffic packet, a paid data traffic packet, information for reminding of purchasing the data traffic packet, and information for recommending of purchasing the data traffic packet.

Optionally, the step of obtaining the data traffic service from the network node according to the predicted user behavior may include: sending a request for acquiring data traffic service to a network node according to the predicted user behavior; and receiving the data traffic service sent by the network node in response to the request for acquiring the data traffic service.

Optionally, the travel plan of the user may be predicted based on at least one of the following information in the electronic terminal used by the user: the position information of the electronic terminal, the information received by the electronic terminal, the webpage use data in the electronic terminal and the application use data in the electronic terminal; the traffic utilization of the user can be predicted according to at least one of the following information: user representation, traffic usage of the user, application used by the user, application usage duration of the user, and application usage frequency of the user.

Alternatively, the data traffic service may be a virtual subscriber identity module, SOFTSIM, data traffic packet, and the network node may be a SOFTSIM management server and/or a virtual operator server.

In another general aspect, there is provided a traffic acquisition device, including: the user behavior prediction module is used for predicting user behaviors; and the flow service acquisition module is used for acquiring data flow services from the network node according to the predicted user behaviors.

In another general aspect, there is provided a traffic providing method including: receiving a request for acquiring data traffic service, wherein the request for acquiring data traffic service is sent by an electronic terminal according to predicted user behavior; and responding to the request for acquiring the data traffic service and sending the data traffic service to the electronic terminal.

In another general aspect, there is provided a traffic sharing method, including: receiving a flow sharing request; distributing subdata traffic service for the shared object from the data traffic service to be shared; and sending the sub-data traffic service to the shared object.

Optionally, the traffic sharing method may further include: determining sub-data traffic service distributed for the shared object according to the predicted traffic use condition of the shared object; and/or adjusting the sub-data traffic service distributed for the shared object according to the actual traffic usage of the shared object.

Optionally, the traffic usage of the shared object may be predicted according to at least one of the following information: user representation, traffic usage of the user, application used by the user, application usage duration of the user, and application usage frequency of the user.

Optionally, the data traffic service may be a virtual subscriber identity module, SOFTSIM, data traffic packet, and the sub-data traffic service may be a sub-SOFTSIM data traffic packet.

In another general aspect, there is provided a traffic sharing apparatus, including: a traffic sharing request receiving module, configured to receive a traffic sharing request; the flow sharing module is used for distributing subdata flow services for the shared object from the data flow services to be shared; and the flow providing module is used for sending the sub-data flow service to the shared object.

In another general aspect, there is provided a traffic sharing method, including: sending a flow sharing request to a network node so that the network node provides a sub-data flow service for a shared object from a data flow service to be shared, and the shared object shares the data flow service to be shared.

Optionally, the traffic sharing method may further include: and acquiring the information of the shared object in a mode of establishing a user group.

In another general aspect, there is provided a flow calibration method, including: acquiring a flow use value of a data flow packet of local statistics; the flow usage value is calibrated.

Optionally, the calibrating the flow usage value may include at least one of: calibrating the locally counted traffic usage value using the traffic usage value obtained from the network node; and calibrating the flow use value of the local statistics according to the calibration coefficient.

Optionally, calibrating the flow usage value may include at least one of: calibrating the locally counted traffic usage value using the traffic usage value obtained from the network node; and calibrating the flow use value of the local statistics according to the calibration coefficient.

Optionally, the data traffic packet may be a virtual subscriber identity module, SOFTSIM, data traffic packet, and the network node may be a SOFTSIM management server and/or a virtual operator server.

In another general aspect, there is provided a flow calibration apparatus, comprising: the flow obtaining module is used for obtaining a flow use value of a data flow packet of local statistics; and the flow calibration module is used for calibrating the flow use value.

In another general aspect, there is provided a flow calibration method, including: receiving a request for acquiring traffic use information of a data traffic packet; and sending the traffic usage information counted by the network node to the electronic terminal.

Optionally, the traffic usage information may include a traffic usage value and/or a calibration coefficient.

In another general aspect, there is provided a traffic diversion method, including: receiving a flow transfer request; and transferring the flow of the data flow packet of the removing party to a receiving party according to the flow transfer request.

Optionally, the traffic forwarding request may include: and the flow transfer-out request of the moving party and/or the flow transfer-in request of the receiving party.

Optionally, the step of transferring the traffic of the data traffic packet of the moving party to the receiving party may include: recovering the data traffic packet of the moving party; and distributing the new data traffic packet to the receiver.

Optionally, the data traffic packet may be a virtual subscriber identity module, SOFTSIM, data traffic packet.

In another general aspect, there is provided a traffic shifting apparatus, comprising: a transfer request receiving module for receiving a flow transfer request; and the flow transfer module is used for transferring the flow of the data flow packet of the moving-out party to the receiving party according to the flow transfer request.

In another general aspect, there is provided a traffic diversion method, including: and sending a flow transfer request to the network node so that the network node transfers the flow of the data flow packet of the moving-out party to a receiving party according to the flow transfer request.

Optionally, the traffic forwarding request may include: traffic roll-out requests and/or traffic roll-in requests.

Optionally, the traffic diversion method may further include: according to the indication of the network node, recovering the data traffic packet; and/or; and receiving the transferred data traffic packet sent by the network node.

In another general aspect, there is provided an electronic device including: a processor; a memory storing a computer program that, when executed by the processor, implements any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method.

In another general aspect, there is provided a network node device, comprising: a processor; a memory storing a computer program that, when executed by the processor, implements any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method.

In another general aspect, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method.

By adopting the method and the equipment, the functions of the existing data traffic service can be enriched, so that the user can use the data traffic service more conveniently and flexibly.

Drawings

The above and other objects, features and advantages of exemplary embodiments of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings which illustrate exemplary embodiments, wherein:

fig. 1 shows a schematic diagram of an electronic terminal and a network node according to an exemplary embodiment of the invention;

fig. 2 shows a block diagram of an electronic terminal and a network node for implementing a traffic acquisition function according to an exemplary embodiment of the present invention;

FIG. 3 illustrates a flow diagram for implementing a traffic acquisition function in accordance with an exemplary embodiment of the present invention;

FIG. 4 illustrates a flow diagram for predicting user behavior according to an exemplary embodiment of the present invention;

fig. 5 shows a first schematic diagram of an information interaction flow for traffic acquisition between an electronic terminal and a network node according to an exemplary embodiment of the present invention;

fig. 6 shows a second schematic diagram of an information interaction flow for traffic acquisition between an electronic terminal and a network node according to an exemplary embodiment of the present invention;

fig. 7 illustrates a block diagram of an electronic terminal and a network node for implementing a traffic sharing function according to an exemplary embodiment of the present invention;

FIG. 8 illustrates a flow diagram for implementing traffic sharing functionality in accordance with an exemplary embodiment of the present invention;

fig. 9 illustrates a first diagram of an information interaction flow for traffic sharing between an electronic terminal and a network node according to an exemplary embodiment of the present invention;

FIG. 10 illustrates a schematic diagram of predicting traffic usage by a user in accordance with an exemplary embodiment of the present invention;

FIG. 11 illustrates a diagram of dynamically adjusting data traffic allocated to a user based on the user's actual traffic usage according to an exemplary embodiment of the present invention;

fig. 12 shows a second schematic diagram of an information interaction flow for traffic sharing between an electronic terminal and a network node according to an exemplary embodiment of the present invention;

fig. 13 shows a block diagram of an electronic terminal and a network node for implementing a traffic calibration function according to an exemplary embodiment of the invention;

fig. 14 illustrates a flow diagram for traffic calibration based on traffic usage values obtained from network nodes, according to an exemplary embodiment of the invention;

FIG. 15 shows a schematic flow chart for calculating calibration coefficients according to an exemplary embodiment of the present invention;

FIG. 16 illustrates a block diagram of an electronic terminal and a network node for implementing a traffic forwarding function, according to an exemplary embodiment of the invention;

FIG. 17 shows a flow diagram for implementing a traffic diversion function in accordance with an exemplary embodiment of the present invention;

fig. 18 shows a first diagram of an information interaction flow for traffic transfer between an electronic terminal and a network node according to an exemplary embodiment of the invention;

fig. 19 illustrates a second schematic diagram of an information interaction procedure for traffic transfer between an electronic terminal and a network node according to an exemplary embodiment of the present invention.

Detailed Description

Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present invention by referring to the figures.

Fig. 1 shows a schematic view of an electronic terminal and a network node according to an exemplary embodiment of the invention.

It should be appreciated that in exemplary embodiments of the present invention, functions of traffic acquisition, traffic sharing, traffic calibration, and/or traffic transfer may be implemented through information interaction between the electronic terminal and the network node. Optionally, the traffic mentioned above may refer to SOFTSIM data traffic, in this case, as shown in fig. 1, the electronic terminal may include a SOFTSIM packet management module, a local traffic statistics calibration module, a forwarding module, a group module, a SOFTSIM packet request module, a user behavior prediction module, and a payment module. The modules described above may be implemented as individual modules in an application (e.g., SOFTSIM application) installed on an electronic terminal. Besides, the electronic terminal may further include a SOFTSIM packet control module, a SOFTSIM logic module in a trusted zone, and a MODEM.

The network node can comprise an order management module, a bill module, a data statistics module, a recovery module, a SOFTSIM data packet sending module, a SOFTSIM data packet pushing module, a group sending module, a group management module, a SOFTSIM data packet management module and a payment module. The above functions can be realized through information interaction between the electronic terminal and the network node.

For example, for the requirement of emergency communication capability, after predicting the user behavior, the user behavior prediction module in the SOFTSIM application may request the SOFTSIM packet request module of the SOFTSIM application for the corresponding SOFTSIM packet, and may further notify the relevant prediction result to the SOFTSIM management module of the network node (e.g., the SOFTSIM application server) through the SOFTSIM packet request module of the SOFTSIM application.

And the SOFSIM application program server acquires a corresponding SOFSIM data packet and sends the data packet to the electronic terminal by using the SOFSIM data packet pushing module.

For the requirement of sharing SOFTSIM data by multiple persons, the group module in the SOFTSIM application notifies the group information (such as a subscription number of a SOFTSIM packet to be shared, a device ID of the SOFTSIM packet to be shared, and a device ID of a user group to be added) to the group management module of the SOFTSIM application server. The group management module of the SOFSIM application server requests the corresponding SOFSIM data packet from the SOFSIM data packet request module of the SOFSIM application server according to the corresponding group information, and the SOFSIM application server sends the corresponding SOFSIM data packet to each electronic terminal by using the group sending module after acquiring the corresponding SOFSIM data packet.

For the requirement of accurately measuring the data traffic usage amount at the electronic terminal, a local traffic statistical calibration module in the SOFSIM application program informs a data statistical module of a SOFSIM application program server of relevant statistical data, and the data statistical module of the SOFSIM application program server calculates an available calibration coefficient according to recorded historical calibration data.

For the requirement of data traffic transfer, after transfer transaction is achieved between the electronic terminal of the moving-out party and the electronic terminal of the receiving party through the second-hand traffic market or confirmation between the terminals by the terminal (for example, scanning two-dimensional codes, NFC tags and the like, a transfer module in the SOFTSIM application of the electronic terminal of the moving-out party notifies a transfer request to a recovery module of a SOFTSIM application server, and a recovery module on the side of the SOFTSIM application server sends a recovered SOFTSIM data packet to the electronic terminal of the receiving party through a SOFTSIM data packet sending module.

As an example, the electronic terminal may be a mobile communication terminal, a personal computer, a tablet computer, a portable wearable device, a personal digital assistant, a game machine, a digital multimedia player, an IOT internet of things device, or other electronic devices capable of supporting data traffic services. As an example, the network node 20 may be a server.

The procedures for performing the functions of traffic acquisition, traffic sharing, traffic calibration, and traffic diversion will be described in detail below with reference to the accompanying drawings.

In a first exemplary embodiment, a process of implementing a traffic acquisition function through information interaction between an electronic terminal and a network node is described.

Fig. 2 shows a block diagram of an electronic terminal 10 and a network node 20 for implementing a traffic acquisition function according to an exemplary embodiment of the present invention.

As shown in fig. 2, the traffic acquiring apparatus in the electronic terminal 10 according to the exemplary embodiment of the present invention includes: a user behavior prediction module 101 and a traffic service acquisition module. In addition, the traffic acquiring apparatus in the electronic terminal 10 according to the exemplary embodiment of the present invention may further include a detection module 102 and a data traffic management module 105. The traffic service acquisition module may include a request module 103 and a receive module 104. These modules may be implemented by a general-purpose hardware processor such as a digital signal processor or a field programmable gate array, or by a special-purpose hardware processor such as a special-purpose chip, or may be implemented entirely by a computer program in a software manner, for example, as respective modules in an application program (e.g., an application program for implementing a flow acquisition function) 30 installed on an electronic terminal. Here, the electronic terminal 10 according to an exemplary embodiment of the present invention may further include a data traffic control module 106, a trusted zone 107, and a MODEM108, in addition to the above-described modules.

The traffic acquisition device in the network node 20 according to an exemplary embodiment of the present invention may include: a data traffic service request module 201 and a data traffic service sending module 203. In addition, the traffic acquisition device in the network node 20 may also include a data traffic management module 202.

Specifically, the user behavior prediction module 101 is configured to predict user behavior, and the traffic service acquisition module is configured to acquire a data traffic service from the network node 20 according to the predicted user behavior.

For example, after the user behavior prediction module 101 predicts the user behavior, the request module 103 may send a request for obtaining a data traffic service to the network node 20 according to the predicted user behavior, the data traffic service request module 201 receives the request for obtaining the data traffic service and requests the data traffic management module 202 for a data traffic service corresponding to the received request in response to the received request for obtaining the data traffic service, the data traffic management module 202 issues the data traffic service corresponding to the received request for obtaining the data traffic service, and the data traffic service sending module 203 sends the issued data traffic service to the receiving module 104 in the electronic terminal 10, so that the electronic terminal 10 can perform communication using the data traffic service obtained from the network node 20.

Alternatively, the data traffic service acquired from the network node 20 may refer to a data traffic service with respect to a SOFTSIM (virtual subscriber identity module), but the present invention is not limited thereto, and the data traffic service may also be other data traffic services than the data traffic service with respect to the SOFTSIM.

For the case where the data traffic service is a data traffic service with respect to SOFTSIM, network node 20 may be any one of the following servers, as an example: the system comprises a SOFSIM application server, a virtual operator server and a SOFSIM server with functions of the SOFSIM application server and the virtual operator server (namely, the SOFSIM application server and the virtual operator server are deployed on the same server). That is, the SOFTSIM server has both the function of a SOFTSIM application server and the function of a SOFTSIM packet management module of a virtual operator server.

The information interaction flow for traffic acquisition between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM application server 21 is described below with reference to fig. 3 to 5, taking the data traffic service as the data traffic service related to the SOFTSIM as an example.

Fig. 3 shows a flow diagram for implementing a traffic acquisition function according to an exemplary embodiment of the present invention. Fig. 4 illustrates a flow diagram for predicting user behavior according to an exemplary embodiment of the present invention. Fig. 5 shows a first schematic diagram of an information interaction flow for traffic acquisition between the electronic terminal 10 and the network node 20 according to an exemplary embodiment of the present invention. In this example, the request module 103, the receiving module 104, the data traffic service request module 201, the data traffic management module 202, and the data traffic service sending module 203 shown in fig. 2 correspond to the SOFTSIM request module, the SOFTSIM receiving module, the SOFTSIM packet request module, the SOFTSIM packet management module, and the SOFTSIM packet sending module in fig. 5, respectively.

Referring to fig. 5, in step S10, the user behavior prediction module 101 in the electronic terminal 10 predicts the user behavior based on the information for predicting the user behavior. Here, it should be understood that the user behavior prediction module 101 may be a module in the SOFTSIM application of the electronic terminal 10, or may be a module other than the SOFTSIM application. For the case where the user behavior prediction module 101 is a module other than the SOFTSIM application, the user behavior prediction module 101 may notify the SOFTSIM application of the prediction result.

For example, the information used to predict user behavior may include information in the electronic terminal 10 used by the user and/or information about traffic usage by the user.

For example, the user behavior prediction module 101 may utilize a user behavior prediction model to predict user behavior. Here, the user behavior may refer to a future behavior of the user. As an example, the user behavior prediction model may be in the form of an SDK, embedded in the electronic terminal 10, and the SDK may interact with the network node 20 through an API interface.

As an example, user behavior may include any of the following: travel plan of the user, communication cost condition of the user and flow use condition of the user. Here, the trip plan of the predicted user may include the number of trips, trip time, trip location, and/or trip law of the trip plan of the predicted user.

In the first case, a travel plan of the user may be predicted based on information in the electronic terminal used by the user.

As an example, the trip plan of the user may be predicted based on at least one of the following information in the electronic terminal used by the user: the position information of the electronic terminal, the information received by the electronic terminal, the webpage use data in the electronic terminal, and the application use data in the electronic terminal. That is, the user behavior prediction module 101 may acquire the above-described information in the electronic terminal from various data acquisition channels.

In this case, the user behavior prediction module 101 may obtain a plurality of corresponding user behavior prediction results based on information in the electronic terminal acquired from a plurality of data acquisition channels, respectively, and determine a final prediction result according to the plurality of user behavior prediction results, so as to acquire the data traffic service from the network node 20 according to the final prediction result.

For example, the user behavior prediction module 101 may determine the final prediction result by: and setting a weight value for each data acquisition channel, and obtaining a final prediction result based on the user behavior prediction result corresponding to each data acquisition channel and the corresponding weight value.

Optionally, the user behavior prediction results indicating the same prediction content in the plurality of user behavior prediction results may be merged into one user behavior prediction result, where the weight value of the merged user behavior prediction result is the sum of the weight values corresponding to all the user behavior prediction results indicating the same prediction content, and at this time, the user behavior prediction result corresponding to the highest weight value is determined as the final prediction result.

A process of predicting a travel plan of a user based on location information of an electronic terminal is described below.

Alternatively, the position information of the electronic terminal may be acquired by: acquiring location information of an electronic terminal from a Global Positioning System (GPS); alternatively, the location information of the electronic terminal is determined by MCC (Mobile Country Code) contained in PLMN data acquired from a PLMN (Public Land Mobile Network). Here, since the GPS of the electronic terminal needs to be turned on before being used, in order to avoid the GPS data being unavailable, the PLMN data may be used for analysis to determine the location information of the electronic terminal.

Here, the PLMN data includes MCC and mnc (mobile Network code), the MCC is a mobile country code, 3 digits in total, and can uniquely identify the country where the mobile subscriber is located, for example, the MCC of china is 460. The MNC is a mobile network code, which is 2 bits in total, for example, the MNC used by the china mobile TD system is 00, the MNC used by the china unicom GSM system is 01, the MNC used by the china mobile GSM system is 02, and the MNC used by the china telecommunication CDMA system is 03. That is, the country to which the location of the electronic terminal belongs can be determined by the mobile country code included in the PLMN data, and it can be determined whether the user using the electronic terminal is located overseas.

In one example, the location information of the electronic terminal may be real-time location information of the electronic terminal. In this case, the user behavior prediction module 101 may predict a trip plan of the user based on the real-time location information of the electronic terminal.

For example, a travel plan of the user may be predicted based on real-time location information of the electronic terminal by: and detecting real-time position information of the electronic terminal, and predicting a trip destination of the user according to a change track of the position in the detected real-time position information when detecting that the change rate of the position in the real-time position information of the electronic terminal is greater than a predetermined threshold (such as continuous directional change). When the predicted destination of the user's trip is located overseas, it may be determined that the trip plan of the user using the electronic terminal is an overseas trip plan.

That is, the destination of the user trip can be predicted through the variation trend of the real-time position information of the electronic terminal within a certain period of time. For example, when a trend of change (i.e., a change trajectory) of the real-time location information of the electronic terminal is detected to indicate that the user is currently on the way from Shenzhen to hong Kong, the destination of the user's trip can be predicted to be hong Kong.

In another example, the location information of the electronic terminal may be historical location information of the electronic terminal. In this case, the user behavior prediction module 101 may predict a trip plan of the user based on the historical location information of the electronic terminal.

For example, a travel plan of a user using the electronic terminal may be predicted based on historical location information of the electronic terminal by: and predicting a travel rule of the user using the electronic terminal according to the acquired historical position information of the electronic terminal, wherein the travel rule of the user can comprise a travel frequency of the user and/or a possible travel time of the user in the near future, and a travel plan of the user is predicted according to the travel frequency and/or the possible travel time of the user in the near future. For example, when the current time reaches a travel time predicted based on the travel law of the user, it may be determined that the user using the electronic terminal is about to travel, at which time the data traffic service may be acquired from the network node 20.

A process of predicting a user's travel plan based on information received by the electronic terminal, web page usage data in the electronic terminal, and application usage data in the electronic terminal will be described below.

As an example, the information received by the electronic terminal may comprise at least one of: short messages, Push (Push) messages and e-mails received by the electronic terminal. Web page (web) usage data in an electronic terminal may include a record of clicks/browses and/or a record of searches on a web page by a user using the electronic terminal. The application usage data in the electronic terminal may refer to application usage data of a predetermined application program installed in the electronic terminal. Here, the reservation application may refer to an application installed in the electronic terminal and related to a user's trip (e.g., OTA, online travel agency), and the application usage data of the reservation application may include order information, browsing records, and/or searching records generated in the reservation application by the user using the electronic terminal. As an example, the predetermined application may comprise at least one of: an application for ordering airline tickets, an application for booking hotels, an application for renting cars, an application for purchasing travel products.

For example, the user behavior prediction module 101 may identify information for predicting user behavior from information received from the electronic terminal, web page usage data in the electronic terminal, application usage data in the electronic terminal, and optionally, the identified information for predicting user behavior may be stored in a database in the form of structured data. For example, information/data having a predetermined keyword may be detected from the above information/data as information for predicting user behavior. Here, the user behavior prediction module 101 may detect keywords using various existing keyword detection techniques. Such as word segmentation techniques, natural language processing techniques, and the like. As an example, the predetermined keyword may include related information indicating a sender of the information (e.g., a phone number, a mail address, a sender name), a keyword indicating time, a keyword indicating a travel manner, and a keyword indicating a place.

In an alternative example, a phone number database in which various phone numbers related to the trip of the user are stored may be previously established, when the electronic terminal receives a short message, a phone number of a sender of the short message is extracted, if the phone number of the sender is found from the phone number database, the received short message is determined as information for predicting the user behavior, and the content of the short message is analyzed by matching (e.g., "airport", "hotel", etc.) keywords, so that information of the airport name, city name, restaurant name, country/district name, etc. can be obtained, thereby predicting the trip plan of the user. When the location indicated by the information obtained by analyzing the content of the short message is overseas, the overseas trip plan of the user can be predicted.

Here, with the cancellation of the domestic roaming fee, domestic trip is not a strong demand market using the SOFTSIM data packet, and thus, the trip plan of the user may alternatively refer to an overseas trip plan of the user, in which case the data traffic service acquired from the network node 20 may be a data traffic service suitable for the overseas trip plan of the user, so that the electronic terminal has an emergency communication capability overseas.

Second, the user behavior prediction module 101 may predict traffic usage of the user based on information about the traffic usage of the user. Here, the traffic usage of the user may refer to traffic usage preference of the user, so as to obtain a data traffic service matching with the traffic usage preference of the user from a network node, and meet personalized traffic demand of the user.

For example, the network node may analyze the key consumption zones of traffic, predict traffic usage preferences of the user (e.g., may predict whether the user is a game-preferred user, a short video-preferred user, a long video-preferred user, etc.) based on monitoring and statistics of traffic usage for applications in the electronic terminal, to send information from the network node to the electronic terminal recommending personalized data traffic services matching the traffic usage preferences of the user.

As an example, traffic usage of a user may be predicted based on at least one of the following: user profile, traffic usage of the user, applications used by the user, application usage duration of the user, and application usage frequency of the user. For example, the traffic consumption type of the user may be predicted based on the at least one type of information, and the traffic usage value of the user of the traffic consumption type may be used as the traffic usage value of the user. The process of predicting the traffic usage of the user will be described in detail in fig. 10, and the present invention is not described herein again.

In the third case, the user behavior prediction module 101 may predict the communication charge situation of the user based on information of the electronic terminal used by the user.

In one example, the user's communication cost condition may refer to a balance of the user's communication cost. At this time, the information of the electronic terminal used by the user may refer to a short message received by the electronic terminal.

That is, the balance of the communication charges of the user may be predicted based on the short message received by the electronic terminal, and when the predicted balance of the communication charges of the electronic terminal is less than or equal to a set value, the data traffic service is acquired from the network node 20 for providing the emergency communication capability through the acquired data traffic packet when the electronic terminal is in a defaulting shutdown. On the basis, when the predicted balance of the communication cost of the electronic terminal is less than or equal to the set value, the network node 20 may further send a reminding message to the electronic terminal 10 to prompt the user that the communication cost is due, so that when the electronic terminal is in a state of being due for outage, the acquired data traffic packet may be used for emergency communication. Aiming at the condition that the data traffic service is the SOFSIM data traffic packet, the method is to promote the SOFSIM data traffic service and promote the conversion of the traditional SIM user into the traditional SIM user

An efficient way of SOFTSIM users.

In another example, a user's communication cost profile may refer to a traffic consumption profile in a tariff package of the user (e.g., a remaining traffic value in the tariff package). At this time, the information of the electronic terminal used by the user may refer to a short message received by the electronic terminal (e.g., a short message about a tariff package acquired from a network node) or a traffic usage value locally counted by the electronic terminal.

That is, the remaining traffic value in the tariff package of the electronic terminal may be predicted based on the short message received by the electronic terminal or the traffic usage value locally counted by the electronic terminal, and when the predicted remaining traffic value in the tariff package of the electronic terminal is smaller than the set traffic value, the network node 20 may send a prompt message to the electronic terminal 10 to prompt that the remaining traffic of the user is about to be used up, and the network node 20 may send a data traffic service to the electronic terminal 10.

In step S20, the detection module 102 detects whether there is an available data traffic service in the electronic terminal. For example, it may be detected whether an activated data traffic packet is present in the electronic terminal (it may also be detected whether the user has purchased a SOFTSIM data traffic packet of a predicted travel destination) or whether a remaining traffic value in the data traffic packet is greater than a traffic threshold.

If the detection module 102 detects that there is an available data traffic service in the electronic terminal, communication is performed using the detected available data traffic service. For example, when it is detected that an activated data traffic packet exists in the electronic terminal or that a remaining traffic value in the data traffic packet is greater than a traffic threshold value, it is determined that there is an available data traffic service detected in the electronic terminal.

If the detection module 102 does not detect that there is an available data traffic service in the electronic terminal, step S30 is executed: the SOFTSIM request module sends a request to the SOFTSIM application server 21 to obtain data traffic services. Optionally, the request for obtaining the data traffic service is a request for requesting a free SOFTSIM data traffic packet.

For example, when it is detected that there is no activated data traffic packet in the electronic terminal or that the remaining traffic value in the data traffic packet is not greater than (i.e., less than or equal to) the traffic threshold, it is determined that there is no data traffic service available in the electronic terminal.

Optionally, the request for obtaining the data traffic service includes information about the predicted user behavior. For example, information about the user's travel plan (e.g., travel destination, route points, airplane stop points, travel days, etc.) may be included in the request.

In step S40, the SOFTSIM packet request module 201 in the SOFTSIM application server 21 requests the data traffic service from the SOFTSIM packet management module in the virtual operator server (e.g., MVNE)22 in response to the received request for obtaining the data traffic service.

In step S50, the SOFTSIM packet management module 202 issues the requested data traffic service according to the request for acquiring the data traffic service.

As an example, the data traffic service may include data traffic packets and/or information about purchasing data traffic packets. Alternatively, the data traffic packet may be referred to as a SOFTSIM data traffic packet.

For example, the data traffic service may include at least one of: a globally available data traffic package, a data traffic package available at a destination of the travel plan, and a data traffic package available at a route point of the travel plan. Alternatively, the data traffic packet may be a directional traffic packet, a free data traffic packet, or a paid data traffic packet. The information about purchasing data traffic packets may include information that reminds of purchasing data traffic packets and/or information that recommends purchasing data traffic packets.

Here, the SOFTSIM data packet management module, after receiving the request for data traffic service, if it is determined that the received request is a request for a free data traffic packet, pushes the free data traffic packet directly in response to the received request for data traffic service without checking a payment status for the request, i.e., without requiring a user to purchase the data traffic packet.

As an example, a directed data traffic packet may refer to a data traffic packet usable by a specified application in an electronic terminal (e.g., a data traffic packet for use only by a WeChat application or a *** map application) or a data traffic packet for implementing a specified function (e.g., a data traffic packet usable only for purchasing SOFTSIM data packets). Alternatively, the traffic volume of the directed data traffic packets may be greater than the traffic volume of the non-directed data traffic packets. The directional data flow package has limited use range, is competitive in price, can efficiently trigger the purchase behavior of a user using the electronic terminal to the SOFTSIM data flow service through means of low price, personalized accurate recommendation, the advantages that the SOFTSIM does not need to be replaced with a card, additional free trial and the like, and is favorable for popularization of the SOFTSIM data flow service.

The SOFTSIM packet management module 202 may determine the type of the data traffic packets to be sent and the amount of the data traffic packets based on the user requirements.

In one example, the SOFTSIM packet management module 202 may determine the amount of the data traffic packets sent down according to the traffic consumption level of the user.

For example, SOFTSIM packet management module 202 may determine a traffic consumption level of the subscriber based on historical purchase records of data traffic packets by the subscriber, and determine an amount of traffic packets based on the traffic consumption level of the subscriber. Here, the higher the traffic consumption level of the subscriber, the higher the credit of the data traffic packet. At the moment, a user hierarchical grading mechanism can be established, and marketing strategies for users with different flow consumption grades are developed.

In another example, SOFTSIM packet management module 202 may determine the amount of data traffic packets that are reminded and/or recommended for purchase by: the method comprises the steps of counting the daily average traffic usage of a user, predicting the traveling days of a traveling plan of the user, and determining the traffic usage amount of a traffic data packet for reminding and/or recommending the user to purchase based on the counted daily average traffic usage and the predicted traveling days. For example, the daily average traffic usage of the user may be determined based on the statistics of the virtual operator server 23 or the statistics of the electronic terminal 10 itself. The daily average traffic usage of the user, the predicted trip plan of the user and/or the predicted trip days of the trip plan of the user, which are counted by the electronic terminal, may be extracted from the request for obtaining the data traffic service.

In step S60, the SOFTSIM packet sending module 203 sends the data traffic service (SOFTSIM packet) sent by the SOFTSIM packet management module 202 to the SOFTSIM receiving module in the electronic terminal 10.

The electronic terminal 10 according to an exemplary embodiment of the present invention may further include a display, and when the received data traffic service is information reminding or recommending the purchase of a data traffic package, the information may be displayed on the display of the electronic terminal.

By way of example, the information reminding or recommending the purchase of the data traffic package may be displayed in any of the following ways: displaying in a notification bar of the electronic terminal, displaying in a floating window of the electronic terminal, and displaying on a negative screen of the electronic terminal in a push notification manner.

In step S70, the SOFTSIM management module stores the SOFTSIM packet information (which may include, for example, IMSI-International Mobile Subscriber Identity, KI-key Identity, key, etc.) into a Trusted Execution Environment (TEE) 107 of the electronic terminal 10.

The electronic terminal 10 according to an exemplary embodiment of the present invention may further include an input module 110 for receiving a user input for activating the SOFTSIM packet. For example, in step S80, the input module 110 receives an operation for activating the SOFTSIM packet input by the user.

As an example, when the SOFTSIM application detects that the electronic terminal has reached a predicted travel destination or cannot judge the location and is in a no-network state, the user may be prompted to activate a free SOFTSIM packet, and the user may select to activate the free SOFTSIM packet so as to purchase a locally available package of SOFTSIM packets on the network using the activated free SOFTSIM packet. The presence state does not require a reminder and the user can use the existing network to perform the desired operation, such as purchasing a local SOFTSIM package.

In step S90, the SOFTSIM packet control module reads the SOFTSIM packet information from the trusted zone 107 in response to the received operation.

In step S110, the SOFTSIM packet control module 106 writes the SOFTSIM packet information, and drives the MODEM to perform network residence by interacting with the MODEM.

It should be understood that fig. 5 illustrates the information exchange flow for traffic acquisition between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM application server 21,

fig. 6 shows an information interaction flow for traffic acquisition between the electronic terminal 10 and the network node 20 in case the network node 20 is the SOFTSIM server 23.

Here, the information exchange flow shown in fig. 6 is different from the information exchange flow shown in fig. 5 only in that the SOFTSIM server 23 integrates the functions of the SOFTSIM application server 21 and the virtual operator server 22, that is, the SOFTSIM server 23 includes the data traffic service request module 201, the data traffic management module 202 and the data traffic service transmission module 203. Otherwise, the information interaction flow shown in fig. 6 is the same as the other processing procedures of the information interaction flow shown in fig. 5, and the details of this part of the present invention are not repeated.

The electronic terminal 10 and the network node 20 for implementing the traffic acquisition function according to the exemplary embodiment of the present invention can intelligently provide the emergency communication capability in the wireless state for the electronic terminal by predicting the user behavior, and implement "what is needed if provided". Meanwhile, the method brings value to both terminal equipment manufacturers and network operators, for example, the terminal equipment manufacturers can bring more convenient and better user experience to users using the electronic terminals, the method is beneficial to improving the activity and the viscosity of the users, attracting new users, generating the advantage of competitive differentiation and improving income share. The network operator can reduce the investment cost, improve the amount of terminal users and improve the income.

In a second exemplary embodiment, a procedure for implementing a traffic sharing function through information interaction between an electronic terminal and a network node is described.

Fig. 7 shows a block diagram of an electronic terminal 10 and a network node 20 for implementing a traffic sharing function according to an exemplary embodiment of the present invention.

As shown in fig. 7, the traffic sharing apparatus in the electronic terminal 10 according to the exemplary embodiment of the present invention includes a traffic sharing request module (corresponding to the group module 120 in the user group establishing mode), a receiving module 104, and a data traffic management module 105. The modules may be implemented by a general-purpose hardware processor such as a digital signal processor, a field programmable gate array, or the like, or by a special-purpose hardware processor such as a special-purpose chip, or may be implemented entirely by a computer program in a software manner, for example, as each module in an application program (e.g., an application program for implementing a traffic sharing function) 40 installed on an electronic terminal. Here, the electronic terminal 10 according to an exemplary embodiment of the present invention may further include a data traffic control module 106, a trusted zone 107, and a MODEM108, in addition to the above-described modules.

The traffic sharing apparatus in the network node 20 according to an exemplary embodiment of the present invention may include: a data traffic service request module 201 and a data traffic service sending module 203. In addition, the traffic acquiring device in the network node 20 may also include a data traffic management module 202, a group management module 204, and a traffic dynamic adjustment module 205.

In particular, the traffic sharing request module sends a traffic sharing request to the network node 20.

The group management module 204 in the network node 20 receives the traffic sharing request.

The data traffic management module 202 allocates sub data traffic services for the shared object from the data traffic services to be shared.

In one example, the data traffic service to be shared may be a data traffic service in an electronic terminal that sends a traffic sharing request, and information of a sharing object may be included in the traffic sharing request. As an example, the information of the shared object may include, but is not limited to, an identification of an electronic terminal used by the shared object.

In another example, the data traffic service to be shared may be a data traffic service in a specific electronic terminal, and at this time, the traffic sharing request may include information of the sharing object and information of the specific electronic terminal.

The data traffic service sending module 203 is configured to send the sub data traffic service to the shared object, that is, send the sub data traffic service to the electronic terminal used by the shared object.

Alternatively, in the present exemplary embodiment, the data traffic service may refer to a data traffic service with respect to a virtual subscriber identity module, SOFTSIM. Alternatively, the data traffic service may be a SOFTSIM data traffic packet, and the sub-data traffic service may be a sub-SOFTSIM data traffic packet, but the present invention is not limited thereto, and the data traffic service may also be other data traffic services than the data traffic packet related to the SOFTSIM.

For the case where the data traffic service is a SOFTSIM data traffic packet, network node 20 may be any one of the following servers, as an example: the system comprises a SOFSIM application server, a virtual operator server and a SOFSIM server with functions of the SOFSIM application server and the virtual operator server.

The following describes, with reference to fig. 8 and fig. 9, an information interaction flow for traffic sharing between the electronic terminal 10 and the network node 20 in the case that the network node 20 is the SOFTSIM application server 21, taking the data traffic service as the SOFTSIM data traffic packet as an example.

Fig. 8 shows a flowchart for implementing a traffic sharing function according to an exemplary embodiment of the present invention. Fig. 9 shows a first schematic diagram of an information interaction flow for traffic sharing between an electronic terminal 10 and a network node 20 according to an exemplary embodiment of the present invention. In the present example, the receiving module 104, the data traffic management module 105, the data traffic service request module 201, the data traffic management module 202, and the data traffic service transmitting module 203 shown in fig. 7 correspond to those in fig. 9, respectively

The system comprises a SOFSIM receiving module, a SOFSIM data packet control module, a SOFSIM data packet request module, a SOFSIM data packet management module and a SOFSIM data packet sending module.

Referring to fig. 9, when the primary user wishes to share the purchased SOFTSIM packet with the secondary user/loT device, the group module 120 in the electronic terminal used by the primary user may establish a user group to acquire information of the shared object by establishing the user group in step S501. The above-mentioned manner of obtaining the information of the shared object by establishing the user group is only an example, and the information of the shared object may also be obtained by other manners.

Here, the electronic terminal used by the primary user may refer to an electronic terminal for providing a data traffic service to be shared, and the electronic terminal used by the secondary user may refer to an electronic terminal for sharing a data traffic service to be shared, and the secondary user may include one or more secondary users, as an example. A shared object may refer to an object (i.e., may refer to a secondary user) for sharing data traffic services to be shared.

The master user may add the shared object to the user group by way of invitation (e.g., scanning a group two-dimensional code) or manual addition, the shared object may also actively apply for joining the user group, or the SOFTSIM application server 21 may recommend the shared object to the master user based on the analyzed social relationship about the master user. When a new shared object joins the user group, the group module of the electronic terminal (or loT device) used by the primary user or the secondary user may upload information of the new shared object to the group management module.

In step S502, the group module 120 in the electronic terminal used by the primary user or the secondary user uploads the group information of the established user group to the group management module in the SOFTSIM application server 21. Here, the group information may include information of a sharing object and information of a data traffic service to be shared, for example, an electronic terminal used by a primary user or a secondary user may determine a data traffic service of a designated user in a user group as the data traffic service to be shared according to a selection of the user.

The group management module creates a 'flow pool' according to the data flow service to be shared, and the flow consumed by all users in the user group comes from the flow pool. That is, the total traffic usage amount of all the users in the user group is the traffic amount of the data traffic service to be shared.

Here, the group module uploading the group information is equivalent to sending a traffic sharing request to the SOFTSIM application server 21.

In step S503, the SOFTSIM packet request module requests the sub-data traffic service allocated for the shared object from the virtual operator server 23 in response to the received traffic sharing request.

When the traffic sharing request includes information of the shared object and information of the designated electronic terminal, the SOFTSIM packet request module may determine, based on the traffic sharing request, a data traffic service in the designated electronic terminal as the data traffic service to be shared.

For the case that the group module establishes the user group, the traffic sharing request may include group information, since the group information includes information of the sharing object and information of the data traffic service to be shared. In this case, the SOFTSIM packet request module may determine the shared object and the data traffic service to be shared based on the group information in the received traffic sharing request.

When the traffic sharing request includes information of the shared object, the SOFTSIM packet request module may determine the shared object based on the received traffic sharing request, and determine the data traffic service in the electronic terminal that sent the traffic sharing request as the data traffic service to be shared.

In step S504, the SOFTSIM packet management module in the virtual operator server 23 allocates the sub data traffic service (i.e., sub SOFTSIM packets). Here, the number of sub SOFTSIM packets is the number of all users included in the user group minus one.

In step S505, the SOFTSIM packet transmission module transmits the sub SOFTSIM packet to the shared object. At this time, the secondary user may store the sub-SOFTSIM packet information to the trusted zone 107 after receiving the sub-SOFTSIM packet, and activate the sub-SOFTSIM packet according to an operation for activating the sub-SOFTSIM packet input by the user to perform network communication based on the sub-SOFTSIM packet sharing traffic in the data traffic service to be shared. Thus, after each sharing object in the user group receives the sub SOFTSIM data packet and selects to perform activation operation by self, all sharing objects can use the traffic in the data traffic packet to be shared to perform network communication. It should be understood that all sub-SOFTSIM packets need not be all activated, and may be selected for activation and use by the shared object according to its own needs.

In an optional embodiment, the SOFTSIM packet management module may determine the sub-data traffic service allocated to the shared object according to the predicted traffic usage of the shared object.

For example, traffic usage of a shared object may be predicted based on at least one of: user representation, traffic usage of the user, application used by the user, application usage duration of the user, and application usage frequency of the user.

The process of predicting traffic usage by a user is described below with reference to fig. 10.

FIG. 10 illustrates a schematic diagram of predicting traffic usage by a user, according to an exemplary embodiment of the invention.

For example, a traffic usage record for each user may be acquired, and traffic usage of each user may be predicted based on the acquired traffic usage of each user and/or a user profile of each user, so as to determine a traffic usage amount allocated to each sharing target based on the predicted traffic usage of each user.

Referring to fig. 10, alternatively, the manner of predicting the traffic usage of any user based on the acquired traffic usage record of any user and the user profile of any user may be:

determining the traffic usage time distribution condition (namely, a usage schedule) of any user according to the traffic usage condition of any user, the application used by any user, the application usage duration of any user, the application usage frequency of any user and the user portrait of any user; determining the traffic consumption distribution condition of any user according to the traffic usage condition of any user, the application used by any user, the application use duration of any user and the application use frequency of any user; determining the application preference of any user according to the application used by any user, the application use duration of any user, the application use frequency of any user and the user portrait of any user; determining the user type of any user according to the traffic use time distribution condition and the application preference of any user; and predicting the traffic usage of any user according to the traffic usage time distribution condition, the traffic consumption distribution condition, the application preference, the user type and the traffic historical usage of the user type. Alternatively, the prediction process described above may be implemented based on deep neural network techniques.

Returning to fig. 9, in step S506, the traffic dynamic adjustment module obtains the actual traffic usage value of the electronic terminal, and adjusts the sub-data traffic service allocated to each sharing object based on the actual traffic usage value of the sharing object, so that the traffic usage amount allocated to each sharing object can satisfy the traffic usage requirements of different sharing objects.

The traffic dynamic adjustment module may obtain the actual traffic usage of the electronic terminal from the electronic terminal, or may obtain the actual traffic usage of each electronic terminal from the virtual operator server. For the situation of obtaining the actual flow usage amount from the electronic terminal, the main electronic terminal and the sub-electronic terminal may upload the accurate flow usage value obtained by the local flow statistics and calibration module as the actual flow usage value to the flow dynamic adjustment module of the SOFTSIM application server 21, so that the flow dynamic adjustment module may obtain the actual flow usage value from the electronic terminal.

Here, the local traffic statistic calibration module is configured to calibrate the traffic usage value locally counted by the electronic terminal to obtain an accurate traffic usage value. The process of calibrating the local statistical traffic usage value will be described in detail in the third exemplary embodiment, and details of this part of the present invention are not repeated herein.

In step S507, when the traffic dynamic adjustment module determines that the sum of the actual traffic usage values of the primary user and the secondary user reaches the total amount of the data traffic service to be shared (i.e., the traffic amount of the traffic pool), a notification indicating that the traffic is used up may be sent to the primary electronic terminal and the secondary electronic terminal, and the SOFTSIM packet control modules in the primary electronic terminal and the secondary electronic terminal perform a deactivation operation on the SOFTSIM packet.

Fig. 11 illustrates a diagram for dynamically adjusting data traffic allocated to a user according to the actual traffic usage of the user according to an exemplary embodiment of the present invention.

As shown in fig. 11, the traffic may be allocated to each user according to the user type obtained by the analysis, and after the traffic shares for a period of time, the actual traffic usage value of each user is inconsistent with the expected traffic usage value, and at this time, the dynamic traffic quota allocation module adjusts the allocated traffic according to the actual traffic usage value of each user. For example, the allocated traffic quota module may dynamically adjust the allocated traffic quota for each subscriber based on the subscriber profile and the actual traffic usage values of each subscriber. Here, the deep neural network parameters may be reversely adjusted and trained according to the actual traffic usage values of the users, so as to improve the accuracy of predicting the traffic usage of the users.

It should be understood that, in addition to the above-mentioned case of adjusting the traffic distribution according to the actual traffic usage value of the user, when the traffic quota allocated by any one of the sharing objects has been used up, the dynamic traffic quota allocation module may allocate the remaining traffic in the "traffic pool" again according to the actual traffic usage value, and so on, until the traffic in the "traffic pool" is used up.

It should be understood that fig. 9 shows an information exchange flow for traffic sharing between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM application server 21, and fig. 12 shows an information exchange flow for traffic sharing between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM server 23.

Here, the information exchange flow shown in fig. 12 is different from the information exchange flow shown in fig. 9 only in that the SOFTSIM server 23 integrates the functions of the SOFTSIM application server 21 and the virtual operator server 22, that is, the SOFTSIM server 23 includes a traffic sharing request receiving module, a traffic sharing module, and a traffic providing module. Otherwise, the information interaction flow shown in fig. 12 is the same as the other processing procedures of the information interaction flow shown in fig. 9, and the details of this part of the present invention are not repeated.

According to the electronic terminal 10 and the network node 20 for implementing the traffic sharing function in the exemplary embodiment of the present invention, multiple users can share the same SOFTSIM data traffic packet for communication, and the traffic usage amount allocated to each user can be dynamically adjusted according to the actual traffic usage amount of the users sharing the same SOFTSIM data traffic packet. The traffic sharing mode does not increase the power consumption of the electronic terminal providing the data traffic service to be shared, and is not limited by the distance between the sharing objects, so that the sharing of the data traffic service is more convenient and intelligent.

In a third exemplary embodiment, a process of implementing a traffic calibration function through information interaction between an electronic terminal and a network node is described.

Fig. 13 shows a block diagram of an electronic terminal 10 and a network node 20 for implementing a traffic calibration function according to an exemplary embodiment of the present invention.

As shown in fig. 13, the traffic calibration apparatus in the electronic terminal 10 according to the exemplary embodiment of the present invention includes: a flow acquisition module 140 and a flow calibration module 150. In addition, the flow calibration apparatus in the electronic terminal 10 may further include: a calibration request module 160. The modules may be implemented by a general-purpose hardware processor such as a digital signal processor, a field programmable gate array, etc., or by a special-purpose hardware processor such as a special-purpose chip, etc., or may be implemented completely by a computer program in a software manner, for example, as each module in an application program (e.g., an application program for implementing a flow calibration function) 50 installed on an electronic terminal.

The traffic calibration apparatus in the network node 20 according to an exemplary embodiment of the present invention includes: a request receiving module 210, a sending module 211 and a calibration coefficient calculating module 212.

Specifically, the traffic obtaining module 140 is configured to obtain a traffic usage value of a data traffic packet of local statistics.

The traffic calibration module 150 is configured to calibrate the traffic usage value of the locally counted data traffic packets.

In one example, the traffic usage value of the local statistics may be calibrated using the traffic usage value obtained from the network node 20.

In this case, the calibration request module 160 may send a request to the request receiving module 210 to obtain the traffic usage value of the data traffic packet. The request receiving module 210 receives a request to obtain a traffic usage value for a data traffic packet.

The sending module 211 sends the traffic usage value counted by the network node 20 to the traffic calibration module 150 in the electronic terminal 10. The traffic calibration module 150 calibrates the locally counted traffic usage values using the traffic usage values obtained from the network nodes.

Optionally, using the traffic usage value obtained from the network node, the step of calibrating the locally statistical traffic usage value comprises at least one of: when the traffic utilization value of the local statistics reaches the set traffic utilization value, acquiring the traffic utilization value from the network node, and calibrating the traffic utilization value of the local statistics by using the traffic utilization value acquired from the network node; alternatively, the locally counted traffic usage values are calibrated based on traffic usage values obtained from the network nodes at predetermined times.

For example, in the case of performing calibration using traffic usage acquired from a network node, a plurality of calibration points may be set, one calibration point corresponding to one set traffic usage value, and errors may be dispersed by a calibration method of "coarse-to-fine, multipoint calibration".

For example, when it is detected that the traffic usage value of the data traffic packet of the local statistics reaches the set traffic usage value corresponding to any one calibration point, the traffic usage value is acquired from the network node, the traffic usage value of the local statistics at the any one calibration point is updated to the traffic usage value acquired from the network node, and the local statistics is continued with the updated traffic usage value of the local statistics as a reference.

In an alternative embodiment, the calibration of the local statistical traffic usage values assuming four calibration points are set is described below by way of example in fig. 14 and 15.

Fig. 14 illustrates a flow diagram for traffic calibration based on traffic usage values obtained from network nodes according to an exemplary embodiment of the invention.

As shown in fig. 14, at the first calibration point (i.e., calibration node 1): when the local statistical traffic usage Ld0 (for example, the traffic usage obtainable through the system interface of the electronic terminal) reaches a first set traffic usage (for example, the first set traffic usage may refer to 50% of the data traffic packet quota Pd in the electronic terminal), the local statistical traffic usage Cd1 is calibrated using the traffic usage Nd1 obtained from the network node, that is, the local statistical traffic usage is updated to the network node statistical traffic usage with reference to the network node statistical traffic usage, and then the local statistics continues based on the updated local statistical traffic usage. Meanwhile, the local statistical traffic usage Cd1 at the first calibration point, the network node statistical traffic usage Nd1, and the model of the electronic terminal are uploaded to the network node (such as the SOFTSIM application server or the virtual operator server) and stored in the historical traffic statistics database.

At the second calibration point (i.e., the calibration node 2), when the locally-counted traffic usage value (i.e., the sum of the locally-counted traffic usage value Cd1 calibrated at the previous calibration point and the traffic usage value Ld1 acquired through the system interface of the electronic terminal between the previous calibration point and the current calibration node) reaches a second set traffic usage value (which may be 75% of the data traffic packet quota Pd, as an example), the locally-counted traffic usage value Cd2 is calibrated using the network-node-counted traffic usage value Nd2 acquired from the network node, the locally-counted traffic usage value Cd2 is updated to the network-node-counted traffic usage value Nd2, and then local statistics continues based on the updated locally-counted traffic usage value. Meanwhile, the local statistical traffic usage value Ld1 at the second calibration point, the network node statistical traffic usage value Nd2+ Nd1, and the model of the electronic terminal are also uploaded to the network node for storage.

At the third calibration point (i.e., the calibration node 3), when the locally-counted traffic usage value (i.e., the sum of the locally-counted traffic usage value Cd2 calibrated at the previous calibration point and the traffic usage value Ld2 acquired through the system interface of the electronic terminal between the previous calibration point and the current calibration node) reaches a third set traffic usage value (which may be 87.5% of the data traffic packet quota Pd, as an example), the locally-counted traffic usage value Cd3 is calibrated using the network-node-counted traffic usage value Nd3 acquired from the network node, the locally-counted traffic usage value Cd3 is updated to the network-node-counted traffic usage value Nd3, and then local statistics continues on the basis of the updated locally-counted traffic usage value. Meanwhile, the local statistical traffic usage value Ld2 at the third calibration point, the network node statistical traffic usage value Nd3+ Nd2, and the model of the electronic terminal are also uploaded to the network node for storage.

At a fourth calibration point (i.e., the calibration node 4), when the locally-counted traffic usage (i.e., the sum of the locally-counted traffic usage Cd3 calibrated at the previous calibration point and the traffic usage Ld3 acquired through the system interface of the electronic terminal between the previous calibration point and the current calibration node) reaches a fourth set traffic usage (for example, the fourth set traffic usage is 97% of the data traffic packet quota Pd), calibrating the locally-counted traffic usage Cd4 by using the network node-counted traffic usage Nd4 acquired from the network node, updating the locally-counted traffic usage Cd4 to the network node-counted traffic usage Nd4, and if the calibrated traffic usage reaches or exceeds the data traffic packet quota, considering that the data traffic packet is exhausted, sending a prompt message to the electronic terminal to prompt that the user traffic is about to be exhausted, the SOFTSIM packet is also deactivated when the data traffic packet may be a SOFTSIM data traffic packet. Otherwise, a prompt is generated to prompt the user that the traffic is about to run out, and at certain time intervals (e.g., 10 minutes), the local statistical traffic usage value is calibrated again using the network node statistical traffic usage value obtained from the network node, and an iterative process is started. Meanwhile, the flow use value of the local statistics at the fourth calibration point, the flow use value of the network node statistics and the model of the electronic terminal are uploaded to the network node for storage.

If the traffic usage of the local statistics reaches the fourth set traffic usage value, or the traffic usage value is not obtained from the network node in the subsequent iteration process (that is, the network node does not respond to the request for obtaining the traffic usage value of the data traffic packet), it may be considered that the traffic of the data traffic packet is exhausted, and at this time, the user using the electronic terminal is prompted. The SOFTSIM packet is also deactivated when the data traffic packet may be a SOFTSIM data traffic packet. Optionally, when the network node does not respond, the sending of the traffic calibration request to the network node may be repeated a predetermined number of times, and if the network node still does not respond, the traffic of the data traffic packet is considered to be exhausted.

And if the calibrated flow usage reaches or exceeds the limit of the data flow packet in the subsequent iteration process, the flow of the data flow packet is considered to be exhausted, and prompt information is sent to the electronic terminal to prompt that the flow of the user is about to be exhausted. The SOFTSIM packet is also deactivated when the data traffic packet may be a SOFTSIM data traffic packet. Otherwise, the iteration will continue at certain time intervals (e.g., 10 minutes).

In another example, the locally statistical flow usage value may be calibrated according to a calibration coefficient.

Fig. 15 shows a flowchart for calculating calibration coefficients according to an exemplary embodiment of the present invention.

As shown in fig. 15, for example, a calibration coefficient may be generated based on historical calibration information, and the locally-counted flow usage value may be calibrated according to the generated calibration coefficient. Alternatively, the product of the local statistical flow usage value and the calibration coefficient may be used as the calibrated local statistical flow usage value.

Here, the calibration coefficients may be generated by the electronic terminal or by the calibration coefficient calculation module 212 in the network node. Here, the historical calibration information may refer to traffic usage values of network node statistics and local statistics at the set calibration point. Alternatively, the calibration coefficient may be calculated for each model of electronic terminal based on the historical calibration information of different models of electronic terminals.

In this case, a calibration point may be set, when the product of the local statistical traffic usage value Ld and the calibration coefficient α reaches a set traffic value (e.g., 97% of the traffic quota Pd of an activated traffic packet in the electronic terminal), the traffic usage value counted by the network node is obtained from the network node, if the traffic usage value is not obtained from the network node (i.e., the network node does not respond to the request for obtaining the traffic usage value of the data traffic packet), the traffic of the data traffic packet may be considered to be exhausted, and the user using the electronic terminal is prompted, the user using the data traffic packet may be prompted, the user may further deactivate the SOFTSIM packet when the data traffic packet may be a SOFTSIM data traffic packet.

Alternatively, the calibration coefficients may be determined by: and calculating a calibration coefficient corresponding to the electronic terminal of the preset model according to the local statistical flow use value of the electronic terminal of the preset model at least one calibration point and the flow use value of the network node statistics.

For example, the ratio of the local statistical traffic usage value at each calibration point to the network node statistical traffic usage value may be calculated, and the ratio of the sum of all the calculated ratios to the number of at least one calibration point is used as the calibration coefficient.

As an example, the calibration coefficient may be calculated by the following formula:

in the above equation, α denotes the calibration coefficient, N_iTraffic usage value, C, representing network node statistics at ith calibration point_iAnd (3) representing the flow use value of the local statistics of the electronic terminal at the ith calibration point, wherein i is more than or equal to 1 and less than or equal to n, and n is the number of the calibration points.

It should be understood that the closer the value of the calibration coefficient α is to 1, the smaller the error between the traffic usage value of the local statistics of the electronic terminal and the traffic usage value of the statistics of the network node.

Alternatively, the data traffic packet may be a virtual subscriber identity module, SOFTSIM, data traffic packet. In this case, the network node 20 may be, for example, any one of the following servers: the system comprises a SOFSIM application server, a virtual operator server and a SOFSIM server with functions of the SOFSIM application server and the virtual operator server. It should be understood that the traffic calibration method and apparatus described above can be used not only in the SOFTSIM data traffic service, but also in other scenarios requiring locally accurate traffic statistics.

According to the electronic terminal 10 and the network node 20 for implementing the flow calibration function in the exemplary embodiment of the present invention, the flow usage value of the local statistics is calibrated through the flow usage value counted by the network side or the calibration coefficient calculated based on the historical calibration information, so that the accuracy of the local flow statistics is improved, and especially the accuracy of the flow statistics of the large flow rate is improved more significantly.

In a fourth exemplary embodiment, a process of implementing a traffic transfer function through information interaction between an electronic terminal and a network node is described.

Fig. 16 shows a block diagram of an electronic terminal 10 and a network node 20 for implementing a traffic transfer function according to an exemplary embodiment of the present invention.

As shown in fig. 16, the traffic shifting apparatus in the electronic terminal 10 for implementing a traffic shifting function according to an exemplary embodiment of the present invention includes: a traffic transfer request module 170, a payment module 180, and a data traffic management module 105. When the electronic terminal 10 is an electronic terminal of a receiver of traffic diversion, the traffic diversion apparatus may further include: and a data traffic packet receiving module 190. As an example, the above modules may be implemented as respective modules in an application (e.g., an application for implementing a traffic transfer function) 60 installed on the electronic terminal. Here, the electronic terminal 10 according to an exemplary embodiment of the present invention may further include a data traffic control module 106, a trusted zone 107, and a MODEM108, in addition to the above-described modules.

The network node 20 for implementing a traffic transfer function according to an exemplary embodiment of the present invention includes: a second-hand data packet management module, a billing module 210, a payment management module 220, and a traffic transfer module. The second-hand data packet management module comprises a transfer request receiving module 230, and the traffic transfer module comprises a recycling module 260, a data packet management module 250 and a data packet sending module 240.

Specifically, the traffic transfer request module 170 sends a traffic transfer request to the network node. Here, the traffic transfer request may include a traffic roll-out request and/or a traffic roll-in request.

The transfer request receiving module 230 receives a traffic transfer request.

And the flow transfer module transfers the flow of the data flow packet of the moving-out party to a receiving party according to the received flow transfer request.

For example, the step of the traffic transfer module transferring the traffic of the data traffic packet of the moving party to the receiving party may include: recovering the data flow packet of the moving-out party; and distributing the new data traffic packet to the receiving party.

Optionally, in this exemplary embodiment, the data traffic packet may be a data traffic packet of the SOFTSIM, and at this time, the electronic terminal should support the SOFTSIM card function. In this case, the network node 20 may be, for example, any one of the following servers: the system comprises a SOFSIM application server, a virtual operator server and a SOFSIM server with functions of the SOFSIM application server and the virtual operator server.

The following describes an information interaction flow for traffic transfer between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM application server 21, with reference to fig. 17 and 18.

Fig. 17 shows a flow diagram for implementing a traffic diversion function according to an exemplary embodiment of the present invention. Fig. 18 shows a first schematic diagram of an information interaction flow for traffic transfer between the electronic terminal 10 and the network node 20 according to an exemplary embodiment of the present invention. In this example, the data traffic management module, the packet sending module, and the transfer request receiving module shown in fig. 16 correspond to the SOFTSIM packet management module, the SOFTSIM packet sending module, and the second-hand packet management module in fig. 18, respectively.

Referring to fig. 18, in step S111, the electronic terminal of the moving party or the electronic terminal of the receiving party may transmit a traffic transfer request to the SOFTSIM application server 21. For example, the traffic transfer request may include a traffic egress request and/or a traffic transfer request. That is, the electronic terminal of the moving-out party may send a traffic-out request to the SOFTSIM application server 21, and the electronic terminal of the receiving party may send a traffic-in request to the SOFTSIM application server 21. Optionally, the electronic terminal of the moving-out party may send a traffic directional transfer request to the electronic terminal of the receiving party, and the electronic terminal of the receiving party sends a traffic transfer request to the SOFTSIM application server 21 according to the traffic directional transfer request. The traffic forwarding request includes information about the traffic packet to be forwarded (i.e., information about the data traffic packet of the outbound side).

And a transfer request receiving module in the second-hand data packet management module receives the flow transfer request.

The transfer request receiving module judges the type of the traffic transfer request after receiving the traffic transfer request.

And when the transfer request receiving module determines that the type of the received flow transfer request is a flow transfer-out request sent by the electronic terminal of the moving-out party, the payment management module and the bill module confirm payment. It is necessary to confirm whether the receiver pays. For example, in step S112, the payment management module receives payment information indicating that the payment was successful, which is sent by the receiving party. The payment management module confirms with the bill module, and the bill module sends a confirmation certificate to the payment management module after the confirmation is completed.

In step S113, after the payment management module confirms that the payment is successful, the payment management module sends information indicating that the payment is successful to the recovery module, and the recovery module recovers the data traffic packet of the moving party.

For example, when receiving a traffic roll-out request, sales information about the remaining traffic value in a sales traffic data packet is issued to all electronic terminals establishing a connection with the SOFTSIM application server. When payment information indicating that a user of any one of the electronic terminals has successfully purchased a remaining traffic value in a sold data traffic packet is received from the any one of the electronic terminals, the traffic packet is recovered from the electronic terminals in response to the payment information.

In step S114, the SOFTSIM packet management module performs the recovery of the data traffic packet according to the instruction of the recovery module, that is, sends a notification of recovering the data traffic packet to the SOFTSIM packet control module.

In step S115, the SOFTSIM packet control module deletes the SOFTSIM packet from the trusted zone 107.

In step S116 (not shown in the figure), the SOFTSIM packet control module sends a notification indicating that the packet recovery is successful to the SOFTSIM packet management module.

In step S117, the SOFTSIM packet management module sends a notification indicating that the packet recovery is successful to the recovery module.

In step S118, the recycle module notifies the packet management module of the recycle result.

In step S119, the packet management module generates a new SOFTSIM packet and sends the new SOFTSIM packet to the packet sending module. That is, the packet management module assigns a new data traffic packet to the receiving party, where the packet management module may generate the new data packet according to the remaining traffic value in the data traffic packet of the moving-out party.

In step S120, the SOFTSIM packet sending module sends the new packet to the SOFTSIM receiving module of the receiving party.

In step S121, after the SOFTSIM application server 21 determines that the remaining traffic value is transferred to the receiving party or the data packet is successfully recovered, the SOFTSIM application server 21 returns the refund corresponding to the remaining traffic value in the traffic data packet to the payment module of the electronic terminal.

It should be understood that fig. 18 shows an information exchange flow for traffic transfer between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM application server 21, and fig. 19 shows an information exchange flow for traffic transfer between the electronic terminal 10 and the network node 20 in the case where the network node 20 is the SOFTSIM server 23.

Here, the information exchange flow shown in fig. 19 is different from the information exchange flow shown in fig. 18 only in that the SOFTSIM server 23 integrates the functions of the SOFTSIM application server 21 and the virtual operator server 22, that is, the SOFTSIM server 23 includes a traffic sharing request receiving module, a traffic sharing module, and a traffic providing module. Otherwise, the information interaction flow shown in fig. 19 is the same as the processing procedure of the information interaction flow shown in fig. 18, and details of this part of the present invention are not repeated.

According to the electronic terminal 10 and the network node 20 for implementing the traffic transfer function, which are provided by the exemplary embodiment of the invention, the unused SOFTSIM data packets are transferred between the devices through a series of operations such as recovery and redistribution, so that the transfer and the second-hand buying and selling of the SOFTSIM data packets between the users are realized, and the waste of traffic resources is avoided.

There is also provided, in accordance with an exemplary embodiment of the present invention, an electronic device including: a processor; a memory storing a computer program that, when executed by the processor, implements any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method.

There is also provided in accordance with an exemplary embodiment of the invention, a network node device, including: a processor; a memory storing a computer program that, when executed by the processor, implements any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method.

There is also provided, in accordance with an exemplary embodiment of the present invention, a computer-readable storage medium storing a computer program. The computer readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform any one of the following methods: the above-mentioned traffic acquisition method, the above-mentioned traffic sharing method, the above-mentioned traffic calibration method, and the above-mentioned traffic transfer method. The computer readable recording medium is any data storage device that can store data read by a computer system. Examples of the computer-readable recording medium include: read-only memory, random access memory, read-only optical disks, magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission through the internet via wired or wireless transmission paths).

By adopting the traffic acquiring, providing, sharing, calibrating and transferring method and the traffic acquiring, providing, sharing, calibrating and transferring equipment according to the exemplary embodiment of the invention, the functions of the existing data traffic service can be enriched, so that a user can use the data traffic service more conveniently and flexibly.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.

Claims

1. A traffic acquisition method, comprising:

predicting user behavior;

and acquiring data traffic service from the network node according to the predicted user behavior.

2. The traffic obtaining method according to claim 1, wherein the user behavior includes any one of: travel plan of the user, communication cost condition of the user and flow use condition of the user.

3. The traffic acquisition method according to claim 1 or 2, wherein the data traffic service comprises at least one of: the travel plan comprises a globally available data traffic packet, a data traffic packet available at a destination of the travel plan, a data traffic packet available at a route point of the travel plan, a directional traffic data packet, a free data traffic packet, a paid data traffic packet, information for reminding of purchasing the data traffic packet, and information for recommending of purchasing the data traffic packet.

4. The traffic obtaining method according to claim 1, wherein the step of obtaining data traffic services from a network node based on predicted user behavior comprises:

sending a request for acquiring data traffic service to a network node according to the predicted user behavior;

and receiving the data traffic service sent by the network node in response to the request for acquiring the data traffic service.

5. The traffic acquiring method according to claim 2, wherein the travel plan of the user is predicted based on at least one of the following information in the electronic terminal used by the user: the position information of the electronic terminal, the information received by the electronic terminal, the webpage use data in the electronic terminal and the application use data in the electronic terminal;

the traffic utilization of the user is predicted according to at least one of the following information: user representation, traffic usage of the user, application used by the user, application usage duration of the user, and application usage frequency of the user.

6. The traffic obtaining method according to any one of claims 1 to 5, wherein the data traffic service is a virtual subscriber identity module, SOFTSIM, data traffic packet, and the network node is a SOFTSIM management server and/or a virtual operator server.

7. A traffic providing method, comprising:

receiving a request for acquiring data traffic service, wherein the request for acquiring data traffic service is sent by an electronic terminal according to predicted user behavior;

and responding to the request for acquiring the data traffic service and sending the data traffic service to the electronic terminal.

8. A traffic sharing method, comprising:

receiving a flow sharing request;

distributing subdata traffic service for the shared object from the data traffic service to be shared;

and sending the sub-data traffic service to the shared object.

9. The traffic sharing method according to claim 8, further comprising:

determining sub-data traffic service distributed for the shared object according to the predicted traffic use condition of the shared object; and/or the presence of a gas in the gas,

and adjusting the sub-data traffic service distributed for the shared object according to the actual traffic usage of the shared object.

10. The traffic sharing method according to claim 9, wherein the traffic usage of the shared object is predicted according to at least one of the following information: user representation, traffic usage of the user, application used by the user, application usage duration of the user, and application usage frequency of the user.

11. The traffic sharing method according to any of claims 8-10, wherein the data traffic service is a virtual subscriber identity module, SOFTSIM, data traffic packet and the sub-data traffic service is a sub-SOFTSIM data traffic packet.

12. A traffic sharing method, comprising:

sending a flow sharing request to a network node so that the network node provides a sub-data flow service for a shared object from a data flow service to be shared, and the shared object shares the data flow service to be shared.

13. The traffic sharing method according to claim 12, further comprising:

and acquiring the information of the shared object in a mode of establishing a user group.

14. A method of flow calibration, comprising:

acquiring a flow use value of a data flow packet of local statistics;

the flow usage value is calibrated.

15. The flow calibration method of claim 14, wherein the calibrating the flow usage value comprises at least one of:

calibrating the locally counted traffic usage value using the traffic usage value obtained from the network node;

and calibrating the flow use value of the local statistics according to the calibration coefficient.

16. The traffic calibration method according to claim 14 or 15, wherein the data traffic packet is a virtual subscriber identity module, SOFTSIM, data traffic packet, and the network node is a SOFTSIM management server and/or a virtual operator server.

17. A method of flow calibration, comprising:

receiving a request for acquiring traffic use information of a data traffic packet;

and sending the traffic usage information counted by the network node to the electronic terminal.

18. The flow calibration method of claim 17, the flow usage information comprising flow usage values and/or calibration coefficients.

19. A traffic diversion method, comprising:

receiving a flow transfer request;

and transferring the flow of the data flow packet of the removing party to a receiving party according to the flow transfer request.

20. The traffic shifting method of claim 19, wherein the traffic shifting request comprises: and the flow transfer-out request of the moving party and/or the flow transfer-in request of the receiving party.

21. The traffic shifting method of claim 19, wherein the step of shifting the traffic of the data traffic packets of the outgoing party to the receiving party comprises:

recovering the data traffic packet of the moving party;

and distributing the new data traffic packet to the receiver.

22. The traffic shifting method according to any of claims 19-22, wherein the data traffic packets are virtual subscriber identity module, SOFTSIM, data traffic packets.

23. A traffic diversion method, comprising:

and sending a flow transfer request to the network node so that the network node transfers the flow of the data flow packet of the moving-out party to a receiving party according to the flow transfer request.

24. The traffic shifting method of claim 23, wherein the traffic shifting request comprises: traffic roll-out requests and/or traffic roll-in requests.

25. The traffic shifting method according to claim 23, further comprising:

according to the indication of the network node, recovering the data traffic packet; and/or;

and receiving the transferred data traffic packet sent by the network node.

26. An electronic device, characterized in that the electronic device comprises:

a processor;

a memory storing a computer program that, when executed by the processor, implements any one of the following methods: a traffic acquisition method according to any one of claims 1-6, a traffic sharing method according to claim 12 or 13, a traffic calibration method according to any one of claims 14-16, a traffic transfer method according to any one of claims 23-25.

27. A network node device, characterized in that the network node device comprises:

a processor;

a memory storing a computer program that, when executed by the processor, implements any one of the following methods: a traffic acquisition method according to claim 7, a traffic sharing method according to any one of claims 8-11, a traffic calibration method according to claim 17 or 18, a traffic transfer method according to any one of claims 19-22.

28. A computer-readable storage medium storing a computer program which, when executed by a processor, implements any one of the following methods:

the traffic acquisition method according to any one of claims 1 to 6, the traffic acquisition method according to claim 7, the traffic sharing method according to any one of claims 8 to 11, the traffic sharing method according to claim 12 or 13, the traffic calibration method according to any one of claims 14 to 16, the traffic calibration method according to claim 17 or 18, the traffic transfer method according to any one of claims 19 to 22, the traffic transfer method according to any one of claims 23 to 25.