CN116709267A

CN116709267A - Profile distribution method and device, storage medium, terminal and server

Info

Publication number: CN116709267A
Application number: CN202310628998.9A
Authority: CN
Inventors: 王宗良
Original assignee: RDA Microelectronics Beijing Co Ltd
Current assignee: RDA Microelectronics Beijing Co Ltd
Priority date: 2023-05-30
Filing date: 2023-05-30
Publication date: 2023-09-05

Abstract

A profile distribution method and device, a storage medium, a terminal and a server, wherein the method comprises the following steps: transmitting a profile request message, wherein the profile request message is used for requesting a target profile for a target service; and downloading the target profile. The application provides a dynamic profile allocation method which is beneficial to improving the utilization rate of profiles.

Description

Profile distribution method and device, storage medium, terminal and server

Technical Field

The present application relates to the field of communications technologies, and in particular, to a profile allocation method and apparatus, a storage medium, a terminal, and a server.

Background

Currently, related art embedded subscriber identity modules (embeddedsubscriber identification module, esims) are receiving widespread attention. esims are devices that embed traditional SIM cards directly onto the device chip, rather than being added as a separate removable component, without the user having to insert an actual SIM card.

In addition, unlike traditional SIMs, esims are programmable, which enable the downloading, installation, etc. of carrier profiles, commonly referred to as "profiles," through Over-the-Air Technology (OTA). In the prior art, the profile is downloaded to the eSIM and is fixedly used, and if the frequency of data transmission is low, the profile is in an idle state for a long time, so that the problem of resource waste is easily caused.

Disclosure of Invention

The technical problem to be solved by the application is how to improve the utilization rate of profile.

In a first aspect, an embodiment of the present application provides a profile allocation method, where the method includes: transmitting a profile request message, wherein the profile request message is used for requesting a target profile for the target service; and downloading the target profile.

Optionally, the sending the profile request message includes: and responding to the requirement of the target service, and sending the profile request message.

Optionally, the profile request message includes a service related parameter, where the service related parameter is used to describe a requirement of the target service.

Optionally, the service related parameter includes at least one of: service type, service estimation duration, service estimation traffic.

Optionally, the profile request message further includes: and the position information of the terminal.

Optionally, the method further comprises: and deactivating the target profile in response to the end of use of the target profile.

Optionally, the method further comprises: and reporting the completion notification message.

Optionally, the method further comprises: and reporting the service condition of the target profile.

Optionally, the method further comprises: and judging whether the target service is finished or not in response to the use condition of the target profile meeting the recycling condition or in response to the receiving of a recycling instruction, and negotiating to continue to use the target profile if the judging result is negative.

Optionally, the negotiating to continue using the target profile includes: a deferred request message is sent, and the deferred request message is used for requesting to continue to use the target profile; and receiving a response of the deferred request message.

Optionally, the method further comprises: and deactivating the target profile in response to the use condition of the target profile meeting a recycling condition or in response to the receipt of a recycling instruction.

In a second aspect, an embodiment of the present application provides a profile allocation method, where the method includes: receiving a profile request message, wherein the profile request message is used for requesting a target profile for a target service; and issuing the target profile.

Optionally, before the target profile is issued, the method includes: and responding to the profile request message, and selecting the target profile from idle profiles.

Optionally, selecting the target profile from the idle profiles includes: correcting the service related parameters according to profile request preference of the terminal; and selecting the target profile from the idle profiles according to the corrected service related parameters.

Optionally, selecting the target profile from the idle profiles includes: and selecting the target profile according to the idle duration of the idle profile and/or the rate of the idle profile.

Optionally, the method further comprises: receiving a completion notification message; and responding to the completion notification message, and recovering the target profile.

Optionally, the method further comprises: and receiving the use condition of the target profile.

Optionally, a reclamation instruction is sent.

Optionally, the method further comprises: receiving a deferred request message, wherein the deferred request message is used for requesting to continue to use the target profile; and sending a response of the deferred request message.

