Method and apparatus for service continuity

Abstract

The embodiment of the invention provides a method and a device for service continuity. A method performed by a first service enabler server includes receiving context information of a second service enabler server from the second service enabler server. The method further includes storing context information of the second service enabler server. The method further includes sending the endpoint information of the first service enabler server to the service enabler client and / or initiating a traffic impact process with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

Description

Technical Field

[0001] Non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and in particular to methods and apparatus for service continuity. Background Art

[0002] This section introduces various aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light, and should not be understood as an admission about what is or is not in the prior art.

[0003] Service continuity may be required for application relocation in various networks. The network may be required to minimize service interruption. Service continuity may rely on application layer support for seamless context / state relocation between application servers. Transport layer connection reestablishment may also cause service interruption. Therefore, real-time transport layer relocation may be supported between source and target application servers.

[0004] The 3rd Generation Partnership Project (3GPP) System Aspects (SA) Working Group 6 (SA6) has been working on vertical application enablement layers for many years and has developed some common application enablement layers, such as the edge application (EDGEAPP) in 3GPP TS 23.558 V17.4.0, the disclosure of which is incorporated herein by reference in its entirety, and the Service Enabler Architecture Layer (SEAL) for Verticals in 3GPP TS 23.434 V18.1.0, the disclosure of which is incorporated herein by reference in its entirety.

[0005] In 3GPP Release 18, SA6 is studying new vertical application enablers, such as Service Enabler Architecture Layer Data Delivery (SEALDD) in 3GPP TR 23.700-34 V0.6.0, the disclosure of which is incorporated herein by reference in its entirety, and Personal Internet of Things (IoT) Network Application (PINAPP) in 3GPP TR 23.700-78 V0.4.0, the disclosure of which is incorporated herein by reference in its entirety. Summary of the invention

[0006] This Summary is provided to introduce selected concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0007] The application enabler may be deployed in a network (e.g., an edge data network for edge computing). When the UE moves, the application server and / or its application enabler may need to be relocated. In the case of load rebalancing, the application server and / or application enabler may also be relocated.

[0008] Therefore, application service continuity is a topic in subsequent 3GPP technology research.

[0009] In 3GPP TR 23.700-34 V0.6.0, key issue #2 describes service continuity, which covers UE location change and server load rebalancing scenarios, as shown below.

[0010] 3GPP TS23.548V17.3.0 and 3GPP TS23.558V17.4.0 stipulate that service continuity is required for EAS relocation, and service continuity depends on the application layer's support for seamless context / state relocation between EAS servers. Transport layer connection reestablishment can also cause service interruption. Therefore, EAS IP replacement is also discussed in 3GPP TS23.548V17.3.0, assuming that real-time transport layer relocation is supported between the source EAS and the target EAS. However, for vertical / enterprises, real-time context / state relocation and transport layer real-time relocation are not always supported. In those cases where network support is unavailable, the application enablement layer can support this function for the application. The data transfer enabler service in the network can maintain a transport layer connection with the corresponding client in the UE. EAS can use this data transfer enabler service for EAS relocation (including context transfer and lossless packet transfer). This data transfer enabler can ensure service continuity for the UE, including seamless data transfer and enhanced transport layer management.

[0011] For example, two basic scenarios involving a data transfer enabler may be considered.

[0012] Figure 1a EAS relocation due to EAS load balancing according to an embodiment of the present disclosure is shown. Figure 1a Same as Figure 4.2-1 of 3GPP TR 23.700-34 V0.6.0.

[0013] In this scenario, the UPF and SEALDD server remain unchanged. The SEALDD server should support seamless EAS relocation to ensure UE service continuity. The SEALDD server can provide transport layer enhancement (i.e., transport layer packet processing to ensure that S-EAS and T-EAS can correctly receive / send packets without re-establishing transport layer connections).

[0014] Figure 1b EAS relocation due to UE position change according to an embodiment of the present disclosure is shown. Figure 1a Same as Figure 4.2-1 of 3GPP TR 23.700-34 V0.6.0.

[0015] In this case, the UPF and SEALDD server are changed. The SEALDD server can provide transport layer enhancements (i.e. lossless packet transfer and transport layer state coordination during the entire relocation process).

[0016] The following aspects may be studied to support SEALDD-enabled transport layer enhancements for UE continuity:

[0017] - How to support EAS relocation scenarios involving SEALDD servers (e.g., EAS relocation initiated by AF / AS for load balancing or EAS relocation initiated by 5GC due to UE location change).

[0018] -How does the SEALDD enabler provide support for seamless relocation and lossless data delivery?

[0019] In 3GPP TR 23.700-78 V0.4.0, key issue #5 describes service continuity, and there are some open issues related to this topic to be resolved, as shown below.

[0020] As indicated in 3GPP TS 22.261 clause 6.38, the following requirements describing service continuity will be studied in this TR phase and are reflected in this key issue:

[0021] - The 5G system should be able to minimize service disruption when a PIN element changes the communication path from one PIN element (e.g. a PIN element with gateway capabilities) to another PIN element or operator providing mobile access. The communication path between PIN elements may include licensed and unlicensed spectrum as well as 3GPP access and non-3GPP access.

[0022] PIN applications are applications deployed on a PIN element (e.g., UE) in the PIN. One of the features of PIN applications is that a PIN application in the UE can have direct communication with other PIN applications in the PIN without having any routing from the 5GS.

[0023] However, there are the following situations where there may be service interruption or relocation:

[0024] - When the UE moves out of the PIN or the terminal PIN application is in a mobile state, the original direct communication between the two PIN applications may be affected and changed (for example, the direct communication between the two PIN applications may be routed via PEGC);

[0025] - Normally, if a PIN application on the UE is using services from an application server, and due to the mobility of the UE, the PIN application on the UE should continue to receive services from the application server.

[0026] The following should be studied:

[0027] -How to support service continuity when the PIN application in the UE is in a mobile state?

[0028] - How to support service continuity and maintain communication with PIN applications when the UE moves out of PIN?

[0029] NOTE 1 Some of the service continuity work is related to SA2 work and depends on later feedback from SA2.

[0030] To overcome or mitigate at least one of the key issues discussed above or other issues, an improved solution for service continuity may be desired.

[0031] In a first aspect of the present disclosure, a method performed by a first service enabler server is provided. The method may include receiving context information of the second service enabler server from the second service enabler server. The method may also include storing the context information of the second service enabler server. The method may also include sending endpoint information of the first service enabler server to a service enabler client, and / or initiating a business impact procedure with a network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0032] In an embodiment, receiving the context information of the second service enabler server from the second service enabler server may include: sending a context pull request to the second service enabler server; and receiving a context pull response including the context information of the second service enabler server from the second service enabler server.

[0033] In an embodiment, receiving the context information of the second service enabler server from the second service enabler server may include: receiving a context push request including the context information of the second service enabler server from the second service enabler server, and sending a context push response to the second service enabler server.

[0034] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0035] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN).

[0036] In an embodiment, the context information of the second service enabler server may also include a transport layer context.

[0037] In an embodiment, the endpoint information of the service enabler server may include at least one of the following: a uniform resource identifier (URI), a fully qualified domain name (FQDN), an Internet Protocol (IP) address for user plane communication, or a port number for user plane communication.

[0038] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0039] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel including old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0040] In an embodiment, during relocation of a service enabler server with a user plane function (UPF) change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward the existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0041] In an embodiment, the method may further include sending a registration request including a profile of the first service enabler server to an edge enabler server (EES). The profile of the first service enabler server may include information indicating support for transport layer context transfer. The method may further include receiving a registration response from the EES.

[0042] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer.

[0043] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0044] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0045] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0046] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0047] In an embodiment, the first service enabler server is a new PIN server, the second service enabler server is a old PIN server, and the service enabler client is a PIN client.

[0048] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server, the second service enabler server is a legacy SEALDD server, and the service enabler client is a SEALDD client.

[0049] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server.

[0050] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0051] In a second aspect of the present disclosure, a method performed by a second service enabler server is provided. The method may include sending context information of the second service enabler server to the first service enabler server.

[0052] In an embodiment, sending the context information of the second service enabler server to the first service enabler server may include: receiving a context pull request from the first service enabler server, and sending a context pull response including the context information of the second service enabler server to the first service enabler server.

[0053] In an embodiment, sending the context information of the second service enabler server to the first service enabler server may include: sending a context push request including the context information of the second service enabler server to the first service enabler server, and receiving a context push response from the first service enabler server.

[0054] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0055] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN).

[0056] In an embodiment, the context information of the second service enabler server may also include a transport layer context.

[0057] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0058] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel including old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0059] In an embodiment, during relocation of a service enabler server with a UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0060] In an embodiment, the method may further include sending a registration request including a profile of the second service enabler server to the EES. The profile of the second service enabler server may include information indicating support for transport layer context transfer. The method may further include receiving a registration response from the EES.

[0061] In an embodiment, the method may further include sending a discovery request to the EES for discovering a service enabler server supporting transport layer context transfer. The method may further include receiving a registration response including information about the discovered service enabler server supporting transport layer context transfer from the EES.

[0062] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer.

[0063] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0064] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0065] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0066] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0067] In an embodiment, the first service enabler server is the new PIN server and the second service enabler server is the old PIN server.

[0068] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server and the second service enabler server is a legacy SEALDD server.

[0069] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server.

[0070] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0071] In an embodiment, the method may further include initiating a service impact procedure with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0072] In a third aspect of the present disclosure, a method performed by a service enabler client is provided. The method may include receiving endpoint information of the first service enabler server from the first service enabler server. Context information of the second service enabler server is received and stored in the first service enabler server.

[0073] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0074] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN).

[0075] In an embodiment, the context information of the second service enabler server may also include a transport layer context.

[0076] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0077] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel including old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0078] In an embodiment, during relocation of a service enabler server with a UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0079] In an embodiment, the method may further include sending a discovery request to the EES for discovering a service enabler server supporting transport layer context transfer. The method may further include receiving a registration response from the EES, the registration response including information about the discovered service enabler server supporting transport layer context transfer.

[0080] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer.

[0081] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0082] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0083] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0084] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0085] In an embodiment, the first service enabler server is the new PIN server and the second service enabler server is the old PIN server.

[0086] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server and the second service enabler server is a legacy SEALDD server.

[0087] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server.

[0088] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0089] In an embodiment, the endpoint information of the service enabler server may include at least one of the following: a uniform resource identifier (URI), a fully qualified domain name (FQDN), an Internet Protocol (IP) address for user plane communication, or a port number for user plane communication.

[0090] In a fourth aspect of the present disclosure, a first service enabler server is provided. The first service enabler server may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first service enabler server is operable to receive context information of the second service enabler server from the second service enabler server. The first service enabler server is also operable to store the context information of the second service enabler server. The first service enabler server is also operable to send endpoint information of the first service enabler server to a service enabler client, and / or initiate a business impact process with the network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0091] In a fifth aspect of the present disclosure, a second service enabler server is provided. The second service enabler server may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The second service enabler server is operable to send context information of the second service enabler server to the first service enabler server.

[0092] In a sixth aspect of the present disclosure, a service enabler client is provided. The service enabler client may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The service enabler client is operable to receive endpoint information of the first service enabler server from the first service enabler server. Context information of the second service enabler server is received and stored in the first service enabler server.

[0093] In a seventh aspect of the present disclosure, a first service enabler server is provided. The first service enabler server may include a first receiving module, which is configured to receive context information of the second service enabler server from the second service enabler server. The first service enabler server may also include a storage module, which is configured to store the context information of the second service enabler server. The first service enabler server may also include a first sending module and / or an initiating module, the first sending module is configured to send the endpoint information of the first service enabler server to the service enabler client, and the initiating module is configured to initiate a business impact process with the network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0094] In an embodiment, the first service enabler server may further include a second sending module configured to send a registration request including a profile of the first service enabler server to the edge enabler server (EES). The profile of the first service enabler server may include information indicating support for transport layer context transfer.

