Deployment method, device and system of application server

Abstract

The embodiment of the invention provides an application server deployment method, device and system, and relates to the technical field of communication. The method comprises the steps that a configuration server receives a first request message from first equipment, the first request message requests the configuration server to find an enabling server associated with a first application server identified by a first identifier, and the first application server is used for providing service for a terminal when the terminal is located at a target position; the configuration server determines at least one enabled server according to the first request message and instantiation time information of at least one application server associated with each enabled server; the configuration server sends information of at least one enabled server to the first device, the information of the at least one enabled server is used for determining a first enabled server, and the first enabled server is an enabled server associated with the first application server. Therefore, the application server meeting the requirement can be selected for the terminal when the terminal arrives at the target position.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and system for deploying an application server. Background Technology

[0002] An edge application server (EAS) typically refers to a server located in an edge data network (EDN). It is characterized by its proximity to end users or data sources to provide low-latency, high-bandwidth services.

[0003] In existing technologies, terminal devices can discover edge enabler servers (EES) through edge configuration servers (ECS), and then discover EAS through EES. Summary of the Invention

[0004] This application provides a method, apparatus, and system for deploying an application server. This solution can instantiate the application server before the terminal moves to the target location, thereby providing better services to the terminal.

[0005] The technical solution is as follows:

[0006] In a first aspect, embodiments of this application provide a method for deploying an application server. The method includes: a configuration server receiving a first request message from a first device, the first request message including a first identifier, the first request message requesting the configuration server to discover an enabling server associated with a first application server identified by the first identifier, the first application server being used to provide services to the terminal when the terminal is located at a target location; the configuration server determining at least one enabling server based on the first request message and instantiation time information (i.e., first time information) of at least one application server associated with each of the one or more enabling servers; the configuration server sending information of the at least one enabling server to the first device, the information of the at least one enabling server being used to determine a first enabling server, the first enabling server being an enabling server associated with the first application server.

[0007] In this scheme, the configuration server can select at least one enabling server for the terminal based on the first request message from the first device and the instantiation time information of at least one application server associated with each of the one or more enabling servers. Since the at least one enabling server includes a first enabling server, and the first enabling server is associated with a first application server, the first application server can be used to provide services to the terminal when the terminal reaches the target location. This scheme can achieve the acquisition of a first application server that meets the requirements.

[0008] In one possible implementation, the first request message further includes first time information, which indicates the time when the terminal arrives at the target location;

[0009] The configuration server determines at least one enabling server based on the first request message and the instantiation time information of at least one application server associated with each enabling server, including:

[0010] The configuration server determines the first enabling server based on the instantiation time information of at least one application server associated with each enabling server and the first time information. The first application server associated with the first enabling server completes instantiation before the time indicated by the first time information.

[0011] In one possible implementation, the configuration server sending the information of the at least one enabling server to the first device further includes:

[0012] The configuration server sends the instantiation time information and instantiation status information of one or more application servers to the first device, wherein the one or more application servers are application servers respectively associated with the at least one enabling server.

[0013] In one possible implementation, the first request message further includes: first time information or first instruction information. The first instruction information is at least an ACR of the service continuity planning type.

[0014] In one possible implementation, the method provided in this application embodiment further includes:

[0015] The configuration server obtains the instantiation time information of at least one application server associated with each of the one or more enabling servers.

[0016] In one possible implementation, the configuration server obtains instantiation time information of at least one application server associated with each of the one or more enabling servers, including:

[0017] The configuration server receives a third request message from any one of the one or more enabling servers. The third request message carries the identifier of the enabling server, the instantiation status information of one or more application servers associated with the enabling server, and the instantiation time information of one or more application servers.

[0018] In one possible implementation, the configuration server obtains instantiation time information of at least one application server associated with each of the one or more enabling servers, including:

[0019] The configuration server obtains configuration information, which includes the instantiation time of the EAS associated with different EAS identifiers;

[0020] The configuration server receives a second indication from any of the enabling servers, the second indication indicating that a second application server is being instantiated; the second application server is one of at least one application server associated with any of the enabling servers.

[0021] The configuration server determines the instantiation time information of the second application server based on the second indication information and the configuration information.

[0022] In one possible implementation, the instantiation time information of any of the application servers is the remaining duration of the application server instantiation, or the completion time of the application server instantiation.

[0023] In one possible implementation, the instantiation time information of any of the application servers is determined by the start time of the application server instantiation and / or the duration of the instantiation, as well as the corresponding instantiation duration of the application server.

[0024] In one possible implementation, the instantiation time information is either the remaining instantiation time of the application server or the completion time of the application server instantiation.

[0025] In one possible implementation, the instantiation time information is determined by the start time of application server instantiation and / or the duration of application server instantiation, as well as the target instantiation duration of the application server. The target instantiation duration is the total time required for the application server to complete instantiation from the start of instantiation.

[0026] In one possible implementation, the method provided in this application embodiment includes: a configuration server receiving second indication information from at least one enabling server, the second indication information being used to indicate the duration for which a second application server has been instantiated, or the start time of the instantiation of the second application server.

[0027] In one possible implementation, the second indication information is further used to indicate that the instantiation of the second application server is in progress. The method provided in this application embodiment further includes: the configuration server determining the instantiation time information of the second application server based on the second indication information. For example, the remaining instantiation time or the instantiation completion time of the second application server.

[0028] In one possible implementation, the method provided in this application embodiment further includes: a configuration server receiving instantiation time information corresponding to an application server associated with any of at least one enabling server. Alternatively, the configuration server pre-configures the duration required for application server instantiation.

[0029] In one possible implementation, the method provided in this application embodiment includes: a configuration server receiving instantiation time information from at least one application server corresponding to at least one enabling server.

[0030] In one possible implementation, the first request message includes second time information, which indicates the time when the terminal arrives at the target location.

[0031] In one possible implementation, the method provided in this application includes: a configuration server determining a first enabling server based on at least one of instantiation status information, instantiation time information, and second time information corresponding to at least one application server associated with each enabling server.

[0032] In one possible implementation, the configuration server sends at least one enabling server information to the first device, including: the configuration server sending a first response message to the first device, the first response message including the first enabling server information. For example, the first enabling server information includes the identifier of the first enabling server and / or the address of the first enabling server.

[0033] In one possible implementation, the configuration server sends information about at least one enabling server to the first device, including: the configuration server sending a first response message to the terminal device, the first response message including information about at least one enabling server, instantiation status information and instantiation time information of one or more application servers associated with any of the at least one enabling server. The at least one enabling server can be all or some of the one or more enabling servers.

[0034] In one possible implementation, the method provided in this application embodiment further includes: a configuration server obtaining information about multiple platforms corresponding to at least one enabling server.

[0035] In one possible implementation, the enabling server configures its identification information, address information, and information about at least one platform corresponding to the enabling server. The enabling server sends a registration request message to the configuration server, which includes, but is not limited to, the enabling server's identification information, the application server's identification information, the application server's status information, and information about at least one platform.

[0036] Optionally, the method provided in this application embodiment further includes: a configuration server determining the deployment time of the application server on different platforms based on information from at least one platform. The configuration server receives a service configuration request message from a terminal device. Correspondingly, the terminal device sends a configuration service request message to the configuration server. For example, the configuration service request message is a service provisioning request message, which carries the identifier of the application server and second time information. When it is necessary to select an instantiable application server, the configuration server determines the enabling server based on the second time information, information from at least one platform, and the capability information corresponding to the platform.

[0037] Optionally, the method provided in this application embodiment further includes: a configuration server receiving a service configuration request message from a terminal device. Correspondingly, the terminal device sends a configuration service request message to the configuration server. The configuration server sends a service configuration response message to the terminal device. Correspondingly, the terminal device receives a service configuration response message from the configuration server. In the absence of an available application server, the terminal device determines the deployment time of the application server on different platforms based on information from at least one platform, and determines the enabling server based on second time information.

[0038] Secondly, embodiments of this application provide a method for deploying an application server, the method comprising: a first enabling server receiving a second request message from a first device, the second request message including a first identifier, the second request message requesting the discovery of a first application server identified by the first identifier, the first application server being used to provide services to the terminal when the terminal is located at a target location;

[0039] The first enabling server determines at least one application server based on the second request message and the instantiation information of one or more application servers associated with the first enabling server. The instantiation information includes the instantiation status information and instantiation time information of the application server. The first enabling server sends the information of the at least one application server to the first device. The information of the at least one application server is used by the first device to determine the first application server.

[0040] In one possible implementation of this application, the first enabling server sends information about the at least one application server to the first device, including: the first enabling server sending information about the first application server to the first device, or sending information about the at least one application server to the first device, and instantiation information of at least one of the application servers.

[0041] In one possible implementation, the second request message includes second time information, which indicates the time when the terminal arrives at the target location.

[0042] In one possible implementation, the method provided in this application embodiment includes: a first enabling server determining a first application server based on at least one of instantiation state information, instantiation time information, and first time information corresponding to at least one application server, wherein the first application server completes instantiation before the terminal reaches the target location.

[0043] In one possible implementation, the first enabling server sends information about at least one application server to the terminal, including: the first enabling server sending a second response message to the terminal, the second response message including information about the first application server. The information about the first application server includes the application server's identification information and / or address information.

[0044] In one possible implementation, the instantiation time information is either the remaining duration of application server instantiation or the time when application server instantiation is complete.

[0045] In one possible implementation, the instantiation time information of any application server is determined by the start time of instantiation of any application server and / or the duration of instantiation, as well as the duration of the target instance corresponding to any application server.

[0046] In one possible implementation, the method provided in this application embodiment includes: a first enabling server receiving second indication information from a first network management system, the second indication information indicating the duration for which a second application server has been instantiated, or the start time of the instantiation of the second application server. The second application server is any application server associated with the first enabling server.

[0047] In one possible implementation, the method provided in this application embodiment includes: a first enabling server determining the instantiation time information of the second application server based on second instruction information and the duration required for the instantiation of the second application server. It is understood that, for any application server associated with the first enabling server, the first enabling server may determine the instantiation time information of any application server by referring to the method used to determine the instantiation time information of the second application server.

[0048] In one possible implementation, the method provided in this application embodiment further includes: the first enabling server sending the instantiation time information corresponding to the first application server to the configuration server.

[0049] In one possible implementation, the method provided in this application embodiment includes: a first enabling server determining the duration for which the second application server has been instantiated, or the start time of the instantiation of the second application server, based on second indication information. The first enabling server sends the first indication information to a configuration server. In this application embodiment, the duration for which the application server has been instantiated can be referred to as the execution duration.

[0050] In one possible implementation, the method provided in this application embodiment further includes: a first enabling server sending a second response message to a terminal, the second response message including information of at least one application server, wherein the information of any one of the at least one application server includes the identification information of the application server, and / or, address information, and instantiation time information corresponding to the application server.

[0051] In one possible implementation, the method provided in this application further includes: a first enabling server receiving a discovery request message from a terminal. The discovery request message includes a first identifier and second time information. When it is necessary to select an instantiable application server, the first enabling server determines the platform on which the first application server is deployed based on the second time information, information about at least one platform, and the capability information corresponding to the platform. The first enabling server sends indication information to a first network management system. The indication information is used to trigger the instantiation of the first application server.

[0052] Optionally, the method provided in this application embodiment further includes: the first enabling server directly configuring the deployment duration information of the first application server.

[0053] Thirdly, embodiments of this application provide a method for deploying an application server, the method comprising: a first device (e.g., a terminal or the terminal's EEC or the source enable server corresponding to the terminal) sending a first request message to a configuration server, the first request message including a first identifier, the first request message requesting the configuration server to discover an enable server associated with a first application server identified by the first identifier, the first application server being used to provide services to the terminal when the terminal is located at a target location;

[0054] The first device receives information from at least one enabling server from the configuration server, the information of the at least one enabling server being used to determine a first enabling server, the first enabling server being the enabling server associated with the first server among the at least one enabling servers;

[0055] The first device sends a second request message to the first enabling server. The second request message includes the first identifier and requests the first enabling server to discover the first application server identified by the first identifier.

[0056] The first device receives information from one or more application servers, including the first application server, from the first enabling server.

[0057] In one possible implementation of this application, the first request message further includes second time information, which is used to indicate the time when the terminal arrives at the target location;

[0058] The first device receives information from at least one enabling server of the configuration server, including:

[0059] The first device receives information from the first enabling server of the configuration server.

[0060] In one possible implementation of this application, the second request message further includes second time information, which is used to indicate the time when the terminal arrives at the target location;

[0061] The first device receives information from one or more application servers from the first enabling server, including:

[0062] The first device receives information from the first application server from the first enabling server.

[0063] In one possible implementation of this application, the first device receives information from at least one enabling server from the configuration server, and further includes:

[0064] The first device receives instantiation status information and instantiation time information of the application server associated with each of the at least one enabling server in the configuration server;

[0065] The method further includes:

[0066] The first device determines the first enabling server from at least one enabling server based on the instantiation status information, instantiation time information, and second time information of the application server associated with each enabling server.

[0067] In one possible implementation of this application, the first device receives information from one or more application servers from the first enabling server, and further includes:

[0068] The first device receives instantiation status information and instantiation time information of one or more application servers associated with the first enabling server from the first enabling server.

[0069] The method further includes:

[0070] The first device determines the first application server from the one or more application servers associated with the first enabling server based on the instantiation status information, instantiation time information, and second time information.

[0071] In one possible implementation of this application, the first device receives information from one or more application servers from the first enabling server, including:

[0072] The first device receives information from the first application server from the first enabling server.

[0073] Fifthly, embodiments of this application provide a communication device that can implement the methods in the first aspect or any possible implementation of the first aspect, and therefore can also achieve the beneficial effects of the first aspect or any possible implementation of the first aspect. This communication device can be a configuration server, or an apparatus that supports the configuration server in implementing the methods in the first aspect or any possible implementation of the first aspect, such as a chip applied in the configuration server. This device can implement the above methods through software, hardware, or hardware executing corresponding software.

[0074] Sixthly, embodiments of this application provide a communication device that can implement the methods in the second aspect or any possible implementation of the second aspect, and therefore can also achieve the beneficial effects of the second aspect or any possible implementation of the second aspect. This communication device can be an enabling server, or an apparatus that supports the enabling server in implementing the methods in the second aspect or any possible implementation of the second aspect, such as a chip applied in the enabling server. This device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0075] Seventhly, embodiments of this application provide a communication device that can implement the methods in the third aspect or any possible implementation of the third aspect, and thus also achieve the beneficial effects of the third aspect or any possible implementation of the third aspect. The communication device can be a first device or an apparatus that supports the first device in implementing the methods in the third aspect or any possible implementation of the third aspect, such as a chip applied in the first device. The device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0076] Eighthly, embodiments of this application provide a communication device that can implement the methods in the fourth aspect or any possible implementation of the fourth aspect, and thus also achieve the beneficial effects of the fourth aspect or any possible implementation of the fourth aspect. The communication device can be a first device or an apparatus that supports the first device in implementing the methods in the fourth aspect or any possible implementation of the fourth aspect, such as a chip or control circuit applied in the first device. The device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0077] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform an application server deployment method as described in any of the possible implementations of the first aspect.