In a third aspect, an embodiment of the present application provides a profile allocation apparatus, where the apparatus includes: the communication module is used for sending a profile request message, wherein the profile request message is used for requesting a target profile for the target service; the communication module is also used for downloading the target profile.

In a fourth aspect, an embodiment of the present application provides a profile allocation apparatus, where the apparatus includes: the communication module is used for receiving a profile request message, wherein the profile request message is used for requesting a target profile for a target service; the communication module is also used for issuing the target profile.

In a fifth aspect, an embodiment of the present application provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, causes the profile allocation method provided in any one of the above aspects to be performed.

In a sixth aspect, an embodiment of the present application provides a terminal, including a memory and a processor, where the memory stores a computer program capable of running on the processor, and the processor executes the steps of the profile allocation method provided in the first aspect when running the computer program.

In a seventh aspect, an embodiment of the present application provides a server, including a memory and a processor, where the memory stores a computer program that can be run on the processor, and the processor executes the steps of the profile allocation method provided in the second aspect when the processor runs the computer program.

In an eighth aspect, an embodiment of the present application provides a chip (or a communication device) on which a computer program is stored, where the computer program, when executed by the chip, causes the profile allocation method provided in any one of the above aspects to be performed.

In a ninth aspect, an embodiment of the present application provides a chip module, where a computer program is stored on the chip module, and when the computer program is executed by the chip module, the profile allocation method provided in any one of the above aspects is executed.

In a tenth aspect, an embodiment of the present application provides a computer program product, which comprises a computer program, which when run on a computer causes the computer to perform the profile allocation method provided in any one of the above aspects.

In an eleventh aspect, embodiments of the present application provide a system comprising means for performing the method provided in the first aspect and means for performing the method provided in the second aspect.

Compared with the prior art, the technical scheme of the embodiment of the application has the following beneficial effects:

in the scheme of the embodiment of the application, the terminal sends a profile request message to request the server for the target profile for the target service, and the server responds to the profile request message to select the target profile from the idle profiles and send the target profile to the terminal. In the scheme of the embodiment of the application, the terminal allocates the profile based on the service request server, and the server allocates the profile to the terminal based on the service requirement of the terminal. That is, when there is a service at the terminal side, the profile is allocated to the terminal, and when there is no service at the terminal side, the profile is not allocated to the terminal, so that the profile can be allocated to the terminal with the service requirement, and the situation that the profile is not used after being allocated is avoided, thereby being beneficial to improving the utilization rate of the profile.

Further, in the solution of the embodiment of the present application, the profile request message includes a service related parameter for describing a requirement of the target service, and the server selects the target profile according to the service related parameter. By adopting the scheme, a more appropriate target profile can be selected for the target service, and the utilization rate of the profile is further improved.

Further, in the scheme of the embodiment of the application, the server corrects the service related parameters reported by the terminal according to the profile request preference of the terminal, and selects the target profile according to the corrected service related parameters. By adopting the scheme, the selected target profile and the target service can be more matched.

Further, in the solution of the embodiment of the present application, the profile request message further includes location information of the terminal, and the server selects the target profile according to the location information of the terminal. By adopting the scheme, the situation that the target profile terminal selected by the server cannot be used can be avoided, and the reliability of the scheme is improved.

Further, in the scheme of the embodiment of the application, after the use of the target profile is finished, the terminal target reports the use condition of the profile, and the server records the use condition of the target profile, so as to assist the selection and distribution of the follow-up profile.

Further, in the scheme of the embodiment of the application, in response to the use condition of the target profile meeting the recycling condition or in response to the receiving of the recycling instruction, the terminal judges whether the target service is completed, and if not completed, the terminal negotiates with the server to continue to use the target profile. Compared with a scheme that a terminal directly returns the target profile usage right, the scheme is beneficial to ensuring smooth execution of the service.

Drawings

Fig. 1 is a schematic diagram of data interaction of a profile allocation method in an embodiment of the present application;

FIG. 2 is a schematic diagram of data interaction of another profile allocation method according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a profile distributing apparatus according to an embodiment of the present application;