[0095] In an embodiment, the first service enabler server may further include a second receiving module configured to receive a registration response from the EES.

[0096] In an eighth aspect of the present disclosure, a second service enabler server is provided. The second service enabler server may include a first sending module configured to send context information of the second service enabler server to the first service enabler server.

[0097] In an embodiment, the second service enabler server may further include a second sending module configured to send a registration request including a profile of the second service enabler server to the EES. The profile of the second service enabler server may include information indicating support for transport layer context transfer.

[0098] In an embodiment, the second service enabler server may further include a first receiving module configured to receive a registration response from the EES.

[0099] In an embodiment, the second service enabler server may further include a third sending module configured to send a discovery request for discovering a service enabler server supporting transport layer context transfer to the EES.

[0100] In an embodiment, the second service enabler server may further include a second receiving module configured to receive a registration response including information about the discovered service enabler server supporting transport layer context transfer from the EES.

[0101] In an embodiment, the second service enabler server may further include an initiation module configured to initiate a service impact procedure with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0102] In a ninth aspect of the present disclosure, a service enabler client is provided. The service enabler client may include a first receiving module configured to receive endpoint information of the first service enabler server from the first service enabler server. Context information of the second service enabler server is received and stored in the first service enabler server.

[0103] In an embodiment, the service enabler client may further include a sending module configured to send a discovery request for discovering a service enabler server supporting transport layer context transfer to the EES.

[0104] In an embodiment, the service enabler client may further include a second receiving module configured to receive a registration response from the EES, the registration response including information about the discovered service enabler server supporting transport layer context transfer.

[0105] In another aspect of the present disclosure, a computer program product is provided, comprising instructions, which, when executed by at least one processor, cause the at least one processor to perform a method according to any one of the first aspect, the second aspect or the third aspect.

[0106] In another aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed by at least one processor, the instructions cause the at least one processor to perform a method according to any one of the first aspect, the second aspect or the third aspect.

[0107] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer includes a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a network node (e.g., the first service enabler server or the second service enabler server described above) and / or a terminal device (e.g., the service enabler client described above).

[0108] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the network node.

[0109] In an embodiment of the present disclosure, a processing circuit of a host computer is configured to execute a host application to provide user data; and a terminal device includes a processing circuit configured to execute a client application associated with the host application.

[0110] In another aspect of the present disclosure, a communication system is provided, which includes a host computer and a network node. The host computer includes a communication interface, which is configured to receive user data originating from a transmission from a terminal device. The transmission is from the terminal device to the network node. The terminal device is the above-mentioned service enabler client.

[0111] In an embodiment of the present disclosure, the processing circuit of the host computer is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0112] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host computer, a network node and a terminal device. The method may include providing user data at the host computer. Optionally, the method may include initiating a transmission carrying user data to the terminal device at the host computer via a cellular network including the network node.

[0113] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network may include a network node having a radio interface and processing circuitry.

[0114] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host computer, a network node and a terminal device. The method may include providing user data at the host computer. Optionally, the method may include initiating a transmission carrying user data to the terminal device via a cellular network including the network node at the host computer. The terminal device may perform any steps of the method according to the third aspect of the present disclosure.

[0115] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any step of the method according to the third aspect of the present disclosure.

[0116] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host computer, a network node and a terminal device. The method may include, at the host computer, receiving user data sent from the terminal device to the network node, the terminal device may perform any steps of the method according to the third aspect of the present disclosure.

[0117] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any step of the method according to the third aspect of the present disclosure.

[0118] In another aspect of the present disclosure, a method implemented in a communication system is provided, which may include a host computer, a network node, and a terminal device. The method may include, at the host computer, receiving from the network node user data originating from a transmission that the network node has received from the terminal device.

[0119] In another aspect of the present disclosure, a communication system is provided, which may include a host computer. The host computer may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The network node may include a radio interface and a processing circuit.

[0120] The embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments herein, the proposed solution may support EAS relocation scenarios involving SEALDD servers (e.g., EAS relocation initiated by AF / AS for load balancing or EAS relocation initiated by 5GC due to UE location changes). In some embodiments herein, the proposed solution may enable the SEALDD enabler to provide support for seamless relocation and lossless data delivery. In some embodiments herein, the proposed solution may support service continuity when the PIN application in the UE is in a mobile state. In some embodiments herein, the proposed solution may support service continuity and maintain communication with the PIN application when the UE moves out of the PIN. In some embodiments herein, the T-EAS discovery process is used to promote SEALDD layer service continuity. In some embodiments herein, the proposed solution may utilize the features defined in 3GPP SA2 for EAS IP replacement to support SEALDD-enabled transport layer state coordination for service continuity. The impact on EAS registration is identified to enable appropriate T-EAS discovery to support smooth transport service continuity. The embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0121] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, by way of example, in which like reference numerals or letters are used to refer to similar or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0122] Figure 1a illustrates EAS relocation due to EAS load balancing according to an embodiment of the present disclosure;

[0123] Figure 1b shows EAS relocation due to UE position change according to an embodiment of the present disclosure;

[0124] Figure 1c shows an architecture for a SEAL data delivery service according to an embodiment of the present disclosure;

[0125] Figure 1d An architecture for application service transfer according to an embodiment of the present disclosure is shown;

[0126] Figure 1e The architecture of a personal IoT network application enabling service according to an embodiment of the present disclosure is shown;

[0127] Figure 2a Schematically illustrates a high-level architecture in a fifth generation network according to an embodiment of the present disclosure;

[0128] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown;

[0129] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown;

[0130] Figure 3b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0131] Figure 4a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0132] Figure 4b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0133] Figure 4c A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0134] Figure 4d A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0135] Figure 5a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0136] Figure 5b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0137] Figure 6 illustrating a PINAPP architecture with PIN-enabled inter-server communication according to an embodiment of the present disclosure;

[0138] Figure 7a A flowchart of a PIN enabling layer context transfer according to an embodiment of the present disclosure is shown;

[0139] Figure 7b A flowchart of SEALDD context transfer according to an embodiment of the present disclosure is shown;

[0140] Figure 7c A flowchart of SEALDD context transfer according to another embodiment of the present disclosure is shown.

[0141] Figure 8a is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure;

[0142] Figure 8b is a block diagram illustrating a first service enabler server according to an embodiment of the present disclosure;

[0143] Figure 8c is a block diagram illustrating a second service enabler server according to an embodiment of the present disclosure;

[0144] Figure 8d is a block diagram illustrating a service enabler client according to another embodiment of the present disclosure;

[0145] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments;

[0146] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments;

[0147] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments;

[0148] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0149] Fig.13 is a schematic diagram illustrating a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0150] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0151] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0152] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments; and

[0153] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments. DETAILED DESCRIPTION

[0154] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus realize the present disclosure, rather than suggesting any limitation on the scope of the present disclosure. References to features, advantages or similar language throughout the specification do not mean that all features and advantages that can be implemented with the present disclosure should be in or in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages should be understood to mean that specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, in one or more embodiments, the features, advantages and characteristics described in the present disclosure may be combined in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, and the additional features and advantages may not exist in all embodiments of the present disclosure.

[0155] As used herein, the term "network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" may be used interchangeably. In addition, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to communication protocols defined by standard organizations such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols and / or any other protocol currently known or developed in the future.

[0156] The term "network node" or "network node" refers to any suitable network function (NF) that can be implemented in a (physical or virtual) network element of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform (e.g., on a cloud infrastructure). For example, a 5G system (5GS) may include multiple NFs, such as an access and mobility management function (AMF), a session management function (SMF), an authentication service function (AUSF), a unified data management (UDM), a policy control function (PCF), an application function (AF), a network open function (NEF), a user plane function (UPF) and a network repository function (NRF), a radio access network (RAN), a service communication agent (SCP), a network data analysis function (NWDAF), a network slice selection function (NSSF), a network slice specific authentication and authorization function (NSSAAF), etc. For example, a 4G system (e.g., LTE) may include a mobility management entity (MME), a home subscriber server (HSS), a PCRF (Policy and Charging Rules Function), a packet data network gateway (PGW), a PGW control plane (PGW-C), a serving gateway (SGW), a SGW control plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, the network functions may include different types of NFs, e.g., depending on the specific network.

[0157] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), etc. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate in accordance with one or more communication standards (e.g., 3GPP's LTE standard or NR standard) issued by 3GPP (3rd Generation Partnership Project). As used herein, a "user equipment" or "UE" may not necessarily have a "user" in terms of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Alternatively, a UE may represent a device that is intended to be sold to a human user or operated by a human user but may not initially be associated with a specific human user.

[0158] As another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement, and sends the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machinery, or household or personal appliances, such as refrigerators, televisions, personal wearable devices (e.g., watches), etc. In other scenarios, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0159] References in the specification to "one embodiment," "an embodiment," "an exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is claimed that it is within the knowledge of those skilled in the art to affect that feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0160] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiments, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more associated listed terms.

[0161] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean any of "only A, only B, or both A and B". The phrase "A and / or B" should be understood to mean any of "only A, only B, or both A and B".

[0162] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the example embodiments. Unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" as used herein are also intended to include the plural forms. It will be further understood that when used herein, the terms "include", "comprise", "have", "have", "contain" and / or "cover" specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0163] Note that these terms used in this article are only used to facilitate description and to distinguish between nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.

[0164] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0165] Figure 1c An architecture for a SEAL data delivery service according to an embodiment of the present disclosure is shown. Figure 1c With 3GPPTR 23.700-34V0.6.0 Figure 6.1.1-4 are the same.

[0166] SEALDD is a part of the SEAL enabler and it provides data delivery (DD) services to the vertical application layer (VAL).

[0167] For uplink traffic, the VAL client sends application data traffic to the SEALDD client for SEALDD service via SEALDD-C. After the SEALDD client processes the data plane packets, the application data traffic is converted to SEALDD data traffic and transferred to the SEALDD server via SEALDD-UU. The SEALDD server recovers the application data traffic and sends it to the VAL server via SEALDD-S. For downlink traffic, the VAL server sends application data traffic to the SEALDD server for SEALDD service via SEALDD-S. After the SEALDD server processes the data plane packets, the application data traffic is converted to SEALDD data traffic and transferred to the SEALDD client via SEALDD-UU. The SEALDD client recovers the application data traffic and sends it to the VAL client via SEALDD-C. Optionally, a VAL deployment may choose to use the SEALDD service to route application signaling traffic and application data traffic for some or all of the functions it provides. Figure 1d An architecture for achieving this is described. In this case, the VAL Client and VAL Server may choose not to maintain the application connection themselves, but instead transfer all application traffic for those functions over the SEALDD connection.

[0168] Figure 1d An architecture for application service migration according to an embodiment of the present disclosure is shown. Figure 1d With 3GPP TR23.700-34 V0.6.0 Figure 6 .1.1-5 are the same.

[0169] The SEAL data delivery client interacts with the SEAL data delivery server to establish an application layer data transmission path.

[0170] Through this path, SEALDD servers and clients provide data transmission service capabilities, such as data plane packet processing (e.g., packet replication, elimination, or transmission coordination), data forwarding, data caching, background data transfer, etc., to support VAL servers and clients.

[0171] Figure 1e The architecture for personal IoT network application enabling services according to an embodiment of the present disclosure is shown. Figure 1e Same as Figure 7.2.1-1 of 3GPP TR 23.700-78 V0.4.0.

[0172] The UE or Personal IoT (PIN) element has a PIN client. The UE or PIN element with gateway capability (PEGC) performs the role of an entity supporting gateway capability for the PIN. The PEGC provides gateway functions for the PIN element. The UE or PIN element with management capability (PEMC) performs the role of an entity supporting management capabilities for the PIN. The PEMC provides management functions for the PIN element.

