Resource determination method and apparatus

Abstract

Provided in the present application are a resource determination method and apparatus. The method comprises: receiving first information, wherein the first information is used for determining a change in resources that a first edge application entity provides for a terminal device entity; and on the basis of a first resource that the first edge application entity can provide and the first information, determining a second resource that the first edge application entity can provide. By means of the method, when performance requirements of a terminal device entity change or the state of connection between the terminal device entity and a first edge application entity changes, the current available resources of the first edge application entity are dynamically maintained.

Description

Resource determination method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 13, 2023, with application number 202311719757.1 and application name “Method and Apparatus for Resource Determination”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a method and apparatus for resource determination. Background Art

[0003] Mobile Edge Computing (MEC) technology migrates computing, storage, and business service capabilities to the edge of the network, eliminating the need to transmit data back to the cloud as much as possible, reducing the waiting time and network costs for data traveling to and from the cloud.

[0004] Application clients (ACs) are used by application users to obtain application services from application servers. Application clients can connect to edge application servers (EASs) deployed and running in one or more edge data networks (EDNs) to obtain application services. In other words, EASs can provide resources (such as computing and storage) to ACs.

[0005] The Edge Enabler Server (EES) can obtain the maximum resources that EAS can provide during the EAS registration process. Summary of the Invention

[0006] The present application provides a method and apparatus for determining resources, by which the usage of EAS resources can be dynamically maintained / determined / updated.

[0007] In a first aspect, a method for determining resources is provided, which can be performed by a first entity, or by a chip or circuit configured in the first entity, which is not limited in this application. Optionally, the first entity is an edge-enabled entity.

[0008] The method includes: receiving first information, the first information is used to determine the change of resources provided by the first edge application entity to the terminal device entity; based on the first resources and first information that the first edge application entity can provide, determining the second resources that the first edge application entity can provide.

[0009] Through the above solution, when the resources provided by the first edge application entity to the terminal device entity change, the resources currently available to the first edge application entity are updated, thereby dynamically maintaining the currently available resources of the first edge application entity.

[0010] In combination with the first aspect, in some implementations of the first aspect, the first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connected or disconnected.

[0011] Through the above solution, when the connection status between the terminal device entity and the first edge application entity changes, the change in the connection status is notified to the first entity, thereby dynamically maintaining the current available resources of the first edge application entity.

[0012] In combination with the first aspect, in some implementation methods of the first aspect, based on the first resource and first information that can be provided by the first edge application entity, determining the second resource that can be provided by the first edge application entity, including: obtaining the first performance requirement of the terminal device entity, the first performance requirement is the performance requirement after the terminal device entity is connected to the first edge application entity; when the first information indicates that the terminal device entity and the first edge application entity are about to be connected or are already connected, determining the second resource based on the first resource and the third resource, the third resource is the resource corresponding to the first performance requirement of the terminal device entity.

[0013] Through the above scheme, when the terminal device entity is about to connect or is already connected to the first edge application entity, the change in the connection status is notified to the first entity, and the first entity updates the resources currently available to the first edge application entity, thereby dynamically maintaining the current available resources of the first edge application entity.

[0014] Optionally, the second resource is equal to the first resource minus the third resource.

[0015] In combination with the first aspect, in some implementation methods of the first aspect, based on the first resource and first information that can be provided by the first edge application entity, determining the second resource that can be provided by the first edge application entity, including: obtaining the second performance requirement of the terminal device entity, the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity; when the first information indicates that the terminal device entity is about to be disconnected from the first edge application entity or has been disconnected, determining the second resource based on the first resource and the fourth resource, the fourth resource being the resource corresponding to the second performance requirement of the terminal device entity.

[0016] Through the above scheme, when the terminal device entity and the first edge application entity are about to be disconnected or have been disconnected, the change in the connection status is notified to the first entity, and the first entity updates the resources currently available to the first edge application entity, thereby dynamically maintaining the current available resources of the first edge application entity.

[0017] Optionally, the second resource is equal to the first resource plus the fourth resource.

[0018] In combination with the first aspect, in some implementation methods of the first aspect, obtaining the first performance requirement of the terminal device entity, and obtaining the second performance requirement of the terminal device entity include: receiving an edge application entity discovery request message, the edge application entity discovery request message includes the first performance requirement and / or the second performance requirement.

[0019] With the above solution, the edge application entity discovers that the request message carries the performance requirements of the terminal device entity, thereby saving signaling resources.

[0020] In combination with the first aspect, in some implementations of the first aspect, the first information includes at least one of the following information: the identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, the service attributes of the terminal device entity, the moment when the terminal device entity is connected or disconnected from the first edge application entity, and the time period when the terminal device entity is connected to the first edge application entity.

[0021] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending second information, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the terminal device entity is connected or disconnected from the first edge application entity.

[0022] Through the above solution, the first entity instructs the terminal device entity to inform the first entity when the terminal device entity is connected to or disconnected from the first edge application entity, so that the first entity can maintain the current available resources of the first edge application entity.

[0023] In combination with the first aspect, in some implementations of the first aspect, sending the second information includes: sending an edge application entity discovery response message, where the edge application entity discovery response message includes the second information.

[0024] With the above solution, the edge application entity discovers that the response message carries the second information, thereby saving signaling resources.

[0025] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending third information, the third information including information of a second edge application entity, and the second edge application entity is different from the first edge application entity.

[0026] Through the above solution, the first entity can recommend other edge application entities suitable for the terminal device entity to the terminal device entity.

[0027] In combination with the first aspect, in some implementations of the first aspect, the method also includes: sending fourth information, the fourth information is used to subscribe to a first event of the terminal device entity, the first event indicates that the connection between the terminal device entity and the first edge application entity is disconnected, and the fourth information includes the identification ID of the terminal device entity and / or the address of the terminal device entity.

[0028] Through the above solution, the first entity can subscribe to the core network for the connection disconnection event between the terminal device entity and the first edge application entity, thereby maintaining the current available resources of the first edge application entity when the connection between the terminal device entity and the first edge application entity is disconnected.

[0029] In combination with the first aspect, in some implementations of the first aspect, receiving the first information includes: receiving the first information sent by the core network element / entity, the first information indicating that the terminal device entity is disconnected from the first edge application entity.

[0030] In combination with the first aspect, in some implementations of the first aspect, when the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in the performance requirement of the terminal device entity, and the change in the performance requirement is from the third performance requirement to the fourth performance requirement.

[0031] Through the above solution, when the performance requirement of the terminal device entity changes, the change in the performance requirement is notified to the first entity, thereby dynamically maintaining the current available resources of the first edge application entity.

[0032] In combination with the first aspect, in some implementation methods of the first aspect, based on the first resource and first information that can be provided by the first edge application entity, the second resource that can be provided by the first edge application entity is determined, including: determining the second resource based on the first resource, the fifth resource and the sixth resource, the fifth resource being the resource corresponding to the third performance requirement of the terminal device entity, and the sixth resource being the resource corresponding to the fourth performance requirement of the terminal device entity.

[0033] Through the above solution, the first entity can update the resources currently available to the first edge application entity based on changes in performance requirements, thereby dynamically maintaining the currently available resources of the first edge application entity.

[0034] Optionally, the second resource is equal to the first resource minus the fifth resource plus the sixth resource.

[0035] In combination with the first aspect, in some implementations of the first aspect, the first information includes at least one of the following information: the identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, and the service attributes of the terminal device entity.

[0036] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending second information, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the performance requirements of the terminal device entity change.

[0037] Through the above solution, the first entity instructs the terminal device entity to inform the first entity when the performance requirements of the terminal device entity change, so that the first entity can maintain the current available resources of the first edge application entity.

[0038] In combination with the first aspect, in some implementations of the first aspect, sending the second information includes: sending an edge application entity discovery response message, where the edge application entity discovery response message includes the second information.

[0039] With the above solution, the edge application entity discovers that the response message carries the second information, thereby saving signaling resources.

[0040] In a second aspect, a method for determining resources is provided, which can be executed by a second entity, or by a chip or circuit configured in the second entity, which is not limited in this application. Optionally, the second entity is a terminal device entity.

[0041] The method includes: receiving second information, the second message being used to instruct the terminal device entity to send first information to the edge enabling entity when the terminal device entity is connected to or disconnected from the first edge application entity, or being used to instruct the terminal device entity to send first information to the edge enabling entity when the performance requirements of the terminal device entity change, the first information being used to determine changes in resources provided by the first edge application entity to the terminal device entity.

[0042] In combination with the second aspect, in some implementations of the second aspect, the first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connected or disconnected.

[0043] In combination with the second aspect, in some implementations of the second aspect, the method also includes: sending an edge application entity discovery request message, the edge application entity discovery request message indicates a first performance requirement and / or a second performance requirement, the first performance requirement is the performance requirement after the terminal device entity is connected to the first edge application entity, and the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity.

