CN113055877A

CN113055877A - Cloud card distribution method and device, electronic equipment and storage medium

Info

Publication number: CN113055877A
Application number: CN202010657694.1A
Authority: CN
Inventors: 刘珍慧; 龚智辉
Original assignee: Shenzhen Youke Yunlian Technology Co ltd
Current assignee: Shenzhen Youke Yunlian Technology Co ltd
Priority date: 2020-07-09
Filing date: 2020-07-09
Publication date: 2021-06-29
Anticipated expiration: 2040-07-09
Also published as: WO2022007902A1; CN113055877B

Abstract

The application is applicable to the technical field of communication, and provides a cloud card distribution method and device, electronic equipment and a storage medium. The method comprises the following steps: responding to a card distributing request sent by terminal equipment, and acquiring a target application type; determining a cloud card type list according to the target application type; sending the cloud card type list to the terminal equipment; responding to a selection operation result sent by terminal equipment, and distributing a target cloud card for the terminal equipment; the selection operation result is generated by the terminal device in response to the selection operation of the user for the cloud card type list. It should be understood that the application type information is obtained to identify the general requirements of the user by responding to the card distribution request sent by the terminal, and the cloud card type list is generated according to the application type information. The real requirements of the user are sensed through the selection operation of the user on the cloud card type list, so that the aim of distributing the cloud card which meets the actual requirements of the user to the user is fulfilled.

Description

Cloud card distribution method and device, electronic equipment and storage medium

Technical Field

The present application belongs to the field of communications technologies, and in particular, to a cloud card allocation method and apparatus, an electronic device, and a storage medium.

Background

The cloud card CloudSIM is a Subscriber Identity Module (Subscriber Identity Module) that distributes cloud card information to devices applying the cloud card through a server. In an application mode of a cloud card, a server sends cloud card information to terminal equipment, and the terminal equipment registers an operator network according to the cloud card information to realize wireless communication. The cloud card information includes, but is not limited to, an ICCID (integrated circuit card Identity), an IMSI (International Mobile Subscriber Identity), and some information of a carrier.

With the growth of users using cloud card services, the behaviors of the users using the cloud cards are in a diversified trend, such as playing games, watching videos and performing network social activities through the cloud cards. It can be understood that the demands of users on the application of the cloud card are more and more diversified. At present, a cloud server directly allocates a usable cloud card for a user, and the cloud card suitable for the user requirement cannot be allocated for the user according to the actual requirement of the user.

Disclosure of Invention

The embodiment of the application provides a cloud card distribution method and device, electronic equipment and a storage medium, which can solve at least part of the problems.

In a first aspect, an embodiment of the present application provides a method for allocating a cloud card, including:

responding to a card distributing request sent by terminal equipment, and acquiring a target application type;

determining a cloud card type list according to the target application type;

sending the cloud card type list to the terminal equipment;

responding to a selection operation result sent by terminal equipment, and distributing a target cloud card for the terminal equipment; the selection operation result is generated by the terminal device in response to the selection operation of the user for the cloud card type list.

It should be understood that, in the embodiment provided in the present application, the application type information is obtained by responding to the card distribution request sent by the terminal to identify the approximate requirement of the user, and the cloud card type list is generated according to the application type information. The real requirements of the user are sensed through the selection operation of the user on the cloud card type list, so that the aim of distributing the cloud card which meets the actual requirements of the user to the user is fulfilled.

In a second aspect, an embodiment of the present application provides a method for acquiring a cloud card, including:

responding to the received card distributing instruction, and sending a card distributing request to a server;

acquiring a cloud card type list sent by the server; the cloud card type list is determined by the server according to the target application type;

responding to the received selection operation of the user for the cloud card type list, and sending a selection operation result to the server; the selection operation result is used for indicating the server to distribute the cloud card for the terminal equipment target;

and receiving the target cloud card distributed by the server.

In a third aspect, an embodiment of the present application provides an apparatus for allocating a cloud card, including:

the first response module is used for responding to a card distributing request sent by the terminal equipment and acquiring a target application type;

the cloud card type list determining module is used for determining a cloud card type list according to the target application type;

the cloud card type list sending module is used for sending the cloud card type list to the terminal equipment;

the second response module is used for responding to a selection operation result sent by the terminal equipment and distributing the target cloud card to the terminal equipment; the selection operation result is generated by the terminal device in response to the selection operation of the user for the cloud card type list.

In a fourth aspect, an embodiment of the present application provides an apparatus for acquiring a cloud card, including:

the third response module is used for responding to the received card distributing instruction and sending a card distributing request to the server;

the cloud card type list acquisition module is used for acquiring a cloud card type list sent by the server; the cloud card type list is determined by the server according to the target application type;

the fourth response module is used for responding to the received selection operation of the user for the cloud card type list and sending a selection operation result to the server; the selection operation result is used for indicating the server to distribute the cloud card for the terminal equipment target;

and the target cloud card receiving module is used for receiving the target cloud cards distributed by the server.

In a fifth aspect, an embodiment of the present application provides an electronic device, including:

a memory, a processor and a computer program stored in the memory and executable on the processor, the computer program, when executed by the processor, implementing the method steps of the first aspect.

In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including: the computer readable storage medium stores a computer program which, when executed by a processor, performs the method steps of the first aspect described above.

In a seventh aspect, this application provides a computer program product, which when run on an electronic device, causes the electronic device to perform the method steps of the first aspect.

It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic diagram of a system provided by an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for allocating a cloud card according to an embodiment of the present application;

fig. 3 is a schematic information interaction flow diagram of a cloud card distribution method according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating a cloud card type list displayed by a terminal device according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a method for allocating a cloud card according to another embodiment of the present application;

fig. 6 is a schematic flowchart of a method for allocating a cloud card according to another embodiment of the present application;

fig. 7 is a schematic flowchart of a method for allocating a cloud card according to another embodiment of the present application;

fig. 8 is a schematic flowchart of a method for acquiring a cloud card according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a distribution device of a cloud card according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an acquisition apparatus of a cloud card according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

The cloud card is a user identification card with card information stored in the cloud. The mobile communication network can be connected to the terminal equipment through the cloud card by sending the card information of the cloud card to the terminal equipment. In the prior art, a user sends a card distribution request to a server for distributing a cloud card, and the server distributes a cloud card that can be used in a geographic location to the user according to user information, such as geographic location information.

However, the purpose or requirement of the user to access the mobile communication service by using the cloud card is various, and different requirements correspond to different network performance requirements.

For example, if a user uses a cloud card to access a mobile communication network for playing a game, the user's requirements for the rate and delay of the network are high. It is often necessary to assign a high-rate, low-latency cloud card to the user to meet the user's needs.

For another example, the purpose of using the cloud card by the user is to watch a video through accessing the mobile communication network by the cloud card, and then, the demand of the user is high in traffic consumption and high in speed requirement. The cloud card with high flow and high speed is generally required to be allocated to the user to meet the requirement of the user.

For another example, if the user uses the cloud card to access the mobile communication network through the cloud card and then uses the social-class application, the traffic and speed requirements of the network for the user are low. It is usually sufficient to assign the user a cloud card with limited traffic at a rate that can substantially satisfy social applications.

However, at present, the server cannot sense the user requirements, and therefore the cloud card cannot be allocated to the user according to the user requirements. After a cloud card is distributed to a user, the performance of a mobile communication network accessed by the cloud card or the package flow of the cloud card can not meet the requirements of the user easily, so that the user experience is poor; or the performance of the mobile communication network accessed by the cloud card or the package flow of the cloud card far exceeds the requirement of the user, so that the resource waste is caused.

Therefore, how to sense the user requirements and allocate the cloud cards to the users through the sensed user requirements becomes a problem to be solved.

In the embodiment provided by the application, the application type information is acquired by responding to the card distributing request sent by the terminal equipment so as to identify the approximate requirement of the user, and the cloud card type list is generated according to the application type information. The real requirements of the user are sensed through the selection operation of the user on the cloud card type list, so that the aim of distributing the cloud card which meets the actual requirements of the user to the user is fulfilled.

Fig. 1 illustrates a cloud card service system 100 provided in an embodiment of the present application. The cloud card service system comprises a server 110 and one or more terminal devices 120.

The server 110 is an independent server, a server cluster, a distributed server, and a server that provide a cloud card service. In some embodiments, the cloud card services include, but are not limited to, cloud card distribution services. In other embodiments, the cloud card services further include, but are not limited to, terminal access services, cloud card data analysis, cloud card billing systems, cloud card databases, and the like. When the embodiment of the application is implemented, the cloud card service may be deployed on one or more servers in combination with a specific situation, which is not specifically limited in the application.

The terminal device 120 includes, but is not limited to, a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and other terminal devices, and the specific type of the terminal device is not limited in the embodiment of the present application.

The cloud card CloudSIM is a Subscriber Identity Module (Subscriber Identity Module) that distributes cloud card information to devices using the cloud card through a server. In one implementation mode, the server sends the cloud card information to the terminal device, and the terminal device registers in an operator network according to the cloud card information to achieve wireless communication. The cloud card information includes, but is not limited to, an ICCID (integrated circuit card Identity), an IMSI (International Mobile Subscriber Identity), and some information of a carrier. In some embodiments, the cloud card may be a Subscriber identity module (Subscriber identity module) placed in a card carrier device communicatively connected to the server. The server reads the cloud card information through the card loading device and sends the cloud card information to the terminal device, and the terminal device registers the operator network according to the cloud card information to achieve wireless communication. The SIM card includes, but is not limited to, SIM (Subscriber Identity Module) card, UIM card (user Identity Module), USIM card (Universal Subscriber Identity Module), eSIM card (Embedded SIM), softSIM (soft SIM), or vSIM card (virtual SIM).

Wherein the terminal device 120 and the server 110 communicate via wireless communication.