[0173] Interaction between PEMC and PIN clients is supported via PIN-3. Interaction between PEMC and PEGC is supported via PIN-4. Interaction between PEGC and PIN clients is supported via PIN-2. Interaction between PIN clients from different UEs or PIN elements is supported via PIN-5.

[0174] Although the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to systems that conform to Figure 2a-2b For simplicity, the communication system of the exemplary system architecture shown is described. Figure 2a-2b The system architecture of only depicts some exemplary elements. In practice, the communication system may further include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices to access and / or use services provided by or via the communication system.

[0175] Figure 2a The high-level architecture in the fifth generation network according to an embodiment of the present disclosure is schematically shown. For example, the fifth generation network may be 5GS. Figure 2a The architecture of is the same as Figure 4.2.3-2 described in 3GPP TS 23.501 V17.2.0, the disclosure of which is incorporated herein by reference in its entirety. Figure 2a The system architecture may include some exemplary elements, such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (service communication agent), NSSAAF (network slice specific authentication and authorization function), NSACF (network slice admission control function), etc.

[0176] According to an exemplary embodiment, Figure 2aAs shown in , the UE can establish a signaling connection with the AMF through reference point N1. The signaling connection enables NAS (non-access stratum) signaling exchange between the UE and the core network, including a signaling connection between the UE and the (R)AN and an N2 connection between the (R)AN and the AMF for the UE. The (R)AN can communicate with the UPF through reference point N3. The UE establishes a protocol data unit (PDU) session to the DN (data network, such as an operator network or the Internet) through the UPF through reference point N6.

[0177] like Figure 2a As further shown in FIG. 1 , the exemplary system architecture also includes some reference points, such as N1, N2, N3, N4, N6, N9 and N15, which can support the interaction between NF services in NF. For example, these reference points can be implemented through corresponding NF service-based interfaces and by specifying some NF service consumers and providers and their interactions in order to perform specific system processes. The PCF provides the AM-related policies for the registered UE to the AMF via the N15 interface. The AMF can obtain the AM policy during the AM policy association establishment / modification process.

[0178] Figure 2a The various NFs shown in the figure may be responsible for functions such as session management, mobility management, authentication, security, etc. AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF may include, for example, the functions defined in clause 6.2 of 3GPP TS23.501 V17.2.0.

[0179] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown, which is the same as FIG. 4.2-1a of 3GPP TS23.682 V17.2.0, the disclosure of which is incorporated herein by reference in its entirety. Figure 2bThe system architecture may include some exemplary elements, such as service capability server (SCS), application server (AS), SCEF (service capability exposure function), HSS, UE, RAN (radio access network), SGSN (serving GPRS (general packet radio service) support node), MME, MSC (mobile switching center), S-GW (serving gateway), GGSN / P-GW (gateway GPRS support node / PDN (packet data network) gateway), MTC-IWF (machine type communication-interworking function), CDF / CGF (charging data function / charging gateway function), MTC-AAA (machine type communication-authentication, authorization and charging), SMS-SC / GMSC / IWMSC (short message service-service center / gateway MSC / interworking MSC), IP-SM-GW (Internet Protocol Short Message Gateway). Figure 2b The network elements and interfaces shown in may be the same as the corresponding network elements and interfaces described in 3GPP TS 23.682 V17.2.0.

[0180] The system architecture shows an architecture in which a UE for MTC is connected to a 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network), etc.) via a Um / Uu / LTE-Uu interface. The system architecture also shows the opening of 3GPP network service capabilities to SCS and AS.

[0181] like Figure 2b As further shown in , the exemplary system architecture also includes various reference points.

[0182] Tsms: A reference point used by entities outside the 3GPP network to communicate with UEs for MTC via SMS (Short Message Service).

[0183] Tsp: Reference point used by the SCS to communicate with the MTC-IWF related control plane signaling.

[0184] T4: Reference point used between MTC-IWF and SMS-SC in HPLMN.

[0185] T6a: Reference point used between SCEF and serving MME.

[0186] T6b: Reference point used between SCEF and serving SGSN.

[0187] T8: Reference point used between SCEF and SCS / AS.

[0188] S6m: Reference point used by the MTC-IWF to query the HSS / HLR (Home Location Register).

[0189] S6n: Reference point used by MTC-AAA to query HSS / HLR.

[0190] S6t: Reference point used between SCEF and HSS.

[0191] SGs: Reference point used between MSC and MME.

[0192] Gi / SGi: Reference point used between GGSN / P-GW and application server and between GGSN / P-GW and SCS.

[0193] Rf / Ga: Reference point used between MTC-IWF and CDF / CGF.

[0194] Gd: Reference point used between SMS-SC / GMSC / IWMSC and SGSN.

[0195] SGd: Reference point used between SMS-SC / GMSC / IWMSC and MME.

[0196] E: Reference point used between SMS-SC / GMSC / IWMSC and MSC.

[0197] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by a device implemented in a first service enabler server, or a device implemented at a first service enabler server, or a device implemented as a first service enabler server, or a device communicatively coupled to a first service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 300, and components or modules for implementing other processes in combination with other components.

[0198] At block 302, a first service enabler server may receive context information of the second service enabler server from the second service enabler server.

[0199] The service enabler server may be any suitable network node. The service enabler server may provide any suitable function. For example, the service enabler server may forward / switch / relay application data services between the terminal device and the application service. The service enabler server may act as a server for data transfer enablement. The service enabler server may provide configuration information to the UE. The service enabler server may provide authorization functions.

[0200] The service enabler server may be relocated due to various reasons, such as UE mobility or load rebalancing or maintenance aspects (such as normal shutdown of the service enabler server). In this case, the first service enabler server can receive context information of the second service enabler server from the second service enabler server.

[0201] For example, there are the following situations that may have service interruptions or relocations:

[0202] - When the UE moves out of the PIN or the terminal PIN application is in a mobile state, the original direct communication between the two PIN applications may be affected and changed (for example, the direct communication between the two PIN applications may be routed via PEGC);

[0203] - Typically, if a PIN application on the UE is using services from an application server and due to UE mobility, the PIN application on the UE should continue to receive services from the application server.

[0204] The first service enabler server may receive the context information of the second service enabler server from the second service enabler server in a variety of ways such as pulling or pushing.

[0205] In an embodiment, the first service enabler server may send a context pull request to the second service enabler server, and receive a context pull response including context information of the second service enabler server from the second service enabler server.

[0206] In an embodiment, the first service enabler server may receive a context push request including context information of the second service enabler server from the second service enabler server, and send a context push response to the second service enabler server.

[0207] The context information of the second service enabler server may include any suitable information, such as context information related to the service enabler client, context information related to the application server, and context information related to the transport layer.

[0208] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0209] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN). For example, the profile of the PIN may be the same as the PIN profile described in clause 7.7 of 3GPP TR 23.700-78 V0.4.0. Table 1 shows an example of a PIN profile, which is the same as Table 7.7.2.2.1-1 of 3GPP TR 23.700-78 V0.4.0.

[0210] Table 1: PIN profiles in PIN server, PEMC, PEGC and PINE

[0211] Table 2 shows an example of dynamic profile information of a PIN, which is the same as Table 7.7.2.3-1 of 3GPP TR 23.700-78 V0.4.0.

[0212] Table 2: Dynamic profile information for PIN

[0213] In an embodiment, the context information of the second service enabler server may also include a transport layer context. In this case, the first service enabler server may initiate a service impact procedure with the network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0214] In an embodiment, when there are multiple service enabler clients served by a second service enabler server, due to various reasons such as UE mobility or load rebalancing or maintenance, the service of at least one of the multiple service enabler clients can be transferred from the second service enabler server to the first service enabler server, and the received context information of the second service enabler server can be related to the affected service enabler client.

[0215] The first service enabler server may store context information of the second service enabler server at block 304. The context information of the second service enabler server may be used by the first service enabler server when an application server and / or a service enabler client interacts with the first service enabler server.

[0216] At block 306 , the first service enabler server may send the endpoint information of the first service enabler server to the service enabler client and / or initiate a service impact procedure with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0217] The endpoint information of the first service enabler server may include any suitable information that the service enabler client may use to contact the first service enabler server.

[0218] In an embodiment, the endpoint information of the service enabler server may include at least one of the following: a uniform resource identifier (URI), a fully qualified domain name (FQDN), an Internet Protocol (IP) address for user plane communication, or a port number for user plane communication.

[0219] In an embodiment, when there are multiple service enabler clients served by a second service enabler server, due to various reasons (such as UE mobility or load rebalancing or maintenance aspects), the service of at least one service enabler client among the multiple service enabler clients can be transferred from the second service enabler server to the first service enabler server, and the first service enabler server can send endpoint information of the first service enabler server to each of the affected service enabler clients.

[0220] The traffic impact procedure may be any suitable traffic impact procedure.In an embodiment, the traffic impact procedure may be the following enhancement to AF impact as described in clause 6.3.3.2 of 3GPP TS 23.548 V17.3.0 (the disclosure of which is incorporated herein by reference in its entirety).

[0221] Enhanced impact on AF

[0222] AF can also include one or more source and target EAS IP addresses and one or more port numbers in Nnef_TrafficInfluence_Create / Update or Nnef_TrafficInfluence_AppRelocationInfo or Nsmf_EventExposure_AppRelocationInfo requests. Based on one or more source EAS IP addresses and one or more port numbers, SMF knows which service flows need EAS IP replacement.

[0223] Using the early / late notification procedure, SMF can notify AF of the ability to support EAS IP replacement in 5GC, and when EAS relocation is completed, AF sends an early / late notification response to SMF. SMF sends "External Header Creation" and "External Header Removal" FARs to the (target) local PSA UPF, and the (target) local PSA UPF starts EAS IP address replacement as described in clause 6.3.3.1.

[0224] For load balancing purposes, the AF may move certain UEs from the old target EAS to a new target EAS in the same L-DN identified by the DNAI. For abnormal situations of EAS, the AF may move all UEs served by the source EAS to the target EAS in the same L-DN. For these purposes, the AF needs to include a list of UEs, the source / old target EAS IP addresses and port numbers for the affected DNAIs, and the (new) target EAS IP addresses and port numbers for the affected DNAIs in the Nnef_TrafficInfluence_Create / Update request. If the 5GC does not support the EAS IP replacement capability, the SMF shall reject this AF request.

[0225] Additional parameters for enabling EAS IP replacement are defined in clause 5.6.7.1 of 3GPP TS 23.501, clauses 4.3.6.3 and 4.3.6.4 of 3GPP TS 23.502.

[0226] In an embodiment, the first service enabler server is a new PIN server, the second service enabler server is a old PIN server, and the service enabler client is a PIN client.

[0227] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server, the second service enabler server is a legacy SEALDD server, and the service enabler client is a SEALDD client.

[0228] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0229] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel including old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0230] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer. In this case, the first service enabler server and / or the second service enabler server may initiate a service impact procedure with the network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0231] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0232] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0233] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0234] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0235] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server, and

[0236] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0237] In an embodiment, during relocation of a service enabler server with a user plane function (UPF) change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward the existing incomplete application traffic flows, while new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0238] Figure 3b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first service enabler server, or a device implemented at a first service enabler server, or a device implemented as a first service enabler server, or a device communicatively coupled to a first service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 310, and components or modules for implementing other processes in combination with other components.

[0239] At block 312, the first service enabler server may send a registration request including a profile of the first service enabler server to an edge enabler server (EES). The profile of the first service enabler server may include information indicating support for transport layer context transfer. The EES may be the same as the EES described in 3GPP TS23.558 V17.4.0.

[0240] At block 314, the first service enabler server may receive a registration response from the EES.

[0241] For example, the registration request may be an edge application server (EAS) registration request, and the registration response may be an EAS registration response, as described in 3GPP TS 23.558 V17.4.0.

