WO2022007902A1 - 一种云卡的分配方法、装置、电子设备及存储介质 - Google Patents

一种云卡的分配方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2022007902A1
WO2022007902A1 PCT/CN2021/105259 CN2021105259W WO2022007902A1 WO 2022007902 A1 WO2022007902 A1 WO 2022007902A1 CN 2021105259 W CN2021105259 W CN 2021105259W WO 2022007902 A1 WO2022007902 A1 WO 2022007902A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud card
card
cloud
terminal device
type
Prior art date
Application number
PCT/CN2021/105259
Other languages
English (en)
French (fr)
Inventor
刘珍慧
龚智辉
Original Assignee
深圳优克云联科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳优克云联科技有限公司 filed Critical 深圳优克云联科技有限公司
Publication of WO2022007902A1 publication Critical patent/WO2022007902A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the present application belongs to the field of communication technologies, and in particular, relates to a cloud card distribution method, device, electronic device and storage medium.
  • Cloud SIM CloudSIM is a subscriber identity module (Subscriber Identity Module) that distributes cloud card information to devices that apply cloud cards through a server.
  • the server sends the cloud card information to the terminal device, and the terminal device registers the operator network according to the cloud card information to realize wireless communication.
  • the cloud card information includes but is not limited to ICCID (Integrate circuit card identity, integrated circuit card identification code), IMSI (International Mobile Subscriber Identity, International Mobile Subscriber Identity) and some information of the operator, etc.
  • cloud server directly allocates a cloud card that can be used to the user, and cannot allocate a cloud card suitable for the user's needs according to the user's actual needs.
  • Embodiments of the present application provide a cloud card distribution method, device, electronic device, and storage medium, which can solve at least part of the above problems.
  • an embodiment of the present application provides a method for allocating a cloud card, including:
  • a target cloud card is allocated to the terminal device; the selection operation result is generated by the terminal device in response to a user's selection operation on the cloud card type list.
  • the application type information is obtained to identify the general needs of the user, and a cloud card type list is generated according to the application type information.
  • a cloud card type list is generated according to the application type information.
  • an embodiment of the present application provides a method for acquiring a cloud card, including:
  • the 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 selection operation result is sent to the server; the selection operation result is used to instruct the server to allocate a cloud card to the terminal device target;
  • an embodiment of the present application provides a cloud card distribution device, including:
  • a first response module configured to obtain the target application type in response to a card splitting request sent by the terminal device
  • a cloud card type list determining module configured to determine a cloud card type list according to the target application type
  • a cloud card type list sending module configured to send the cloud card type list to the terminal device
  • the second response module is configured to allocate a target cloud card to the terminal device in response to a selection operation result sent by the terminal device; the selection operation result is generated by the terminal device in response to a user's selection operation on the cloud card type list .
  • an embodiment of the present application provides a device for acquiring a cloud card, including:
  • a third response module configured to send a split card request to the server in response to the received split card instruction
  • the cloud card type list acquisition module is used to acquire the 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 configured to send the selection operation result to the server in response to the received user selection operation on the cloud card type list; the selection operation result is used to indicate that the server is the terminal device target allocation cloud card;
  • the target cloud card receiving module is used for receiving the target cloud card allocated by the server.
  • an electronic device including:
  • a memory a processor and a computer program stored in the memory and executable on the processor, the computer program implementing the method steps of the first aspect above when executed by the processor.
  • an embodiment of the present application provides a computer-readable storage medium, including: the computer-readable storage medium stores a computer program, and the computer program implements the method described in the first aspect when the computer program is executed by a processor step.
  • an embodiment of the present application provides a computer program product that, when the computer program product runs on an electronic device, causes the electronic device to execute the method steps described in the first aspect above.
  • 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 provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of an information exchange process flow of a cloud card allocation method provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of a terminal device displaying a list of cloud card types according to an embodiment of the present application
  • FIG. 5 is a schematic flowchart of a method for allocating a cloud card provided by another embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for allocating a cloud card provided by another embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for allocating a cloud card provided by another embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for acquiring a cloud card provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a cloud card distribution device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an apparatus for acquiring a cloud card provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the term “if” may be contextually interpreted as “when” or “once” or “in response to determining” or “in response to detecting “.
  • the phrases “if it is determined” or “if the [described condition or event] is detected” may be interpreted, depending on the context, to mean “once it is determined” or “in response to the determination” or “once the [described condition or event] is detected. ]” or “in response to detection of the [described condition or event]”.
  • references in this specification to "one embodiment” or “some embodiments” and the like mean that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the present application.
  • appearances of the phrases “in one embodiment,” “in some embodiments,” “in other embodiments,” “in other embodiments,” etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean “one or more but not all embodiments” unless specifically emphasized otherwise.
  • the terms “including”, “including”, “having” and their variants mean “including but not limited to” unless specifically emphasized otherwise.
  • Cloud card refers to the user identification card whose card information is stored in the cloud.
  • the terminal device can be connected to the mobile communication network through the cloud card.
  • a user sends a card splitting request to a server that allocates cloud cards, and the server allocates a cloud card that can be used in the geographical location to the user according to user information, such as geographic location information.
  • a user uses a cloud card to access a mobile communication network to play games
  • the user has relatively high requirements on the speed and delay of the network. It is usually necessary to allocate a high-speed, low-latency cloud card to the user to meet the user's needs.
  • the purpose of the user using the cloud card is to access the mobile communication network through the cloud card to watch videos. Then, the user's demand consumes a large amount of data and requires a high rate. Usually, a cloud card with large traffic and high speed needs to be allocated to the user to meet the user's needs.
  • the purpose of the user using the cloud card is to use social applications after accessing the mobile communication network through the cloud card, so the user has relatively low requirements on the network traffic and speed.
  • a cloud card with limited traffic and a rate that can basically meet social applications can be allocated to the user.
  • the server cannot perceive user needs, so it cannot allocate cloud cards to users according to user needs. After allocating a cloud card to a user, it is very likely that the performance of the mobile communication network accessed by the cloud card or the package traffic of the cloud card cannot meet the needs of the user, resulting in poor user experience; or the performance of the mobile communication network accessed by the cloud card Or the package traffic of the cloud card far exceeds the user's needs, resulting in a waste of resources.
  • the application type information is obtained to identify the general needs of the user, and a cloud card type list is generated according to the application type information.
  • a cloud card type list is generated according to the application type information.
  • FIG. 1 shows a cloud card service system 100 provided by an embodiment of the present application.
  • the cloud card service system includes 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 cloud card services.
  • the cloud card service includes, but is not limited to, a cloud card distribution service.
  • the cloud card service further includes but is not limited to terminal access service, cloud card data analysis, cloud card billing system, cloud card database, and the like.
  • the cloud card service may be deployed on one or more servers according to specific circumstances, which is not specifically limited in the present application.
  • the terminal device 120 includes but is not limited to mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, notebook computers, ultra-mobile personal computers (ultra- mobile personal computer, UMPC), netbooks, personal digital assistants (personal digital assistants) Assistant, PDA) and other terminal devices, the embodiments of the present application do not impose any restrictions on the specific types of the terminal devices.
  • AR augmented reality
  • VR virtual reality
  • PDA personal digital assistants
  • PDA personal digital assistants
  • the cloud card CloudSIM referred to in this application is a subscriber identity module (Subscriber Identity Module) that distributes cloud card information to a device applying the cloud card through a server.
  • the server sends cloud card information to the terminal device, and the terminal device registers with the operator network according to the cloud card information to implement wireless communication.
  • the cloud card information includes but is not limited to ICCID (Integrate circuit card identity, integrated circuit card identification code), IMSI (International Mobile Subscriber Identity, International Mobile Subscriber Identity) and some information of the operator, etc.
  • the cloud card may be a subscriber identity module (Subscriber Identity Module) placed in a card-carrying device communicatively connected to the server.
  • the server reads the cloud card information through the card carrier device, and sends the cloud card information to the terminal device, and the terminal device registers the carrier network according to the cloud card information to realize wireless communication.
  • the user identification card includes but is not limited to a SIM card (Subscriber Identification Module, user identification card), UIM card (User IdentityModel, user identification module), USIM card (Universal Subscriber Identity Module, global user identification card), eSIM card (Embedded SIM, embedded SIM card), softSIM (soft SIM, soft SIM card), vSIM card (virtual SIM card) SIM, virtual SIM card) etc.
  • the terminal device 120 communicates with the server 110 through wireless communication.
  • FIG. 2 shows a cloud card allocation method provided by an embodiment of the present application, which is applied to the server 110 in the cloud card service system shown in FIG. 1 and can be implemented by software and/or hardware of the server 110 .
  • the method includes steps S110 to S140.
  • FIG. 3 shows a schematic diagram of an information exchange flow of a cloud card allocation method provided by an embodiment of the present application. As shown in FIG. 3 , the specific implementation principle of each step is described below with reference to FIG. 3 .
  • 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.
  • the target application type may be obtained in the following manner: obtaining the application type included in the card splitting request as the target application type; or, according to the historical card splitting request sent by the terminal device containing the Determine the target application type; or, analyze the historical data of the terminal device communicating through the cloud card to determine the target application type.
  • the split-card request sent by the terminal device 120 to the server 110 carries the application type, and the server parses the split-card request to obtain the application type.
  • the user may forget to select the application type in the terminal device.
  • the storage medium communicatively coupled with the server stores the application type included in the card splitting request sent by the terminal device to the server in the past preset time period.
  • the preset time period in the past may be in the past month.
  • the application types included in the card splitting request sent by the terminal in the past month may be different.
  • the one that contains the most application types in the card splitting requests sent by the terminal in the past one month may be used as the target application type.
  • the application type may also be included in the card splitting request sent by the terminal last time as the target application type.
  • the storage medium coupled with the server stores the historical data of the terminal device communicating through the cloud card, such as the traffic data of the terminal device in various time periods in the past, and the terminal device uses the cloud
  • the historical traffic data of the communication with the card is analyzed to determine the target application type.
  • the user uses the terminal device to communicate through the cloud card, and the user's different application requirements will cause the user's traffic data to present different distributions.
  • the traffic distribution of video applications is the distribution of large traffic for a long time
  • the traffic distribution of game applications is the distribution of long-term but alternating high traffic and small traffic
  • the traffic distribution of social applications is the distribution of frequent bursts of small traffic for a long time.
  • the voice is a long-term stable small traffic distribution. Therefore, the historical data of the terminal device's communication through the cloud card can be analyzed to determine the target application type.
  • the analysis of the historical traffic data that the terminal device communicates with through the cloud card includes, but is not limited to, analysis through statistical models, analysis through neural network models, and analysis through big data models.
  • a mapping table between traffic characteristics and application types is established, the user traffic characteristics are determined by analyzing user historical traffic data within a period of time through the above model, and the mapping table between traffic characteristics and application types is queried to determine the sub-card. Request the corresponding application type.
  • the target application type is determined by analyzing the historical data of the terminal device communicating through the cloud card; the historical data is the historical data of the sampling time period in the past preset days; the The sampling time period is the time period corresponding to the sampling time in the past preset days that is the same as the current time. For example, the current time is 10:00 in the morning, and the same sampling time as the current time in the preset days is 10 am every day in the past 7 days. At 1 o'clock, each sampling time is used as the reference time, and a preset time period before, or after, or before and after the sampling time is determined as the sampling time period, for example, 1 hour.
  • the terminal device 120 sends a card splitting request to the server in response to the received card splitting instruction.
  • a program that implements the power-on process or searches for a mobile communication network automatically executes the card splitting instruction.
  • the terminal device prompts the user to perform a card splitting operation through user interaction, and the terminal device obtains a card splitting instruction by receiving the user's card splitting operation.
  • the terminal device sends a card splitting request to the server 110 .
  • the sub-card request includes one of the above application types, that is, the target application type.
  • the response of the server 110 upon receiving the card splitting request includes, but not limited to, acquiring the target application type included in the splitting card request.
  • S120 Determine a cloud card type list according to the target application type.
  • the cloud card type is the category of the cloud card that the operation can provide for the user.
  • Each cloud card type contains multiple category attributes.
  • the category attributes can be divided into service area attributes, package traffic attributes, and network standard attributes. Cloud card types can be classified by category attribute.
  • operator A can provide 4 categories of user identification cards that can be used as cloud cards for cloud card services. If they are classified by category attributes, they include: 5G + local card + limited traffic card; 5G + national card + unlimited card ;4G+local card+unlimited card;4G+national card+unlimited card. It can be seen that the cloud card type is a combination of cloud card category attributes, and each category attribute corresponds to a cloud card type. It should be understood that the division of the category attributes of the cloud card may not be limited to the above examples.
  • each cloud card type provided by each operator includes multiple 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 includes: for the target application type, filtering the cloud card types according to the application type weight, and determining the cloud card type list.
  • the server pre-stores a mapping table of the mapping relationship between application types and cloud card types.
  • the mapping table multiple cloud card types may correspond to the same application type. For the obtained target application type, look up the cloud card type corresponding to the application type in the mapping table, obtain each cloud card type corresponding to the target application type, and form a cloud card type list.
  • the server 110 sends the cloud card list to the terminal device 120 .
  • S140 Allocate a target cloud card to the terminal device in response to a selection operation result sent by the terminal device; the selection operation result is generated by the terminal in response to a user's selection operation on the cloud card type list.
  • the terminal device 120 displays the cloud card type list on the user operation interface.
  • FIG. 4 is a non-limiting example of the terminal device 120 displaying the cloud card type list 121 .
  • the terminal device obtains the result of the user's selection operation on the cloud card type list by receiving the user's selection operation on the cloud card type list.
  • the terminal device sends the selection operation result to the server, and the server allocates the target cloud card to the terminal device according to the selection operation result.
  • the server maintains a cloud card pool, which includes cloud card information of each cloud card, and the server searches the cloud card pool for a cloud card of a cloud card type selected by the user as a target cloud card.
  • the search operation may be to randomly select a cloud card of the cloud card type selected by the user as the target cloud card in the card pool; it may also be to determine a cloud card of the cloud card type selected by the user as the target according to the preset order.
  • a cloud card; a cloud card of a cloud card type selected by a user can also be determined as a target cloud card according to a preset algorithm, and the preset algorithm user prefers a cloud card of the cloud card type selected by the user, and the specific algorithm is not limited.
  • the general needs of the user are identified through the application type information in the card splitting request sent by the terminal, and a cloud card type list is generated according to the application type information. Through the user's selection operation on the cloud card type list, the user's real needs are perceived, so as to achieve the purpose of allocating a cloud card that meets the user's actual needs.
  • each cloud card type provided by each operator includes multiple class attributes; corresponding to the target application type, each cloud card type The category attribute of the card type has the corresponding application type weight.
  • Step S120 the determining the cloud card type list according to the application type, as shown in FIG. 5 , may be replaced with step S120'.
  • the category attributes of the user identification card that can be used for cloud card services can be divided into service area attributes, package traffic attributes and network standard attributes. Divided into different categories, local card, national card, unlimited data, limited data, 2G/3G, 4G, 5G, etc. Each category attribute corresponds to a weight for each application type.
  • the values in Table 1 represent the weights; "Filter” means that the weights are infinitely small, which means that the corresponding card type is not suitable for such applications and will be filtered out; "Remaining traffic is greater than a certain traffic threshold filter condition" identifies the The weight corresponds to the remaining traffic, the larger the remaining traffic of the cloud card; the higher the weight, the smaller the remaining traffic of the cloud card, the lower the weight; the corresponding relationship between the traffic and the weight can be determined according to the service of the cloud card. Operational experience or operational testing to determine.
  • the specific implementation of filtering cloud card types according to the application type weight may be: obtaining the weight of each category attribute of each cloud card type corresponding to the target application, and sorting all categories The weights of the attributes are added to obtain the total weight of the cloud card type. In this way, the total weight of each cloud card type is obtained.
  • the card splitting request further includes at least one of user location information and package information; corresponding to the user location information, each The category attribute of the 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.
  • the server records the traffic information of the cloud card service used by the user through the terminal device for a preset period of time in the past, such as the past week, and generates a user traffic label for the user; corresponding to the user traffic label, each cloud card
  • the category attributes of types have corresponding label weights.
  • the traffic labels of users can be divided into two categories, namely high-traffic users and low-traffic users.
  • Step S120' for the target application type, the cloud card type is screened according to the application type weight, and the cloud card type list is determined, as shown in Figure 6, which can be replaced by step S120''.
  • S120'' for the target application type, filter the cloud card type according to at least one of the user location weight, the package weight and the label weight, and the application type weight, and determine the target application type. See the list of cloud card types.
  • the cloud card type is filtered according to the user location weight, the package weight, and the application type weight as an example for description.
  • the category attributes of the user identification card that can be used for cloud card services can be divided into service area attributes, package traffic attributes and network standard attributes, and the category attributes can be subdivided into different categories. , national card, unlimited traffic, limited traffic, 2G/3G, 4G, 5G, etc. Each category attribute corresponds to a weight for each application type.
  • the values in Table 2 represent the weights; "Filter” means that the weights are infinitely small, which means that the corresponding card type is not suitable for such applications and will be filtered out; "Remaining traffic is greater than a certain traffic threshold filter condition" identifies the The weight corresponds to the remaining traffic, the larger the remaining traffic of the cloud card; the higher the weight, the smaller the remaining traffic of the cloud card, the lower the weight; the corresponding relationship between the traffic and the weight can be determined according to the service of the cloud card. Operational experience or operational testing to determine.
  • the setting of the weight of the category attribute needs to consider a variety of factors.
  • the following is an implementation manner, in conjunction with Table 2, how the location weight, package weight and application type weight are determined. instruction.
  • the card pool of the cloud card is generally a national card, which can only be used in the country where the card belongs.
  • the country information in the location information reported by the device is directly used as a filter condition to filter out the cloud card that cannot be used in the current country.
  • the location in the location information reported by the device For the local card, if the location reported by the terminal does not match the usable location of the local card, the local card cannot be assigned.
  • the location information reported by the device is directly used as a filter condition to filter out cloud cards that cannot be used in the current area.
  • the user package information includes the packages ordered by the end user at the cloud card service provider, and has nothing to do with the cloud card's package at the operator. But the package billing form may be close or similar. There are also differences in the validity period or the size of the traffic or the range of service countries in the user package, but this is not a factor that affects the score card.
  • the factors affecting the user package of the subcard mainly lie in the potential user experience requirements or the user's potential traffic usage behavior. Therefore, the package attributes are mainly divided into directional traffic packages and general traffic packages.
  • the directional traffic package in the package information refers to a specific package that may be strongly related to the application. Such as video package, voice package, game package.
  • Directed traffic packets contain generic traffic.
  • the general traffic packet is the data traffic packet for normal Internet access. This factor is a potential factor.
  • the user chooses to purchase, indicating that the user has the intention to use a certain type of application. But users buy directional traffic packages, and they may not necessarily watch videos or play games. Users have purchased a general data package, and may also choose to play games or watch videos, etc. Therefore, for users who use directional traffic packages, the impact of this factor on the cloud card is mainly reflected in the package traffic of the cloud card and the speed of the cloud card.
  • the card allocation priorities are prioritized according to weight evaluation.
  • For the cloud card service system user experience has a higher priority than cost requirements, so the weight of the limited-traffic card supporting 5G should be 100 higher than the total weight of the unlimited card supporting 4G.
  • a card with both attributes at the same time has a total weight of 300 points and has a higher priority.
  • the service scope of the local card is small, so when the weights of other attributes are the same, the priority of the local card is higher than that of the national card.
  • the package information is general traffic, there is no specific requirement for the card, and the impact of this factor is relatively small. In accordance with the principle of prioritizing the largest remaining traffic. Under this factor, the 4G card has a higher priority than the 5G card, and the unlimited card has a higher priority than the limited-traffic card, but the traffic has a higher priority than the standard.
  • the game application type For the game application type: it requires small delay, fast speed, and large consumption of traffic.
  • support for 5G, unlimited packages, and local cards are bonus items.
  • the weight of bonus points is reflected in the most important 5G card, followed by the unlimited package card, and finally the local card. This is to ensure that the card that supports 5G has a higher priority than the 4G local card that is an unlimited plan. Cards with unlimited plans have higher priority than local cards.
  • the total weight of the card bonus items that support these three attributes is 360, which can ensure that the priority must be the highest.
  • the weight is vertically higher than the weight of other attributes of other cards. Considering the weight of the game application type of the 4G card in the previous general traffic factor, the weight is higher in the horizontal direction than that of other factors in which the score is inconsistent in the standard. If there is only a 4G card for the delay, the local card can be guaranteed to have a higher weight than the general traffic factor 4G national card horizontally. Since game applications are applications that require high stability, try to change cards as little as possible during use. If the system only has cards with limited flow, the process should ensure that the remaining flow of the card selected for the first time is above a certain threshold. Even if it is a 5G card, but the remaining traffic does not reach the threshold, it is better to allocate a 4G unlimited card or a limited traffic card that meets the conditions.
  • the video application type has a caching mechanism, the latency requirement is not high. And the sensitivity to changing cards is relatively small for games and voice. Therefore, there is no requirement for delay.
  • the guaranteed unlimited card has a higher weight than the standard system, and horizontally, the guaranteed unlimited card has a higher weight than the 4G card local card set in the directional traffic.
  • Voice application types require low latency and high speed.
  • Voice services have high requirements on network stability, so for limited-traffic cards, the remaining traffic must be above a certain threshold. Vertically, it is sufficient to ensure that the local limited-traffic card has a higher priority than the unlimited national card. Horizontally, the 5G card is guaranteed to have a higher priority than the 4G unlimited card.
  • the above fixed weights are all high-level weights. There are also low-level weights. Mainly for cloud cards with limited data packages. When the attributes of other categories are the same and the system only has cloud cards with limited traffic, since the remaining traffic of each card is inconsistent, from the perspective of cost, it is necessary to prioritize the allocation of cloud cards with larger remaining traffic. The remaining flow value changes dynamically, and the weight value also needs to change dynamically at this time, so the weight value is based on 1G. The more traffic remaining, the higher the weight and the higher the allocation priority.
  • the priorities of the cloud cards that can be allocated are:
  • the cloud card type to the left of the greater than sign has a higher priority than the cloud card type to the right of the greater than sign.
  • the idle cards after determining the priority of cloud card types, among the idle cards, there are several different operators, and for each operator, one or two cloud cards with the highest total weight are recommended.
  • the card types are presented to the user, so that the user can select the desired operator and cloud card type according to their own subjective wishes. In this way, the perception of user needs is realized, and a cloud card suitable for user needs is allocated to users.
  • the cloud card type is filtered for the target application type according to the user location weight, the package weight and the application type weight as an example. It can be obtained that the cloud card type is filtered according to the user location weight, the package weight, the label weight, and the application type weight, respectively. Or, a technical solution for screening cloud card types according to any combination of the user location weight, the package weight, the label weight, and the application type weight. I won't go into details here.
  • step S140 after assigning a cloud card to the terminal device according to the result of the selection operation, as shown in FIG. 7 , further Step S150 is included.
  • S150 Acquire a test result of the target cloud card by the terminal device; or acquire an evaluation result generated by the terminal device in response to a user's evaluation operation on the target cloud card.
  • each cloud card category includes a historical evaluation attribute; the historical evaluation attribute is obtained by performing statistics on 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; for the target application type, the cloud card type is screened according to the application type weight of the type attribute, and the selected cloud card type is determined.
  • the cloud card type list includes: for the target application type, filtering the cloud card types according to the application type weight and the historical evaluation weight, and determining the cloud card type list.
  • the user may choose to test the currently allocated target cloud card to obtain a test result during the process of using the terminal device.
  • the terminal device uploads the test result to the server.
  • the terminal device also periodically tests the target cloud card to obtain test results, and the terminal device uploads the test results to the server.
  • the test results include but are not limited to: application type, user information, country information, IMSI, cloud card PLMN, registered PLMN, LAC, TAC, CELL, standard, signal strength, peak uplink rate, peak downlink rate, peak delay, Test data such as average uplink rate, average downlink rate, and average delay.
  • the terminal device displays an operation interface for evaluating the use of the target cloud card to the user through the user interaction interface.
  • the terminal device generates an evaluation result in response to the user's evaluation operation on the cloud card, and sends the evaluation result to the server.
  • the server after acquiring the cloud card test performance indicators or user evaluation results reported by multiple terminal devices, the server obtains the position of each operator in the test performance indicators, or the application type of the test performance indicators through a preset statistical model. service level. 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. No specific limitation is made here.
  • the terminal device 120 tests the target cloud card to generate a test result. 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 dissatisfied with the test result, for example, the user can click the button of the dissatisfied test result displayed by the terminal device, and the terminal device displays the cloud card type list sent by the server to the user. Non-limiting, the cloud card type that the user selected last time is no longer displayed. The user re-selects the cloud card type list through the terminal device.
  • the terminal device In response to the received user's re-selection operation on the cloud card type list, the terminal device sends a second selection result of the re-selection operation to the server; the second selection result is used to indicate that the server is the selected server again.
  • the terminal device allocates a target cloud card; and receives the target cloud card allocated by the server. It should be understood that on 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 that the terminal device responds to the user's selection of the cloud card type list. Select Action Generated again.
  • the user's needs can be further sensed. If the user is satisfied with the currently allocated target cloud card, it means that the assigned The target cloud card has matched the user's needs. If the user is not satisfied with the currently allocated target cloud card, the user's real needs are further perceived through the second selection result. So as to achieve the effect of allocating the cloud card that matches the user's needs to the user.
  • FIG. 8 shows a cloud card acquisition method provided by an embodiment of the present application, which is applied to the terminal device 120 in the cloud card service system shown in FIG. 1 and can be implemented by software and/or hardware of the terminal device 120 . As shown in FIG. 2, the method includes steps S210 to S240.
  • S220 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.
  • S230 in response to the received user selection operation on the cloud card type list, send a selection operation result to the server; the selection operation result is used to instruct the server to allocate a cloud card to the terminal device target.
  • S240 Receive the target cloud card allocated by the server.
  • the card splitting request includes a target application type.
  • the application type includes at least one of the following: a game application type, a video application type, a voice application type, and a social application type.
  • the card splitting request includes at least one of user location information and package information.
  • the method further includes: performing a test on the currently distributed cloud card to generate a test result; or, in response to the received user's evaluation operation on the currently distributed cloud card, generating an evaluation result; sending the test result and the evaluation result to the server.
  • FIG. 8 and the embodiment shown in FIG. 2 are based on the same inventive concept, and the various implementations and implementation combinations and their beneficial effects in the above embodiments are also applicable to this embodiment. No longer.
  • FIG. 9 shows a cloud card distribution device provided by an embodiment of the present application, including:
  • the first response module M110 is configured to obtain the target application type in response to a card splitting request sent by the terminal device;
  • the cloud card type list determination module M120 is configured to determine a cloud card type list according to the target application type
  • the cloud card type list sending module M130 is configured to send the cloud card type list to the terminal device
  • the second response module M140 is configured to allocate a target cloud card to the terminal device in response to the selection operation result sent by the terminal device; the selection operation result is generated by the terminal in response to the user's selection operation on the cloud card type list .
  • FIG. 10 shows a cloud card distribution device provided by an embodiment of the present application, including:
  • the third response module M210 is configured to send a card splitting request to the server in response to the received splitting card instruction.
  • the cloud card type list acquisition module M220 is configured to acquire the 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 M230 is configured to send the selection operation result to the server in response to the received user selection operation on the cloud card type list; the selection operation result is used to indicate that the server is the terminal Device target allocation cloud card.
  • 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 to implement the server 110 or the terminal device 120 of the cloud card service system 100 in the embodiment of the present application.
  • the electronic device D10 of this embodiment includes: at least one processor D100 (only one is shown in FIG. 11 ), a processor, a memory D101 , and a processor D101 stored in the memory D101 and available for processing in the at least one processor A computer program D102 running on the processor D100, and the processor D100 implements the steps in any of the foregoing method embodiments when the processor D100 executes the computer program D102.
  • the processor D100 executes the computer program D102, the functions of the modules/units in the foregoing device embodiments are implemented.
  • the electronic device D10 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the electronic device may include, but is not limited to, a processor D100 and a memory D101.
  • FIG. 11 is only an example of the electronic device D10, and does not constitute a limitation to the electronic device D10, and may include more or less components than the one shown, or combine some components, or different components , for example, may also include input and output devices, network access devices, and the like.
  • the so-called processor D100 may be a central processing unit (Central Processing Unit, CPU), and the processor D100 may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuits) , ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory 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, for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital memory card equipped on the electronic device D10 (Secure Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory D101 may also include both an internal storage unit of the electronic device D10 and an external storage device.
  • the memory D101 is used to store an operating system, an application program, a boot loader (Boot Loader), data, and other programs, such as program codes of the computer program.
  • the memory D101 can also be used to temporarily store data that has been output or will be output.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps in the foregoing method embodiments can be implemented.
  • the embodiments of the present application provide a computer program product, when the computer program product runs on an electronic device, the steps in the foregoing method embodiments can be implemented when the electronic device executes.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • all or part of the processes in the methods of the above embodiments can be implemented by a computer program to instruct the relevant hardware.
  • the computer program can be stored in a computer-readable storage medium, and the computer program When executed by the processor, the steps of the above-mentioned various method embodiments may be implemented.
  • the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form, and the like.
  • the computer-readable medium may include at least: any entity or device capable of carrying the computer program code to the photographing device/terminal device, recording medium, computer memory, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), electrical carrier signals, telecommunication signals, and software distribution media.
  • computer readable media may not be electrical carrier signals and telecommunications signals.
  • the disclosed apparatus/network device and method may be implemented in other manners.
  • the apparatus/network device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units. Or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请适用于通信技术领域，提供了一种云卡的分配方法、装置、电子设备及存储介质。所述方法包括：响应于终端设备发送的分卡请求，获取目标应用类型；根据所述目标应用类型确定云卡类型列表；将所述云卡类型列表发送给所述终端设备；响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端设备响应于用户针对所述云卡类型列表的选择操作生成的。应理解，通过响应终端发送的分卡请求，获取应用类型信息以识别用户的大致需求，并根据应用类型信息生成云卡类型列表。通过用户对云卡类型列表的选择操作感知用户的真实需求，从而达到为用户分配符合用户实际需求的云卡的目的。

