Communication method and related device

Abstract

The embodiment of the invention provides a communication method, and the method comprises the steps: a first computing node subscribes to a mobility event of a terminal device, and determines that a device providing an access service from a first computing service of the terminal device is switched from a first network device to a second network device through second information, and the first computing node can release the first connection between the terminal equipment and the first computing node by sending the third information, so that the situation that a path is not good or unreachable due to the fact that the terminal equipment still tries to be connected with the original computing node is reduced, and the terminal equipment can be conveniently connected with the adaptive computing node subsequently.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0002] In future generations of mobile communication systems, cloud edge nodes may be further decentralized to network access nodes. Therefore, the access network can further undertake some computing functions. Computing nodes with these functions may be units within the base station or external, independent units separate from the base station's logical functions. Computing nodes can be nodes that provide access services for the computing services of terminal devices. Computing services can be understood as independent application processes that implement a set or a specific set of computing functions to solve a specific problem.

[0003] The Domain Name System (DNS) provides the function of resolving application domain names to Internet Protocol (IP) addresses. Terminal devices request the application's domain name from the DNS system and obtain DNS records containing the IP addresses of the computing nodes corresponding to the requested application service. This allows them to subsequently obtain application services from the computing nodes corresponding to those IP addresses. When DNS records can be cached locally and have a lifespan, if the same application service is accessed again within that timeframe, the terminal device directly retrieves the corresponding computing node's IP address from the local DNS cache, thus avoiding the need for the terminal device to query the computing node again and improving the efficiency of the computing node in processing computing services.

[0004] However, as the terminal device moves, the computing nodes adapted to it may change due to its location. Because the DNS cache may still be on the computing nodes accessed in the past, the terminal device may still attempt to connect to the original computing nodes, potentially resulting in suboptimal or unreachable paths. Summary of the Invention

[0005] This application provides a communication method in which a first computing node subscribes to the mobility events of a terminal device and determines, through second information, that the device providing access services for the terminal device's first computing service has switched from a first network device to a second network device. Subsequently, the first computing node can release the first connection between the terminal device and the first computing node by sending third information, thereby reducing the path defects or unreachability caused by the terminal device still trying to connect to the original computing node, and also facilitating the subsequent connection of the terminal device to a compatible computing node.

[0006] This application provides a communication method, which is executed by a first computing node, or by some components (e.g., processor, chip, or chip system) of the first computing node, or by a logic module or software capable of implementing all or part of the functions of the first computing node. In the first aspect and its possible implementations, the method is described as being executed by a first computing node. The first computing node first sends first information to a first network element, the first information being used to subscribe to mobility events of a terminal device. Then, it receives second information, the second information being used to instruct a device providing access services for the first computing service of the terminal device to switch from the first network device to a second network device. After receiving the second information, the first computing node sends third information, the third information being used to instruct the release of the first connection between the terminal device and the first computing node.

[0007] The first network element refers to a network device, terminal device, or gateway, etc. A gateway may include at least one of the following: an application programming interface (API) gateway, an API proxy, a network exposure function (NET) element, etc.

[0008] Furthermore, the first information can also be understood as a subscription request, and the third information can be understood as a connection release request. Sending the third information by the first computing node specifically refers to the first computing node sending third information to the terminal device. For example, the first computing node could send the third information directly to the terminal device, or it could send the third information to the terminal device through a gateway, etc. The specifics are not limited here.

[0009] Based on the above scheme, the first computing node subscribes to the mobility events of the terminal device and determines through the second information that the device providing access services for the first computing service of the terminal device has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending the third information, thereby reducing the path suboptimal or unreachable caused by the terminal device still trying to connect to the original computing node, and also facilitating the terminal device to connect to a new computing node in the future.

[0010] Optionally, in one possible implementation of the first aspect, the aforementioned third information is also used to instruct that a new connection request to the first computing service be initiated after the first connection is released.

[0011] In this possible implementation, the third information sent by the first computing node is used not only to indicate the release of the first connection, but also to re-initiate a connection request to the first computing service. Therefore, after receiving the third information, the terminal device can release the first connection with the first computing node and then re-initiate a connection request to the new computing node through the second network device. This reduces the risk of the terminal device attempting to connect to the original computing node after switching from the first network device to the second network device, thus minimizing the path optimization or unreachability issues caused by the terminal device still trying to connect to the original computing node.

[0012] Alternatively, in one possible implementation of the first aspect, the aforementioned third information is also used to instruct the cleanup of DNS records on the terminal device.

[0013] In this possible implementation, by instructing the terminal device to clear its DNS records through third-party information, the probability of the terminal device still trying to connect to the original computing node can be reduced, and the terminal device can also reselect a computing node that is more suitable for itself, thereby improving the user experience.

[0014] Optionally, in one possible implementation of the first aspect, if the first computing service finishes execution, the aforementioned first computing node sends third information.

[0015] In this possible implementation, releasing the connection after the first computing service has finished executing can improve the service performance of the first computing service.

[0016] Optionally, in one possible implementation of the first aspect, the first computing node described above may receive second information sent by the first network device or the second network device.

[0017] In this possible implementation, the first network device or the second network device can send a mobility event notification to the terminal device fed back by the first computing node, thereby facilitating the timely entry into the connection release phase and improving the efficiency of computing node updates.

[0018] Optionally, in one possible implementation of the first aspect, the first network element is a first network device, a terminal device, or a gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0019] This possible implementation can be applied to various subscription scenarios, such as the scenario where the first computing node initiates a subscription request to the network device, the scenario where the first computing node initiates a subscription request to the network device through the gateway, and the scenario where the first computing node directly initiates a subscription request to the terminal device.

[0020] Optionally, in one possible implementation of the first aspect, the aforementioned first information is further used by the first network element to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are respectively used to subscribe to the mobility events of the terminal device.

[0021] In this possible implementation, the first information can also be obtained by the gateway from multiple subscriptions, thereby reducing the complexity of subsequent network devices maintaining subscriptions.

[0022] Optionally, in one possible implementation of the first aspect, the first computing node specifically receives the second information sent by the first network element. The first computing node specifically sends the third information to the first network element.

[0023] This possible implementation can be applied not only to scenarios where the first network element is the source base station of the terminal device, but also to scenarios with a gateway.

[0024] A second aspect of this application provides a communication method, which is executed by a first network device, or by some components (e.g., a processor, chip, or chip system) of the first network device, or by a logic module or software capable of implementing all or part of the functions of the first network device. In this second aspect and its possible implementations, the method is described as being executed by a first network device. The first network device receives first information sent by a second network element and sends second information to the second network element.

[0025] The first information is used for the first computing node to subscribe to the mobility events of the terminal device, and the first computing node has connected to the service instance of the first computing service. The second information is used to instruct the terminal device to switch from the first network device to the second network device.

[0026] Based on the above scheme, after the first network device receives the subscription information from the second network element, it sends feedback to the second network element that the terminal device has switched from the first network device to the second network device, thereby providing a basis for judgment to facilitate the subsequent release of the connection between the first computing node and the terminal device.

[0027] Optionally, in one possible implementation of the second aspect, when the second network device supports a service instance of the first computing service, the first network device sends the second information to the second network element.

[0028] In this possible implementation, when it is determined that there is an instance supporting the first computing service, the second information is fed back to the second network element. By limiting the conditions for feeding back the second information, the timing of the feedback of the second information can be clarified, reducing the situation where there are no suitable computing nodes after the connection is released.

[0029] Optionally, in one possible implementation of the second aspect, the first network device receives second indication information sent by the second network device, the second indication information being used to indicate that the second network device supports a service instance of the first computing service.

[0030] In this possible implementation, the first network device can directly determine whether the second network device supports the instance of the first computing service through the second indication information, thereby reducing the latency or efficiency problems caused by the first network device probing the instance itself.

[0031] Optionally, in one possible implementation of the second aspect, the first network device first determines at least one service instance supported by the second network device; then determines that the at least one service instance includes a service instance of the first computing service.

[0032] In this possible implementation, the first network device can first determine at least one instance supported by the second network device, and then determine whether the at least one instance includes an instance that supports the first computing service, thereby reducing the situation where there are no suitable computing nodes after the connection is released.

[0033] Optionally, in one possible implementation of the second aspect, the first network device may further send a third request message to the second network device, the third request message being used to request the second network device to provide access service for the first computing service; the first network device receives a response message to the third request message sent by the second network device, the response message being used to indicate acceptance of the request to switch the first computing service.

[0034] In this possible implementation, the first network device can determine whether the first computing service has a connectable service instance based on the response information of the third request information, thereby ensuring the normal computing of the first computing service and improving the user experience.

[0035] Optionally, in one possible implementation of the second aspect, the aforementioned response information is also used to indicate whether the second network device supports a service instance of the first computing service.

[0036] In this possible implementation, the first network device can also determine whether the second network device supports the instance of the first computing service through response information, so that when switching to the second network device, the normal operation of the first computing service is not affected, thus improving the user experience.

[0037] Alternatively, in one possible implementation of the second aspect, the aforementioned response information is also used to indicate the service instance identifier that the second network device is connecting to.

[0038] In this possible implementation, the first network device can first learn about the instance connected by the second network device through the response information, which makes it easier to find a suitable instance for the first computing service in the future.

[0039] Optionally, in one possible implementation of the second aspect, the first network device may also determine whether the second network device has a service instance of the first computing service that meets the service requirements of the first computing service, based on the service requirements of the first computing service.

[0040] In this possible implementation, when determining the instance support status of other network devices, the first network device can guarantee the service quality of the first computing service by considering the business requirements of the first computing service.

[0041] Optionally, in one possible implementation of the second aspect, the aforementioned second network element is a first computing node or a gateway, the gateway being used to aggregate multiple first request information from multiple computing nodes, the multiple first request information being used to subscribe to mobility events of terminal devices.

[0042] This possible implementation can be applied to various transmission scenarios, such as a transmission scenario where the terminal device and the network device are directly connected, or a transmission scenario where the terminal device and the network device are indirectly connected through a gateway.

[0043] Optionally, in one possible implementation of the first or second aspect, the aforementioned second information is further used to indicate that the second network device supports a service instance of the first computing service.

[0044] In this possible implementation, by indicating the instance that meets the requirements through the second information, the second network element can find an instance that is compatible with the first computing node, thereby improving the user experience.

[0045] Optionally, in one possible implementation of the first aspect or the second aspect, the first information mentioned above includes at least one of the following: first indication information, the identifier of the terminal device, the identifier of the first computing service, and the transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0046] In this possible implementation, the first information of the mobility event of the subscribing terminal device can also include indicators, transmission requirements, etc. This makes it easier for the first network device to determine whether the second network device is compatible with the relevant requirements, reducing service quality degradation caused by handover.

[0047] Optionally, in one possible implementation of the first or second aspect, the second information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, and an identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0048] Optionally, in one possible implementation of the first aspect or the second aspect, the first connection described above includes at least one of the following: a transport layer connection and an application layer connection.

[0049] This possible implementation can be applied to the release and reconstruction of transport layer connections or application layer connections.

[0050] A third aspect of this application provides a communication method, which is executed by a second network device, or by a component (e.g., a processor, chip, or chip system) of the second network device, or by a logic module or software capable of implementing all or part of the functions of the second network device. In this third aspect and its possible implementations, the method is described as being executed by a second network device. The second network device receives a third request message sent by a first network device, the third request message requesting the second network device to provide access service for a first computing service of a terminal device. The second network device sends a response message to the third request message to the first network device, the response message indicating acceptance of the request to switch to the first computing service.

[0051] Based on the above scheme, the second network device can indicate to the first network device through response information that it accepts the request to provide access services for the first computing service, thereby improving the first network device's understanding of the relevant capabilities of the second network device and facilitating the subsequent connection of the terminal device to new computing nodes.

[0052] Optionally, in one possible implementation of the third aspect, if a service instance of the first computing service exists, the second network device sends a response message to the first network device.

[0053] In this possible implementation, if the second network device has a corresponding instance, it can inform the first network device through response information so that a suitable computing node can be found for the terminal device in the future.

[0054] Alternatively, in one possible implementation of the third aspect, the aforementioned response information is also used to indicate whether the second network device supports a service instance of the first computing service.

[0055] In this possible implementation, the first network device can quickly understand the second network device's support for the first computing service based on the response information.

[0056] Alternatively, in one possible implementation of the third aspect, the aforementioned response information is also used to indicate the service instance identifier that the second network device is connecting to.

[0057] In this possible implementation, the first network device can first learn about the instance connected by the second network device through the response information, which makes it easier to find a suitable instance for the first computing service in the future.

[0058] Optionally, in one possible implementation of the third aspect, the second network device may further receive a fourth message sent by the terminal device, the fourth message being used to request the first computing service or transmit user plane data of the first computing service; the second network device then sends a fifth message to the second computing node, the fifth message being used to instruct the second computing node to perform the first computing service.

[0059] In this possible implementation, the second network device can establish a corresponding connection request for the terminal device so that the second computing node can serve the terminal device.

[0060] Optionally, in one possible implementation of the third aspect, the aforementioned response information is further used to indicate at least one of the following: a second computing service in the first computing service supported by the second network device, and a third computing service in the first computing service not supported by the second network device.

[0061] In this possible implementation, the second network device can inform the first network device of the instances it supports or the computing services / instances it does not support, thereby improving the accuracy of the first network device in judging the corresponding instances.

[0062] Optionally, in one possible implementation of the third aspect, the second network device is further configured to receive a third instruction information sent by the first network device, the third instruction information being configured to instruct the first computing node to send second information, the second information being configured to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device; after receiving the third instruction information, the second network device sends the second information to the first computing node.

[0063] In this possible implementation, the second network device can use a third instruction to enable the first network device to provide a subscription notification from the terminal device.

[0064] Optionally, in one possible implementation of the third aspect, the aforementioned third request information includes at least one of the following: the identifier of the first computing service, the transmission requirements of the first computing service, and notification acceptance address information.

[0065] In this possible implementation, by indicating the receiving address information, the second network device can clearly identify which computing node to establish a connection with.

[0066] The fourth aspect of this application provides a communication method, which is executed by a gateway, or by a component of the gateway (e.g., a processor, chip, or chip system), or may be implemented by a logic module or software capable of implementing all or part of the gateway's functions. In this fourth aspect and its possible implementations, the method being executed by a gateway is described as an example.

[0067] The gateway receives multiple first request messages from multiple computing nodes, aggregates these messages to obtain first information, and sends the first information to the first network device. Then, it sends second information to the multiple computing nodes.

[0068] Among them, multiple first request messages are used to subscribe to the mobility events of the terminal device; the first information is used to subscribe to the mobility events of the terminal device, the first computing node has connected to the service instance of the first computing service, and the second information is used to instruct the terminal device to switch from the first network device to the second network device.

[0069] Based on the above scheme, by aggregating the distribution of multiple first request messages and second messages through the gateway, not only can the complexity of network devices maintaining multiple subscriptions be reduced, but the second message can also indicate the switching of network devices, so that the subsequent second network device can select a new computing node for the terminal device.

[0070] Optionally, in one possible implementation of the fourth aspect, the gateway sends a second request message to a first computing node among a plurality of computing nodes. The second request message is used to request the release of the first connection between the terminal device and the first computing node. The gateway sends a third message to the terminal device. The third message is used to instruct the release of the first connection between the terminal device and the first computing node.

[0071] In this possible implementation, the gateway can release the connection between the terminal device and the first computing node through the second request information and the third information, thereby not affecting the establishment of the connection between the terminal device and the new computing node and improving the user experience.

[0072] Alternatively, in one possible implementation of the fourth aspect, the aforementioned second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0073] In this possible implementation, by indicating the instance that meets the requirements through the second information, the second network element can find an instance that is compatible with the first computing node, thereby improving the user experience.

[0074] Optionally, in one possible implementation of the fourth aspect, the first information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, an identifier of the first computing service, and a transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0075] In this possible implementation, the first information of the mobility event of the subscribing terminal device can also include indicators, transmission requirements, etc. This makes it easier for the first network device to determine whether the second network device is compatible with the relevant requirements, reducing service quality degradation caused by handover.

[0076] Optionally, in one possible implementation of the fourth aspect, the second information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, and an identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0077] This application provides a communication method, which is executed by a terminal device, or by a component (e.g., a processor, chip, or chip system) within the terminal device, or by a logic module or software capable of implementing all or part of the terminal device's functions. In this fifth aspect and its possible implementations, the method is described as being executed by a terminal device. The terminal device receives third information sent by a second network element, the third information being used to release a first connection between the terminal device and a first computing node; the terminal device sends fourth information to a second network device, the fourth information being used to identify the computing node associated with the terminal device.