[0044] In combination with the second aspect, in some implementations of the second aspect, the first information includes at least one of the following information: the identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, the service attributes of the terminal device entity, the moment when the terminal device entity is connected or disconnected from the first edge application entity, and the time period when the terminal device entity is connected to the first edge application entity.

[0045] In combination with the second aspect, in some implementations of the second aspect, when the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in the performance requirement of the terminal device entity, and the change in the performance requirement is from the third performance requirement to the fourth performance requirement.

[0046] In combination with the second aspect, in some implementations of the second aspect, the first information includes at least one of the following information: the identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, and the service attributes of the terminal device entity.

[0047] According to a third aspect, a communication device is provided. The device may be an edge enabling entity or a module (eg, a chip or a circuit) of the edge enabling entity.

[0048] The device includes: a receiving unit for receiving first information, the first information being used to determine a change in resources provided by a first edge application entity to a terminal device entity; and determining a second resource that can be provided by the first edge application entity based on the first resource and the first information that can be provided by the first edge application entity.

[0049] In a possible implementation, the first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connected or disconnected.

[0050] In one possible implementation, the device also includes: a processing unit, used to control the device to obtain a first performance requirement of the terminal device entity, the first performance requirement being the performance requirement after the terminal device entity is connected to the first edge application entity; the processing unit is also used to determine a second resource based on the first resource and the third resource when the first information indicates that the terminal device entity and the first edge application entity are about to be connected or are already connected, the third resource being the resource corresponding to the first performance requirement of the terminal device entity.

[0051] In one possible implementation, the processing unit is also used to control the device to obtain a second performance requirement of the terminal device entity, where the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity; the processing unit is also used to determine the second resource based on the first resource and the fourth resource when the first information indicates that the terminal device entity is about to be disconnected from the first edge application entity or has been disconnected, where the fourth resource is the resource corresponding to the second performance requirement of the terminal device entity.

[0052] In a possible implementation manner, the processing unit is further configured to control the receiving unit to receive an edge application entity discovery request message, where the edge application entity discovery request message includes the first performance requirement and / or the second performance requirement.

[0053] In one possible implementation, the first information includes at least one of the following information: an identification ID of the terminal device entity, an identification ID of the first edge application entity, an address of the first edge application entity, performance requirements of the terminal device entity, service attributes of the terminal device entity, a moment when the terminal device entity is connected or disconnected from the first edge application entity, and a time period when the terminal device entity is connected to the first edge application entity.

[0054] In a possible implementation, the apparatus further includes: a sending unit, configured to send second information, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the terminal device entity is connected to or disconnected from the first edge application entity.

[0055] In a possible implementation manner, the sending unit is further configured to send an edge application entity discovery response message, where the edge application entity discovery response message includes the second information.

[0056] In a possible implementation, the sending unit is further configured to send third information, where the third information includes information about a second edge application entity, and the second edge application entity is different from the first edge application entity.

[0057] In one possible implementation, the sending unit is also used to send fourth information, which is used to subscribe to a first event of the terminal device entity, the first event indicating that the connection between the terminal device entity and the first edge application entity is disconnected, and the fourth information includes the identification ID of the terminal device entity and / or the address of the terminal device entity.

[0058] In a possible implementation, the receiving unit is further configured to receive first information sent by a core network element / entity, where the first information indicates that the terminal device entity is disconnected from the first edge application entity.

[0059] In a possible implementation, when the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in a performance requirement of the terminal device entity, where the change in the performance requirement is from a third performance requirement to a fourth performance requirement.

[0060] In one possible implementation, the processing unit is also used to control the device to determine the second resource based on the first resource, the fifth resource and the sixth resource, the fifth resource is the resource corresponding to the third performance requirement of the terminal device entity, and the sixth resource is the resource corresponding to the fourth performance requirement of the terminal device entity.

[0061] In one possible implementation, the first information includes at least one of the following information: an identification ID of the terminal device entity, an identification ID of the first edge application entity, an address of the first edge application entity, performance requirements of the terminal device entity, and service attributes of the terminal device entity.

[0062] In a possible implementation, the sending unit is further configured to send second information, where the second information is configured to instruct the terminal device entity to send the first information to the edge enabling entity when a performance requirement of the terminal device entity changes.

[0063] In a possible implementation manner, the sending unit is further configured to send an edge application entity discovery response message, where the edge application entity discovery response message includes the second information.

[0064] In a fourth aspect, a communication device is provided. The device may be a terminal device entity or a module (eg, a chip or circuit) of the terminal device entity.

[0065] The device includes: a receiving unit for receiving second information, the second message being used to instruct the terminal device entity to send first information to the edge enabling entity when the terminal device entity is connected to or disconnected from the first edge application entity, or being used to instruct the terminal device entity to send first information to the edge enabling entity when the performance requirements of the terminal device entity change, the first information being used to determine changes in resources provided by the first edge application entity to the terminal device entity.

[0066] In a possible implementation, the first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connected or disconnected.

[0067] In one possible implementation, the device also includes: a sending unit, used to send an edge application entity discovery request message, the edge application entity discovery request message indicates a first performance requirement and / or a second performance requirement, the first performance requirement is the performance requirement after the terminal device entity is connected to the first edge application entity, and the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity.

[0068] In one possible implementation, the first information includes at least one of the following information: an identification ID of the terminal device entity, an identification ID of the first edge application entity, an address of the first edge application entity, performance requirements of the terminal device entity, service attributes of the terminal device entity, a moment when the terminal device entity is connected or disconnected from the first edge application entity, and a time period when the terminal device entity is connected to the first edge application entity.

[0069] In a possible implementation, when the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in a performance requirement of the terminal device entity, where the change in the performance requirement is from a third performance requirement to a fourth performance requirement.

[0070] In one possible implementation, the first information includes at least one of the following information: an identification ID of the terminal device entity, an identification ID of the first edge application entity, an address of the first edge application entity, performance requirements of the terminal device entity, and service attributes of the terminal device entity.

[0071] In a fifth aspect, a communication device is provided, comprising a processor coupled to a memory, and configured to execute the method of any possible implementation of the first aspect. In one possible implementation, the memory is included in the communication device. In another possible implementation, the communication device further comprises a communication interface, and the processor is coupled to the communication interface.

[0072] In one implementation, the communication device is a first entity. When the communication device is the first entity, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0073] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0074] In a sixth aspect, a communication device is provided, comprising a processor coupled to a memory, and configured to execute the method of any possible implementation of the second aspect. In one possible implementation, the memory is included in the communication device. In another possible implementation, the communication device further comprises a communication interface, and the processor is coupled to the communication interface.

[0075] In one implementation, the communication device is a second entity. When the communication device is a second entity, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0076] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0077] In a seventh aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the method of any of the first and second aspects, and any possible implementation of the aforementioned aspects, is implemented.

[0078] In a specific implementation, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0079] In an eighth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the method of any one of the first and second aspects, and any possible implementation of any of the above aspects.

[0080] In a possible implementation, there are one or more processors and one or more memories.

[0081] In a possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0082] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0083] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0084] The processor in the above aspects can be a chip, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0085] In the ninth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when run, enables a computer to execute any one of the first to second aspects, as well as any possible implementation method of the above aspects.

[0086] In the tenth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions). When the computer program is run on a computer, the computer executes any one of the first to second aspects above, as well as any possible implementation of the above aspects.

[0087] In the eleventh aspect, a chip system is provided, comprising a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a communication device equipped with the chip system executes any one of the first to second aspects above, as well as a method in any possible implementation of the above aspects.

[0088] Among them, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0089] In a twelfth aspect, a communication system is provided, comprising at least one of the aforementioned terminal device entity and edge enabling entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] FIG1 is a schematic diagram of an example of a communication system to which the present application is applied.

[0091] FIG2 is a schematic diagram of an example of a communication system to which the present application is applied.

[0092] FIG3 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0093] FIG4 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0094] FIG5 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0095] FIG6 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0096] FIG7 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0097] FIG8 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0098] FIG9 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0099] FIG10 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0100] FIG11 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0101] FIG12 is a schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0102] The technical solution in this application will be described below with reference to the accompanying drawings.

[0103] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), fifth generation (5G) system or new radio (NR) or other evolved communication systems.

[0104] Figure 1 is a schematic diagram of a network architecture 100. Various embodiments of the present application can be applied to the network architecture shown in Figure 1. The various parts involved in the network architecture shown in Figure 1 are described below.

[0105] 1. Terminal equipment.

[0106] The terminal device may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0107] The terminal device may be a device that provides voice / data connectivity to users, such as a handheld device or vehicle-mounted device with wireless connection function. At present, some examples of terminal devices are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). network, PLMN) and other terminal devices, etc., are not limited to this.

[0108] The terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for everyday wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are full-featured, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that focus on a certain type of application function and can be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0109] In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.