[0078] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform an application server deployment method as described in any of the possible implementations of the second aspect.

[0079] Eleventhly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform an application server deployment method as described in any of the possible implementations of the third aspect to the third aspect.

[0080] In a twelfth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform an application server deployment method as described in any of the possible implementations of the fourth aspect to the fourth aspect.

[0081] In a thirteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform an application server deployment method described in the first aspect or various possible implementations of the first aspect.

[0082] In a fourteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform an application server deployment method described in the second aspect or various possible implementations of the second aspect.

[0083] In a fifteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform an application server deployment method described in the third aspect or various possible implementations of the third aspect.

[0084] In a sixteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform an application server deployment method described in the fourth aspect or various possible implementations of the fourth aspect.

[0085] In a seventeenth aspect, embodiments of this application provide a communication device for implementing various methods in various possible designs of any of the first, second, third, or fourth aspects described above. The communication device may be the configuration server described above, or an apparatus containing the configuration server described above, or a component (e.g., a chip) applied to a configuration server. Alternatively, the communication device may be the enabling server described above, or an apparatus containing the enabling server described above, or a component (e.g., a chip) applied to an enabling server. Alternatively, the communication device may be the first device described above, or an apparatus containing the first device described above, or a component (e.g., a chip) applied to a first device. The communication device includes modules and units corresponding to the methods described above. These modules and units may be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0086] It should be understood that the communication device described in aspect seventeen above may further include: a bus and a memory, the memory being used to store code and data. Optionally, at least one processor communication interface and the memory are coupled to each other.

[0087] In an eighteenth aspect, embodiments of this application provide a communication device comprising at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the methods described in the first aspect or any of the various possible designs of the first aspect. For example, the communication device may be a configuration server, or a chip applied in a configuration server.

[0088] In a nineteenth aspect, embodiments of this application provide a communication device comprising at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform a method as described in the second aspect above, or any of the various possible designs of the second aspect. For example, the communication device may be an enabling server, or a chip applied in an enabling server.

[0089] In a twentieth aspect, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the methods described in the third aspect or any of the various possible designs of the third aspect. For example, the communication device may be a first device or a chip applied in a first device.

[0090] In a twentieth aspect, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform a method as described in the fourth aspect above, or any of the various possible designs of the fourth aspect. For example, the communication device may be a first device, or a chip applied in a first device.

[0091] It should be understood that the memory described in any of aspects eighteen to twenty-one may also be replaced by a storage medium, and the embodiments of this application do not limit this.

[0092] In one possible implementation, the memory described in any of aspects eighteen to twenty-one can be internal to the communication device. Of course, the memory can also be located external to the communication device, but at least one processor can still execute computer execution instructions or programs stored in the memory.

[0093] In a twentieth aspect, embodiments of this application provide a communication device comprising one or more modules for implementing the methods of any one of the first, second, third, and fourth aspects described above. The one or more modules may correspond to the various steps in the methods of any one of the first, second, third, and fourth aspects described above.

[0094] In a twenty-third aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods in the first aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0095] In a twentieth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods of the second aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0096] In a twentieth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods of the third aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0097] In a twentieth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods in the fourth aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0098] In a twentieth aspect, embodiments of this application provide a communication system comprising: a first device, a configuration server, and an enable server. The configuration server is configured to execute the methods described in the first aspect and any possible implementation thereof. The enable server is configured to execute the methods described in the second aspect and any possible implementation thereof. The first device is configured to execute the methods described in the third or fourth aspect.

[0099] The first device can be a terminal or the source EES corresponding to the terminal.

[0100] In a twentieth aspect, embodiments of this application provide a server deployment method, the method comprising: a configuration server determining first time information of at least one application server instantiation corresponding to at least one enabling server, the first time information being used to indicate the remaining time information of application server instantiation; the configuration server receiving a first request message from a terminal device, the first request message being used to instruct the configuration server to obtain information of at least one enabling server, the at least one enabling server including a first enabling server; the configuration server determining the first enabling server based on the remaining time information of application server instantiation and the information of at least one enabling server, the first enabling server being used to provide services to the terminal device.

[0101] In this application, the configuration server first determines the remaining time information for the instantiation of at least one application server corresponding to at least one enabling server, and then receives a first request message from the terminal device to determine the information of at least one enabling server. Since the enabling server corresponds to at least one application server, and the at least one enabling server includes the first enabling server required by the terminal, by combining the application server corresponding to the enabling server and the remaining time information for instantiation, the first enabling server that meets the requirements of the terminal device can be determined. This allows the terminal device to obtain an application server that meets its requirements.

[0102] In one possible implementation, the first-time information is either the remaining duration of application server instantiation or the completion time of application server instantiation.

[0103] In one possible implementation, the first-time information is determined by the start time of application server instantiation and / or the execution duration, as well as the duration corresponding to application server instantiation.

[0104] In one possible implementation, the method provided in this application embodiment includes: a configuration server receiving first indication information from at least one enabling server, the first indication information being used to indicate the execution duration of application server instantiation, or the start time of application server instantiation.

[0105] In one possible implementation, the first indication information is also used to indicate that application server instantiation is in progress. The method provided in this application embodiment further includes: the configuration server determining the moment of application server instantiation based on the first indication information.

[0106] In one possible implementation, the method provided in this application embodiment further includes: a configuration server receiving the duration corresponding to the instantiation of the application server from at least one enabling server. Alternatively, the configuration server pre-configures the duration required for application server instantiation.

[0107] In one possible implementation, the method provided in this application embodiment includes: a configuration server receiving first time information from at least one application server instantiated corresponding to at least one enabling server.

[0108] In one possible implementation, the first request message includes second time information, which indicates the time when the terminal device arrives at the target location.

[0109] In one possible implementation, the method provided in this application includes: a configuration server determining a first enabling server based on at least one of the instantiation status information, first time information, and second time information corresponding to at least one enabling server and at least one application server corresponding to at least one enabling server.

[0110] In one possible implementation, the method provided in this application further includes: a configuration server sending a first response message to a terminal device, the first response message including information about a first enabling server. The information about the first enabling server includes an identifier of the first enabling server and / or the address of the first enabling server.

[0111] In one possible implementation, the method provided in this application embodiment further includes: a configuration server sending a first response message to a terminal device, the first response message including information of at least one enabling server, the information of the enabling server including the identifier of the enabling server and / or the address of the enabling server, first time information of the application server corresponding to the enabling server, and / or, first indication information.

[0112] In one possible implementation, the method provided in this application embodiment further includes: a configuration server obtaining information about multiple platforms corresponding to at least one enabling server.

[0113] In one possible implementation, the enabling server configures its identification information, address information, and information about at least one platform corresponding to the enabling server. The enabling server sends a registration request message to the configuration server, which includes, but is not limited to, the enabling server's identification information, the application server's identification information, the application server's status information, and information about at least one platform.

[0114] Optionally, the method provided in this application embodiment further includes: a configuration server determining the deployment time of the application server on different platforms based on information from at least one platform. The configuration server receives a service configuration request message from a terminal device. Correspondingly, the terminal device sends a configuration service request message to the configuration server. For example, the configuration service request message is a service provisioning request message, which carries the identifier of the application server and second time information. When it is necessary to select an instantiable application server, the configuration server determines the enabling server based on the second time information, information from at least one platform, and the capability information corresponding to the platform.

[0115] Optionally, the method provided in this application embodiment further includes: a configuration server receiving a service configuration request message from a terminal device. Correspondingly, the terminal device sends a configuration service request message to the configuration server. The configuration server sends a service configuration response message to the terminal device. Correspondingly, the terminal device receives a service configuration response message from the configuration server. In the absence of an available application server, the terminal device determines the deployment time of the application server on different platforms based on information from at least one platform, and determines the enabling server based on second time information.

[0116] In a twentieth aspect, embodiments of this application provide a server deployment method, the method comprising: enabling a server to receive a second request message from a terminal device, the second request message being used to obtain information about an application server. The second request message includes identification information of the terminal device and / or application information to be executed. The enabling server sends a second response message to the terminal device, the second response message including information about at least one application server, the application server information including identification information of the application server and / or address information.

[0117] In one possible implementation, the second request message includes second time information, which indicates the time when the terminal device arrives at the target location.

[0118] In one possible implementation, the method provided in this application embodiment includes: enabling the server to determine a first application server based on at least one of instantiation status information, first time information, and second time information corresponding to at least one application server, wherein the first application server completes instantiation before the time when the terminal device arrives at the target location.

[0119] In one possible implementation, the method provided in this application embodiment includes: enabling the server to send a second response message to the terminal device, the second response message including information about a first application server. The information about the first application server includes the application server's identification information and / or address information.

[0120] In one possible implementation, the first-time information is either the remaining duration of application server instantiation or the moment when application server instantiation is completed.

[0121] In one possible implementation, the first-time information is determined by the start time of application server instantiation and / or execution duration, as well as the duration required for application server instantiation.

[0122] In one possible implementation, the method provided in this application embodiment includes: enabling the server to receive second indication information from a first network management system, the second indication information being used to indicate the execution duration of application server instantiation, or the start time of application server instantiation.

[0123] In one possible implementation, the method provided in this application embodiment includes: enabling the server to determine first time information based on second instruction information and the duration required for application server instantiation.

[0124] In one possible implementation, the method provided in this application embodiment further includes: enabling the server to send first time information to the configuration server, wherein the first time information corresponds to the application server.

[0125] In one possible implementation, the method provided in this application embodiment includes: enabling a server to determine first indication information based on second indication information, wherein the first indication information is used to indicate the execution duration of application server instantiation, or the start time of application server instantiation. The enabling server then sends the first indication information to a configuration server.

[0126] In one possible implementation, the method provided in this application embodiment further includes: enabling the server to send a second response message to the terminal device, the second response message including information of at least one application server, the information of the application server including the identification information of the application server, and / or, address information, and first time information corresponding to the application server.

[0127] In one possible implementation, the method provided in this application embodiment further includes: an enabling server receiving a discovery request message from a terminal device. The discovery request message includes identification information of the application server and second time information. When it is necessary to select an instantiable application server, the enabling server determines the platform for deploying the application server based on the second time information, information of at least one platform, and capability information corresponding to the platform. The enabling server sends indication information to a first network management system. The indication information is used to trigger application server instantiation.

[0128] Optionally, the method provided in this application embodiment further includes: enabling the server to directly configure the deployment duration information of the application server.

[0129] In a thirtieth aspect, embodiments of this application provide a server deployment method, the method comprising: a terminal device sending a first request message to a configuration server. The first request message is used to instruct the configuration server to obtain information about at least one enabling server, the information of the at least one enabling server including a first enabling server, the first enabling server being used to provide services to the terminal device.

[0130] In one possible implementation, the first request message includes second time information, which indicates the time when the terminal device arrives at the target location.

[0131] In one possible implementation, the method provided in this application includes: a terminal device receiving a first response message from a configuration server, the first response message including information about a first enabling server. The information about the first enabling server includes an identifier of the first enabling server and / or the address of the first enabling server.

[0132] In one possible implementation, the method provided in this application includes: a terminal device receiving information from a configuration server and at least one enabling server, and / or first time information corresponding to the identifier of at least one application server corresponding to at least one enabling server. The terminal device determines at least one first enabling server based on at least one of the instantiated state information, the first time information, and second time information corresponding to at least one enabling server and at least one application server corresponding to at least one enabling server.

[0133] In a thirty-first aspect, embodiments of this application provide a server deployment method, the method comprising: a terminal device sending a second request message to an enabling server, the second request message being used to obtain information about an application server, the information about the application server including identification information of the terminal device and / or application information.

[0134] In one possible implementation, the second request message includes second time information.

[0135] In one possible implementation, the method provided in this application embodiment includes:

[0136] The terminal device receives a second response message from the enable server. The second response message includes information about the first application server, which includes the identification information and / or address information of the first application server.

[0137] In one possible implementation, the method provided in this application embodiment includes: a terminal device receiving second response information from an enabling server, the second response information including information about at least one application server, the application server information including identification information and / or address information of the application server. The terminal device determines a first application server based on at least one of instantiated status information, first time information, and second time information corresponding to at least one application server.

[0138] Any of the devices, computer storage media, computer program products, chips, or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding solutions in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0139] Figure 1 This is a schematic diagram of the architecture of an edge application system provided in an embodiment of this application;

[0140] Figure 2 This is a schematic diagram of an application context migration process provided in an embodiment of this application;

[0141] Figure 3This is a schematic diagram illustrating a method for instantiating EAS provided in an embodiment of this application;

[0142] Figure 4 This is a schematic diagram of another method for instantiating EAS provided in the embodiments of this application;

[0143] Figure 5 This is a schematic diagram illustrating an application server deployment method provided in an embodiment of this application;

[0144] Figure 6 This is a schematic diagram of another application server deployment method provided in an embodiment of this application;

[0145] Figure 7 This is a flowchart illustrating the implementation of the first EAS deployment method provided in this application embodiment;

[0146] Figure 8 This is a flowchart illustrating the implementation of the second EAS deployment method provided in this application embodiment;

[0147] Figure 9 This is a flowchart illustrating the implementation of the third EAS deployment method provided in this application embodiment;

[0148] Figure 10 This is a flowchart illustrating the implementation of the fourth EAS deployment method provided in this application embodiment;

[0149] Figure 11 This is a flowchart illustrating the implementation of the fifth EAS deployment method provided in this application embodiment;

[0150] Figure 12 This is a flowchart illustrating the implementation of the sixth EAS deployment method provided in this application embodiment;

[0151] Figure 13 This is a flowchart illustrating the implementation of the seventh EAS deployment method provided in this application embodiment;