Fig. 2 illustrates a cloud card allocation method provided in an embodiment of the present application, which is applied to the server 110 in the cloud card service system illustrated in fig. 1, and may be implemented by software and/or hardware of the server 110. As shown in fig. 2, the method includes steps S110 to S140. Fig. 3 is a schematic view illustrating an information interaction flow of a cloud card allocation method provided in an embodiment of the present application. As shown in fig. 3, the following describes a specific implementation principle of each step in conjunction with fig. 3.

And S110, responding to the card distributing request sent by the terminal equipment, and acquiring the type of the target application.

In an embodiment of the present application, the application type of the cloud card in the terminal device 120 includes at least one of a game application type, a video application type, a voice application type, and a social application type.

In an embodiment of the present application, the target application type may be obtained by: acquiring an application type contained in the card distributing request as the target application type; or, determining the target application type according to the application type contained in the historical card distribution request sent by the terminal equipment; or analyzing historical data of the terminal device communicated through the cloud card, and determining the type of the target application.

In an embodiment of obtaining the target application type, the terminal device 120 carries the application type in a card distribution request sent to the server 110, and the server parses the card distribution request to obtain the application type.

In another embodiment of obtaining the target application type, in a non-limiting scenario, the user may forget to select the application type in the terminal device. And the storage medium which is in communication coupling with the server stores the application type contained in the card distributing request which is sent to the server within the past preset time period by the terminal equipment. For example, the past predetermined period of time may be within the past month. For example, the type of application included in the card separation request sent by the terminal in the past month may be different. The target application type may be the most one of the application types included in the card distribution request sent by the terminal all the time in the past month. Without limitation, the card separation request sent last by the terminal may also include the application type as the target application type.

In another embodiment of obtaining the target application type, a storage medium coupled to the server stores historical data of the terminal device communicating through the cloud card, for example, traffic data of the terminal device in each past time period, and analyzes the historical traffic data of the terminal device communicating through the cloud card to determine the target application type. It should be understood that, when a user uses a terminal device to communicate through a cloud card, different application requirements of the user may cause traffic data of the user to present different distributions. For example, the traffic distribution of a video application is a distribution of a large traffic for a long time, the traffic distribution of a game application is a distribution of a large traffic and a small traffic alternately appearing for a long time, the traffic distribution of a social application is a distribution of a small traffic which is frequently bursty for a long time, and the traffic distribution of a voice is a distribution of a small traffic which is stable for a long time. Therefore, historical data of communication of the terminal device through the cloud card can be analyzed, and the target application type can be determined. The analysis of the historical traffic data communicated by the terminal device through the cloud card includes, but is not limited to, analysis through a statistical model, analysis through a neural network model, analysis through a big data model, and the like. In a non-limiting example, a mapping table of traffic characteristics and application types is established, historical traffic data of a user within a period of time is analyzed through the model to determine the traffic characteristics of the user, and the mapping table of the traffic characteristics and the application types is queried to determine the application types corresponding to the card distribution requests. In a non-limiting example, historical data of communication of the terminal device through the cloud card is analyzed, and the target application type is determined; the historical data is historical data of sampling time periods in past preset days; the sampling time period is a time period corresponding to the same sampling time in the past preset days as the current time, for example, the current time is 10 o 'clock in the morning, the same sampling time as the current time in the past preset days is 10 o' clock in the morning every 7 days, each sampling time is used as a reference time, and the preset time before, after, or before and after the sampling time is determined as the sampling time period, for example, 1 hour.

In the embodiment of the present application, as shown in fig. 3, the terminal device 120 sends a card distribution request to the server in response to the received card distribution instruction. Illustratively, when the terminal device is powered on or searches for the mobile communication network, the power-on process or the mobile communication network searching program automatically executes the card distribution instruction. Illustratively, the terminal device prompts the user to perform card distribution operation through user interaction, and the terminal device obtains a card distribution instruction by receiving the card distribution operation of the user. The terminal device transmits a card distribution request to the server 110 in response to the card distribution instruction. The card distribution request includes one of the application types, namely, a target application type. As shown in fig. 3, the server 110 receives the card distribution request and responds including, but not limited to, obtaining the target application type contained in the card distribution request.

And S120, determining a cloud card type list according to the target application type.

The cloud card type is a category of cloud cards which can be provided for users in operation. Each cloud card type contains a plurality of category attributes. In one non-limiting example, the category attributes can be divided into service area attributes, package traffic attributes, and network system attributes. The cloud card types may be classified by category attributes.

For example, the a carrier may provide 4 categories of user identification cards, which may be cloud cards serving as cloud cards, and if the user identification cards are classified by category attributes, the method includes: 5G + local card + current-limiting card; 5G + national card + unlimited card; 4G + local card + infinite card; 4G + national card + unlimited card. As can be seen, the cloud card type is a combination of category attributes of the cloud card, and each category attribute corresponds to one cloud card type. It should be understood that the classification of the category attributes of the cloud card may not be limited to the above examples.

In one implementation of the embodiment of the present application, each cloud card type provided by each operator includes a plurality of category attributes; corresponding to the target application type, the category attribute of each cloud card type has a corresponding application type weight; the determining the cloud card type list according to the application type comprises the following steps: and screening the cloud card types according to the application type weight aiming at the target application type, and determining the cloud card type list.