[0110] 2. (Radio) Access Network (R)AN): This provides network access for authorized users in a specific area and utilizes transmission tunnels of varying quality based on user level and service requirements. (R)AN network elements manage radio resources, provide access services to terminal devices, and forward control signals and user data between terminal devices and the core network. Specifically, the (R)AN can also be understood as the base station within the (R)AN and can be referred to as access network equipment.

[0111] Specifically, the access network device can be a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (for example, home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless controller in a cloud radio access network (CRAN) scenario, or the access network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and an access network device in a 5G network or an access network device in a future evolved public land mobile network (PLMN) network, etc. It can be an access point (AP) in a WLAN, or a gNB in ​​a new radio system (NR) system, and the embodiments of the present application are not limited. In a network structure, the access network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a RAN device including a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node.

[0112] 3. Access and Mobility Management Function (AMF): Mainly used for mobility management and access management. Specifically, AMF can be used to implement other functions of the Mobility Management Entity (MME) in addition to session management, such as lawful interception or access authorization (or authentication).

[0113] 4. Session Management Function (SMF): Also known as the session management function network element, it is primarily responsible for session management, Internet Protocol (IP) address allocation and management for terminal devices, selection of endpoints for manageable user plane functions, policy control, or charging function interfaces, and downlink data notification. Specifically, source session management network element 110, anchor session management network element 120, and target session management network element 190 in Figure 1 can all be SMFs.

[0114] It should be understood that in the above system architecture 100, the access network device 120 can be the RAN in Figure 2; the access and mobility management network element 130 can be the AMF in Figure 2; and the session management network element 140 can be the SMF in Figure 2, without limitation.

[0115] Optionally, the system architecture 200 may further include:

[0116] 5. User plane function (UPF): Also known as user plane function, user plane network element, or user plane function network element, it is used for packet routing and forwarding, or quality of service (QoS) processing of user plane data.

[0117] 6. Data network (DN): A network used to provide data transmission, such as the Internet.

[0118] 7. Authentication server function (AUSF): mainly used for user authentication, etc.

[0119] 8. Policy control function (PCF): A unified policy framework used to guide network behavior and provide policy rule information to control plane functional network elements (such as AMF, SMF network elements, etc.).

[0120] 9. Unified data management (UDM): used to handle user identification, access authentication, registration, or mobility management.

[0121] 10. Application Function (AF): This function primarily supports interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. It can be understood as a third-party server, such as an application server on the Internet, providing relevant service information, including providing service quality requirement information corresponding to the service to the PCF, and sending user plane data information of the service to the PSA-UPF. The AF can be a service provider (CP).

[0122] 11. Network slice selection function (NSSF): used to select network slices.

[0123] In this system architecture 100, the N1 interface is the reference point between the terminal device and the AMF; the N2 interface is the reference point between the (R)AN and the AMF, used for sending non-access stratum (NAS) messages, etc.; the N3 interface is the reference point between the (R)AN and the I-UPF, used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF and the I-UPF, used for transmitting information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages; the N5 interface is the reference point between the PCF and the AF; the N6 interface is the reference point between the UPF and the DN, used for transmitting user plane data, etc.; the N7 interface is the reference point between the SMF and the PCF; the N8 interface is the reference point between the AMF and the UDM; the N9 interface is the reference point between the UPF; the N10 interface is the reference point between the SMF and the UDM; the N11 interface is the reference point between the AMF and the SMF; the N12 interface is the reference point between the AMF and the AUSF; and the N22 interface is the reference point between the AMF and the NSSF.

[0124] It should be understood that the above-mentioned system architecture 100 is only an example of a network architecture described from the perspective of a reference point architecture. The network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0125] It should be noted that the interface names between the various network elements in Figure 1 are only examples. The names of the interfaces in specific implementations may be other names, and the embodiments of the present application do not specifically limit this.

[0126] It should be noted that the names of the various network elements (such as SMF, AF, UPF, etc.) included in Figure 1 are only examples and do not limit the functions of the network elements themselves. In 5G networks and other future networks, the above-mentioned network elements may also have other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or may use other names, etc., which are uniformly explained here and will not be repeated below. In addition, it should be understood that the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0127] The network architecture shown in FIG1 is merely an example, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0128] For example, in some network architectures, network function entities such as AMF, SMF, PCF, and UDM are all called network functions (NF); or, in other network architectures, the collection of AMF, SMF, PCF, UDM, etc. can be called control plane functions.

[0129] Figure 2 shows an application architecture and functional model of Mobile Edge Computing (MEC). The following describes each part involved in the network architecture shown in Figure 2.

[0130] 1. Edge Data Network (EDN): A common understanding is that an EDN corresponds to only one data network, a special local data network (local DN), which can be identified by a Data Network Access Identifier (DNAI) and a DNN. It is a network logical concept. Another understanding of EDN is that the EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center (geographic concept), identified by a DNAI, and can include multiple local data networks.

[0131] 2. Application instance / edge application / edge application server (EAS): An application deployed in an edge data network is called an application instance. Specifically, it refers to an instance of a server application (for example, social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN. An application can deploy one or more EAS in one or more EDNs. EAS deployed and running in different EDNs can be considered as different EAS of an application. They can share a domain name, use an IP address, or use different IP addresses. EAS can also be called edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc.

[0132] 3. Application Client (AC): The UE-side counterpart of edge applications. The AC allows users to access application services from the application server. The AC is a client program running on the terminal. It can connect to the application server in the cloud or to the EAS deployed and running in one or more EDNs.

[0133] 4. Edge Enabler Server (EES): It can provide edge server discovery function for application clients AC deployed in EDN, which can better support the deployment of applications in MEC.

[0134] It can support the registration of edge applications, authentication and authorization of UEs, and provide UEs with the IP address information of application instances. It can also further support obtaining the identification and IP address information of application instances, and further provide the EES configuration file (i.e., EES profile, including the EES identification, EES address information, and the EAS identification registered on the EES) to the edge configuration server through an EES registration request message. EES is deployed in the EDN. Generally, an 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, and the EES controls / manages the EAS registered / configured on the EES.

[0135] 5. Edge Enabler Client (EEC): This is the UE-side counterpart of the EES. The EEC is responsible for registering EEC information and application client information with the EES, performing security authentication and authorization, obtaining the EAS IP address from the EES, and providing edge computing capabilities to the application client, such as returning the EAS IP address to the application client through the EAS discovery process.

[0136] 6. Edge Configuration Server (ECS): Responsible for EDN configuration, such as providing EES information to UEs. The EES registers the EES configuration file (i.e., EES profile) on the ECS through the EES registration process. The EEC performs the EES discovery process (service provisioning) on ​​the ECS to discover EES information with the required EAS ID (i.e., the EES has the required EAS information for registration, management, or storage).

[0137] Application users sign a service agreement with the application provider to provide services to the application users. Application users log in to the application client AC on the terminal and communicate with the edge application EAS through the connection between the application client AC and the edge application EAS. The edge enabling client EEC is a middleware layer, generally located in the operating system or between the application client and the operating system. The application client AC can obtain edge enabling services from the edge enabling client EEC in the form of an application programming interface (API).

[0138] The present application provides a plurality of resource determination methods, through which the edge enabling server EES dynamically maintains / determines / updates the resource usage of the server EAS based on the connection information of the application client, the business attribute information of the application client, and the resource information of the edge server EAS.

[0139] It should be understood that the description of the specific scenarios in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0140] It should be understood that the names of all nodes and messages in this application are merely names set for the convenience of description in this application. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as a method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0141] The following describes in detail various communication methods provided in the embodiments of the present application with reference to the accompanying drawings.

[0142] It should be understood that the step numbers in the embodiments of the present application are for illustration only and do not limit the order in which the steps occur.

[0143] FIG3 shows a resource determination method 300 provided in the present application. The method 300 includes at least part of the method shown in FIG3 .

[0144] S310 (optional step): The edge enabling entity obtains a first performance requirement and / or a second performance requirement of a terminal device entity.

[0145] The first performance requirement is the performance requirement after the terminal device entity is connected to the first edge application entity, and the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity.

[0146] Optionally, the edge enabling entity receives an edge application entity discovery request message sent by the terminal device entity, where the edge application entity discovery request message includes the first performance requirement and / or the second performance requirement. Optionally, the terminal device entity may also send the first performance requirement and / or the second performance requirement to the edge enabling entity through other messages.

[0147] Optionally, the edge application entity discovery request message includes attributes of the terminal device entity service / a first performance requirement after the terminal device entity is connected. The first performance requirement can be static or dynamic (and can be included in the AC service KPI). Dynamic performance requirements refer to performance requirements that change over time after the application is connected, such as resource consumption during the waiting time after connection or resource consumption during the running time after connection.

[0148] Exemplarily, the first performance requirement may include a performance requirement at a certain time period or a certain moment after the terminal device entity is connected to the first edge application entity.

[0149] Optionally, the first performance requirement may be expressed as a performance requirement that the terminal device entity requires the first edge application entity to provide, or in other words, the first performance requirement may be expressed as a resource that the terminal device entity requires the first edge application entity to provide.