[0242] For example, the first service enabler server determines that it needs to register with EES (e.g., the first service enabler server is instantiated and started). The first service enabler server sends an EAS registration request to EES. The request should include the first service enabler server profile and may include the proposed expiration time for the registration. EES performs an authorization check to verify whether the first service enabler server has authorization to register on EES. After successful authorization, EES stores the first service enabler server profile for later use and replies to the first service enabler server with an EAS registration response. EES can provide an expiration time to indicate to the first service enabler server when the registration will automatically expire. In order to maintain the registration, the first service enabler server should send a registration update request before the expiration time. If the registration update request is not received before the expiration time, EES should treat the first service enabler server as implicitly unregistered.

[0243] Figure 4a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second service enabler server, or a device implemented at a second service enabler server, or a device implemented as a second service enabler server, or a device communicatively coupled to a second service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 400, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0244] At block 402, the second service enabler server may send context information of the second service enabler server to the first service enabler server.

[0245] The service enabler server may be relocated due to various reasons, such as UE mobility or load rebalancing or maintenance aspects (such as normal shutdown of the service enabler server). In this case, the second service enabler server can send context information of the second service enabler server to the first service enabler server.

[0246] The second service enabler server may send the context information of the second service enabler server to the first service enabler server in various ways (eg, pull or push).

[0247] In an embodiment, the second service enabler server may receive a context pull request from the first service enabler server and send a context pull response including context information of the second service enabler server to the first service enabler server.

[0248] In an embodiment, the second service enabler server may send a context push request including context information of the second service enabler server to the first service enabler server, and receive a context push response from the first service enabler server.

[0249] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0250] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN).

[0251] In an embodiment, the context information of the second service enabler server may also include a transport layer context.

[0250] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0252] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel containing old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0254] In an embodiment, during relocation of a service enabler server with a UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0255] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer.

[0256] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0257] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0258] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0259] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0260] In an embodiment, the first service enabler server is the new PIN server and the second service enabler server is the old PIN server.

[0261] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server and the second service enabler server is a legacy SEALDD server.

[0262] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server.

[0263] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0264] Figure 4b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second service enabler server, or a device implemented at a second service enabler server, or a device implemented as a second service enabler server, or a device communicatively coupled to a second service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 410, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0265] At block 412, the second service enabler server may send a registration request including a profile of the second service enabler server to the EES. The profile of the second service enabler server may include information indicating support for transport layer context transfer. The EES may be the same as the EES described in 3GPP TS23.558 V17.4.0.

[0266] At block 414, the second service enabler server may receive a registration response from the EES.

[0267] For example, the registration request may be an EAS registration request, and the registration response may be an EAS registration response, as described in 3GPP TS 23.558 V17.4.0.

[0268] For example, the second service enabler server determines that it needs to register with EES (e.g., the second service enabler server is instantiated and started). The second service enabler server sends an EAS registration request to EES. The request should include the second service enabler server profile and may include a suggested expiration time for the registration. EES performs an authorization check to verify whether the second service enabler server has authorization to register on EES. After successful authorization, EES stores the second service enabler server profile for later use and replies to the second service enabler server with an EAS registration response. EES can provide an expiration time to indicate to the second service enabler server when the registration will automatically expire. In order to maintain the registration, the second service enabler server should send a registration update request before the expiration time. If the registration update request is not received before the expiration time, EES should treat the second service enabler server as implicitly unregistered.

[0269] Figure 4c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second service enabler server, or a device implemented at a second service enabler server, or a device implemented as a second service enabler server, or a device communicatively coupled to a second service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 420, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0270] At block 422, the second service enabler server may send a discovery request to the EES to discover a service enabler server that supports transport layer context transfer.

[0271] At block 424, the second service enabler server may receive a registration response from the EES, the registration response including information about the discovered service enabler servers that support transport layer context transfer.

[0272] For example, the discovery request may be an EAS discovery request, and the discovery response may be an EAS discovery response, as described in 3GPP TS 23.558 V17.4.0.

[0273] For example, the second service enabler server sends an EAS discovery request to the EES. The EAS discovery request includes a requestor identifier and security credentials, and may include a service enabler server discovery filter, and may also include a UE location to retrieve information about one or more specific service enabler servers or a class of service enabler servers, such as gaming applications, or retrieve information about one or more service enabler servers available in certain service areas (e.g., available on the predicted or expected route of the UE). After receiving the request from the second service enabler server, the EES checks whether the second service enabler server is authorized to discover the requested one or more service enabler servers. The authorization check can be applied to a single service enabler server, a class of service enabler servers, or to the EDN, i.e., to all service enabler servers. If the location information of the UE is not yet available, the EES obtains the UE location by utilizing the capabilities of the 3GPP core network. If the second service enabler server provides a service enabler server discovery filter, the EES identifies one or more service enabler servers based on the provided service enabler server discovery filter and the UE location. If processing of the request is successful, the EES will send an EAS discovery response to the second service enabler server, which includes information about the discovered service enabler server. For the discovered service enabler server, this includes endpoint information. Depending on the service enabler server discovery filter received in the EAS discovery request, the response may include additional information about the matching capabilities, such as service authority level, KPI (key performance indicators), one or more AC locations that the service enabler server can support, etc. The EAS discovery response may include a list of service enabler servers. The list may be based on a service enabler server discovery filter that includes the geographic or topological service area (e.g., route) included by the second service enabler server in the EAS discovery request.

[0274] Figure 4d A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second service enabler server, or a device implemented at a second service enabler server, or a device implemented as a second service enabler server, or a device communicatively coupled to a second service enabler server. Therefore, the device can provide components or modules for implementing various parts of method 430, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0275] At block 432, the second service enabler server may initiate a service impact process with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0276] The service impact procedure may be any suitable service impact procedure.In an embodiment, the service impact procedure may be an enhancement to the AF impact as described in clause 6.3.3.2 of 3GPP TS 23.548 V17.3.0.

[0277] The first enabler server or the second service enabler server may initiate the business impact process.Which service enabler server initiates the business impact process may be predefined or may be negotiated between the first service enabler server and the second service enabler server.

[0278] Figure 5a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a service enabler client, or a device implemented at a service enabler client, or a device implemented as a service enabler client, or a device communicatively coupled to a service enabler client. Therefore, the device can provide components or modules for implementing various parts of method 500, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0279] At block 502, a service enabler client may receive endpoint information of a first service enabler server from a first service enabler server. Context information of a second service enabler server is received and stored in the first service enabler server.

[0280] The service enabler server may be relocated due to various reasons, such as UE mobility or load rebalancing or maintenance aspects (such as normal shutdown of the service enabler server). In this case, the service enabler client can receive endpoint information of the first service enabler server from the first service enabler server.

[0281] For example, as described above, the first service enabler server may receive context information of the second service enabler server from the second service enabler server and store it in the first service enabler server.

[0282] In an embodiment, the context information of the second service enabler server may include at least one of the following: service subscription information created during the interaction of the application server for requesting the data transmission service of the second service enabler server, service enabler client communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server, or service enabler server communication tunnel management information created during the interaction of the service enabler client for requesting the data transmission service of the second service enabler server.

[0283] In an embodiment, the context information of the second service enabler server may include a profile of a personal Internet of Things (IoT) network (PIN).

[0284] In an embodiment, the context information of the second service enabler server may also include a transport layer context.

[0285] In an embodiment, if the service enabler server is adapted for edge applications (EDGEAPP) as an edge application server (EAS), the EAS relocation procedure may be used to support service enabler server relocation for both user equipment (UE) mobility and service enabler server load rebalancing.

[0286] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for UE mobility, the service enabler client discovers the first service enabler server, and the service enabler client establishes a new communication channel including old communication channel information, and for service enabler server load rebalancing, the second service enabler server discovers the first service enabler server.

[0287] In an embodiment, during relocation of a service enabler server with a UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward the existing incomplete application traffic flows, while new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

[0288] In an embodiment, the first service enabler server and / or the second service enabler server supports transport layer context transfer.

[0289] In an embodiment, if the PIN application server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support PIN AS relocation.

[0290] In an embodiment, if the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

[0291] In an embodiment, if the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure may be used to support service enabler server relocation for both PIN element (PINE) mobility and service enabler server load rebalancing.

[0292] In an embodiment, if the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

[0293] In an embodiment, the first service enabler server is the new PIN server and the second service enabler server is the old PIN server.

[0294] In an embodiment, the first service enabler server is a new Service Enabler Architecture Layer Data Delivery (SEALDD) server and the second service enabler server is a legacy SEALDD server.

[0295] In an embodiment, the old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server.

[0296] In an embodiment, a new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

[0297] In an embodiment, the endpoint information of the service enabler server may include at least one of the following: a uniform resource identifier (URI), a fully qualified domain name (FQDN), an Internet Protocol (IP) address for user plane communication, or a port number for user plane communication.

[0298] Figure 5b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a service enabler client, or a device implemented at a service enabler client, or a device implemented as a service enabler client, or a device communicatively coupled to a service enabler client. Therefore, the device can provide components or modules for implementing various parts of method 510, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0299] At block 512, the service enabler client may send a discovery request to the EES to discover a service enabler server that supports transport layer context transfer.

[0300] At block 514, the service enabler client may receive a registration response from the EES, the registration response including information about the discovered service enabler servers that support transport layer context transfer.

[0301] For example, the discovery request may be an EAS discovery request, and the discovery response may be an EAS discovery response, as described in 3GPP TS 23.558 V17.4.0.

[0302] For example, a service enabler client sends an EAS discovery request to EES. The EAS discovery request includes a requestor identifier and security credentials, and may include a service enabler server discovery filter, and may also include a UE location to retrieve information about one or more specific service enabler servers or a class of service enabler servers, such as gaming applications, or retrieve information about one or more service enabler servers available in certain service areas (e.g., available on the predicted or expected route of the UE). After receiving the request from the service enabler client, EES checks whether the service enabler client is authorized to discover the requested one or more service enabler servers. The authorization check can be applied to a single service enabler server, a class of service enabler servers, or EDN, i.e., all service enabler servers. If the UE's location information is not yet available, EES obtains the UE location by utilizing the capabilities of the 3GPP core network. If the service enabler client provides a service enabler server discovery filter, EES identifies one or more service enabler servers based on the provided service enabler server discovery filter and the UE location. If processing of the request is successful, the EES sends an EAS discovery response to the service enabler client, which includes information about the discovered service enabler servers. For the discovered service enabler servers, this includes endpoint information. Depending on the service enabler server discovery filter received in the EAS discovery request, the response may include additional information about the matching capabilities, such as service authority level, KPI (key performance indicators), one or more AC locations that the service enabler server can support, etc. The EAS discovery response may include a list of service enabler servers. The list may be based on a service enabler server discovery filter that includes the geographic or topological service area (e.g., route) of the second service enabler server included in the EAS discovery request.

[0303] Figure 6 A PINAPP architecture with PIN enabler-server communication according to an embodiment of the present disclosure is shown.

[0304] The architectural assumptions of 3GPP TR 23.700-78 V0.4.0 clause 7.2 are also assumed in this solution. In addition, a new PIN-11 reference point is added between PIN servers (enablers) in the data network, which supports PIN enablement layer context transfer during service continuity.

[0305] Figure 7aA flowchart of a PIN enabling layer context transfer according to an embodiment of the present disclosure is shown.

[0306] For example, in a PIN enablement server relocation, a PIN enablement layer context transfer may occur.

[0307] PINE is outside the PIN coverage area

[0308] When a PINE communicates with another PINE in the same PIN, and either PINE moves out of the PIN coverage (e.g., outside the WiFi coverage), the user plane traffic routing is switched from PINE-PINE to PINE-RAN-UPF-RAN-PINE.

[0309] Note: A PINE may have an internal IP address assigned by a PIN (e.g., a LAN gateway). For a PINE outside a PIN to communicate with another PINE inside a PIN, NAT traversal is outside the scope of this study.

[0310] PIN Enabler Server Relocation and PIN AS Relocation

[0311] When a PINE moves, if the currently used PIN AS (application server) can still provide services for the PIN application clients in the PINE, no service continuity process is triggered.