Description

一种云卡的分配方法、装置、电子设备及存储介质
本申请要求于2020年7月9日在中国专利局提交的、申请号为202010657694.1的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，尤其涉及一种云卡的分配方法、装置、电子设备及存储介质。
 背景技术
云卡CloudSIM是一种通过服务器分配云卡信息到应用云卡的设备的用户身份识别卡（Subscriber Identity Module）。在一种云卡的应用方式中，服务器将云卡信息发送至终端设备，终端设备根据云卡信息注册运营商网络，实现无线通信。所述云卡信息包括但不限于ICCID(Integrate circuit card identity，集成电路卡识别码)、IMSI(International Mobile Subscriber Identity，国际移动用户识别码)以及运营商的一些信息等。
随着使用云卡业务用户的增长，用户使用云卡的行为呈现多样化的趋势，例如通过云卡玩游戏、看视频、进行网络社交活动。可以理解为，用户对云卡的应用的需求也越来越多样化。目前，云端服务器直接为用户分配一个可以使用的云卡，无法针对用户的实际需求为用户分配适合用户需求的云卡。
 技术问题
本申请实施例提供了一种云卡的分配方法、装置、电子设备及存储介质，可以解决以上问题的至少一部分。
 技术解决方案
第一方面，本申请实施例提供了一种云卡的分配方法，包括：
响应于终端设备发送的分卡请求，获取目标应用类型；
根据所述目标应用类型确定云卡类型列表；
将所述云卡类型列表发送给所述终端设备；
响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端设备响应于用户针对所述云卡类型列表的选择操作生成的。
应理解，在本申请提供的实施例中，通过响应终端发送的分卡请求，获取应用类型信息以识别用户的大致需求，并根据应用类型信息生成云卡类型列表。通过用户对云卡类型列表的选择操作感知用户的真实需求，从而达到为用户分配符合用户实际需求的云卡的目的。
第二方面，本申请实施例提供了一种云卡的获取方法，包括：
响应于接收到的分卡指令，向服务器发送分卡请求；
获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的；
响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备目标分配云卡；
接收所述服务器分配的目标云卡。
第三方面，本申请实施例提供了一种云卡的分配装置，包括：
第一响应模块，用于响应于终端设备发送的分卡请求，获取目标应用类型；
云卡类型列表确定模块，用于根据所述目标应用类型确定云卡类型列表；
云卡类型列表发送模块，用于将所述云卡类型列表发送给所述终端设备；
第二响应模块，用于响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端设备响应于用户针对所述云卡类型列表的选择操作生成的。
第四方面，本申请实施例提供了一种云卡的获取装置，包括：
第三响应模块，用于响应于接收到的分卡指令，向服务器发送分卡请求；
云卡类型列表获取模块，用于获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的；
第四响应模块，用于响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备目标分配云卡；
目标云卡接收模块，用于接收所述服务器分配的目标云卡。
第五方面，本申请实施例提供了一种电子设备，包括：
存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述第一方面所述的方法步骤。
第六方面，本申请实施例提供了一种计算机可读存储介质，包括：所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面所述的方法步骤。
第七方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在电子设备上运行时，使得电子设备执行上述第一方面所述的方法步骤。
可以理解的是，上述第二方面至第五方面的有益效果可以参见上述第一方面中的相关描述，在此不再赘述。
 附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例提供的系统示意图；