[0150] Exemplarily, the first performance requirement is a variable value. For example, from time period t1 to t2, the resources required by the terminal device entity are X1; and from time period t2 to t3, the resources required by the terminal device entity are X2.

[0151] Exemplarily, the first performance requirement is a static value. For example, the first performance requirement is expressed as the maximum value of resources required by the terminal device entity.

[0152] The edge enabling entity can obtain the first performance requirement and / or the second performance requirement through the attributes of the terminal device entity service / the performance requirements after the terminal device entity is connected.

[0153] S320: The edge enabling entity receives first information, where the first information is used to determine a change in resources provided by the first edge application entity to the terminal device entity.

[0154] In one implementation, the edge enabling entity receives first information, where the first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connection or disconnection.

[0155] Optionally, the edge enabling entity receives a message carrying the first information, and obtains the first information through the message.

[0156] Optionally, the edge enabling entity receives the message carrying the first information, and the message name of the message indicates the first information.

[0157] For example, the message name of the message is a connection notification indication message. After receiving the connection notification indication message, the edge enabling entity can know that the terminal device entity and the first edge application entity are about to be connected or have been connected.

[0158] For another example, the message name is a disconnection notification indication message. After receiving the disconnection notification indication message, the edge enablement entity can know that the terminal device entity and the first edge application entity will be disconnected or have been disconnected.

[0159] Optionally, the edge enabling entity receives first information sent by the terminal device entity.

[0160] Exemplarily, the terminal device entity is preparing to connect or is connected to the first edge application entity, and sends first information to the edge enabling entity, and the first information is used to inform the edge enabling entity that the terminal device entity and the first edge application entity will be connected or are already connected; and / or, the terminal device entity is preparing to disconnect or is disconnected from the first edge application entity, and sends first information to the edge enabling entity, thereby informing the edge enabling entity that the terminal device entity and the first edge application entity will be disconnected or are already disconnected.

[0161] Optionally, when the first information indicates that the terminal device entity is about to be connected to or is already connected to the first edge application entity, the first information includes at least one of the following information:

[0162] The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity (including the first performance requirements), the service attributes of the terminal device entity, the moment when the terminal device entity is connected to the first edge application entity, and indication information that the terminal device entity and the first edge application entity will be connected or are already connected.

[0163] Optionally, when the first information indicates that the terminal device entity is about to be disconnected from the first edge application entity or has been disconnected, the first information includes at least one of the following information:

[0164] The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity (including the second performance requirements), the service attributes of the terminal device entity, the moment when the terminal device entity is disconnected from the first edge application entity, and indication information that the terminal device entity will be disconnected or has been disconnected from the first edge application entity.

[0165] Optionally, before the edge enabling entity receives the first information sent by the terminal device entity, the edge enabling entity sends second information to the terminal device entity, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the terminal device entity is connected or disconnected from the first edge application entity.

[0166] Optionally, the edge enabling entity receives first information sent by a core network device / entity / network element.

[0167] Exemplarily, when the terminal device entity is disconnected from the first edge application entity, the core network device / entity / network element sends a first message to the edge enabling entity to inform the edge enabling entity that the terminal device entity is disconnected from the first edge application entity.

[0168] Optionally, before the edge enabling entity receives the first information sent by the core network device / entity / network element, the edge enabling entity sends fourth information to the core network device / entity / network element, and the fourth information is used to subscribe to the first event of the terminal device entity. The first event indicates the connection status between the terminal device entity and the first edge application entity. The first subscription information includes the identification ID of the terminal device entity and / or the address of the terminal device entity.

[0169] Optionally, the core network device / entity / network element is a Network Exposure Function (NEF) or a PCF.

[0170] In another implementation, when the terminal device entity is in a connected state with the first edge application entity, the edge enabling entity receives first information sent by the terminal device entity, and the first information indicates a change in the performance requirement of the terminal device entity, and the change in the performance requirement is from a third performance requirement to a fourth performance requirement.

[0171] It should be understood that if the service requirements of the terminal device entity change and its performance requirements also change, the first information is sent to the edge enabling entity to inform the edge enabling entity of the change in the performance requirements of the terminal device entity.

[0172] Optionally, when the first information indicates a change in the performance requirement of the terminal device entity, the first information includes at least one of the following information:

[0173] The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity (including the fourth performance requirement), and the service attributes of the terminal device entity.

[0174] The fourth performance requirement is a performance requirement after the performance requirement of the terminal device entity changes. Similar to the first performance requirement, the fourth performance requirement can be static or dynamic. For example, the fourth performance requirement can include a performance requirement for a certain time period or a certain moment after the performance requirement of the terminal device entity changes.

[0175] S330: The edge enabling entity determines a second resource that can be provided by the first edge application entity according to the first information and the first resource that can be provided by the first edge application entity.

[0176] Optionally, the first resource is a maximum available resource of the first edge application entity, or the first resource is an available resource of the first edge application entity maintained before the edge enabling entity receives the first information.

[0177] In one implementation, the first information indicates that the terminal device entity is connected to the first edge application entity. The edge enabling entity may determine a second resource that the first edge application entity can provide based on the first performance requirement and the first resource that the first edge application entity can provide.

[0178] Optionally, the second resource is equal to the first resource minus the third resource, and the third resource is the resource corresponding to the first performance requirement of the terminal device entity.

[0179] In another implementation, the first information indicates that the terminal device entity is disconnected from the first edge application entity.The edge enabling entity may determine a second resource that the first edge application entity can provide based on the second performance requirement and the first resource that the first edge application entity can provide.

[0180] Optionally, the second resource is equal to the first resource plus a fourth resource, and the fourth resource is a resource corresponding to the second performance requirement of the terminal device entity.

[0181] In another implementation, the first information indicates a change in a performance requirement of the terminal device entity, where the change in performance requirement is from a third performance requirement to a fourth performance requirement. The edge enabling entity may determine a second resource that the first edge application entity can provide based on the third performance requirement, the fourth performance requirement, and the first resource that the first edge application entity can provide.

[0182] Optionally, the second resource is equal to the first resource minus the fifth resource plus the sixth resource, the fifth resource is the resource corresponding to the third performance requirement of the terminal device entity, and the sixth resource is the resource corresponding to the fourth performance requirement of the terminal device entity.

[0183] Optionally, the resources that need to be increased or decreased for the terminal device entity can be determined based on the difference between the third performance requirement and the fourth performance requirement, and the resources corresponding to the difference can be increased or decreased based on the available resources of the currently maintained first edge application entity to obtain the second resource.

[0184] Through the above method, the edge enabling entity learns that the connection status between the terminal device entity and the first edge application entity has changed, or the performance requirements of the terminal device entity have changed, then the resources that can be provided by the first edge application entity have changed, and the edge enabling entity can determine the second resource that can currently be provided by the changed first edge application entity based on the first information and the first resource that can currently be provided by the first edge application entity.

[0185] The following uses the first edge application entity as EAS, the edge enabling entity as EES, and the terminal device entity as AC / EEC as an example to explain the method of the present application in detail with reference to specific examples. It should be noted that the operations performed by the AC or EEC can be regarded as the operations performed by the terminal device entity. That is, in the following description, both AC and EEC can be replaced by the terminal device entity.

[0186] FIG4 shows a resource determination method 400 provided in the present application. The method 400 includes at least part of the method shown in FIG4 .

[0187] It should be understood that method 400 is a specific implementation of method 300 .

[0188] S410, EAS registration, EES obtains resources that EAS can provide; EES registration; EES discovery.

[0189] EAS registration: EAS sends an EAS registration request message (or registration update request message) to EES. The request message includes the EAS configuration file (i.e., EAS profile), specifically including the EAS ID, EAS address information (i.e., EAS endpoint), and available resources of EAS (i.e., EAS service KPIs, maximum computing performance and maximum storage capacity that EAS can provide). EES sends an EAS registration response message (or registration update response message) to EAS.

[0190] EES registration: EES sends an EES registration request message (or registration update request message) to ECS. The request message includes the EES configuration file (i.e., EES profile), specifically including the EES ID, EES address information (i.e., EES endpoint), and EAS ID information registered on EES. ECS sends an EES registration response message (or registration update response message) to EES.

[0191] EES discovery: The EEC sends an EES discovery (i.e., service provisioning) request message to the ECS. The request message includes the EEC ID, UE location information, AC profile, etc. The ECS sends an EES discovery response message to the EEC. The response message includes the discovered EES information, i.e., the EES ID, EES address information, etc.

[0192] S420: The EES obtains the first performance requirement of the AC.

[0193] For example, the EES sends an EAS discovery request message through the terminal device entity EEC, where the request message includes the AC's performance requirements, where the performance requirements include the first performance requirements. The present application does not limit the message carrying the first performance requirements, and the message carrying the first performance requirements may be the EAS discovery request message, or may be another message that provides the first performance requirements of the terminal device entity.

[0194] The first performance requirement is the performance requirement after the AC is connected to the EAS.