fig. 4 is a schematic structural view of another profile distribution apparatus according to an embodiment of the present application.

Detailed Description

As described in the background art, in the prior art, the profile is downloaded to the eSIM and is fixed for use, and if the frequency of data transmission is low, the profile is in an idle state for a long time, which is easy to cause a problem of resource waste.

Taking an industrial internet of things scenario as an example, an internet of things device is configured with an eSIM, and uses an eSIM access network to perform services such as data transmission. In an industrial internet of things scene, the frequency of data transmission of internet of things equipment is low, and in the time of not carrying out data transmission, profile is in an unused stage, so that resource waste is caused.

In view of this, an embodiment of the present application provides a method for allocating profile, in the solution of the embodiment of the present application, a terminal sends a profile request message to request a server for a target profile for a target service, and the server responds to the profile request message to select the target profile from idle profiles and send the target profile to the terminal. In the scheme of the embodiment of the application, the terminal allocates the profile based on the service request server, and the server allocates the profile to the terminal based on the service requirement of the terminal. That is, when there is a service at the terminal side, the profile is allocated to the terminal, and when there is no service at the terminal side, the profile is not allocated to the terminal, so that the profile can be allocated to the terminal with the service requirement, and the situation that the profile is not used after being allocated is avoided, thereby being beneficial to improving the utilization rate of the profile.

It should be noted that, in the embodiment of the present application, the "profile" refers to a generic term of a series of files and data related to an operator, and a terminal may access a network of the operator using the profile. If the eSIM does not have the profile, the terminal cannot access the network of the operator by using the eSIM.

In order to make the above objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures are described in detail below.

Referring to fig. 1, fig. 1 is a schematic diagram of data interaction of a profile allocation method in an embodiment of the present application. The method illustrated in fig. 1 may include S11 to S13. In the present application, S in each step number represents a step (step).

S11, the terminal sends a profile request message to the server.

In the scheme of the embodiment of the application, the terminal sends a profile request message to the server so as to request the profile for the target service from the server. That is, the profile request message is associated with a service of the terminal, and the terminal transmits the profile request message to the server based on a requirement of the service.

Specifically, the server may store a plurality of profiles, which may be profiles purchased from one or more operators, and manage the plurality of profiles.

In the solution of the embodiment of the present application, each profile may have attribute information, where the attribute information may include at least one of the following: status, operator identification, rate, traffic threshold.

Specifically, the profile state may be an idle state or a usage state, where the idle state indicates that the profile has not been allocated to a terminal for use, and the usage state indicates that the profile has been allocated to a terminal for use. The operator identity may be used to indicate the operator providing the profile. The charging criteria for profile determined by the operator may be used to determine the fee the terminal needs to pay to use the profile. In implementations, the rates for different profiles may be different. In addition, the flow threshold of the profile may refer to a package flow threshold corresponding to the profile, and if the flow of the terminal using the profile exceeds the flow threshold of the profile, the cost needs to be calculated according to the rate set by the operator.

For example, the server may be configured with a first profile set and a second profile set, wherein the first profile set includes free profiles and the second profile set includes assigned profiles. That is, the profiles in the first profile set are all idle states, and the profiles in the second profile set are all in use states.

In addition, the terminal in the embodiment of the application can be configured with an eSIM and can communicate with a network. More specifically, an eSIM can support multiple profiles. The terminal may be a mobile phone, a computer, an internet of things device, a wearable device, a vehicle-mounted terminal, etc., but is not limited thereto.

In a specific implementation, the eSIM of the terminal may be configured with a fixed profile. The terminal may monitor a service requirement, and in response to the monitored requirement of the target service, the terminal may send a profile request message to the server using a fixed profile, where the profile request message is used to request a profile for the target service.

As a possible implementation manner, the target service may be preset, and if it is detected that the upcoming service is the target service, the terminal may send a profile request message to the server.

As another possible implementation, the target service may be a non-fixed service, the target service being an upcoming service, the terminal requesting a profile for the upcoming service from the server.