[0078] Based on the above scheme, the terminal device can determine the connection release request of the second network element through the third information, and enable the second network device to select a suitable computing node for the terminal device through the fourth information. This reduces the risk of the terminal device attempting to connect to the original computing node after switching from the first network device to the second network device, thus minimizing path errors or unreachability, and also facilitates subsequent connections to suitable computing nodes.

[0079] Alternatively, in one possible implementation of the fifth aspect, the aforementioned terminal device may also release the first connection and / or re-initiate a connection request to the first computing service.

[0080] In this possible implementation, after receiving the third information, the terminal device can release the first connection with the first computing node and / or re-initiate a connection request with the new computing node. This reduces the path inefficiency or unreachability caused by the terminal device still trying to connect to the original computing node after switching from the first network device to the second network device, and also facilitates the terminal device's subsequent connection to the adapted computing node.

[0081] Alternatively, in one possible implementation of the fifth aspect, the aforementioned terminal device may also clean up the Domain Name System (DNS) records of the terminal device.

[0082] In this possible implementation, by clearing DNS records, the terminal device can reduce the probability that it will still try to connect to the original computing node, and it also makes it easier for the network device to reselect a suitable computing node for the terminal device, thereby improving the user experience.

[0083] Optionally, in one possible implementation of the fifth aspect, the second network element mentioned above is a first computing node or a gateway, and the gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0084] This possible implementation can be applied to various transmission scenarios, such as a transmission scenario where the terminal device and the network device are directly connected, or a transmission scenario where the terminal device and the network device are indirectly connected through a gateway.

[0085] A sixth aspect of this application provides a communication device that is a first computing node, or a component of the first computing node (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first computing node. Taking the communication device as an example of a first computing node, the first computing node includes a transceiver unit.

[0086] The transceiver unit is used to send first information to the first network element, and the first information is used to subscribe to the mobility events of the terminal device;

[0087] The transceiver unit is also used to receive second information, which is used to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device;

[0088] The transceiver unit is also used to send third information, which is used to indicate the release of the first connection between the terminal device and the first computing node.

[0089] Alternatively, in one possible implementation of the sixth aspect, the aforementioned third information is also used to instruct that a new connection request to the first computing service be initiated after the first connection is released.

[0090] Alternatively, in one possible implementation of the sixth aspect, the aforementioned third information is also used to instruct the cleanup of DNS records on the terminal device.

[0091] Optionally, in one possible implementation of the sixth aspect, the aforementioned transceiver unit is specifically used to send third information if the first computing service has finished executing.

[0092] Optionally, in one possible implementation of the sixth aspect, the aforementioned transceiver unit is specifically used to receive second information sent by the first network device or the second network device.

[0093] Optionally, in one possible implementation of the sixth aspect, the first network element mentioned above is a first network device, a terminal device, or a gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0094] Optionally, in one possible implementation of the sixth aspect, the aforementioned first information is further used by the first network element to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are respectively used to subscribe to the mobility events of the terminal device.

[0095] Optionally, in one possible implementation of the sixth aspect, the aforementioned transceiver unit is specifically used to receive the second information sent by the first network element; the transceiver unit is specifically used to send the third information to the first network element.

[0096] Alternatively, in one possible implementation of the sixth aspect, the aforementioned second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0097] Optionally, in one possible implementation of the sixth aspect, the first information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, an identifier of the first computing service, and a transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0098] Optionally, in one possible implementation of the sixth aspect, the second information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, and an identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0099] Optionally, in one possible implementation of the sixth aspect, the first connection described above includes at least one of the following: a transport layer connection and an application layer connection.

[0100] A seventh aspect of this application provides a communication device, which is a first network device, or a component of the first network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first network device. Taking the first network device as an example, the first network device includes a transceiver unit, or the first network device includes a transceiver unit and a processing unit.

[0101] The transceiver unit is used to receive first information sent by the second network element. The first information is used for the first computing node to subscribe to the mobility events of the terminal device and for the first computing node to connect to the service instance of the first computing service.

[0102] The transceiver unit is also used to send second information to the second network element, the second information being used to instruct the terminal device to switch from the first network device to the second network device.

[0103] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is specifically used to send second information to the second network element when the second network device supports a service instance of the first computing service.

[0104] Optionally, in one possible implementation of the seventh aspect, the transceiver unit described above is further configured to receive second indication information sent by the second network device, the second indication information being used to indicate that the second network device supports a service instance of the first computing service.

[0105] Optionally, in one possible implementation of the seventh aspect, the aforementioned processing unit is configured to determine at least one service instance supported by the second network device; the processing unit is further configured to determine that the at least one service instance includes a service instance of the first computing service.

[0106] Optionally, in one possible implementation of the seventh aspect, the transceiver unit is further configured to send a third request message to the second network device, the third request message being used to request the second network device to provide access service for the first computing service; the transceiver unit is further configured to receive a response message to the third request message sent by the second network device, the response message being used to indicate acceptance of the request to switch the first computing service.

[0107] Alternatively, in one possible implementation of the seventh aspect, the aforementioned response information is also used to indicate whether the second network device supports a service instance of the first computing service.

[0108] Alternatively, in one possible implementation of the seventh aspect, the aforementioned response information is also used to indicate the service instance identifier that the second network device is connecting to.

[0109] Optionally, in one possible implementation of the seventh aspect, the aforementioned processing unit is further configured to determine, based on the service requirements of the first computing service, whether the second network device has a service instance that satisfies the service requirements of the first computing service.

[0110] Optionally, in one possible implementation of the seventh aspect, the aforementioned second network element is a first computing node or a gateway, the gateway being used to aggregate multiple first request information from multiple computing nodes, the multiple first request information being used to subscribe to mobility events of terminal devices.

[0111] Alternatively, in one possible implementation of the seventh aspect, the aforementioned second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0112] Optionally, in one possible implementation of the seventh aspect, the first information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, an identifier of the first computing service, and a transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0113] Optionally, in one possible implementation of the seventh aspect, the second information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, and an identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0114] Optionally, in one possible implementation of the seventh aspect, the first connection described above includes at least one of the following: a transport layer connection and an application layer connection.

[0115] An eighth aspect of this application provides a communication device, which is a second network device, or a component of a second network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the second network device. Taking the communication device as a second network device as an example, the second network device includes a transceiver unit.

[0116] The transceiver unit is used to receive a third request message sent by the first network device. The third request message is used to request the second network device to provide access service for the first computing service of the terminal device.

[0117] The transceiver unit is also used to send a response to the third request to the first network device, the response being used to indicate acceptance of the request to switch the first computing service.

[0118] Optionally, in one possible implementation of the eighth aspect, the aforementioned transceiver unit is specifically used to send response information to the first network device if a service instance of the first computing service exists.

[0119] Alternatively, in one possible implementation of the eighth aspect, the aforementioned response information is also used to indicate whether the second network device supports a service instance of the first computing service.

[0120] Alternatively, in one possible implementation of the eighth aspect, the aforementioned response information is also used to indicate the service instance identifier that the second network device is connecting to.

[0121] Optionally, in one possible implementation of the eighth aspect, the transceiver unit described above is further configured to receive fourth information sent by the terminal device, the fourth information being used to request the first computing service or transmit user plane data of the first computing service; the transceiver unit is further configured to send fifth information to the second computing node, the fifth information being used to instruct the second computing node to perform the first computing service.

[0122] Optionally, in one possible implementation of the eighth aspect, the aforementioned response information is further used to indicate at least one of the following: a second computing service in the first computing service supported by the second network device, and a third computing service in the first computing service not supported by the second network device.

[0123] Optionally, in one possible implementation of the eighth aspect, the transceiver unit is further configured to receive third indication information sent by the first network device, the third indication information being used to instruct the transmission of second information to the first computing node, the second information being used to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device; the transceiver unit is further configured to transmit the second information to the first computing node.

[0124] Optionally, in one possible implementation of the eighth aspect, the aforementioned third request information includes at least one of the following: the identifier of the first computing service, the transmission requirements of the first computing service, and notification acceptance address information.

[0125] The ninth aspect of this application provides a communication device, which is a gateway, or a component of a gateway (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the gateway's functions. Taking the communication device as a gateway as an example, the gateway includes a transceiver unit and a processing unit.

[0126] The transceiver unit is used to receive multiple first request messages sent by multiple computing nodes, and the multiple first request messages are used to subscribe to the mobility events of the terminal device.

[0127] The processing unit is used to aggregate multiple first request messages and send first information to the first network device. The first information is used to subscribe to the mobility events of the terminal device and the first computing node has been connected to the service instance of the first computing service.

[0128] The transceiver unit is also used to send second information to multiple computing nodes, the second information being used to instruct the terminal device to switch from the first network device to the second network device.

[0129] Optionally, in one possible implementation of the ninth aspect, the transceiver unit described above is further configured to send a second request message to a first computing node among a plurality of computing nodes, the second request message being used to request the release of the first connection between the terminal device and the first computing node; the transceiver unit is further configured to send a third message to the terminal device, the third message being used to instruct the release of the first connection between the terminal device and the first computing node.

[0130] Alternatively, in one possible implementation of the ninth aspect, the aforementioned second information is further used to instruct the second network device to support a service instance of the first computing service.

[0131] Optionally, in one possible implementation of the ninth aspect, the first information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, an identifier of the first computing service, and a transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0132] Optionally, in one possible implementation of the ninth aspect, the second information mentioned above includes at least one of the following: first indication information, an identifier of the terminal device, and an identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0133] The tenth aspect of this application provides a communication device, which is a terminal device, or a component of a terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of a terminal device. Taking the communication device as a terminal device as an example, the terminal device includes a transceiver unit, or the terminal device includes a transceiver unit and a processing unit.

[0134] The transceiver unit is used to receive third information sent by the second network element. The third information is used to release the first connection between the terminal device and the first computing node.

[0135] The transceiver unit is also used to send fourth information to the second network device, which is used to identify the computing node associated with the terminal device.

[0136] Optionally, in one possible implementation of the tenth aspect, the aforementioned processing unit is used to release the first connection and / or re-initiate a connection request to the first computing service.

[0137] Alternatively, in one possible implementation of the tenth aspect, the aforementioned processing unit is used to clean up the Domain Name System (DNS) records of the terminal device.

[0138] Optionally, in one possible implementation of the tenth aspect, the aforementioned second network element is a first computing node or a gateway, the gateway being used to aggregate multiple first request information from multiple computing nodes, the multiple first request information being used to subscribe to mobility events of terminal devices.

[0139] The eleventh aspect of this application provides a communication device, including at least one processor coupled to at least one memory; the at least one memory is used to store a program or instructions; the at least one processor is used to execute the program or instructions to enable the device to implement any possible implementation of any of the first to fifth aspects.

[0140] The twelfth aspect of this application provides a communication device including at least one logic circuit and at least one input / output interface; the logic circuit is used to perform the method as described in any possible implementation of any of the first to fifth aspects described above.

[0141] The thirteenth aspect of this application provides a communication system, which includes a communication device according to any possible implementation of the sixth aspect, the seventh aspect, the eighth aspect, and the tenth aspect.

[0142] Alternatively, it may include a communication device that implements any of the possible implementations of the sixth aspect, the seventh aspect, the eighth aspect, the ninth aspect, and the tenth aspect.

[0143] The fourteenth aspect of this application provides a computer-readable storage medium for storing one or more computer-executable instructions, which, when executed by a processor, perform the method as described in any possible implementation of any of the first to fifth aspects above.

[0144] The fifteenth aspect of this application provides a computer program product (or computer program) that, when executed by a processor, performs the method described in any possible implementation of any of the first to fifth aspects described above.

[0145] The sixteenth aspect of this application provides a chip or chip system including at least one processor for supporting a communication device in implementing the method described in any possible implementation of any of the first to fifth aspects.

[0146] In one possible design, the chip system may further include at least one memory for storing program instructions and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete components. Optionally, the chip system may also include interface circuitry that provides program instructions and / or data to at least one processor.

[0147] The technical effects of any of the design methods in aspects six through sixteen can be found in the technical effects of the different design methods in aspects one through five above, and will not be repeated here. Attached Figure Description

[0148] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0149] Figure 1A This is a schematic diagram of the communication system involved in this application;

[0150] Figure 1B This is another schematic diagram of the communication system involved in this application;

[0151] Figure 1C This is another schematic diagram of the communication system involved in this application;

[0152] Figure 2A This is a schematic diagram of the system architecture involved in this application;

[0153] Figure 2B This is another schematic diagram of the system architecture involved in this application;

[0154] Figure 3A This is a schematic diagram illustrating the deployment method involved in this application;

[0155] Figure 3B This is another schematic diagram illustrating the deployment method involved in this application;

[0156] Figure 4 This is a flowchart illustrating the communication method involved in this application;

[0157] Figure 5 This is another flowchart illustrating the communication method involved in this application;

[0158] Figure 6 This is another flowchart illustrating the communication method involved in this application;

[0159] Figure 7 This is another flowchart illustrating the communication method involved in this application;

[0160] Figures 8 to 11 Several schematic diagrams of the communication device provided in this application. Detailed Implementation

[0161] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0162] First, some terms used in the embodiments of this application will be explained to facilitate understanding by those skilled in the art.

[0163] 1. Communication computing node (or simply communication node)

[0164] A communication node is a network device with both computing and communication capabilities. The communication capability refers to the ability to provide access services to terminal devices and / or to communicate with other network devices.

[0165] 2. Computational Unit (or Computational Node)

[0166] A computing unit is a device with computing capabilities. In some implementations, a computing unit can also be a general computing node.

[0167] 3. Computing service

[0168] Computing services, also known as computing power services, can be understood as a set of independent application processes or a specific computing function that can solve specific problems.

[0169] Alternatively, the computing service can use a lightweight application programming interface (API) and communicate with other devices / instances / units through a well-defined interface.

[0170] Generally, a computing service can correspond to one or more computing functions (or computing power functions) that provide the same functionality. That is, multiple different computing functions implement the same function and can provide the same computing service. Typically, the functionality implemented by a computing function can be encapsulated as a service and provided to external entities for invocation via an API. A computing power function can also be called a computation function, and it can be understood as a serverless computing model, usually consisting of a series of configurations and a series of executable code / software packages. Business logic code is the software program code written to support the computational processing of input data or events according to a specified algorithm. For example, the aforementioned computational processing may include: video stream transcoding, image rendering, image detection, artificial intelligence (AI) computation, etc.

[0171] Correspondingly, the computing power (or computing function) of a computing node or computing unit can be understood as: the ability to provide computing resources for computing services.

[0172] 4. Service Instances of Computing Services

[0173] A service instance of a computing service can also be called a function instance of a computing service, a computing service instance, a computing function instance, a computing power service instance, or a computing power function instance. A service instance of a computing service can be understood as an application program obtained by installing computing power function code onto a computing node or computing unit.

[0174] A service instance or function instance can be understood as an entity that can provide computing power functions to run. For example, it can be carried by a container that has the runtime environment for computing power functions, can process the function's input, execute code logic, and give output results.

[0175] 5. Calculation task

[0176] A computational task, also known as a computing power task, represents the execution of a computing power function call (invoke) or the acquisition of a computing power service result in order to complete a business logic transaction. For example, performing video transcoding on specified data: for a video segment or video chip, a computing power function call / service can be executed once, using the video segment or video chip as input, until the computing power function / service obtains the complete transcoded segment or chip; this is called a computational task. Processing the next different video segment or video chip requires executing a new computational task, i.e., calling or executing the computing power function / service again. In other words, different calls / executions of computing power functions / services are called different computational tasks. The same computing power function, or computing power logic / transaction, can be executed multiple times; the inputs may be the same or different, and the outputs may also be the same or different.

[0177] 6. Computing Service Identifier

[0178] A computing service identifier, also known as a computing power service identifier, is used to uniquely identify a computing service or computing power service. Alternatively, it can be understood as a globally unique identifier for a computing service or computing power service.

[0179] Optionally, the computing power service identifier can be an identifier in any of the following formats: (1) a globally unique identifier, for example, composed of one or more combinations of letters, numbers, and special characters; (2) an identifier in the format of a uniform resource locator (URL); (3) a fully qualified domain name (FQDN); (4) an IP address, for example, an IP anycast address or an IP unicast address; (5) an IP address + port number; (6) an identifier in the format of a uniform resource identifier (URI). In this application, unless explicitly stated otherwise, computing power service and computing power function can be used interchangeably, and computing power function identifier and computing power service identifier can be used interchangeably.