图2是本申请一实施例提供的云卡的分配方法的流程示意图；
图3是本申请一实施例提供的云卡的分配方法的信息交互流程示意图；
图4是本申请一实施例终端设备展示云卡类型列表的示意图；
图5是本申请另一实施例提供的云卡的分配方法的流程示意图；
图6是本申请另一实施例提供的云卡的分配方法的流程示意图；
图7是本申请另一实施例提供的云卡的分配方法的流程示意图；
图8是本申请一实施例提供的云卡的获取方法的流程示意图；
图9是本申请实施例提供的云卡的分配装置的结构示意图；
图10是本申请实施例提供的云卡的获取装置的结构示意图；
图11是本申请实施例提供的电子设备的结构示意图。
 本发明的实施方式
以下描述中，为了说明而不是为了限定，提出了诸如特定系统结构、技术之类的具体细节，以便透彻理解本申请实施例。然而，本领域的技术人员应当清楚，在没有这些具体细节的其它实施例中也可以实现本申请。在其它情况中，省略对众所周知的系统、装置、电路以及方法的详细说明，以免不必要的细节妨碍本申请的描述。
应当理解，当在本申请说明书和所附权利要求书中使用时，术语“包括”指示所描述特征、整体、步骤、操作、元素和/或组件的存在，但并不排除一个或多个其它特征、整体、步骤、操作、元素、组件和/或其集合的存在或添加。
还应当理解，在本申请说明书和所附权利要求书中使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。
如在本申请说明书和所附权利要求书中所使用的那样，术语“如果”可以依据上下文被解释为“当...时”或“一旦”或“响应于确定”或“响应于检测到”。类似地，短语“如果确定”或“如果检测到[所描述条件或事件]”可以依据上下文被解释为意指“一旦确定”或“响应于确定”或“一旦检测到[所描述条件或事件]”或“响应于检测到[所描述条件或事件]”。
另外，在本申请说明书和所附权利要求书的描述中，术语“第一”、“第二”、“第三”等仅用于区分描述，而不能理解为指示或暗示相对重要性。
在本申请说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
云卡是指卡信息存储在云端的用户身份识别卡。可以通过将云卡的卡信息发送给终端设备，实现终端设备通过该云卡连接移动通信网络。现有的技术方案中，用户向分配云卡的服务器发送分卡请求，服务器根据用户信息，例如地理位置信息，为用户分配一个可在该地理位置使用的云卡。
但是用户使用云卡接入移动通信服务的目的或需求是多种多样的，不同的需求也对应与不同的网络性能需求。
例如，用户使用云卡的目的是接入移动通信网络进行游戏，那么用户对该网络的速率和延时的要求就比较高。通常需要为该用户分配高速率、低延时的云卡才能满足该用户的需求。
又例如，用户使用云卡的目的是通过云卡接入移动通信网络观看视频，那么，用户的需求对流量消耗比较大，对速率要求高。通常需要为该用户分配流量大、速率高的云卡才能满足用户的需求。
再例如，用户使用云卡的目的是通过云卡接入移动通信网络后使用社交类的应用，那么该用户对网络的流量和速率的要求都比较低。通常为该用户分配有限流量的、速率可以基本满足社交应用的云卡即可。
但是目前服务器无法感知用户需求，因此也就无法根据用户的需求为用户分配云卡。在为用户分配云卡后极易出现该云卡接入的移动通信网络性能或者该云卡的套餐流量不能满足用户的需求，造成用户体验变差；或该云卡接入的移动通信网络性能或者该云卡的套餐流量远远超出了用户的需求造成资源的浪费。
因此，如何感知用户需求，并通过感知到的用户需求为用户分配云卡成为需要解决的问题。
在本申请提供的实施例中，通过响应终端设备发送的分卡请求，获取应用类型信息以识别用户的大致需求，并根据应用类型信息生成云卡类型列表。通过用户对云卡类型列表的选择操作感知用户的真实需求，从而达到为用户分配符合用户实际需求的云卡的目的。
图1示出的是本申请实施例提供的一种云卡服务系统100。该云卡服务系统中，包括服务器110、一个或多个终端设备120。
其中，服务器110为提供云卡服务的独立服务器、服务器集群、分布式服务器和服务器。在一些实施例中，所述云卡服务包括但不限于云卡分配服务。在另一些实施例中，所述云卡服务还包括但不限于终端接入服务、云卡数据分析、云卡计费系统、云卡数据库等。在实现本申请实施例时，云卡服务可以结合具体情况在一个或多个服务器上部署，本申请不做具体限定。
其中，终端设备120包括但不限于手机、平板电脑、可穿戴设备、车载设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)等终端设备上，本申请实施例对终端设备的具体类型不作任何限制。
其中，本申请所称云卡CloudSIM是一种通过服务器分配云卡信息到应用云卡的设备的用户身份识别卡（Subscriber Identity Module）。在一种实施方式中，服务器将云卡信息发送至终端设备，终端设备根据云卡信息注册运营商网络，实现无线通信。所述云卡信息包括但不限于ICCID(Integrate circuit card identity，集成电路卡识别码)、IMSI(International Mobile Subscriber Identity，国际移动用户识别码)以及运营商的一些信息等。在一些实施例中，云卡可以是放置在与服务器通信连接的载卡设备中的用户身份识别卡（Subscriber Identity Module）。服务器通过载卡设备读取云卡信息，并将云卡信息发送至终端设备，终端设备根据云卡信息注册运营商网络，实现无线通信。所述用户身份识别卡包括但不限于SIM卡（Subscriber Identification Module，用户身份识别卡）、UIM卡（User IdentityModel，用户识别模块）、USIM卡（Universal Subscriber Identity Module，全球用户识别卡）、eSIM卡（Embedded SIM，嵌入式SIM卡）、softSIM （soft SIM，软SIM卡）、vSIM卡（virtual SIM，虚拟SIM卡）等形式。
其中，所述终端设备120和所述服务器110通过无线通信方式通信。
图2示出了本申请实施例提供的云卡的分配方法，应用于上述图1所示的云卡服务系统中的服务器110，可由所述服务器110的软件和/或硬件实现。如图2所示，该方法包括步骤S110至S140。图3示出的是本申请实施例提供的云卡分配方法的信息交互流程示意图。如图3所示，以下结合图3说明各个步骤的具体实现原理。
S110，响应于终端设备发送的分卡请求，获取目标应用类型。
在本申请的实施例中，终端设备120中云卡的应用类型包括游戏应用类型、视频应用类型、语音应用类型和社交应用类型至少之一。
在本申请的实施例中，可以通过以下方式获取目标应用类型：获取所述分卡请求中包含的应用类型作为所述目标应用类型；或，根据所述终端设备发送的历史分卡请求中包含的应用类型确定所述目标应用类型；或，对所述终端设备通过云卡进行通信的历史数据进行分析，确定所述目标应用类型。
在一种获取目标应用类型的实施方式中，终端设备120向服务器110发送的分卡请求中携带应用类型，服务器解析分卡请求获取应用类型。
在另一种获取目标应用类型的实施方式中，非限定性的场景中，用户可能忘记在终端设备中选择应用类型。与服务器通信耦合的存储介质中存储该终端设备过去的预设时间段内向服务器发送的分卡请求中包含的应用类型。示例性的，过去的预设时间段内可以是过去的一个月内。示例性的，在过去一个月内该终端发送的分卡请求包含的应用类型可能是不同的。可以将过去一个月内该终端历次发送的分卡请求中包含应用类型中最多的一种作为目标应用类型。非限定性的，也可以将该终端上一次发送的分卡请求中包含应用类型中作为目标应用类型。
在另一种获取目标应用类型的实施方式中，与服务器耦合的存储介质存储该终端设备通过云卡进行通信的历史数据，例如该终端设备过去各个时间段的流量数据，对该终端设备通过云卡进行通信的历史流量数据进行分析，确定所述目标应用类型。应理解，用户采用终端设备通过云卡进行通信，用户的不同应用需求会导致用户的流量数据呈现不同的分布。例如，视频应用的流量分布为长时间大流量的分布，游戏应用的流量分布为长时间但是大流量和小流量交替出现的分布，社交应用的流量分布为长时间内频繁突发的小流量分布，语音为长时间稳定的小流量分布。因此，可以对终端设备通过云卡进行通信的历史数据进行分析，确定所述目标应用类型。对该终端设备通过云卡进行通信的历史流量数据进行分析包括但不限于通过统计学模型进行分析、通过神经网络模型进行分析、通过大数据模型进行分析等。在一个非限定的示例中，建立流量特征与应用类型的映射表，通过上述模型分析一段时长内的用户历史流量数据确定用户流量特征，查询流量特征与应用类型的映射表，从而确定该分卡请求对应的应用类型。在一个非限定性的示例中，对终端设备通过云卡进行通信的历史数据进行分析，确定所述目标应用类型；其中所述历史数据为过去预设天数中采样时间段的历史数据；所述采样时间段为过去预设天数中与当前时间相同的采样时间对应的时间段，例如当前时间为早上10点钟，去预设天数中与当前时间相同的采用时间为过去7天的每天早上10点钟，以各个采样时间作为基准时间，确定采样时间之前，或之后，或前后的预设时长作为采样时间段，例如1小时。
在本申请的实施例中，如图3所示，终端设备120响应于接收到的分卡指令，向服务器发送分卡请求。示例性的，终端设备上电时或搜索移动通信网络时，实现上电流程或搜索移动通信网络的程序自动执行分卡指令。示例性的，终端设备通过用户交互提示用户进行分卡操作，终端设备通过接收用户的分卡操作获得分卡指令。终端设备响应于该分卡指令，向服务器110发送分卡请求。该分卡请求中包括上述应用类型之一，即目标应用类型。如图3所示，服务器110接收到该分卡请求作出响应包括但不限于，获取所述分卡请求包含的目标应用类型。
S120，根据所述目标应用类型确定云卡类型列表。
其中，所述云卡类型为运营可以为用户提供的云卡的类别。每个云卡类型包含多个类别属性。在一个非限定性的示例中，类别属性可以分为服务区域属性、套餐流量属性和网络制式属性。云卡类型可以通过类别属性进行分类。
示例性的，A运营商可以提供4种类别的用户身份识别卡可以作为云卡服务的云卡，以类别属性进行分类的话，包括：5G+本地卡+有限流量卡；5G+全国卡+无限量卡；4G+本地卡+无限量卡；4G+全国卡+无限量卡。可以看出，云卡类型是云卡的类别属性的组合，每一种类别属性对应一个云卡类型。应理解，对云卡的类别属性的划分可以不限于以上的示例。
在本申请的实施例的一种实施方式中，各个运营商提供的每个云卡类型包括多个类别属性；对应于所述目标应用类型，每个云卡类型的类别属性具备相应的应用类型权值；所述根据所述应用类型确定云卡类型列表，包括：针对目标应用类型，根据应用类型权值对云卡类型进行筛选，确定所述云卡类型列表。
在本申请的实施例的另一种实施方式中，服务器预存应用类型与云卡类型映射关系的映射表，在该映射表中，可以是多个云卡类型对应同一个应用类型，服务器根据接收到的目标应用类型，在所述映射表中查找与该应用类型对应的云卡类型，得到与目标应用类型对应的各个云卡类型，形成云卡类型列表。
S130，将所述云卡类型列表发送给所述终端设备。
在本申请的实施例中，如图3所示，服务器110将云卡列表发送给终端设备120。
S140，响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端响应于用户针对所述云卡类型列表的选择操作生成的。
在本申请的实施例中，如图3所示，终端设备120获取服务器110发送的云卡类型列表后，在用户操作界面显示该云卡类型列表。图4是终端设备120显示云卡类型列表121的一个非限定性示例。终端设备通过接收用户对该云卡类型列表的选择操作获得用户对云卡类型列表的选择操作结果。终端设备将该选择操作结果发送给服务器，服务器根据选择操作结果为终端设备分配目标云卡。非限定性的，服务器维护云卡卡池，该卡池中包括各个云卡的云卡信息，服务器在云卡卡池中查找一个用户选定的云卡类型的云卡作为目标云卡。应理解，查找操作可以为在卡池中随机选择一个用户选定的云卡类型的云卡作为目标云卡；也可以为根据预设顺序确定一个用户选定的云卡类型的云卡作为目标云卡；还可以为根据预设算法确定一个用户选定的云卡类型的云卡作为目标云卡，预设算法用户优选用户选定的云卡类型的云卡，具体算法不做限定。
可以理解的是，通过终端发送的分卡请求中的应用类型信息识别用户的大致需求，并根据应用类型信息生成云卡类型列表。通过用户对云卡类型列表的选择操作感知用户的真实需求，从而达到为用户分配符合用户实际需求的云卡的目的。
在图2所示的实施例的基础上，在本申请的实施例的一个示例中，各个运营商提供的每个云卡类型包括多个类别属性；对应于所述目标应用类型，每个云卡类型的类别属性具备相应的应用类型权值。步骤S120，所述根据所述应用类型确定云卡类型列表，如图5所示，可以替换为步骤S120’。
S120’，针对目标应用类型，根据应用类型权值对云卡类型进行筛选，确定所述云卡类型列表。
在本申请的实施例中，参考表1，对于运营商A，其可用于云卡服务的用户身份识别卡的类别属性可以分为服务区域属性、套餐流量属性和网络制式属性，类别属性可细分为不同的类别，本地卡、全国卡、无限流量、有限流量、2G/3G、4G、5G等。每一个类别属性对应于每个应用类型一个权值。表1中的数值代表权值；“过滤”代表权值无限小，此权值意味着对应的卡类型不适合此类应用，将被过滤掉；“剩余流量大于一定流量阈值过滤条件”标识该权值和剩余流量的多少对应，云卡的剩余流量越大；该权值约高，云卡的剩余流量越小，该权值约低；流量和权值的对应关系可以根据云卡服务的运营经验或运营测试确定。
在一个非限定性的示例中，根据应用类型权值对云卡类型进行筛选的具体实施方式可以为，获取每个云卡类型的每个类别属性对应于目标应用的权值，并将全部类别属性的权值相加获得该云卡类型的总权值。这样就获得了各个云卡类型的总权值。
Figure dest_path_image001
表1
在图5所示的实施例的基础上，在本申请的实施例的一个示例中，所述分卡请求还包括用户位置信息和套餐信息至少之一；对应于所述用户位置信息，每个云卡类型的类别属性具备相应的位置权值；对应于所述套餐信息，每个云卡类型的类别属性具备相应的套餐权值。在一些实施例中，服务器记录过去的预设时长内，例如过去一周，用户通过终端设备使用云卡服务的流量信息，为用户生成用户流量标签；对应于所述用户流量标签，每个云卡类型的类别属性具备相应的标签权值。在一个非限定示例中，用户的流量标签可以分为两类，分别为大流量用户和小流量用户。
步骤S120’，所述针对目标应用类型，根据应用类型权值对云卡类型进行筛选，确定所述云卡类型列表，如图6所示，可以替换为步骤S120’’。
S120’’，针对所述目标应用类型，根据所述用户位置权值、所述套餐权值和所述标签权值至少之一，和所述应用类型权值对云卡类型进行筛选，确定所述云卡类型列表。
在本申请的实施例中，以针对所述目标应用类型，根据所述用户位置权值、所述套餐权值和所述应用类型权值对云卡类型进行筛选为例进行说明。参考表2，对于运营商B，其可用于云卡服务的用户身份识别卡的类别属性可以分为服务区域属性、套餐流量属性和网络制式属性，类别属性可细分为不同的类别，本地卡、全国卡、无限流量、有限流量、2G/3G、4G、5G等。每一个类别属性对应于每个应用类型一个权值。表2中的数值代表权值；“过滤”代表权值无限小，此权值意味着对应的卡类型不适合此类应用，将被过滤掉；“剩余流量大于一定流量阈值过滤条件”标识该权值和剩余流量的多少对应，云卡的剩余流量越大；该权值约高，云卡的剩余流量越小，该权值约低；流量和权值的对应关系可以根据云卡服务的运营经验或运营测试确定。
Figure dest_path_image002
表2
在本申请的实施例中，类别属性的权值的设置需要考虑多种因素，以下是一种实施方式中，结合表2对位置权值、套餐权值和应用类型权值是如何确定的进行说明。
云卡的卡池中一般都是本国卡，只能在卡归属国家使用，设备上报的位置信息中的国家信息，直接作为过滤条件来过滤不能在当前国家使用的云卡。
设备上报位置信息中的位置，对于本地卡来说，终端上报位置如果和本地卡可使用位置不匹配，本地卡不能分配。设备上报位置信息直接作为过滤条件过滤不能在当前区域使用的云卡。
用户套餐信息包含的是终端用户在云卡服务商处订购的套餐，和云卡在运营商处的套餐没有任何关系。但套餐计费形式可能接近或类似。用户套餐还有有效期或流量大小或服务国家范围等区别，但这不是影响分卡的因素。影响分卡的用户套餐因素主要在于潜在的用户体验要求或与用户潜在的流量使用行为。因此套餐属性主要区分为定向流量包和通用流量包。
套餐信息中的定向流量包指的与应用可能强相关的特定套餐。比如视频包，语音包，游戏包。定向流量包中含有通用流量。通用流量包则就是正常上网的数据流量包。该因素是潜在的因素。用户选择购买，表示用户有使用某类应用的意向。但用户购买的是定向流量包，不一定会看视频，玩游戏。用户购买了通用流量包，也可能选择玩游戏或看视频等。因此对与使用定向流量包的用户来说，分卡考虑这个因素对云卡的影响主要体现在云卡的套餐流量和云卡的速度上。
参考表2，卡分配优先级按照权值评估进行优先级排序。对于云卡服务系统来说，用户体验要比成本要求优先级高，因此权值上要体现出支持5G的有限流量卡要比支持4G的无限量卡总权值高出100。同时具有这两个属性的卡总权值300分优先级要更高。本地卡服务范围小，因此其他属性权值相同时，本地卡优先级要比全国卡优先级高。
套餐信息为通用流量的对于卡没有特定要求，该因素影响比较微小。按照优先分配剩余流量大的原则。该因素下，4G卡比5G卡优先级高，无限量卡比有限流量卡优先级高，但流量相比制式，制式权重较大。
应用类型权值中，对于游戏应用类型：要求时延小、速度快、消耗流量大。游戏类应用类型中，支持5G、是无限量套餐、且是本地卡就是加分项。但加分权重体现在5G卡最重要，其次是无限量套餐卡，最后是本地卡。这是为了保证支持5G的卡优先级要比是无限量套餐的4G本地卡优先级要高。无限量套餐的卡要比本地卡优先级更高。支持这三个属性的卡加分项总权值为360，可保证优先级一定最高。
游戏类型应用5G要保证绝对优先的话，该权值纵向上要比其他卡其他属性权值权重高。考虑到前面通用流量因素中 4G卡的游戏应用类型权值，因此横向上要比其他因素在制式上评分有矛盾的地方权值权重要高。时延上本地卡，如果只有4G卡，该因素本地卡横向上可保证要比通用流量因素4G全国卡权值高。由于游戏类应用属于对稳定性要求很高的应用，因此使用过程中尽量要少换卡。如果系统只有有限流量的卡那么流程上要保证第一次挑选的卡的剩余流量在一定阈值之上。即使是5G卡，但剩余流量达不到阈值，宁可分配4G的无限量卡或满足条件的有限流量卡。
由于视频应用类型具有缓存机制，因此时延上要求不高。且对换卡的敏感度相当游戏和语音要小。因此时延上没有要求。纵向上保证无限量比制式权重高，横向上保证无限量卡比定向流量中设置的4G卡本地卡权重高。
语音应用类型要求时延小，速度快。语音业务对网络稳定性要求高，因此对有限流量卡来说，剩余流量要在一定阈值之上。纵向上保证本地的有限流量卡优先级高于无限量的全国卡即可。横向上，保证5G的卡优先级高于4G的无限量卡。
对于社交应用类型，保证用户正常上网即可。社交对云卡使用要求稍低，只要保证数据服务正常稳定即可。此业务场景下，要求尽量分配一般卡资源，保证优质卡资源预留给其他用户使用。因此纵向上保证4G卡优先分配。横向上和用户套餐中的流量因素对比，保证4G卡优先级高于5G的无限量本地卡。
需要注意的是，对于只支持2G/3G的云卡来说，这类卡基本上使用体验都是不足的，因此在这类卡所有使用业务场景来说都是负分，即相比其他类别的卡来说，优先级都是最低的。因此该属性权值负分在纵向上要比所有因素纵向上的加分项量级要高。
还需要注意的是，上述固定权值都是高级别权重。还有低级别权重。主要是针对有限流量套餐的云卡。当其他类别属性一致，系统只有有限流量的云卡时，由于每张卡的剩余流量不一致，因此从成本角度出发，需要优先分配剩余流量较大的云卡。剩余流量值动态变化，此时权重权值也需要动态变化，所以权值按照1G为单位，剩余多少G，取整就取值多少。剩余流量越多，权值就越高，分配优先级越高。
还需要注意的是，系统分卡时，高优先级权重已经能区分优先级的情况下，忽略低优先级权重权值。在高优先级权重权值相等的情况下，才通过低优先级权重权值进行分配。
以下是在本申请的一种实施方式的非限定性示例，对不同的云卡类型参照表2获得该云卡类型的权值的实现方式。本示例中，某个用户在中国广东深圳开机，该用户订购的是通用流量包，该用户选择的应用类型为视频应用类型。对照表2，获得各个云卡类别的总权值如表3所示。
云卡类别 （制式属性的套餐权值+制式属性的应用类型权值） +（服务区域属性的套餐权值+服务器区域属性的应用类型权值） +（套餐流量属性的套餐权值+套餐流量属性的应用类型权值） =总权值
5G+本地卡+无限流量卡 （0+100）+（10+10）+（10+200）=330
5G+全国卡+无限流量卡 （0+100）+（0+0）+（10+200）=310
5G+本地卡+有限流量卡 （0+100）+（10+10）+（0+0）=120
5G+全国卡+有限流量卡 （0+100）+（0+0）+（0+0）=100
4G+本地卡+无限流量卡 （0+0）+（10+10）+（10+200）=230
4G+全国卡+无限流量卡 （0+0）+（0+0）+（10+200）=210
4G+本地卡+有限流量卡 （0+0）+（10+10）+（0+0）=20
4G+全国卡+有限流量卡 （0+0）+（0+0）+（0+0）=0
2G/3G卡 <0
表3
从上述权值中可以看出, 可分配云卡优先级为：
5G，无限量卡 >4G，无限量卡 >5G，有限流量 >4G，有限流量卡
大于号左边的云卡类型的优先级高于大于号右边的云卡类型优先级。
在一个非限定性的示例中，针在确定云卡类型的优先级后，在空闲卡中，有几个不同的运营商，就每个运营商推荐一到两个总权值靠前的云卡类别呈现给用户，以便用户根据自己的主观愿望选择想要的运营商和云卡类别。从而实现了对用户需求的感知，为用户分配适合用户需求的云卡。
应理解，参考上述以针对所述目标应用类型，根据所述用户位置权值、所述套餐权值和所述应用类型权值对云卡类型进行筛选为例进行的说明。可以得到分别根据所述用户位置权值、所述套餐权值和所述标签权值，和所述应用类型权值对云卡类型进行筛选。或者，根据所述用户位置权值、所述套餐权值和所述标签权值的任意组合和所述应用类型权值对云卡类型进行筛选的技术方案。这里不再赘述。
在图6所示的实施例的基础上，在本申请的实施例的一个示例中，在步骤S140，根据所述选择操作结果为所述终端设备分配云卡后，如图7所示，还包括步骤S150。
S150，获取所述终端设备对所述目标云卡的测试结果；或获取所述终端设备响应于用户针对所述目标云卡的评价操作生成的评价结果。
在此实施方式基础上，每个云卡类别包括历史评价属性；所述历史评价属性是通过对预设时间段内，对云卡类别的所述测试结果或所述评价结果进行统计获得的；对应于所述目标应用类型，每个云卡类型的历史评价属性具备一个相应的历史评价权值；所述针对目标应用类型，根据类型属性的应用类型权值对云卡类型进行筛选，确定所述云卡类型列表，包括：针对目标应用类型，根据应用类型权值和历史评价权值对云卡类型进行筛选，确定所述云卡类型列表。
在服务器为终端设备分配目标云卡后，在用户使用终端设备的过程中，用户可选择对当前分配的目标云卡进行测试获得测试结果。终端设备将该测试结果上传到服务器。非限定性的，终端设备也会周期的对目标云卡进行测试获得测试结果，终端设备将该测试结果上传到服务器。所述测试结果包括但不限于：应用类型、用户信息、国家信息、IMSI、云卡PLMN、注册PLMN、LAC、TAC、 CELL、制式、信号强度、峰值上行速率、峰值下行速率、峰值时延、平均上行速率、平均下行速率、平均时延等测试数据。
非限定性的，终端设备通过用户交互界面向用户展示对目标云卡的使用评价操作界面。终端设备响应于用户对所述云卡的评价操作，生成评价结果，将所述评价结果发送到所述服务器。
在一些实施例中，服务器在获取多个终端设备上报的云卡测试性能指标或者用户评价结果后，通过预设统计模型获得各个运营商在测试性能指标的位置，或者测试性能指标的应用类型的服务等级。应理解，可以采用任意的统计模型，例如大数据统计模型，人工智能统计模型或数值分析统计模型。这里不做具体的限定。
可以理解的是，通过历史评价属性对云卡类型进行筛选，可以获得根据用户使用体验给用户分配云卡，使得分配的目标云卡更加符合用户的应用类型，更加适应用户的需求。
在本申请的一些实施方式中，在终端设备120接收到服务器110分配的目标云卡后，终端设备对该目标云卡进行测试生成测试结果。如果用户对该测试结果满意，则用户继续使用该云卡进行通信。但是有些情形下，如果用户对该测试结果不满意，示例性的，用户可以通过点选终端设备展示的测试结果不满意的按钮，终端设备向用户展示服务器发送的云卡类型列表。非限定性的，不再展示用户上一次选择过的云卡类型。用户通过终端设备重新进行对云卡类型列表的选择操作。终端设备响应于接收到的用户针对所述云卡类型列表的再次选择操作，将再次选择操作的第二选择结果发送给所述服务器；所述第二选择结果用于指示所述服务器再次为所述终端设备分配目标云卡；接收所述服务器分配的所述目标云卡。应理解，在服务器端，服务器响应于终端设备发送的第二选择结果，重新为所述终端设备分配目标云卡；所述第二选择结果是终端设备响应于用户针对所述云卡类型列表的再次选择操作生成的。
可以理解的是，通过对目标云卡进行测试并获取用户对该目标云卡是否满意的操作结果，可以进一步的感知用户的需求，如果用户对当前分配的目标云卡满意的话，则说明分配的目标云卡已经匹配了用户的需求。如果用户对当前分配的目标云卡不满意，则通过第二选择结果进一步感知用户的真实需求。从而达到为用户分配匹配用户需求的云卡的效果。
图8示出了本申请实施例提供的云卡的获取方法，应用于上述图1所示的云卡服务系统中的终端设备120，可由所述终端设备120的软件和/或硬件实现。如图2所示，该方法包括步骤S210至S240。
S210，响应于接收到的分卡指令，向服务器发送分卡请求。
S220，获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的。
S230，响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备目标分配云卡。
S240，接收所述服务器分配的目标云卡。
可选的，所述分卡请求包括目标应用类型。
可选的，应用类型包括以下至少之一：游戏应用类型、视频应用类型、语音应用类型和社交应用类型。
可选的，所述分卡请求包括用户位置信息和套餐信息至少之一。
可选的，在所述接收所述服务器分配的云卡后，还包括：对当前分配的云卡进行测试生成测试结果；或，响应于接收到的用户对当前分配的云卡的评价操作，生成评价结果；将所述测试结果和所述评价结果发送给所述服务器。
可以理解的是，图8示出的实施例与图2示出的实施例基于同一发明构思，以上实施例中的各种实施方式和实施方式组合及其有益效果同样适用于本实施例，这里不再赘述。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
对应于上述图2所示的云卡的分配方法，图9示出的是本申请实施例提供的一种云卡的分配装置，包括：
第一响应模块M110，用于响应于终端设备发送的分卡请求，获取目标应用类型；
云卡类型列表确定模块M120，用于根据所述目标应用类型确定云卡类型列表；
云卡类型列表发送模块M130，用于将所述云卡类型列表发送给所述终端设备；
第二响应模块M140，用于响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端响应于用户针对所述云卡类型列表的选择操作生成的。
可以理解的是，以上实施例中的各种实施方式和实施方式组合及其有益效果同样适用于本实施例，这里不再赘述。
对应于上述图8所示的云卡的分配方法，图10示出的是本申请实施例提供的一种云卡的分配装置，包括：
第三响应模块M210，用于响应于接收到的分卡指令，向服务器发送分卡请求。
云卡类型列表获取模块M220，用于获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的。
第四响应模块M230，用于响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备目标分配云卡。
目标云卡接收模块M240，用于接收所述服务器分配的目标云卡。
可以理解的是，以上实施例中的各种实施方式和实施方式组合及其有益效果同样适用于本实施例，这里不再赘述。
图11为本申请一实施例提供的电子设备的结构示意图。该电子设备用于实现本申请实施例中云卡服务系统100的服务器110或终端设备120。如图11所示，该实施例的电子设备D10包括：至少一个处理器D100（图11中仅示出一个）处理器、存储器D101以及存储在所述存储器D101中并可在所述至少一个处理器D100上运行的计算机程序D102，所述处理器D100执行所述计算机程序D102时实现上述任意各个方法实施例中的步骤。或者，所述处理器D100执行所述计算机程序D102时实现上述各装置实施例中各模块/单元的功能。
所述电子设备D10可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。该电子设备可包括，但不仅限于，处理器D100、存储器D101。本领域技术人员可以理解，图11仅仅是电子设备D10的举例，并不构成对电子设备D10的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如还可以包括输入输出设备、网络接入设备等。
所称处理器D100可以是中央处理单元(Central Processing Unit，CPU)，该处理器D100还可以是其他通用处理器、数字信号处理器 (Digital Signal Processor，DSP)、专用集成电路 (Application Specific Integrated Circuit，ASIC)、现成可编程门阵列 (Field-Programmable Gate Array，FPGA) 或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器D101在一些实施例中可以是所述电子设备D10的内部存储单元，例如电子设备D10的硬盘或内存。所述存储器D101在另一些实施例中也可以是所述电子设备D10的外部存储设备，例如所述电子设备D10上配备的插接式硬盘，智能存储卡（Smart Media Card, SMC），安全数字（Secure Digital, SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器D101还可以既包括所述电子设备D10的内部存储单元也包括外部存储设备。所述存储器D101用于存储操作系统、应用程序、引导装载程序(BootLoader)、数据以及其他程序等，例如所述计算机程序的程序代码等。所述存储器D101还可以用于暂时地存储已经输出或者将要输出的数据。
需要说明的是，上述装置/单元之间的信息交互、执行过程等内容，由于与本申请方法实施例基于同一构思，其具体功能及带来的技术效果，具体可参见方法实施例部分，此处不再赘述。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。另外，各功能单元、模块的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现可实现上述各个方法实施例中的步骤。
本申请实施例提供了一种计算机程序产品，当计算机程序产品在电子设备上运行时，使得电子设备执行时实现可实现上述各个方法实施例中的步骤。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一计算机可读存储介质中，该计算机程序在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机程序包括计算机程序代码，所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质至少可以包括：能够将计算机程序代码携带到拍照装置/终端设备的任何实体或装置、记录介质、计算机存储器、只读存储器（Read-Only Memory，ROM）、随机存取存储器（Random Access Memory，RAM）、电载波信号、电信信号以及软件分发介质。例如U盘、移动硬盘、磁碟或者光盘等。在某些司法管辖区，根据立法和专利实践，计算机可读介质不可以是电载波信号和电信信号。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的实施例中，应该理解到，所揭露的装置/网络设备和方法，可以通过其它的方式实现。例如，以上所描述的装置/网络设备实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通讯连接可以是通过一些接口，装置或单元的间接耦合或通讯连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (18)

  1. 一种云卡的分配方法，其特征在于，包括：
    响应于终端设备发送的分卡请求，获取目标应用类型；
    根据所述目标应用类型确定云卡类型列表；
    将所述云卡类型列表发送给所述终端设备；
    响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端设备响应于用户针对所述云卡类型列表的选择操作生成的。
  2. 如权利要求1所述的分配方法，其特征在于，各个运营商提供的每个云卡类型包括多个类别属性；对应于所述目标应用类型，每个云卡类型的类别属性具备相应的应用类型权值；
    所述根据所述目标应用类型确定云卡类型列表，包括：
    针对所述目标应用类型，根据所述应用类型权值对云卡类型进行筛选，确定所述云卡类型列表。
  3. 如权利要求2所述的分配方法，其特征在于，所述分卡请求还包括用户位置信息、套餐信息至少之一；对应于所述用户位置信息，每个云卡类型的类别属性具备相应的位置权值；对应于所述套餐信息，每个云卡类型的类别属性具备相应的套餐权值；每个终端设备对应一个用户流量标签；对应于所述用户流量标签，每个云卡类型的类别属性具备相应的标签权值；
    所述针对所述目标应用类型，根据所述应用类型权值对云卡类型进行筛选，确定所述云卡类型列表，包括：
    针对所述目标应用类型，根据所述用户位置权值、所述套餐权值和所述标签权值至少之一，和所述应用类型权值对云卡类型进行筛选，确定所述云卡类型列表。
  4. 如权利要求3所述的分配方法，其特征在于，在为所述终端设备分配目标云卡后，还包括：
    获取所述终端设备对所述目标云卡的测试结果；或
    获取所述终端设备响应于用户针对所述目标云卡的评价操作生成的评价结果。
  5. 如权利要求4所述的分配方法，其特征在于，每个云卡类别包括历史评价属性；所述历史评价属性是通过对预设时间段内，对云卡类别的所述测试结果或所述评价结果进行统计获得的；对应于所述目标应用类型，每个云卡类型的历史评价属性具备一个相应的历史评价权值；
    所述针对所述目标应用类型，根据所述应用类型权值对云卡类型进行筛选，确定所述云卡类型列表，包括：
    针对目标应用类型，根据应用类型权值和历史评价权值对云卡类型进行筛选，确定所述云卡类型列表。
  6. 如权利要求1至5任一项所述的分配方法，其特征在于，所述目标应用类型包括以下至少之一：
    游戏应用类型、视频应用类型、语音应用类型和社交应用类型。
  7. 如权利要求1所述的分配方法，其特征在于，获取目标应用类型，包括：
    获取所述分卡请求中包含的应用类型作为所述目标应用类型；或，
    根据所述终端设备发送的历史分卡请求中包含的应用类型确定所述目标应用类型；或，
    对所述终端设备通过云卡进行通信的历史数据进行分析，确定所述目标应用类型。
  8. 如权利要求1所述的分配方法，其特征在于，还包括：
    响应于终端设备发送的第二选择结果，重新为所述终端设备分配目标云卡；所述第二选择结果是终端设备响应于用户针对所述云卡类型列表的再次选择操作生成的。
  9. 一种云卡的获取方法，其特征在于，应用于终端设备，所述方法包括：
    响应于接收到的分卡指令，向服务器发送分卡请求；
    获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的；
    响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备分配目标云卡；
    接收所述服务器分配的所述目标云卡。
  10. 如权利要求9所述的获取方法，其特征在于，所述分卡请求包括应用类型。
  11. 如权利要求10所述的获取方法，其特征在于，所述应用类型包括以下至少之一：
    游戏应用类型、视频应用类型、语音应用类型和社交应用类型。
  12. 如权利要求10所述的获取方法，其特征在于，所述分卡请求还包括用户位置信息和套餐信息至少之一。
  13. 如权利要求9至12任一项所述的获取方法，其特征在于，在所述接收所述服务器分配的所述目标云卡后，还包括：
    对当前分配的云卡进行测试生成测试结果；或，
    响应于接收到的用户对当前分配的云卡的评价操作，生成评价结果；
    将所述测试结果和所述评价结果发送给所述服务器。
  14. 如权利要求13所述的获取方法，其特征在于，在所述生成测试结果后，还包括：
    响应于接收到的用户针对所述云卡类型列表的再次选择操作，将再次选择操作的第二选择结果发送给所述服务器；所述第二选择结果用于指示所述服务器再次为所述终端设备分配目标云卡；
    接收所述服务器分配的所述目标云卡。
  15. 一种云卡的分配装置，其特征在于，包括：
    第一响应模块，用于响应于终端设备发送的分卡请求，获取目标应用类型；
    云卡类型列表确定模块，用于根据所述目标应用类型确定云卡类型列表；
    云卡类型列表发送模块，用于将所述云卡类型列表发送给所述终端设备；
    第二响应模块，用于响应于终端设备发送的选择操作结果，为所述终端设备分配目标云卡；所述选择操作结果是终端设备响应于用户针对所述云卡类型列表的选择操作生成的。
  16. 一种云卡的获取装置，其特征在于，包括：
    第三响应模块，用于响应于接收到的分卡指令，向服务器发送分卡请求；
    云卡类型列表获取模块，用于获取所述服务器发送的云卡类型列表；所述云卡类型列表是所述服务器根据目标应用类型确定的；
    第四响应模块，用于响应于接收到的用户针对所述云卡类型列表的选择操作，将选择操作结果发送给所述服务器；所述选择操作结果用于指示所述服务器为所述终端设备分配目标云卡；
    目标云卡接收模块，用于接收所述服务器分配的所述目标云卡。
  17. 一种电子设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，其特征在于，所述处理器执行所述计算机程序时实现如权利要求1至8任一项所述的分配方法，或权利要求9至14任一项所述的获取方法。
  18. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现如权利要求1至8任一项所述的分配方法，或权利要求9至14任一项所述的获取方法。