In an embodiment of the present application, before executing S31, the terminal may estimate the traffic required by the target service, and record the estimated traffic. If the estimated traffic flow is greater than or equal to the first traffic threshold, S31 may be performed, and if the estimated traffic flow is less than the first traffic threshold, the target traffic may be performed using a fixed profile. That is, the terminal may request the target profile in case that the target traffic is a high traffic. The first flow threshold may be determined according to a flow threshold of the fixed profile, for example, the first flow threshold is a result of subtracting a set threshold from the flow threshold of the fixed profile.

Illustratively, the flow threshold of the fixed profile is less than the flow threshold of the target profile. In other words, the fixed profile may be a low traffic profile, the target profile may be a high traffic profile, and the terminal may obtain the usage rights of the high traffic profile through the profile request message.

In an embodiment of the present application, the profile request message may include a service related parameter, which may be used to describe the requirements of the target service. Thus, after receiving the profile request message, the server can select an appropriate profile according to the service related parameters.

Illustratively, the service related parameter may include at least one of: service type, service estimation duration, service estimation traffic. The service type refers to a type of a target service, for example, a voice service, a video service, a database service, etc., but is not limited thereto. The service estimation duration may be a duration of time for completing the target service estimated by the terminal, and the service estimation flow may be a flow for completing the target service estimated by the terminal.

Also, as an example, the profile request message may further include location information of the terminal, which indicates a location or area where the terminal is located. In practice, operators who provide services in different areas may be different. Therefore, the position information of the terminal is reported, so that the server can select the profile of the operator providing the service in the current area according to the position of the terminal, and the problem that the selected target profile cannot be normally used is avoided.

After S11, the server selects a target profile from the idle profiles in response to the profile request message.

Specifically, the server may select a target profile from the first profile set.

In an embodiment of the present application, the server may randomly select one profile from the first profile set as the target profile.

In another embodiment of the present application, the server may select the target profile according to location information and/or service related parameters of the terminal.

Specifically, the server may determine, according to the location information of the terminal, a target operator that provides a service in an area where the terminal is located, and select a target profile from profiles that are provided by the target operator and are in an idle state.

In a specific implementation, the server may also select the target profile according to the service-related parameters.

Specifically, the server may determine the target profile according to one or more of the service type, the service estimation duration, and the service estimation traffic.

Illustratively, since the user generally expects that the traffic actually used by the target traffic can not exceed the traffic threshold of the target profile, in order to save costs. For this, the server may preferentially select the target profile according to the traffic estimation traffic and the traffic threshold of each idle profile.

Also exemplary, the server may calculate the second estimated traffic based on the traffic type and the estimated duration of the traffic. And recording the service estimated flow reported by the terminal as a first service estimated flow, and comparing the first service estimated flow and a second service estimated flow by the server and determining a target profile according to a comparison result. Specifically, the flow threshold of the target profile determined according to the first traffic estimation flow is smaller than the flow threshold of the target profile determined according to the second traffic estimation flow.

If the difference between the second traffic estimated traffic minus the first traffic estimated traffic is greater than or equal to the difference threshold, a target profile may be selected based on the second traffic estimated traffic. By adopting the scheme, the problem that the actual flow of the target service executed by the terminal by using the profile selected according to the estimated flow of the first service exceeds the flow threshold too much can be avoided, and the cost of using the target profile by the terminal can be reduced.

If the difference between the second traffic estimated traffic minus the first traffic estimated traffic is less than the difference threshold, a target profile may be selected based on the first traffic estimated traffic. In this case, even if the actual traffic of the terminal performing the target traffic exceeds the traffic threshold using the profile selected according to the first traffic estimation traffic, the exceeded traffic is generally acceptable. By adopting the scheme, the server can reserve the use right of the high-flow profile as much as possible so as to cope with the subsequent use requirement, and is beneficial to optimizing the overall distribution and utilization of the profile.