In another implementation manner of the embodiment of the application, a mapping table of mapping relationships between application types and cloud card types is prestored in a server, in the mapping table, multiple cloud card types may correspond to the same application type, and according to a received target application type, the server searches for a cloud card type corresponding to the application type in the mapping table to obtain each cloud card type corresponding to the target application type, so as to form a cloud card type list.

And S130, sending the cloud card type list to the terminal equipment.

In the embodiment of the present application, as shown in fig. 3, the server 110 sends the cloud card list to the terminal device 120.

S140, responding to a selection operation result sent by the terminal equipment, and distributing a target cloud card for the terminal equipment; the selection operation result is generated by the terminal in response to the selection operation of the user on the cloud card type list.

In the embodiment of the present application, as shown in fig. 3, after the terminal device 120 obtains the cloud card type list sent by the server 110, the cloud card type list is displayed on the user operation interface. Fig. 4 is a non-limiting example of terminal device 120 displaying cloud card type list 121. And the terminal equipment obtains the selection operation result of the user on the cloud card type list by receiving the selection operation of the user on the cloud card type list. And the terminal equipment sends the selection operation result to the server, and the server distributes the target cloud card for the terminal equipment according to the selection operation result. In a non-limiting manner, the server maintains a cloud card pool, the card pool includes cloud card information of each cloud card, and the server searches a cloud card of a cloud card type selected by the user in the cloud card pool as a target cloud card. It should be understood that the search operation may be to randomly select a cloud card of the user-selected cloud card type in the card pool as the target cloud card; the cloud card type selected by the user can be determined according to the preset sequence to serve as the target cloud card; the cloud card of the cloud card type selected by the user can be determined as the target cloud card according to the preset algorithm, the preset algorithm user prefers the cloud card of the cloud card type selected by the user, and the specific algorithm is not limited.

It can be understood that the general requirements of the user are identified through the application type information in the card distribution request sent by the terminal, and the cloud card type list is generated according to the application type information. The real requirements of the user are sensed through the selection operation of the user on the cloud card type list, so that the aim of distributing the cloud card which meets the actual requirements of the user to the user is fulfilled.

On the basis of the embodiment shown in fig. 2, in one example of the embodiment of the present application, each cloud card type provided by each operator includes a plurality of category attributes; and corresponding to the target application type, the category attribute of each cloud card type has a corresponding application type weight. Step S120, determining a cloud card type list according to the application type, as shown in fig. 5, may be replaced with step S120'.

And S120', screening the cloud card types according to the application type weight aiming at the target application type, and determining the cloud card type list.

In the embodiment of the application, referring to table 1, for operator a, the category attributes of the user identification card that can be used for the cloud card service may be classified into a service area attribute, a package flow attribute, and a network system attribute, and the category attributes may be subdivided into different categories, such as a local card, a national card, an unlimited flow, a limited flow, 2G/3G, 4G, 5G, and the like. Each category attribute corresponds to a weight per application type. The numerical values in table 1 represent weights; "filter" represents an infinitely small weight, which means that the corresponding card type is not suitable for this type of application and will be filtered out; the filtering condition that the residual flow is larger than a certain flow threshold value identifies the correspondence between the weight and the residual flow, and the larger the residual flow of the cloud card is; the weight is about high, the smaller the residual flow of the cloud card is, and the weight is about low; the corresponding relationship between the flow and the weight can be determined according to the operation experience or operation test of the cloud card service.

In a non-limiting example, a specific implementation manner of screening the cloud card types according to the application type weight may be that a weight corresponding to the target application is obtained for each category attribute of each cloud card type, and the weights of all the category attributes are added to obtain a total weight of the cloud card type. Thus, the total weight value of each cloud card type is obtained.

TABLE 1

On the basis of the embodiment shown in fig. 5, in an example of the embodiment of the present application, the card distribution request further includes at least one of user location information and package information; corresponding to the user position information, the category attribute of each cloud card type has a corresponding position weight; and corresponding to the package information, the category attribute of each cloud card type has a corresponding package weight. In some embodiments, the server records the traffic information of the cloud card service used by the user through the terminal device within a past preset time length, for example, a past week, and generates a user traffic tag for the user; and corresponding to the user traffic label, the category attribute of each cloud card type has a corresponding label weight. In one non-limiting example, the traffic labels of users can be divided into two categories, large and small traffic users, respectively.

Step S120', for the target application type, the cloud card types are screened according to the application type weight, and the cloud card type list is determined, as shown in fig. 6, which may be replaced with step S120 ″.

And S120', aiming at the target application type, screening cloud card types according to at least one of the user position weight, the package weight and the label weight and the application type weight, and determining the cloud card type list.