[0312] If a PIN AS (eg, deployed in an EDN and having service area restrictions) can no longer provide services for PIN application clients, the PIN AS needs to be relocated.

[0313] If the PIN AS is suitable for EDGE APP as EAS, the EAS relocation procedure can be used to support PIN AS relocation. If the PIN AS is not suitable for EDGE APP, the PIN application client can discover (e.g. using DNS (Domain Name System)) a new PIN AS in the target area and start communicating with the new PIN AS. PIN AS specific context transfer is outside the scope of 3GPP.

[0314] Similarly, a PIN-enabled server may be adapted for EDGE APP and its relocation may be triggered due to PINE mobility or PIN-enabled server load rebalancing. DNS may also be used to discover new PIN-enabled servers.

[0315] For PIN to enable specific context transfer, such as Figure 6 As depicted in , one of a pull or a push operation may be used via the PIN-11 reference point. One of a pull (steps 1a and 2a) or a push (steps 1b and 2b) operation may be used.

[0316] For the pull operation, in step 1a, the new PIN server sends a PIN enabler context pull request to the old PIN server. In step 2a, the old PIN server sends a PIN enabler context pull response including the old PIN enabler context to the new PIN server.

[0317] For the push operation, in step 1b, the old PIN server sends a PIN enabler context push request including the old PIN enabler context to the new PIN server. In step 2b, the new PIN server sends a PIN enabler context push response to the old PIN server.

[0318] The transferred PIN enabler context may include a PIN profile as described in Solution #6 of 3GPP TR 23.700-78 V0.4.0.

[0319] In step 3, the new PIN enabling server, after receiving the context from the old PIN enabling server, updates the PIN enabling client with the new PIN server endpoint so that the PIN enabling client knows where to contact for subsequent interactions with the PIN enabling server.

[0320] In step 4, the PIN enables the client to confirm the received notification.

[0321] NOTE: PIN enabled clients are subscribed to receive notifications of updates in the PIN.

[0322] This solution can solve the key issue #5 service continuity of 3GPP TR 23.700-78V0.4.0.

[0323] For PINEs outside of PIN coverage, the mechanisms specified by 3GPP SA2 for user plane routing may be used.When the PINE IP (Internet Protocol) address changes, it is up to the application to maintain service continuity.

[0324] For PIN server (enabler) relocation and PIN AS relocation, the EDGEAPP mechanism can be used to facilitate the discovery process. In addition, specific procedures for PIN enabler context transfer between PIN servers (enablers) over the PIN-11 reference point are used to maintain service continuity in the PIN enabling layer.

[0325] Figure 7b A flowchart of SEALDD context transfer according to an embodiment of the present disclosure is shown.

[0326] For example, in a SEALDD server relocation, a SEALDD context transfer may occur.

[0327] As described in 3GPP TR 23.700-34 V0.6.0 clause 4.2, a SEALDD server may be relocated due to UE mobility or load rebalancing. 3GPP TR 23.700-34 V0.6.0 clause 4.7 also discusses open issues regarding SEALDD server discovery and selection in case of SEALDD server change.

[0328] If the SEALDD server is suitable for EDGEAPP as EAS, the EAS relocation process can be used to support the SEALDD server relocation for both UE mobility and SEALDD server load rebalancing. If SEALDD is not suitable for EDGEAPP, for UE mobility, the SEALDD client can discover (e.g., using DNS) a new SEALDD server in the target area and establish a new SEALDD communication channel including the old SEALDD communication channel information. For load rebalancing, the SEALDD server can discover (e.g., using DNS) an equivalent SEALDD server and communicate with the new SEALDD server.

[0329] During SEALDD server relocation with UPF change, the new UPF handles the existing unfinished application traffic flow towards the old VAL server, and the inter-UPF tunnel is used to forward the traffic. For new application traffic flows that can have the new IP address of the UE as the source IP address, the new SEALDD server sends it directly to the new VAL server.

[0330] For SEALDD server relocation, inter-SEALDD server communication via SEALDD-E reference point is required, which transfers the SEALDD context from the old SEALDD server to the new SEALDD server. The following figure describes the SEALDD context transfer process in a pull (steps 1a and 2a) or push (steps 1b and 2b) operation.

[0331] For the pull operation, in step 1a, the new SEALDD server sends a SEALDD context pull request to the old SEALDD server. In step 2a, the old SEALDD server sends a SEALDD context pull response containing the old SEALDD context to the new SEALDD server.

[0332] For the push operation, in step 1b, the old SEALDD server sends a SEALDD context push request including the old SEALDD context to the new SEALDD server. In step 2b, the new SEALDD sends a SEALDD context push response to the old SEALDD server.

[0333] The transferred SEALDD context includes the service subscription information created when the VAL server interacts to request the SEALDD delivery service, and also includes the SEALDD client and SEALDD server communication tunnel management information (e.g., UE IP address) created when the SEALDD client interacts to request data delivery (e.g., 3GPP TR 23.700-34 V0.6.0 Figure 6 .9.2.2-1, steps 5 and 6).

[0334] In step 3, after receiving the SEALDD context from the old SEALDD server, the new SEALDD server may update the connection information, such as updating the allocated IP address and port for SEALDD-Uu communication.

[0335] In step 4, the SEALDD client confirms the received SEALDD connection information update notification.

[0336] Note: The SEALDD client has subscribed to receive connection information update notifications in the SEALDD connection establishment request.

[0337] Figure 7c A flowchart of SEALDD context transfer according to another embodiment of the present disclosure is shown.

[0338] There is an EAS IP replacement feature defined in 3GPP TS 23.548 V17.3.0 that allows the AF to perform server changes (e.g. due to load rebalancing) without affecting the UE (i.e. the UE is not aware of the EAS change). Figure 7c In, with Figure 7b The difference is:

[0339] - In steps 1 and 2, the additional transport layer context is transferred from the old SEALDD server to the new SEALDD server; and

[0340] - Instead of informing the SEALDD client of the new SEALDD server IP address and port, the AF service impact with EAS IP replacement is performed through the old or new SEALDD server to the 3GPP core network as described in 3GPP TS 23.548 V17.3.0 clause 6.3.3.2.

[0341] The EAS IP replacement feature requires support for TCP / TLS / QUIC (Transmission Control Protocol / Transport Layer Security / Quick UDP (User Datagram Protocol) Internet Connections) context transfer between EAS. One possible impact for SEALDD discovery using EEL (Edge Enabler Layer) may be an enhanced EAS profile during the EAS registration process that has such seamless transport service continuity capabilities so that old SEALDD servers can discover new SEALDD servers that support TCP / TLS / QUIC context transfer (i.e., T-EAS (Target EAS) in the EDGEAPP context).

[0342] This solution can solve the key issue #7 in 3GPP TR 23.700-34 V0.6.0 regarding SEALDD server discovery and selection. The T-EAS discovery process is used to facilitate SEALDD layer service continuity.

[0343] The solution can address key issue #2 in 3GPP TR 23.700-34 V0.6.0 to leverage the features defined in 3GPP SA2 for EAS IP replacement to support SEALDD-enabled transport layer state coordination for service continuity. The impact on EAS registration is identified to enable appropriate T-EAS discovery to support smooth transport service continuity.

[0344] According to various embodiments, several new improvements are proposed. An enabling layer context transfer process is added, and specific context information is described in the process. The EAS profile is enhanced with new capabilities, especially for the EAS IP replacement feature.

[0345] The embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments herein, the proposed solution may support EAS relocation scenarios involving SEALDD servers (e.g., EAS relocation initiated by AF / AS for load balancing or EAS relocation initiated by 5GC due to UE location changes). In some embodiments herein, the proposed solution may enable the SEALDD enabler to provide support for seamless relocation and lossless data delivery. In some embodiments herein, the proposed solution may support service continuity when the PIN application in the UE is in a mobile state. In some embodiments herein, the proposed solution may support service continuity and maintain communication with the PIN application when the UE moves out of the PIN. In some embodiments herein, the T-EAS discovery process is used to promote SEALDD layer service continuity. In some embodiments herein, the proposed solution may utilize the features defined in 3GPP SA2 for EAS IP replacement to support SEALDD-enabled transport layer state coordination for service continuity. The impact on EAS registration is identified to enable appropriate T-EAS discovery to support smooth transport service continuity. The embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0346] Figure 8a 800 is a block diagram showing an apparatus suitable for practicing some embodiments of the present disclosure. For example, any of the first service enabler server, the second service enabler server or the service enabler client described above can be implemented as the apparatus 800 or implemented by the apparatus 800.

[0347] The device 800 includes at least one processor 821, such as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The device 800 may further include a transmitter TX and a receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed on the associated processor 821, enable the device 800 to operate according to embodiments of the present disclosure. The combination of at least one processor 821 and at least one MEM 822 may form a processing device 825 suitable for implementing various embodiments of the present disclosure.

[0348] Various embodiments of the present disclosure may be implemented by a computer program that may be executed by one or more of the processor 821 , software, firmware, hardware, or a combination thereof.

[0349] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0350] Processor 821 may be of any type suitable to the local technical environment, and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples.

[0351] In embodiments where the apparatus is implemented as or at a first service enabler server, the memory 822 stores instructions executable by the processor 821 whereby the first service enabler server operates according to any method related to the first service enabler server as described above.

[0352] In embodiments where the apparatus is implemented as or at a second service enabler server, the memory 822 stores instructions executable by the processor 821 whereby the second service enabler server operates according to any method related to a second service enabler server as described above.

[0353] In embodiments where the apparatus is implemented as or at a service enabler client, the memory 822 stores instructions executable by the processor 821 whereby the service enabler client operates according to any of the methods described above in relation to service enabler clients.

[0354] Figure 8b is a block diagram showing a first service enabler server according to an embodiment of the present disclosure. As shown in the figure, the first service enabler server 840 includes a first receiving module 841, which is configured to receive context information of the second service enabler server from the second service enabler server. The first service enabler server 840 may also include a storage module 842, which is configured to store the context information of the second service enabler server. The first service enabler server 840 may also include a first sending module 843 and / or an initiating module 844, the first sending module 843 is configured to send the endpoint information of the first service enabler server to the service enabler client, and the initiating module 844 is configured to initiate a business impact process with the network to request to replace the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0355] In an embodiment, the first service enabler server 840 may further include a second sending module 845 configured to send a registration request including a profile of the first service enabler server to the edge enabler server (EES). The profile of the first service enabler server includes information indicating support for transport layer context transfer.

[0356] In an embodiment, the first service enabler server 840 may further include a second receiving module 846 configured to receive a registration response from the EES.

[0357] Figure 8c 8 is a block diagram showing a second service enabler server according to an embodiment of the present disclosure. As shown in the figure, the second service enabler server 860 includes a first sending module 861, which is configured to send context information of the second service enabler server to the first service enabler server.

[0358] In an embodiment, the second service enabler server 860 may further include a second sending module 862 configured to send a registration request including a profile of the second service enabler server to the EES. The profile of the second service enabler server includes information indicating support for transport layer context transfer.

[0359] In an embodiment, the second service enabler server 860 may further include a first receiving module 863 configured to receive a registration response from the EES.

[0360] In an embodiment, the second service enabler server 860 may further include a third sending module 864 configured to send a discovery request for discovering a service enabler server supporting transport layer context transfer to the EES.

[0361] In an embodiment, the second service enabler server 860 may further include a second receiving module 865 configured to receive a registration response including information about the discovered service enabler server supporting transport layer context transfer from the EES.

[0362] In an embodiment, the second service enabler server 860 may further include an initiation module 866 configured to initiate a service impact procedure with the network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

[0363] Figure 8d 8 is a block diagram showing a service enabler client according to another embodiment of the present disclosure. As shown in the figure, the service enabler client 870 includes a first receiving module 871, which is configured to receive endpoint information of the first service enabler server from the first service enabler server. The context information of the second service enabler server is received and stored in the first service enabler server.