[0195] Optionally, the EAS discovery request message includes AC service attributes / AC post-connection performance requirements. These performance requirements can be static or dynamic (and can be included in the AC service KPI). Dynamic performance requirements refer to performance requirements that change over time after the application is connected, such as resource consumption during the wait time after connection or resource consumption during the run time after connection.

[0196] S430 , the EEC / AC receives second information from the EES, where the second information is used to instruct the AC to notify the EES when connecting to or disconnecting from the EAS, ie, to send the first information to the EES.

[0197] Optionally, the EEC / AC receives an EAS discovery response message from the EES, where the EAS discovery response message includes discovered EAS information (ie, EAS profile) and the second information.

[0198] The present application does not limit the message that carries the second information. The message that carries the second information may be an EAS discovery response message or other message that carries the second information.

[0199] This application does not limit the execution order of steps S420 and S430.

[0200] S440: The EEC sends first information to the EES, where the first information indicates that the AC and the EAS are about to be connected or have been connected.

[0201] Optionally, the EEC sends an EAS connection notification request message to the EES, where the EAS connection notification request message includes the first information.

[0202] Specifically, after the AC / EEC selects and determines to connect to the EAS based on the EAS(s) information fed back in the EAS discovery response message, the EEC sends the first information to the EES.

[0203] The first information may include at least one of the following information:

[0204] EEC ID, AC ID, EAS information selected for connection (such as EAS identifier, EAS address, etc.), AC service attributes / performance requirements after AC connection (including the first performance requirement), which can be static or dynamic (can be included in the AC service KPI), time information for connecting to EAS (which can be the moment when EAS connection is started, and / or the time period after EAS connection is started), and indication information that AC and EAS will be connected or have been connected.

[0205] For the message carrying the first information, the connection status of the AC and the EAS may be indicated by indication information indicating that the AC and the EAS are about to be connected or have been connected.

[0206] It should be understood that the first performance requirement of the AC may be carried in the EAS discovery request message sent by the EEC to the EES in S420 or in the first information. This application does not limit the name of the message carrying the first performance requirement.

[0207] S450: The EES determines a second resource that can be provided by the EAS based on the first resource and the first information that can be provided by the EAS.

[0208] After receiving the first information, EES calculates and updates the remaining resources of EAS (i.e., the second resources) based on the first resources that EAS can provide (EAS resource information / EAS service KPI carried in the EAS registration request message or the EAS registration update request message, or the EAS resource information currently maintained by EES), and the third resources corresponding to the first performance requirements of AC (resource status required by AC application / AC service KPI), and / or the time information of connecting to EAS.

[0209] Optionally, the remaining resources of the EAS are equal to the first resources minus the third resources.

[0210] It should be understood that the EAS resource information (i.e., EAS service KPI) carried in the EAS registration request message or the EAS registration update request message represents the EAS maximum available resource information; the EAS resource information currently maintained by the EES represents the EAS resource information maintained by the EES before the AC / EEC connects to the EAS, that is, the information represents the latest EAS resource information maintained by the EES before the AC / EEC connects to the EAS.

[0211] For example, after EAS goes online and registers with EES, when there is the first AC / EEC connection, the remaining resources of EAS can be obtained based on the EAS maximum available resource information (i.e., EAS service KPI), the AC's performance requirements, and / or the time information of the connected EAS.

[0212] For example, at a certain moment after the AC is connected to the EAS, the remaining resources of the EAS at that moment can be obtained by subtracting the resources required by the AC at that moment from the maximum available resources of the EAS.

[0213] For example, after EAS goes online and registers with EES, if EAS already maintains information other than the maximum available EAS resources (i.e., EAS service KPI), that is, EES has currently maintained EAS resource information (i.e., it has been previously connected to another AC), EES can obtain the remaining EAS resources based on the currently maintained EAS resource information, the AC's performance requirements, and / or the connected EAS time information.

[0214] For example, at a certain moment after the AC is connected to the EAS, the remaining resources of the EAS at that moment can be obtained by subtracting the resources required by the AC application at that moment from the EAS resource information currently maintained by the EES.

[0215] Optionally, the remaining resources maintained by the EAS may be remaining resources for AC applications, that is, remaining resources at an application granularity.

[0216] Optionally, the remaining resources maintained by the EAS may also be the remaining resources for the EAS server, that is, the remaining resources at the server granularity, that is, the total remaining resources after the EAS provides services for all different ACs.

[0217] S460: The EES sends third information to the EEC, where the third information includes relevant information of other EASs.

[0218] EES can discover and select EAS based on the current EAS resource information and AC demand information, and recommend other EAS suitable for AC applications, such as returning the EAS address to EEC.

[0219] Optionally, the EES sends a response message to the EAS connection notification request message to the EEC. The response message may include a response result, indicating whether the EAS connection notification request message is successful or failed. The response message includes third information.

[0220] This application does not limit the message names of the EAS connection notification request message and its response message. It should be understood that the message name of the EAS connection notification request message is only an example.

[0221] Through the above method, when the AC establishes or is about to establish a connection with the EAS, the EEC sends the first information to the EES, so that the EES can calculate and update the remaining resources of the EAS.

[0222] FIG5 shows a resource determination method 500 provided in the present application. The method 500 includes at least part of the method shown in FIG5 .

[0223] It should be understood that method 500 is a specific implementation of method 300 .

[0224] S510, EAS registration, EES obtains resources that EAS can provide; EES registration; EES discovery.

[0225] Step S510 refers to step S410.

[0226] S520: The EES obtains the second performance requirement of the AC.

[0227] Optionally, the EEC sends an EAS discovery request message (an example of an edge application entity discovery request message) to the EES. The EAS request message includes the performance requirement of the AC, and the performance requirement includes the second performance requirement.

[0228] The second performance requirement is a performance requirement when the terminal device entity is disconnected from the EAS.

[0229] Optionally, the EAS discovery request message includes attributes of the AC service / performance requirements when the AC is disconnected. The performance requirements may be performance requirements when the application is disconnected, such as resource consumption when the connection is disconnected.

[0230] S530: The EES sends a second message to the EEC / AC, where the second message is used to instruct the AC and the EAS to notify the EES when they are about to be disconnected or have been disconnected.

[0231] For example, when the second information indicates that the AC and the EAS are about to be disconnected or have been disconnected, the first information is sent to the EES, where the first information is used to indicate that the AC and the EAS are about to be disconnected or have been disconnected.

[0232] Optionally, the EES sends an EAS discovery response message to the EEC, where the EAS discovery response message includes discovered EAS information (ie, EAS profile) and second information.

[0233] Optionally, the EES sends a response message to the EEC for the EAS connection notification request message. The response message may include a response result, indicating whether the EAS connection notification request message succeeds or fails. The response message also includes second information.

[0234] This application does not limit the bearer message of the second information.

[0235] This application does not limit the execution order of steps S520 and S530.

[0236] S540: The EEC sends first information to the EES, where the first information indicates that the AC and the EAS are about to be connected or have been connected.

[0237] Optionally, the EEC sends an EAS connection notification request message to the EES, where the EAS connection notification request message includes the first information.

[0238] Step S540 refers to step S440. After receiving the first information, the EES can determine the latest remaining resources of the EAS.

[0239] S550: The EEC sends first information to the EES, where the first information indicates that the AC and the EAS are about to be disconnected or have been disconnected.

[0240] Optionally, the EEC sends an EAS disconnection notification request message to the EES, where the EAS disconnection notification request message includes the first information.

[0241] The first information may include at least one of the following information:

[0242] EEC ID, AC ID, EAS information selected for disconnection (such as EAS identifier, EAS address, etc.), AC service attributes / performance requirements after AC connection (including the second performance requirement), which can be static or dynamic (can be included in the AC service KPI), time information for disconnecting the EAS (which can be the moment of disconnecting the EAS), and indication information that the AC and EAS will be disconnected or have been disconnected.

[0243] For the message carrying the first information, the AC and the EAS may use disconnection or disconnected indication information to indicate the connection status of the AC and the EAS.

[0244] It should be understood that the second performance requirement of the AC can be carried in the EAS discovery request message sent by the EEC to the EES in S520, or in the EAS disconnection notification request message in S550. This application does not limit the name of the message carrying the second performance requirement.

[0245] S560: The EES determines a second resource that can be provided by the EAS based on the first resource and the first information that can be provided by the EAS.

[0246] After receiving the first information, EES calculates and updates the remaining resources of EAS (i.e., the second resources) based on the first resources that EAS can provide (EAS resource information currently maintained by EES), the fourth resources corresponding to the second performance requirements of AC (the resource situation required by AC application / AC service KPI), and the time information of disconnecting EAS.

[0247] Optionally, the remaining resources of the EAS are equal to the first resource plus the fourth resource.