[0180] 7. Quality of Service (QoS)

[0181] Computing QoS, also known as network QoS, mainly includes transmission QoS and computation QoS. Transmission QoS is a parameter used to guarantee communication (or information transmission). Computation QoS is a parameter used to guarantee computational performance.

[0182] Optionally, the computing power QoS may include at least one of the following: transmission resource type, priority, packet delay budget, packet error rate, packet loss rate, default maximum data burst size, default average window, etc. It may also include computing resource types, such as central processing unit (CPU) resources, graphics processing unit (GPU) resources, neural network processing unit (NPU) resources, tensor processing unit (TPU) resources, deep learning processing unit (DPU) resources, field programmable gate array (FPGA) resources, memory resources, storage resources, etc. It may also include resource consumption granularity and computing power requirements, such as at least one of floating point operations per second (FLOPS) and operations per second (OPS).

[0183] 8. Service Level Agreement (SLA) Requirements for Computing Services

[0184] SLA requirements for a computing service can indicate the computing performance that the service needs to provide. For example, SLA requirements can indicate the latency required for a function instance to execute a computing task. If the computing task is an image rendering task, the latency required to execute the computing task can be the time required to render one frame. Alternatively, SLA requirements can also indicate the computing and communication performance that the service needs to provide. For example, SLA requirements can indicate the total latency from when the terminal device sends a computing task request to when the terminal device receives the computing task execution result. If the computing task is an image rendering task, the total latency can be the total time from when the terminal device sends an image rendering request to when the terminal device receives the image rendering result.

[0185] 9. Configuration and Pre-configuration

[0186] This application uses both configuration and pre-configuration. Configuration refers to the network device / server sending configuration information or parameter values ​​to the terminal via messages or signaling, so that the terminal can determine communication parameters or resources for transmission based on these values ​​or information. Pre-configuration is similar to configuration; it can be parameter information or values ​​pre-negotiated between the network device / server and the terminal device, parameter information or values ​​specified by standard protocols for use by the base station / network device or terminal device, or parameter information or values ​​pre-stored in the base station / server or terminal device. This application does not limit this.

[0187] Furthermore, these values ​​and parameters can be changed or updated.

[0188] 10. In this application, "for indicating" can include both direct and indirect indication. When describing an indication information as indicating A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0189] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementation, there are many ways to instruct the information to be instructed. For example, it can be implemented through direct instruction, such as through the information to be instructed itself or its index. It can also be implemented indirectly by instructing other information, where there is a relationship between the other information and the information to be instructed. Alternatively, only a part of the information to be instructed can be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

[0190] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, MAC layer control elements (CE); physical layer signaling includes, for example, downlink control information (DCI).

[0191] 11. In the embodiments of this application, "sending" and "receiving" indicate the direction of signal transmission. In this application, entity A sends information to entity B, either directly to B or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be radio access network (RAN) nodes or terminals, or modules within RAN nodes or terminals. Information sending and receiving can be information interaction between RAN nodes and terminals, such as information interaction between a base station and a terminal; information sending and receiving can also be information interaction between two RAN nodes, such as information interaction between a CU and a DU; information sending and receiving can also be information interaction between different modules within a device, such as information interaction between a terminal chip and other modules of the terminal, or information interaction between a base station chip and other modules in the base station. "Sending" can also be understood as the "output" of the chip interface, such as the baseband chip outputting information to the radio frequency chip, and "receiving" can also be understood as the "input" of the chip interface; for example, "sending" can also be understood as the baseband part inside the device outputting information to the radio frequency part, and "receiving" can also be understood as the radio frequency part inside the device receiving the information output by the baseband part.

[0192] 12. The terms "system" and "network" in the embodiments of this application can be used interchangeably. "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority or importance of multiple objects.

[0193] Please see Figure 1A This is a schematic diagram of the architecture of the communication system 1000 used in an embodiment of this application. Figure 1A As shown, the communication system includes a radio access network (RAN) 100 and a core network 200. Optionally, the communication system 1000 may also include an Internet 300. The RAN 100 includes at least one RAN node (e.g., ...). Figure 1A 110a and 110b, collectively referred to as 110, may also include at least one terminal device (such as...). Figure 1A RAN100, denoted as RAN100, comprises RAN nodes 120a-120j, collectively referred to as RAN120. RAN100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1A (Not shown in the image). Terminal device 120 is wirelessly connected to RAN node 110, and RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be independent physical devices, or they can be the same physical device integrating the logical functions of core network equipment and RAN nodes. Terminal devices and RAN nodes can be interconnected via wired or wireless means.

[0194] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, an NR system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0195] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminal devices access communication systems wirelessly. Furthermore, RAN nodes can also be called network devices, which are apparatuses deployed in a radio access network to provide wireless communication functions for terminal devices. Network devices can include various forms of macro base stations, micro base stations (also known as small cells), relay stations, access points, etc. The names of network devices may differ in systems employing different radio access technologies. It is understood that all or part of the functions of the access network devices in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The embodiments of this application do not limit the specific technologies or specific device forms used in the radio access network devices.

[0196] In one application scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, or a base station in a future mobile communication system. A RAN node can also be a macro base station (such as...). Figure 1A 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1A The RAN node (110b) can also be a relay node or donor node, or a wireless controller in a Cloud Radio Access Network (CRAN) scenario. Of course, in future communication systems, RAN nodes may also be wearable devices or vehicle-mounted devices, etc.

[0197] In another application scenario, multiple RAN nodes can collaborate to help terminal devices achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). RUs can be included in radio frequency equipment, such as remote radio units (RRUs) or active antenna units (AAUs). CUs can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0198] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes.

[0199] A terminal device is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminal devices can also be referred to as user equipment (UE), mobile stations, mobile terminal devices, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0200] For ease of description, Figure 1A The illustrated communication system is described using a base station as an example of an access network device. It is understood that when the communication system includes an integrated access and backhaul (IAB) network, the base station can be an IAB node. It should be noted that in the embodiments of this application, the base station and the access network device can be interchanged.

[0201] Base stations and terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminal equipment.

[0202] The roles of base stations and terminal devices can be relative, for example, Figure 1A The helicopter or drone 120i can be configured as a mobile base station. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a base station; however, for base station 110a, 120i is a terminal device, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminal devices can be collectively referred to as communication equipment. Figure 1A The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1AThe 120a-120j in the text can be referred to as communication equipment with terminal device functions.

[0203] Communication between base stations and terminal devices, between base stations, and between terminal devices can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0204] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can be executed by modules (such as chips or modems) within the terminal device, or by a device that includes terminal device functions.

[0205] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. In order to communicate with the base station, the terminal needs to establish a radio connection on a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell.

[0206] As can be understood, RAN100, as previously described, includes at least one RAN node (e.g., Figure 1A 110a and 110b, collectively referred to as 110, may also include at least one terminal device (such as...). Figure 1A 120a-120j in the series are collectively referred to as 120).

[0207] In one possible implementation method Figure 1A The communication system shown can also be as follows Figure 1B As shown, it includes one RAN node 110 and multiple terminal devices (such as...). Figure 1B (Referring to 120A and 120B in the original text). In this case, a single RAN node can transmit data or control signaling to one or more terminal devices.

[0208] In another possible way of implementation Figure 1A The communication system shown can also be as follows Figure 1C As shown, this includes multiple RAN nodes (such as...) Figure 1C110 (110A, 110B, and 110C) 110 and a terminal device 120. In this case, multiple RAN nodes can also transmit data or control signaling to a single terminal device simultaneously.

[0209] The technical solution of this application can be applied to 3GPP-related cellular communication systems. For example, fourth-generation (4G) communication systems, 5G communication systems, and communication systems beyond fifth-generation (5G) systems. For example, future communication systems. For example, fourth-generation communication systems may include long-term evolution (LTE) communication systems. Fifth-generation communication systems may include new radio (NR) communication systems. The technical solution of this application can also be applied to wireless fidelity (WiFi) systems, communication systems supporting the integration of multiple wireless technologies, device-to-device (D2D) systems, or vehicle-to-everything (V2X) communication systems, etc., and is not specifically limited here.

[0210] Furthermore, the access network can also undertake some computing functions from cloud edge nodes. These computing functions may be internal to the base station or an external, independent function separate from the base station's logical functions. The introduction of this computing function enhances upon the aforementioned… Figure 1A The architecture has been updated. The following description uses the example of a computing function that is an external, independent function separate from the base station logic function to illustrate the updated communication system.

[0211] Figure 2A and Figure 2B A schematic diagram of the system architecture provided in an embodiment of this application is shown. See also Figure 2A and Figure 2B The system includes RAN nodes, compute nodes, and a core network. Optionally, the system also includes terminals. Figure 2A and Figure 2B The difference is that, Figure 2A The system shown does not include an application programming interface (API) gateway or proxy. Figure 2B The system shown includes an API gateway or proxy. The following is about... Figure 2A and Figure 2B The system architecture shown is briefly explained.

[0212] exist Figure 2A and Figure 2BIn the system architecture shown, the RAN node is used to provide access services for terminals (e.g., UEs), and the RAN node has the ability to provide and / or allocate computing resources for computing services requested by the terminal. The RAN node can be a general computing node. Figure 2A and Figure 2B The RAN nodes include CU, DU, and RU.

[0213] AI applications can be understood as applications deployed on the cloud or edge. Data interaction between AI applications and terminals can be carried out in various ways. For example, RAN node <-> compute node <-> AI application. Another example is RAN node <-> API gateway <-> compute node <-> AI application. Yet another example is RAN node <-> UPF <-> general-purpose computing server <-> AI application. Here, the general-purpose computing server can also be considered a type of compute node, providing computing services. In this embodiment, <-> indicates a bidirectional data interaction path. For example, RAN node <-> compute node <-> AI application can refer to the data interaction path between the RAN node and the AI ​​application. This could mean the RAN node transmits data to the AI ​​application through the compute node, or the AI ​​application transmits data to the RAN node through the compute node.

[0214] A computing node can also be called a computing unit, intelligent node, intelligent unit, computing power unit, computing power node, etc. Computing nodes can be used to provide computing services, offering users one or more of the following functions: connectivity, computation, or data storage. More specifically, one or more service instances can be loaded on a computing node, each of which can be used to provide computing services.

[0215] The compute node and the computing service on the terminal have a protocol reference point, which supports the computing service module on the terminal to call computing services. The compute node can also have a protocol reference point with the RAN node, which includes control plane signaling and user plane data. This protocol reference point can use the IP protocol or a tunneling transport protocol such as GTP. The network connection between the RAN node and the compute node can be based on Layer 2 (L2) switch forwarding or Layer 3 (L3) IP routing forwarding. The RAN node and the compute node can be directly connected at L2 or L3, meaning there are no other intermediate nodes in the transmission path between the two nodes. One or more RAN nodes can connect to the same compute node.

[0216] Optionally, the computing node may only possess computing capabilities and the ability to send and receive computing service-related information and data with the RAN node, without the ability to provide access services to terminals; that is, the computing node only provides function instances. In other words, the computing node and the RAN node can be two independent physical devices.

[0217] Optionally, the computing node can also possess both computing and communication capabilities, meaning it is a multi-functional computing node. In other words, the computing node and the RAN node are co-located and integrated within the same physical device. In this case, the interaction between the computing node and the RAN node is an internal device interaction.

[0218] Optionally, the compute nodes also have load balancing (LB) functionality. The LB function can select a suitable compute instance for a compute task based on the load of each compute instance on the compute node.

[0219] The load balancer (LB) function can be understood as a module that can be integrated within a compute node or exist independently of it. The LB function can manage one compute node or multiple compute nodes. This application does not impose any limitations on this.

[0220] The core network can communicate with at least one RAN node. Each RAN node can communicate with at least one compute node. The core network includes a compute node control entity. This entity is used to manage the compute nodes. The compute node control entity can be a single logical functional entity, deployed independently or alongside other functional modules, or it can consist of multiple entities distributed across different geographical locations. This application does not limit its scope. Corresponding to the name of the compute node, the compute node control entity can also be called a compute unit control entity, intelligent node control entity, intelligent unit control entity, or alternatively, a compute node control function network element, compute unit control function network element, intelligent node control function network element, intelligent unit control function network element, or simply compute node control function, compute unit control function, intelligent node control function, intelligent unit control function, etc.

[0221] For example, a compute node control entity may have the following functions:

[0222] 1. Service Registry Function: Also known as the Computing Unit Repository Function, Service Repository Function, etc., it is responsible for managing computing nodes, including receiving computing node registrations and address allocations. This function can be co-located with NRF. Computing node registration includes: computing nodes can register their configuration information (profile) with the Computing Node Control Entity, and / or, computing nodes can register the configuration information of the computing power services on their nodes with the Computing Node Control Entity.

[0223] 2. Configuration function for compute nodes or compute services: Configure information about compute nodes and compute services to RAN nodes. This function can be co-located with AMF.

[0224] 3. Functions related to business requirements: Decomposition of business requirements, generation of QoS parameters, and interaction with the policy control function (PCF) to obtain QoS information. This part of the functionality can be shared with the session management function (SMF) or PCF.

[0225] Operations administration and maintenance (OAM) comprises the RAN management platform and the compute node management platform. The RAN management platform is connected to the RAN nodes, for example, to the compute units (CUs) within the RAN nodes, and is used to manage the RAN. The compute node management platform is connected to the compute nodes and is used to manage the compute nodes. For example, the compute node management platform can control the creation, updating, or deletion of compute instances on the compute nodes.

[0226] In addition, the core network may include access and mobility management function (AMF), SMF and PCF network exposure function (NEF) elements, and service modules can access the internal data of the core network through NEF.

[0227] For example, the terminal device may include Figure 1A Any one of the terminal devices 120a-120j shown. If the terminal devices include Figure 1A If any one of the terminal devices 120a, 120b, 120c, and 120i shown is present, then the RAN node may include... Figure 1A RAN node 110a in the RAN node, the computing node may include Figure 1A RAN node 110b in the middle; or, if the terminal device includes Figure 1A If any one of the terminal devices 120f, 120g, and 120h is shown, then the RAN node may include Figure 1A RAN node 110b in the RAN node, the compute node may include Figure 1A RAN node 110a in the core network. The core network can communicate with each network element through the control plane, which may include one or more control plane functional entities in the core network 200.

[0228] and Figure 2A different, Figure 2BThis also includes API gateways or proxies. API gateways or proxies can provide proxy functionality for signaling and data exchange between RAN nodes and compute nodes (including service instances deployed on them), or between terminals and compute nodes (including service instances deployed on them). The proxy can be a transparent proxy or a reverse proxy. API gateways or proxies can also provide load balancing functionality, selecting compute nodes and / or service instances to serve the terminals.

[0229] In addition, API gateways or proxies can also provide layer 4 (L4) and layer 7 (L7) proxy functionality. L4 proxy includes proxy functionality for layers such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Quick UDP Internet Connection (QUIC). L7 proxy includes application layer proxy functionality, such as proxy functionality for the Hypertext Transfer Protocol (HTTP) layer.

[0230] In addition, there are multiple deployment methods (or topology relationships) between the aforementioned RAN nodes, compute nodes, and service instances, which are described below:

[0231] Figure 3A and Figure 3B A schematic diagram illustrating the deployment method provided in an embodiment of this application is shown. See also... Figure 3A and Figure 3B The deployment involves RAN nodes, compute nodes, and service instances (referred to as instances). Figure 3A and Figure 3B The difference is that, Figure 3A Different RAN nodes cannot connect to the same compute node. Figure 3B Different RAN nodes can be connected to the same compute node.

[0232] Optionally, an API gateway (not shown in the figure) may also be included between the RAN node and multiple compute nodes. The API gateways used by different RAN nodes can be the same or different, which is not limited here.

[0233] The relationship between a RAN node and a connected compute node can be described as follows: RAN node has deployed compute nodes, RAN node has carried compute nodes, RAN node has connected compute nodes, RAN node supports compute nodes, RAN node has activated compute nodes, RAN node and compute nodes are reachable, RAN node provides compute services through compute nodes, etc.

[0234] Correspondingly, the relationship between a compute node and the instances on the compute node can be described as follows: compute node has deployed instances, compute node has hosted instances, compute node has connected instances, compute node supports instances, compute node is activated, and compute node provides computing services through instances.