[0152] Figure 14 This is a flowchart illustrating the implementation of the eighth EAS deployment method provided in this application embodiment;

[0153] Figure 15 This is a schematic diagram of a communication device provided in an embodiment of this application;

[0154] Figure 16 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0155] Figure 17 This is a schematic diagram of a chip structure provided in an embodiment of this application. Detailed Implementation

[0156] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0157] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0158] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0159] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0160] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural.

[0161] The character " / " generally indicates that the preceding and following objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any single or multiple items. For example, "at least one of a, b, or c" can be expressed as: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0162] Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

[0163] The steps involved in the communication method provided in this application embodiment are merely examples. Not all steps are mandatory, nor are all contents of each piece of information or message mandatory. They can be added or removed as needed during use.

[0164] In this application, the same step or a step or message with the same function can be referenced and learned from each other in different embodiments.

[0165] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0166] like Figure 1 As shown, Figure 1 This is a schematic diagram of the architecture of an edge application server deployment system provided in an embodiment of this application. The system includes: a terminal 110, a core network 120, a first data network 130, and a first server 140.

[0167] Terminal 110 runs the application. Core network 120 is used for functions such as call processing, data transmission, and mobility management within the network. First data network 130 is used for data processing and storage. First server 140 is used for configuring first data network 130.

[0168] For example, the first data network 130 can be an edge data network (EDN), which is used to push data processing and storage functions to the edge of the network, that is, closer to the data source or user.

[0169] For example, the first server 140 could be an edge configuration server (ECS), which is responsible for configuring EDN.

[0170] Optional, such as Figure 1 As shown, terminal 110 includes one or more application clients (ACs) and edge enabler clients (EECs). The application client is the peer entity of the edge application on the terminal side. The application client is used by application users to obtain application services from the application server. The application client is a client program on the terminal side; it can connect to the application server in the cloud to obtain application services, or it can connect to EAS deployed and running in one or more EDNs to obtain application services. The edge enabler client is the peer entity of the EES on the terminal side. The EEC is used to register EEC information and application client information with the EES, perform security authentication and authorization, obtain the IP address of the EAS from the EES, and provide edge computing enabling capabilities to the application client, such as the EAS discovery service returning the IP address of the EAS to the application client. The application client and the EEC communicate through edge interface 5. For example, the application client sends the address information of the EAS to the AC.

[0171] The first network 130 includes at least one edge application server (EAS) and at least one edge enabler server (EES). The EAS and EES communicate via edge interface 3. The EES communicate with each other via edge interface 5.

[0172] In this process, application data is transmitted between the edge application server and the terminal through the core network.

[0173] In one embodiment of this application, taking the first data network 130 as an EDN as an example, the application deployed in the EDN is called an application instance, specifically referring to an instance of a server application deployed and running in the EDN, such as social media software, augmented reality (AR), virtual reality (VR), etc. An application can deploy at least one EAS in one or more EDNs, and EAS deployed and running in different EDNs can be considered as different EAS of the same application, which can share a domain name, use a single address, or use different addresses.

[0174] It is worth noting that EES is deployed in EDN. Generally, EAS is registered on an EES, or the information of an EAS is configured on an EES through the management system. This EES is called the EES associated with the EAS. The EES can control or manage the registered or configured EAS on that EES.

[0175] Figure 1 For example, the interface between EES and EEC is EDGE-1, the interface between EES and core network 120 is EDGE-2, the interface between ECS and EEC is EDGE-4, the interface between EES and ECS is EDGE-6, the interface between EAS and core network 120 is EDGE-7, and the interface between ECS and core network 120 is EDGE-8.

[0176] A terminal is a device that allows users to access network services. In the 3GPP standard, the interface between the terminal and the network is a wireless interface.

[0177] Terminals can include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; they can also include subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, machine-type communication (MTC) terminals, user equipment (UE), mobile stations (MS), terminal devices, or relay user equipment, etc. Relay user equipment can be, for example, a 5G residential gateway (RG). For ease of description, the user equipment mentioned above is collectively referred to as a terminal in this application.

[0178] It should be understood that the terminal in the embodiments of this application can also be a terminal in various vertical industry application fields such as Internet of Things terminal devices, ports, smart factories, railway transportation, logistics, drones, and autonomous vehicles. For example, mobile robots, automated guided vehicles (AGVs), autonomous vehicles, control equipment and sensors on trains, and control equipment and sensors deployed in factories.

[0179] In one embodiment of this application, the user enters into a service agreement with the application provider to provide services to the user. The user connects to and communicates with the EAS in the EDN by logging into the AC on the terminal device 110. The EEC is a middleware layer, typically located within the operating system or between the AC and the operating system. The AC can obtain edge enabling services from the EEC via an application programming interface (API).

[0180] Edge computing also involves application context migration, which typically refers to migrating a running application or service from one compute node to another while maintaining service continuity and state consistency. Based on... Figure 1 The architecture shown illustrates the application context migration process as follows: Figure 2 As shown, it specifically includes:

[0181] Step 1: Detection of application context transitions.

[0182] As an example, the detection entity may determine that context transition is necessary. For instance, the terminal device's location may change, or the user plane path of the terminal device may be updated.

[0183] Step 2: Decision-making regarding application context transition.

[0184] As an example, the decision entity determines that context transfer is needed based on the detection results of the detection entity.

[0185] Step 3: Execution of application context migration.

[0186] As an example, the execution entity transfers the application's context from the source EAS to the target EAS.

[0187] Optionally, the execution entity is also used to notify the terminal device of the target EAS information, and to notify the network device of the completion of context migration and related information about the target EAS.

[0188] For example, the address information of the target EAS, the routing information corresponding to the target EAS, etc.

[0189] It is worth noting that, in the specific implementation, the detection entity, decision-making entity, and execution entity can be the same entity or different entities, and no limitation is made here.

[0190] Step 4: Cleanup work after application context migration.

[0191] For example, the application client initiates a new socket connection to the target EAS.

[0192] In existing technologies, current standards define the discovery processes for EES and EAS, primarily employing a two-level discovery mechanism: first, EES is discovered, and then EAS is discovered from within EES. The specific process is as follows:

[0193] The first step is for the EEC to discover the EES platform from the ECS, which specifically includes:

[0194] Step 1: The EEC requests / subscribes to the EES corresponding to the location of the terminal device from the ECS.

[0195] Step 2: The EEC receives an EES or EDN from the ECS that meets the EEC's conditions.

[0196] Step 3: The ECS determines the EES that meets the requirements based on the information from the EAS and the EES.

[0197] For example, ECS selects a suitable EES for each application based on EAS information, data network access identifier (DNAI), fully qualified domain name (FQDN), and EES configuration information.

[0198] Step 4: Obtain the DNAI of EES from EEC.

[0199] Step 5: The ECS sends one or more EES messages to the EEC.

[0200] The second step involves the EEC discovering the EAS from the EES, specifically including:

[0201] Step 1: The EEC sends the information of the EAS that needs to be accessed to the EES.

[0202] Step 2: EES matches the information of the registered EAS with the information of the EAS it needs to access.

[0203] For example, EES matches EAS that meet the user's request based on information from locally registered or online EASs, as well as discovery filtering parameters provided by the user. There can be multiple EASs.

[0204] Step 3: EES returns EAS information to EEC.

[0205] As an example, EEC can provide EAS information to application clients so that they can connect to EAS.

[0206] In some related technologies, EAS can be dynamically instantiated. That is, when a terminal device requests an available EAS, and no EAS is available on the EES / EDN, the EES can trigger EAS instantiation from the Edge Computing Service Provider Management System (ECSP MnS) based on the terminal device's needs. Specific implementation methods are as follows... Figure 3 As shown, Figure 3 A method for instantiating EAS provided in this application embodiment includes:

[0207] Step 1: The ASP sends a first request message to the ECSP. Correspondingly, the ECSP receives the first request message from the ASP.

[0208] The first request message is used to request the creation of an MOI for the EAS requirement IOC during the EAS deployment process.

[0209] Step 2: The ECSP sends a first response message to the ASP. Correspondingly, the ASP receives the first response message from the ECSP.

[0210] The first response message is used to indicate that EAS deployment is in progress.

[0211] Step 3: ECSP analyzes the requirements and determines the operation for EAS VNF instantiation.

[0212] Step 4: ECSP sends a second request message to ETSI NFV MANO NFVO. Correspondingly, ETSI NFV MANO NFVO receives the second request message from ECSP.

[0213] The second request message is used to request the instantiation of EAS VNF.

[0214] Step 5: The ETSI NFV MANO NFVO sends a first notification message to the ECSP. Correspondingly, the ECSP receives the first notification message from the ETSI NFV MANO NFVO.

[0215] The first notification message is used to indicate the result of EAS instantiation.

[0216] Step 6: If instantiation is successful, ECSP creates the EAS function IOC.

[0217] Step 7a: Create an MOI for the EAS requirement IOC.

[0218] Step 7b: The ECSP sends a second notification message to the ASP. Correspondingly, the ASP receives the second notification message from the ECSP.

[0219] The second notification message is used to indicate that the EAS Requirement MOI and EAS Function MOI have been created.

[0220] Step 7c: In the event of instantiation failure, the ECSP sends a third notification message to the ASP. Correspondingly, the ASP receives the third notification message from the ECSP.

[0221] The third notification message is used to indicate that the creation of the EAS requirement MOI failed.

[0222] In other related technologies, to ensure service continuity planning, application context migration can be performed in advance when it is predicted that the terminal device will move to a predicted location within a certain period of time. That is, before the terminal device moves to the predicted location, the EES and EAS are discovered in advance, and the application context is migrated from the initial EAS to the target EAS. This way, when the terminal device moves to the predicted location, it can directly connect to the target EAS, thereby reducing service interruption time.

[0223] like Figure 4 The above, Figure 4 Another method for instantiating EAS provided in the embodiments of this application includes:

[0224] Step 1: The EES maintains a list of EAS that can be instantiated, and the ECS and the target EES obtain the instantiation time information of the EAS.

[0225] Step 2: The target EES sends a first request message to the ECS. Correspondingly, the ECS receives the first request message from the target EES.

[0226] For example, the first request message is an EES registration request message, which carries the EAS instantiation status and the time required for the corresponding EAS instantiation.

[0227] Optionally, in step 3, the initial EAS sends a discovery request message to the initial EES. Correspondingly, the initial EES receives the discovery request message from the initial EAS.

[0228] For example, the discovery request message is an EAS discovery procedure message, which carries the Edge Application Server Discovery Filter (EAS discovery filter), the UEID (User Equipment ID), and the ACID (Application Client ID).

[0229] Optionally, the EAS discovery procedure message can also carry service continuity planning indication information and prediction expiration time. Prediction expiration time describes the estimated latest time that the terminal device may arrive at the predicted / expected location or EAS service area, and is used for the ACR type of service continuity planning.

[0230] Step 4: The initial EES sends a second request message to the ECS. Correspondingly, the ECS receives the second request message from the initial EES.

[0231] For example, the second request message is a retrieve T-EES request message, which carries the EAS discovery filter, UEID, ACID, service continuity planning indication, and prediction expiration time.

[0232] Step 5: Based on the service continuity planning indication, prediction expiration time, and the corresponding time information of EAS, ECS determines whether it can select the EES corresponding to the EAS that can be instantiated but has not yet been instantiated.

[0233] For example, if the prediction expiration time is less than the time required for EAS instantiation, instantiating the EAS will further increase the ACR latency, thereby leading to a further increase in service interruption latency or poor service performance. In this case, an already instantiated EAS should be selected.

[0234] Step 6: The ECS sends a first response message to the initial EES. Correspondingly, the initial EES receives the first response message from the ECS.

[0235] For example, the first response message is a retrieve T-EES response message, which carries information about the target EES (T-EES information), including: EAS instantiation information, the identifier of the target EES (T-EES ID), and EES endpoint information.

[0236] EAS instantiation information can be EAS instantiation (status) information, such as EAS being instantiated, or EAS being instantiable but not yet instantiated.

[0237] Step 7: The initial EES sends a third request message to the target EES. Correspondingly, the target EES receives the third request message from the initial EES.

[0238] For example, the third request message is an EAS discovery request message, which carries the EAS discovery filter, service continuity planning indication, and prediction expiration time.

[0239] Step 8: The target EES determines whether to select an EAS that can be instantiated but has not yet been instantiated based on the prediction expiration time.

[0240] For example, the target EES determines whether to select an EAS that can be instantiated but has not yet been instantiated, based on the received service continuity planning indication, prediction expiration time, and the EAS's corresponding time information. If necessary, it triggers EAS instantiation.

[0241] Step 9: The target EES sends a second response message to the initial EES. Correspondingly, the initial EES receives the second response message from the target EES.

[0242] For example, the second response message is an EAS discovery response message, which carries information about the target EAS (T-EAS information). This target EAS information can be an EAS profile, which includes the EAS ID and EAS endpoint. Once the EAS is instantiated, the target EES can send the instantiated EAS information to the initial EES.

[0243] Step 10: The initial EES sends a third response message to the initial EAS. Correspondingly, the initial EAS receives the third response message from the initial EES.

[0244] For example, the third response message is the EAS discovery response message.

[0245] It is worth noting that in this embodiment, the initial EAS can be replaced with AC, and the initial EES can be replaced with EEC.

[0246] However, in existing technologies, the maximum time required for EAS instantiation is directly configured on ECS and EES. But different EAS deployment times vary across different platforms, making it inaccurate to select EES or EAS based solely on this maximum instantiation time. Therefore, determining the appropriate EAS to meet the requirements during service continuity planning, ensuring EAS instantiation is completed before the terminal device moves to the predicted location, is a critical issue that needs to be addressed.

[0247] Based on this, embodiments of this application provide a server deployment method, in which the ECS or EEC determines whether to select an EES corresponding to an already instantiated EAS or an EES in the process of instantiating an EAS, based on the instantiation completion time of the corresponding EAS on the EES and the time when the terminal device moves to the target location.

[0248] In this application embodiment, the specific structure of the execution entity of a server deployment method is not particularly limited, as long as communication can be performed according to the server deployment method by running a program that records the code of the server deployment method of this application embodiment. For example, the execution entity of the server deployment method provided in this application embodiment can be a functional module in a terminal device that can call and execute a program, or a communication device applied in a terminal device, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be located inside the terminal device or can be independent of the terminal device, and this application embodiment does not impose any restrictions. For example, the execution entity of the server deployment method provided in this application embodiment can be a functional module in a configuration server that can call and execute a program, or a communication device applied in a configuration server, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be located inside the configuration server or can be independent of the configuration server, and this application embodiment does not impose any restrictions. For example, the execution entity of a server deployment method provided in this application embodiment can be a functional module in the enabling server that can call and execute programs, or a communication device applied in the enabling server, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be located inside the enabling server or can be independent of the enabling server; this application embodiment does not impose any restrictions.