As a possible implementation manner, the server may also select the target profile according to the idle duration of each idle profile. Specifically, the idle duration of the profile in the first profile set and the probability that the profile is selected as the target profile are positively correlated. The idle duration refers to a time interval between a time when the profile is last used and a current time. By adopting the scheme, the overall utilization rate of profile at the server is improved.

As another possible implementation, the server may select the target profile according to the rate of the idle profile. Specifically, the server may select the target profile according to the service-related parameters and the rate of the profile, so that the total cost of the target profile for the target service is as low as possible.

In an embodiment of the present application, the server may modify the service-related parameters according to the profile request preference of the terminal before selecting the target profile according to the service-related parameters.

Specifically, the server may record profile request preferences of the terminal. The profile request preference of the terminal can be used for describing the difference or the size relation between the service related parameters reported by the terminal and the actual use condition of the profile. The actual profile use condition may include a duration of actually using the profile by the terminal, an actually used flow rate, and the like. For example, the estimated traffic flow reported by the terminal is typically 80% of the actual traffic used by profile. In this case, the server may increase the traffic estimation traffic to obtain the corrected traffic estimation traffic.

Specifically, the profile request preference of the terminal may be determined according to the service related parameters reported by the terminal in a past period of time and the actual use condition of the corresponding profile, and different terminals may have different profile request preferences. In addition, profile request preferences of the same terminal may also vary.

Further, the server may select a target profile from the idle profiles according to the corrected service related parameters. In the scheme, certain difference between the service related parameters reported by the terminal and the actual use condition of the profile is considered, the service related parameters are corrected according to the profile request preference, and the target profile is selected according to the corrected service related parameters, so that the matching degree of the selected target profile and the target service is higher.

S12, the server transmits the target profile to the terminal.

Specifically, after determining the target profile, the server may assign the usage rights of the target profile to the terminal.

On the one hand, the server transmits the target profile, and correspondingly, the terminal downloads the target profile from the server.

On the other hand, the server may change the state of the target profile from the idle state to the use state. Specifically, the server may remove the target profile from the first profile set and add it to the second profile set.

Thereby, the terminal obtains the usage right of the target profile.

Further, after the downloading of the target profile is completed, the terminal may activate the target profile and execute the target service using the activated profile.

The following describes in detail a process of recovering the usage rights of the target profile by the server.

In an embodiment of the present application, when the target service is completed, the terminal may end to use the target profile.

Further, in response to the end of the use of the target profile, the terminal may deactivate the target profile.

Further, in response to the end of the use of the target profile, the terminal may transmit a completion notification message to the server to notify the server that the terminal ends using the target profile.

Further, in response to receiving the completion notification message, the server may reclaim usage rights for the target profile. Specifically, the server may change the state of the profile from the use state to the idle state, remove the target profile from the second profile set, and add the target profile to the first profile set. Thus, the target profile is restored to the idle state and waits for the next allocation.

In a specific implementation, in response to the end of the use of the target profile, the terminal may also report the use condition of the target profile to the server. That is, after the usage of the target profile is finished, the terminal reports the actual usage of the target profile. For example, the usage of the target profile may be carried in the completion notification message described above.

Further, the server may save the usage of the target profile for subsequent use in updating the profile request preferences of the terminal.

In a specific implementation, the completion notification message and the target profile may be reported using the fixed profile.

In this way, the embodiment of the application provides a method for distributing profiles, which is different from a method for fixedly using profiles, and the embodiment of the application performs unified planning management on the usage rights of a plurality of profiles by a server, comprehensively considers information such as the position of a terminal, service type, service duration, service flow and the like, selects a proper profile, distributes the selected profile to the terminal, and timely recovers the distributed profile. Therefore, in the scheme of the embodiment of the application, the server does not fix the profile (high-flow profile) to a certain terminal for use, and dynamically distributes the profile according to the service requirements of each terminal, so that the utilization rate of the profile can be effectively improved, and the comprehensive use cost is reduced.