PCT/CN2021/105259 2020-07-09 2021-07-08 一种云卡的分配方法、装置、电子设备及存储介质 WO2022007902A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010657694.1 2020-07-09
CN202010657694.1A CN113055877B (zh) 2020-07-09 2020-07-09 一种云卡的分配方法、装置、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2022007902A1 true WO2022007902A1 (zh) 2022-01-13

Family

ID=76507604

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/105259 WO2022007902A1 (zh) 2020-07-09 2021-07-08 一种云卡的分配方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN113055877B (zh)
WO (1) WO2022007902A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113055877B (zh) * 2020-07-09 2023-03-31 深圳优克云联科技有限公司 一种云卡的分配方法、装置、电子设备及存储介质
CN114245366B (zh) * 2021-11-25 2023-10-27 深圳市优克联新技术有限公司 一种统一云卡发卡方法、混合云卡服务系统以及系统设备
CN117035292A (zh) * 2023-07-28 2023-11-10 广州盈风网络科技有限公司 一种云产品分配方法、装置、设备及存储介质
CN117641517A (zh) * 2024-01-26 2024-03-01 深圳优克云联科技有限公司 多功能sim卡及其分配方法、分卡系统和电子设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017185382A1 (zh) * 2016-04-29 2017-11-02 华为技术有限公司 虚拟sim卡分发、接入网络的方法及相关设备
CN107846678A (zh) * 2016-09-19 2018-03-27 中兴通讯股份有限公司 数据流量的使用控制方法及装置
CN108668333A (zh) * 2018-07-09 2018-10-16 深圳市优克联新技术有限公司 一种移动网络的切换方法及系统
CN109275135A (zh) * 2018-09-27 2019-01-25 惠州Tcl移动通信有限公司 虚拟sim卡资源的选取方法、存储介质以及移动终端
CN109587747A (zh) * 2018-10-26 2019-04-05 努比亚技术有限公司 Sim卡切换控制方法、终端及计算机存储介质
CN113055877A (zh) * 2020-07-09 2021-06-29 深圳优克云联科技有限公司 一种云卡的分配方法、装置、电子设备及存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104902463B (zh) * 2015-05-22 2020-01-07 努比亚技术有限公司 移动终端及其虚拟卡终端的多卡管理方法和服务器
CN105554728A (zh) * 2015-12-10 2016-05-04 深圳市迪讯飞科技有限公司 一种云端sim卡池系统
CN105682077B (zh) * 2015-12-31 2019-08-02 宇龙计算机通信科技(深圳)有限公司 一种虚拟sim卡切换方法及装置
CN108769978A (zh) * 2018-04-13 2018-11-06 深圳市优克联新技术有限公司 Sim卡管理服务器、绑定装置、管理方法、绑定方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017185382A1 (zh) * 2016-04-29 2017-11-02 华为技术有限公司 虚拟sim卡分发、接入网络的方法及相关设备
CN107846678A (zh) * 2016-09-19 2018-03-27 中兴通讯股份有限公司 数据流量的使用控制方法及装置
CN108668333A (zh) * 2018-07-09 2018-10-16 深圳市优克联新技术有限公司 一种移动网络的切换方法及系统
CN109275135A (zh) * 2018-09-27 2019-01-25 惠州Tcl移动通信有限公司 虚拟sim卡资源的选取方法、存储介质以及移动终端
CN109587747A (zh) * 2018-10-26 2019-04-05 努比亚技术有限公司 Sim卡切换控制方法、终端及计算机存储介质
CN113055877A (zh) * 2020-07-09 2021-06-29 深圳优克云联科技有限公司 一种云卡的分配方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN113055877A (zh) 2021-06-29
CN113055877B (zh) 2023-03-31