[0364] In an embodiment, the service enabler client 870 may further include a sending module 872 configured to send a discovery request for discovering a service enabler server supporting transport layer context transfer to the EES.

[0365] In an embodiment, the service enabler client 870 may further include a second receiving module 873 configured to receive a registration response including information of a discovered service enabler server supporting transport layer context transfer from the EES.

[0366] By using the functional unit, the first service enabler server, the second service enabler server or the service enabler client may not need a fixed processor or memory, and any computing resources and storage resources may be arranged from the first service enabler server, the second service enabler server or the service enabler client in the communication system. The introduction of virtualization technology and network computing technology can improve the utilization efficiency of network resources and the flexibility of the network.

[0367] According to one aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform any of the above methods.

[0368] According to one aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform any of the above methods.

[0369] In addition, an exemplary overall communication system including a terminal device and a network node will be introduced below.

[0370] Embodiments of the present disclosure provide a communication system including a host computer, the host computer including: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a network node (such as a first service enabler server or a second service enabler server, etc.) and / or a terminal device, such as the above-mentioned service enabler client.

[0371] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the base station.

[0372] In an embodiment of the present disclosure, a processing circuit of a host computer is configured to execute a host application to provide user data; and a terminal device includes a processing circuit configured to execute a client application associated with the host application.

[0373] The embodiment of the present disclosure also provides a communication system including a host computer and a base station, wherein the host computer includes: a communication interface configured to receive user data originating from a transmission from a terminal device. The transmission is from the terminal device to the base station.

[0374] In an embodiment of the present disclosure, the processing circuit of the host computer is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0375] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments.

[0376] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to wireless networks, such as Fig. 9 For simplicity, Fig. 9 The wireless network of FIG. 1 depicts only the network 1006, the network nodes 1060 (corresponding to the network side nodes) and 1060b, and the WDs (corresponding to the terminal devices) 1010, 1010b, and 1010c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, the network node 1060 and the wireless device (WD) 1010 are depicted with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device to access services provided by the wireless network and / or use services provided by or via the wireless network.

[0377] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0378] The network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communications between devices.

[0379] The network node 1060 and WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and signals via wired or wireless connections.

[0380] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and then may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may further include one or more components (or all components) of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Components of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet another example of a network node includes a multi-standard radio (MSR) device (e.g., an MSR BS), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide a wireless device with access to a wireless network or to provide certain services to a wireless device that has accessed a wireless network.

[0381] exist Fig. 9 In the embodiment, the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig. 9The network node 1060 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 1060 are depicted as a single box located within a larger box or a single box nested within multiple boxes, in reality, the network node can include multiple different physical components that constitute a single illustrated component (for example, the device readable medium 1080 can include multiple separate hard drives and multiple RAM modules).

[0382] Similarly, the network node 1060 may be composed of multiple physically separated components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1060 includes multiple individual components (e.g., BTS and BSC components), one or more individual components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single individual network node in some cases. In some embodiments, the network node 1060 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components (e.g., separate device-readable media 1080 for different RATs) may be repeated, and some components may be reused (e.g., the same antenna 1062 may be shared by the RATs). The network node 1060 may further include multiple sets of various illustrated components for different wireless technologies integrated into the network node 1060, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .

[0383] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) as described herein as provided by the network node. Such operations performed by the processing circuit 1070 may include processing information obtained by the processing circuit 1070 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0384] The processing circuit 1070 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which can operate alone or in conjunction with other network node 1060 components (e.g., device readable medium 1080) to provide network node 1060 functions. For example, the processing circuit 1070 can execute instructions stored in the device readable medium 1080 or a memory within the processing circuit 1070. Such functions may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC).

[0385] In some embodiments, processing circuit 1070 may include one or more of the following: radio frequency (RF) transceiver circuit 1072 and baseband processing circuit 1074. In some embodiments, radio frequency (RF) transceiver circuit 1072 and baseband processing circuit 1074 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuit 1072 and baseband processing circuit 1074 may be on the same chip or chipset, board, or unit.

[0386] In certain embodiments, some or all of the functions described herein as provided by a network node, base station, eNB, or other such network node may be performed by processing circuit 1070 executing instructions stored on device-readable medium 1080 or memory within processing circuit 1070. In alternative embodiments, some or all of the functions may be provided by processing circuit 1070, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable medium. In any of these embodiments, processing circuit 1070 may be configured to perform the described functions, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functions are not limited to processing circuit 1070 or to other components of network node 1060, but are generally enjoyed by network node 1060 as a whole and / or by end users and wireless networks.

[0387] Device readable medium 1080 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data and / or instructions that can be used by processing circuit 1070. Device readable medium 1080 may store any suitable instructions, data or information that can be executed by processing circuit 1070 and used by network node 1060, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions. Device readable medium 1080 may be used to store any calculations made by processing circuit 1070 and / or any data received through interface 1090. In some embodiments, processing circuit 1070 and device readable medium 1080 may be considered integrated.

[0388] Interface 1090 is used for wired or wireless communication of signaling and / or data between network node 1060, network 1006 and / or WD 1010. As shown, interface 1090 includes one or more ports / one or more terminals 1094, which are used, for example, to send data to network 1006 and receive data from network 1006 via a wired connection. Interface 1090 further includes a radio front-end circuit 1092, which can be coupled to antenna 1062, or in some embodiments is part of antenna 1062. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 can be connected to antenna 1062 and processing circuit 1070. The radio front-end circuit can be configured to adjust the signal transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front end circuit 1092 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1098 and / or amplifiers 1096. The radio signal may then be transmitted through the antenna 1062. Similarly, when receiving data, the antenna 1062 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 1092. The digital data may be passed to the processing circuit 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0389] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, and instead, the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without the separate radio front end circuit 1092. Similarly, in some embodiments, all or some of the RF transceiver circuit 1072 may be considered part of the interface 1090. In still other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074, which is part of the digital unit (not shown).

[0390] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuit 1090 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector or flat panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals to / from devices in a specific area, and flat panel antennas may be line of sight antennas used to send / receive radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna 1062 may be separated from network node 1060 and may be connected to network node 1060 via an interface or port.

[0391] Antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0392] The power circuit 1087 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 1060 for performing the functions described herein. The power circuit 1087 may receive power from the power supply 1086. The power supply 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the various components (e.g., at the voltage and current level required by each respective component). The power supply 1086 may be included in the power circuit 1087 and / or the network node 1060 or outside the power circuit 1087 and / or the network node 1060. For example, the network node 1060 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source supplies power to the power circuit 1087. As another example, the power supply 1086 may include a power source in the form of a battery or a battery pack, which is connected to the power circuit 108 or integrated in the power circuit 1087. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.

[0393] Alternative embodiments of network node 1060 may include, in addition to Fig. 9 , which may be responsible for providing certain aspects of the network node functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1060 may include a user interface device to allow information to be input to the network node 1060 and to allow information to be output from the network node 1060. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1060.

[0394] As used herein, a wireless device (WD) refers to a device that can, is configured, is arranged and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a network, a WD may be designed to send information to a network according to a predetermined schedule. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted wireless terminal devices, etc. For example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), WD can support device-to-device (D2D) communication, and in this case, WD can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, such as metering devices of power meters, industrial machinery, or household or personal appliances (such as refrigerators, televisions, etc.), personal wearable devices (such as watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0395] As shown, wireless device 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036 and power supply circuit 1037. WD 1010 may include multiple sets of one or more of the components shown for different wireless technologies supported by WD 1010 (e.g., such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within WD 1010.

[0396] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and connected to interface 1014. In some alternative embodiments, antenna 1011 may be separated from WD 1010 and may be connected to WD 1010 via an interface or port. Antenna 1011, interface 1014 and / or processing circuit 1020 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front end circuitry and / or antenna 1011 may be considered as an interface.

[0397] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020, and is configured to condition the signals communicated between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or may be part of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered part of the interface 1014. The radio front-end circuit 1012 may receive digital data, which will be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1012. The digital data may be passed to processing circuit 1020. In other embodiments, the interface may include different components and / or different combinations of components.

[0398] The processing circuit 1020 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic, which can operate to provide WD 1010 functions alone or in conjunction with other WD 1010 components (e.g., device readable medium 1030). Such functions may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 1020 may execute instructions stored in the device readable medium 1030 or a memory within the processing circuit 1020 to provide the functions disclosed herein.

[0399] As shown, the processing circuit 1020 includes one or more of the following: RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of WD 1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined in one chip or chipset, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In yet another alternative embodiment, part or all of RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 1022 may be part of interface 1014. RF transceiver circuit 1022 may condition RF signals for processing circuit 1020.

[0400] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by the processing circuit 1020 executing instructions stored on the device-readable medium 1030, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit 1020 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 1020 or to other components of the WD 1010, but are generally enjoyed by the WD 1010 as a whole and / or by end users and wireless networks.

[0401] Processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations as performed by processing circuit 1020 may include processing information obtained by processing circuit 1020 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 1010, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0402] Device-readable medium 1030 is operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by processing circuit 1020. Device-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuit 1020. In some embodiments, processing circuit 1020 and device-readable medium 1030 may be considered integrated.

[0403] The user interface device 1032 may provide a component that allows a human user to interact with the WD 1010. This interaction may be in multiple forms, such as visual, auditory, tactile, etc. The user interface device 1032 may operate to generate output to the user and allow the user to provide input to the WD 1010. The type of interaction may vary depending on the type of user interface device 1032 installed in the WD 1010. For example, if the WD 1010 is a smart phone, the interaction may be through a touch screen; if the WD 1010 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1032 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 1032 is configured to allow information to be input into the WD 1010, and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. The user interface device 1032 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 1032 is also configured to allow information to be output from the WD 1010, and to allow the processing circuit 1020 to output information from the WD 1010. The user interface device 1032 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 1032, the WD 1010 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0404] Auxiliary device 1034 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and types of components of auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0405] In some embodiments, the power source 1036 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. The WD 1010 may further include a power circuit 1037 for delivering power from the power source 1036 to various components of the WD 1010 that require power from the power source 1036 to perform any function described or indicated herein. In some embodiments, the power circuit 1037 may include a power management circuit. The power circuit 1037 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 1010 may be connected to an external power source (e.g., a power outlet) via an input circuit or an interface such as a power cable. In some embodiments, the power circuit 1037 may also be operable to deliver power from an external power source to the power source 1036. This may be used, for example, to charge the power source 1036. The power circuit 1037 may perform any formatting, conversion, or other modifications to the power from the power source 1036 to make the power suitable for the various components of the WD 1010 being powered.

[0406] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments.

[0407] Fig.10 An embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Conversely, a UE may represent a device that is intended to be sold to or operated by a human user but may not be or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE1100 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.10 As shown, UE 1100 is an example of a WD that is configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE can be used interchangeably. Therefore, although Fig.10 It is UE, but the components discussed here are also applicable to WD, and vice versa.

[0408] exist Fig.10 In the embodiment, UE 1100 includes a processing circuit 1101, which is operably coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connection interface 1111, a memory 1115 (including a random access memory (RAM) 1117, a read-only memory (ROM) 1119, and a storage medium 1121, etc.), a communication subsystem 1131, a power supply 1113 and / or any other components, or any combination thereof. The storage medium 1121 includes an operating system 1123, an application 1125, and data 1127. In other embodiments, the storage medium 1121 may store other similar types of information. Some UEs may utilize Fig.10 All components shown in the UE or only a subset of the components. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0409] exist Fig.10 In the embodiment of the present invention, the processing circuit 1101 can be configured to process computer instructions and data. The processing circuit 1101 can be configured to implement any sequential state machine that is operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 1101 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0410] In the depicted embodiment, the input / output interface 1105 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1100 may be configured to use an output device through the input / output interface 1105. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1100 and provide output from the UE 1100. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1100 may be configured to use an input device through the input / output interface 1105 to allow a user to capture information into the UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. For example, the sensor can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0411] exist Fig.10 In the embodiment of the present invention, the RF interface 1109 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface 1111 can be configured to provide a communication interface to the network 1143a. The network 1143a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1143a can include a Wi-Fi network. The network connection interface 1111 can be configured to include a receiver and a transmitter interface, which is used to communicate with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can alternatively be implemented separately.