[0235] For ease of description, the following will be Figure 3A The deployment method shown is called deployment 1. Figure 3B The deployment method shown is called deployment 2.

[0236] like Figure 3A As shown, deployment 1 involves RAN node 1, RAN node 2, compute node 1, compute node 2, and compute node 3.

[0237] For example, RAN node 1 is connected to compute node 1, and RAN node 2 is connected to compute node 2 and compute node 3. Compute node 1 has instances 1 and 2 deployed, compute node 2 has instances 3 and 4 deployed, and compute node 3 has instances 5 and 6 deployed.

[0238] like Figure 3B As shown, deployment 1 involves RAN node 1, RAN node 2, compute node 1, compute node 2, compute node 3, and compute node 4.

[0239] For example, RAN node 1 is connected to compute node 1 and compute node 2, and RAN node 2 is connected to compute node 2, compute node 3, and compute node 4. Compute node 1 has instances a and b deployed, compute node 2 has instances c and d deployed, compute node 3 has instances e and f deployed, and compute node 4 has no instances deployed.

[0240] Among these, any one of instances 1 to 6, or instances a to f, can provide computing services. Thus, the computing node provides the corresponding service to the terminal devices connected to the RAN node through the appropriate instance. For example, Figure 3A Computing node 1 in the RAN can provide services corresponding to instance 1 to terminal devices connected to RAN node 1 through instance 1.

[0241] It is understandable that instances deployed on the same compute node can correspond to the same or different compute services, and instances deployed on different compute nodes can be the same or different, and the compute services corresponding to different instances can be the same or different. For example, instance 1 and instance 4 can be the same instance or different instances. As another example, instance 1 and instance 2 both correspond to compute service 1.

[0242] For example, with Figure 3A Taking deployment 1 as an example, assume that a terminal device switches from RAN node 2 (or source RAN node) to RAN node 1 (or destination RAN node). The path between the terminal device and the compute node or instance must pass through RAN node 2. For example, the path between the terminal device and compute node 1 could be: terminal device <-> RAN node 2 <-> RAN node 1 <-> compute node 1.

[0243] For example, with Figure 3B Taking deployment 2 as an example, assume that a terminal device switches from RAN node 2 (or source RAN node) to RAN node 1 (or destination RAN node). The path between the terminal device and the compute node or instance may not need to pass through RAN node 2. For example, the path between the terminal device and compute node 2 could be terminal device <-> RAN node 2 <-> compute node 2.

[0244] Understandable, Figure 3A and Figure 3B The number of RAN nodes, compute nodes, and instances mentioned are just examples. In actual applications, deployment methods can involve more RAN nodes, API gateways, compute nodes, or instances, which are not limited here.

[0245] In future generations of mobile communication systems, cloud edge nodes may be further moved down to network access nodes. Therefore, the access network can further undertake some computing functions. This computing unit with computing capabilities may be an internal unit of the base station or an external, independent unit separate from the base station's logical functions. The computing unit can be a unit that provides access services for the computing services of terminal devices. Computing services can be understood as independent application processes that implement a set or a specific set of computing functions to solve a specific problem.

[0246] The Domain Name System (DNS) provides the function of resolving application domain names to IP addresses. Terminal devices request the application's domain name from the DNS system and obtain DNS records containing the IP addresses of the compute nodes for the requested application service. This allows them to subsequently obtain application services from the compute nodes corresponding to those IP addresses. When DNS records are cached locally and have a lifespan, if the same application service is accessed again within that timeframe, the terminal device directly retrieves the corresponding compute node's IP address from the local DNS cache, thus avoiding further queries to the compute node and improving its efficiency in processing computing services. However, as the terminal device moves, the compute nodes compatible with it may change. Because the DNS cache may still be on previously accessed compute nodes, the terminal device will still attempt to connect to the original compute node, potentially leading to suboptimal or unreachable paths.

[0247] To address the aforementioned technical issues, this application provides a communication method in which a first computing node subscribes to mobility events of a terminal device and determines, through second information, that the device providing access services for the terminal device's first computing service has switched from a first network device to a second network device. Subsequently, the first computing node can release the first connection between the terminal device and the first computing node by sending third information, thereby reducing the terminal device's attempts to connect to the original computing unit and facilitating the subsequent connection of the terminal device to a compatible computing unit.