[0249] The following describes an embodiment of a server deployment method. Where there is no conflict, the following embodiments can be combined.

[0250] In one possible embodiment of this application, the configuration server determines the instantiation time information of at least one application server corresponding to at least one enabling server. This can be done by the enabling server sending the instantiation time information of at least one application server to the configuration server, or by the configuration server determining the instantiation time information of at least one application server based on the indication information.

[0251] The instantiation time information refers to the remaining time for the application server to instantiate itself. For example, it could be the remaining duration of application server instantiation or the instantiation completion time.

[0252] For example, application server 1 has started instantiation and will take another 10 minutes (min) to complete instantiation, or it will complete instantiation at 10:30.

[0253] One of the enabling servers can register at least one application server; or, the information of at least one application server can be configured on the enabling server, for example, through a network management system.

[0254] For example, Application Server 1 (EAS#1) is registered on Enable Server 1 (EES#1); or, the information of Application Server 1 (EAS#1) is configured on Enable Server 1 (EES#1). It can be understood that Enable Server 1 (EES#1) is the enable server associated with Application Server 1 (EAS#1). Furthermore, Enable Server 1 (EES#1) can control or manage the Application Server (EAS#1) registered or configured on Enable Server (EES#1).

[0255] In one possible implementation of this application, the instantiation time information is determined by the start time and / or execution duration of the application server instantiation, as well as the time information corresponding to the application server instantiation.

[0256] The start time of application server instantiation refers to the moment when the application server begins to execute the instantiation process.

[0257] The execution time of application server instantiation represents the total time that the application server has been running.

[0258] The time information corresponding to application server instantiation indicates the total / full / overall duration of application server instantiation. For example, it represents the total time required for the application server to complete instantiation from the start of instantiation.

[0259] For example, if the instantiation start time of application server 1 (EAS#1) is 10:00, and the instantiation time information of application server 1 (EAS#1) is 30 minutes, then the instantiation time information of application server 1 (EAS#1) is the instantiation completion time of 10:30.

[0260] For example, if the execution time of instantiating application server 1 (EAS#1) is known to be 15 minutes, and the time information corresponding to the instantiation of application server 1 (EAS#1) is 30 minutes in total, then the instantiation time information of application server 1 (EAS#1) is the remaining time of instantiation 15 minutes.

[0261] Case 1: The application server instantiation time information is determined by the enabling server.

[0262] In one possible embodiment of this application, the enabling server determines the instantiation time information of the application server, specifically through the following methods:

[0263] Step 1: Enable the server to receive instruction information from the first network management system. The instruction information is used to indicate the start time and / or execution duration of the application server instantiation.

[0264] In one possible implementation, the first network management system sends an instruction message to the enabling server.

[0265] For example, the indication information could be an EAS instantiation in progress message corresponding to the application server, indicating that the application server instantiation is in progress.

[0266] Optionally, the indication information may include the start time of application server instantiation and / or the execution duration of application server instantiation.

[0267] In one possible implementation, the enabling server can determine the start time of application server instantiation and / or the execution duration of application server instantiation based on the received EASinstantiation inprogress message.

[0268] Optionally, when the first network management system sends the EASinstantiationinprogress message to the enabling server, the message may also carry the completion time corresponding to the instantiation of the application server.

[0269] In one possible implementation, the enabling server can determine the completion time of application server instantiation based on the received EAS instantiation in progress message. Specifically, the completion time of the application server is determined based on the time when the EAS instantiation in progress message is received and the time information required for application server instantiation.

[0270] Step 2: Enable the server to determine the instantiation time information of the application server based on the instruction information and the time required for the application server to be instantiated.

[0271] The time required for application server instantiation can be configured by the enabling server. The instantiation time for each application server may be the same or different.

[0272] For example, application server 1 is identified by EAS ID#1 and its instantiation time is 10 minutes (min), while application server 2 is identified by EAS ID#2 and its instantiation time is 30 minutes (min).

[0273] Optionally, the same application server can be instantiated at different times.

[0274] For example, if application A requires high key performance indicators (KPIs) from application server A, then application server A will take longer to instantiate. For instance, a higher KPI means application A needs more resources (such as graphics processing units and memory processing units), thus increasing instantiation time (e.g., 30 minutes). Conversely, if application A requires low KPIs from application server A, then application server A will take shorter to instantiate. For instance, a lower KPI means application A needs fewer resources (such as graphics processing units and memory processing units), thus increasing instantiation time (e.g., 15 minutes).

[0275] In one possible implementation, the indication information carries the start time of application server instantiation and / or execution duration, enabling the server to determine the application server instantiation time information in combination with the time required for application server instantiation.

[0276] The enabling server can obtain the execution duration based on the start time of application server instantiation, and similarly, the start time can also be obtained based on the execution duration of application server instantiation.

[0277] For example, if the enabling server receives the start time of application server 1 (EAS#1) instantiation at 10:00 and the time of receiving the indication information is 10:15, it can be concluded that the instantiation has been running for 15 minutes. Combined with the enabling server's configuration that the instantiation of application server 1 (EAS#1) requires 30 minutes, it can be determined that the instantiation time information of application server 1 (EAS#1) is either 15 minutes remaining or 10:30.

[0278] For example, if the enabling server receives an instruction from the application server 1 (EAS#1) that the instantiation execution time is 15 minutes and the instantiation start time is 10:15, we can conclude that the instantiation started 15 minutes ago, which is 10:00. Combining this with the enabling server's configuration that the instantiation of application server 1 (EAS#1) requires 30 minutes, we can determine that the instantiation time information of application server 1 (EAS#1) is either 15 minutes remaining or 10:30.

[0279] In another possible implementation, the instruction information carries the completion time corresponding to the instantiation of the application server. The enabling server determines the instantiation time information of the application server based on the instruction information, that is, the remaining duration of the application server instantiation or the completion time of the application server instantiation.

[0280] For example, if the enabling server receives an instruction message that indicates the completion time of the application server instantiation is 10:30 and the instruction message was received at 10:15, then the remaining time for the application server instantiation is 15 minutes.

[0281] In another possible implementation, the enabling server can determine the start time of application server instantiation based on the received EAS instantiationin progress message, and further determine the completion time of application server instantiation or the remaining time information of application server instantiation. Specifically, the instantiation time information of the application server is determined based on the time of receiving the EAS instantiationin progress message and the time information corresponding to application server instantiation.

[0282] Optionally, the method provided in this application embodiment further includes: Step 3, enabling the server to send the instantiation time information of the application server to the configuration server. Correspondingly, the configuration server receives the instantiation time information of the application server from the enabling server.

[0283] In one possible implementation, the enabling server sends a registration request message, such as an EES registration request message, to the configuration server. This message includes application server instantiation time information, such as the completion time of application server instantiation.

[0284] Scenario 2: The instantiation time information of the application server is determined by the configuration server.

[0285] In one possible embodiment of this application, the configuration server determines the instantiation time information of the application server, specifically by means of:

[0286] Step 1: Configure the server to receive instruction information. This instruction information indicates the start time of application server instantiation and / or the execution duration.

[0287] In one possible implementation, the enabling server sends instruction information to the configuration server.

[0288] For example, the indication information could be an EAS instantiation in progress message corresponding to the application server, indicating that the application server instantiation is in progress.

[0289] Optionally, the indication information may include the start time of application server instantiation and / or the execution duration of application server instantiation.

[0290] In one possible implementation, the configuration server can determine the start time of application server instantiation and / or the execution duration of application server instantiation based on the received EAS instantiation inprogress message.

[0291] Optionally, when the enabling server sends an EAS instantiation in progress message to the configuration server, the message may also carry the completion time corresponding to the application server instantiation and / or the remaining duration corresponding to the application server instantiation.

[0292] In another possible implementation, the configuration server can determine the start time of application server instantiation based on the received EAS instantiationin progress message, and further determine the completion time of application server instantiation or the remaining time information of application server instantiation. Specifically, the instantiation time information of the application server is determined based on the time of receiving the EAS instantiationin progress message and the time information corresponding to application server instantiation.

[0293] Optionally, in another possible implementation, the first network management system sends instruction information to the configuration server. The configuration server determines the instantiation time information of the application server based on the instruction information and the duration required for application server instantiation.

[0294] The difference between Case 1 and Case 2, where the enabling server determines the instantiation time information of the application server, is that the time required for application server instantiation is configured by the configuration server.

[0295] For specific implementation details, please refer to the implementation example of enabling the server to determine the instantiation time information of the application server, which will not be repeated here.

[0296] In one possible embodiment of this application, the configuration server or terminal can determine at least one enabling server based on information about the instantiation of at least one application server, first time information about the instantiation of at least one application server, and second time information. The enabling server deploys the application server that provides services to the terminal device.

[0297] The information instantiated in at least one application server includes the application server instantiation status information corresponding to the identifier of each application server. The application server instantiation status information is used to indicate the instantiation status of the application server.

[0298] For example, the status information of application server instantiation can include the following: instantiation completed, instantiation can be performed but has not started, and instantiation is in progress.

[0299] The second time information is used to indicate the time when the terminal device arrives at the target location.

[0300] For example, the enabling server obtains the expected location information of the terminal device based on the information provided by the terminal device and the core network functions. The information provided by the terminal device may include the AC schedule, the expected AC geographical service area, the expected AC service KPIs, and the preferred ESCP list. Optionally, the expected location information of the terminal device may also include the corresponding time information.

[0301] It's worth noting that in business continuity planning, the application context may be copied and sent from the initial application server to the target application server before the terminal device moves to its intended location. In this case, the business context in the initial application server is transferred to the target application server and continuously updated until the application client on the terminal device establishes a connection with the target application server. Once the terminal device has moved to its intended location, the application client on the terminal device can disconnect from the initial application server and connect directly to the target application server.

[0302] Scenario 1: The configuration server determines at least one enabling server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information.

[0303] In one possible implementation, the method includes:

[0304] Step 1: Configure the server to receive the first request message. The first request message is used to request the discovery enable server.

[0305] For example, the terminal device sends a first request message to the configuration server.

[0306] The first request message includes the application server's identifier and the second time information.

[0307] Optionally, the first request message may also include at least one of the following: the identifier of the terminal device, the location information of the terminal device, and application information. The application information includes an access controller (AC) profile, which includes the AC identifier, the service key performance indicators (KPIs) required by the AC, and the identifier of at least one corresponding application server (e.g., a list of EAS IDs).

[0308] For example, the first request message includes at least one of expected expired time and predicted expiration time, which indicates the estimated time at which the terminal device can arrive at the predicted / expected terminal device location or application server service area at the latest. Expected expired time focuses on indicating the expected end time, for example, the expected time for the terminal device to arrive at location 1 is 10:30; predicted expiration time focuses on indicating the expected duration, for example, the expected duration for the terminal device to arrive at location 1 is 30 minutes.

[0309] In one possible implementation, the first request message can be either a serviceprovisioningrequest message or an EESdiscoveryrequest message. The specific message carried is not limited in this embodiment.

[0310] Step 2: Configure the server to determine at least one enabled server.

[0311] The configuration server can determine at least one enabling server based on the instantiation status information, first time information, and second time information of at least one application server corresponding to at least one enabling server. The application server deployed on at least one enabling server can be instantiated before the terminal device reaches the target location; the configuration server can also directly determine at least one enabling server without filtering. The following explains both scenarios:

[0312] Case 1) The configuration server determines the first enabling server based on at least one of the instantiation status information, first time information, and second time information of at least one enabling server corresponding to at least one application server.

[0313] In one possible implementation, the application servers corresponding to the application server identifier in the first request message are all in the process of instantiation. The configuration server determines the first enabling server based on the first time information and the second time information of the application server instantiation.

[0314] As an example, the configuration server can determine the first enabling server based on the remaining duration of the application server instantiation, combined with the second time information.

[0315] For example, taking the remaining time for application server instantiation as the first information, the remaining time for application server 1 corresponding to enabling server 1 to be instantiated is 15 minutes, and the remaining time for application server 2 corresponding to enabling server 2 to be instantiated is 5 minutes. The terminal device is expected to arrive at location 1 after 5 minutes. Based on this, the configuration server determines that application server 2 corresponding to enabling server 2 can complete instantiation when the terminal device arrives at the target location, and therefore determines enabling server 2 as the first enabling server.

[0316] As an example, the configuration server can determine the first enabling server based on the completion time of application server instantiation, combined with second time information.

[0317] For example, taking the completion time of application server instantiation as the first time information, the completion time of application server 1 instantiation corresponding to enabling server 1 is 10:30, and the completion time of application server 2 instantiation corresponding to enabling server 2 is 10:15. The terminal device is expected to arrive at location 1 at 10:15. Based on this, the configuration server determines that application server 2 corresponding to enabling server 2 can complete instantiation when the terminal device arrives at the target location, and therefore determines enabling server 2 as the first enabling server.

[0318] In another possible implementation, if the application server identifier in the first request message corresponds to different instantiation status information of the application server, then the configuration server determines the first enabling server based on the instantiation status information of the application server, the first time information, and the second time information.

[0319] As an example, the configuration server can determine the first enabling server based on the status of each application server.

[0320] For example, application server 1, corresponding to enabled server 1, has been instantiated, while application server 2, corresponding to enabled server 2, is currently being instantiated. Because application server 1 has poor service quality, the configuration server determines that enabled server 2 is the first enabled server.

[0321] As an example, the configuration server can determine the first enabling server based on the status of each application server and the remaining duration or completion time of the instantiation, combined with second time information.

[0322] For example, application server 1, corresponding to enabling server 1, requires 10 minutes to instantiate but has not yet started execution. Application server 2, corresponding to enabling server 2, requires 30 minutes to complete instantiation, and its instantiation was triggered 15 minutes ago, meaning application server 2 has 15 minutes remaining for instantiation. The terminal device arrives at location 1 after 10 minutes. Based on this, since application server 1, although not yet instantiated, only requires 10 minutes to complete instantiation, while application server 2, although already instantiated, still requires 15 minutes to complete instantiation, the configuration server determines enabling server 2 as the first enabling server.

[0323] For example, application server 1 corresponding to enable server 1 has been instantiated, application server 2 corresponding to enable server 2 is currently being instantiated, and application server 3 corresponding to enable server 3 has not yet started instantiating. Application server 2 instantiation takes 30 minutes and was triggered 15 minutes ago; application server 3 instantiation takes 20 minutes. The terminal device is expected to arrive at location 1 in 15 minutes. The configuration server first determines whether the service quality of application server 1 meets the requirements. If the service quality of application server 1 is poor, then enable server 2 is determined as the first enabled server; if the service quality of application server 1 meets the requirements, then enable server 1 is determined as the first enabled server.

[0324] Case 2) Configure the server to directly determine at least one enabling server.

[0325] In this process, the configuration server is not screened, or the configuration server determines at least one enabling server as a candidate enabling server based on existing technology.

[0326] Step 3: The configuration server sends a first response message to the first device. Correspondingly, the first device receives the first response message from the configuration server.

[0327] In one possible implementation, if the configuration server determines a first enabling server, then the first response message includes information about the first enabling server and / or the identifier of the application server corresponding to the first enabling server. The information about the first enabling server includes its identifier and / or its address.

[0328] For example, the configuration server sends at least one of the following to the first device: the address information (EES address) of the first enabling server, the identification information of the first enabling server, and the identification (EAS ID) of the application server corresponding to the first enabling server.

[0329] In another possible implementation, if the configuration server determines at least one enabling server, the first response message includes at least one of the following: information about the first enabling server, an identifier of the application server corresponding to the first enabling server, and first time information corresponding to the identifier of the application server. The information about the first enabling server includes the identifier information of the first enabling server and / or the address information of the first enabling server. The first time information corresponding to the identifier of the application server is used by the first device to determine the first enabling server.

[0330] Scenario 2: The terminal device determines at least one enabling server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information.

[0331] In one possible implementation, the method includes:

[0332] Step 1: The first device sends a first request message to the configuration server. Correspondingly, the configuration server receives the first request message from the first device.

[0333] The first request message includes the application server's identifier and the second time information.

[0334] For the specific implementation method, please refer to the implementation method of step 1 in the configuration server determining at least one enabling server in the above embodiment, which will not be repeated here.

[0335] Step 2: The first device receives the first response message from the configuration server.

[0336] The first response message includes at least one of the following: information about at least one enabling server, an identifier of the application server corresponding to the enabling server, and first-time information corresponding to the identifier of the application server. The enabling server information includes the identifier of the enabling server and / or the address information of the enabling server. The first-time information corresponding to the identifier of the application server is used by the terminal device to determine the first enabling server.

[0337] In one possible implementation, the first response message is a serviceprovisioningrequest message, which includes an EAS instantiation in progress message corresponding to the identifier (EAS ID) of the application server corresponding to at least one enabling server address (list of EES address), and the first time information of the application server instantiation.

[0338] Step 3: The first device determines at least one enabling server based on the first time information and the second time information instantiated by the application server.

[0339] The implementation method of the first device determining at least one enabling server is the same as step 2 in the configuration server determining at least one enabling server in the above embodiment, and will not be repeated here.

[0340] In one possible embodiment of this application, after the enabling server determines the first time information of the application server instantiation, the method further includes: the enabling server or the terminal device determining a first application server based on at least one application server instantiation information, the first time information of the application server instantiation, and the second time information. The first application server is used to provide services to the terminal device.

[0341] Case 1: The enabling server determines the first application server based on the application server's instantiation status information, the first time information of the application server's instantiation, and the second time information.

[0342] In one possible implementation, the method includes:

[0343] Step 1: Enable the server to receive a second request message from the first device. The second request message is used to obtain information about the application server.

[0344] For example, the first device sends a second request message to the enabling server.

[0345] The second request message includes at least one of the following: terminal identification information, terminal location information, and application information. The application information includes an AC profile, which contains the AC identifier, the service KPIs required by the AC, and a list of EAS IDs.

[0346] In one possible implementation, the second request message can be either a serviceprovisioningrequest message or an EESdiscoveryrequest message. The specific message carried is not limited in this embodiment.

[0347] The second request message includes second time information, which indicates the time when the terminal device arrives at the target location.

[0348] For example, the first request message includes at least one of expected expired time and predicted expiration time, used to indicate the estimated time at which the terminal device can arrive at the predicted / expected terminal device location or application server service area at the latest. A specific example is given in step 1 of the embodiment described above, where the configuration server determines at least one enabling server based on the application server's instantiation status information, the first time information of the application server's instantiation, and the second time information; these steps will not be repeated here.

[0349] Step 2: The enabling server determines the first application server based on the instantiation status information, first time information, and second time information corresponding to at least one application server.

[0350] A specific example is similar to step 2 (case 1) in the embodiment described above, where the configuration server determines at least one enabling server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information. The difference is that in this embodiment, the enabling server determines the first application server, while in the above embodiment, the configuration server determines the first enabling server.

[0351] Step 3: The enabling server sends a second response message to the terminal device. Correspondingly, the terminal device receives the second response message from the enabling server.

[0352] The second response information includes application server information. This application server information includes the application server's identification information and / or its address information.

[0353] For example, the second response information is an EAS discovery response message, which includes the application server's address information, such as the EAS address.

[0354] Scenario 2: The first device determines the first application server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information.

[0355] In one possible implementation, the method includes:

[0356] Step 1: The first device sends a second request message to the first enabling server. Correspondingly, the first enabling server receives the second request message from the first device. The second request message is used to discover the first application server.

[0357] The specific implementation method is the same as step 1 in the above-mentioned first enabling server determining the first application server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information, and will not be repeated here.

[0358] Step 2: The first device receives a second response message from the first enabling server. The second response message is used to indicate information from the first application server.

[0359] For example, the first enabling server sends a second response message to the first device.

[0360] The second response information includes the identifier of the application server corresponding to the address of the first application server, the status information of the application server corresponding to the identifier of the application server, and the first time information of the application server instantiation.

[0361] Step 3: The first device determines the first application server from one or more application servers based on the instantiation time information of one or more application servers provided by the first enabling server, the second time information, and the instantiation status information of one or more application servers.

[0362] The specific implementation of the terminal determining the first application server refers to case 1) of step 2 in the above-mentioned configuration server determining at least one enabling server based on the instantiation status information of the first application server, the instantiation time information of the application server, and the second time information. The difference is that in this embodiment, the first application server is determined by the first device, while in the above embodiment, the first enabling server is determined by the configuration server.

[0363] Step 4: The first device sends information about the first application server to the first enabling server. Correspondingly, the first enabling server receives information about the first application server from the terminal device.

[0364] The information of the first application server includes the identification information of the first application server and / or the address information of the first application server.

[0365] For example, the first device sends an EAS information provisioning procedure to the enabling server, which includes information about the first application server, such as the EAS address.

[0366] In this application, the configuration server and the enabling server first determine the application server instantiation time information, namely the remaining duration of application server instantiation or the completion time of application server instantiation. The configuration server or terminal device then determines at least one enabling server based on the application server instantiation time information and a second time information, namely the expected time information for the terminal device to reach the target location; the enabling server or terminal device then determines the application server that provides services to the terminal device based on the application server instantiation time information and the second time information.

[0367] like Figure 5 As shown, Figure 5 This application illustrates a method for deploying an application server, comprising:

[0368] Step 501: Configure the server to obtain the first-time information of the instantiation of at least one application server corresponding to at least one enabling server.

[0369] The first-time information can be determined by the configuration server, or it can be determined by the enable server and then sent to the configuration server.

[0370] For the specific implementation method, please refer to the implementation method of the configuration server determining the first time information of at least one application server instantiation corresponding to at least one enabling server in the above embodiment, which will not be repeated here.

[0371] Step 502: The first device sends a first request message to the configuration server, and correspondingly, the first device receives the first request message from the first device.

[0372] For example, the first device can be a terminal or a source enabling server. The source enabling server is the enabling server associated with the first application server that provides services to the terminal at its current location. For instance, the first request message includes a first identifier and second time information, where the second time information indicates the time the terminal arrived at the target location. The first request message requests to find the enabling server associated with the first application server identified by the first identifier. Alternatively, the first request message requests to find the enabling server associated with the first application server identified by the first identifier that was instantiated before the time indicated by the second time information. The first application server is the application server that provides services to the terminal when it is at the target location.

[0373] Step 503a: The configuration server determines at least one enabled server or a first enabled server based on at least one of the instantiation status information, instantiation time information, and second time information of at least one enabled server corresponding to at least one application server.

[0374] Specifically, at least one enabling server or the first application server associated with the first enabling server completes instantiation before the terminal reaches the target location. It is understood that the first application server associated with at least one enabling server or the first enabling server can be an application server that has already been instantiated, or an application server that is being instantiated, but this application server can complete instantiation before the terminal reaches the target location.

[0375] The instantiation status information of an application server can refer to whether the application server has been instantiated, is being instantiated, or is an EAS that can be instantiated but has not yet been instantiated.

[0376] The specific implementation method refers to the implementation method of steps 1 to 3 of the above embodiment where the configuration server determines at least one enabling server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information, and will not be repeated here.

[0377] It is worth noting that if the configuration server determines the information of the first enabling server in step 503a, then step 504a is executed. If the configuration server determines the information of at least one enabling server in step 503a, then step 503b is executed.

[0378] It is worth noting that at least one enabling server can be all or some of one or more enabling servers. One or more enabling servers are the enabling servers associated with the configuration server. The configuration server may not have secondary time information when determining at least one enabling server.

[0379] Step 504a: The configuration server sends a first response message to the first device. Correspondingly, the first device receives the first response message from the configuration server.

[0380] The first response message includes information about the first enabling server. This information includes the identifier and / or address of the first enabling server. The first application server associated with the first enabling server is an enabling server instantiated before the terminal reaches the target location.

[0381] Step 503b: The configuration server sends information about at least one enabling server to the first device. Correspondingly, the first device receives information about at least one enabling server from the configuration server.

[0382] The enabling server information includes the identifier of the application server corresponding to the enabling server, the status information of the application server corresponding to the identifier of the application server, and the first time information of the application server instantiation.

[0383] Step 504b: The first device determines the first enabling server based on at least one of the instantiation status information, instantiation time information, and second time information corresponding to at least one application server associated with at least one enabling server.

[0384] The specific implementation method refers to the implementation method of steps 1 to 3 of the above embodiment where the terminal device determines at least one enabling server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information, and will not be repeated here.

[0385] In this embodiment of the application, after the configuration server or the first device determines the first enabling server, the first enabling server or the first device can determine the first application server based on the instantiation time information of the application server instantiation and the second time information. For example... Figure 6 As shown, the specific methods include:

[0386] Step 601: The first enabling server receives a second request message from the first device, the second request message requesting the first enabling server to discover the first application server associated with the first identifier.

[0387] The second request message includes second time information and a first identifier. The second time information indicates the time when the terminal arrives at the target location. Specifically, the second request message requests the first enabling server to discover the first application server that was instantiated before the first terminal arrived at the target location.

[0388] In one possible implementation of this application, after the first enabling server receives a second request message from the first device, the method includes:

[0389] Step 602a: The first enabling server determines the first application server from one or more application servers based on the instantiation status information, instantiation time information, and second time information of one or more application servers associated with the first enabling server.

[0390] The first application server is instantiated before the terminal reaches the target location.

[0391] The specific implementation method refers to the implementation method of steps 1 to 3 of the above embodiment where the enabling server determines the first application server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information, and will not be repeated here.

[0392] Step 603a: The first enabling server sends a second response message to the first device. Correspondingly, the first device receives the second response message from the first enabling server.

[0393] The second response information includes information about the first application server. This information includes the first application server's identification information and / or its address information.

[0394] In another possible implementation of this application, after the first enabling server receives a second request message from the first device, the method includes:

[0395] Step 602b: The first enabling server sends a third response message to the first device. Correspondingly, the first device receives the third response message from the first enabling server.

[0396] The third response information includes information about at least one application server, its instantiation status information, and its instantiation time information. The at least one application server can be all or some of the one or more application servers. For example, the first enabling server can provide the first device with the instantiation status information of one or more application servers and the instantiation time information of at least one application server, based on the second request message, or select at least one application server from the one or more application servers and then provide the instantiation status information and instantiation time information of at least one application server. For example, the at least one application server can be one or more application servers that can be instantiated before the terminal reaches the target location.

[0397] Step 603b: The first device determines the first application server based on the instantiation status information, instantiation time information, and second time information of at least one application server. The first application server completes instantiation before the time when the terminal arrives at the target location.

[0398] The specific implementation method refers to the implementation method of steps 1 to 4 of the above embodiment where the terminal determines the first application server based on the instantiation status information of the application server, the first time information of the application server instantiation, and the second time information, which will not be repeated here.

[0399] Step 604b: The terminal device sends information about the first application server to the enabling server. Correspondingly, the enabling server receives the information about the first application server from the terminal device.

[0400] The information of the first application server includes the identification information of the first application server and / or the address information of the first application server.

[0401] The following is combined Figure 5 and Figure 6 The application server deployment method shown illustrates a specific implementation of a server deployment method provided in this application embodiment. Specifically, it is used as an example where the configuration server is an edge configuration server (ECS), the enabling server is an edge enabling server (EES), the application server is an edge application server (EAS), and the terminal device is an edge enabling client (EEC).

[0402] like Figure 7 As shown, Figure 7 A specific process for deploying an application server, as provided in this application embodiment, includes:

[0403] Step 701: EES determines the instantiation of EAS based on the requirements of EEC and pre-configures the instantiation time of EAS.

[0404] For example, a terminal (such as the EEC on the terminal) sends a request message to the EES, which indicates the EEC's needs. For example, if the EEC needs to start an application, and the application corresponds to an EAS, then the EAS needs to be instantiated.

[0405] In one possible implementation, EES configures the EAS instantiation time based on the EAS identifier. This means that the instantiation times corresponding to different EAS identifiers can be the same or different.

[0406] The EAS instantiation time can be understood as the duration required for EAS to be instantiated.

[0407] For example, EAS1 is identified as EAS ID#1, and its instantiation time is 10 minutes (min). EAS2 is identified as EAS ID#2, and its instantiation time is 30 minutes (min).

[0408] Optionally, the same EAS instance can be instantiated at different times.

[0409] For example, if application A requires high Key Performance Indicators (KPIs) from EAS1, the EAS1 instantiation time will be longer. For instance, higher KPIs mean application A needs more resources (such as GPU and memory processors), thus resulting in a longer EAS1 instantiation time (e.g., 30 minutes). Conversely, if application A requires low KPIs from EAS1, the EAS1 instantiation time will be shorter. For instance, lower KPIs mean application A needs fewer resources (such as GPU and memory processors), thus resulting in a shorter EAS1 instantiation time (e.g., 15 minutes).

[0410] Step 702: The edge enabling server sends a request message to the first network management system to trigger EAS instantiation. Correspondingly, the first network management system receives the request message from the edge enabling server to trigger EAS instantiation.

[0411] The request message that triggers EAS instantiation includes an identifier for the EAS that needs to be instantiated. Specifically, the request message that triggers EAS instantiation is used to request the instantiation of the edge application server identified by that identifier.

[0412] Optionally, the request message that triggers EAS instantiation may also include resource requirements for the edge application server that needs to be instantiated, such as the image processor unit and memory processor unit corresponding to the edge application server.

[0413] In one possible implementation, the edge enabling server determines, based on the terminal's request, that an edge application server needs to be instantiated, and then executes step 702.

[0414] In another possible implementation, the edge enabling server determines, based on triggering conditions, that a first edge application server needs to be instantiated, and then executes step 702.

[0415] For example, if the trigger condition is that the EAS server is overloaded, for example, if the EAS identifier is EAS ID#1, the edge enabling server determines that the EAS1 corresponding to EAS ID#1 is overloaded, then it determines that EAS1 needs to be instantiated.

[0416] The first network management system can be the edge computing service provider management node system (ECSP MNS).

[0417] Step 703: The first network management system sends a request message to the second network management system to create an EAS (create EAS request message). Correspondingly, the second network management system receives the request message to create an EAS from the first network management system.

[0418] The request message to create an EAS is used to request the creation of an EAS. The request message carries an identifier for the EAS to be instantiated.

[0419] For example, the first request message may also include requirements for the EAS to be created, such as the image processor unit and memory processor unit required by the EAS.

[0420] For example, the second network management system could be the European Telecommunications Standards Institute Network Functions Virtualization Management and Orchestration (ETSI NFV MANO), which is responsible for deploying EAS.

[0421] Step 704: When the second network management system determines that the EAS can be instantiated, the second network management system sends an EAS creation response message to the first network management system. Correspondingly, the first network management system receives the EAS creation response message from the second network management system.

[0422] The EAS creation response message is used to indicate that EAS instantiation is in progress, or to indicate that EAS instantiation is in the process of being performed. Optionally, the create EAS response message may also include an identifier of the EAS being instantiated.

[0423] For example, the create EAS response message includes an indication that instantiation is in progress.

[0424] Step 705: The second network management system executes EAS instantiation.

[0425] Step 706: The first network management system sends a second instruction message to the EES. Correspondingly, the EES receives the second instruction message from the first network management system.

[0426] The second indication information is used to indicate that EAS instantiation is in progress. The second indication information includes the identifier of EAS.

[0427] For example, the second indication information could be an EAS instantiation in progress message, which includes the EAS ID.

[0428] Optionally, the second indication information may also include the expected duration of EAS instantiation or the expected completion time. Alternatively, step 706 may also include the first network management system sending the second indication information and the third time information to the edge enabling server. The third time information is used to indicate the expected duration of edge application server instantiation or the expected completion time.

[0429] Step 707: EES determines the instantiation time information of EAS corresponding to the identifier of EAS based on the second instruction information.

[0430] The instantiation time information refers to the remaining duration of EAS instantiation, or the moment / time when EAS instantiation is completed.

[0431] As an example, step 707 can be implemented using the following methods 1 and 2:

[0432] Method 1: In step 706, the first network management system does not provide third-time information to the edge enabling server.

[0433] In one possible implementation, step 707 can be achieved in the following way:

[0434] The edge enabling server can determine the expected duration or expected completion time of the first edge application server instantiation based on the time when it receives the second indication information and the time when the first edge application server is instantiated as pre-configured in step 701.

[0435] For example, if the edge enabling server pre-configures the instantiation time of the first edge application server to be 30 minutes, and the edge enabling server receives the second instruction information from the first network management system at 10:15, then the timing can start from the moment the second instruction information is received. The edge enabling server determines that the remaining time for the instantiation of the first edge application server is 30 minutes, or that the instantiation of the first edge application server is completed at 10:45.

[0436] Method 2: In step 706, the first network management system provides third-time information to the edge enabling server.

[0437] In another possible implementation, step 707 can be implemented in the following way:

[0438] The edge enabling server determines the remaining instantiation time of the edge application server identified by the first identifier, or the moment when the edge application server instantiation is completed, based on the third time information.

[0439] In Method 2, the process of pre-configuring the time of instantiation of the first edge application server in step 701 above can be omitted.

[0440] For example, if the third time information includes the expected completion time of the first edge application server instantiation as 30 minutes, or the expected completion time as 10:15, then the edge enabling server can directly determine the remaining time of the first edge application server instantiation as 30 minutes, or the completion time of the first edge application server instantiation as 10:15, based on the third time information.

[0441] Step 708: The edge enabling server sends a registration request message (EES registration request) or a registration update request message to the edge configuration server. Correspondingly, the edge configuration server receives the registration request message or registration update request message from the edge enabling server.

[0442] The registration request message or registration update request message includes: the EED identifier (EES ID), indication information indicating that the edge application server instantiation process is in progress, and instantiation time information. The instantiation time information may include the moment when the edge application server instantiation is completed, or the expected duration for EAS instantiation to complete.

[0443] It is worth noting that step 708 is an optional step and can be omitted in practice.

[0444] Step 709: The edge configuration server obtains the instantiation time information of the edge application servers corresponding to one or more server identifiers. The instantiation time information of the edge application server corresponding to any server identifier is used to indicate the completion time of the instantiation of that edge application server / the time required for EAS instantiation.

[0445] It is worth noting that, for example, in step 709, the edge configuration server can obtain the instantiation time information of the edge application server corresponding to any server identifier from step 708.

[0446] As an example, the edge enable server can proactively send a registration request message (EES registration request) or a registration update request message to the edge configuration server so that the edge configuration server can obtain the instantiation time information of the edge application server corresponding to any server identifier from step 708.

[0447] As another example, the edge configuration server can send a request message to the edge enabling server, requesting the edge enabling server to send the instantiation time information of one or more edge application servers corresponding to server identifiers. In this way, the edge enabling server can provide the edge configuration server with the instantiation time information of one or more edge application servers corresponding to server identifiers based on the request.

[0448] As another example, the edge configuration server may be pre-configured with one or more server identifiers corresponding to the instantiation time information of the edge application server.

[0449] Step 710: The terminal or its EEC or S-EES sends a service provisioning request message to the edge configuration server. Correspondingly, the edge configuration server receives the service provisioning request message from the terminal or S-EES.

[0450] The service configuration request message includes a first identifier and second time information. The service configuration request message is used to request the discovery of a first edge enabling server associated with a first EAS corresponding to the first identifier. The first EAS is the EAS used to provide services to the terminal when the terminal is located at the target location.

[0451] The second time information is used to indicate the time (moment) when the terminal arrives at the target location, or the second time information is used to indicate the time or moment when the terminal arrives at the service area of ​​the first EAS. It can be understood that the target location can also be understood as the service area of ​​the first EAS.

[0452] For example, the second time information could be the predicted expiration time or the expected expired time. Here, S-EES refers only to the EES associated with the EAS that provides services to the terminal at its current location. The first EES mentioned below can refer to the target EES, i.e., the EES associated with the first EAS that provides services to the terminal after it reaches the target location.

[0453] Step 711: The edge configuration server determines the first edge enabling server based on the status information of the edge application server corresponding to the edge enabling server, the completion time of the edge application server instantiation, and the second time information.

[0454] The status information of the edge application server includes the instantiated process. For example, the status of the edge application server can be instantiable but not instantiated, or it can be instantiated.

[0455] The first edge enabling server is the EES corresponding to the EAS that was instantiated before the time indicated by the second time information.

[0456] For example, if the terminal arrives at location #1 in 5 minutes, the ECS determines that there are two EES for location #1 and EASID, and the two EES correspond to two EAS. For EAS #1, it takes a total of 30 minutes to complete instantiation. Steps 701-711 have not been executed, meaning that the instantiation process of this EAS has not yet been triggered. For EAS #2, it takes a total of 20 minutes to complete instantiation, and the EAS instantiation process was triggered and executed 15 minutes ago, meaning that it still takes 5 minutes to complete the EAS instantiation. Assuming that the prediction expiration time corresponding to the terminal is 5 minutes, then the ECS should prioritize EES #2 corresponding to EAS #2 to provide services to the terminal.

[0457] Step 712: The edge configuration server sends a service provisioning response message. Correspondingly, the terminal / S-EES receives the configuration service response message from the edge configuration server.

[0458] The configuration service response message includes information about the first edge enabling server. For example, the identifier of the first edge enabling server, and / or the address of the first edge enabling server.

[0459] Step 713: The terminal or its EEC / S-EES sends a discovery request message (EASdiscovery request) to the first edge enabling server. Correspondingly, the first edge enabling server receives the discovery request message from the EEC / S-EES.

[0460] The EAS discovery request includes a first edge identifier (EAS ID) and second time information (prediction expiration time). The EAS discovery request is essentially a first request message that requests the discovery of a first application server identified by the first identifier. This first application server is used to provide services to the terminal when it is located at the target location. The target location can be a specific location or a region; this embodiment does not limit the scope of the request.

[0461] Step 714: The first edge enabling server determines the first edge application server based on the instantiation status information of at least one edge application server associated with the first edge enabling server, the completion time of the edge application server instantiation, and the second time information.

[0462] The first edge application server is an edge application server that is instantiated before the time (moment) when the terminal arrives at the predicted / expected target location, or before the time (moment) when the second time information is used to indicate the time (time) when the first terminal arrives at the target EAS service area.

[0463] For example, if a terminal arrives at location 1 (location#1) after 5 minutes, based on location#1 and the first identifier (EAS ID), the first edge enabling server determines that two edge application servers meet the requirements: edge application server 1 (EAS#1) and edge application server 2 (EAS#2). For EAS#1, instantiation takes 30 minutes and its status is "instantiation not started." For EAS#2, instantiation takes 20 minutes and its status is "instantiation was triggered 15 minutes ago." At this point, EAS#1 still needs 30 minutes to complete instantiation, while EAS#2 only needs 5 minutes. Assuming the second time information corresponding to the terminal device, such as the prediction expiration time, is 5 minutes, the first edge enabling server determines EAS#2 as the target edge application server.

[0464] Optionally, if the first edge application server has not yet been instantiated, the method provided in this application embodiment further includes:

[0465] Step 715: The first edge enabling server sends second instruction information to the first network management system. Correspondingly, the first network management system receives the second instruction information from the first edge enabling server.

[0466] The second instruction information is used to trigger the first network management system to instantiate the first edge application server.

[0467] Step 716: The first edge enabling server sends an EAS discovery response message. Correspondingly, the terminal or S-EES receives the discovery response message from the first edge enabling server.

[0468] The response message includes information about the first edge application server, such as the identifier of the first edge application server and / or the address of the target edge application server.

[0469] It should be noted that steps 709-715 occur during the application context migration phase, which requires the discovery of the target EAS (i.e., the first EAS) and the target EES (i.e., the first EES). Therefore, EEC can also be replaced with S-EES, where S-EES is the EES for the initial connection of the terminal.

[0470] Figure 7 In the embodiment shown, during the application context migration phase, when reselecting EES or EAS for the terminal, the real-time status of EAS instantiation can be taken into account. At this time, the corresponding EAS / EES can be determined based on the latest time information of EAS instantiation, avoiding the selection of an unsuitable EAS, which would prevent the terminal from obtaining the optimal service.

[0471] like Figure 8 As shown, Figure 8 Another implementation of the application server deployment method provided in this application embodiment includes:

[0472] Steps 801 to 810 are the same as steps 701 to 710 in the above embodiments, and will not be repeated here.

[0473] Optionally, in step 810, the service configuration request message may not carry the second time information, but instead carry indication information. This indication information is used to indicate the service continuity planning type ACR, that is, to pre-execute the discovery enable server, the discovery application server, and the application context transmission based on the terminal's predicted location.

[0474] Optionally, in step 810, the service configuration request message does not carry second time information or indication information. In this case, the configuration server does not need to determine a unique application server.

[0475] Step 811: The configuration server sends a service provisioning response message. Correspondingly, the EEC / S-EES receives the service provisioning response message from the configuration server.

[0476] The service configuration response message includes: information about one or more enabling servers, one or more server identifiers associated with each enabling server, instantiation status information of the application server identified by any server identifier, and the completion time or expected completion time of the instantiation of the application server identified by any server identifier.

[0477] It should be noted that the ECS can send all its associated EES information to the EEC or S-EES, or determine at least one EES based only on the EASID requested by the terminal / S-EES and the EASID corresponding to the EES on the ECS. In this case, the ECS also needs to send the EASID corresponding to the EES, the instantiation status corresponding to the EASID, and the EAS instantiation completion time / completion duration information to the EEC or S-EES.

[0478] Step 812: The EEC / S-EES determines the first enabling server based on the terminal's second time information and one or more server identifiers associated with each enabling server, the instantiation status information of the application server identified by any server identifier, and the completion time or expected completion time of the instantiation of the application server identified by any server identifier.

[0479] The first server available can be the EES corresponding to EAS that was instantiated before the Prediction expiration time.

[0480] Step 813: The EEC / S-EES sends an Application Server Discovery Request (EAS discovery request) message to the first enabling server. Correspondingly, the enabling server receives the Application Server Discovery Request message from the terminal device.

[0481] The discovery request message includes the application server's identifier. Optionally, the discovery request message may also include secondary time information or indications of service continuity planning.

[0482] Step 814: The first enabling server sends an application server discovery response message (EASdiscovery response message) to the EEC / S-EES. Correspondingly, the EEC / S-EES receives the application server discovery response message from the first enabling server.

[0483] For example, the first enabling server can send an application server discovery response message directly to EEC / S-EES, or send an application server discovery response message to EEC / S-EES through the target enabling server.

[0484] For example, the application server discovery response message includes: information about at least one application server, instantiation status information for each application server, and the instantiation completion time or estimated instantiation completion duration for each application server. The instantiation status information indicates whether instantiation has commenced.

[0485] Step 815: EEC / S-EES determines the first application server from at least one application server based on the instantiation status information of each application server, the instantiation completion time or the expected instantiation completion duration of each application server, and the second time information.

[0486] The first application server is an application server that is instantiated before the terminal reaches the target location.

[0487] Optionally, after step 815, the method provided in this application embodiment may further include:

[0488] Step 816: The EEC / S-EES sends information about the first application server to the first enabling server. Correspondingly, the first enabling server receives information from the first application server of the EEC.

[0489] For example, the EEC sends an EAS information provisioning procedure message to the first enabling server, which includes the address information of the target application server.

[0490] exist Figure 8 In the embodiment shown, when selecting EES or EAS, the terminal or S-EES can take into account the real-time status of EAS instantiation. At this time, the corresponding EAS / EES can be determined based on the latest time information of EAS instantiation, so as to avoid selecting an unsuitable EAS and causing the terminal to be unable to obtain the optimal service.

[0491] like Figure 9 As shown, Figure 9 This is an implementation of the third application server deployment method provided in the embodiments of this application. Figure 9 The illustrated embodiments and Figure 7 The difference in the illustrated embodiments lies in whether the ECS has a pre-configured EAS instantiation time. Specific methods include:

[0492] Step 901: The edge configuration server is pre-configured with one or more edge application server instantiation times.

[0493] Steps 902 to 906 are the same as steps 702 to 706 in the above embodiments, and will not be repeated here.

[0494] Step 907: The edge enabling server sends a second instruction to the edge configuration server. Correspondingly, the edge configuration server receives the second instruction from the edge enabling server.

[0495] The second indication information is used to indicate that the instantiation of the first edge-enabled server identified by the EAS ID is being performed.

[0496] For example, the second indication information could be an EAS instantiation in progress message, which includes the EAS ID.

[0497] Step 908: The edge configuration server determines the first time information of the instantiation of the first edge enabling server based on the second instruction information.

[0498] In one possible implementation, the edge enabling server can determine the instantiation completion time of the first edge enabling server or the remaining time of the first edge enabling server instantiation based on the time of receiving the second indication information and the time of instantiation of the first edge enabling server pre-configured by the edge configuration server in step 901.

[0499] For the specific implementation method, please refer to the description of step 707 in the above embodiment, which will not be repeated here.

[0500] Steps 909 to 914 are the same as steps 710 to 715 in the above embodiments, and will not be repeated here.

[0501] ECS can determine the moment / duration when EAS instantiation is complete based on the EAS instantiation in progress indication information and the EAS instantiation time. At this time, when selecting EES or EAS, ECS / EES can take into account the real-time status of EAS instantiation. The corresponding EES / EAS can be determined based on the latest EAS instantiation time information, avoiding the selection of an unsuitable EAS, which would prevent the UE from obtaining the optimal service.

[0502] like Figure 10 As shown, Figure 10 This is an implementation of the fourth application server deployment method provided in the embodiments of this application. Figure 10 The illustrated embodiments and Figure 8 The difference in the illustrated embodiments lies in whether the ECS has a pre-configured EAS instantiation time. The specific method includes:

[0503] Steps 1001 to 1009 are the same as steps 901 to 909 in the above embodiments, and will not be repeated here.

[0504] Steps 1010 to 1015 are the same as steps 811 to 816 in the above embodiments, and will not be repeated here.

[0505] ECS can determine the moment / duration when EAS instantiation is complete based on the EAS instantiation in progress indication information and the EAS instantiation time. At this time, when selecting EES or EAS, UE can take into account the real-time status of EAS instantiation. It can determine the corresponding EES / EAS based on the latest EAS instantiation time information to avoid selecting an unsuitable EAS, which would prevent UE from obtaining the best service.

[0506] like Figure 11 As shown, Figure 11 This is a schematic diagram illustrating the specific implementation of the fifth application server deployment method provided in this application embodiment.

[0507] In this embodiment of the application, the enabling server can correspond to multiple hardware platforms. On different hardware platforms, the application server is instantiated at different times, and the capabilities of different hardware platforms are also different.

[0508] In one possible embodiment of this application, the method provided by this application further includes: a configuration server obtaining information about multiple platforms corresponding to at least one enabling server.

[0509] The information for multiple platforms includes the identifier of each platform and / or its capability information. Each platform is used to deploy the application server, and the platform's capability information includes the duration of the application server's deployment on the platform.

[0510] Step 1101: Configure the server and / or enable the server to be configured with the time information of the application server instantiation corresponding to the identifier of at least one platform, and / or the capability information of at least one platform.

[0511] Step 1102: The first network management system sends a Create EES request message to the second network management system. Correspondingly, the second network management system receives the Create EES request message from the first network management system. The Create EES request message is used to request the creation of an enable server.

[0512] For example, the first network management system is ESCP MNS, and the second network management system is ETSI NFV MANO.

[0513] The creation of an EES request message includes EES requirements, such as EES location and software image.

[0514] Step 1103: The second network management system sends a response message to the first network management system. Correspondingly, the first network management system receives a response message from the second network management system. The response message is used to indicate whether the server instantiation process is enabled.

[0515] For example, the response message is a create EES response message, which includes, but is not limited to, the instantiation in progress information.

[0516] Step 1104: The second network management system enables the instantiation of the server.

[0517] Step 1105: The second network management system sends a notification message to the first network management system. Correspondingly, the first network management system receives the notification message from the second network management system. The notification message is used to indicate whether the server's functions are enabled.

[0518] For example, the notification message is a create EES notification message, which includes, but is not limited to: the enabling server's function information (EES function), such as the enabling server's identification information (EES ID), serving location, enabling server's address information (EES address), and the enabling server's corresponding platform information (infrastructure ID).

[0519] Step 1106: Enable the server to obtain the configuration file.

[0520] The configuration file (EES profile) contains the identifier information of the enabling server (EES ID), the port of the enabling server (EES endpoint), and information about at least one platform corresponding to the enabling server (listinfrastructure ID).

[0521] Step 1107: The enabling server sends a registration request message to the configuration server. Correspondingly, the configuration server receives the registration request message from the enabling server.

[0522] For example, the registration request message is an EES registration request message, which includes, but is not limited to: the identification information of the enabling server (EES ID), the identification information of the application server (EAS ID), the status information of the application server (e.g., EAS instantiated or instantiable), and the information of at least one platform corresponding to the enabling server (list infrastructure ID).

[0523] Step 1108: Configure the server to determine the deployment time of the application server on different platforms based on the information (listinfrastructure ID) of at least one platform corresponding to the enabling server.

[0524] Optionally, the configuration server determines the deployment time of the application server on different platforms based on the information (listinfrastructure ID) of at least one platform corresponding to the enabling server and the configuration information.

[0525] Step 1109: The EEC / S-EES sends a service provisioning request message to the configuration server. Correspondingly, the configuration server accepts the service provisioning request message from the terminal device.

[0526] For example, a service configuration request message may include the application server's identification information (EAS ID) and / or, second time information (expected expired time, or prediction expiration time).

[0527] Step 1110: The configuration server determines the first enabling server based on the second time information, the identification information of at least one platform corresponding to the enabling server, and the capability information corresponding to the platform.

[0528] Step 1111: The configuration server sends a service configuration response message to the EEC / S-EES. Correspondingly, the EEC / S-EES receives the service configuration response message from the configuration server.

[0529] The service configuration response message includes information about the first enabling server, such as its EES address.

[0530] Step 1112: The EEC / S-EES sends an EAS discovery request message to the first enabling server. Correspondingly, the first enabling server receives the EAS discovery request message from the EEC / S-EES.

[0531] Among them, the EAS discovery request message requests the determination of the platform on which the application server is deployed.

[0532] For example, the EAS discovery request message includes, but is not limited to, the application server's identification information (EAS ID) and second time information.

[0533] Step 1113: The first enabling server determines the target platform of the application server identified by the identification information of the application server from one or more first platforms based on the second time information, the identifier of one or more first platforms corresponding to the first enabling server, and the capability information corresponding to one or more first platforms.

[0534] For example,

[0535] Step 1114: The first enabling server sends instruction information to the first network management system. Correspondingly, the first network management system receives the instruction information from the first enabling server. The instruction information is used to indicate the application server identified by the identification information of the application server instantiated on the target platform.

[0536] For example, the instruction information includes, but is not limited to, the identifier of the target platform.

[0537] Step 1115: The first enabling server sends an EAS discovery response message to the EEC / S-EES. Correspondingly, the EEC / S-EES receives the EAS discovery response message from the enabling server.

[0538] The EAS discovery response message includes the application server's address information (EAS address).

[0539] like Figure 12 As shown, Figure 12 This is a schematic diagram illustrating a specific implementation of a sixth server deployment method provided in this application embodiment.

[0540] Steps 1201 to 1203 are the same as steps 1102 to 1104 in the above embodiments, and will not be repeated here.

[0541] Step 1204: The second network management system sends a notification message to the first network management system. Correspondingly, the first network management system receives the notification message from the second network management system.

[0542] The difference from step 1105 in the above embodiment is that the notification message includes: enabling server function information (EES function), such as enabling server identification information (EES ID), service location, enabling server address information (EES address), and application server deployment duration information on the enabling server.

[0543] Step 1205: Enable the server to obtain the configuration file.

[0544] The difference between step 1106 in the above embodiment is that the configuration file (EES profile) contains the identifier information (EES ID) of the enabling server, the port (EES endpoint) of the enabling server, and the duration of application server deployment on the enabling server.

[0545] Step 1206: The enabling server sends a registration request message to the configuration server. Correspondingly, the configuration server receives the registration request message from the enabling server. The registration request message is used to request the determination of the deployment time of the application server corresponding to the enabling server on the platform.

[0546] The difference from step 1107 in the above embodiment is that the registration request message includes, but is not limited to: the identification information of the enabling server (EES ID), the identification information of the application server (EAS ID), the status information of the application server (e.g., EAS instantiated or instantiable), and the duration of application server deployment on the enabling server.

[0547] Step 1207 is the same as step 1108 in the above embodiment, and will not be described again here.

[0548] Step 1208: Configure the server to determine at least one enabled server based on the second time information and the duration of application server deployment on the enabled server.

[0549] Steps 1209 to 1210 are the same as steps 1111 to 1112 in the above embodiments, and will not be repeated here.

[0550] Step 1211: If it is necessary to select an application server that can be instantiated, enable the server to determine the required deployment duration of the application server based on the second time information.

[0551] For example, if the second time information is the prediction expiration time, and the expected time for the terminal device to reach the target location is 10 minutes, then the required deployment time of the application server needs to be less than 10 minutes.

[0552] Steps 1212 to 1213 are the same as steps 1114 to 1115 in the above embodiments, and will not be repeated here.

[0553] like Figure 13 As shown, Figure 13 This is a schematic diagram illustrating a specific implementation of a seventh server deployment method provided in this application embodiment.

[0554] Step 1301: The terminal obtains the time information of the application server instantiation corresponding to the identifier of at least one platform, and / or the capability information of at least one platform.

[0555] Steps 1302 to 1307 are the same as steps 1102 to 1107 in the above embodiments, and will not be repeated here.

[0556] Step 1308: The configuration server sends a service configuration response message to the terminal. Correspondingly, the terminal device receives the service configuration response message from the configuration server.

[0557] The service configuration response message includes, but is not limited to: the identifier information of the enabling server (EES ID), the port of the enabling server (EES endpoint), the status information of the application server instantiation, and the information of at least one platform corresponding to the enabling server (list infrastructure ID).

[0558] Step 1309: In the absence of an available application server, the terminal device determines the deployment duration of the application server based on the identification information of the platform corresponding to the enabling server, and determines the enabling server based on the second time information.

[0559] The application server corresponding to the enabling server is instantiated before the terminal device reaches the target location.

[0560] Step 1310: The terminal sends a discovery response message to the enabling server. Correspondingly, the enabling server receives the discovery response message from the terminal device.

[0561] The difference between step 1112 in the above embodiment is that the discovery request message includes, in addition to the application server's identification information (EAS ID) and the second time information, the platform's identification information (required infrastructure ID) corresponding to the application server that needs to be instantiated.

[0562] Steps 1311 to 1312 are the same as steps 1114 to 1115 in the above embodiments, and will not be repeated here.

[0563] like Figure 14 As shown, Figure 14 This is a schematic diagram illustrating the specific implementation of the eighth server deployment method provided in this application embodiment.

[0564] Steps 1401 to 1407 are the same as steps 1201 to 1207 in the above embodiments, and will not be repeated here.

[0565] Step 1408: The configuration server sends a service configuration request message to the terminal device. Correspondingly, the terminal device receives a service configuration response message from the configuration server.

[0566] The service configuration response message includes, but is not limited to: the identifier information of the enabling server (EES ID), the port of the enabling server (EES endpoint), the status information of the application server instantiation, and the duration of the application server deployment on the enabling server.

[0567] Step 1409: In the absence of an available application server, the terminal device determines the enabling server based on the second time information.

[0568] Step 1410: The terminal device sends a discovery request message to the enabling server. Correspondingly, the enabling server receives the discovery request message from the terminal device.

[0569] The discovery request message includes, but is not limited to: the application server's identification information (EAS ID), second time information, and the application server that needs to be instantiated.

[0570] Step 1411: If it is necessary to select an instantiable application server, enable the server to determine the required deployment duration of the application server based on the second time information.

[0571] Steps 1412 to 1413 are the same as steps 1114 to 1115 in the above embodiments, and will not be repeated here.

[0572] The above mainly describes the solutions of the embodiments of this application from the perspective of interaction between various network elements. It is understood that each network element, such as a terminal, configuration server, and enable server, includes corresponding structures and / or software modules to perform the above functions in order to achieve them. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0573] This application embodiment can divide functional units according to the configuration server, enable server, and terminal device in the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0574] The above combination Figure 5 and Figure 6 The methods described in the embodiments of this application have been explained. The communication apparatus provided in the embodiments of this application for executing the above methods is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced in each other. The communication apparatus provided in the embodiments of this application can execute the steps performed by the configuration server and the enable server in the above analysis method.

[0575] When using integrated units Figure 15 The communication device involved in the above embodiments is shown. The communication device 150 may include a communication module 1501 and a processing module 1502.

[0576] In an alternative implementation, the communication device 150 may further include a storage module 1503 for storing the program code and data of the communication device.

[0577] On one hand, the communication device 150 is a configuration server, or a chip used in a configuration server. In this case, the communication module 1501 is used to support communication between the communication device and external network elements (e.g., terminal devices). For example, the communication module 1501 is used to perform signal transmission and reception operations of the configuration server in the above method embodiments. The processing module 1502 is used to perform signal processing operations of the configuration server in the above method embodiments.

[0578] In one example, the communication module 1501 is used to perform the above embodiments. Figure 5 The receiving action in step 502 is performed by the configuration server. The communication module 1501 is used to perform the actions described in the above embodiments. Figure 5 The sending action performed by the configuration server in step 504a.

[0579] In one possible embodiment, the processing module 1502 is used to execute the embodiments described above. Figure 5 The processing action performed by the configuration server in step 501 or step 503a.

[0580] On the other hand, the communication device 150 is a terminal device, or a chip applied in a terminal device. In this case, the communication module 1501 is used to support communication between the communication device and external network elements (e.g., a configuration server). For example, the communication module 1501 is used to perform signal transmission and reception operations of the terminal device in the above method embodiments. The processing module 1502 is used to perform signal processing operations of the terminal device in the above method embodiments.

[0581] In one example, the communication module 1501 is used to perform the above embodiments. Figure 5 The sending action in step 502 is performed by the terminal device. The communication module 1501 is used to perform the above-described embodiment. Figure 5 The receiving action performed by the terminal device in step 504a or step 503b.

[0582] On one hand, the communication device 150 is an enabling server, or a chip applied in an enabling server. In this case, the communication module 1501 is used to support communication between the communication device and external network elements (e.g., terminal devices). For example, the communication module 1501 is used to perform the signal transmission and reception operations of the enabling server in the above method embodiments. The processing module 1502 is used to perform the signal processing operations of the enabling server in the above method embodiments.

[0583] In one example, the communication module 1501 is used to perform the above embodiments. Figure 6 The receiving action performed by the enabling server in step 601 or step 604b. Communication module 1501 is used to perform the above embodiments. Figure 6 The sending action performed by the configuration server in step 603a or step 602b.

[0584] In one possible embodiment, the processing module 1502 is used to execute the embodiments described above. Figure 6 The processing action performed by the enabling server in step 602a.

[0585] On the other hand, the communication device 150 is a terminal device, or a chip applied in a terminal device. In this case, the communication module 1501 is used to support communication between the communication device and external network elements (e.g., a configuration server). For example, the communication module 1501 is used to perform signal transmission and reception operations of the terminal device in the above method embodiments. The processing module 1502 is used to perform signal processing operations of the terminal device in the above method embodiments.

[0586] In one example, the communication module 1501 is used to perform the above embodiments. Figure 6 The sending action performed by the terminal device in step 603a or step 604b. Communication module 1501 is used to perform the above embodiments. Figure 6 The receiving action performed by the terminal device in step 603a or step 602b.

[0587] The processing module 1502 can be a processor or controller, such as a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication module can be a transceiver, transceiver circuitry, or communication interface, etc. The storage module can be a memory.

[0588] When the processing module 1502 is a processor 1601 or a processor 1605, the communication module 1501 is a transceiver 1603, and the storage module 1503 is a memory 1602, the communication device involved in this application can be... Figure 16 The communication device shown.

[0589] Figure 16 This illustration shows a schematic diagram of the hardware structure of a communication device according to an embodiment of this application. The hardware structures of the terminal device and network device in this embodiment can be referenced as follows: Figure 16 The structure shown is described. The communication device includes a processor 1601, a communication line 1604, and at least one transceiver. Figure 16 (The illustration is merely exemplary, using transceiver 1603 as an example only).

[0590] The processor 1601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0591] Communication line 1604 may include a path for transmitting information between the aforementioned components.