In the embodiment of the present application, for the target application type, screening the cloud card type according to the user location weight, the package weight, and the application type weight is described as an example. Referring to table 2, for operator B, the category attributes of the user identification card that can be used for the cloud card service may be classified into a service area attribute, a package traffic attribute, and a network format attribute, and the category attributes may be subdivided into different categories, such as a local card, a national card, an unlimited traffic, a limited traffic, 2G/3G, 4G, 5G, and the like. Each category attribute corresponds to a weight per application type. The values in table 2 represent weights; "filter" represents an infinitely small weight, which means that the corresponding card type is not suitable for this type of application and will be filtered out; the filtering condition that the residual flow is larger than a certain flow threshold value identifies the correspondence between the weight and the residual flow, and the larger the residual flow of the cloud card is; the weight is about high, the smaller the residual flow of the cloud card is, and the weight is about low; the corresponding relationship between the flow and the weight can be determined according to the operation experience or operation test of the cloud card service.

TABLE 2

In the embodiment of the present application, a plurality of factors need to be considered for setting the weight of the category attribute, and how the location weight, the package weight, and the application type weight are determined is described below with reference to table 2 in an implementation manner.

The cloud card pool is generally a home country card, which can only be used in the country to which the card belongs, and the country information in the location information reported by the device is directly used as a filtering condition to filter the cloud cards which can not be used in the current country.

And the equipment reports the position in the position information, and for the local card, if the position reported by the terminal is not matched with the usable position of the local card, the local card cannot be distributed. The device reports the position information directly as a filtering condition to filter the cloud cards which can not be used in the current area.

The user package information contains packages ordered by the end user at the cloud card service provider and packages of the cloud card at the operator. The package billing format may be close or similar. The user package also has the difference of validity period or flow size or service country range, but the difference is not a factor influencing the card distribution. The user package factors influencing the card distribution mainly lie in potential user experience requirements or potential traffic use behaviors with the user. The package attributes are therefore mainly distinguished into directed traffic packets and generic traffic packets.

A directed traffic packet in package information refers to a particular package that may be strongly related to an application. Such as video packets, voice packets, game packets. The directional traffic packet contains general traffic. The general traffic packet is a data traffic packet for normal internet access. This factor is a potential factor. The user selects a purchase indicating that the user has an intention to use a certain type of application. But the user purchases the directed traffic packet and does not necessarily watch the video and play the game. The user purchases the universal traffic package and may also choose to play games or watch videos, etc. Therefore, for the user using the directional traffic packet, the card distribution considers that the influence of the factor on the cloud card is mainly reflected on the package traffic of the cloud card and the speed of the cloud card.

Referring to table 2, the card assignment priorities are prioritized according to weight evaluation. For a cloud card service system, the user experience is higher in priority than the cost requirement, so that the total weight of a card with limited quantity supporting 5G is 100 higher than that of a card with unlimited quantity supporting 4G. The card total weight 300 having both attributes is prioritized higher. The service range of the local card is small, so that the priority of the local card is higher than that of the national card when the other attribute weight values are the same.

The package information is general flow, no specific requirement is made on the card, and the influence of the factor is small. According to the principle of preferentially distributing the large residual flow. Under the factor, the 4G card has higher priority than the 5G card, the unlimited card has higher priority than the limited flow card, but the flow has higher system weight than the system.

In the application type weight, for the game application type: the requirements are small time delay, high speed and large consumed flow. In the game application type, 5G is supported, an unlimited package is formed, and a local card is an added item. But the weighting is most important in 5G cards, followed by unlimited set of meal cards, and finally by local cards. This is to ensure that the 5G supported card priority is higher than the 4G local card priority for an unlimited package. The card for the unlimited package is prioritized higher than the local card. The total weight of the card and the subentry supporting the three attributes is 360, so that the priority can be guaranteed to be certain highest.

If the game type application 5G is to ensure absolute priority, the weight is higher than the weight of other attributes of other cards in the vertical direction. Considering the weight of the game application type of the 4G card in the general flow factors, the weight is more important than the weight of the place with contradictory scoring on the standard by other factors in the transverse direction. The local card is delayed, if only 4G card exists, the local card can be ensured to have higher weight value than the 4G national card of the general flow factor in the transverse direction. As the game application belongs to the application with high requirement on stability, cards need to be changed as few as possible in the using process. If the system has only cards with limited traffic, then the flow is guaranteed to be above a certain threshold for the remaining traffic of the first card picked. Even if 5G cards are used, the remaining flow rate does not reach the threshold value, and 4G infinite quantity cards or limited quantity cards meeting the condition can be distributed.

The video application type has a cache mechanism, so the requirement on time delay is not high. And the sensitivity to card changes is comparable to game play and voice. There is no requirement on latency. And ensuring that the weight of the unlimited card is higher than that of the system in the longitudinal direction and ensuring that the weight of the 4G card local card arranged in the unlimited card is higher than that of the directional flow in the transverse direction.

The voice application type requires small time delay and high speed. Voice traffic has high requirements on network stability, so for limited traffic cards, the remaining traffic is above a certain threshold. And longitudinally ensuring that the local limited traffic card has higher priority than the unlimited national card. In the horizontal direction, 5G cards are guaranteed to have higher priority than 4G unlimited cards.