[0248] Please see Figure 4 This application provides a flowchart illustrating a communication method, which includes steps 401 to 412. Steps 401 to 412 can be executed by a communication device. The "communication device" can refer to the communication device itself (e.g., a terminal device and / or network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication device. The communication device can be one of the aforementioned... Figures 1A to 3B The architecture shown includes terminal devices, access network devices, computing nodes, or API gateways. The following description uses the example of execution by a communication device. The processing performed by a single execution entity in steps 401 to 412 can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, if the communication device is an access network device, the processing performed by the communication device can be divided into execution by at least one of CU, DU, and RU.

[0249] It should be noted that the first network device in this application embodiment can be understood as the source RAN node of the terminal device, and the second network device can be understood as the destination RAN node of the terminal device. That is, the terminal device may undergo a handover from the source RAN node to the destination RAN node. The computing nodes involved in this application (e.g., the first computing node and the second computing node) may include mobile edge computing (MEC) and / or application server (AS), etc. Furthermore, the number of first computing nodes and the number of second computing nodes can be one or more, and no specific limitation is made here. Figure 4 The communication method shown can be applied not only to the aforementioned Figure 3A The deployment shown in Figure 1 can also be applied to the aforementioned Figure 3B As shown in deployment 2.

[0250] Furthermore, the first network element and the second network element can have various forms. Specifically, the first network element can be a first network device, a gateway, or a terminal device, etc. A gateway can be, for example, an API gateway, an API proxy, a network exposure function (NET) element, a user plane gateway, etc., and the second network element can be a first computing node or a gateway. For example, the first network element is the first network device, and the second network element is the first computing node. Another example is that the first network element is a terminal device, and the second network element is the first computing node. Yet another example is that the first network element and the second network element refer to a gateway, etc., and the specifics are not limited here. Steps 401 to 412 are described below:

[0251] Step 401: The first computing node sends the first information to the first network element.

[0252] Prior to step 401, the terminal device had already established a service connection with the first computing node through the first network device. Alternatively, this can be understood as the first network device providing access services for the terminal device's first computing service and exchanging service data with the terminal device through the first computing node.

[0253] The first information in this embodiment is used to subscribe to the mobility events of the terminal device. These mobility events can also be called handover (HO) or HO events. Correspondingly, the first information can also be called an HO subscription request.

[0254] Optionally, the first information may include at least one of the following: first indication information, the identifier of the terminal device (e.g., UE identifier), the identifier of the first computing service, and the requirement information of the first computing service (e.g., transmission requirements, computing power service quality, SLA requirement information, etc.). For example, when subscribing based on a single UE single service granularity (per service per UE), the first information includes at least the UE identifier and the identifier of the first computing service. As another example, when subscribing based on any UE granularity under a single service (per service all UE), the first information includes at least the identifier of the first computing service. Yet another example, when subscribing based on UE granularity (per UE all services), the first information includes at least the UE identifier.

[0255] The first indication information is used to indicate a mobility event. Alternatively, it can be understood as indicating that the first computing node should subscribe to an event of mobility type.

[0256] The identifier of a terminal device is used to distinguish different terminal devices. This identifier can uniquely identify a terminal device within a certain range, or it can be globally unique. Of course, the identifier of a terminal device can be a single identifier or address, or it can be a combination of multiple identifiers or addresses, etc., without being limited here.

[0257] For example, the identifier of a terminal device can be represented by a UE identifier (ID), IP address, Generic Public Subscription Identifier (GPSI), etc., without being limited here.

[0258] The identifier of the first computing service is used to distinguish different computing services. Similar to the identifier of the terminal device, the identifier of the first computing service can uniquely identify the computing service within a certain range, or it can be globally unique, etc. Of course, the identifier of the first computing service can be identified by a single identifier or address, or it can be combined with multiple identifiers or multiple addresses, etc., etc., without being limited here.

[0259] The transmission requirements of the first computing service can be understood as the requirements that affect the transmission of related business processes. For example, these may include at least one of the following: latency requirements, packet error rate requirements, packet loss rate requirements, etc., without further limitation here.

[0260] In this embodiment, there are several scenarios in which the first computing node sends the first information to the first network element, which are described below:

[0261] In the first scenario, the first network element is the first network device.

[0262] This situation can also be understood as the aforementioned Figure 2A The system architecture shown is such that there is no gateway between the network devices and the computing nodes in this case.

[0263] In this scenario, the specific steps include: the first computing node sending first information to the first network device; and correspondingly, the first network device receiving the first information sent by the first computing node.

[0264] In the second scenario, the first network element is the gateway.

[0265] This situation can also be understood as the aforementioned Figure 2B The system architecture shown indicates that there is a gateway between the network devices and the computing nodes in this scenario.

[0266] In this scenario, the specific steps include: the first computing node sending first information to the gateway. Correspondingly, the gateway receives the first information sent by the first computing node.

[0267] Optionally, the gateway can receive multiple first request messages sent by multiple computing nodes, each of which is used to subscribe to the mobility events of a terminal device. After receiving the multiple first request messages, the gateway can aggregate the multiple first request messages according to the identifier of the terminal device carried in the multiple first request messages, and send the aggregated request messages to the network device that provides access services to the terminal device.

[0268] The aggregated request information may include at least one of the following: first instruction information, the identifier of the terminal device (or a list of identifiers of multiple terminal devices), the identifier of the first computing service (or a list of identifiers of multiple computing services), and the transmission requirements of the first computing service (or a list of multiple transmission requirements), etc.

[0269] It is understandable that multiple first request messages may correspond to the same terminal device or different terminal devices.

[0270] For example, compute node 1 sends request information 1 to the gateway, compute node 2 sends request information 2 to the gateway, and compute node 3 sends request information 4 to the gateway. Request information 1 and request information 3 are used to subscribe to the mobility events of terminal device 1, and request information 2 is used to subscribe to the mobility events of terminal device 2. The network device serving terminal device 1 is network device 1, and the network device serving terminal device 2 is network device 2. The gateway can then aggregate request information 1 and request information 3, send the aggregated request information to network device 1, and send request information 2 to network device 2.

[0271] In the third scenario, the first network element is a terminal device.

[0272] This situation can also be understood as computing nodes being able to directly subscribe to the mobility events of terminal devices.

[0273] In this scenario, the specific steps include: the first computing node sending first information to the terminal device; and the terminal device receiving the first information sent by the first computing node.

[0274] It is understandable that the above three situations are just examples. In actual applications, the device that interacts with the first computing node to exchange the first information can also be other devices or network elements, etc., which are not limited here.

[0275] Step 402: The first network device receives the first information.

[0276] There are several scenarios in which the first network device receives the first information, corresponding to the scenarios in step 401 above.

[0277] In one possible implementation, the first network device receives first information sent by the first computing node. Correspondingly, the first computing node sends first information to the first network device.

[0278] In another possible implementation, the first network device receives first information sent by the gateway. Correspondingly, the gateway sends first information to the first network device.

[0279] In another possible implementation, the first network device receives the first information sent by the terminal device. That is, the first computing node first sends the first information to the terminal device. Correspondingly, the terminal device receives the first information sent by the first computing node. Then, the terminal device sends the first information to the first network device. Correspondingly, the first network device receives the first information sent by the terminal device.

[0280] Optionally, after receiving the first information, the first network device sends a response message to the second network element or the terminal device. Correspondingly, the second network element receives the response message sent by the first network device. This response message can be used to indicate whether the terminal device's mobility event subscription was successful. Alternatively, after receiving the first information from the second network element, the first network device can perform authentication operations based on the information carried by the second network element or the request message. Upon successful authentication, it sends a response message to the second network element indicating successful subscription.

[0281] Step 403: The terminal device prepares to switch over to the first network device.

[0282] The handover preparation may include: a first network device sending a reference signal to a terminal device; the terminal device measuring the reference signal and determining whether the measured value satisfies a handover event. If satisfied, the terminal device switches from the first network device to the second network device.

[0283] This application does not limit the reference signal, handover event, type of handover event, or threshold of handover event in its embodiments. For example, a handover event or type of handover event can be at least one of the following: A1 event, A2 event, A3 event, A4 event, A5 event, A6 event, B1 event, or B2 event, etc. As another example, the type of handover event can be an event within the same system or an event between different systems, etc. As yet another example, the type of handover event can refer to at least one of the following: handover within the same access ring, handover across access rings, handover across network segments, etc.

[0284] For example, the conditions and meanings corresponding to the above events are shown in Table 1:

[0285] Table 1

[0286]

[0287] Optionally, the serving cell can be understood as the cell where the first network device is located, and the neighboring cell can be understood as the cell where the second network device is located.

[0288] Step 404: The first network device or the second network device determines that the second network device has a service instance of the first computing power service.

[0289] Step 405: The first network device or the second network device sends the second information to the second network element.

[0290] One possibility is that the second network element is the first computing node, meaning that either the first network device or the second network device sends the second information to the first computing node. Correspondingly, the first computing node receives the second information sent by either the first network device or the second network device.

[0291] Another possibility is that the second network element is a gateway, meaning that either the first or second network device sends the second information to the gateway. Correspondingly, the gateway receives the second information sent by either the first or second network device. Furthermore, the gateway can also, based on the previously aggregated multiple first request messages, send the second information back to multiple computing nodes separately.

[0292] Optionally, if the handover event is met, the terminal device performs a handover. A handover by the terminal device can be understood as the terminal device connecting to a second network device. For example, the terminal device switches from a first network device to a second network device. Alternatively, if the terminal device supports dual-active protocol stack handover, the connection to the first network device can remain open, meaning the terminal device can be connected to both the first and second network devices simultaneously.

[0293] Step 404 is related to step 405 and has multiple possible outcomes. Step 404 and step 405 will be explained together below:

[0294] In one possible implementation, the first network device is unaware of the computing service deployment and topology on the second network device.

[0295] In step 404, after the handover event is satisfied, the first network device can send a third request message (also called a handover request, HO request) to the second network device. Correspondingly, the second network device receives the third request message sent by the first network device. This third request message is used to request the second network device to provide access services for the terminal device's first computing service. Furthermore, the third request message can also be a request to establish network transmission resources for the first computing service, or it can refer to signaling or data corresponding to the first computing service, etc., without specific limitations here.

[0296] The third request information may be used to indicate at least one of the following: the first computing service information of the terminal device to be switched (or understood as the first computing service information of the terminal device to be switched), the context of the terminal device, etc.

[0297] Optionally, the first computing service information may include at least one of the following: the identifier of the aforementioned first computing service (or a list of identifiers of multiple computing services), the instance identifier associated with the computing service, the transmission requirements of the aforementioned first computing service, the aforementioned first indication information, the address of the computing node receiving the subscription notification, etc.

[0298] Furthermore, after receiving the handover request information sent by the first network device, the second network device can determine / judge at least one of the following: whether the second network device can provide access service for the first computing service; whether there are available instances of the first computing service on the second network device; whether there are connectable instances of the first computing service on the second network device; whether the second network device can meet the transmission requirements of the first computing service; whether the computing nodes deployed by the second network device support the first computing service; whether the second network device has instances that support the first computing service; and whether the second network device is within the scope of instances of the first computing service.

[0299] Optionally, after determining its own support status based on the handover request information, the second network device may send response information back to the first network device. The response information may indicate that the second network device supports service instances of the first computing service. Furthermore, the response information may also indicate at least one of the following: computing services or instances supported by the second network device, computing services or instances not supported by the second network device, computing services or instances accepted by the second network device, computing services or instances rejected by the second network device, or instances that the second network device is currently connecting to. Thus, the first network device determines the computing service deployment and topology on the second network device based on the response information sent back by the second network device.

[0300] For example, the switch request information indicates a desire to switch between computing service 1 and computing service 2 on the terminal device. For instance, the second network device supports computing service 1 but not computing service 2. Alternatively, it can be understood that computing service 1 has a connectable instance on the second network device, while computing service 2 does not have a connectable instance on the second network device.

[0301] For example, the switching request information indicates a desire to switch between Instance 1 and Instance 2 of computing service 1 on the terminal device. For instance, the second network device does not support Instance 1 of computing service 1, but supports Instance 2 of computing service 1. Alternatively, it can be understood that computing service 1 has no connectable Instance 1 on the second network device, but computing service 1 has a connectable Instance 2 on the second network device.

[0302] In step 405, after the first network device determines the computing service deployment and topology on the second network device based on feedback from the second network device, the first network device can directly send second information to the second network element (i.e., the first computing node or gateway). Correspondingly, the second network element receives the second information sent by the first network device. This second information is used to indicate that the first computing service / instance of the terminal device switches from the first network device to the second network device, or that the device providing access services for the first computing service / instance switches from the first network device to the second network device.

[0303] Optionally, the second information may also be used to indicate at least one of the following: the second network device can provide access services for the first computing service; the first computing service has available instances on the second network device; the first computing service has connectable instances on the second network device; the second network device is able to meet the transmission requirements of the first computing service; the computing nodes of the second network device support the first computing service; the second network device has instances that support the first computing service; the second network device is within the scope of instances of the first computing service; first indication information; the identifier of the terminal device; the identifier of the first computing service, etc.

[0304] On the other hand, the first network device can send third indication information to the second network device. After receiving the third indication information from the first network device, the second network device sends second information to the second network element according to the third indication information. Correspondingly, the second network element receives the second information sent by the second network device. The third indication information is used to instruct the second network device to send the second information to the second network element. Optionally, the third indication information can also be used to indicate at least one of the following: the identifier of the first computing service, the instance identifier related to the computing service, the address of the computing node receiving the subscription notification, etc. Thus, after receiving the third indication information from the first network device, the second network device can send the second information to the second network element according to the third indication information.

[0305] On the other hand, if the handover request information or the first computing service information sent by the first network device to the second network device already indicates the information indicated by the third indication information (e.g., the address of the computing node receiving the subscription notification), then the second network device can directly send the second information to the second network element based on the computing node address. Accordingly, the second network element receives the second information sent by the second network device.

[0306] In another possible implementation, the first network device is aware of the computing service deployment and topology on the second network device.

[0307] In step 404, after the handover event is satisfied, if the first network device perceives the deployment and topology of the computing service on the second network device, then the first network device can determine / judge at least one of the following: whether the second network device can provide access service for the first computing service; whether there are available instances of the first computing service on the second network device; whether there are connectable instances of the first computing service on the second network device; whether the second network device can meet the transmission requirements of the first computing service; whether the computing nodes deployed on the second network device support the first computing service; whether there are instances of the second network device that support the first computing service; and whether the second network device is within the range of instances of the first computing service, etc.

[0308] Optionally, the first network device determines at least one computing service or at least one instance supported by the second network device, wherein the at least one computing service includes the first computing service, or the at least one instance includes an instance of the first computing service. Then the first network device determines at least one of the above.

[0309] Optionally, the first network determines, based on the service requirements of the first computing service, that the second network device possesses a service instance of the first computing service that meets those requirements. For example, when the second network device and the first network device are located on the same access ring or in the same network segment, it is determined that the second network device possesses a service instance of the first computing service that meets the service requirements. When the second network device and the first network device are located on different access rings or in different network segments, it is determined that the service instance of the first computing service corresponding to the second network device cannot meet the service requirements of the first computing service.

[0310] In step 405, after the first network device determines the computing service deployment and topology on the second network device based on feedback from the second network device, the first network device can directly send second information to the second network element (i.e., the first computing node or gateway). Correspondingly, the second network element receives the second information sent by the first network device. This second information is used to instruct the terminal device to switch from the first network device to the second network device.

[0311] On the other hand, the first network device can send third indication information to the second network device. After receiving the third indication information from the first network device, the second network device sends second information to the second network element according to the third indication information. This third indication information is used to instruct the second network device to send second information to the second network element. Optionally, the third indication information can also be used to indicate at least one of the following: the identifier of the first computing service, the instance identifier related to the computing service, the address of the computing node receiving the subscription notification, etc. Therefore, after receiving the third indication information from the first network device, the second network device can send second information to the second network element according to the third indication information.

[0312] On the other hand, if the handover request information or the first computing service information sent by the first network device to the second network device already indicates the information indicated by the third indication information (e.g., the address of the computing node receiving the subscription notification), then the second network device can directly send the second information to the second network element based on the computing node address. Accordingly, the second network element receives the second information sent by the first network device.

[0313] Step 406: The first computing node receives the second information sent by the first network element or the second network device.

[0314] Corresponding to step 405 above, this step could be the first computing node receiving the second information sent by the first network device, the first computing node receiving the second information sent by the gateway, the first computing node receiving the second information sent by the second network device, or the first computing node receiving the second information sent by the terminal device. The corresponding descriptions can be found in the aforementioned description of step 405, and will not be repeated here.

[0315] Step 407: The first computing node sends the third information.

[0316] Step 408: The terminal device receives the third information sent by the second network element.

[0317] There are several scenarios in which the first computing node sends third information. For example, after receiving second information, the first computing node determines, based on the second information, that the device providing access service for the first computing service has switched from the first network device to the second network device. Then, the first computing node sends the third information. Alternatively, the first computing node can determine to send the third information without relying on the second information sent by the network device (e.g., the first or second network device). For instance, after a mobility event occurs on a terminal device, the terminal device sends a mobility indication to the first computing node, and the first computing node determines to send the third information based on this mobility indication. This mobility indication is used to indicate one or more of the following: the terminal device has experienced a mobility event, the terminal device is preparing for a handover, or a network device handover has already occurred.

[0318] Optionally, the situation where the first computing node receives the second information can be further divided into several scenarios. For example, the second information received by the first computing node may include first indication information, and the first computing node determines to send third information based on the first indication information. That is, the network device (first network device or second network device) determines whether a mobility event has occurred or whether reconnection is required for the terminal device, and the network device instructs the first computing node whether a mobility event has occurred or whether reconnection is required through the first indication information. Another example is that the second information received by the first computing node may not include the first indication information, meaning the first computing node itself determines whether a mobility event has occurred or whether reconnection is required for the terminal device. In the case of a mobility event or reconnection requirement for the terminal device, the first computing node sends the third information.

[0319] In this embodiment, the third information is used to indicate the release of the first connection between the terminal device and the first computing node. The first connection may include at least one of the following: a transport layer (L4) connection, an application layer (L7) connection, etc. Furthermore, the third information may include at least one of the following: an identifier of the first connection, an identifier of the terminal device, an indication value, etc. The indication value is used to indicate whether edge application server (EAS) redirection / DNS redirection / refresh, etc., is required.

[0320] It is understood that the third information in the embodiments of this application may have various names, such as connection release request, reconnection indication, connection redirection request, EAS redirection, DNS redirection, refresh connection, etc., and no specific name is limited here.

[0321] Optionally, the third information is also used to instruct that after releasing the first connection, a new connection request to the first computing service be initiated. In this way, after switching network devices, the terminal device can release the L4 or L7 connection with the first network device, thus not affecting the terminal device's ability to re-initiate a connection request to the first computing service.

[0322] Optionally, the third information is also used to instruct the clearing of DNS records on the terminal device. These DNS records include cached domain names and their corresponding IP addresses on the terminal device. This ensures that the terminal device clears its DNS records after switching network devices. Consequently, not only will subsequent re-established connections to the compute node not be based on the original compute node, but the second network device can also be triggered to select a better compute node for the terminal device's computing services.

[0323] Step 407 is related to step 408 and has multiple possible outcomes. Step 407 and step 408 will be explained together below:

[0324] In one possible implementation, the first computing node directly sends the third information to the terminal device. Correspondingly, the terminal device receives the third information sent by the first computing node.

[0325] In another possible implementation, the first computing node sends third information to the gateway. The gateway then receives the third information from the first computing node. After receiving the third information, the gateway sends third information to the terminal device. The terminal device then receives the third information from the gateway.

[0326] It is understandable that there may be minor differences in the third-party information transmitted between different devices / network elements, such as the addition, deletion, or modification of the header / tail.

[0327] Optionally, the triggering of step 407 can also be subject to a preset condition, that is, step 407 specifically means: if the preset condition is met, the first computing node sends the third information.

[0328] For example, the preset condition is that a computing task of the first computing service has been completed, or there is currently no computing task of the first computing service in progress. That is, if a computing task of the first computing service has been completed, or there is currently no computing task of the first computing service in progress, then the first computing node sends the third information.

[0329] Step 409: The terminal device releases the first connection. This step is optional.

[0330] Step 410: The terminal device sends the fourth information to the second network device. This step is optional.

[0331] Step 411: The second network device interacts with the second computing node to exchange fifth information. This step is optional.

[0332] Step 412: The terminal device interacts with the second computing node to perform computing tasks. This step is optional.

[0333] Optionally, after the terminal device receives the second network element (i.e., the first computing node or gateway), on the one hand, as shown in step 409, the terminal device can release the first connection. On the other hand, as shown in step 410, the terminal device can send fourth information to the second network device. Correspondingly, the second network device receives the fourth information sent by the terminal device. This fourth information is used to request the first computing service or to transmit user plane data for the first computing service.

[0334] Optionally, step 410 can be understood as the process by which the terminal device re-initiates a connection request to the first computing service. It can also be understood as the fourth piece of information referring to a new service connection establishment request or a scheduling request from a business server or application server (AS), etc.

[0335] Optionally, the fourth information is used to indicate at least one of the following: service identifier (e.g., anycast address or virtual IP address), port number, re-initiated service discovery, obtaining a new Edge Application Server (EAS) address, etc. For example, the fourth information is also used to determine the computing node associated with the terminal device or the first computing service.

[0336] Furthermore, after receiving the fourth information, the second network device can determine the second computing node based on the fourth information. For example, the second network device selects a new second computing node based on the identifier or address of the first computing service in the service connection establishment request. Another example is that the second network device selects a new second computing node based on the identifier of the first computing service in the AS scheduling request. Yet another example is that the second network device selects a second computing node with a better distance based on the current location of the terminal device. Still another example is that the second network device selects a better second computing node based on the requirements information of the first computing service.

[0337] Optionally, in step 411, after receiving the fourth information, the second network device can allocate a corresponding computing node to the instance of the first computing service for the terminal device based on the fourth information. For example, the second network device sends a fifth information to the second computing node. Correspondingly, the second computing node receives the fifth information sent by the second network device. This fifth information is used to instruct the second computing node to execute the first computing service, that is, to start a new computing task of the first computing service.

[0338] Optionally, in step 412, after the terminal device sends the fourth information or after the second computing node receives the fifth information, the terminal device can interact with the second computing node to perform the first computing task.

[0339] Furthermore, if the second computing node has already established a connection with the terminal device, it can also send new subscription information to the second network device. This new subscription information is used to subscribe to the terminal device's mobility events. This ensures that if the terminal device subsequently experiences another mobility event, the network device can still allocate a new computing node to the terminal device.

[0340] The method provided in this embodiment has several variations. For example, the method provided in this embodiment includes steps 401 to 408. Another example is that the method provided in this embodiment includes steps 401 to 409. Yet another example is that the method provided in this embodiment includes steps 401 to 408 and step 410. Yet another example is that the method provided in this embodiment includes steps 401 to 410. Yet another example is that the method provided in this embodiment includes steps 401 to 409 and step 411. Yet another example is that the method provided in this embodiment includes steps 401 to 408, step 410, and step 411.

[0341] In this embodiment, the first computing node subscribes to the mobility events of the terminal device and determines, through the second information, that the device providing access services for the first computing service of the terminal device has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending the third information, thereby reducing the path defects or unreachability caused by the terminal device still trying to connect to the original first computing node. It also facilitates the subsequent connection of the terminal device to the adapted second computing node, so that the service data of the terminal device after the move can still be processed through the adapted second computing node, thereby improving the user experience.

[0342] The above passed Figure 4 The general ideas and solutions provided in the embodiments of this application are briefly described. The methods provided in the embodiments of this application are divided into different cases based on various gateway scenarios. First, the system architecture does not involve gateway interaction. Second, the system architecture involves gateway interaction, and control plane signaling passes through the gateway, but user plane data does not. Third, the system architecture involves gateway interaction, and both control plane signaling and user plane data need to pass through the gateway. The above-mentioned cases are further described below with reference to the accompanying drawings.

[0343] Firstly, the system architecture applicable to the embodiments of this application does not include a gateway. That is... Figure 5 The method provided in the illustrated embodiment adopts the aforementioned Figure 2A The system architecture shown.

[0344] Please see Figure 5 , Figure 5 Another communication method provided in this application embodiment includes steps 501 to 515. Steps 501 to 515 can be executed by a communication device. "Communication device" can refer to the communication device itself (e.g., a terminal device and / or network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication device. The communication device can be as described above. Figures 1A to 3BThe architecture shown includes terminal devices, access network devices, or computing nodes. The following description uses a communication device as an example. The processing performed by a single execution entity in steps 501 to 515 can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, if the communication device is an access network device, the processing performed by the communication device can be divided into execution by at least one of CU, DU, and RU.

[0345] It should be noted that in this embodiment, the first network device can be understood as the source RAN node of the terminal device, and the second network device can be understood as the destination RAN node of the terminal device. That is, the terminal device may undergo a handover from the source RAN node to the destination RAN node. The computing nodes involved in this application (e.g., the first computing node and the second computing node) may include MECs or ASs, etc. Furthermore, the number of first computing nodes and the number of second computing nodes can be one or more; no specific limitation is made here. Figure 5 The communication method shown can be applied not only to the aforementioned Figure 3A The deployment shown in Figure 1 can also be applied to the aforementioned Figure 3B As shown in deployment 2.

[0346] also, Figure 5 In the communication method shown, from the application layer perspective: the intermediate node between the terminal device and the computing node does not process application layer protocol data packets. Before the handover, from the network side perspective: the uplink and downlink transmission of application layer data packets between the terminal device and the computing node must pass through the first network device. The description after the handover will follow after step 508. Steps 501 to 515 are described below:

[0347] Step 501: The first computing node sends a subscription request to the first network device.

[0348] Similar to the description in step 401 above, the terminal device has established a service connection with the first computing node through the first network device. Alternatively, this can be understood as the first network device providing access services for the terminal device's first computing service and interacting with the terminal device for service data through the first computing node.

[0349] The first computing node sends a subscription request to the first network device. Correspondingly, the first network device receives the subscription request sent by the first computing node. This subscription request is used to subscribe to mobility events of the terminal device.

[0350] The subscription request can be referenced from the above. Figure 4 The description of the first information in the illustrated embodiment will not be repeated here.

[0351] Step 502: The first network device sends a subscription response to the first computing node. This step is optional.

[0352] Optionally, after receiving the subscription request, the first network device sends a subscription response to the first computing node. Correspondingly, the first computing node receives the subscription response sent by the first network device.

[0353] The subscription response can be referred to in the description of the response information in step 402 above, and will not be repeated here.

[0354] Step 503: The terminal device prepares to switch over to the first network device.

[0355] In this step 503, the aforementioned method can be used as a reference. Figure 4 The description of step 403 in the illustrated embodiment will not be repeated here.

[0356] After step 503, there are two branches: one branch includes step 504, and the other branch includes steps 505 to 508. Alternatively, one branch can be understood as the first network device sending a subscription notification to the first computing node, and the other branch as the second network device sending a subscription notification to the first computing node.

[0357] Step 504: The first network device sends a subscription notification to the first computing node. This step is optional.

[0358] Optionally, after a mobility event occurs on the terminal device, the first network device sends a subscription notification to the first computing node. Correspondingly, the first computing node receives the subscription notification sent by the first network device.

[0359] In this step 504, reference can be made to the aforementioned steps. Figure 4 The descriptions related to "the first network device sending second information to the second network element" in the illustrated embodiment will not be repeated here.

[0360] Step 505: The first network device sends a handover request to the second network device. This step is optional.

[0361] Optionally, the first network device sends a handover request to the second network device. Correspondingly, the second network device receives the handover request sent by the first network device.

[0362] Step 506: The second network device sends a handover response to the first network device. This step is optional.

[0363] Optionally, after receiving the handover request from the first network device, the second network device sends a handover response to the first network device. Correspondingly, the first network device receives the handover response from the second network device.

[0364] Step 507: The second network device determines that there is a service instance of the first computing power service on the second network device. This step is optional.

[0365] Optionally, after receiving the handover request, the second network device can determine whether the second network device has a service instance of the first computing power service based on the handover request.

[0366] Step 508: The second network device sends a subscription notification to the first computing node. This step is optional.

[0367] Optionally, after a mobility event occurs on the terminal device, the second network device sends a subscription notification to the first computing node. Correspondingly, the first computing node receives the subscription notification sent by the second network device.

[0368] Steps 505 to 508 can be referred to the above. Figure 4 The descriptions related to "the second network device sending second information to the second network element" in the illustrated embodiment will not be repeated here.

[0369] Furthermore, there are several possible transmission paths for application layer data. Before a mobility event occurs on the terminal device, the transmission path for application layer data is: terminal device <-> first network device <-> first computing node. After a mobility event occurs on the terminal device, there are two scenarios (corresponding to...). Figure 5 Deployment 1 and Deployment 2 in the above will be described separately below.

[0370] For example, in deployment 1, after a mobility event occurs on the terminal device, the transmission path of application layer data is: terminal device <-> second network device <-> first network device <-> first computing node. For example, in deployment 2, after a mobility event occurs on the terminal device, the transmission path of application layer data is: terminal device <-> second network device <-> first computing node.

[0371] Step 509: The first computing node sends a connection release request to the terminal device.

[0372] After receiving the subscription notification, the first computing node sends a connection release request to the terminal device. Correspondingly, the terminal device receives the connection release request sent by the first computing node.

[0373] The connection release request can be referred to in the description of the third information in step 402 above, and will not be repeated here.

[0374] Step 510: The terminal device releases the first connection. This step is optional.

[0375] Step 511: The terminal device sends a connection request to the second network device. This step is optional.

[0376] Optionally, the terminal device sends a connection request to the second network device. Correspondingly, the second network device receives the connection request sent by the terminal device.

[0377] Steps 510 and 511 can be referred to the above. Figure 4 The descriptions of steps 409 and 410 in the illustrated embodiment are provided above. For connection requests, please refer to the foregoing. Figure 4 The description of the fourth information in the illustrated embodiment will not be repeated here.

[0378] Step 512: The second network device determines the second computing node. This step is optional.

[0379] Optionally, after receiving the connection request sent by the terminal device, the second network device can determine the second computing node based on the connection request.

[0380] Step 512 can be referred to the above. Figure 4 The descriptions related to "the second network device determining the second computing node based on the fourth information" in the illustrated embodiment will not be repeated here.

[0381] Step 513: The second network device establishes a connection with the second computing node. This step is optional.

[0382] Optionally, after the second network device determines the second computing node, the second network device establishes a connection with the second computing node.

[0383] The description of establishing a connection can be found above. Figure 4 The descriptions related to "fifth information" in the illustrated embodiments will not be repeated here.

[0384] Step 514: The terminal device interacts with the second computing node to perform computing tasks. This step is optional.

[0385] Optionally, after the second network device establishes a connection with the second computing node, the terminal device connected to the second network device can interact with the second computing node to perform the first computing task, thereby enabling the second computing node to process the first computing task of the terminal device.

[0386] Step 515: The second computing node sends a new subscription request to the second network device. This step is optional.

[0387] Optionally, after the second computing node establishes a connection with the terminal device, it can be understood that the terminal device has established a service connection with the second computing node through the second network device. Alternatively, it can be understood that the second network device has provided access services for the terminal device's first computing service and interacts with the terminal device for service data through the second computing node. The second computing node can send a new subscription request to the second network device. Correspondingly, the second network device receives the new subscription request sent by the second computing node. This new subscription request is used to subscribe to the terminal device's mobility events. This ensures that if the terminal device experiences another mobility event subsequently, it will not affect the network device's allocation of a new computing node to the terminal device.

[0388] It is understandable that step 515 can be seen as a new round of communication method, or it can be understood as step 515 being similar to step 501. The only difference between step 515 and step 501 is that the computing node and network device connected to the computing service of the terminal device are different.

[0389] The method provided in this embodiment has multiple variations. For example, the method provided in this embodiment includes steps 501, 503, 504, and 509. Another example is that the method provided in this embodiment includes steps 501, 503, and steps 505 to 509. Yet another example is that the method provided in this embodiment includes steps 501 to 504 and step 509. Yet another example is that the method provided in this embodiment includes steps 501, 503, 504, and steps 509 to 514. Yet another example is that the method provided in this embodiment includes steps 501, 503, 505 to 514. Yet another example is that the method provided in this embodiment includes steps 501, 503, 504, and steps 509 to 515. For example, the method provided in this embodiment includes steps 501, 503, 505 to 515, etc., and the specific steps are not limited here.

[0390] In this embodiment, the first computing node subscribes to the mobility events of the terminal device and determines, through the second information, that the device providing access services for the first computing service of the terminal device has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending the third information, thereby reducing the path defects or unreachability caused by the terminal device still trying to connect to the original first computing node. It also facilitates the subsequent connection of the terminal device to the adapted second computing node, so that the service data of the terminal device after the move can still be processed through the adapted second computing node, thereby improving the user experience.

[0391] The second approach involves a system architecture that includes a gateway, where control plane signaling passes through the gateway, while user plane signaling does not. That is... Figure 6 The method provided in the illustrated embodiment adopts the aforementioned Figure 2B The system architecture shown.

[0392] Please see Figure 6 , Figure 6 Another communication method provided in this application embodiment includes steps 601 to 620. Steps 601 to 620 can be executed by a communication device. "Communication device" can refer to the communication device itself (e.g., a terminal device and / or network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication device. The communication device can be one of the aforementioned... Figures 1A to 3B The architecture shown includes terminal devices, access network devices, computing nodes, or gateways. The following description uses a communication device as an example. The processing performed by a single execution entity in steps 601 to 620 can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, if the communication device is an access network device, the processing performed by the communication device can be divided into execution by at least one of CU, DU, and RU.

[0393] It should be noted that in this embodiment, the first network device can be understood as the source RAN node of the terminal device, and the second network device can be understood as the destination RAN node of the terminal device. That is, the terminal device may undergo a handover from the source RAN node to the destination RAN node. The first network element and the second network element refer to gateways. The computing nodes involved in this application (e.g., the first computing node and the second computing node) may include MECs or ASs, etc. Furthermore, the number of first computing nodes and the number of second computing nodes can be one or more; no specific limitation is made here. Figure 6 The communication method shown can be applied not only to the aforementioned Figure 3A The deployment shown in Figure 1 can also be applied to the aforementioned Figure 3B As shown in deployment 2.

[0394] also, Figure 6 In the communication method shown, specifically from the application layer perspective: the intermediate node between the terminal device and the computing node does not process application layer protocol data packets. Before the handover, from the network side perspective: the uplink and downlink transmission of application layer data packets between the terminal device and the computing node must pass through the first network device. The description after the handover will be provided after step 611. Steps 601 to 620 are described below:

[0395] Step 601: The first computing node sends a first request message to the gateway.

[0396] The first computing node sends a first request message to the gateway, and the gateway receives the first request message sent by the first computing node. This first request message can also be called a subscription request, used to subscribe to the mobility events of terminal devices.

[0397] In the implementation of this application, the number of first computing nodes can be one or more, and no specific limit is made here.

[0398] Optionally, there are multiple first computing nodes, each sending a first request message to the network element. Correspondingly, the gateway receives multiple first request messages from the multiple first computing nodes, each used to subscribe to mobility events of the terminal device.

[0399] In this embodiment, the description of the first request information can be referred to the relevant descriptions of "first information" or "subscription request" in the previous embodiments, and will not be repeated here.

[0400] Step 602: The gateway aggregates multiple first request information. This step is optional.

[0401] Optionally, if the gateway receives multiple first request messages from multiple computing nodes, it can aggregate the multiple first request messages. Accordingly,

[0402] Furthermore, the gateway can determine the access network device serving each terminal device based on the terminal device identifier carried in multiple first request messages, and then aggregate them according to the access network device. This allows the gateway to have only one subscription with each access network device, facilitating subsequent maintenance and reducing the number of interactions.

[0403] For example, the gateway receives subscription request 1 from compute node 1, subscription request 2 from compute node 2, and subscription request 3 from compute node 3. Subscription request 1 is used to subscribe to the mobility events of UE1, subscription request 2 is used to subscribe to the mobility events of UE2, and subscription request 3 is used to subscribe to the mobility events of UE1. The base station serving UE1 is xNB1, and the base station serving UE1 is xNB2. Therefore, the gateway can aggregate the subscription requests sent by compute node 1 and compute node 3; that is, the gateway can aggregate subscription request 1 and subscription request 3.

[0404] Optionally, if the gateway receives a first request from a compute node, the "aggregation" process in this step can be omitted. Alternatively, the gateway can receive a first request from a compute node and execute step 603.

[0405] Step 603: The gateway sends the first message (subscription request) to the first network device.

[0406] After receiving at least one first request message, the gateway can send first information to the first network device. Correspondingly, the first network device receives the first information sent by the gateway.

[0407] Optionally, if at least one first request message is a first request message, after receiving the first request message, the gateway may send the first message to the first network device.

[0408] Optionally, if at least one first request information is two or more first request information, after receiving at least two first request information, the gateway may first aggregate multiple first request information to obtain first information, and then send the first information to the first network device.

[0409] The first information can be equivalent to the first request information, or it can be obtained by processing at least one request information. This processing may include at least one of the following: modification, adjustment, deletion, addition, or aggregation of header or footer information, etc., without specific limitations here. Alternatively, it can be understood that subscription requests exchanged between different network elements may be the same or different.

[0410] For example, continuing the above example, the gateway sends subscription request 1 to xNB1 and subscription request 2 to xNB2. Subscription request 1 is obtained by aggregating subscription request 1 and subscription request 3.

[0411] Step 604: The first network device sends a subscription response to the gateway. This step is optional.

[0412] Optionally, after receiving the subscription request, the first network device sends a subscription response to the first computing node. Correspondingly, the first computing node receives the subscription response sent by the first network device.

[0413] The subscription response can be referred to in the description of the response information in step 402 above, and will not be repeated here.

[0414] For example, continuing the above example, after the gateway sends subscription request 1 to xNB1, xNB1 sends subscription response 1 corresponding to subscription request 1 to the gateway. Similarly, after the gateway sends subscription request 2 to xNB2, xNB2 sends subscription response 2 corresponding to subscription request 2 to the gateway.

[0415] Step 605: The gateway distributes the subscription response based on the subscription. This step is optional.

[0416] Optionally, after receiving the subscription response, the gateway can send a subscription response to the first compute node based on the subscription. Correspondingly, the first compute node receives the subscription response sent by the gateway.

[0417] Furthermore, if the subscription request sent by the aforementioned gateway is an aggregated set of multiple subscription requests, the gateway can also determine how to distribute the subscription response to multiple computing nodes based on the previous aggregation rules after receiving the subscription response.

[0418] For example, continuing the above example, the gateway receives subscription response 1 corresponding to subscription request 1 sent by xNB1. The gateway receives subscription response 2 corresponding to subscription request 2 sent by xNB2. Then, based on the subscription status or aggregation rules of multiple compute nodes, the gateway sends subscription response 1 to compute node 1, subscription response 1 to compute node 3, and subscription response 2 to compute node 2.

[0419] Step 606: The terminal device prepares to switch over to the first network device.

[0420] In this step 603, reference can be made to the aforementioned steps. Figure 4 The description of step 403 in the illustrated embodiment will not be repeated here.

[0421] After step 606, there are two branches: one branch includes step 607, and the other branch includes steps 608 to 611. Alternatively, one branch can be understood as the first network device sending a subscription notification to the gateway, and the other branch as the second network device sending a subscription notification to the gateway.

[0422] Step 607: The first network device sends a subscription notification to the gateway. This step is optional.

[0423] Optionally, after a mobility event occurs on the terminal device, the first network device sends a subscription notification to the gateway. Correspondingly, the gateway receives the subscription notification sent by the first network device.

[0424] In this step 607, reference can be made to the aforementioned steps. Figure 4 The descriptions related to "the first network device sending second information to the second network element" in the illustrated embodiment will not be repeated here.

[0425] Step 608: The first network device sends a handover request to the second network device. This step is optional.

[0426] Step 609: The second network device sends a handover response to the first network device. This step is optional.

[0427] Step 610: The second network device determines that there is a service instance of the first computing power service on the second network device. This step is optional.

[0428] Step 611: The second network device sends a subscription notification to the gateway. This step is optional.

[0429] Optionally, after a mobility event occurs on the terminal device, the second network device sends a subscription notification to the gateway. Correspondingly, the gateway receives the subscription notification sent by the second network device.

[0430] Steps 608 to 611 can refer to the aforementioned steps. Figure 4 The descriptions related to "the second network device sending second information to the second network element" in the illustrated embodiment will not be repeated here.

[0431] In addition, due to Figure 6 In the illustrated embodiment, control plane signaling passes through a gateway, while user plane signaling does not. There are several possible transmission paths for application layer data. Before a mobility event occurs on the terminal device, the transmission path for application layer data is: terminal device <-> first network device <-> first computing node. After a mobility event occurs on the terminal device, there are two scenarios (corresponding to...). Figure 6 Deployment 1 and Deployment 2 in the above will be described separately below.

[0432] For example, in deployment 1, after a mobility event occurs on the terminal device, the transmission path of application layer data is: terminal device <-> second network device <-> first network device <-> first computing node. For example, in deployment 2, after a mobility event occurs on the terminal device, the transmission path of application layer data is: terminal device <-> second network device <-> first computing node.

[0433] Step 612: The gateway distributes subscription notifications based on the subscription.

[0434] After receiving the subscription notification from the first network device or the second network device, the gateway can distribute the subscription notification to the first computing node. The distribution process can refer to the distribution process in step 605 above, and will not be repeated here.

[0435] Step 613: The first computing node determines to initiate a connection release request.

[0436] After receiving the subscription notification from the gateway, the first compute node can determine whether to initiate a connection release request based on the subscription notification. If it decides to initiate a connection release request, step 614 is triggered.

[0437] Optionally, some restrictions can be added to this step. For example, a connection release request can be initiated only after the first computing service has been completed.

[0438] Additionally, interactions can be added to the control plane to enable the gateway to initiate connection release requests; specific details are not specified here.

[0439] Step 614: The first computing node sends a connection release request to the terminal device.

[0440] Step 615: The terminal device releases the first connection. This step is optional.

[0441] Step 616: The terminal device sends a connection request to the second network device. This step is optional.

[0442] Step 617: The second network device determines the second computing node. This step is optional.

[0443] Steps 614 to 617 can be referred to the above. Figure 5 The relevant descriptions of steps 509 to 512 in the illustrated embodiments, or refer to the foregoing Figure 4 The relevant descriptions of steps 407 to 410 in the illustrated embodiment will not be repeated here.

[0444] Step 618: The second network device and the second computing node establish a connection through the gateway. This step is optional.

[0445] Optionally, after the second network device determines the second computing node, because Figure 6 In the illustrated embodiment, control plane signaling needs to pass through a gateway; therefore, the second network device and the second computing node establish a connection through the gateway. The description of the connection establishment can be found in the foregoing. Figure 4 The descriptions related to "fifth information" in the illustrated embodiments will not be repeated here.

[0446] It should be noted that the gateway connected to the second computing node can be the same as or different from the gateway connected to the first computing node; no specific restrictions are imposed here.

[0447] Step 619: The terminal device and the second computing node interact with each other to perform computing tasks. This step is optional.

[0448] Step 620: The second computing node sends a new subscription request to the second network device. This step is optional.

[0449] Steps 619 and 620 can be referred to the above. Figure 5 The descriptions of steps 514 and 515 in the illustrated embodiments, or step 619, can be referenced from the foregoing. Figure 4 The relevant description of step 412 in the illustrated embodiment will not be repeated here.

[0450] The method provided in this embodiment has multiple variations. For example, the method provided in this embodiment includes steps 601 to 603, 606, 607, and 612 to 614. Another example is that the method provided in this embodiment includes steps 601 to 603, 606, and 608 to 614. Yet another example is that the method provided in this embodiment includes steps 601 to 614. Yet another example is that the method provided in this embodiment includes steps 601 to 619. Yet another example is that the method provided in this embodiment includes steps 601 to 620, and so on. The specific implementation is not limited here.

[0451] In this embodiment, on one hand, the gateway aggregates subscriptions to mobility events of the terminal device from multiple computing nodes and sends the aggregated subscriptions to the corresponding network devices, thereby reducing the complexity of network devices maintaining subscriptions. On the other hand, the first computing node can determine, through second information, that the device providing access services for the terminal device's first computing service has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending third information, thereby reducing the path optimization or unreachability caused by the terminal device still attempting to connect to the original first computing node. This also facilitates the terminal device's subsequent connection to the adapted second computing node, ensuring that the terminal device's business data can still be processed through the adapted second computing node after migration, thus improving the user experience.

[0452] Thirdly, the system architecture applicable to the embodiments of this application includes a gateway, and both control plane signaling and user plane data need to pass through the gateway. That is, the aforementioned... Figure 2B The system architecture shown is... Figure 7 The method provided in the illustrated embodiment adopts the aforementioned Figure 2B The system architecture shown.

[0453] Please see Figure 7 , Figure 7 Another communication method provided in this application embodiment includes steps 701 to 722. Steps 701 to 722 can be executed by a communication device. "Communication device" can refer to the communication device itself (e.g., a terminal device and / or network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication device. The communication device can be one of the aforementioned... Figures 1A to 3BThe architecture shown includes terminal devices, access network devices, computing nodes, or gateways. The following description uses the example of execution by a communication device. The processing performed by a single execution entity in steps 701 to 722 can also be divided into execution by multiple execution entities, which can be logically and / or physically separated. For example, if the communication device is an access network device, the processing performed by the communication device can be divided into execution by at least one of CU, DU, and RU.

[0454] It should be noted that in this embodiment, the first network device can be understood as the source RAN node of the terminal device, and the second network device can be understood as the destination RAN node of the terminal device. That is, the terminal device may undergo a handover from the source RAN node to the destination RAN node. The first network element and the second network element refer to gateways. The computing nodes involved in this application (e.g., the first computing node and the second computing node) may include MECs or ASs, etc. Furthermore, the number of first computing nodes and the number of second computing nodes can be one or more; no specific limitation is made here. Figure 7 The communication method shown can be applied not only to the aforementioned Figure 3A The deployment shown in Figure 1 can also be applied to the aforementioned Figure 3B As shown in deployment 2.

[0455] also, Figure 7 In the communication method shown, specifically from the application layer perspective: the intermediate node between the terminal device and the computing node does not process application layer protocol data packets. Before the handover, from the network side perspective: the uplink and downlink transmission of application layer data packets between the terminal device and the computing node must pass through the first network device. The description after the handover will be provided after step 711. Steps 701 to 722 are described below:

[0456] Step 701: The first computing node sends a first request message to the gateway.

[0457] Step 702: The gateway aggregates multiple first request information. This step is optional.

[0458] Step 703: The gateway sends the first message (subscription request) to the first network device.

[0459] Step 704: The first network device sends a subscription response to the gateway. This step is optional.

[0460] Step 705: The gateway distributes the subscription response based on the subscription. This step is optional.

[0461] Step 706: The terminal device prepares to switch over to the first network device.

[0462] Step 707: The first network device sends a subscription notification to the gateway. This step is optional.

[0463] Step 708: The first network device sends a handover request to the second network device. This step is optional.

[0464] Step 709: The second network device sends a handover response to the first network device. This step is optional.

[0465] Step 710: The second network device determines that there is a service instance of the first computing power service on the second network device. This step is optional.

[0466] Step 711: The second network device sends a subscription notification to the gateway. This step is optional.

[0467] Step 712: The gateway distributes subscription notifications based on the subscription. This step is optional.

[0468] Steps 701 to 712 can be referred to the above. Figure 6 The descriptions related to steps 601 to 612 in the illustrated embodiment will not be repeated here.

[0469] This embodiment and Figure 6 The main difference in the illustrated embodiments is that, Figure 6 In the illustrated embodiment, control plane signaling passes through the gateway, while user plane signaling does not. Figure 7 In the illustrated embodiment, both control plane signaling and user plane data need to pass through a gateway.

[0470] in, Figure 7 In the illustrated embodiment, before a mobility event occurs on the terminal device, the data transmission path for the application layer is: terminal device <-> first network device <-> gateway <-> first computing node. After a mobility event occurs on the terminal device, there are two scenarios (corresponding to...). Figure 7 Deployment 1 and Deployment 2 in the above will be described separately below.

[0471] For example, in deployment 1, after a mobility event occurs on the terminal device, the data transmission path for the application layer is: terminal device <-> second network device <-> first network device <-> gateway <-> first computing node. For example, in deployment 2, after a mobility event occurs on the terminal device, the data transmission path for the application layer is: terminal device <-> second network device <-> gateway <-> first computing node.

[0472] Step 713: The gateway determines to initiate a connection release request.

[0473] After receiving a subscription notification from the first or second network device, the gateway can determine whether to initiate a connection release request based on the subscription notification. If it determines to initiate a connection release request, step 714 or step 716 is triggered.

[0474] Understandably, due to Figure 7 In the illustrated embodiment, both control plane signaling and user plane data need to pass through the gateway. Therefore, the gateway can determine which computing node the terminal device is connected to, and thus determine to initiate the corresponding connection release request.

[0475] Optionally, some restrictions can be added to this step. For example, a connection release request can be initiated only after the first computing service has been completed.

[0476] Step 714: The gateway sends a connection release request to the first computing node. This step is optional.

[0477] Optionally, after determining that a connection release request needs to be initiated, the network element may send a connection release request to the first computing node. Correspondingly, the first computing node receives the connection release request sent by the network element. This connection release request is used to request the release of the first connection between the current first computing node and the terminal device.

[0478] The connection release request may carry at least one of the following: the identifier of the first connection.

[0479] The "connection release request" can be referred to in the above. Figure 4 Description of "third information" in the illustrated embodiment.

[0480] Furthermore, the "connection release requests" transmitted between different network elements / devices are related. For example, the connection release requests corresponding to steps 714, 715, or 716 can be related.

[0481] For example, the connection release request in step 715 is related to the connection release request in step 714. For instance, this relationship can indicate that the connection release request in step 715 is obtained by processing the connection release request in step 714. This processing may include at least one of the following: modification, adjustment, deletion, addition, or aggregation of information such as headers or footers, etc., without specific limitations here. Alternatively, it can be understood that the connection release requests exchanged between different network elements may be the same or different.

[0482] Step 715: The first compute node sends a connection release request / response to the gateway. This step is optional.

[0483] Optionally, after receiving the connection release request from the gateway, if the connection can be released at present, the first compute node can send a 714 connection release request response message (i.e., a connection release response) to the gateway. The gateway then receives the connection release response from the first compute node. If the conditions for releasing the connection are not currently met, the first compute node will proactively send a connection release request to the gateway when the conditions for connection release become available later. The gateway then receives the connection release request from the first compute node.

[0484] Step 716: The gateway sends a connection release request to the terminal device.

[0485] The triggering condition for this step can be after the gateway determines to initiate connection release, after the gateway receives the connection release request sent by the first computing node, or after the first computing service has been completed, etc. The specific condition is not limited here.

[0486] For example, step 713 can trigger step 716. Similarly, step 714 can trigger step 716. And again, step 715 can trigger step 716.

[0487] Once the triggering conditions are met, the gateway sends a connection release request to the terminal device.

[0488] Step 717: The terminal device releases the first connection. This step is optional.

[0489] Step 718: The terminal device sends a connection request to the second network device. This step is optional.

[0490] Step 719: The second network device determines the second computing node. This step is optional.

[0491] Step 720: The terminal device establishes a connection with the second computing node through a gateway. This step is optional.

[0492] Steps 717 to 720 can refer to the aforementioned steps. Figure 6 The relevant descriptions of steps 615 to 618 in the illustrated embodiment will not be repeated here.

[0493] It should be noted that the gateway connected to the second computing node can be the same as or different from the gateway connected to the first computing node; no specific restrictions are imposed here.

[0494] Step 721: The terminal device and the second computing node interact with each other through the gateway for computing tasks. This step is optional.

[0495] Optionally, after the second network device and the second computing node establish a connection through the gateway, the terminal device connected to the second network device can interact with the second computing node through the gateway to perform the first computing task, thereby enabling the second computing node to process the first computing task of the terminal device.

[0496] Step 722: The second computing node sends a new subscription request to the second network device. This step is optional.

[0497] Optionally, after the second computing node establishes a connection with the terminal device, it can be understood that the terminal device has established a service connection with the second computing node through network elements and the second network device. Alternatively, it can be understood that the second network device has provided access services for the terminal device's first computing service and interacts with the terminal device for service data through the second computing node and the gateway. The second computing node can send a new subscription request to the second network device through the gateway. Correspondingly, the second network device receives the new subscription request sent by the gateway. This new subscription request is used to subscribe to the terminal device's mobility events. This ensures that if the terminal device experiences another mobility event subsequently, it will not affect the network device's allocation of a new computing node to the terminal device.

[0498] The method provided in this embodiment has multiple variations. For example, the method provided in this embodiment includes steps 701 to 703, 706, 707, and steps 712 to 716. Another example is that the method provided in this embodiment includes steps 701 to 703, 706, and 708 to 716. Yet another example is that the method provided in this embodiment includes steps 701 to 716. Yet another example is that the method provided in this embodiment includes steps 701 to 720. Yet another example is that the method provided in this embodiment includes steps 701 to 722, and so on. The specific implementation is not limited here.

[0499] In this embodiment, on one hand, the gateway aggregates subscriptions to mobility events of the terminal device from multiple computing nodes and sends the aggregated subscriptions to the corresponding network devices, thereby reducing the complexity of network devices maintaining subscriptions. On the other hand, the first computing node can determine, through second information, that the device providing access services for the terminal device's first computing service has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending third information, thereby reducing the path optimization or unreachability caused by the terminal device still attempting to connect to the original first computing node. This also facilitates the terminal device's subsequent connection to the adapted second computing node, ensuring that the terminal device's business data can still be processed through the adapted second computing node after migration, thus improving the user experience.

[0500] The communication method in the embodiments of this application has been described above. The communication device in the embodiments of this application is described below. Please refer to [link / reference]. Figure 8 This application provides an embodiment of the communication device 800. This communication device 800 can implement the functions of the first computing node / first network device / second network device / gateway / terminal device in the above-described method embodiments, and therefore also achieves the beneficial effects of the above-described method embodiments. In this application embodiment, the communication device 800 can be a communication device, or it can be an integrated circuit or component within a communication device, such as a chip. The communication device 800 includes a transceiver unit 801. Alternatively, the communication device 800 includes a transceiver unit 802 and a processing unit 802.

[0501] In one possible implementation, the communication device 800 is as described above. Figures 1A to 7 The first computing node in the illustrated embodiment has the following functions for each unit:

[0502] The transceiver unit 801 is used to send first information to the first network element, and the first information is used to subscribe to the mobility events of the terminal device;

[0503] The transceiver unit 801 is also used to receive second information, which is used to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device.

[0504] The transceiver unit 801 is also used to send third information, which is used to indicate the release of the first connection between the terminal device and the first computing node.

[0505] Optionally, the third information is also used to instruct that after the first connection is released, a new connection request to the first computing service be initiated.

[0506] Optionally, the third information is also used to instruct the cleanup of DNS records on the terminal device.

[0507] Optionally, the transceiver unit 801 is specifically used to send third information if the first computing service has finished executing.

[0508] Optionally, the transceiver unit 801 is specifically used to receive second information sent by the first network device or the second network device.

[0509] Optionally, the first network element is a first network device, a terminal device, or a gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0510] Optionally, the first information is also used by the first network element to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0511] Optionally, the transceiver unit 801 is specifically used to receive the second information sent by the first network element; the transceiver unit 801 is specifically used to send the third information to the first network element.

[0512] Optionally, the second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0513] Optionally, the first information includes at least one of the following: first indication information, the identifier of the terminal device, the identifier of the first computing service, and the transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0514] Optionally, the second information includes at least one of the following: first indication information, the identifier of the terminal device, and the identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0515] Optionally, the first connection includes at least one of the following: a transport layer connection and an application layer connection.