[0248] It should be understood that the EAS resource information (i.e., EAS service KPI) carried in the EAS registration request message or the EAS registration update request message represents the EAS maximum available resource information; the EAS resource information currently maintained by the EES represents the EAS resource information maintained by the EES before the AC / EEC connects to the EAS, that is, the information represents the latest EAS resource information maintained by the EES before the AC / EEC connects to the EAS.

[0249] For example, after EAS goes online and registers with EES, when there is the first AC / EEC connection, the remaining resources of EAS can be obtained based on the EAS maximum available resource information (i.e., EAS service KPI), the AC's performance requirements, and / or the time information of the connected EAS.

[0250] For example, when the AC is disconnected from the EAS, the remaining resources of the EAS can be obtained by subtracting the resources required by the AC at that moment from the maximum available resources of the EAS.

[0251] For example, after EAS goes online and registers with EES, if EAS already maintains resource information other than the EAS maximum available resource information (i.e., EAS service KPI), that is, EES has currently maintained EAS resource information (i.e., it has been previously connected to another AC), EES can obtain the remaining resources of EAS based on the EAS currently maintained EAS resource information, the resource status information required by the AC application, and / or the time information of the disconnected EAS.

[0252] For example, when the AC is disconnected from the EAS, the EAS resource information currently maintained by the EES is increased by the resources required by the AC application at that moment to obtain the remaining resources of the EAS.

[0253] Optionally, the remaining resources maintained by the EAS may be remaining resources for AC applications, that is, remaining resources at an application granularity.

[0254] Optionally, the remaining resources maintained by the EAS may also be the remaining resources for the EAS server, that is, the remaining resources at the server granularity, that is, the total remaining resources after the EAS provides services for all different ACs.

[0255] S570 , the EES sends a response message to the EEC in response to the EAS disconnection notification request message.

[0256] The EES sends a response message to the EEC in response to the EAS disconnection notification request message. This message may include a response result, indicating whether the EAS disconnection notification request message succeeded or failed. This application does not limit the message names of the EAS disconnection notification request message and its response message. It should be understood that the message name of the EAS disconnection notification request message is only an example.

[0257] Through the above method, after the EEC is disconnected from the EAS, it sends a disconnection notification message to the EES, so that the EES can calculate and update the remaining resources of the EAS.

[0258] FIG6 shows a resource determination method 600 provided in the present application. The method 600 includes at least part of the method shown in FIG6 .

[0259] It should be understood that method 600 is a specific implementation of method 300 .

[0260] S610, EAS registration, EES obtains resources that EAS can provide; EES registration; EES discovery.

[0261] Step S610 refers to step S410.

[0262] S620: The EES obtains the second performance requirement of the AC.

[0263] Step S620 refers to step S520.

[0264] S630, the EES / AF subscribes to the network capability exposure event to the core network, that is, sends the fourth information, the fourth information is used to subscribe to the first event of the terminal device entity, the first event indicates that the terminal device entity is about to be disconnected from the EAS or has been disconnected.

[0265] Optionally, the terminal device entity is a terminal device.

[0266] Optionally, the fourth information includes the identifier of the terminal device entity / the address of the terminal device entity, and the subscribed network event (ie, loss of connectivity event).

[0267] Exemplarily, the EES / AF sends the fourth information to the NEF or PCF of the core network.

[0268] Optionally, the EES / AF sends Nnef_EventExposure_Subscribe to the NEF, including the fourth information.

[0269] Optionally, the EES / AF sends Npcf_EventExposure_Subscribe to the PCF, including the fourth information.

[0270] The present application does not limit the order and location of execution of step S630. For example, the EES / AF may subscribe to events from the core network before, after, or during EAS discovery.

[0271] S640, after the terminal device entity is disconnected from the EAS, the core network element / entity / device sends a first message to the EES, where the first message indicates that the terminal device entity is about to be disconnected from the EAS or has been disconnected.

[0272] The fact that the terminal device entity is about to be disconnected from the EAS or has been disconnected can be understood as the fact that the application AC on the terminal device entity is about to be disconnected from the EAS or has been disconnected.

[0273] S650: The EES determines a second resource that can be provided by the EAS based on the first resource and the first information that can be provided by the EAS.

[0274] Step S650 refers to step S560.

[0275] Through the above method, when the terminal device entity is about to be disconnected from the EAS or has been disconnected, the core network sends the first information to the EES, so that the EES can calculate and update the remaining resources of the EAS.

[0276] FIG7 shows a resource determination method 700 provided in the present application. The method 700 includes at least part of the method shown in FIG7 .

[0277] It should be understood that method 700 is a specific implementation of method 300 .

[0278] Steps S710 to S720 refer to steps S410 to S420.

[0279] S730, the EEC / AC receives second information from the EES, where the second information is used to instruct the AC / EEC to send first information to the EES after connecting to the EAS fed back in the EAS discovery response message when the performance requirement of the AC changes.

[0280] Optionally, the EES sends an EAS discovery response message to the EEC, where the EAS discovery response message includes discovered EAS information (ie, EAS profile) and second information.

[0281] Steps S740 to S750 refer to steps S440 to S450.

[0282] S760: The EES sends third information to the EEC. The third information includes relevant information of other EASs.

[0283] EES can discover and select EAS based on the current EAS resource information and AC demand information, and recommend other EAS suitable for AC applications, such as returning the EAS address to EEC.

[0284] Optionally, the EES sends a response message to the EAS connection notification request message to the EEC. The response message may include a response result, indicating whether the EAS connection notification request message is successful or failed. The response message includes third information.

[0285] Optionally, the response message also includes second information.

[0286] S770, AC performance requirements have changed.

[0287] For example, the first performance requirement is changed to the third performance requirement, or the third performance requirement is changed to the fourth performance requirement. For the description of the fourth performance requirement, refer to method 300.

[0288] The method of the present application is described below by taking the case where the performance requirement of the AC changes from the third performance requirement to the fourth performance requirement as an example.

[0289] S780: The EEC sends first information to the EES. The first information indicates a change in the performance requirement of the AC, where the change in the performance requirement is from the third performance requirement to the fourth performance requirement.

[0290] It should be understood that if the service requirements of the AC change, its performance requirements also change, and the first information is sent to the EES.

[0291] The first information includes at least one of the following information:

[0292] EEC ID, AC ID, EAS information for the selected connection (such as EAS identifier, EAS address, etc.), attributes of the service after the AC changes / performance requirements after the AC changes (including the fourth performance requirement), which can be static or dynamic (can be included in the AC service KPI), and time information when the requirement changes to the fourth performance requirement (which can be the moment when it changes to the fourth performance requirement).

[0293] S790, EES calculates and updates the remaining resources of EAS (i.e., an example of the second resource) based on the currently maintained EAS resource information (an example of the first resource), the fifth resource corresponding to the third performance requirement of AC, the sixth resource corresponding to the fourth performance requirement of AC, and the time information when the requirement changes to the fourth performance requirement.

[0294] Optionally, the remaining resources of the EAS are equal to the current EAS resources minus the fifth resource plus the sixth resource.

[0295] For example, at a certain moment in the second time period after the AC changes to the fourth performance requirement, the remaining resources of the EAS can be obtained by subtracting the resources required by the AC at that moment from the maximum available resources of the EAS.

[0296] Optionally, the remaining resources maintained by the EAS may be remaining resources for AC applications, that is, remaining resources at an application granularity.

[0297] Optionally, the remaining resources maintained by the EAS may also be the remaining resources for the EAS server, that is, the remaining resources at the server granularity, that is, the total remaining resources after the EAS provides services for all different ACs.

[0298] Through the above method, after the AC establishes a connection with the EAS, when the performance requirements change, it sends a message to the EES, so that the EES can calculate and update the remaining resources of the EAS.

[0299] The following uses the first edge application entity as the target EAS (Target EAS, T-EAS), the edge enabling entity as the target EES (Target EES, T-EES), and the terminal device entity as the AC / EEC as an example to describe the method of the present application in detail with reference to specific examples. It should be noted that the operations performed by the AC or EEC can be regarded as operations performed by the terminal device entity. That is, in the following description, both AC and EEC can be replaced by the terminal device entity.

[0300] FIG8 shows a resource determination method 800 provided in the present application. The method 800 includes at least part of the method shown in FIG8 .

[0301] It should be understood that method 800 is a specific implementation of method 300 .

[0302] S810, EAS registration

[0303] Refer to the EAS registration in step S410.

[0304] S820, discovered by T-EES.

[0305] The S-EES sends a target EES discovery (retrieve EES) request message to the ECS, which includes the EES ID, the required EAS ID, etc. The ECS sends a target EES discovery (retrieve EES) response message to the S-EES, which includes the discovered target EES information, namely, the EES ID, the EES address information, etc.

[0306] S830: T-EES obtains the first performance requirement of the AC.

[0307] Optionally, the S-EES sends an EAS discovery request message to the T-EES, the request message including the S-EES ID and the EAS discovery filter. The T-EES sends an EAS discovery response message to the S-EES, the response message including the discovered target EAS information (i.e., the EAS profile). The EAS request message indicates the AC's performance requirements, which include the first performance requirement.