In an embodiment of the present application, if the server does not select the target profile from the idle profiles, the server may recover the profile from other terminals, and then allocate the recovered profile to the terminal for use. Specifically, the server may negotiate with the terminal using the profile, and after the negotiation is successful, the server recovers the profile used by the terminal. For example, the target profile selection fails due to the fact that the profiles at the server are in a use state or the currently idle profiles cannot meet the service requirements of the terminal.

In consideration of the above situation, in the solution of the embodiment of the present application, the server may record the usage terminal and the service of each profile in the second profile set. That is, for each profile in the second profile, a terminal currently using the profile and a service performed by the terminal using the profile are recorded.

Further, if the selection of the target profile fails and the priority of the target service is higher than the priority of the service executed by each profile currently in use, the server may recover one of the profiles in use. For example, the server may select the usage right to recycle the profile with the lowest service priority, and assign the recycled profile as the target profile to the terminal. By adopting the scheme, the overall utilization rate of profile is facilitated, and the service with high priority is ensured to be executed preferentially

Referring to fig. 2, fig. 2 is a schematic diagram of data interaction of another profile allocation method according to an embodiment of the present application. The method illustrated in fig. 2 may include S21 and S22. In a specific implementation, S21 and S22 may be performed after S12 in fig. 1.

S21, the terminal sends a deferred request message to the server.

Wherein the deferred request message may be used to request continued use of the target profile. For example, the deferred request message may include a deferred duration.

In an embodiment of the present application, the server may send a reclamation instruction to the terminal before S21. The embodiment of the application does not limit the time when the server sends the recycling instruction.

For example, the target profile may be configured with a reclamation condition, and the server may send a reclamation instruction to the terminal in response to the usage of the target profile satisfying the reclamation condition. For example, the target profile may be set with a usage time length threshold, and if the duration of using the target profile by the terminal reaches the usage time length threshold, the server may send a reclamation instruction to the terminal.

Also for example, the server needs to urgently assign the target profile to a higher priority terminal or use a higher priority service, and the server may send a reclamation instruction to the terminal.

In response to the reclamation instruction, the terminal may first determine whether the target service is completed, and if the target service is completed, may deactivate the target profile and send a completion notification message to the server, so that the server reclaims the usage rights of the target profile. If the target service is not completed, the terminal can send a deferred request message to the server.

In another embodiment of the present application, the target profile may be configured with a recovery condition, and the terminal determines whether the usage of the detected target profile satisfies the recovery condition in the process of using the target profile. And in response to the use condition of the target profile meeting the recovery condition, the terminal can further judge whether the target service is completed. If the target service is completed, the target profile may be deactivated and a completion notification message may be sent to the server so that the server may recover the usage rights of the target profile. If the target service is not completed, the terminal can send a deferred request message to the server.

S22, the server sends a response of the deferred request message to the terminal.

The response of the deferral request message may be an acknowledgement of the deferral request message, or the response of the deferral request message may be a negative acknowledgement of the deferral request message.

If the terminal receives the confirmation of the deferred request message, the terminal can continue to use the target profile.

If the terminal receives the denial of the deferred request message, the terminal can end using the target profile so that the server can recover the use right of the target profile.

Further, after the terminal finishes using the target profile, the terminal may request a new profile from the server again.

In the scheme of the embodiment of the application, the terminal can initiate the negotiation process of continuing to use the profile for the recovery instruction of the server, thereby being beneficial to ensuring the smooth proceeding of the target service.

In other embodiments, the server may have super rights. Specifically, the server may send a reclamation instruction to the terminal, after the terminal receives the reclamation instruction, the terminal may determine the type of the reclamation instruction, and if the type of the reclamation instruction is a common type and the target service is not yet completed, the terminal may execute the scheme shown in fig. 2 to negotiate to continue to use the target profile. If the type of the recycling instruction is a mandatory type, the terminal can end using the target profile, i.e. directly return the use right of the target profile.

It will be appreciated that in a specific implementation, the method may be implemented in a software program running on a processor integrated within a chip or a chip module; alternatively, the method may be implemented in hardware or a combination of hardware and software, for example, implemented in a dedicated chip or chip module, or implemented in a dedicated chip or chip module in combination with a software program.