[0516] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1A to 7 The description of the first computing node in the illustrated embodiment is similar and will not be repeated here.

[0517] In this embodiment, the transceiver unit 801 subscribes to the mobility events of the terminal device by sending first information, and determines through second information that the device providing access services for the first computing service of the terminal device has switched from the first network device to the second network device. Then, the first computing node can release the first connection between the terminal device and the first computing node by sending third information, thereby reducing the path defects or unreachability caused by the terminal device still trying to connect to the original first computing node. It also facilitates the subsequent connection of the terminal device to the adapted second computing node, so that the service data of the terminal device after the move can still be processed through the adapted second computing node, thereby improving the user experience.

[0518] In another possible implementation, the communication device 800 is as described above. Figures 1A to 7 The first network device in the illustrated embodiment has the following functions for each unit:

[0519] The transceiver unit 801 is used to receive first information sent by the second network element. The first information is used for the first computing node to subscribe to the mobility event of the terminal device and for the first computing node to connect to the service instance of the first computing service.

[0520] The transceiver unit 801 is also used to send second information to the second network element, the second information being used to instruct the terminal device to switch from the first network device to the second network device.

[0521] Optionally, the transceiver unit 801 is specifically used to send second information to the second network element when the second network device supports a service instance of the first computing service.

[0522] Optionally, the transceiver unit 801 is further configured to receive second indication information sent by the second network device, the second indication information being used to indicate that the second network device supports a service instance of the first computing service.