And for the social application type, the normal internet surfing of the user is ensured. The social requirement on the cloud card is slightly low, and the data service is guaranteed to be normal and stable. Under the service scene, general card resources are required to be distributed as much as possible, and high-quality card resources are reserved for other users. Thus ensuring the preferential allocation of the 4G card in the longitudinal direction. And comparing the horizontal direction with the flow factor in the user package to ensure that the priority of the 4G card is higher than that of the 5G unlimited local card.

It should be noted that, for the cloud card supporting only 2G/3G, the use experience of such card is basically insufficient, so that all the use service scenarios of such card are negative scores, i.e. the priority is the lowest compared with other kinds of cards. Therefore, the attribute weight minus score is higher in the longitudinal direction than the plus score magnitude in the longitudinal direction of all the factors.

It should also be noted that the fixed weights are all high-level weights. There are also low level weights. Mainly a cloud card for a limited-traffic package. When other types of attributes are consistent and the system only has cloud cards with limited traffic, the cloud cards with larger residual traffic need to be preferentially allocated from the cost perspective because the residual traffic of each card is inconsistent. The remaining flow value changes dynamically, and at this time, the weight value also needs to change dynamically, so the weight value takes the value of the number of remaining G by taking the integer according to the unit of 1G. The more the remaining traffic, the higher the weight and the higher the assigned priority.

It should also be noted that when the system is divided into cards, the low priority weight is ignored when the high priority weight is already available for prioritization. The high priority weight is assigned by the low priority weight only if the high priority weight is equal.

The following is a non-limiting example of an embodiment of the present application, and an implementation manner of obtaining a weight value of a different cloud card type with reference to table 2 is described below. In this example, a user starts up in Guangdong Shenzhen in China, the user subscribes to a general traffic package, and the application type selected by the user is a video application type. Referring to table 2, the total weight of each cloud card category is obtained as shown in table 3.

TABLE 3

As can be seen from the above weights, the assignable cloud card priority is:

5G, unlimited amount card >4G, unlimited amount card >5G, limited flow >4G, limited flow card

The cloud card types that are larger to the left of the number have a higher priority than the cloud card types that are larger to the right of the number.

In a non-limiting example, after the priorities of the cloud card types are determined, in the idle cards, several different operators are available, and one or two cloud card categories with the highest total weight are recommended to each operator and presented to the user, so that the user can select the desired operator and cloud card category according to the subjective desire of the user. Therefore, the perception of the user requirements is realized, and the cloud card suitable for the user requirements is distributed to the user.

It should be understood that, reference is made to the above description taking as an example the screening of the cloud card types according to the user location weight, the package weight and the application type weight for the target application type. And screening the cloud card types according to the user position weight, the package weight, the label weight and the application type weight. Or, according to the user position weight, the package weight and the label weight, and the application type weight, the cloud card type is screened. And will not be described in detail herein.

Based on the embodiment shown in fig. 6, in an example of the embodiment of the present application, after the cloud card is allocated to the terminal device according to the selection operation result in step S140, as shown in fig. 7, step S150 is further included.

S150, obtaining a test result of the terminal device on the target cloud card; or obtaining an evaluation result generated by the terminal device in response to the evaluation operation of the user for the target cloud card.

On the basis of the embodiment, each cloud card category comprises historical evaluation attributes; the historical evaluation attribute is obtained by counting the test result or the evaluation result of the cloud card category within a preset time period; corresponding to the target application type, the historical evaluation attribute of each cloud card type has a corresponding historical evaluation weight; the screening of the cloud card types according to the application type weight of the type attribute aiming at the target application type to determine the cloud card type list comprises the following steps: and screening the cloud card types according to the application type weight and the historical evaluation weight aiming at the target application type, and determining the cloud card type list.

After the server allocates the target cloud card to the terminal device, the user can select to test the currently allocated target cloud card to obtain a test result in the process that the user uses the terminal device. And the terminal equipment uploads the test result to the server. And in a non-limiting manner, the terminal device may also periodically test the target cloud card to obtain a test result, and the terminal device uploads the test result to the server. The test results include, but are not limited to: the method comprises the following steps of testing data such as application type, user information, national information, IMSI, cloud card PLMN, registered PLMN, LAC, TAC, CELL, mode, signal strength, peak uplink rate, peak downlink rate, peak time delay, average uplink rate, average downlink rate, average time delay and the like.

And in a non-limiting manner, the terminal equipment displays a use evaluation operation interface of the target cloud card to the user through a user interaction interface. And the terminal equipment responds to the evaluation operation of the user on the cloud card, generates an evaluation result and sends the evaluation result to the server.

In some embodiments, after obtaining the cloud card test performance indexes or the user evaluation results reported by the plurality of terminal devices, the server obtains the positions of the operators at the test performance indexes or the service levels of the application types of the test performance indexes through a preset statistical model. It should be understood that any statistical model may be employed, such as a big data statistical model, an artificial intelligence statistical model, or a numerical analysis statistical model. And is not particularly limited herein.

The cloud card type is screened according to the historical evaluation attribute, the cloud card is distributed to the user according to the user experience, the distributed target cloud card is enabled to better meet the application type of the user, and the requirement of the user is better met.