[0412] RAM 1117 may be configured to interface with processing circuit 1101 via bus 1102 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 1119 may be configured to provide computer instructions or data to processing circuit 1101. For example, ROM 1119 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input and output (I / O), booting, or receipt of keystrokes from a keyboard, which are stored in non-volatile memory. Storage media 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable tape, or flash drive. In one example, the storage medium 1121 may be configured to include an operating system 1123, an application 1125 (e.g., a web browser application, a widget or gadget engine, or another application), and a data file 1127. The storage medium 1121 may store any operating system or combination of operating systems from a variety of operating systems for use by the UE 1100.

[0413] The storage medium 1121 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. The storage medium 1121 may allow the UE 1100 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture (e.g., an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 1121, which may include a device-readable medium.

[0414] exist Fig.10In the embodiment of the present invention, the processing circuit 1101 can be configured to communicate with the network 1143b using the communication subsystem 1131. The network 1143a and the network 1143b can be the same network or multiple networks or different networks or multiple networks. The communication subsystem 1131 can be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 can be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication according to one or more communication protocols (e.g., IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.), such as another WD, UE or base station of a radio access network (RAN). Each transceiver can include a transmitter 1133 and / or a receiver 1135 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 1133 and the receiver 1135 of each transceiver can share circuit components, software or firmware, or can alternatively be implemented separately.

[0415] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) power or direct current (DC) power to the components of the UE 1100.

[0416] The features, benefits and / or functions described herein may be implemented in one of the components of UE 1100 or divided across multiple components of UE 1100. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 may be configured to include any component described herein. In addition, the processing circuit 1101 may be configured to communicate with any such component via a bus 1102. In another example, any such component may be represented by a program instruction stored in a memory, and when the program instruction is executed by the processing circuit 1101, the program instruction performs the corresponding function described herein. In another example, the function of any such component may be divided between the processing circuit 1101 and the communication subsystem 1131. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0417] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments.

[0418] Fig.11 1 is a schematic block diagram illustrating a virtualized environment 1200 in which functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0419] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0420] Functionality may be implemented by one or more applications 1220 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that are operable to implement some features, functions, and / or benefits of some embodiments disclosed herein. Applications 1220 run in a virtualized environment 1200 that provides hardware 1230 including processing circuitry 1260 and memory 1290-1. Memory 1290-1 stores instructions 1295 that may be executed by processing circuitry 1260, whereby applications 1220 are operable to provide one or more features, benefits, and / or functionality disclosed herein.

[0421] The virtualized environment 1200 includes general or special purpose network hardware devices 1230, which include a set of one or more processors or processing circuits 1260, which may be commercial off-the-shelf (COTS) processors, special purpose application-specific integrated circuits (ASICs), or any other type of processing circuit, including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuit 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also known as network interface cards, which include a physical network interface 1280. Each hardware device may further include a non-transitory, persistent, machine-readable storage medium 1290-2 in which software 1295 and / or instructions that may be executed by the processing circuit 1260 have been stored. The software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also known as hypervisors), software for executing virtual machines 1240, and software that enables them to perform functions, features and / or benefits associated with some of the embodiments described herein.

[0422] The virtual machine 1240 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of the virtual device 1220 may be implemented on one or more virtual machines 1240 and may be implemented in different ways.

[0423] During operation, processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1250 may present a virtual operating platform that appears to virtual machines 1240 as networked hardware.

[0424] like Fig.11As shown in , hardware 1230 can be a standalone network node with common or specific components. Hardware 1230 can include antenna 12225 and some functions can be implemented through virtualization. Alternatively, hardware 1230 can be part of a larger hardware cluster (e.g., in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 12100, which, among other things, oversees the lifecycle management of application 1220.

[0425] Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises devices.

[0426] In the context of NFV, a virtual machine 1240 can be a software implementation of a physical machine that runs a program as if the program were running on a physical, non-virtualized machine. Each virtual machine 1240, and that portion of the hardware 1230 on which the virtual machine executes, whether hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 1240, forms a separate virtual network element (VNE).

[0427] Still in the context of NFV, a virtual network function (VNF) is responsible for handling a specific network function running in one or more virtual machines 1240 on the hardware networking infrastructure 1230 and corresponds to Fig.11 Application 1220.

[0428] In some embodiments, one or more radio units 12200 (each radio unit includes one or more transmitters 12220 and one or more receivers 12210) can be coupled to one or more antennas 12225. The radio unit 12200 can communicate directly with the hardware node 1230 through one or more appropriate network interfaces, and can be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0429] In some embodiments, some signaling may be implemented using a control system 12230 , which may alternatively be used for communications between the hardware node 1230 and the radio unit 12200 .

[0430] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediary network according to some embodiments.

[0431] Reference Fig.12According to an embodiment, the communication system includes a telecommunication network 1310, such as a 3GPP type cellular network, which includes an access network 1311, such as a radio access network, and a core network 1314. The access network 1311 includes a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c may be connected to the core network 1314 via a wired or wireless connection 1315. A UE 1391 located in the coverage area 1313c is configured to be wirelessly connected to or paged by the corresponding base station 1312c. A relay UE 1392 located in the coverage area 1313a may be wirelessly connected to the corresponding base station 1312a. Although multiple UEs 1391, 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to a corresponding base station 1312a, 1312b, 1312c.

[0432] The telecommunications network 1310 itself is connected to a host computer 1330, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1330 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 1321 and 1322 between the telecommunications network 1310 and the host computer 1330 may extend directly from the core network 1314 to the host computer 1330, or may extend to the host computer 1330 through an optional intermediate network 1320. The intermediate network 1320 may be one of the following, or a combination of more than one of the following: a public network, a private network, or a hosted network; the intermediate network 1320, if any, may be a backbone network or the Internet; in particular, the intermediate network 1320 may include two or more sub-networks (not shown).

[0433] Fig.12The communication system as a whole enables connectivity between the connected UEs 1391, 1392 and the host computer 1330. The connectivity may be described as an over-the-top (OTT) connection 1350. The host computer 1330 and the connected UEs 1391, 1392 are configured to transmit data and / or signaling via the OTT connection 1350 using the access network 1311, the core network 1314, any intermediate networks 1320, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1350 may be transparent in the sense that the participating communication devices through which the OTT connection 1350 passes are unaware of the routing of uplink and downlink communications. For example, the base stations 1312a, 1312b, 1312c may not or need to be informed of the past routing of incoming downlink communications having data originating from the host computer 1330 to be forwarded (e.g., handed over) to the connected UE 1391. Similarly, base stations 1312a , 1312b , 1312c need not be aware of the future routing of outgoing uplink communications originating from UE 1391 to host computer 1330 .

[0434] Fig.13 is a schematic diagram illustrating a host computer communicating with a user device over a partially wireless connection via a base station according to some embodiments.

[0435] According to the embodiment, reference will now be made to Fig.13 Describe the example implementations of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system 1400, the host computer 1410 includes: hardware 1415, which includes a communication interface 1416, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 1400. The host computer 1410 further includes a processing circuit 1418, which may have storage and / or processing capabilities. In particular, the processing circuit 1418 may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 1410 further includes software 1411, which is stored in the host computer 1410 or can be accessed by the host computer 1410 and can be executed by the processing circuit 1418. Software 1411 includes a host application 1412. The host application 1412 may operate to provide services to a remote user, such as a UE 1430 connected via an OTT connection 1450 terminated at the UE 1430 and the host computer 1410. In providing services to the remote user, the host application 1412 may provide user data sent using the OTT connection 1450.

[0436] The communication system 1400 further includes a base station 1420, which is provided in the telecommunication system and includes hardware 1425 that enables it to communicate with the host computer 1410 and the UE 1430. The hardware 1425 may include a communication interface 1426 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1400, and for communicating with devices located in the coverage area ( Fig.13 1420) establishes and maintains at least a radio interface 1427 of a wireless connection 1470. The communication interface 1426 may be configured to facilitate a connection 1460 to the host computer 1410. The connection 1460 may be direct, or it may be through a core network ( Fig.13 1420) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1425 of the base station 1420 further includes processing circuitry 1428, which may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 1420 also has software 1421 stored internally or accessible via an external connection.

[0437] The communication system 1400 further includes the UE 1430 already mentioned. Its hardware 1435 may include a radio interface 1437, which is configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area where the UE 1430 is currently located. The hardware 1435 of the UE 1430 further includes a processing circuit 1438, which may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 1430 further includes software 1431, which is stored in the UE 1430 or can be accessed by the UE 1430 and can be executed by the processing circuit 1438. The software 1431 includes a client application 1432. The client application 1432 can operate to provide services to human or non-human users via the UE 1430 with the support of the host computer 1410. In the host computer 1410, the executing host application 1412 can communicate with the executing client application 1432 by terminating the OTT connection 1450 at the UE 1430 and the host computer 1410. In providing services to users, the client application 1432 can receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1450 can send both the request data and the user data. The client application 1432 can interact with the user to generate the user data it provides.

[0438] Notice, Fig.13The host computer 1410, base station 1420 and UE 1430 shown in FIG. Fig.12 The host computer 1330, one of the base stations 1312a, 1312b, 1312c and one of the UEs 1391, 1392 are similar or identical to each other. That is, the internal workings of these entities can be as follows Fig.13 As shown, and independently, the surrounding network topology can be Fig.12 The surrounding network topology.

[0439] exist Fig.13 , an OTT connection 1450 has been abstractly drawn to illustrate communications between a host computer 1410 and a UE 1430 through a base station 1420, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 1430 or from the service provider operating the host computer 1410, or from both. While the OTT connection 1450 is active, the network infrastructure can also make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0440] The wireless connection 1470 between UE 1430 and base station 1420 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments use OTT connection 1450 to improve the performance of the OTT service provided to UE 1430, wherein the wireless connection 1470 forms the last segment. More precisely, in some embodiments herein, the proposed solution can support EAS relocation scenarios involving SEALDD servers (e.g., EAS relocation initiated by AF / AS for load balancing or EAS relocation initiated by 5GC due to UE location change). In some embodiments herein, the proposed solution can enable the SEALDD enabler to provide support for seamless relocation and lossless data delivery. In some embodiments herein, the proposed solution can support service continuity when the PIN application in the UE is in a mobile state. In some embodiments herein, the proposed solution can support service continuity and maintain communication with the PIN application when the UE moves out of the PIN. In some embodiments herein, the T-EAS discovery process is used to promote SEALDD layer service continuity. In some embodiments herein, the proposed solution may leverage features defined by 3GPP SA2 for EASIP replacement to support SEALDD-enabled transport layer state coordination for service continuity. Impact on EAS registration is identified to enable appropriate T-EAS discovery to support smooth transport service continuity.

[0441] The measurement process may be provided for the purpose of monitoring data rates, delays, and other factors that are improved by one or more embodiments. There may also be optional network functions for reconfiguring the OTT connection 1450 between the host computer 1410 and the UE 1430 in response to changes in the measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 1450 may be implemented in the software 1411 and hardware 1415 of the host computer 1410 or in the software 1431 and hardware 1435 of the UE 1430 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1450 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities, and the software 1411, 1431 may calculate or estimate the monitoring quantities from the values ​​of other physical quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not necessarily affect the base station 1420, and the base station 1420 may be unaware or imperceptible. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 1410 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in software 1411 and 1431 that uses OTT connection 1450 to transmit messages (particularly null messages or "dummy" messages) while software 1411 and 1431 monitors propagation time, errors, etc.