[0523] Optionally, the processing unit 802 is configured to determine at least one service instance supported by the second network device; the processing unit 802 is further configured to determine that at least one service instance includes a service instance of the first computing service.

[0524] Optionally, the transceiver unit 801 is further configured to send a third request message to the second network device, the third request message being used to request the second network device to provide access service for the first computing service; the transceiver unit 801 is further configured to receive a response message to the third request message sent by the second network device, the response message being used to indicate acceptance of the request to switch the first computing service.

[0525] Optionally, the response information may also be used to indicate whether the second network device supports a service instance of the first computing service.

[0526] Optionally, the response information may also be used to indicate the service instance identifier that the second network device is connecting to.

[0527] Optionally, the processing unit 802 is further configured to determine, based on the service requirements of the first computing service, whether the second network device has a service instance that meets the service requirements of the first computing service.

[0528] Optionally, the second network element is a first computing node or a gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0529] Optionally, the second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0530] Optionally, the first information includes at least one of the following: first indication information, the identifier of the terminal device, the identifier of the first computing service, and the transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0531] Optionally, the second information includes at least one of the following: first indication information, the identifier of the terminal device, and the identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0532] Optionally, the first connection includes at least one of the following: a transport layer connection and an application layer connection.

[0533] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1A to 7 The description of the first network device in the illustrated embodiment is similar and will not be repeated here.

[0534] In this embodiment, after receiving the subscription information of the second network element, the transceiver unit 801 sends feedback to the second network element that the terminal device has switched from the first network device to the second network device, thereby providing a basis for judgment to facilitate the subsequent release of the connection between the first computing node and the terminal device.

[0535] In another possible implementation, the communication device 800 is as described above. Figures 1A to 7 The second network device in the illustrated embodiment has the following functions for each unit:

[0536] The transceiver unit 801 is used to receive a third request information sent by the first network device, the third request information being used to request the second network device to provide access service for the first computing service of the terminal device;

[0537] The transceiver unit 801 is also used to send a response message to the third request message to the first network device. The response message is used to indicate acceptance of the request to switch the first computing service.

[0538] Optionally, the transceiver unit 801 is specifically used to send response information to the first network device if a service instance of the first computing service exists.

[0539] Optionally, the response information may also be used to indicate whether the second network device supports a service instance of the first computing service.

[0540] Optionally, the response information may also be used to indicate the service instance identifier that the second network device is connecting to.

[0541] Optionally, the transceiver unit 801 is further configured to receive a fourth message sent by the terminal device, the fourth message being used to request the first computing service or transmit user plane data of the first computing service; the transceiver unit 801 is further configured to send a fifth message to the second computing node, the fifth message being used to instruct the second computing node to perform the first computing service.

[0542] Optionally, the response information may also be used to indicate at least one of the following: a second computing service in the first computing service supported by the second network device, and a third computing service in the first computing service not supported by the second network device.

[0543] Optionally, the transceiver unit 801 is further configured to receive third indication information sent by the first network device, the third indication information being used to instruct the transmission of second information to the first computing node, the second information being used to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device; the transceiver unit 801 is further configured to transmit the second information to the first computing node.

[0544] Optionally, the third request information includes at least one of the following: the identifier of the first computing service, the transmission requirements of the first computing service, and the notification acceptance address information.

[0545] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1A to 7 The description of the second network device in the illustrated embodiment is similar and will not be repeated here.