Referring to fig. 3, fig. 3 is a schematic structural diagram of a profile distributing apparatus according to an embodiment of the present application, where an eSIM may be built in the profile distributing apparatus. The profile allocation apparatus shown in fig. 3 may be deployed at the above terminal, and the apparatus shown in fig. 3 may include:

a communication module 31, configured to send a profile request message, where the profile request message is used to request a target profile for the target service;

the communication module 31 is further configured to download the target profile.

In an implementation, the profile allocation apparatus shown in fig. 3 may correspond to a chip having a communication function in a terminal; or corresponds to a chip or a chip module having a communication function included in the terminal, or corresponds to the terminal.

Referring to fig. 4, fig. 4 is a schematic structural diagram of another profile allocation apparatus according to an embodiment of the present application, where the apparatus shown in fig. 4 may be deployed on the server, and the apparatus shown in fig. 4 may include:

A communication module 41, configured to receive a profile request message, where the profile request message is used to request a target profile for a target service;

the communication module 41 is further configured to issue the target profile.

In addition, the apparatus shown in fig. 4 may further include a processing module 42, configured to select the target profile from the idle profiles in response to the profile request message.

In an implementation, the profile allocation apparatus shown in fig. 4 may correspond to a chip having a communication function in a server; or corresponds to a chip or a chip module having a communication function included in the server, or corresponds to the server.

For more matters such as the working principle, the working method and the beneficial effects of the profile allocation apparatus in the embodiment of the present application, reference may be made to the above related description about the communication method, which is not repeated here.

The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, performs the profile allocation method described above. The storage medium may include ROM, RAM, magnetic or optical disks, and the like. The storage medium may also include a non-volatile memory (non-volatile) or a non-transitory memory (non-transitory) or the like.

The embodiment of the application also provides a terminal, which comprises a memory and a processor, wherein the memory stores a computer program which can be run on the processor, and the processor executes the steps of the profile allocation method when running the computer program. The terminal comprises, but is not limited to, a mobile phone, a computer, a tablet personal computer and other terminal equipment. The terminal may be a mobile phone, a computer, a tablet computer, a vehicle-mounted terminal, an internet of things device, etc., but is not limited thereto.

The embodiment of the application also provides a server, which comprises a memory and a processor, wherein the memory stores a computer program which can be run on the processor, and the processor executes the steps of the profile allocation method when running the computer program.