[0308] The description of the first performance requirement refers to method 300 .

[0309] S840 (optional step), the S-EES sends the second information to the EEC. The AC notifies the EES when it is about to connect or has been connected to the EAS, that is, sends the first information to the EES.

[0310] Optionally, the S-EES feeds back the selected target EAS information and / or the target EES information corresponding to the target EAS to the EEC. The feedback message includes the second information.

[0311] S850: The S-EAS sends an ACR status update message to the S-EES. The message is used to notify the S-EES whether the application context of the AC on the S-EAS has been successfully migrated to the T-EAS.

[0312] S860 (optional step): S-EES sends second information to EEC.

[0313] Optionally, the S-EES feeds back an ACR completion notification to the EEC, where the notification includes whether the application context of the AC on the S-EAS has been successfully migrated to the T-EAS, and corresponding T-EAS information. The feedback message includes the second information.

[0314] It should be noted that the S-EES sends the second information to the EEC, and the bearer message of the second information can be any message in S840 or S860.

[0315] S870, T-EES maintains the remaining resource information of T-EAS. For the specific method, refer to steps S440 to S460 in which EES maintains the remaining resource information of EAS.

[0316] FIG9 shows a resource determination method 900 provided in the present application. The method 900 includes at least part of the method shown in FIG9 .

[0317] It should be understood that method 900 is a specific implementation of method 300 .

[0318] Steps S910 to S920 refer to steps S810 to S820.

[0319] S930: T-EES obtains the second performance requirement of the AC.

[0320] Optionally, the S-EES sends an EAS discovery request message to the T-EES, the request message including the S-EES ID and the EAS discovery filter. The T-EES sends an EAS discovery response message to the S-EES, the response message including the discovered target EAS information (i.e., the EAS profile). The EAS request message indicates the AC's performance requirements, which include the second performance requirements.

[0321] The description of the second performance requirement refers to method 300 .

[0322] S940, the S-EES sends the second information to the EEC. The AC notifies the EES when it is about to be disconnected from the EAS or has been disconnected, that is, it sends the first information to the EES.

[0323] Optionally, the S-EES feeds back the selected target EAS information and / or the target EES information corresponding to the target EAS to the EEC. The feedback message includes the second information.

[0324] Step S950 refers to step S850.

[0325] S960: S-EES sends second information to EEC.

[0326] Optionally, the S-EES feeds back an ACR completion notification to the EEC, where the notification includes whether the application context of the AC on the S-EAS has been successfully migrated to the T-EAS, and corresponding T-EAS information. The feedback message includes the second information.

[0327] It should be noted that the S-EES sends the second information to the EEC, and the bearer message of the second information can be any message in S840 or S860.

[0328] S970, T-EES maintains the remaining resource information of T-EAS. For the specific method, refer to steps S550 to S570 in which EES maintains the remaining resource information of EAS.

[0329] FIG10 shows a resource determination method 1000 provided in the present application. The method 1000 includes at least part of the method shown in FIG10 .

[0330] It should be understood that method 1000 is a specific implementation of method 300 .

[0331] Steps 1010 to 1030 refer to steps S910 to S930.

[0332] S1040: The S-EES feeds back the selected target EAS information and / or the target EES information corresponding to the target EAS to the EEC.

[0333] S1050 , the S-EAS sends an ACR status update message to the S-EES. The message is used to notify the S-EES whether the application context of the AC on the S-EAS has been successfully migrated to the T-EAS.

[0334] S1060 , the S-EES feeds back an ACR completion notification to the EEC. The message includes whether the application context of the AC on the S-EAS has been successfully migrated to the T-EAS, and the corresponding T-EAS information.

[0335] S1070, T-EES maintains the remaining resource information of T-EAS. For the specific method, refer to steps S630 to S650 in which EES maintains the remaining resource information of EAS.

[0336] The communication method embodiment of the present application is described in detail above in conjunction with Figures 1 to 10. The communication device embodiment of the present application will be described in detail below in conjunction with Figures 11 and 12. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0337] Figure 11 is a schematic diagram of a communication device provided in an embodiment of the present application. As shown in Figure 11, the communication device 1100 includes a processing module 1110 and a communication module 1120. The communication device 1100 can be a terminal device entity, or a communication device applied to a terminal device entity or used in conjunction with a terminal device entity and capable of implementing a method executed by the terminal device entity, such as a chip, a chip system or a circuit; or the communication device 1100 can be an edge enabling entity, or a communication device applied to an edge enabling entity or used in conjunction with an edge enabling entity and capable of implementing a method executed by the edge enabling entity, such as a chip, a chip system or a circuit;

[0338] The communication module may also be referred to as a transceiver module, transceiver, transceiver, or transceiver device. The processing module may also be referred to as a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to perform the sending and receiving operations of the terminal device entity and the edge-enabled entity in the above method. The device used to implement the receiving function in the communication module can be regarded as the receiving unit, and the device used to implement the sending function in the communication module can be regarded as the sending unit. That is, the communication module includes a receiving unit and a sending unit.

[0339] When the communication device 1100 is applied to a terminal device entity, the processing module 1110 can be used to implement the processing function of the terminal device entity in the above embodiments, and the communication module 1120 can be used to implement the sending and receiving functions of the terminal device entity in the above embodiments.

[0340] When the communication device 1100 is applied to an edge enabling entity, the processing module 1110 can be used to implement the processing function of the edge enabling entity in the above embodiments, and the communication module 1120 can be used to implement the transceiver function of the terminal device entity in the above embodiments.

[0341] In addition, it should be noted that the aforementioned communication module and / or processing module can be implemented by a virtual module, for example, the processing module can be implemented by a software functional unit or a virtual device, and the communication module can be implemented by a software function or a virtual device. Alternatively, the processing module or the communication module can also be implemented by a physical device, for example, if the device is implemented using a chip / circuit (such as an integrated circuit or a logic circuit, etc.). The communication module can be an input and output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module is an integrated processor or microprocessor or circuit (such as an integrated circuit or a logic circuit, etc.).

[0342] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single processor, exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in either hardware or software functional modules.

[0343] FIG12 is a schematic diagram of another communication device provided in an embodiment of the present application. As shown in FIG12 , the communication device 1200 may optionally be a chip or a chip system. Optionally, in the present application, the chip system may be composed of a chip or may include a chip and other discrete devices.

[0344] The communication device 1200 can be used to implement the functions of any device (e.g., terminal device entity, edge enabling entity) in the communication system described in the above examples. The communication device 1200 may include at least one processor 1210. Optionally, the processor 1210 is coupled to a memory, and the memory may be located within the device, or the memory may be integrated with the processor, or the memory may be located outside the device. For example, the communication device 1200 may also include at least one memory 1220. The memory 1220 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 1210 may execute the computer program stored in the memory 1220 to complete the method in any of the above examples.

[0345] The communication device 1200 may also include a communication interface 1230, through which the communication device 1200 can exchange information with other devices. Exemplarily, the communication interface 1230 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 1200 is a chip-type device or circuit, the communication interface 1230 in the device 1200 may also be an input / output circuit that can input information (or receive information) and output information (or send information). The processor 1210 is an integrated processor, microprocessor, integrated circuit, or logic circuit, etc., and the processor can determine output information based on input information.

[0346] Coupling in this application refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. Processor 1210 may operate in conjunction with memory 1220 and communication interface 1230. This application does not limit the specific connection medium between the processor 1210, memory 1220, and communication interface 1230.

[0347] Optionally, as shown in FIG12 , the processor 1210, the memory 1220, and the communication interface 1230 are interconnected via a bus 1240. Optionally, the bus may include an address bus, a data bus, a control bus, or other types of buses. Furthermore, for ease of illustration, FIG12 shows one bus 1240, but this does not mean that there is only one bus or only one type of bus.

[0348] It should be understood that the processors mentioned in the embodiments of the present application may be the following devices or the circuit portions of the following devices used for processing functions: a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0349] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0350] 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, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0351] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0352] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the terminal device entity and the edge enabling entity in the above-mentioned method embodiments.

[0353] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by the terminal device entity and the edge enabling entity in the above-mentioned method embodiments.

[0354] An embodiment of the present application further provides a communication system, which includes the terminal device entity and the edge enabling entity in the above embodiments.

[0355] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above and will not be described again here.

[0356] To facilitate understanding of the above embodiments provided in this application, the following points are explained:

[0357] 1) In this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0358] 2) In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple, respectively.

[0359] 3) The ordinal numbers "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first indication information and the second indication information can be the same information or different information, and such names do not indicate differences in the content, size, application scenario, sender / receiver, priority, or importance of the two messages. In addition, the numbering of the steps in the various embodiments introduced in this application is only for distinguishing different steps and is not used to limit the order of the steps.

[0360] 4) In this application, descriptions such as "when...", "in the case of...", and "if" all mean that the device will perform corresponding processing under certain objective circumstances. They do not limit the time, nor do they require the device to perform judgment actions when implementing them, nor do they mean that there are other limitations.