[0546] In this embodiment, the transceiver unit 801 can indicate to the first network device through response information that it accepts the request to provide access services for the first computing service, so as to improve the first network device's understanding of the capabilities of the second network device and facilitate finding a suitable computing node for the terminal device in the future.

[0547] In another possible implementation, the communication device 800 is as described above. Figure 2B , Figures 4 to 7 In the gateway shown in the embodiment, the functions of each unit are as follows:

[0548] The transceiver unit 801 is used to receive multiple first request messages sent by multiple computing nodes, and the multiple first request messages are used to subscribe to the mobility events of the terminal device.

[0549] Processing unit 802 is used to aggregate multiple first request information and send first information to the first network device. The first information is used to subscribe to the mobility event of the terminal device and the first computing node has connected to the service instance of the first computing service.

[0550] The transceiver unit 801 is also used to send second information to multiple computing nodes, the second information being used to instruct the terminal device to switch from the first network device to the second network device.

[0551] Optionally, the transceiver unit 801 is further configured to send a second request message to a first computing node among a plurality of computing nodes, the second request message being used to request the release of the first connection between the terminal device and the first computing node; the transceiver unit 801 is further configured to send a third message to the terminal device, the third message being used to instruct the release of the first connection between the terminal device and the first computing node.

[0552] Optionally, the second information is also used to indicate that the second network device supports a service instance of the first computing service.

[0553] Optionally, the first information includes at least one of the following: first indication information, the identifier of the terminal device, the identifier of the first computing service, and the transmission request of the first computing service; the first indication information is used to indicate a mobility event.

[0554] Optionally, the second information includes at least one of the following: first indication information, the identifier of the terminal device, and the identifier of the first computing service; the first indication information is used to indicate a mobility event.

[0555] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figure 2B , Figures 4 to 7 The description of the first network device in the illustrated embodiment is similar and will not be repeated here.

[0556] In this embodiment, by aggregating the distribution of multiple first request information and second information through the processing unit 802, not only can the complexity of network devices maintaining multiple subscriptions be reduced, but also subsequent terminal devices can be reconnected to new computing nodes based on the second information.

[0557] In another possible implementation, the communication device 800 is as described above. Figures 1A to 7 In the terminal device shown in the embodiment, the functions of each unit are as follows:

[0558] The transceiver unit 801 is used to receive third information sent by the second network element, and the third information is used to release the first connection between the terminal device and the first computing node;

[0559] The transceiver unit 801 is also used to send fourth information to the second network device, the fourth information being used to determine the computing node associated with the terminal device.

[0560] Optionally, the processing unit 802 is used to release the first connection and / or re-initiate a connection request to the first computing service.

[0561] Optionally, the processing unit 802 is used to clean up the Domain Name System (DNS) records of the terminal device.

[0562] Optionally, the second network element is a first computing node or a gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes, and the multiple first request information are used to subscribe to the mobility events of the terminal device.

[0563] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1A to 7 The terminal devices in the illustrated embodiments are described similarly, and will not be repeated here.

[0564] In this embodiment, the transceiver unit 801 can obtain the connection release request of the second network element through the received third information, and use the fourth information to enable the second network device to select a suitable computing node for the terminal device. This reduces the risk of the terminal device attempting to connect to the original computing node after switching from the first network device to the second network device, thus facilitating subsequent connection of the terminal device to a suitable computing node.

[0565] Please see Figure 9 This is another schematic structural diagram of the communication device 900 provided in this application. The communication device 900 includes a logic circuit 901 and an input / output interface 902. The communication device 900 can be a chip or an integrated circuit.

[0566] in, Figure 8 The transceiver unit 801 shown can be a communication interface, which can be... Figure 9 The input / output interface 902 in the communication interface may include an input interface and an output interface. Alternatively, the communication interface may also be a transceiver circuit, which may include an input interface circuit and an output interface circuit. Figure 8 The processing unit 802 shown can be Figure 9 The logic circuit 901 in the middle.

[0567] The logic circuit 901 and the input / output interface 902 can also perform other steps performed by the first computing node, the first network device, the second network device, the gateway, or the terminal device in any embodiment and achieve corresponding beneficial effects, which will not be elaborated here.

[0568] Optionally, the logic circuit 901 can be a processing device, the functions of which can be partially or entirely implemented in software.

[0569] Optionally, the processing apparatus may include a memory and a processor, wherein the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to perform the corresponding processing and / or steps in any of the method embodiments.

[0570] Optionally, the processing device may consist of only a processor. A memory for storing computer programs is located outside the processing device, and the processor is connected to the memory via circuitry / wires to read and execute the computer programs stored in the memory. The memory and processor may be integrated together or physically independent of each other.

[0571] Optionally, the processing device may be one or more chips, or one or more integrated circuits. For example, the processing device may be one or more field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), system on-chips (SoCs), central processors (CPUs), network processors (NPs), digital signal processors (DSPs), microcontroller units (MCUs), programmable logic devices (PLDs), or other integrated chips, or any group of the above chips or processors.

[0572] Please see Figure 10 The communication device 1000 mentioned in the above embodiments provided for the embodiments of this application can specifically be a communication device that serves as a first computing node, gateway, or terminal device in the above embodiments.

[0573] The present invention provides a possible logical structure diagram of the communication device 1000, which may include, but is not limited to, at least one processor 1001 and a communication port 1002.

[0574] in, Figure 8 The transceiver unit 801 shown can be a communication interface, which can be... Figure 10 The communication port 1002 may include an input interface and an output interface. Alternatively, the communication port 1002 may also be a transceiver circuit, which may include an input interface circuit and an output interface circuit.

[0575] Further optionally, the device may also include at least one of a memory 1003 and a bus. In embodiments of this application, the at least one processor 1001 is used to control the operation of the communication device 1000.

[0576] Furthermore, the processor 1001 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0577] It is understandable that this application relates to Figure 10 The number of each component shown is not limited. For example, the number of processors 1001, the number of communication ports 1002, and the number of memory 1003 can each be one or more, and the specific number is not limited here.

[0578] It should be noted that, Figure 10 The communication device 1000 shown can be used to implement the steps implemented by the first computing node, gateway, or terminal device in the aforementioned method embodiments, and achieve the corresponding technical effects. Figure 10 The specific implementation of the communication device shown can be referred to the description in the foregoing method embodiments, and will not be repeated here.

[0579] Please see Figure 11 The above-described embodiments of the communication device 1100 provided in this application are structural schematic diagrams. Specifically, the communication device 1100 can be a communication device serving as a first network device or a second network device as described in the above embodiments. The structure of the communication device can be referenced from... Figure 11 The structure shown.

[0580] The communication device 1100 includes at least one processor 1111 and at least one network interface 1114. Optionally, the communication device further includes at least one memory 1112, at least one transceiver 1113, and one or more antennas 1115. The processor 1111, memory 1112, transceiver 1113, and network interface 1114 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited thereto. The antenna 1115 is connected to the transceiver 1113. The network interface 1114 enables the communication device to communicate with other communication devices through a communication link. For example, the network interface 1114 may include a network interface between the communication device and core network equipment, such as an S1 interface; the network interface may also include a network interface between the communication device and other communication devices (e.g., other network devices or core network equipment), such as an X2 or Xn interface.

[0581] in, Figure 8 The transceiver unit 801 shown can be a communication interface, which can be... Figure 11 The network interface 1114 may include an input interface and an output interface. Alternatively, the network interface 1114 may also be a transceiver circuit, which may include an input interface circuit and an output interface circuit.

[0582] The processor 1111 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs, for example, to support the communication device in performing the actions described in the embodiments. The communication device may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data, while the central processing unit is mainly used to control the entire communication device, execute software programs, and process data from the software programs. Figure 11 The processor 1111 in the communication device can integrate the functions of a baseband processor and a central processing unit. Those skilled in the art will understand that the baseband processor and the central processing unit can also be independent processors interconnected via technologies such as buses. Those skilled in the art will understand that the communication device can include multiple baseband processors to adapt to different network standards, and multiple central processing units to enhance its processing capabilities. The various components of the communication device can be connected via various buses. The baseband processor can also be described as a baseband processing circuit or a baseband processing chip. The central processing unit can also be described as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored in memory as a software program, with the processor executing the software program to implement the baseband processing function.

[0583] The memory is primarily used to store software programs and data. The memory 1112 can exist independently or be connected to the processor 1111. Optionally, the memory 1112 can be integrated with the processor 1111, for example, integrated into a single chip. The memory 1112 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 1111. The various types of computer program code being executed can also be considered as drivers for the processor 1111.

[0584] Figure 11 Only one memory and one processor are shown. In actual communication devices, there may be multiple processors and multiple memories. Memory can also be called storage medium or storage device, etc. Memory can be a storage element on the same chip as the processor, i.e., an on-chip storage element, or it can be a separate storage element; this application does not limit this.

[0585] Transceiver 1113 can be used to support the reception or transmission of radio frequency signals between a communication device and a terminal. Transceiver 1113 can be connected to antenna 1115. Transceiver 1113 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1115 can receive radio frequency signals. The receiver Rx of transceiver 1113 is used to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to processor 1111 so that processor 1111 can perform further processing on the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in transceiver 1113 is also used to receive the modulated digital baseband signals or digital intermediate frequency signals from processor 1111, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1115. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of these downmixing and IF conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband signal or digital IF signal to obtain a radio frequency signal. The order of these upmixing and IF conversion processes is also adjustable. The digital baseband signal and the digital IF signal can be collectively referred to as digital signals.

[0586] The transceiver 1113 can also be called a transceiver unit, transceiver, transceiver device, etc. Optionally, the device in the transceiver unit that performs the receiving function can be regarded as the receiving unit, and the device in the transceiver unit that performs the transmitting function can be regarded as the transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be called a receiver, input port, receiving circuit, etc., and the transmitting unit can be called a transmitter, transmitter, or transmitting circuit, etc.

[0587] It should be noted that, Figure 11 The communication device 1100 shown can be used to implement the steps implemented by the network device in the aforementioned method embodiments, and to achieve the corresponding technical effects of the network device. Figure 11 The specific implementation of the communication device 1100 shown can be referred to the description in the foregoing method embodiments, and will not be repeated here.

[0588] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as a radio frequency module or antenna) in the terminal, information sent to the terminal by the base station; or, the terminal chip sends information to other modules (such as a radio frequency module or antenna) in the terminal, information sent to the base station by the terminal. For example, when the first device is a terminal, the terminal sending indication information can be understood as the process of the terminal's chip outputting indication information.

[0589] When the aforementioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above method embodiments. The base station module receives information from other modules (such as radio frequency modules or antennas) in the base station, information sent by the terminal to the base station; or, the base station module sends information to other modules (such as radio frequency modules or antennas) in the base station, information sent by the base station to the terminal. Here, the base station module can be the baseband chip of the base station, or a DU (Distributed Unit) or other modules. The DU can be a DU under an Open Radio Access Network (O-RAN) architecture. For example, when the first device is a base station, the base station sending indication information can be understood as the process of the base station's chip outputting indication information.

[0590] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0591] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0592] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method, characterized in that, The method is applied to a first computing node, and the method includes: Send first information to the first network element, wherein the first information is used to subscribe to the mobility events of the terminal device; Receive second information, the second information being used to instruct the device providing access service for the first computing service of the terminal device to switch from the first network device to the second network device; Send a third message, the third message being used to instruct the release of the first connection between the terminal device and the first computing node.

2. The method according to claim 1, characterized in that, The third information is also used to indicate that after the first connection is released, a new connection request to the first computing service should be initiated.

3. The method according to claim 1 or 2, characterized in that, The third piece of information is also used to instruct the clearing of DNS records on the terminal device.

4. The method according to any one of claims 1 to 3, characterized in that, The receiving of the second information includes: Receive the second information sent by the first network device or the second network device.

5. The method according to any one of claims 1 to 4, characterized in that, The receiving of the second information includes: Receive the second information sent by the first network element; The sending of the third information includes: The third information is sent to the first network element.

6. A communication method, characterized in that, The method is applied to a first network device, and the method includes: The first information sent by the second network element is received. The first information is used for the first computing node to subscribe to the mobility events of the terminal device. The first computing node has connected to the service instance of the first computing service. Send a second message to the second network element, the second message being used to instruct the terminal device to switch from the first network device to the second network device.

7. The method according to claim 6, characterized in that, Sending the second information to the second network element includes: When the second network device supports a service instance of the first computing service, it sends the second information to the second network element.

8. The method according to claim 6 or 7, characterized in that, The method further includes: The system receives a second indication message sent by a second network device, the second indication message being used to instruct the second network device to support a service instance of the first computing service.

9. The method according to any one of claims 6 to 8, characterized in that, The method further includes: Send a third request message to the second network device, the third request message being used to request the second network device to provide access service for the first computing service; The response information received from the third request information sent by the second network device is used to indicate acceptance of the request to switch the first computing service.

10. The method according to claim 9, characterized in that, The response information is also used to indicate the service instance identifier that the second network device is connecting to.

11. The method according to any one of claims 6 to 10, characterized in that, The method further includes: Based on the service requirements of the first computing service, it is determined that the second network device has a service instance of the first computing service that meets the service requirements.

12. The method according to any one of claims 1 to 11, characterized in that, The first information includes at least one of the following: first indication information, the identifier of the terminal device, the identifier of the first computing service, and the transmission request of the first computing service; the first indication information is used to indicate the mobility event.

13. The method according to any one of claims 1 to 12, characterized in that, The second information includes at least one of the following: first indication information, the identifier of the terminal device, and the identifier of the first computing service; the first indication information is used to indicate the mobility event.

14. A communication method, characterized in that, The method is applied to a second network device, and the method includes: The system receives a third request message sent by a first network device, the third request message being used to request the second network device to provide access service for the first computing service of the terminal device; A response message is sent to the first network device to indicate acceptance of the request to switch the first computing service.

15. The method according to claim 14, characterized in that, Sending response information to the first network device includes: If a service instance of the first computing service exists, the response information is sent to the first network device.

16. The method according to claim 14 or 15, characterized in that, The response information is also used to indicate whether the second network device supports a service instance of the first computing service.

17. The method according to any one of claims 14 to 16, characterized in that, The response information is also used to indicate the service instance identifier that the second network device is connecting to.

18. The method according to any one of claims 14 to 17, characterized in that, The method further includes: The terminal device receives a fourth message, which is used to request a first computing service or transmit user plane data of the first computing service. A fifth message is sent to the second computing node, the fifth message being used to instruct the second computing node to execute the first computing service.

19. The method according to any one of claims 14 to 18, characterized in that, The response information is also used to indicate at least one of the following: a second computing service in the first computing service supported by the second network device, and a third computing service in the first computing service not supported by the second network device.

20. The method according to any one of claims 14 to 19, characterized in that, The method further includes: The device receives a third indication message sent by the first network device. The third indication message is used to instruct the first computing node to send second information. The second information is used to instruct the device that provides access service for the first computing service of the terminal device to switch from the first network device to the second network device. Send the second information to the first computing node.

21. The method according to any one of claims 14 to 20, characterized in that, The third request information includes at least one of the following: the identifier of the first computing service, the transmission requirements of the first computing service, and the notification acceptance address information.

22. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: The third information sent by the second network element is received, and the third information is used to release the first connection between the terminal device and the first computing node; Send a fourth message to the second network device, the fourth message being used to identify the computing node associated with the terminal device.

23. The method according to claim 22, characterized in that, The method further includes: Release the first connection and / or re-initiate a connection request to the first computing service.

24. The method according to claim 22 or 23, characterized in that, The method further includes: Clean up the Domain Name System (DNS) records of the terminal device.

25. The method according to any one of claims 22 to 24, characterized in that, The second network element is the first computing node or gateway. The gateway is used to aggregate multiple first request information from multiple computing nodes. The multiple first request information are used to subscribe to the mobility events of the terminal device.

26. A communication device, characterized in that, It includes at least one processor coupled to at least one memory; the at least one processor is used to perform the method as described in any one of claims 1 to 25.

27. A chip or chip system, characterized in that, The chip or chip system is used to perform the method as described in any one of claims 1 to 25.

28. A communication system, characterized in that, It includes at least one of the following communication devices: a communication device for performing the method of any one of claims 1 to 5, 12 or 13; a communication device for performing the method of any one of claims 6 to 13; a communication device for performing the method of any one of claims 14 to 21; and a communication device for performing the method of any one of claims 22 to 25.

29. A readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 25.

30. A computer program product, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 25.

Images