[0592] Transceiver 1603 is a device that uses any transceiver class for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0593] Optionally, the communication device may also include a memory 1602.

[0594] Memory 1602 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 1602 may exist independently and be connected to processor 1601 via communication line 1604. Memory 1602 may also be integrated with processor 1601.

[0595] The memory 1602 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 1601. The processor 1601 executes the computer execution instructions stored in the memory 1602, thereby implementing the communication method provided in the following embodiments of this application.

[0596] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0597] In a specific implementation, as one example, the processor 1601 may include one or more CPUs, for example... Figure 16 CPU0 and CPU1 in the CPU.

[0598] In a specific implementation, as one example, the communication device may include multiple processors, for example... Figure 16 Processors 1601 and 1602 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0599] Figure 17 This is a schematic diagram of the structure of chip 170 provided in an embodiment of this application. Chip 170 includes one or more (including two) processors 1710 and communication interfaces 1730.

[0600] Optionally, the chip 170 also includes a memory 1740, which may include read-only memory and random access memory, and provides operation instructions and data to the processor 1710. A portion of the memory 1740 may also include non-volatile random access memory (NVRAM).

[0601] In some implementations, memory 1740 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0602] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 1740 (the operation instructions can be stored in the operating system).

[0603] One possible implementation is that the terminal and network devices have similar structures, and different devices can use different chips to achieve their respective functions.