[0442] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0443] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, this section will only include references Fig.14 . In step 1510, the host computer provides user data. In sub-step 1511 of step 1510 (which may be optional), the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission to the UE carrying the user data. In step 1530 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0444] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0445] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, only references Fig.15 . In step 1610 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be passed via a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0446] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0447] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, this section will only include references Fig.16 . In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application, which provides user data in response to the received input data provided by the host computer. In providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates the transmission of user data to the host computer in sub-step 1730 (which may be optional). In step 1740 of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0448] Fig.17is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0449] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and 13 For the sake of brevity of this disclosure, this section will only include references Fig.17 In step 1810 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 1820 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0450] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0451] The techniques described herein can be implemented in various ways so that the device that implements one or more functions of the corresponding device described in the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding device described using the embodiments, and it can include separate components for each separate function, or can be configured as components that perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, the implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0452] Exemplary embodiments of the present invention have been described above with reference to block diagrams and flow charts of methods and apparatus. It will be understood that each block of the block diagrams and flow charts and combinations of blocks in the block diagrams and flow charts, respectively, can be implemented by various components including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, whereby the instructions executed on the computer or other programmable data processing device create components for implementing the functions specified in the flow chart block or blocks.

[0453] In addition, although the operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequence, or that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion contains several specific implementation details, these should not be interpreted as limitations on the scope of the subject matter described herein, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0454] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or the scope that may be claimed, but should be interpreted as descriptions of features that may be specific to a particular embodiment of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although the above-mentioned features may be described as working in certain combinations and even initially claimed to be so protected, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0455] It is obvious to those skilled in the art that, with the advancement of technology, the inventive concept can be implemented in various ways. The above embodiments are given for the purpose of describing rather than limiting the present disclosure, and it should be understood that, as those skilled in the art will readily appreciate, modifications and variations can be made without departing from the spirit and scope of the present disclosure. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (300) performed by a first service enabler server, comprising: receiving (302) context information of a second service enabler server from the second service enabler server; storing (304) the context information of the second service enabler server; as well as The endpoint information of the first service enabler server is sent (306) to a service enabler client, and / or a service impact procedure with a network is initiated to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

2. The method according to claim 1, wherein: Receiving context information of the second service enabler server from the second service enabler server includes: sending a context pull request to the second service enabler server; and A context pull response including the context information of the second service enabler server is received from the second service enabler server.

3. The method according to claim 1 or 2, wherein: Receiving context information of the second service enabler server from the second service enabler server includes: receiving, from the second service enabler server, a context push request including the context information of the second service enabler server; and A context push response is sent to the second service enabler server.

4. The method according to any one of claims 1 to 3, wherein: The context information of the second service enabler server includes at least one of the following: service subscription information created when an application server interacts with the data transmission service of the second service enabler server, service enabler client communication tunnel management information created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction, or The service enabler server communication tunnel management information is created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction.

5. The method according to any one of claims 1 to 4, wherein: The context information of the second service enabler server includes a profile of a personal Internet of Things (IoT) network PIN.

6. The method according to any one of claims 4 to 5, wherein: The context information of the second service enabler server further includes a transport layer context.

7. The method according to any one of claims 1 to 6, wherein: The endpoint information of the service enabler server includes at least one of the following: Uniform Resource Identifier (URI), Fully Qualified Domain Name FQDN, The Internet Protocol (IP) address for user-side communications, or Port number for user plane communication.

8. The method according to any one of claims 1 to 7, wherein: If the service enabler server is adapted for edge application EDGEAPP as edge application server EAS, the EAS relocation procedure is used to support service enabler server relocation for both user equipment UE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for UE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

9. The method according to any one of claims 1 to 8, wherein: During relocation of a service enabler server with a user plane function UPF change, the existing incomplete application service flows toward the old application server are handled by the new UPF, and the inter-UPF tunnel is used to forward the existing incomplete application service flows, and new application service flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

10. The method according to any one of claims 1 to 9, further comprising: sending a registration request including a profile of the first service enabler server to an edge enabler server EES (312), wherein the profile of the first service enabler server includes information indicating support for transport layer context transfer; and A registration response is received (314) from the EES.

11. The method according to any one of claims 1 to 10, wherein: The first service enabler server and / or the second service enabler server supports transport layer context transfer.

12. The method according to any one of claims 1 to 11, wherein: If the PIN Application Server is adapted for EDGE APP as EAS, the EAS Relocation procedure is used to support PIN AS Relocation; and / or If the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

13. The method according to any one of claims 1 to 12, wherein: If the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support service enabler server relocation for both PIN element PINE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

14. The method according to any one of claims 1 to 13, wherein: The first service enabler server is a new PIN server, the second service enabler server is an old PIN server, and the service enabler client is a PIN client, or The first service enabler server is a new service enabler architecture layer data delivery SEALDD server, the second service enabler server is a legacy SEALDD server, and the service enabler client is a SEALDD client.

15. The method according to any one of claims 1 to 14, wherein: The old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server, A new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

16. A method (400) performed by a second service enabler server, comprising: Context information of the second service enabler server is sent (402) to the first service enabler server.

17. The method according to claim 16, wherein: Sending the context information of the second service enabler server to the first service enabler server includes: receiving a context pull request from said first service enabler server; and A context pull response including the context information of the second service enabler server is sent to the first service enabler server.

18. The method according to claim 16 or 17, wherein: Sending the context information of the second service enabler server to the first service enabler server includes: sending a context push request including the context information of the second service enabler server to the first service enabler server; and A context push response is received from the first service enabler server.

19. The method according to any one of claims 16 to 18, wherein: The context information of the second service enabler server includes at least one of the following: service subscription information created when an application server interacts with the data transmission service of the second service enabler server, service enabler client communication tunnel management information created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction, or The service enabler server communication tunnel management information is created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction.

20. The method according to any one of claims 16 to 19, wherein: The context information of the second service enabler server includes a profile of a personal Internet of Things (IoT) network PIN.

21. The method according to any one of claims 19-20, wherein: The context information of the second service enabler server further includes a transport layer context.

22. The method according to any one of claims 16 to 21, wherein: If the service enabler server is adapted for edge application EDGEAPP as edge application server EAS, the EAS relocation procedure is used to support service enabler server relocation for both user equipment UE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for UE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

23. The method according to any one of claims 16 to 22, wherein: During relocation of a service enabler server with UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward the existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

24. The method according to any one of claims 16 to 23, further comprising: sending (410) a registration request including a profile of the second service enabler server to an EES, wherein the profile of the second service enabler server includes information indicating support for transport layer context transfer; and A registration response is received (414) from the EES.

25. The method according to any one of claims 16 to 24, further comprising: sending (422) a discovery request to the EES for discovering a service enabler server that supports transport layer context transfer; as well as A registration response including information about the discovered service enabler server supporting transport layer context transfer is received (424) from the EES.

26. The method according to any one of claims 16 to 25, wherein: The first service enabler server and / or the second service enabler server supports transport layer context transfer.

27. The method according to any one of claims 16 to 26, wherein: If the PIN Application Server is adapted for EDGE APP as EAS, the EAS Relocation procedure is used to support PIN AS Relocation; and / or If the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

28. The method according to any one of claims 16 to 27, wherein: If the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support service enabler server relocation for both PIN element PINE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

29. The method according to any one of claims 16 to 28, wherein: the first service enabler server is a new PIN server and the second service enabler server is an old PIN server, or The first service enabler server is a new service enabler architecture layer data delivery SEALDD server and the second service enabler server is a legacy SEALDD server.

30. The method according to any one of claims 16 to 29, wherein: The old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server, and A new data transmission path is to be established via the application client, the service enabler client, the first service enabler server and the application server.

31. The method according to any one of claims 16 to 30, further comprising: A service impact process is initiated (432) with a network to request replacement of the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

32. A method (500) performed by a service enabler client, comprising: receiving (502) endpoint information of a first service enabler server from the first service enabler server, The context information of the second service enabler server is received and stored in the first service enabler server.

33. The method of claim 32, wherein: The context information of the second service enabler server includes at least one of the following: service subscription information created when an application server interacts with the data transmission service of the second service enabler server, service enabler client communication tunnel management information created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction, or The service enabler server communication tunnel management information is created when the service enabler client is used to request the data transmission service of the second service enabler server for interaction.

34. The method according to any one of claims 32-33, wherein: The context information of the second service enabler server includes a profile of a personal Internet of Things (IoT) network PIN.

35. The method according to any one of claims 32 to 34, wherein: The context information of the second service enabler server further includes a transport layer context.

36. The method according to any one of claims 32 to 35, wherein: If the service enabler server is adapted for edge application EDGEAPP as edge application server EAS, the EAS relocation procedure is used to support service enabler server relocation for both user equipment UE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for UE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

37. The method according to any one of claims 32 to 36, wherein: During relocation of a service enabler server with UPF change, existing incomplete application traffic flows toward the old application server are handled by the new UPF, and inter-UPF tunnels are used to forward the existing incomplete application traffic flows, and new application traffic flows with the UE's new IP address as the source IP address are sent directly by the first service enabler server to the new application server.

38. The method according to any one of claims 32-37, further comprising: sending (512) a discovery request to the EES for discovering a service enabler server that supports transport layer context transfer; as well as A registration response including information about the discovered service enabler server supporting transport layer context transfer is received (514) from the EES.

39. The method according to any one of claims 32 to 38, wherein: The first service enabler server and / or the second service enabler server supports transport layer context transfer.

40. The method according to any one of claims 32 to 39, wherein: If the PIN Application Server is adapted for EDGE APP as EAS, the EAS Relocation procedure is used to support PIN AS Relocation; and / or If the PIN AS is not suitable for EDGE APP, a new PIN AS is discovered by the service enabler client.

41. The method according to any one of claims 32 to 40, wherein: If the service enabler server is adapted for EDGE APP as EAS, the EAS relocation procedure is used to support service enabler server relocation for both PIN element PINE mobility and service enabler server load rebalancing; and / or If the service enabler server is not suitable for EDGEAPP, for PINE mobility, the first service enabler server is discovered by the service enabler client, and a new communication channel including old communication channel information is established by the service enabler client, and for service enabler server load rebalancing, the first service enabler server is discovered by the second service enabler server.

42. The method according to any one of claims 32 to 41, wherein: the first service enabler server is a new PIN server and the second service enabler server is an old PIN server, or The first service enabler server is a new service enabler architecture layer data delivery SEALDD server and the second service enabler server is a legacy SEALDD server.

43. The method according to any one of claims 32 to 42, wherein: The old data transmission path is established via the application client, the service enabler client, the second service enabler server and the application server, and A new data transmission path is established via the application client, the service enabler client, the first service enabler server and the application server.

44. The method according to any one of claims 32 to 43, wherein: The endpoint information of the service enabler server includes at least one of the following: Uniform Resource Identifier (URI), Fully Qualified Domain Name FQDN, The Internet Protocol (IP) address for user-side communications, or Port number for user plane communication.

45. A first service enabler server (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first service enabler server (800) is operable to: receiving context information of the second service enabler server from the second service enabler server; storing the context information of the second service enabler server; as well as Sending the endpoint information of the first service enabler server to a service enabler client, and / or initiating a service impact procedure with a network to request replacing the endpoint information of the second service enabler server with the endpoint information of the first service enabler server.

46. ​​The first service enabler server of claim 45, wherein: The first service enabler server is further operable to perform the method of any one of claims 2 to 15.

47. A second service enabler server (800), comprising: Processor(821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the second service enabler server (800) is operable to: The context information of the second service enabler server is sent to the first service enabler server.

48. The second service enabler server according to claim 47, wherein: The second service enabler server is further operable to perform the method of any one of claims 17 to 31 .

49. A service enabler client (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the service enabler client (800) is operable to: receiving, from a first service enabler server, endpoint information of the first service enabler server, The context information of the second service enabler server is received and stored in the first service enabler server.

50. The service enabler client of claim 49, wherein: The service enabler client is further operable to perform the method of any one of claims 33 to 44.

51. A computer-readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 44.

52. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 44.

Images