In some embodiments of the present application, after the terminal device 120 receives the target cloud card distributed by the server 110, the terminal device tests the target cloud card to generate a test result. And if the user is satisfied with the test result, the user continues to use the cloud card for communication. However, in some cases, if the user is not satisfied with the test result, for example, the user may display the cloud card type list sent by the server to the user by the terminal device by clicking a button displayed by the terminal device, where the test result is not satisfied. And in a non-limiting way, the type of the cloud card selected by the user last time is not shown. And the user performs the operation of selecting the cloud card type list again through the terminal equipment. The terminal equipment responds to the received re-selection operation of the user for the cloud card type list and sends a second selection result of the re-selection operation to the server; the second selection result is used for indicating the server to distribute the target cloud card for the terminal equipment again; and receiving the target cloud card distributed by the server. It should be understood that, at the server side, the server re-allocates the target cloud card to the terminal device in response to the second selection result sent by the terminal device; the second selection result is generated by the terminal device in response to the re-selection operation of the user for the cloud card type list.

It can be understood that by testing the target cloud card and obtaining the operation result whether the user is satisfied with the target cloud card, the requirement of the user can be further sensed, and if the user is satisfied with the currently allocated target cloud card, it is indicated that the allocated target cloud card has matched the requirement of the user. And if the user is not satisfied with the currently allocated target cloud card, further sensing the real requirement of the user through a second selection result. Therefore, the effect of distributing the cloud cards matched with the user requirements for the users is achieved.

Fig. 8 illustrates an obtaining method of a cloud card provided in an embodiment of the present application, which is applied to the terminal device 120 in the cloud card service system illustrated in fig. 1, and may be implemented by software and/or hardware of the terminal device 120. As shown in fig. 2, the method includes steps S210 to S240.

S210, responding to the received card distributing instruction, and sending a card distributing request to the server.

S220, acquiring a cloud card type list sent by the server; the cloud card type list is determined by the server according to the target application type.

S230, responding to the received selection operation of the user for the cloud card type list, and sending a selection operation result to the server; and the selection operation result is used for indicating the server to distribute the cloud card for the terminal equipment target.

And S240, receiving the target cloud card distributed by the server.

Optionally, the card separation request includes a target application type.

Optionally, the application type includes at least one of: a game application type, a video application type, a voice application type, and a social application type.

Optionally, the card distribution request includes at least one of user location information and package information.

Optionally, after receiving the cloud card allocated by the server, the method further includes: testing the currently distributed cloud card to generate a test result; or, generating an evaluation result in response to the received evaluation operation of the user on the currently allocated cloud card; and sending the test result and the evaluation result to the server.

It can be understood that the embodiment shown in fig. 8 and the embodiment shown in fig. 2 are based on the same inventive concept, and various embodiments and combinations of embodiments in the above embodiments and their advantages are also applicable to this embodiment, which is not described herein again.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Corresponding to the foregoing cloud card allocation method shown in fig. 2, fig. 9 shows an allocation apparatus for a cloud card according to an embodiment of the present application, including:

the first response module M110 is configured to respond to a card distribution request sent by the terminal device, and acquire a target application type;

a cloud card type list determining module M120, configured to determine a cloud card type list according to the target application type;

a cloud card type list sending module M130, configured to send the cloud card type list to the terminal device;

a second response module M140, configured to respond to a selection operation result sent by a terminal device, and allocate a target cloud card to the terminal device; the selection operation result is generated by the terminal in response to the selection operation of the user on the cloud card type list.

It is understood that various embodiments and combinations of the embodiments in the above embodiments and their advantages are also applicable to this embodiment, and are not described herein again.

Corresponding to the foregoing cloud card allocation method shown in fig. 8, fig. 10 shows an allocation apparatus for a cloud card according to an embodiment of the present application, including:

and a third response module M210, configured to send a card distribution request to the server in response to the received card distribution instruction.

A cloud card type list obtaining module M220, configured to obtain a cloud card type list sent by the server; the cloud card type list is determined by the server according to the target application type.

A fourth response module M230, configured to send a selection operation result to the server in response to a received selection operation of the user for the cloud card type list; and the selection operation result is used for indicating the server to distribute the cloud card for the terminal equipment target.

And the target cloud card receiving module M240 is configured to receive the target cloud card allocated by the server.

Fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device is used for implementing the server 110 or the terminal device 120 of the cloud card service system 100 in the embodiment of the present application. As shown in fig. 11, the electronic device D10 of this embodiment includes: at least one processor D100 (only one is shown in fig. 11), a memory D101, and a computer program D102 stored in the memory D101 and operable on the at least one processor D100, wherein the processor D100 implements the steps of any of the method embodiments described above when executing the computer program D102. Alternatively, the processor D100 implements the functions of the modules/units in the above-mentioned device embodiments when executing the computer program D102.

The electronic device D10 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The electronic device may include, but is not limited to, a processor D100, a memory D101. Those skilled in the art will appreciate that fig. 11 is merely an example of the electronic device D10 and does not constitute a limitation of the electronic device D10, and may include more or fewer components than those shown, or some components in combination, or different components, such as input output devices, network access devices, etc.