[0604] The processor 1710 controls the processing operations of any terminal or network device. The processor 1710 can also be referred to as a central processing unit (CPU).

[0605] Memory 1740 may include read-only memory and random access memory, and provides instructions and data to processor 1710. A portion of memory 1740 may also include NVRAM. For example, in an application, memory 1740, communication interface 1730, and memory 1740 are coupled together via bus system 1720, which, in addition to a data bus, may also include a power bus, control bus, and status signal bus, etc. However, for clarity, in... Figure 17 The general labeled all buses as Bus System 1720.

[0606] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 1710. The processor 1710 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 1710 or by instructions in the form of software. The processor 1710 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 1740. Processor 1710 reads the information in memory 1740 and, in conjunction with its hardware, completes the steps of the above method.

[0607] In one possible implementation, the communication interface 1730 is used to perform... Figure 5 The illustrated embodiment describes the steps for receiving and sending configuration data from the server. Processor 1710 is used to execute these steps. Figure 5 The steps of the configuration server processing in the illustrated embodiment.

[0608] In one possible implementation, the communication interface 1730 is used to perform... Figure 5 The steps of receiving and transmitting data in the terminal device shown in the embodiment are illustrated. Processor 1710 is used to execute... Figure 5 The processing steps of the first device in the illustrated embodiment.