[0361] 5) In this application, "indicate" or "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and does not necessarily mean that the indication information carries A.

[0362] The indication methods involved in the embodiments of this application should be understood to encompass various methods that enable the party to be indicated to obtain information about the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or timing of these sub-information can be the same or different. This application does not limit the transmission method, for example.

[0363] In the embodiments of the present application, the "indication information" may be an explicit indication, i.e., a direct indication via signaling, or may be obtained based on parameters indicated by the signaling, in combination with other rules, other parameters, or by deduction. It may also be an implicit indication, i.e., based on a rule or relationship, or based on other parameters, or by deduction. This application does not impose specific limitations on this.

[0364] 6) The “protocol” referred to in this application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) th generation, 4G) network, fifth generation (5 th generation, 5G) network protocol, NR protocol, 5.5G network protocol, sixth generation (6 th generation, 6G) network protocols and related protocols used in future communication systems, which are not limited in this application.

[0365] 7) In this application, "communication" may also be described as "data transmission", "information transmission", "data processing", etc. "Transmission" includes "sending" and "receiving".

[0366] 8) In this application, "sending information to XX (device)" can be understood as the destination of the information being the device. This can include sending information directly or indirectly to the device. "Receiving information from XX (device)" can be understood as the source of the information being the device, which can include receiving information directly or indirectly from the device. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can still understand the valid information from the source.

[0367] 9) The terms "comprise," "include," and "have," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0368] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0369] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

[0370] It should be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for illustrative description, and the specific form of the devices is not limited in the embodiments of the present application. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0371] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0372] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be described again here.

[0373] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0375] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0376] If the functions are implemented in the form of 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 the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or an edge-enabled entity, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

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

Claims

1. A method for determining resources, characterized in that: include: receiving first information, where the first information is used to determine a change in resources provided by the first edge application entity to the terminal device entity; Based on the first resource that can be provided by the first edge application entity and the first information, a second resource that can be provided by the first edge application entity is determined.

2. The method according to claim 1, characterized in that: The first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connection or disconnection.

3. The method according to claim 2, characterized in that The determining, based on the first resource that can be provided by the first edge application entity and the first information, a second resource that can be provided by the first edge application entity includes: Acquire a first performance requirement of the terminal device entity, where the first performance requirement is a performance requirement after the terminal device entity is connected to the first edge application entity; When the first information indicates that the terminal device entity is to be connected or is connected to the first edge application entity, the second resource is determined based on the first resource and a third resource, and the third resource is a resource corresponding to the first performance requirement of the terminal device entity.

4. The method according to claim 2, characterized in that: The determining, based on the first resource that can be provided by the first edge application entity and the first information, a second resource that can be provided by the first edge application entity includes: Acquire a second performance requirement of the terminal device entity, where the second performance requirement is a performance requirement when the terminal device entity is disconnected from the first edge application entity; When the first information indicates that the terminal device entity is about to be disconnected or has been disconnected from the first edge application entity, the second resource is determined based on the first resource and a fourth resource, and the fourth resource is a resource corresponding to the second performance requirement of the terminal device entity.

5. The method according to claim 3 or 4, characterized in that: The obtaining of the first performance requirement of the terminal device entity and the obtaining of the second performance requirement of the terminal device entity include: An edge application entity discovery request message is received, where the edge application entity discovery request message includes the first performance requirement and / or the second performance requirement.

6. The method according to any one of claims 1 to 5, characterized in that The first information includes at least one of the following information: The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, the service attributes of the terminal device entity, the moment when the terminal device entity is connected to or disconnected from the first edge application entity, the time period when the terminal device entity is connected to the first edge application entity, indication information that the terminal device entity is about to be connected or is already connected to the first edge application entity, and indication information that the terminal device entity is about to be disconnected from or is already disconnected from the first edge application entity.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Sending second information, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the terminal device entity is connected to or disconnected from the first edge application entity.

8. The method according to claim 7, characterized in that The sending of the second information comprises: An edge application entity discovery response message is sent, where the edge application entity discovery response message includes the second information.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Send third information, where the third information includes information of a second edge application entity, where the second edge application entity is different from the first edge application entity.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Send fourth information, where the fourth information is used to subscribe to a first event of the terminal device entity, where the first event indicates that the connection between the terminal device entity and the first edge application entity is disconnected, and the fourth information includes an identification ID of the terminal device entity and / or an address of the terminal device entity.

11. The method according to claim 10, characterized in that The receiving of the first information comprises: Receive the first information sent by a core network element / entity, where the first information indicates that the terminal device entity and the first edge application entity will be disconnected or have been disconnected.

12. The method according to claim 1, characterized in that When the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in a performance requirement of the terminal device entity, where the change in the performance requirement is from a third performance requirement to a fourth performance requirement.

13. The method according to claim 12, characterized in that The determining, based on the first resource that can be provided by the first edge application entity and the first information, a second resource that can be provided by the first edge application entity includes: The second resource is determined based on the first resource, the fifth resource and the sixth resource, the fifth resource being a resource corresponding to the third performance requirement of the terminal device entity, and the sixth resource being a resource corresponding to the fourth performance requirement of the terminal device entity.

14. The method according to claim 12 or 13, characterized in that The first information includes at least one of the following information: The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, and the service attributes of the terminal device entity.

15. The method according to any one of claims 12 to 14, characterized in that The method further comprises: Sending second information, where the second information is used to instruct the terminal device entity to send the first information to the edge enabling entity when the performance requirement of the terminal device entity changes.

16. The method according to claim 15, characterized in that The sending of the second information comprises: An edge application entity discovery response message is sent, where the edge application entity discovery response message includes the second information.

17. The method according to any one of claims 1 to 16, characterized in that The method is applied to an edge enabling entity.

18. A method for determining resources, characterized in that: include: Receive second information, where the second message is used to instruct the terminal device entity to send first information to the edge enabling entity when the terminal device entity is connected to or disconnected from the first edge application entity, or to instruct the terminal device entity to send the first information to the edge enabling entity when the performance requirements of the terminal device entity change, and the first information is used to determine changes in resources provided by the first edge application entity to the terminal device entity.

19. The method according to claim 18, characterized in that The first information indicates a connection status between the terminal device entity and the first edge application entity, where the connection status includes connection or disconnection.

20. The method according to claim 19, characterized in that The method further comprises: Send a first performance requirement and / or a second performance requirement, wherein the first performance requirement is the performance requirement after the terminal device entity is connected to the first edge application entity, and the second performance requirement is the performance requirement when the terminal device entity is disconnected from the first edge application entity.

21. The method according to claim 20, characterized in that The sending of the first performance requirement and / or the second performance requirement includes: An edge application entity discovery request message is sent, where the edge application entity discovery request message includes the first performance requirement and / or the second performance requirement.

22. The method according to any one of claims 18 to 21, characterized in that The first information includes at least one of the following information: The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, the service attributes of the terminal device entity, the moment when the terminal device entity is connected to or disconnected from the first edge application entity, the time period when the terminal device entity is connected to the first edge application entity, indication information that the terminal device entity is about to be connected or is already connected to the first edge application entity, and indication information that the terminal device entity is about to be disconnected from or is already disconnected from the first edge application entity.

23. The method according to claim 18, characterized in that When the terminal device entity is in a connected state with the first edge application entity, the first information indicates a change in a performance requirement of the terminal device entity, where the change in the performance requirement is from a third performance requirement to a fourth performance requirement.

24. The method according to claim 23, characterized in that The first information includes at least one of the following information: The identification ID of the terminal device entity, the identification ID of the first edge application entity, the address of the first edge application entity, the performance requirements of the terminal device entity, and the service attributes of the terminal device entity.

25. The method according to any one of claims 18 to 24, characterized in that The method is applied to a terminal device entity.

26. A communication device, characterized in that: include: A unit for implementing the method of any one of claims 1 to 17; or a unit for implementing the method of any one of claims 18 to 25.

27. A communication device, characterized in that: include: A processor for executing computer instructions stored in the memory, so that the communication device performs the method according to any one of claims 1 to 17, or, So that the communication device performs the method as claimed in any one of claims 18 to 25.

28. The communication device according to claim 27, characterized in that The communication device also includes a memory.

29. The communication device according to claim 27 or 28, characterized in that: The communication device further includes a communication interface, which is coupled to the processor and is used to input and / or output information.

30. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed, Execute the method according to any one of claims 1 to 17, or Execute the method as claimed in any one of claims 18 to 25.

31. A computer program product, characterized in that The computer program product comprises a computer program or instructions, which, when executed, Execute the method according to any one of claims 1 to 17, or Execute the method as claimed in any one of claims 18 to 25.

32. A communication system, characterized in that: include: An apparatus for performing the method as claimed in any one of claims 1 to 17 and an apparatus for performing the method as claimed in any one of claims 18 to 25.

Images