Similar Documents

Publication Publication Date Title
WO2022007902A1 (zh) 一种云卡的分配方法、装置、电子设备及存储介质
US20220141110A1 (en) Managing data transfers over network connections based on priority and a data usage plan
CN107679718B (zh) 名单分配方法、设备以及计算机可读存储介质
US10936371B2 (en) Method for resource allocation and related products
WO2018049859A1 (zh) 数据流量的使用控制方法及装置
CN107832142B (zh) 应用程序的资源配置方法及设备
CN110740088B (zh) 推荐、添加社交资源的方法、装置、终端及介质
US11102145B2 (en) Resource sharing method, computer device, and storage medium
CN111131841A (zh) 直播间接入方法、装置、电子设备及存储介质
CN111490890A (zh) 基于微服务架构的分级注册方法、装置、存储介质及设备
WO2022007901A1 (zh) 一种云卡的分配方法、装置、电子设备及存储介质
CN114157710A (zh) 通信策略配置方法、装置、存储介质及设备
CN111930505B (zh) 大数据平台的数据资源管理方法及系统、服务器及介质
CN114070755B (zh) 虚拟机网络流量确定方法、装置、电子设备和存储介质
CN108616870B (zh) 识别被优先定制的终端的方法和装置
CN116204302A (zh) 一种基于k8s安卓云手机的设备调度方法
CN108881591B (zh) 一种多平台信息推荐方法、装置及存储介质
US20170094542A1 (en) Mobile terminal flow identification method and apparatus
CN111079023A (zh) 目标帐户的识别方法、装置、终端及存储介质
CN115119192B (zh) 网络接入方法和装置
CN113518459B (zh) 资源调度处理方法、装置及电子设备
CN111262871A (zh) 一种数据处理方法及装置、存储介质
WO2014173129A1 (en) Mobile terminal flow identification method and apparatus
CN113590913B (zh) 数据资源的显示方法及装置、存储介质及电子装置
CN116582895A (zh) 一种确定宽带的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21837697

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21837697

Country of ref document: EP

Kind code of ref document: A1