[0609] In one possible implementation, the communication interface 1730 is used to perform... Figure 6 The steps for enabling the server to receive and transmit data in the illustrated embodiment are shown. Processor 1710 is used to execute... Figure 6 The steps for enabling the server processing in the illustrated embodiment.

[0610] In one possible implementation, the communication interface 1730 is used to perform... Figure 6 The steps of receiving and transmitting data in the terminal device shown in the embodiment are illustrated. Processor 1710 is used to execute... Figure 6 The processing steps of the first device in the illustrated embodiment.

[0611] The communication module described above can be a communication interface of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the communication module is the communication interface used by the chip to receive or send signals from other chips or devices.

[0612] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 5 or Figure 6 The functions performed by the configuration server.

[0613] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 5 or Figure 6 The function performed by the first device.

[0614] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 5 or Figure 6 The functions performed by the enabling server.

[0615] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 5 or Figure 6 The functions performed by the configuration server.

[0616] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 5 or Figure 6 The function performed by the first device.

[0617] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 5 or Figure 6The functions performed by the enabling server.

[0618] On one hand, a chip is provided for use in a configuration server. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 5 or Figure 6 The functions performed by the configuration server.

[0619] On one hand, a chip is provided for use in an enabling server. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 5 or Figure 6 The functions performed by the enabling server.