It should be appreciated that in the embodiment of the present application, the processor may be a central processing unit (central processing unit, abbreviated as CPU), and the processor may also be other general purpose processors, digital signal processors (digital signal processor, abbreviated as DSP), application specific integrated circuits (application specific integrated circuit, abbreviated as ASIC), field programmable gate arrays (field programmable gate array, abbreviated as FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically erasable ROM (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM for short) which acts as an external cache. By way of example but not limitation, many forms of random access memory (random access memory, abbreviated as RAM) are available, such as static random access memory (static RAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, abbreviated as DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus random access memory (direct rambus RAM, abbreviated as DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer program may be stored in or transmitted from one computer readable storage medium to another, for example, by wired or wireless means from one website, computer, server, or data center.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus and system may be implemented in other manners. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only one logic function division, and other division modes can be adopted in actual implementation; for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal, each module/unit included in the device, product, or application may be implemented by using hardware such as a circuit, different modules/units may be located in the same component (for example, a chip, a circuit module, or the like) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program, where the software program runs on a processor integrated inside the terminal, and the remaining (if any) part of the modules/units may be implemented by using hardware such as a circuit.

The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In this context, the character "/" indicates that the front and rear associated objects are an "or" relationship.

The term "plurality" as used in the embodiments of the present application means two or more.

The first, second, etc. descriptions in the embodiments of the present application are only used for illustrating and distinguishing the description objects, and no order is used, nor is the number of the devices in the embodiments of the present application limited, and no limitation on the embodiments of the present application should be construed.

Although the present application is disclosed above, the present application is not limited thereto. Various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the application, and the scope of the application should be assessed accordingly to that of the appended claims.

Claims

1. A profile allocation method, the method comprising:

transmitting a profile request message, wherein the profile request message is used for requesting a target profile for a target service;

and downloading the target profile.

2. The profile allocation method according to claim 1, wherein the sending a profile request message includes:

and responding to the requirement of the target service, and sending the profile request message.

3. The profile allocation method according to claim 1, wherein the profile request message includes a service related parameter, the service related parameter being used to describe a requirement of the target service.

4. A profile allocation method according to claim 3, wherein the traffic related parameters comprise at least one of:

service type, service estimation duration, service estimation traffic.

5. The profile allocation method according to claim 1, wherein the profile request message includes: and the position information of the terminal.

6. The profile allocation method according to claim 1, wherein the method further comprises: and deactivating the target profile in response to the end of use of the target profile.

7. The profile allocation method according to claim 1, wherein the method further comprises: and reporting the completion notification message.

8. The profile allocation method according to claim 1, wherein the method further comprises: and reporting the service condition of the target profile.

9. The profile allocation method according to claim 1, wherein the method further comprises: and judging whether the target service is finished or not in response to the use condition of the target profile meeting the recycling condition or in response to the receiving of a recycling instruction, and negotiating to continue to use the target profile if the judging result is negative.

10. The profile allocation method according to claim 9, wherein the negotiating to continue using the target profile comprises:

a deferred request message is sent, and the deferred request message is used for requesting to continue to use the target profile;

and receiving a response of the deferred request message.

11. The profile allocation method according to claim 1, wherein the method further comprises: and deactivating the target profile in response to the use condition of the target profile meeting a recycling condition or in response to the receipt of a recycling instruction.

12. A profile allocation method, the method comprising:

receiving a profile request message, wherein the profile request message is used for requesting a target profile for a target service;

and issuing the target profile.

13. The profile allocation method according to claim 12, wherein the profile request message includes a service related parameter, the service related parameter being used to describe a requirement of the target service.

14. The profile allocation method according to claim 13, wherein the service related parameters comprise at least one of:

service type, service estimation duration, service estimation traffic.

15. The profile assignment method as claimed in claim 13, wherein before the target profile is issued, the method further comprises:

and responding to the profile request message, and selecting the target profile from idle profiles.

16. The profile assignment method as claimed in claim 15, wherein selecting the target profile from idle profiles comprises:

correcting the service related parameters according to profile request preference of the terminal;

and selecting the target profile from the idle profiles according to the corrected service related parameters.

17. The profile assignment method as claimed in claim 15, wherein selecting the target profile from idle profiles comprises:

and selecting the target profile according to the idle duration of the idle profile and/or the rate of the idle profile.

18. The profile allocation method of claim 12, further comprising: receiving a completion notification message;

and responding to the completion notification message, and recovering the target profile.

19. The profile allocation method of claim 12, further comprising: and receiving the use condition of the target profile.

20. The profile allocation method of claim 12, further comprising: and sending a recycling instruction.

21. The profile allocation method of claim 12, further comprising: receiving a deferred request message, wherein the deferred request message is used for requesting to continue to use the target profile;

and sending a response of the deferred request message.

22. A profile distribution apparatus, the apparatus comprising:

the communication module is used for sending a profile request message, wherein the profile request message is used for requesting a target profile for a target service;

The communication module is also used for downloading the target profile.

23. A profile distribution apparatus, the apparatus comprising:

the communication module is used for receiving a profile request message, wherein the profile request message is used for requesting a target profile for a target service;

the communication module is also used for issuing the target profile.

24. A computer readable storage medium having stored thereon a computer program, which, when run by a processor, causes the profile allocation method of any one of claims 1 to 11 or the profile allocation method of any one of claims 12 to 21 to be performed.

25. A terminal comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the profile allocation method according to any of claims 1 to 11 when the computer program is executed.

26. A server comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the profile allocation method according to any of claims 12 to 21 when the computer program is executed.