Processor D100 may be a Central Processing Unit (CPU), and Processor D100 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage D101 may be an internal storage unit of the electronic device D10 in some embodiments, such as a hard disk or a memory of the electronic device D10. In other embodiments, the memory D101 may also be an external storage device of the electronic device D10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device D10. Further, the memory D101 may also include both an internal storage unit and an external storage device of the electronic device D10. The memory D101 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer programs. The memory D101 may also be used to temporarily store data that has been output or is to be output.

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.

The embodiments of the present application provide a computer program product, which when running on an electronic device, enables the electronic device to implement the steps in the above method embodiments when executed.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A cloud card distribution method is characterized by comprising the following steps:

determining a cloud card type list according to the target application type;

sending the cloud card type list to the terminal equipment;

2. The assignment method of claim 1, wherein each cloud card type provided by a respective operator includes a plurality of category attributes; corresponding to the target application type, the category attribute of each cloud card type has a corresponding application type weight;

the determining of the cloud card type list according to the target application type comprises the following steps:

and screening the cloud card types according to the application type weight aiming at the target application type, and determining the cloud card type list.

3. The assignment method of claim 2, wherein the card separation request further includes at least one of user location information, package information; corresponding to the user position information, the category attribute of each cloud card type has a corresponding position weight; corresponding to the package information, the category attribute of each cloud card type has a corresponding package weight; each terminal device corresponds to a user traffic label; corresponding to the user traffic label, the category attribute of each cloud card type has a corresponding label weight;

the screening of the cloud card types according to the application type weight aiming at the target application type to determine the cloud card type list comprises the following steps:

and aiming at the target application type, screening the cloud card type according to at least one of the user position weight, the package weight and the label weight and the application type weight, and determining the cloud card type list.

4. The allocation method according to claim 3, wherein after allocating the target cloud card to the terminal device, the method further comprises:

obtaining a test result of the terminal device on the target cloud card; or

And obtaining an evaluation result generated by the terminal equipment in response to the evaluation operation of the user for the target cloud card.

5. The assignment method of claim 4, wherein each cloud card category includes a historical rating attribute; the historical evaluation attribute is obtained by counting the test result or the evaluation result of the cloud card category within a preset time period; corresponding to the target application type, the historical evaluation attribute of each cloud card type has a corresponding historical evaluation weight;

and screening the cloud card types according to the application type weight and the historical evaluation weight aiming at the target application type, and determining the cloud card type list.

6. The allocation method according to any of claims 1 to 5, wherein the target application type comprises at least one of:

a game application type, a video application type, a voice application type, and a social application type.

7. The allocation method of claim 1, wherein obtaining a target application type comprises:

acquiring an application type contained in the card distributing request as the target application type; or the like, or, alternatively,

determining the target application type according to the application type contained in the historical card distribution request sent by the terminal equipment; or the like, or, alternatively,

and analyzing historical data of the terminal equipment communicated through the cloud card, and determining the type of the target application.

8. The allocation method of claim 1, further comprising:

responding to a second selection result sent by the terminal equipment, and reallocating the target cloud card for the terminal equipment; the second selection result is generated by the terminal device in response to the re-selection operation of the user for the cloud card type list.

9. The method for acquiring the cloud card is applied to terminal equipment, and comprises the following steps:

responding to the received selection operation of the user for the cloud card type list, and sending a selection operation result to the server; the selection operation result is used for indicating the server to distribute a target cloud card for the terminal equipment;

and receiving the target cloud card distributed by the server.

10. The acquisition method according to claim 9, wherein the card separation request includes an application type.

11. The acquisition method of claim 10, wherein the application type comprises at least one of:

12. The acquisition method of claim 10, wherein the card separation request further includes at least one of user location information and package information.

13. The acquisition method according to any one of claims 9 to 12, wherein after the receiving the target cloud card assigned by the server, the acquisition method further comprises:

testing the currently distributed cloud card to generate a test result; or the like, or, alternatively,

generating an evaluation result in response to the received evaluation operation of the user on the currently distributed cloud card;

and sending the test result and the evaluation result to the server.

14. The acquisition method of claim 13, after the generating test results, further comprising:

responding to the received re-selection operation of the user for the cloud card type list, and sending a second selection result of the re-selection operation to the server; the second selection result is used for indicating the server to distribute the target cloud card for the terminal equipment again;

and receiving the target cloud card distributed by the server.

15. A cloud card distribution device, comprising:

16. An acquisition device of a cloud card, comprising:

the fourth response module is used for responding to the received selection operation of the user for the cloud card type list and sending a selection operation result to the server; the selection operation result is used for indicating the server to distribute a target cloud card for the terminal equipment;

17. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the allocation method according to any one of claims 1 to 8 or the acquisition method according to any one of claims 9 to 14 when executing the computer program.

18. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the allocation method according to any one of claims 1 to 8, or the acquisition method according to any one of claims 9 to 14.