[0620] On the one hand, a chip is provided for use in a terminal device. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 5 or Figure 6 Functions performed by terminal devices.

[0621] This application provides a communication system, including: a terminal, a configuration server, and an enable server.

[0622] The configuration server is used to implement, for example Figure 5 or Figure 6 The functions performed by the configuration server. The enabling server is used to implement, for example... Figure 5 or Figure 6 The functions performed by the first enabling server. The first device is used to implement, for example... Figure 5 or Figure 6 The functions performed by the first device are as follows. The application server is used to provide services to the terminal.

[0623] The explanations and beneficial effects of the relevant content in any of the communication devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0624] In this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0625] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0626] It should be understood that the processor mentioned in the embodiments of this application can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0627] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0628] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0629] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0630] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0631] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0632] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0633] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0634] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0635] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0636] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for deploying a server, characterized in that, The method includes: The configuration server determines first time information for instantiation of at least one application server corresponding to at least one enabling server, and the first time information is used to indicate the remaining time information for instantiation of the application server. The configuration server receives a first request message from a terminal device, the first request message being used to instruct the configuration server to obtain information about at least one of the enabling servers, the at least one of the enabling servers including the first enabling server; The configuration server determines the first enabling server based on the remaining time information of the application server instantiation and the information of at least one enabling server. The first enabling server is used to provide services to the terminal device.

2. The method according to claim 1, characterized in that, The first time information is either the remaining duration of the application server instantiation or the completion time of the application server instantiation.

3. The method according to claim 2, characterized in that, The first time information is determined by the start time and / or execution duration of the application server instantiation and the time information corresponding to the application server instantiation.

4. The method according to claim 3, characterized in that, The method includes: The configuration server receives first indication information from at least one of the enabling servers, the first indication information being used to indicate the execution duration of the application server instantiation, or the start time of the application server instantiation.

5. The method according to claim 4, characterized in that, The first indication information is also used to indicate that application server instantiation is in progress, and the method further includes: The configuration server determines the instantiation time of the application server based on the first indication information.

6. The method according to claim 4, characterized in that, The method further includes: The configuration server receives the duration corresponding to the application server instantiation from at least one of the enabling servers; or, The configuration server pre-configures the time required for the application server to be instantiated.

7. The method according to claim 3, characterized in that, The method includes: The configuration server receives first-time information from at least one application server instantiated corresponding to at least one of the enabling servers.

8. The method according to any one of claims 1 to 7, characterized in that, The first request message includes second time information, which indicates the time when the terminal device arrives at the target location.

9. The method according to claim 8, characterized in that, The method includes: The configuration server determines the first enabling server based on at least one of the instantiation status information of at least one application server corresponding to at least one enabling server, the first time information, and the second time information.

10. The method according to claim 9, characterized in that, The method further includes: The configuration server sends a first response message to the terminal device. The first response message includes information about the first enabling server, which includes the identifier of the first enabling server and / or the address of the first enabling server.

11. The method according to any one of claims 1 to 7, characterized in that, The method further includes: The configuration server sends a first response message to the terminal device. The first response message includes information about the at least one enabling server. The information about the enabling server includes the identifier of the enabling server and / or the address of the enabling server, the first time information of the application server corresponding to the enabling server, and / or, first indication information.

12. A method for deploying a server, characterized in that, The method includes: The enabling server receives a second request message from the terminal device. The second request message is used to obtain information about the application server. The second request message includes the identification information of the terminal device and / or the application information to be executed. The enabling server sends a second response message to the terminal device. The second response message includes information about at least one application server, including the application server's identification information and / or address information.

13. The method according to claim 12, characterized in that, The second request message includes second time information, which indicates the time when the terminal device arrives at the target location.

14. The method according to claim 13, characterized in that, The method includes: The enabling server determines the first application server based on at least one of the instantiation status information corresponding to at least one of the application servers, the first time information, and the second time information. The first application server completes instantiation before the time when the terminal device arrives at the target location.

15. The method according to any one of claims 12 to 14, characterized in that, The method includes: The enabling server sends a second response message to the terminal device. The second response message includes information about the first application server, which includes the application server's identification information and / or address information.

16. The method according to claim 14, characterized in that, The first time information is either the remaining duration of the application server instantiation or the moment when the application server instantiation is completed.

17. The method according to claim 16, characterized in that, The first time information is determined by the start time of the application server instantiation and / or the execution duration, as well as the duration required for the application server instantiation.

18. The method according to claim 17, characterized in that, The method includes: The enabling server receives a second indication from the first network management system. The second indication is used to indicate the execution duration of the application server instantiation or the start time of the application server instantiation.

19. The method according to claim 18, characterized in that, The method includes: The enabling server determines the first time information based on the second instruction information and the time required for the application server to be instantiated.

20. The method according to claim 19, characterized in that, The method further includes; The enabling server sends the first time information to the configuration server, and the first time information corresponds to the application server.

21. The method according to claim 18, characterized in that, The method includes: The enabling server determines the first indication information based on the second indication information. The first indication information is used to indicate the execution duration of the application server instantiation or the start time of the application server instantiation. The enabling server sends the first instruction information to the configuration server.

22. The method according to any one of claims 12 to 19, characterized in that, The method further includes: The enabling server sends a second response message to the terminal device. The second response message includes information about at least one application server. The information about the application server includes the application server's identification information and / or address information, as well as the application server's corresponding first time information.

23. A method for deploying a server, characterized in that, The method includes: The terminal device sends a first request message to the configuration server. The first request message is used to instruct the configuration server to obtain information about at least one of the enabling servers. The information about at least one enabling server includes a first enabling server, which is used to provide services to the terminal device.

24. The method according to claim 23, characterized in that, The first request message includes second time information, which indicates the time when the terminal device arrives at the target location.

25. The method according to claim 24, characterized in that, The method includes: The terminal device receives a first response message from the configuration server. The first response message includes information about the first enabling server, which includes the identifier of the first enabling server and / or the address of the first enabling server.

26. The method according to claim 23, characterized in that, The method includes: The terminal device receives information from at least one enabling server from the configuration server, and / or first time information corresponding to the identifier of at least one application server corresponding to at least one enabling server; The terminal device determines at least one first enabling server based on at least one of the instantiation status information of at least one application server corresponding to at least one enabling server, the first time information, and the second time information.

27. A method for deploying a server, characterized in that, The method includes: The terminal device sends a second request message to the enabling server. The second request message is used to obtain information about the application server. The information about the application server includes the identification information of the terminal device and / or application information.

28. The method according to claim 27, characterized in that, The second request message includes second time information.

29. The method according to claim 28, characterized in that, The method includes: The terminal device receives a second response message from the enabling server. The second response message includes information about the first application server, which includes the identification information and / or address information of the first application server.

30. The method according to claim 27, characterized in that, The method includes: The terminal device receives a second response information from the enabling server. The second response information includes information about at least one application server, and the application server information includes the application server's identification information and / or address information. The terminal device determines the first application server based on at least one of the instantiated status information, the first time information, and the second time information corresponding to at least one of the application servers.

Images