RU2783809C2 - Communication method and communication device - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: communication method contains stages, at which the first message, which relates to a session, and which is sent by the third service sample, is received by means of the first service sample, while the first message contains a target identifier, wherein the target identifier contains an identifier of the third service sample, in case if the third service sample is unavailable, the second service sample, which should provide a service for the session, is determined by means of the first service sample, based on the identifier of the third service sample, and the second message related to the session is sent by means of the first service sample to the second service sample, wherein the first service sample is a network element of a user plane function (UPF), and the second service sample and the third service sample are network elements of a session management function (SMF).

EFFECT: increase in a speed of processing of service samples.

12 cl, 16 dwg

Description

Technical field

[0001] This application relates to the field of communication and, more specifically, to a communication method and a communication device.

State of the art

[0002] In the process of providing a communication service for a single user equipment, a plurality of service instances are generally required to communicate with each other. For example, the producer service instance sends a message related to the user equipment to the service structure, and the service structure selects one consumer service instance from the plurality of consumer service instances and sends the message related to the user equipment to the consumer service instance.

[0003] However, in some scenarios, the same service instance is required to serve the same user equipment. The above method cannot guarantee that the same service instance serves the same user equipment in multiple messaging processes. In the prior art, either of two service instances that are communicating related to the same user equipment notifies the peer service instance to subsequently send a message related to the user equipment to the service instance to complete the binding between the service instances. However, the above method of direct binding between service instances increases the binding between service instances and increases the complexity of processing the service instances.

The essence of the invention

[0004] This application provides a communication method and a communication device to reduce the complexity of processing service instances.

[0005] According to a first aspect, a communication method is provided. The communication method includes: receiving a first message sent by the first service instance, the first message including a target identifier; and sending, based on the first message, a second message to a second service instance that has a binding relationship with the target identifier.

[0006] The binding between the target identifier and the service instance in the above technical solution is used to replace the direct binding between service instances in the prior art. This can reduce the coupling between service instances and reduce the complexity of handling service instances.

[0007] It should be understood that the service instance may be a network function in a fifth-generation (5G) mobile communication system, or may be a service provided by a network function. As technology advances, the service instance may alternatively be a service instance separated from the network function. It is not specifically limited in this embodiment of this application.

[0008] It should be understood that the first message is a message related to the user equipment. The first message is used to request a second service. The second service is a service related to the user equipment and provided by the second instance of the service.

[0009] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: when there is no service instance that has a binding relationship with the target ID, obtaining a target service set ID based on the first message; selecting a third service instance from the target service set based on the target service set identifier; and sending a third message to a third service instance based on the first message.

[0010] In the above solution, when there is no service instance that has a link relationship to the target identifier, a new service instance can be quickly and efficiently selected as the target service instance based on the target service set identifier. This ensures the reliability of the service.

[0011] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: obtaining a target service set identifier from the first message, the first message further including a target service set identifier; obtaining a target service set identifier from the target identifier in the first message, the target identifier including the target service set identifier; or defining the service set identifier as the target service set identifier, wherein the service set identifier has a mapping relationship with the target identifier in the first message.

[0012] It should be understood that different service sets have different service set identifiers. The location of the information element which is in the first message and which is occupied by the target service set identifier is not specifically limited in this embodiment of this application. As described above, the target service set identifier may occupy an information element in the target identifier or may occupy an information element in the first message other than the target identifier; or the target service set identifier may be obtained based on a mapping relationship between the target identifier and the service set identifier.

[0013] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: receiving a fourth message sent by the second service instance, and obtaining, through the service transmission proxy server, a binding relationship between the target identifier and the second service instance based on the fourth messages. It should be understood that in the above technical solution, the service instance sends a fourth message to trigger the service transfer proxy to establish a binding relationship between the service instance and the target identifier. In this embodiment of this application, alternatively, the service transfer proxy may actively establish a binding relationship between the service instance and the target identifier without being initiated by the fourth message.

[0014] With reference to the first aspect, in some implementations of the first aspect, the fourth message is a user equipment related message, or the fourth message is a dedicated Binding Request message.

[0015] With reference to the first aspect, in some implementations of the first aspect, the fourth message carries a target identifier.

[0016] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: after receiving the fourth message sent by the second service instance, assigning a target identifier to the second service instance.

[0017] The service transfer proxy assigns a target identifier to the service instance. This can reduce the load on the service instance and reduce the complexity of handling service instances.

[0018] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: when the message is a user equipment related message, adding a target identifier to the fourth message.

[0019] After assigning the target ID, the service transfer proxy adds the target ID to the fourth message. This can ensure that the first service instance can obtain the target ID after receiving the fourth message to which the target ID is added, and can subsequently send the message to the second service instance including the target ID. Thus, the service transfer proxy can send a message to the second service instance based on the binding relationship between the target identifier and the service instance.

[0020] With reference to the first aspect, in some implementations of the first aspect, the fourth message carries at least one of a binding indication and a binding timer, wherein the binding timer is used to release the binding relationship between the target identifier and the second service instance after the binding timer expires.

[0021] It should be understood that the case in which the fourth message carries a binding indication can be understood as an explicit trigger. Of course, the fourth message may alternatively include no indication of the binding. This case can be understood as an implicit trigger. In this case, the service transfer proxy directly establishes, after receiving the fourth message, a binding relationship for binding the target ID and the service instance.

[0022] The binding time for binding a service instance and a target identifier can be precisely controlled by the binding timer so that another service instance can be selected after the binding timer expires. Thus, load balancing is better maintained.

[0023] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: receiving a fifth message sent by the second service instance, the fifth message being used to request release of a binding relationship between the target identifier and the second service instance; or starting the binding timer and releasing the binding relationship between the target identifier and the second service instance after the binding timer expires.

[0024] When the service instance does not need to process a message related to the user equipment, the service instance notifies, using the triggered unbind request or the bind timer, the service handover proxy to release the binding relationship between the target identifier and the service instance. In the above solution, the service transfer proxy maintains a binding relationship between a target identifier and a service instance. Compared with the prior art in which a service instance directly maintains a binding relationship between service instances, the above solution can further reduce the complexity of processing service instances.

[0025] It should be understood that the service instance may initiate a debind request when the service instance has a relatively heavy load, goes offline, goes down, etc., to notify the service handover proxy to debind the target identifier from the service instance. This ensures that the service related to the user equipment can be removed from the service instance in any of the above cases.

[0026] With reference to the first aspect, in some implementations of the first aspect, the fifth message further carries indication information, and the indication information is used to indicate a service transmission proxy to associate a target identifier with a third service instance.

[0027] The fifth message carries indication information to indicate to unbind the target identifier from the original service instance and bind the target identifier to another service instance. This completes the service load transfer between service instances and implements load balancing between service instances.

[0028] It should be understood that the second service instance may request to bind the target identifier to be bound to another service instance when it learns that the other service instance has a relatively light load or better communication quality. However, this is not limited to this embodiment of this application.

[0029] With reference to the first aspect, in some implementations of the first aspect, the target identifier refers to a single user equipment or group of user equipment. Target IDs with granular granularity facilitate the administration of granular services.

[0030] It should be understood that the target identifier may have different formats. For example, when the target ID refers to a single user equipment, the target ID may be at least one of the IP address and port number of the handover proxy server. Alternatively, the target identifier may include a service set identifier to which the second service instance belongs and a unique identifier within the service set. Alternatively, the target identifier is a value that is assigned by the service handover proxy and is unique within that service handover proxy. This application is not limited. When the target identifier refers to a user equipment group, the target identifier may be a service set identifier corresponding to the second service instance, or include a service set identifier and a second service instance identifier, or a service set identifier and a unique service identifier in the service set, the service identifier being used to identify the group of user equipment served by the service set, and so on. In this application, it is expressly not limited.

[0031] It should be understood that a target identifier relating to a single user equipment or a target identifier relating to a plurality of user equipments may be selected based on a specific requirement. When a target ID pertaining to one user equipment or a target ID pertaining to a plurality of user equipments is selected, it is not specifically limited in this embodiment of this application.

[0032] With reference to the first aspect, in some implementations of the first aspect, the target identifier is one of the service indicators configured for the second service instance, and the communication method further includes: receiving a sixth message from the second service instance, the sixth message being used to request service pointer configuration for the second service instance; and sending a sixth response message to the second service instance, the sixth response message including a service indicator configured for the second service instance.

[0033] The service transfer proxy configures the service pointer for the service instance. This may realize the automatic configuration of the service pointer.

[0034] It should be understood that the sixth response message includes one or more service indicators.

[0035] It should be understood that the service indicator may be a service indicator associated with one user equipment, or may be a service indicator associated with multiple user equipments. In other words, one service pointer may correspond to one user equipment or may correspond to multiple user equipments.

[0036] It should be understood that when the service indicator refers to one user equipment, then the service indicator may be in the range of the service indicator (eg, from 1 to 100).

[0037] With reference to the first aspect, in some implementations of the first aspect, the second service instance sends a registration request to the service handover proxy, the registration request including at least one of the following: service instance identifier, service type, manufacturer information , the capacity of the service instance, the area to which the service instance provides the service, the network segment capabilities supported by the service instance, and the identifier of the service set to which the service instance belongs. Based on different service types, the registration request may additionally carry other information such as a data network name (DNN).

[0038] With reference to the first aspect, in some implementations of the first aspect, before the second service instance sends a registration request to the service handover proxy, the method further includes: the second service instance discovering the handover proxy.

[0039] For example, address information, such as a fully qualified domain name (FQDN) or an IP address of a serving service transfer proxy server, may be preconfigured in a configuration file of the second service instance. Alternatively, the service instance discovers the serving service transfer proxy using a discovery mechanism. For example, the second service instance may discover the serving proxy by sending a broadcast or multicast message on the network, or by using a discovery mechanism similar to that of a dynamic host configuration protocol (DHCP) server discovery mechanism. It is not specifically limited in this embodiment of this application.

[0040] With reference to the first aspect, in some implementations of the first aspect, the sixth message includes the number of service indicators that are applied by the second service instance, and the communication method further includes: configuring the service indicator for the second service instance based on the number of service indicators, which are applied by the second instance of the service.

[0041] The sixth message carries the number of requested service indicators. Thus, the service instance requests, based on the service instance load or other information, the service transfer proxy to assign a service pointer to ensure that the service related to the user equipment is administered with an appropriate granularity.

[0042] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: configuring a service pointer for the second service instance based on the capacity of the second service instance.

[0043] The sixth message carries the capacity of the service instance. Thus, the service handover proxy can configure the service pointer comprehensively considering the capacity of the other service instance in the service set to which the second service instance belongs to ensure that binding and unbinding are performed with the proper granularity.

[0044] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: determining a service set to which the second service instance belongs; and configuring a service indicator for the second service instance such that the service indicator corresponding to the second service instance is different from the service indicator corresponding to another service instance in the service set.

[0045] When assigning a service pointer, the identifier of the service set to which the service instance belongs is also taken into account. Different service pointers are assigned to service instances in the same service set. This can avoid conflict between service pointers in a service set. The same pointer is assigned to service instances in different service sets. This can avoid conflict between service pointers throughout the network and avoid waste of service pointer resources.

[0046] With reference to the first aspect, in some implementations of the first aspect, the target identifier includes one of the service indicators configured for the second service instance, and the communication method further includes: receiving a seventh message from the second service instance, the seventh message including includes a service pointer corresponding to the second service instance, so that the service transfer proxy associates the second service instance with the service pointer.

[0047] In the above technical solution, the service indicator in the seventh message may be a service indicator preconfigured for the second service instance. This can ensure that the service pointer is pre-assigned or pre-configured for the second service instance based on the requirement of the second service instance.

[0048] With reference to the first aspect, in some implementations of the first aspect, the communication method further includes: when the service indicator corresponding to the second service instance conflicts with the service indicator corresponding to another service instance in the service set to which the second service instance belongs, reconfiguring the service guide for the second service instance; and sending a seventh response message to the second service instance, the seventh response message including the service pointer reconfigured for the second service instance.

[0049] When the service pointer corresponding to the service instance conflicts with the service pointer corresponding to another service instance in the service set to which the service instance belongs, the service handover proxy reassigns the service pointer to the service instance. This guarantees the uniqueness of the service pointer in the same service set.

[0050] With reference to the first aspect, in some implementations of the first aspect, when the first message is a Hypertext Transfer Protocol HTTP message, the target identifier is located in the HTTP message header.

[0051] The target identifier is located in the HTTP message header to help the service transfer proxy identify and process the target identifier.

[0052] It should be understood that the first message may be an HTTP message, an AMQP message, or a message in another format. The first message is not specifically limited in this embodiment of this application.

[0053] According to a second aspect, a communication method is provided. The communication method includes: sending the second service instance a fourth message to the service handover proxy, the fourth message being used to initiate the handover proxy to establish a binding relationship between the second service instance and the target ID, and the target ID is related to the user equipment; and receiving, by the second service instance, a second message that relates to the user equipment and that is forwarded by the service transfer proxy, the second message including the target identifier.

[0054] With reference to the second aspect, in some implementations of the second aspect, the fourth message is a user equipment related message, or the fourth message is a dedicated Binding Request.

[0055] With reference to the second aspect, in some implementations of the second aspect, the fourth message includes at least one of a target identifier and an association timer.

[0056] It should be understood that the case in which the fourth message carries a binding indication can be understood as an explicit trigger. Of course, the fourth message may alternatively include no indication of the binding. This case can be understood as an implicit trigger.

[0057] The binding time for binding a service instance and a target identifier can be precisely controlled by the binding timer so that another service instance can be selected after the binding timer expires. Thus, load balancing is better maintained.

[0058] With reference to the second aspect, in some implementations of the second aspect, the communication method further includes: sending the second service instance of the target identifier to the first service instance.

[0059] With reference to the second aspect, in some implementations of the second aspect, the communication method further includes: inserting, by a service transfer proxy, a target identifier in a fourth message to send the target identifier to the first service instance.

[0060] The first service instance may obtain a target identifier corresponding to the second service instance. Thus, the first service instance can add the target identifier to the message related to the user equipment during the next exchange of messages and sends the message related to the user equipment to the second service instance with which the message was previously exchanged. This ensures that the same service instance serves the same user equipment.

[0061] With reference to the second aspect, in some implementations of the second aspect, the communication method further includes: sending the second service instance a fifth message to the service handover proxy, the fifth message being used to request release of the binding relationship between the target identifier and the second service instance .

[0062] When the service instance does not need to process a message related to the user equipment, the service instance notifies, using the triggered unbind request, the service handover proxy to release the binding relationship between the target identifier and the service instance. The Service Transfer Proxy maintains a binding relationship between the target identity and the service instance. Compared with the prior art in which a service instance directly maintains a binding relationship between service instances, the above solution can further reduce the complexity of processing service instances.

[0063] It should be understood that the service instance may initiate a debind request when the service instance has a relatively heavy load, goes offline, goes down, etc., to notify the service handover proxy to debind the target identifier from the service instance. This ensures that the service related to the user equipment can be removed from the service instance in any of the above cases.

[0064] With reference to the second aspect, in some implementations of the second aspect, the fifth message further carries indication information, and the indication information is used to indicate a service transmission proxy to associate a target identifier with a third service instance.

[0065] The fifth message carries indication information to indicate to unbind the target identifier from the source service instance and bind the target identifier to another service instance. This completes the service load transfer between service instances and implements load balancing between service instances.

[0066] With reference to the second aspect, in some implementations of the second aspect, the target identifier refers to a single user equipment or group of user equipment.

[0067] The granular target identifiers simplify the administration of granular services.

[0068] With reference to the second aspect, in some implementations of the second aspect, the target identifier is one of the service indicators configured for the second service instance, and the communication method further includes: sending the second service instance a sixth message to the service handover proxy, wherein the sixth message is used to register a second service instance, and the sixth message includes a service indicator corresponding to the second service instance; and receiving, by the second service instance, a sixth response message sent by the service handover proxy, the sixth response message including a service indicator configured for the second service instance.

[0069] The service handover proxy is requested to pre-configure the service pointer for the service instance. This may realize automatic configuration of the service pointer.

[0070] With reference to the second aspect, in some implementations of the second aspect, the second service instance sends a registration request to the service handover proxy, the registration request including the number of service indicators that are applied by the second service instance.

[0071] The registration request carries the number of requested service indications. Thus, the service instance requests, based on the service instance load or other information, the service transfer proxy to assign a service pointer to ensure that the service related to the user equipment is administered with the proper granularity. For example, when the service instance perceives that the service instance has a relatively large load, the service instance may request the service transfer proxy to assign a relatively large number of service pointers to the service instance in order to perform fine-grained administration. In this case, the number of user equipment corresponding to one service indicator can be reduced accordingly to ensure that the service related to the user equipment is administered with an appropriate granularity.

[0072] With reference to the second aspect, in some implementations of the second aspect, the communication method further includes: sending the second service instance a seventh message to the service transmission proxy, the seventh message including a service pointer configured by the second service instance for the second service instance .

[0073] In the above technical solution, the service indicator in the seventh message may be a manually configured service indicator for the second service instance. This can ensure that the service pointer is pre-assigned or pre-configured for the second service instance based on the requirement of the second service instance.

[0074] With reference to the second aspect, in some implementations of the second aspect, when the first message is a Hypertext Transfer Protocol HTTP message, the target identifier is located in the header of the HTTP message.

[0075] The target identifier is located in the HTTP message header to help the service transfer proxy identify and process the target identifier.

[0076] It should be understood that the first message may be an HTTP message or an AMQP message. The first message is not specifically limited in this embodiment of this application.

[0077] According to a third aspect, a communication method is provided. The communication method includes: receiving by the first service instance a target identifier that relates to the user equipment and the second service instance; and adding, by the first service instance, a target identifier to a message that relates to the user equipment and the second service instance, and sending the message, wherein the target identifier is used to send the message to the second service instance.

[0078] With reference to the third aspect, in some implementations of the third aspect, the first service instance receives a target identifier from the second service instance.

[0079] With reference to a third aspect, in some implementations of the third aspect, the first service instance receives a target identifier from a service transfer proxy related to the second service instance.

[0080] According to a fourth aspect, a communication device is provided. The communication device is configured to perform the method in accordance with any of the first aspect or possible implementations of the first aspect. In particular, the device includes a unit configured to perform a method according to any of the first aspect or possible implementations of the first aspect.

[0081] According to a fifth aspect, another communication device is provided. The communication device is configured to perform a method in accordance with any of the second aspect or possible implementations of the second aspect. In particular, the device includes a unit configured to perform a method in accordance with any one of the second aspect or possible implementations of the second aspect.

[0082] According to a sixth aspect, another communication device is provided. The communication device is configured to perform a method in accordance with any of the third aspect or possible implementations of the third aspect. In particular, the device includes a unit configured to perform a method in accordance with any of the third aspect or possible implementations of the third aspect.

[0083] According to a seventh aspect, a communication device is provided. The device includes a transceiver and a processor. The transceiver communicates with the processor through the internal connection path. The processor is configured to control the receiver to receive the signal and control the transmitter to send the signal. Optionally, the communication device further includes a memory. The transceiver, memory, and processor communicate with each other via an internal connection path. The memory is configured to store the instruction. The processor is configured to execute an instruction stored in the memory to control a receiver to receive a signal and control a transmitter to send a signal so that the device can perform the method according to any of the first aspect or possible implementations of the first aspect.

[0084] According to the eighth aspect, another communication device is provided. The device includes a transceiver. The transceiver is configured to receive/send a signal. Optionally, the communication device further includes a processor. The transceiver and processor communicate with each other through an internal connection. The processor is configured to execute an instruction to control a receiver to receive a signal and control a transmitter to send a signal. Optionally, the communication device further includes a memory. The transceiver, memory, and processor communicate with each other via an internal connection path. The memory is configured to store the instruction. The processor is configured to execute an instruction stored in the memory to control a receiver to receive a signal and control a transmitter to send a signal so that the device can perform the method according to any of the second aspect or possible implementations of the second aspect.

[0085] According to a ninth aspect, another communication device is provided. The device includes a transceiver and a processor. The transceiver is configured to receive/send a signal. Optionally, the communication device further includes a processor. The transceiver and processor communicate with each other via an internal connection. The processor is configured to execute an instruction to control a receiver to receive a signal and control a transmitter to send a signal. Optionally, the communication device further includes a memory. The transceiver, memory, and processor communicate with each other via an internal connection path. The memory is configured to store the instruction. The processor is configured to execute an instruction stored in the memory to control a receiver to receive a signal and control a transmitter to send a signal so that the device can perform the method according to any of the third aspect or possible implementations of the third aspect.

[0086] According to a tenth aspect, an embodiment of this application provides a communication system. The communication system includes one or more service transfer proxies and a service instance.

[0087] The service handover proxy is configured to perform the method according to any of the first aspect or possible implementations of the first aspect, or the method performed by the handover proxy in the solutions provided in the embodiments of this application. The service instance is configured to perform a method according to any of the second aspect or possible implementations of the second aspect, a method according to any one of the third aspect or possible implementations of the third aspect or method performed by the service instance in the solutions provided in the embodiments of this application.

[0088] In an exemplary implementation, the system further includes another device, such as an access network element and/or a DN network element, that interacts with either a service handover proxy or a service instance in the solutions provided in the embodiments of this application.

[0089] According to an eleventh aspect, a communication method is provided. The communication method includes: receiving by the first service instance a first message related to the first session and sent by the third service instance or the fourth service instance, the first message including a target identifier; determining by the first service instance, based on the target identifier, the second service instance to provide the service for the first session; and sending, by the first service instance, a second message relating to the first session to the second service instance.

[0090] The first service instance determines, based on the target identifier, the service instance that is to provide the service for the first session. This increases the flexibility of the service instance selection so that the selected service instance that should provide the service for the first session can subsequently be different from the service instance that previously provided the service for the first session to avoid interruption caused by the first session due to the failure of the third instance. services.

[0091] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the first message includes binding method indication information, the binding method indication information is used to indicate binding of the first session to the third service instance or binding of the first session to the target service set, and the target set service includes a second service instance and a third service instance.

[0092] The first service instance may determine, based on the binding method indication information, a service instance selection method.

[0093] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the target identifier includes the identifier of the third service instance.

[0094] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the method further includes:

the first service instance receiving a third message sent by the third service instance, the third message including backup indication information, the backup indication information being used to indicate the second service instance to provide a backup for the third service instance or to indicate the second service instance to provide backup for the first session group, for which the third service instance provides a service, and the first session group includes the first session; and determining by the first service instance based on the target identifier of the second service instance to provide the service for the first session, including: when the third service instance is unavailable, determining by the first service instance of the second service instance based on the backup indication information and the target identifier.

[0095] Based on the backup indication information, the first service instance may use the service instance that provides backup for the first session group as a candidate service instance. When the third service instance to which the first session is bound is not available, the backup service instance must provide the service for the first session. This will help avoid interruption of the first session due to the failure of the third instance of the service and improve the user experience.

[0096] With reference to the eleventh aspect, in some implementations of the eleventh aspect, determining by the first service instance, based on the target identifier, the second service instance to provide the service for the first session, includes: obtaining by the first service instance a target service set identifier based on the target identifier ; and determining, by the first service instance, a second service instance from the target service set based on the target service set identifier, the target service set including the second service instance, the third service instance, and the fourth service instance.

[0097] The first service instance determines, based on the target service set identifier, the service instance that is to provide the service for the first session. This increases the flexibility of the service instance selection so that the selected service instance that should provide the service for the first session can subsequently be the same or different from the service instance that previously provided the service for the first session to avoid interrupting the first session because the service instance not available.

[0098] With reference to the eleventh aspect, in some implementations of the eleventh aspect, determining by the first service instance of the second service instance from the target service set based on the target service set identifier includes: sending, by the first service instance, the target service set identifier to the NRF network element with a network storage function and receiving, by the first service instance, the identifier of the second service instance, which is sent by the NRF network element, to determine the second service instance.

[0100] The first service instance determines, based on the service instance identifier that is sent by the NRF network element, that this service instance should provide the service for the first session. This may reduce the requirements for storage capacity and the ability to process the first instance of the service.

[0101] With reference to an eleventh aspect, in some implementations of the eleventh aspect, the method includes: receiving by the first service instance the first information sent by the service instance in the target service set, the first information including a service instance identifier and a target service set identifier; and determining, by the first service instance, a second service instance from the target service set based on the target service set identifier, including: determining, by the first service instance, a second service instance based on the target service set identifier and the first information.

[0102] The first service instance in accordance with the received target service set identifier and one or more identifiers of one or more service instances included in the target service set to determine the service instance that should provide the service for the first session. This can reduce the dependency of the first service instance on another network element in the system and reduce system latency, and there is no need to deploy an additional network element such as a Domain Name Resolution Server (DNS) or NRF.

[0103] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the first service instance deriving a target service set identifier based on the target identifier includes: deriving the first service instance of the target service set identifier from the target identifier, wherein the target identifier includes the identifier of the target set of services; or when the target identifier includes the identifier of the third service instance, deriving by the first service instance the identifier of the target service set based on the identifier of the third service instance, the target service set including the third service instance.

[0104] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the target identifier includes the identifier of the first session group, and the first session group includes the first session; and determining by the first service instance, based on the target ID, the second service instance to provide the service for the first session, including: sending the first service instance of the first session group ID to the network element of the NRF network repository function; and receiving, by the first service instance, the identifier of the second service instance, which is sent by the NRF network element, to determine the second service instance.

[0105] The first service instance determines, based on the session group to which the first session belongs, the service instance that is to provide the service for the first session. This avoids a state error caused by the first session because the service instance that is randomly selected by the first service instance from the target service set is different from the service instance selected by another network element, such as an AMF network element in the system.

[0106] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the first service instance is a network element of the UPF user plane function, and the second service instance, the third service instance, and the fourth service instance are network elements of the SMF session control function.

[0107] According to a twelfth aspect, a communication device is provided. The communication device includes a processor and a communication interface. The communication interface is configured to receive a first message that relates to the first session and is sent by the third service instance or the fourth service instance, the first message including the target identifier. The processor is configured to determine, based on the target identifier, the second service instance that should provide the service for the first session. The communication interface is further configured to send a second message related to the first session to the second service instance.

[0108] The communication device determines, based on the target identifier, the service instance that should provide the service for the first session. This increases the flexibility of the service instance selection so that the selected service instance that should provide the service for the first session can subsequently be different from the service instance that previously provided the service for the first session to avoid interruption caused for the first session due to the failure of the third session. service instance.

[0109] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the first message includes the binding method indication information, the binding method indication information is used to indicate the binding of the first session to the third service instance or the binding of the first session to the target service set, and the target set service includes a second service instance and a third service instance.

[0110] The communication device may determine, based on the binding method indication information, a service instance selection method.

[0111] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the target identifier includes the identifier of the third service instance.

[0112] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the communication interface is further configured to receive a third message sent by the third service instance, the third message including backup indication information, the backup indication information being used to indicate the second service instance to provide a backup for a third service instance or specify a second service instance to provide backup for a first session group for which the third service instance provides a service and the first session group includes the first session. When the third service instance is not available, the processor is configured to determine the second service instance based on the backup indication information and the target ID.

[0113] Based on the backup indication information, the communication device may use the service instance that provides backup for the first session group as a candidate service instance. When the third service instance to which the first session is bound is not available, the backup service instance must provide the service for the first session. This will help avoid interruption of the first session due to the failure of the third instance of the service and improve the user experience.

[0114] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the processor is further configured to obtain a target service set identifier based on the target identifier. The processor is further configured to determine a second service instance from the target service set based on the target service set identifier, the target service set including the second service instance, the third service instance, and the fourth service instance.

[0115] The communication device determines, based on the target service set identifier, the service instance that is to provide the service for the first session. This increases the flexibility of the service instance selection so that the selected service instance that should provide the service for the first session can subsequently be the same or different from the service instance that previously provided the service for the first session to avoid interrupting the first session because the service instance not available.

[0116] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the communication interface is further configured to send the target service set identifier to the network element of the NRF network repository function. The communication interface is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0117] The communication device determines, based on the service instance ID that is sent by the NRF network element, that this service instance should provide the service for the first session. This may reduce the requirement for storage capacity and the ability to handle the first instance of the service.

[0118] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the communication interface is further configured to receive first information sent by a service instance in the target service set, the first information including a service instance identifier and a target service set identifier. The processor is configured to determine the second service instance based on the target identifier and the first information.

[0119] The communication device receives a target service set and one or more identifiers of one or more service instances included in the target service set to determine the service instance that should provide the service for the first session. This can reduce dependency on another network element in the system and reduce system latency, and there is no need to deploy an additional network element such as a Domain Name Resolution Server (DNS) or NRF.

[0120] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the processor is further configured to obtain a target service set identifier from the target identifier, the target identifier including the target service set identifier; or when the target identifier includes the identifier of the third service instance, the processor is further configured to derive the target service set identifier based on the identifier of the third service instance, the target service set including the third service instance.

[0121] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the target identifier includes the identifier of the first session group, and the first session group includes the first session. The communication interface is further configured to send the first session group ID to the network element of the NRF network repository function. The communication interface is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0122] The communication device determines, based on the session group to which the first session belongs, the service instance that is to provide the service for the first session. This avoids a state error caused by the first session because the service instance that is randomly selected by the communication device from the target service set is different from the service instance selected by another network element, such as an AMF network element in the system.

[0123] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the communication device is a network element of the UPF user plane function, and the second service instance, the third service instance, and the fourth service instance are network elements of the SMF session control function.

[0124] According to a thirteenth aspect, a communication device is provided. The communication device includes a transceiver unit and a determination unit. The transceiver unit is configured to receive a first message that relates to the first session and that is sent by the third service instance or the fourth service instance, the first message including the target identifier. The determiner is configured to determine, based on the target ID, the second service instance to provide the service for the first session. The transceiver unit is further configured to send a second message related to the first session to the second service instance.

[0125] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the first message includes binding method indication information, wherein the binding method indication information is used to indicate binding of the first session to the third service instance or binding of the first session to the target service set, and the target the service set includes a second service instance, a third service instance, and a fourth service instance.

[0126] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the target identifier includes the identifier of the third service instance.

[0127] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the transceiver unit is further configured to receive a third message sent by a third service instance, wherein the third message includes backup indication information, wherein the backup indication information is used to indicate the second service instance to provide a backup for a third service instance or specify a second service instance to provide backup for a first session group for which the third service instance provides a service and the first session group includes the first session. When the third service instance is unavailable, the determining unit is configured to determine the second service instance based on the backup indication information and the target ID.

[0128] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the communication device further includes a receiving unit. The acquiring unit is configured to obtain a target service set ID based on the target ID. The determining unit is configured to determine a second service instance from the target service set based on the target service set identifier, the target service set including the second service instance, the third service instance, and the fourth service instance.

[0129] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the transceiver unit is further configured to send the target service set identifier to the NRF network repository function network element. The transceiver unit is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0130] With reference to a thirteenth aspect, in some implementations of the thirteenth aspect, the transceiver unit is further configured to receive first information sent by a service instance in the target service set, the first information including a service instance identifier and a target service set identifier. The determiner is configured to determine the second service instance based on the target service set identifier and the first information.

[0131] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the acquiring unit is configured to obtain a target service set identifier from the target identifier, the target identifier including the target service set identifier.

[0132] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, when the target identifier includes the identifier of the third service instance, the obtaining unit is configured to obtain the identifier of the target service set based on the identifier of the third service instance, and the target service set includes the third service instance.

[0133] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the target identifier includes the identifier of the first session group, and the first session group includes the first session. The transceiver unit is further configured to send the first session group ID to the network element of the NRF network repository function. The transceiver unit is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0134] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the communication device is a network element of the user plane function UPF, and the second service instance, the third service instance, and the fourth service instance are network elements of the SMF session control function.

[0135] According to a fourteenth aspect, a communication method is provided. The communication method includes: sending by the third service instance a first message related to the first session, the first service instance, wherein the first message includes a target identifier, the target identifier is used to indicate the first service instance to determine the second service instance, and the second service instance is used to provide the service for the first session.

[0136] With reference to the fourteenth aspect, in an exemplary implementation, the first message includes binding method indication information, the binding method indication information is used to indicate binding of the first session to the third service instance or binding of the first session to the target service set, and the target service set includes into itself a second instance of the service and a third instance of the service.

[0137] With reference to the fourteenth aspect, in a possible implementation, the target identifier includes the identifier of the third service instance.

[0138] With reference to the fourteenth aspect, in an exemplary implementation, the third service instance receives capability indication information sent by the first service instance or network element of the NRF network repository function, wherein the capability indication information is used to indicate that the first service instance supports load balancing based on on the target service set, and the target service set includes a second service instance and a third service instance.

[0139] With reference to the fourteenth aspect, in an exemplary implementation, the third service instance sends a target service set identifier and a third service instance identifier to the first service instance, the target service set including the second service instance and the third service instance.

[0140] With reference to the fourteenth aspect, in an exemplary implementation, the third service instance sends backup indication information to the first service instance, wherein the backup indication information is used to indicate the second service instance to provide a backup for the third service instance or to provide a backup for the first session group for which the second service instance provides the service and the first session group includes the first session.

[0141] According to a fifteenth aspect, a communication device is provided. The communication device is configured to perform the method in accordance with any of the fourteenth aspect or possible implementations of the fourteenth aspect. In particular, the device includes a unit configured to perform a method according to any of the fourteenth aspect or possible implementations of the fourteenth aspect.

[0142] According to the sixteenth aspect, a communication device is provided. The device includes a transceiver and a processor. The transceiver communicates with the processor through an internal connection path. The processor is configured to control the receiver to receive the signal and control the transmitter to send the signal. Optionally, the communication device further includes a memory. The transceiver, memory, and processor communicate with each other via an internal connection path. The memory is configured to store the instruction. The processor is configured to execute an instruction stored in the memory to control a receiver to receive a signal and control a transmitter to send a signal so that the device can perform the method according to any of the fourteenth aspect or possible implementations of the fourteenth aspect.

[0143] According to the seventeenth aspect, a communication system is provided. The communication system includes a first instance of the service. The first service instance is configured to perform a method according to any of the eleventh aspect or possible implementations of the eleventh aspect or method performed by the first service instance in the solutions provided in the embodiments of this application.

[0144] With reference to the seventeenth aspect, in a possible implementation, the system may further include a third service instance. The third service instance is configured to perform the method according to any of the fourteenth aspect or possible implementations of the fourteenth aspect, or the method performed by the third service instance in the solutions provided in the embodiments of this application.

[0145] With reference to the seventeenth aspect, in an exemplary implementation, the system may further include another device, such as an access control function network element, that interacts with the first service instance and/or the third service instance in the eleventh aspect and the fourteenth aspect. The access control function network element may be configured to perform the method performed by the access control function network element in the solutions provided in the embodiments of this application.

[0146] According to an eighteenth aspect, a computer program product is provided. The computer program product includes computer program code. When the computer program code is run on the computer, the computer is enabled to execute the method in any possible implementation of any of the above aspects.

[0147] According to a nineteenth aspect, a computer-readable medium is provided. The computer-readable medium is configured to store a computer program. The computer program includes instructions used to perform the method in any possible implementation of any of the above aspects.

[0148] According to the twentieth aspect, a communication chip is provided. The communication chip stores the instruction. When an instruction is executed on a computing device, the communication chip is enabled to execute the method in any possible implementation of any of the above aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

[0149] FIG. 1 is a schematic architectural diagram of a 5G system according to an embodiment of this application;

[0150] FIG. 2 is a schematic diagram of a service infrastructure according to an embodiment of this application;

[0151] FIG. 3 is a schematic diagram of a communication method according to an embodiment of this application;

[0152] FIG. 4 is a schematic diagram of a communication method according to another embodiment of this application;

[0153] FIG. 5 is a schematic diagram of a communication method according to another embodiment of this application;

[0154] FIG. 6 is a schematic diagram of a communication method according to another embodiment of this application;

[0155] FIG. 7 is a schematic diagram of a communication method according to another embodiment of this application;

[0156] FIG. 8 is a schematic diagram of a communication method according to another embodiment of this application;

[0157] FIG. 9 is a schematic diagram of a communication method according to another embodiment of this application;

[0158] FIG. 10 is a schematic diagram of a communication method according to another embodiment of this application;

[0159] FIG. 11 is a schematic structural diagram of a handover proxy server according to an embodiment of this application;

[0160] FIG. 12 is a schematic structural diagram of a service instance according to an embodiment of this application;

[0161] FIG. 13 is a schematic structural diagram of a handover proxy server according to an embodiment of this application;

[0162] FIG. 14 is a schematic structural diagram of a service instance according to another embodiment of this application;

[0163] FIG. 15 is a schematic structural diagram of a communication device according to another embodiment of this application; and

[0164] FIG. 16 is a schematic structural diagram of a communication device according to another embodiment of this application.

Description of Embodiments

[0165] The technical solutions presented in the embodiments of this application may be applied to various service-based communication architectures.

[0166] For ease of understanding, the following briefly describes, using the 5G communication system as an example, the service-based architecture and the communication mode of the service-based architecture with reference to FIG. 1. As shown in FIG. 1, the service-based network architecture 100 provided in the embodiment of this application includes a plurality of network functions (network function, NF).

[0167] 1. Network session control element: The network session control element is mainly configured for: session administration, assignment and administration of the Internet Protocol (IP) address of the terminal device, selection of an endpoint that can administer the functional interface of the user equipment plane and a control policy and a cost accounting function interface, perform downlink data notification, and the like. In 5G communication, the session management network element may be a session management function (SMF) network element. In future communications, such as 6G communications, the session control network element may still be an SMF network element or have a different name. In this application, it is expressly not limited. Nsmf is a service interface provided by SMF. The SMF can communicate with another network function via Nsmf.

[0168] 2. Access control network element: The access control network element is mainly configured to perform mobility administration, access administration, and the like. The access control network element may be configured to implement a function, such as legitimate interception or access authorization (or authentication), in functions of a mobility management entity (MME) other than session administration. In 5G communications, the access control network element may be an access and mobility management function (AMF) network element. In future communications, such as 6G communications, the access control network element may still be an AMF network element or have a different name. In this application, it is expressly not limited. Namf is a service interface provided by AMF. AMF can communicate with another network function via Namf.

[0169] 3. Authentication service network element: The authentication service network element is mainly configured to perform user authentication and the like. In 5G communication, the authentication service network element may be an authentication server function (AUSF) network element. In future communications such as 6G communications, the authentication service network element may still be an AUSF network element or have a different name. In this application, it is expressly not limited. Nausf is a service interface provided by AUSF. The AUSF can communicate with another network function via Nausf.

[0170] 4. Network Discovery Network Element: The Network Discovery Network Element is configured to securely expose to the outside the services, capabilities, and the like that are provided by the 3rd generation partnership project (3GPP) network function. In 5G communication, a network exposure network element may be a network exposure function (NEF) network element. In future communications such as 6G communications, the Network Discovery NE may still be a NEF NE or have a different name. In this application, it is expressly not limited. Nnef is a service interface provided by NEF. NEF can communicate with another network function via Nnef.

[0171] 5. Network repository network element: The network repository network element is configured to store network function object description information and service description information provided by the network function object, and support service discovery, network element object discovery, and the like. In 5G communications, a network repository network element may be a network repository function (NRF) network element. In future communications such as 6G communications, the network repository NE may still be a NEF NE or have a different name. In this application, it is expressly not limited. Nnrf is a service interface provided by NRF. The NRF may communicate with another network function via Nnrf.

[0172] 6. Policy Web Element: The Policy Web Element is configured to guide a unified policy framework for network behavior, provide policy rule information to a control plane function network element (such as AMF or SMF), and the like. In 5G communication, the policy control network element may be a policy control function (PCF) network element. In future communications, such as 6G communications, the policy control network element may still be a PCF network element or have a different name. In this application, it is expressly not limited. Npcf is a service interface provided by PCF. The PCF can communicate with another network function via Npcf.

[0173] 7. Network control element: The network control element is configured to perform processing of user identification, access authentication, registration administration or mobility administration, and the like. In 5G communications, the data network element may be a unified data management (UDM) network element. In future communications, such as 6G communications, the data network element may still be a UDM network element or have a different name. In this application, it is expressly not limited. Nudm is a service interface provided by UDM. The UDM can communicate with another network function via Nudm.

[0174] 8. Application network element: The application network element is configured to perform application-affected data routing, access the network discovery function, interact with the policy infrastructure to perform policy control, and the like. In 5G communications, an application network element may be an application function (AF) network element. In future communications such as 6G communications, the application network element may still be an AF network element or have a different name. In this application, it is expressly not limited. Naf is a service interface provided by AF. AF can communicate with another network function via Naf.

[0175] 9. User equipment (user equipment, UE): user equipment may include various portable devices, vehicle-mounted devices, wearable devices, or computing devices that have a wireless communication function, or other processing device connected to wireless modem, and terminals in various forms such as mobile stations (mobile station, MS), terminals (terminal), user equipment (user equipment, UE) and software terminals, such as water meter, electricity meter and sensor.

[0176] 10. Network element of the network radio (radio) access (radio access network, (R)AN): The network element (R)AN is configured to provide a network access function for authorized user equipment in a specific area and can use transmission tunnels with different quality based on user equipment levels, service requirements, etc.

[0177] A RAN network element may manage radio resources and provide an access service for a terminal device to forward control signal and user equipment data between the terminal and the core network. A RAN network element can also be understood as a base station in a conventional network.

[0178] 11. User plane function (UPF) NE: The user plane NE is configured to perform packet routing and forwarding, perform quality of service (QoS) processing on user plane data, and the like. In 5G communication, a user plane network element may be a user plane function (UPF) network element. In future communications, such as 6G communications, the user plane NE may still be a UPF NE or have a different name. In this application, it is expressly not limited.

[0179] 12. Network element of the data network (Data Network, DN): the network element DN is configured to provide a network for data transmission, for example, the Internet network. The DN network element may be a data network authentication, authorization, accounting network element, an application server (application function), or the like.

[0180] It can be understood that the aforementioned functions or network elements may be network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions built on a platform (eg, a cloud platform).

[0181] Interface N1 in FIG. 1 - reference point between UE and AMF. The N2 interface is the anchor point between the RAN and the AMF and is used to send a non-access stratum (NAS) message and a Next Generation Application Protocol (NGAP) message, and the like. The N3 interface is a reference point between the RAN and the UPF, and is used to transmit user plane data and the like. The N4 interface is a reference point between the SMF and the UPF, and is used to carry information such as N3 connection tunnel ID information, data buffering indication information, and a downlink data notification message. The H6 interface is a reference point between the UPF and the DN, and is capable of transmitting user plane data and the like.

[0182] It should be understood that the network architecture 100 is simply a network architecture described in terms of a service-based architecture. The application scenario is not limited to the embodiments of this application, and any network architecture that can implement the above network functions is applicable to the embodiments of this application.

[0183] Typically, in the process of providing a service, a user needs multiple instances of a service to exchange messages related to the user. The service instance represented in the embodiments of this application may be the network function of FIG. 1, for example, may be a session web control element, an access control web element, or a policy web control element. For ease of description, the network access control element is AMF, the network session control element is SMF, and the network policy control element is PCF, as an example for the subsequent descriptions in this application. In other words, in the following descriptions in this application, the UPF network element can be replaced by a user plane network element, and the SMF network element can be replaced by a session control network element.

[0184] For example, a producer service instance is an AMF. The AMF sends a message related to the user equipment to the service infrastructure (and the service infrastructure may include the NRF of FIG. 1 or may include another network function). Upon receiving the message related to the user equipment, the service infrastructure selects one service instance from a plurality of consumer service instances that can provide the same function. For example, the service infrastructure selects one SMF from a plurality of SMFs and sends a user equipment related message to the SMF. Thus, the producer service instance and the consumer service instance complete the exchange of a message related to the user equipment.

[0185] In some scenarios, the same service instance is required to serve the same user equipment. To achieve the above object in the prior art, two service instances that communicate with each other are directly linked to each other. For example, two service instances, AMF and SMF, handle the session administration procedure related to the user equipment. The AMF and the SMF notify each other to subsequently send each other a message related to the user equipment to implement the binding between the two service instances. However, the binding implemented by the above method increases the complexity of handling service instances, and this problem is obvious, especially in the contention scenario. For example, an AMF and a plurality of SMFs perform a plurality of user equipment related procedures. The AMF and the first SMF perform a session related procedure related to the user equipment, and the AMF and the second SMF perform a mobility related procedure related to the user equipment. When the session procedure between the first SMF and the AMF ends, the first SMF is decoupled from the AMF and determines to no longer send a user equipment related message to the AMF thereafter. However, in this case, the procedure between the AMF and the second SMF has not ended yet. Therefore, AMF does not temporarily release the user equipment context. In this case, if the first SMF initiates the session-related procedure again because the AMF has not yet released the context, the first SMF may send a message to the other AMF. Therefore, a message redirection must be performed so that the message is finally sent to the original AMF. In this case, the interaction between service instances is complex.

[0186] An embodiment of this application provides a method that can reduce the complexity of handling service instances. For ease of understanding, a schematic diagram of the service infrastructure applicable to embodiments of this application is first described below. Fig. 2 is a schematic diagram of a service infrastructure according to an embodiment of this application.

[0187] The service infrastructure shown in FIG. 2 includes an NRF 210, a service transfer proxy 220, a service transfer proxy 230, and a service set 240 for a service set 270.

[0188] FIG. 2, service instances in the same service set may provide the same function, and service instances in different service sets may provide the same function or different functions. For example, service instance 241 and service instance 242 in service set 240 shown in FIG. 2 can perform the same function. For example, both service instance 241 and service instance 242 may be SMF or AMF. In one example, service set 240 and service set 250 may be sets including SMFs, and both service set 260 and service set 270 may be sets including AMFs. The service set may have a service set identifier. For example, the identifier may be a FQDN, an IP address, a Service Set ID, or another unique identifier. The service set identifier type is not specifically limited in this embodiment of this application. Each service instance in a service set may have a target identifier. The target identifier can have different formats. For example, when the target ID refers to a single user equipment, the target ID may be at least one of the IP address and port number of the handover proxy server. Alternatively, the target identifier may include a service set identifier to which the second service instance belongs and a unique identifier within the service set. Alternatively, the target identifier is a value that is assigned by the service handover proxy and is unique within that service handoff proxy. In this application, it is expressly not limited. When the target identifier refers to a user equipment group, the target identifier may be a service set identifier corresponding to the second service instance, or include a service set identifier and a second service instance identifier, or a service set identifier and a unique service identifier in the service set, the service identifier being used to identify the group of user equipment served by the service set, and so on. In this application, it is expressly not limited.

[0189] There may be a communication interface between the service transfer proxy and the service instance. For ease of understanding, the function of the communication interface is described below with reference to an example. As shown in FIG. 2, the service handover proxy 220 may exchange a message with the service instance in the service set 240 via the I1 interface. For example, when the message received by the handover proxy 220 includes a target service set identifier, the handoff proxy 220 determines, based on an identifier that is related to the target service set contained in the message, whether there is a direct interface between the proxies. a service transfer server 220 and a target set of services. Assuming that the identifier that refers to the target service set that is contained in the message is the identifier of the service set 240, the handover proxy 220 determines whether there is a direct interface between the handover proxy 220 and the target service set 240. Since there is a direct interface between the service transfer proxy 220 and the target service set 240, the service transfer proxy may select the target service instance from the service set 240 and send a message to the target service instance.

[0190] It should be understood that the messaging procedure between the service handover proxy and the service instance described above is merely an example and should not limit the embodiments of this application.

[0191] There may also be an interface between service transfer proxies so that the service transfer proxies can also exchange messages. For example, the service transfer proxy 230 and the service transfer proxy 220 may exchange a message over the I2 interface. When there is no direct interface between the service handover proxy and the target service instance, the message may be forwarded to the target service instance through the interface between the handover proxies.

[0192] It should be understood that the service transfer (service) proxy server provided in this embodiment of this application may be a network function newly defined in the service infrastructure. For example, the service transfer proxy may be an HTTP reverse proxy (HTTP Reverse Proxy). In some deployment modes, for ease of communication, the service handover proxy may alternatively be deployed in the same data center as the service instance that interfaces with the handover proxy. Of course, the service handover proxy and the service instance that interfaces with the service handoff proxy may alternatively be deployed in different data centers. It is not specifically limited in this embodiment of this application. In order to support remote disaster recovery, a set of services may be deployed in multiple data centers, and specifically, multiple instances of services in a set of services may be deployed in different data centers. In this case, one handover proxy server instance can be deployed in each data center in which a set of services is deployed, and service handover proxy server instances deployed in a plurality of data centers constitute the aforementioned handoff proxy server.

[0193] It should be understood that the service transfer proxy presented in this embodiment of this application may further support the functions of registering and discovering a local service instance. When the service instance is registered, the service transfer proxy may bind the service instance to a target identifier.

[0194] The service infrastructure presented in this embodiment of this application may further include an NRF 210. The service transfer proxy may sometimes register service set and service instance information in the NRF 210. The NRF 210 may communicate with the transfer proxy services through the I3 interface. When the handover proxy is composed of handover proxy server instances deployed in multiple data centers, the handoff proxy registers the address information of the handover proxy multiple instances in the NRF 210 so that the NRF 210 can select other proxy instances. -service transfer servers for various user equipment. This supports load sharing among a set of services in different data centers, and avoids data path bypass caused by forwarding data by the same service proxy.

[0195] It should be understood that the service infrastructure shown in FIG. 2 is just an example and the service infrastructure may have many structural variations. For example, the service infrastructure may only include a service transfer proxy. In this case, the service handover proxy may integrate the functions of the NRF and the handover proxy shown in FIG. 2. Alternatively, the service infrastructure may include only the service instance and the NRF. In this case, the NRF integrates the functions of the NRF and the service handover proxy in FIG. 2.

[0196] In addition, the service handover proxy function responsible for registering and discovering a service instance and the service handover proxy function responsible for message forwarding may be two independent entities.

[0197] With reference to FIG. 3, the communication method according to an embodiment of this application is described below.

[0198] The communication method shown in FIG. 3 includes steps 310 and 330. Next, each step in FIG. 3 in detail.

[0199] Step 310: Receive the first message sent by the first instance of the service, the first message including the target identifier.

[0200] The service instance represented in this embodiment of this application may be the network function of FIG. 1, for example, may be AMF, SMF or PCF. Alternatively, the service instance may be one of a plurality of service instances obtained by splitting from the network function. As technology advances, the service instance may alternatively exist independently of the network function. It is not specifically limited in this embodiment of this application.

[0201] The first message may be a message related to the user equipment and sent by the first instance of the service. In one example, when the first service instance is an AMF or an SMF, the first message may be a message in a session related procedure, a message in a mobility related procedure, or the like.

[0202] The first message carries a target identifier. The target identifier can have different formats. For example, when the target ID refers to a single user equipment, the target ID may be at least one of the IP address and port number of the handover proxy server. Alternatively, the target identifier may include a service set identifier to which the second service instance belongs and a unique identifier within the service set. Alternatively, the target identifier is a value that is assigned by the service handover proxy and is unique within that service handoff proxy. In this application, it is expressly not limited. When the target identifier refers to a user equipment group, the target identifier may be a service set identifier corresponding to the second service instance, or include a service set identifier and a second service instance identifier, or a service set identifier and a unique service identifier in the service set, the service identifier being used to identify the group of user equipment served by the service set, and so on. In this application, it is expressly not limited.

[0203] In one example, the network element that receives the first message in step 310 may be a service handover proxy in the service infrastructure, or, of course, may be another network element that may provide a handover proxy function. This is not specifically limited in this embodiment of this application.

[0204] Optionally, before step 310, the first service instance may further receive a target identifier related to the user equipment, such that the first message carries the target identifier before or during step 310. In one example, when the first service instance is an SMF, the SMF may accept before sending the first message the target ID sent by AMF. In one example, the SMF may receive, in a session establishment procedure between the SMF and the AMF, the target identifier sent by the AMF and store the target identifier in the context of the user equipment. Thus, when the SMF needs to send an AMF message subsequently, the SMF can obtain the target ID related to the user equipment from the user equipment context and add the target ID to the first message.

[0205] In terms of message type, the first message may be an HTTP message, an AMQP message, or the like. This is not specifically limited in this embodiment of this application.

[0206] Step 330: The service handover proxy sends, based on the first message, a second message to the second service instance having a link relationship to the target identifier.

[0207] The target identifier and the second service instance may have a binding relationship. In other words, the corresponding service instance can be found based on the target identifier. In one example, when the target identifier is a service pointer, the target service instance can be found based on a match between the service pointer and the service instance.

[0208] When the first message is an HTTP message, the target identifier may be located in the HTTP message header to help the service transfer proxy identify and process the target identifier. In this embodiment of this request, a new optional HTTP header called the target identifier can be added. Here, that the new header is called the target identifier is used merely as an example, and the specific name of the newly defined HTTP header is not specifically specified in this embodiment. Alternatively, the target identifier may be located in a network tag (cookie) field in the HTTP message. The HTTP message may include a message body and may further include a uniform resource identifier (URI), a selection parameter, and the like. The message body may also be referred to as the main message body. The message body may include a parameter related to the service provided by the second service instance. The selection parameter may be used to specify a service transfer proxy to determine the second service instance and send a message to the second service instance.

[0209] Optionally, before step 330, the communication method shown in FIG. 3 may further include step 320.

[0210] Step 320: The service handover proxy finds if there is a service instance having a binding relation to the target identifier. If the service transfer proxy finds that the second service instance has a binding relationship with the target identifier, the service transfer proxy sends a second message to the second service instance based on the first message.

[0211] It should be understood that the second message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the second message and directly forwards the first message to the second service instance. Of course, the second message may alternatively be different from the first message. After receiving the first message, the handover proxy may modify the first message, use the modified first message as the second message, and send the second message to the second service instance. For example, the service transfer proxy changes the header of the first message, but keeps the message body of the first message unchanged in order to receive the second message, and sends the second message to the second service instance. It is not specifically limited in this embodiment of this application.

[0212] It should be understood that the service transfer proxy may previously store a binding relationship between the target identifier and the service instance. When receiving the first message, the handover proxy may find, based on the target identifier in the first message, whether there is a service instance having a binding relation to the target identifier. Alternatively, another network element (eg, NRF or data storage unit) may previously store a binding relationship between the target identifier and the service instance. When the service transfer proxy receives the first message, the service transfer proxy looks for a corresponding service instance in another network element based on the target ID in the first message. The network element looks up the binding relationship between the target identifier and the service instance, and notifies the service handover proxy of the result; and the service transfer proxy forwards the message to the target service instance, and so on. The storage location of the anchor relationship between the target identifier and the service instance and the network element for searching the anchor relationship is not specifically limited in this application.

[0213] The binding between the target identifier and the service instance is used to replace the direct binding between service instances in the prior art. This can reduce connections between service instances and reduce the complexity of handling service instances.

[0214] Alternatively, there may be no binding between the target identifier and the service instance. In other words, the service transfer proxy cannot find, based on the target ID, a service instance having a binding relation to the target ID. In this case, the service transfer proxy may obtain the target service set identifier based on the first message, select another service instance from the set, and send the first message to the selected service instance.

[0215] With reference to FIG. 4, the method used when there is no anchor relationship in the service transfer proxy is described below.

[0216] FIG. 4 is a schematic diagram of a communication method according to another embodiment of this application. The method corresponding to FIG. 4 includes steps 410 through 430. Steps 410 through 430 are described below.

[0217] Step 410: The service transfer proxy receives the first message sent by the first service instance, the first message including the target identifier. Step 410 corresponds to step 310 in FIG. 3. Optionally, before performing step 410, the first service instance may also exchange a message with the second service instance to obtain a target identifier corresponding to the second service instance. Details are not described here.

[0218] Step 420: The service handover proxy finds if a service instance exists corresponding to the target identifier. When there is no service instance that has a binding relation to the target identifier, step 430 is executed.

[0219] Step 430: When there is no service instance that has a target ID binding relationship, the service transfer proxy obtains the target service set ID based on the first message and selects a third service instance from the target service set based on the target service set ID. The service transfer proxy sends a third message to a third service instance based on the first message.

[0220] From the above descriptions, it can be understood that different service sets have different service set identifiers. The target service set identifier is the identifier of the service set to which the second service instance belongs. In other words, the third service instance and the second service instance belong to the same service set.

[0221] It should be understood that the third message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the third message and directly forwards the first message to the second service instance. Of course, the third message may alternatively be different from the third message. After receiving the first message, the handover proxy may modify the first message, use the modified first message as the third message, and send the third message to the second service instance. For example, the service transfer proxy changes the header of the first message, but keeps the message body of the first message unchanged to receive the third message, and sends the third message to the second service instance. It is not specifically limited in this embodiment of this application.

[0222] Optionally, the service transfer proxy may obtain the target service set identifier from the first message, the first message further including the target service set identifier. Alternatively, the handover proxy obtains the target service set identifier from the target identifier in the first message, the target identifier including the target service set identifier. Alternatively, the service transfer proxy defines the service set identifier as the target service set identifier, wherein the service set identifier has a mapping relationship with the target identifier in the first message.

[0223] It should be understood that the location of the information element that is in the first message and that is occupied by the target service set identifier is not specifically limited in this embodiment of this application. For example, the target service set identifier may occupy an information element in the target identifier or may occupy an information element in the first message other than the target identifier; or the target service set identifier may be obtained based on a mapping relationship between the target identifier and the service set identifier.

[0224] It should be understood that the method for selecting the third service instance is not specifically limited in this embodiment of this application. For example, a service instance having a relatively light load may be selected from the target service set as the third service instance, or a service instance may be selected from the target service set as the third service instance in a polling mode. This is not specifically limited in this embodiment of this application.

[0225] When there is no service instance that has a binding relationship with the target ID, the target service instance may be selected from the target service set based on the target service set ID using a load balancing algorithm. This provides load balancing between service instances in the target service set.

[0226] In terms of service granularity, the aforementioned target identifier may be an identifier relating to one user equipment, or may be an identifier relating to one group or multiple user equipments.

[0227] The above describes with reference to FIG. 2 - fig. 4, a process in which a service transfer proxy determines a target service instance based on a binding relationship between the target identifier and the service instance. Before performing the steps in FIG. 2 - fig. 4, the binding relationship between the target identifier and the service instance may be further established.

[0228] In the previous descriptions, it was indicated that the target identifier may be a preconfigured target identifier or a target identifier assigned in a communication message. For the aforementioned different types of target identifiers, embodiments of this application provide different ways of establishing a binding relationship between a target identifier and a service instance. When the target service instance is registered with the service transfer proxy, the service transfer proxy may assign a target ID to the service instance and send a target ID to the service instance to complete the association between the target ID and the service instance. Alternatively, the target identifier is pre-configured in the service instance. In this case, the service instance sends the target identifier to the service transfer proxy, and the service transfer proxy maintains the binding relationship between the service instance and the target identifier to complete the binding between the target identifier and the service instance. Alternatively, when the target identifier is the target identifier assigned by the service transfer proxy or the service instance in the communication message, the service transfer proxy establishes a binding relationship between the target identifier and the service instance. In this case, the target identifier may be assigned by the service transfer proxy or the service instance. When the target ID is assigned by the service handover proxy, the service handover proxy further inserts the target ID into the communication message.

[0229] The following describes a process in which a service transfer proxy pre-establishes a binding relationship between a target identifier and a service instance. Fig. 5 and FIG. 6 each shows the process of pre-establishing a binding relationship between a target identifier and a service instance. In the example in FIG. 5 and FIG. 6, a process in which a service transfer proxy pre-establishes a binding relationship between a target ID and a service instance is described using an example in which the target ID is a service pointer.

[0230] FIG. 5 includes steps 510 through 530. Next, steps 510 through 530 are described in detail.

[0231] Step 510: The second service instance sends a sixth message to the service handover proxy, the sixth message being used by the second service instance to register with the handoff proxy.

[0232] It should be understood that the sixth message may include information about the second instance of the service. Thus, the service handover proxy associates the second service instance with the service guide based on information about the second service instance.

[0233] The specific information in the sixth message is not specifically limited in this embodiment of this application. For example, the registration request may include at least one of the following content: service instance identifier, service type, manufacturer information, service set identifier to which the service instance belongs, the scope in which the service instance provides the service, and network segment capabilities, supported by the service instance. Based on different service types, the registration request may additionally carry other information such as a data network name (DNN).

[0234] Optionally, the sixth message may further include a service pointer corresponding to the second service instance such that the service handover proxy associates the second service instance with the service pointer. In this case, the service pointer that corresponds to the second service instance and which is carried in the sixth message may be a service pointer preconfigured for the second service instance, for example, configured in a configuration file of the second service instance.

[0235] Optionally, the sixth message sent by the second service instance may include the capacity of the second service instance.

[0236] Optionally, the sixth message sent by the second service instance may include the number of service indicators that are applied by the second service instance.

[0237] Optionally, before sending the sixth message to the service handover proxy, the second service instance may first need to discover the serving handover proxy. For example, the address information (eg, FQDN or IP address) of the serving service forward proxy may be pre-configured in the configuration file of the second service instance. Alternatively, the service instance discovers the serving service transfer proxy using a discovery mechanism. For example, the second service instance may discover a serving service proxy by sending a broadcast or multicast message on the network, or by using a discovery mechanism similar to that of a dynamic host configuration protocol (DHCP) server discovery mechanism. This is not specifically limited in this embodiment of this application.

[0238] Step 520: The service handover proxy assigns a service pointer to the second service instance based on the received sixth message.

[0239] The service transfer proxy configures the service pointer for the service instance. This may realize automatic configuration of the service pointer.

[0240] When the sixth message includes information about the second service instance, the service transfer proxy may first determine, based on the information about the second service instance, the set to which the second service instance belongs. In other words, the handover proxy may first determine, based on the second service instance information, a service set identifier to which the second service instance belongs.

[0241] In particular, the service transfer proxy may determine, based on information such as service type, manufacturer information, service area, and network segment capability contained in the registration request, whether there is a set of services with the same capability and the same manufacturer and determine whether to add a second instance of the service to the existing set of services. Alternatively, the service transfer proxy creates a new set of services. The example assumes that the second service instance is AMF, the producer is H, and the second service instance supports network segment capability A and service area B. If the service handover proxy determines that there is an existing service set, the service instance in the existing service set is AMF, the manufacturer is also H, and the service instance also supports network segmentation capability A and service area B, the service handoff proxy may determine, that a new service instance can be added to an existing set of services. When the service handover proxy decides to add the second service instance to the existing service set, the service pointer assigned by the service handover proxy to the second service instance is different from the service pointer corresponding to another service instance in the service set to which the second service instance belongs, in order to avoid conflict between service pointers in the same service set.

[0242] When assigning a service pointer, the identifier of the service set to which the service instance belongs is also taken into account. Different service pointers are assigned to service instances in the same service set. This can avoid conflict between service pointers in a service set.

[0243] The registration request carries the number of requested service indications. Thus, the service instance requests, based on the load of the service instance or other information, the service transfer proxy to assign a service pointer to ensure that the service related to the user equipment is administered with an appropriate granularity.

[0244] When the registration request includes the capacity of the second service instance, the service handover proxy may assign a service pointer or the like. to the second service instance based on the capacity of the second service instance. The service handover proxy may determine, based on the capacity of the second service instance and the capacity of the other service instance in the service set to which the second service instance belongs, the number of service indicators assigned to the second service instance.

[0245] Step 530: The service handover proxy sends a sixth response message to the second service instance. Optionally, if the service handover proxy assigns the service pointer to the second service instance, the sixth response message includes the service pointer assigned to the second service instance, and the sixth response message may be used to notify the second service instance of the service pointer assigned by the service handover proxy. the second instance of the service.

[0246] Optionally, the service handover proxy may notify, with the sixth response message, the second service instance that the service handover proxy has established a binding relationship between the second service instance and the service pointer.

[0247] Optionally, FIG. 6 shows another process for establishing a binding relationship between a service pointer and a service instance.

[0248] Step 610: The second service instance sends a seventh message to the service handover proxy, the seventh message including a service indicator corresponding to the second service instance.

[0249] Step 620: The service handover proxy may check if the service pointer conflicts with the service pointer corresponding to another service instance in the service set to which the second service instance belongs. In the event of a conflict, the handover proxy may assign a new service pointer to the second service instance to replace the conflicting service pointer.

[0250] Step 630: The service handover proxy sends a seventh response message to the second service instance. If the service handover proxy assigns a new service pointer to the second service instance in step 620, the seventh response message includes the new service pointer assigned by the service handover proxy to the second service instance.

[0251] It should be understood that FIG. 5 and FIG. 6 are used as examples in which the target identifier is a service pointer. In fact, the target ID can have different formats. For example, when the target ID refers to a single user equipment, the target ID may be at least one of the IP address and port number of the handover proxy server. Alternatively, the target identifier may include a service set identifier to which the second service instance belongs and a unique identifier within the service set. Alternatively, the target identifier is a value that is assigned by the service handover proxy and is unique within that service handover proxy. In this application, it is expressly not limited. When the target identifier refers to a user equipment group, the target identifier may be a service set identifier corresponding to the second service instance, or include a service set identifier and a second service instance identifier, or a service set identifier and a unique service identifier in the service set, the service identifier being used to identify the group of user equipment served by the service set, and so on. In this application, it is expressly not limited.

[0252] It should be understood that the process shown in FIG. 5 or FIG. 6, and in which the binding relationship between the service instance and the target identifier is established, may be performed by the service handover proxy. Alternatively, after receiving the sixth message or the seventh message, the service transfer proxy may forward the message to the NRF or other network function, and the NRF or other network function establishes a binding relationship between the service instance and the target identifier. In this case, the service transfer proxy is only responsible for forwarding the message. This is not specifically limited in this embodiment of this application.

[0253] Additionally, it should be understood that in the solutions of FIG. 5 and FIG. 6, when receiving the sixth message or the seventh message, the service transfer proxy may alternatively only assign a target identifier to the service instance, but not maintain a binding relationship between the service instance and the target identifier. In this case, the service transfer proxy has not established a binding relationship between the service instance and the target identifier. The establishment of a binding relationship between a service instance and a target identifier corresponding to the service instance may be initiated by a communication message.

[0254] The following describes another method for establishing an anchor relationship between a target identifier and a service instance, namely a process in which a service transfer proxy is initiated to establish an anchor relationship between a target identifier and a service instance with a message in a communication process.

[0255] The service handover proxy may further receive a fourth message sent by the second service instance, and the service handover proxy obtains a binding relationship between the target identifier and the second service instance based on the fourth message.

[0256] Optionally, the fourth message may carry a binding relationship between the second service instance and the target identifier. In this case, the service handover proxy can obtain the binding relationship between the second service instance and the target identifier, which is carried in the fourth message. For example, the fourth message may carry a binding relationship between the IP address of the second service instance and the target identifier. In this case, the service transfer proxy can obtain the binding relationship between the IP address of the second service instance and the target ID when receiving the fourth message.

[0257] It should be understood that the fourth message used to initiate the establishment of a binding relationship can take many forms. For example, the fourth message may be a dedicated Bind Request message sent by the second service instance to the service handover proxy. The bind request message may carry one or more target identifiers. The target identifier in the Bind Request message may be a target identifier preconfigured in the service instance, or may be a target identifier assigned by the service handover proxy in the Bind Request message.

[0258] Alternatively, the fourth message may be a general message related to the user equipment. For example, the fourth message is a message sent to another instance of the service. The other service instance may be the first service instance, or may be a service instance other than the first service instance. The following uses an example in which the other service instance is the first service instance to be described. In one implementation, when sending the fourth message to the first service instance, the second service instance adds the target identifier to the fourth message. The handover proxy receives the target ID from the fourth message and establishes a binding relationship between the target ID and the second service instance. In another implementation, the fourth message does not carry a target identifier, but the fourth message does carry an indication. The service handover proxy determines, based on the indication, that the service handover proxy is to assign a target ID, and binds the target ID to the second service instance.

[0259] Alternatively, the target identifier may be the target identifier assigned by the second service instance when the second service instance sends the fourth message. Alternatively, the target identifier may be the target identifier assigned by the service handover proxy to the second service instance when the service handover proxy receives the fourth message sent by the second service instance. In the example where the service instance is an SMF and the SMF sends a fourth message related to the user equipment, the SMF may assign a reference session identifier (corresponding to smContextRef in TS 29.502) for the user equipment context. The session reference identifier is used by the SMF to uniquely identify the session context of a single user equipment. The reference session identifier may be used as the target identifier such that the SMF may be found based on the reference session identifier.

[0260] Optionally, the fourth message may carry an indication of the binding. When the fourth message includes the target identifier, the binding indication is used to indicate the service transfer proxy to record the target identifier in the fourth message. Alternatively, when the fourth message does not include the target ID, the communication proxy assigns the target ID to the second service instance when receiving the binding indication.

[0261] It should be understood that when the fourth message is a message related to the user equipment, and the target ID is assigned by the service communication proxy, the service transmission proxy additionally needs to send the target ID to the first service instance. For example, the target identifier may be inserted in the fourth message.

[0262] It should be understood that the case in which the fourth message carries an indication of a binding may also be referred to as an explicit binding.

[0263] Optionally, the fourth message carries a binding timer. The binding timer is used to release the binding relationship between the target identifier and the second service instance after the binding timer has expired.

[0264] The binding time for binding a service instance and a target identifier can be configured with a binding timer such that another service instance can be selected after the binding timer expires. Thus, load balancing is better maintained.

[0265] The above describes the process of establishing a binding relationship between a target identifier and a service instance. In some cases, the target identifier may be further decoupled from the service instance.

[0266] Optionally, the service transfer proxy may further receive a fifth message sent by the second service instance, the fifth message being used to request release of the binding relationship between the target identifier and the second service instance; or start the binding timer and release the binding relationship between the target identifier and the second service instance after the binding timer expires.

[0267] The service handover proxy may unbind the target identifier from the second service instance when the service handover proxy receives the fifth message or when the timer expires.

[0268] It should be understood that the service instance may initiate a debind request when the service instance has a relatively heavy load, goes offline, goes down, etc., to notify the service handover proxy to debind the target identity from the service instance. This ensures that the service related to the user equipment can be removed from the service instance in any of the above cases.

[0269] The fifth message may further carry indication information. The indication information is used to indicate a service transfer proxy for binding a target identifier to a third service instance.

[0270] The debinding request carries indication information to indicate that the target identifier is to be unbound from the original service instance and the target identifier is to be bound to another service instance. This completes the service load transfer between service instances and implements load balancing between service instances.

[0271] As described above, the target identifier may be one of the service pointers (which may also be referred to as instance pointers) preconfigured for the service instance. In this case, each service pointer may correspond to a plurality of user equipments. In other words, multiple user equipments served by a service instance can share the same service pointer.

[0272] The target identifier may have different formats. For example, when the target ID refers to a single user equipment, the target ID may be at least one of the IP address and port number of the handover proxy server. Alternatively, the target identifier may include a service set identifier to which the second service instance belongs and a unique identifier within the service set. Alternatively, the target identifier is a value that is assigned by the service handover proxy and is unique within that service handover proxy. In this application, it is expressly not limited. When the target identifier refers to a user equipment group, the target identifier may be a service set identifier corresponding to the second service instance, or include a service set identifier and a second service instance identifier, or a service set identifier and a unique service identifier in the service set, the service identifier being used to identify the group of user equipment served by the service set, and so on. In this application, it is expressly not limited.

[0273] Target identifiers with different granularity can be used to implement service administration with different granularity.

[0274] For ease of understanding, the following separately describes, using two detailed embodiments, the communication method provided in the embodiments of this application.

[0275] FIG. 7 is a schematic diagram of a communication method according to another embodiment of this application. The method shown in FIG. 7 includes steps 710 through 760b. The steps shown in FIG. 7 may be performed to implement the binding and unbinding method based on the granularity of the user equipment group.

[0276] Step 710: The second service instance sends a fourth message to the service handover proxy.

[0277] The fourth message is a bind request specifically sent by the second service instance to the service transmission proxy, and includes a target identifier corresponding to the second service instance. The handover proxy server receives the bind request and records the bind relationship that exists between the second service instance and the target identifier, which is contained in the bind request.

[0278] Step 720: The first service instance and the second service instance exchange a message related to the user equipment. In this process, the second service instance sends a target identifier corresponding to the second service instance to the first service instance. Upon receiving the target identifier corresponding to the second service instance, the first service instance stores the target identifier in the context of the user equipment.

[0279] In one example, the first service instance may be an AMF and the second service instance may be an SMF. The AMF may send a session establishment request to the SMF, and the SMF sends a session establishment response to the AMF and includes, in the session establishment response, a target identifier corresponding to the SMF. After receiving the target identifier corresponding to the SMF, the AMF stores the target identifier in the context of the user equipment.

[0280] It should be understood that step 710 and step 720 are not sequential in this embodiment of this application. This is not limited in this embodiment of the present application.

[0281] Step 730: The first service instance sends a first message to the service transfer proxy, the first message carrying a target identifier corresponding to the second service instance and a service set identifier corresponding to the second service instance. In particular, the first service instance obtains the target ID from the user equipment context and adds the target ID to the first message.

[0282] When the first message is an HTTP message, the target identifier and the service set identifier may be located in the header of the HTTP message to help the service transfer proxy read the target identifier.

[0283] It should be noted that there is no relationship between the first message and the fourth messages. In this embodiment, both the fourth message and the first message are sent to the service transfer proxy. However, during actual deployment, the fourth message may alternatively be a message sent to another service instance. For example, when the first service instance is the AMF and the second service instance is the SMF, the fourth message may be a message sent by the AMF to the UDM. For example, the AMF sends a message to the UDM during the user equipment registration process, and in this process, a binding relationship is established between the target identifier and the first instance of the service (namely, the AMF). When the target identifier belongs to a user equipment group, the fourth message and the first message may also be messages for different user equipments in the same user group. In this embodiment, this is not particularly limited.

[0284] Step 750: The service handover proxy finds, based on the target identifier carried in the first message, whether a service instance exists corresponding to the target identifier. If the service handover proxy records the binding relationship between the second service instance and the target ID in step 710, the service handoff proxy finds that the service instance corresponding to the target ID is the second service instance.

[0285] Step 760a: The service handover proxy sends a second message to the second service instance based on the first message.

[0286] It should be understood that the second message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the second message and directly forwards the first message to the second service instance. Of course, the second message may alternatively be different from the first message. After receiving the first message, the handover proxy may modify the first message, such as changing the header of the first message, but keeping the message body of the first message unchanged to receive the second message, and send the second message to the second service instance. This is not specifically limited in this embodiment of this application.

[0287] At a later point, for example, upon detecting an excessive load on the service, the second service instance determines to unbind the target identifier from the second service instance.

[0288] Optionally, step 740: The second service instance sends a fifth message to the service handover proxy. The unbind request is used to request the service transfer proxy to remove the binding relationship between the second service instance and the target identifier.

[0289] There may be one or more target identifiers for which debinding is requested in the bind request. Upon receiving the debinding request sent by the second service instance, the service transfer proxy may remove the binding relationship between the second service instance and the target identifier.

[0290] Optionally, the debinding request may further include indication information. The indication information is used to indicate the binding of the target identifier corresponding to the second service instance to another service instance, such as the third service instance in FIG. 7.

[0291] Step 760b: Assuming that the service handover proxy has unlinked the target identifier corresponding to the second service instance from the second service instance in step 740, and the service handover proxy cannot find, in step 750, the service instance corresponding to the target identifier in the first message, the service transfer proxy may obtain the target service set identifier based on the first message.

[0292] The third service instance may be randomly selected. Alternatively, the service instance may be selected from the target set of services as the third service instance using a load balancing algorithm.

[0293] Optionally, the service transfer proxy may obtain the target service set identifier from the first message, the first message further including the target service set identifier. Alternatively, the handover proxy obtains the target service set identifier from the target identifier in the first message, the target identifier including the target service set identifier. Alternatively, the service transfer proxy defines the service set identifier as the target service set identifier, wherein the service set identifier has a mapping relationship with the target identifier in the first message.

[0294] The service transfer proxy selects a third service instance from the target service set and sends a third message to the third service instance based on the first message.

[0295] It should be understood that the third message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the third message and directly forwards the first message to the second service instance. Of course, the third message may alternatively be different from the third message. After receiving the first message, the handover proxy may modify the first message, such as changing the header of the first message, but keeping the message body of the first message unchanged to receive the third message, and send the third message to the second service instance. This is not specifically limited in this embodiment of this application.

[0296] At step 740, if the second service instance determines to unbind the current service indicia from the second service instance and indicates the service handover proxy to forward the current service indicia to the third service instance, the handoff proxy unbinds the target identifier from the second service instance. service in accordance with the unbind request and binds the target identifier to the third service instance. In this case, the service transfer proxy selects the third service instance based on the target ID and sends the third message to the third service instance.

[0297] In the method of FIG. 7 the fourth message is a dedicated anchor request. With reference to FIG. 8 below describes in detail the procedure in which the fourth message is a message related to the user equipment. The method shown in FIG. 8 includes steps 810 through 880b.

[0298] Step 810: The first service instance sends a fourth message to the service handover proxy. The fourth message is a message related to the user equipment.

[0299] The first service instance may add to the fourth message the target identifier assigned by the first service instance to the user equipment. In an implementation, the target identifier may be used by the service instance to uniquely locate the user equipment context. For example, the first service instance may be an AMF. In this case, the AMF-compliant target identifier is the user equipment identifier, and the target identifier can be a 5G globally unique temporary identity (GUTI), subscriber permanent identifier (SUPI), permanent equipment identifier (SUPI). identifier, PEI), etc. The AMF can uniquely locate a single user equipment context based on the target ID. Alternatively, the first service instance may be an SMF. In this case, the target identifier corresponding to the SMF may be a reference session identifier (eg, smContextRef) assigned by the SMF.

[0300] The fourth message is used to initiate the establishment of a binding relationship between the target identifier and the service instance. The difference between this method and the method shown in FIG. 7 is: the fourth message in step 810 is not a dedicated bind request, but a general message related to the user equipment. For example, when the first service instance and the second service instance are AMF and SMF, respectively, the fourth message may be a create session request message. When a session is created to send a fourth message to the SMF, the first service instance, namely the AMF, may add the service set identifier corresponding to the SMF to the fourth message so that the service transfer proxy selects a peer SMF based on the service set identifier.

[0301] It should be understood that the target identifier may be obtained by the first instance of the service. For example, the first service instance requests the shared data layer corresponding to the service set to assign a target identifier. Alternatively, the target identifier segments may be configured for each service instance. In this case, the first service instance selects a target identifier from the target identifier segments configured for the first service instance. When the target identifier is assigned by the first service instance, the fourth message carries the target identifier assigned by the first service instance. Optionally, the first service instance may add a binding indication to the fourth message to indicate that the first service instance wants the service handover proxy to establish a binding relationship between the target identifier and the first service instance.

[0302] In addition, the target identifier may alternatively be assigned by the service transfer proxy when the fourth message is received. When the target ID is assigned by the service transfer proxy, the fourth message does not carry the target ID, but the service transfer proxy assigns the target ID when receiving the fourth message. In addition, the first service instance may add an indication to the fourth message, and the service transfer proxy assigns a target ID only after receiving the indication. When the target ID is assigned by the service handover proxy, the service handover proxy additionally needs to send the target ID to the second service instance. For example, the handover proxy may insert the target identifier in the fourth message.

[0303] The fourth message may be an HTTP message or an AMQP message. When the fourth message is an HTTP message, the service set identifier is carried in the HTTP hostname field in the fourth message.

[0304] Optionally, the fourth message may further carry a binding timer. The binding timer is used to release the binding relationship between the target identifier and the first instance of the service after the binding timer has expired.

[0305] Step 820: The service transfer proxy binds the target identifier to the first service instance.

[0306] In particular, the service transfer proxy stores a binding relationship between the target identifier and the first service instance.

[0307] The service transfer proxy server adds to the fourth message the target identifier corresponding to the first service instance and the identifier of the service set to which the first service instance belongs, and forwards the fourth message to the second service instance. In some implementations, the handover proxy may perform some processing on the fourth message, such as removing some fields from the fourth message or adding some fields to the fourth message. In this embodiment, this is not limited.

[0308] Step 830: The service handover proxy receives the fourth response message sent by the second service instance and forwards the fourth response message to the first service instance.

[0309] In one example, when the fourth message is a create session request message, the fourth response message is a session create response message. The second service instance may add to the fourth response message a target identifier corresponding to the second service instance, a service set identifier to which the second service instance belongs, a service set identifier to which the first service instance belongs, and a target identifier corresponding to the first service instance, and send the fourth a response message to the service transfer proxy. The handover proxy determines the first service instance based on the target identifier corresponding to the first service instance (the binding is set at 810 and 820) and forwards the fourth response message to the first service instance.

[0310] Step 840: The service transfer proxy associates a target identifier corresponding to the second service instance to the second service instance based on the fourth response message. For example, the service handover proxy may record the binding relationship between the second service instance and the target identifier. See steps 810 and 820 for information on a specific binding method.

[0311] After performing steps 810 to 840, the handover proxy has established a binding relationship between target identities and service instances, where the binding relationship includes a binding relationship between a second service instance and a target identifier corresponding to the second service instance, and a binding relationship between the first service instance and the target identifier corresponding to the first service instance. In addition, after steps 810 through 840, each of the first service instance and the second service instance has obtained a target identifier corresponding to the peer service instance.

[0312] Step 850: The first service instance may send a first message to the service transfer proxy, the first message including a target identifier corresponding to the second service instance, a service set identifier corresponding to the second service instance, and a target identifier corresponding to the first service instance. . The service transfer proxy may select the service instance based on the target identifier corresponding to the second service instance in the first message.

[0313] The first message is a message related to the user equipment. For example, when the first service instance and the second service instance are SMF and AMF, respectively, the first message may be a user equipment session related procedure message. Of course, as an alternative, the first message could be a message in another procedure. This is not specifically limited in this embodiment of this application.

[0314] It should be noted that there is no relationship between the first message and the fourth messages. In this embodiment, both the fourth message and the first message may be sent to the second service instance. However, during actual deployment, the fourth message may alternatively be a message sent to another service instance. For example, when the first service instance is the AMF and the second service instance is the SMF, the fourth message may be a message sent by the AMF to the UDM. For example, the AMF sends a message to the UDM during the user equipment registration process, and in this process, a binding relationship is established between the target identifier and the first instance of the service (namely, the AMF). When the target identifier belongs to a user group, the fourth message and the first message may also be messages for different user equipment in the same user group. In this embodiment, this is not particularly limited.

[0315] Step 870: The service transfer proxy selects a service instance based on the target ID in the first message. If the service handover proxy maintains a binding relationship between the target ID corresponding to the second service instance and the second service instance in step 840, the handover proxy may select the second service instance as the peer service instance.

[0316] Step 880a: The service handover proxy sends a second message to the second service instance based on the first message.

[0317] It should be understood that the second message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the second message and directly forwards the first message to the second service instance. Of course, the second message may alternatively be different from the first message. After receiving the first message, the handover proxy may modify the first message, such as changing the header of the first message, but keeping the message body of the first message unchanged in order to receive the second message and send the second message to the second service instance. It is not specifically limited in this embodiment of this application.

[0318] Optionally, at step 860: the service handover proxy receives a fifth message sent by the second service instance, the fifth message being used to request the service handover proxy to release the binding relationship between the second service instance and the target identifier. The fifth message may carry a target identifier corresponding to the second service instance. Based on the fifth message, the handover proxy may remove the binding relationship between the second service instance and the target identifier corresponding to the second service instance.

[0319] Optionally, the fifth message may further include indication information. The indication information is used to indicate the binding of the target identifier corresponding to the second service instance to another service instance, such as the third service instance in FIG. 8. In this case, at step 870, the service transfer proxy selects the third service instance based on the target identifier carried in the first message; and in step 880a, the handover proxy sends a third message to the third service instance based on the first message. In particular, the fifth message may be triggered when the second service instance determines to store the user equipment context in the shared data layer.

[0320] It should be understood that the reason why the second service instance sends a debinding request is not specifically limited in this embodiment of this application. For example, the reason may be that the second service instance does not want to process a procedure associated with the user equipment, or that the second service instance goes down, or that the second service instance fails.

[0321] In this case, in step 870, the handover proxy selects a peer service instance based on the target ID in the first message. The handover proxy has released the binding relationship between the second service instance and the target ID at 860.

[0322] In this case, in step 880b: the service transfer proxy may search for an appropriate service set based on an identifier that belongs to the service set and that is carried in the first message, and selects a third service instance from the set. The service transfer proxy sends a third message to a third service instance based on the first message.

[0323] Optionally, the service transfer proxy may obtain the target service set identifier from the first message, the first message further including the target service set identifier. Alternatively, the handover proxy obtains the target service set identifier from the target identifier in the first message, the target identifier including the target service set identifier. Alternatively, the service transfer proxy defines the service set identifier as the target service set identifier, wherein the service set identifier has a mapping relationship with the target identifier in the first message.

[0324] It should be understood that the first message, the second message, and the third message may carry a service set identifier, and the service set identifier may be carried in the target identifier or may be used as an independent information element. When a service set identifier is transferred, the target identifier collision in the same service set can be avoided. Of course, if it can be guaranteed that all service instances in the network correspond to different target identifiers at the time of assignment of target identifiers, the message may not carry a service set identifier. In this case, if there is no binding relationship between the target ID and the target service instance, the service transfer proxy may determine the target service set based on the target ID and select the service instance from the target service set. It is not specifically limited in this embodiment of this application.

[0325] FIG. 9 is a schematic diagram of a communication method according to another embodiment of this application.

[0326] Step 1310: The first service instance sends a first message to the service handover proxy, the first message including the target identifier.

[0327] The target identifier may refer to a single user equipment or a group of user equipment. In other words, the target ID is determined based on the user equipment.

[0328] With reference to the descriptions in FIG. 2 - fig. 8, the target identifier may be used to identify a single user equipment or a group of user equipment. For example, the target identifier may include a service pointer. The handover proxy determines the binding of the user equipment to the second service instance. The service transfer proxy determines, based on the target identifier, the service instance to which the service pointer is bound. The service instance to which the service pointer is bound serves the user equipment, and the service instance to which the service pointer is bound may be the second service instance. Anchor relationships are mutable. For example, after the service handover proxy unbinds the service pointer from the second service instance, the service handover proxy may bind the service pointer to another service instance. The target identifier can be included in the network tag field in the first message, or in a newly added optional HTTP header in the first message.

[0329] Alternatively, the target identifier may include a target service set identifier corresponding to the user equipment and/or a second service instance identifier corresponding to the user equipment. In other words, the user equipment is bound to the second instance of the service.

[0330] That the target identifier is a target service set identifier can be considered that the user equipment is associated with the target service set. The service handover proxy may determine from the target service set a service instance to serve the user equipment. For example, the service transfer proxy selects the second service instance or the third service instance to serve the user equipment.

[0331] That the target identifier may include the identifier of the second service instance may be considered that the user equipment is associated with the second service instance. The second service instance identifier is used to identify the second service instance. The second service instance identifier may be the address information of the second service instance, such as an IP address or FQDN, or may be a sequence number assigned by the service handover proxy to the second service instance. The handover proxy may uniquely identify the second service instance based on the identifier of the second service instance. The service handover proxy may determine that the second instance of the service continues to serve the user equipment. The target identifier may further include a target service set identifier.

[0332] The identifier of the second service instance may be included in the URI in the first message or included in the selection parameter in the first message.

[0333] In an implementation, the first message may include binding method indication information. The binding method indication information is used to indicate the binding method of one user equipment or a group of user equipment. In other words, the association method indication information is used to indicate whether the user equipment is associated with a service instance or a service set. This way of specifying is the way of explicit specifying. The first message may explicitly indicate the binding method using the binding method indication information. The binding method indication information may be an enumeration field. For example, the binding method indication information may be one of a plurality of values. Specifically, the indication information is one of the values in {bind to a service instance, bind to a service set}. For example, "0" indicates that the user equipment is associated with a service instance, and "1" indicates that the user equipment is associated with a set of services.

[0334] The binding method indication information may be a bitmap. For example, the binding method indication information may be represented using N bits. Each bit indicates a binding capability. For example, the indication information may be represented using two bits. One bit is used to denote "binding to a service instance". When the bit is 1, this indicates that the user equipment is associated with a service instance; and when the bit is 0, it indicates that the user equipment is not associated with a service instance. Another bit is used to denote "service set binding". When the bit is 1, this indicates that the user equipment is associated with a service set; and when the bit is 0, it indicates that the user equipment is not associated with a service set.

[0335] In this bitmap method, when the user equipment is associated with the second service instance, the target identifier may or may not include the second service instance identifier. For example, the target identifier may include a service pointer corresponding to the second service instance. When there is no binding relationship between the user equipment and the second service instance, or when there is a binding relationship between the user equipment and the second service instance, but the second service instance is unavailable (e.g., the second service instance is disabled), the service pointer is used to select the service instance to serve the user equipment.

[0336] In another implementation, the service transfer proxy determines the binding relationship indication based on the target identifier. In other words, the first message may implicitly indicate a binding relationship. For example, when the target identifier includes the identifier of the second service instance and/or the service pointer, the service transfer proxy determines that the user equipment is associated with the second service instance. The target identifier may further include a target service set identifier. When the target identifier includes only the service set identifier, the service transfer proxy determines that the user equipment is associated with the service set.

[0337] Before step S1310, the first service instance may receive a target identifier.

[0338] Before step S1310, the first service instance may receive the target identifier sent by the second service instance. The second service instance may send an eighth message to the first service instance, the eighth message including the target identifier. For example, when the target identifier includes the second service instance identifier, the eighth message includes the URI. The URI may include the address information of the second service instance, and the address information of the second service instance is used as an identifier of the second service instance. Alternatively, the message body of the eighth message includes the identifier of the second service instance. In addition, the message body of the eighth message may further include a service pointer, a service set identifier, and the like. The eighth message may be an HTTP message. The eighth message further includes binding relationship indication information. The binding relationship indication information may be included in the network tag (Cookie) field in the eighth message, or in the newly added optional HTTP header in the eighth message. In this embodiment of this request, a new optional HTTP header called the anchor indicator can be added. Here, that the new header is called a binding indication is merely used as an example, and the specific name of the newly defined HTTP header is not specifically indicated in this embodiment. The eighth message further includes a service set identifier. The service set identifier may be included in at least one field in the URI field in the eighth message, the message body field in the eighth message, the network tag field in the eighth message, or the newly added optional HTTP header field in the eighth message. Specifically, the service set identifier may be located in the URI, the message body, the network tag field, or in the newly added optional HTTP header in the eighth message.

[0339] Before step S1310, the second service instance may receive capability indication information of the first service instance. The capability indication information is used to indicate whether the first service instance supports selecting a service instance from a set of services.

[0340] The second service instance determines, based on the capabilities of the first service instance, binding method indication information corresponding to the session. This avoids the case that message forwarding takes too long when the second message cannot be sent or sent to another unwanted service instance because the second service instance sets the binding method indication information to bind to the service set when the first service instance does not support instance selection. services from a set of services.

[0341] For example, the second service instance is the SMF and the first service instance is the AMF. After the AMF sends a session establishment request to the SMF, the SMF sends a session establishment response message to the AMF. The session establishment response message includes a resource URI, and the resource URI includes the address information of the second service instance. The network tag field in the session establishment response message may include a service set identifier and binding indication information. The session establishment response message may further include another target identifier, such as a service pointer. In this case, the AMF sends the first SMF message. The first message is a session modification request. In this case, the URI in the first message is the same as the resource URI included in the session establishment response message, and the modification request message includes the service set identifier and binding indication information that are included in the session establishment response message.

[0342] In another example, the first service instance is the SMF and the second service instance is the AMF. When the AMF sends a session establishment request to the SMF, the AMF may send an AMF identifier, an indication of a binding relationship, an identifier of the service set to which the AMF belongs, and the like. in SMF. In this case, when the SMF needs to send an AMF message for the session, the SMF uses the AMF ID as a selection parameter and adds the AMF ID to the first message. In addition, the first message carries an indication of the binding relationship and the identifier of the service set to which the AMF belongs.

[0343] The service transfer proxy receives the first message. The second service instance ID is used to indicate a service transfer proxy to send a second message to the second service instance based on the second service instance ID. For example, when the binding method indication information indicates that the user equipment is bound to the second service instance, the second service instance ID information is used to indicate a service transmission proxy to send a second message to the second service instance based on the second service instance ID information. The service transfer proxy may select a service instance from the service set based on the service set identifier. For example, when the binding method indication information indicates that the user equipment is bound to the service set, or when the second service instance is not available, the service handover proxy may select an available service instance from the service set based on the service set identifier, so that the service instance serves the user equipment. .

[0344] Step 1320: determine the service instance corresponding to the target identifier.

[0345] If the binding indication information indicates that the user equipment is bound to the second service instance, the service handover proxy determines that the second service instance is a device for receiving the second message, and performs step 1330. In step 1330, the service handoff proxy sends the second message to the second instance of the service. The target identifier includes, for example, a service pointer and a second service instance identifier.

[0346] If the binding indication information indicates that the user equipment is bound to the second service instance, but the second service instance is not available, the service handover proxy determines the third service instance that is available from the service set to which the second service instance belongs, and executes step 1340 In step 1340, the service handover proxy sends a third message to the third service instance.

[0347] If the user equipment is associated with a service set, the service transfer proxy determines the second service instance from the service set and performs step 1330. For example, if the binding indication information indicates that the user equipment is associated with the service set, the service transfer proxy determines the second service instance of the service set, and performs step 1330. At step 1330, the service transfer proxy sends a second message to the second service instance.

[0348] Step 1330: The service transfer proxy sends a second message.

[0349] It should be understood that the second message may be exactly the same as the first message. In this case, based on the target ID in the first message, the service transfer proxy uses the first message as the second message and directly forwards the first message to the second service instance. Of course, the second message may alternatively be different from the first message. After receiving the first message, the handover proxy may modify the first message, such as changing the header of the first message, but keeping the message body of the first message unchanged in order to receive the second message and send the second message to the second service instance.

[0350] The first message is an HTTP message. If the first service instance receives a resource URI sent by the second service instance, and the Authorized Domain (Authority) field in the resource URI includes address information of the second service instance, such as an IP address or FQDN, namely, includes the identifier of the second service instance , the resource URI is used in the first message URI, in other words, the first message URI includes the resource URI. The handover proxy determines, based on the binding method indication information, whether the user equipment is bound to the second service instance. When the binding method indication information indicates that the user equipment is bound to the second service instance, the service handover proxy sends a second message to the second service instance that has a binding relationship with the target ID. If the first message is an HTTP message, the service transfer proxy sends a second message to the second service instance based on the address of the second service instance in the URI of the first message. The second message may include information about the URI in the first message. In other words, the URI in the second message may be the same as the URI in the first message.

[0351] The first message is an HTTP message. If the first service instance receives a second service instance identifier from the second service instance and the identifier is not present in the resource URI, the first message includes a selection parameter and the selection parameter includes the second service instance identifier. The handover proxy may determine, based on the binding method indication information in the first message, that the user equipment is bound to the second service instance. The service transfer proxy server obtains the address information of the second service instance, such as an IP address or FQDN, based on the identifier of the second service instance. The service transfer proxy sends a second message to the second service instance based on the address information of the second service instance.

[0352] Step 1340: If the URI in the first message includes the address of the second service instance, but the service transfer proxy selects the third service instance in step 1320, after selecting the third service instance, the service transfer proxy keeps the message body of the first message unchanged to get the third message. The third message may include the address of the third service instance. The URI in the third message may include the address of the third instance of the service. In particular, the service transfer proxy may replace the address of the second service instance in the Authorized Domain (Authority) field in the URI in the first message with the address of the third service instance to receive the third message.

[0353] If the selection parameter in the first message includes the identifier of the second service instance, the service transfer proxy may remove the selection parameter in the first message to generate a third message. The message body of the third message may be exactly the same as the message body of the first message. The service transfer proxy may change the header of the first message and write the address of the third service instance to the URI in the third message, and then send the third message to the third service instance.

[0354] FIG. 10 is a schematic diagram of a communication method according to another embodiment of this application.

[0355] In general, in the process of exchanging information, the same service instance provides a service for a session.

[0356] For example, during session establishment, the second service instance sends an establishment message for the first session to the first service instance, the establishment message including an identifier of the second service instance. The first service instance sends another message related to the first session to the second service instance based on the identifier of the second service instance.

[0357] In this case, the second service instance sends a first message to the first service instance, where the session identifier in the first message can be used to uniquely identify the session in the second service instance.

[0358] However, the service instance that provides the service for the first session may fail, be overloaded, and the like. and affect the session.

[0359] In order to solve the above problem, an embodiment of this application provides a communication method.

[0360] The first service instance may be one of an SMF and a user plane function (UPF) network element. The second service instance may be different in SMF and UPF. The third service instance, the fourth service instance, and the second service instance are network elements having the same function.

[0361] Step 1410: The first service instance receives the first message sent by the third service instance or the fourth service instance, the first message including the target identifier.

[0362] The first service instance determines the second service instance based on the target identifier, and the second service instance is used to provide the service for the first session. In other words, the first service instance determines, based on the target identifier, the second service instance to provide the service for the first session.

[0363] Step 1420: The first service instance sends a second message to the second service instance.

[0364] The first message refers to the first session. The second message refers to the first session. The first message includes the identifier of the first session. The target ID and the first session ID may be located in the same field or in different fields. The session identifier may be used to uniquely identify a session within the target set of services. The second service instance, the third service instance, and the fourth service instance may be service instances in the target service set. In other words, each session served by a set of services corresponds to one session ID. When the first service instance is a UPF, and the third service instance and the fourth service instance are SMF instances, the fully qualified stream endpoint identifier (F-SEID) field in the first message may include a target identifier or identifier. The Node ID in the first message may include the target ID, or the target ID may be located in a different field in the first message. This is not limited in this embodiment of the present application.

[0365] The first session is associated with a service instance, or the first session is associated with a set of services.

[0366] The second service instance, the third service instance, and the fourth service instance are network elements that can provide the same service. For example, both the third service instance and the fourth service instance are AMF or SMF.

[0367] The second message refers to the first session. The second service instance is used to provide the service for the first session. The second message may be used to request a second service instance to provide a service for the first session.

[0368] The first message includes a target identifier. The first session is tied to a third service instance, or tied to a target set of services. The target service set includes a second service instance and a third service instance. The target service set may further include a fourth service instance.

[0369] The first session is associated with a service instance. In this case, the service instance provides the service for the first session. When a service instance is not available, another service instance in the service set to which this service instance belongs must provide the service for the first session. If the first session is bound to the third service instance when the third service instance is unavailable, the first service instance selects the second service instance from the target service set and sends a second message to the second service instance. Optionally, in an implementation, if the target identifier includes a service instance identifier, the first session is bound to the service instance.

[0370] The first session is associated with a set of services. In this case, the service instance in the service set provides the service for the first session. The first service instance specifies that the service instance in the service set is to provide the service for the first session. The first service instance defines a service instance from the service set.

[0371] In an implementation, each service instance in the target service set may provide a service for the first session. For example, prior to step 1410, the third service instance provides a service for the first session, and another service instance in the target service set may obtain a context that is related to the first session and held by the third service instance to provide the service for the first session.

[0372] Optionally, the target identifier may include the identifier of the first session group. The first session group ID is used to identify the session group. The first session group includes one or more sessions in the service set. The first session group includes the first session.

[0373] The session group identifier may be used to identify a unique session group within a service set. The first service instance may determine a second service instance from the target service set based on the first session group ID and the target service set ID.

[0374] Alternatively, the session group identifier may be used to identify a unique session group in the service set that communicates with the first service instance. The first service instance may determine a second service instance from the target service set based on the first session group ID.

[0375] In other words, the session group identifier may be a global identifier or may be an identifier in a service set.

[0376] A session can be classified into a session group by configuration. For example, when a first session establishment is requested, the service instance (eg, the third service instance) that sends the session establishment request or the service instance that sends the session modification request may configure the first session as a session in the first session group.

[0377] If the target identifier includes a plurality of identifiers in a session group identifier, a third service instance identifier, and a target service set identifier, the plurality of identifiers may be encoded as one uniform identifier. For example, multiple identifiers are encoded as a single FQDN and a single FQDN is used as the target identifier. Alternatively, a plurality of identifiers may be respectively located in different fields in the first message. This is not limited in this embodiment of the present application.

[0378] Optionally, the first message includes binding method indication information. The binding method indication information is used to indicate that the first session is bound to a service instance or that the first session is bound to a service set.

[0379] Optionally, the binding method indication information may be used as a new parameter in the first message. Specifically, the binding indication information may be located in the newly added field in the first message. For example, when a session is created, the third service instance adds an optional field to the session creation request to send binding method information. One or more new data type fields may be defined. One or more fields of the new data types are used to carry information about specifying the binding method. The binding method indication information may alternatively be located in an existing field in the first message.

[0380] Alternatively, the binding method may be implicitly specified. When the target identifier includes the identifier of the third service instance, it indicates that the binding method is that the first session is bound to the third service instance. When the target identifier does not include the service instance identifier, for example, the target identifier includes only the target service set identifier, or the target identifier includes the service set identifier and the first session group identifier, or the target identifier includes the first session group identifier, it indicates that the binding method is that the first session is bound to a set of services.

[0381] Optionally, the target identifier may include a target service set identifier. The service set identifier may be located in a fully qualified stream endpoint identifier (F-SEID). Optionally, the service set identifier may optionally be used as a new parameter in the first message. For example, when a session is created, the second service instance adds an optional field to the session creation request to send the service set identifier. One or more new data type fields may be defined. One or more fields of the new data types are used to carry the service set identifier. In this embodiment, this is not limited.

[0382] Optionally, before step 1410, the first service instance may send capability indication information to one or more service instances in the target service set, such as the third or fourth service instance or each service instance.

[0383] A service instance in the target service set, e.g., a second service instance, can determine, based on the capability indication information, whether the first service instance supports load balancing based on the service set, and specifically, whether the first service instance supports selecting a service instance from the set services to provide the service for the first session.

[0384] The third service instance or the fourth service instance receives capability indication information sent by the first service instance. If the capability indication information indicates that the first service instance supports service set-based load balancing, the first message sent by the third service instance or the fourth service instance may include binding relation indication information. The binding relationship indication information indicates that the first session is bound to the service set. Alternatively, the first message implicitly indicates that the first session is bound to a set of services. For example, the first service instance is the UPF, the second service instance, the third service instance, and the fourth service instance are the SMF, and the capability indication information is used to indicate that the UPF supports load balancing based on a set of SMFs.

[0385] In some embodiments, when supporting load balancing that is based on a service set, the first service instance may send capability indication information to all or some of the service instances in the target service set, e.g., a service instance that communicates with the first service instance, wherein the capability indication information is used to indicate that the first service instance supports load balancing based on the service set. When the first service instance does not support service set-based load balancing, the first service instance does not send capability indication information. For example, if UPF does not support the above capability, UPF may not send capability indication information.

[0386] If an instance in the target service set, e.g., the second service instance, does not receive the capability indication information of the first service instance, then the instance in the target service set determines that the first service instance does not support load balancing that is based on the service set.

[0387] In other words, an instance in the target service set determines, based on whether the capability indication information is received, whether the first service instance supports selecting a service instance from the service set.

[0388] In some other embodiments, if an instance in the target service set, such as a third service instance, receives the capability indication information of the first service instance, the capability indication information is used to indicate whether the first service instance supports load balancing, which is based on the service set, an instance in the target service set, eg, the third service instance, determines based on the capability indication information content whether the first service instance supports load balancing based on the service set.

[0389] If the first service instance does not support selecting another service instance from the set of services to which the third service instance belongs, the first message related to the first session and sent by the third service instance or the fourth service instance to the first service instance includes the identifier of the third service instance.

[0390] The fact that the first service instance does not support selecting another service instance from the service set to which the third service instance belongs also means that the first service instance can only receive a response message sent by the service instance (i.e., the third service instance), to which the first session is attached. For example, the first service instance sends a request message to a third service instance, wherein the request message includes an identifier of the third service instance, and the first service instance does not support receiving a response message from a service instance other than the third service instance.

[0391] If the first service instance does not support selecting another service instance from the service set, the third service instance or the fourth service instance may set the binding relation indication information corresponding to the session to bind to the service instance (e.g., bind to the third service instance). The third service instance or the fourth service instance may send binding relation indication information to another control plane service instance such that the other control plane service instance sends a session related message to the third service instance. This avoids the case where the message is redirected relatively many times between the third service instance and the fourth service instance because the first service instance selects the third service instance and the other control plane service instance selects another service instance, such as the fourth service instance.

[0392] For example, during the exchange of information between the third service instance, for example, SMF 1, and the first service instance, for example, UPF, because UPF does not support selecting SMF 2 from the SMF set, to provide a service for a session corresponding to the user equipment, if the SMF 1 sets the anchor relationship indication information to bind to the SMF set, the anchor relationship indication information corresponding to the session when the uplink message related to the session (for example, the user equipment initiates a modification session, in which case the AMF sends the corresponding uplink message connection) and a session-related downlink message (e.g., UPF receives downlink data and initiates paging, in which case UPF sends the corresponding downlink message) are simultaneously triggered if the AMF that sends the uplink message selects SMF 2 and UPF sends a message downlink message in SMF 1, the downlink message sent by UPF must be sent to SMF 2 to be processed by SMF 2. However, UPF does not support receiving a response message from SMF 2. Therefore, UPF considers that UPF cannot send the message downlink in SMF. In this case, if SMF 1 determines, based on the fact that UPF does not support selecting a service instance from a service set, that the session is bound to SMF 1, and indicates in a message to be sent to the AMF that the session is bound to SMF 1, The AMF selects SMF 1 when sending the uplink message but does not select SMF 2 to avoid the above problem.

[0393] When the first service instance does not support load balancing based on the service set, if the third service instance is unavailable, the second service instance sends a session update message to the first service instance. The session update message is used to indicate to the first service instance that the service instance providing the service for the first session has changed from the third service instance to the second service instance. The session update message includes the identifier of the second service instance.

[0394] For example, a second service instance, such as SMF 1, communicates with a first service instance, such as UPF. UPF does not support selecting SMF 2 from the set of SMFs to provide a service for a session corresponding to the user equipment. If SMF 1 is not available and SMF 2 subsequently provides the service for the first session, SMF 2 sends a session update message to UPF to indicate to UPF to determine that the service instance providing the service for the first session has changed from SMF 1 to SMF 2. In an implementation, when SMF 2 determines that SMF 1 is unavailable, SMF 2 sends session update messages to UPF corresponding to all sessions for which SMF 1 provides services, or sends session update messages to UPF corresponding to all sessions for which SMF 1 provides services, and SMF 2 provides backup.

[0395] Optionally, the first service instance may alternatively register with the NRF whether the first service instance has the ability to support selecting a service instance from a service set for the second service instance to receive from the NRF whether the first service instance supports load balancing based on the service set . The second service instance may receive the capability indication information sent by the NRF. The capability indication information indicates whether the first service instance supports selecting a service instance from a service set, in other words, whether the first service instance has the ability to select a service instance from a service set.

[0396] In other words, the third service instance may receive the capability indication information sent by the first service instance or receive the capability indication information sent by the NRF. The capability indication information indicates whether the first service instance supports selecting a service instance from a set of services.

[0397] Optionally, the third service instance may alternatively determine, based on the capabilities of the third service instance and/or the session attribute, the binding indication information corresponding to the first session. If the third service instance does not support service set load balancing or, in some cases, does not support service set load balancing, the first session is bound to the third service instance. For example, if the third service instance is in communication with a fourth generation (i.e., 4G) mobile communication system, the third service instance sets the binding indication information for binding to the service instance (namely, binding to the third service instance), where the binding indication information corresponds to a session, for which the third service instance provides the service. Alternatively, the third service instance determines, based on whether the session supports transition to the LTE system, the binding indication information corresponding to the session. For example, if the session supports transition to the LTE system, the third service instance sets the anchor indication information to bind to the service instance, the anchor indication information corresponding to the session.

[0398] The third service instance may determine, based on the capability indication information of the first service instance, the binding method corresponding to the session. The third service instance may determine the binding method indication information based on the capability indication information of the first service instance.

[0399] The binding method indication information may further indicate that the session is bound to a third service instance or bound to a service set to which the third service instance belongs.

[0400] If the first service instance does not support selecting a service instance from the service set, the binding method indication information indicates that the session is bound to the third service instance.

[0401] If the first service instance is capable of supporting selecting a service instance from a service set, the binding method indication information may indicate that the first session that requires the first service instance to provide the service is bound to the third service instance or bound to the service set , which includes the third instance of the service. The service set including the third service instance is the service set to which the third service instance belongs.

[0402] Alternatively, the third service instance may determine, based on the capabilities of the third service instance and/or the session attribute, the binding method corresponding to the session.

[0403] The third service instance does not support selecting a service instance from a set of services, or the third service instance determines that a session that requires a third service instance to provide the service is associated with the third service instance. For example, if the third service instance supports the LTE system, when the third service instance provides a service through the LTE system, because the LTE system does not support selection of the service instance from the service set, the third service instance does not support the selection of the service instance from the service set. Therefore, that the third service instance supports the LTE system can be considered as that the third service instance does not support selecting a service instance from a set of services.

[0404] If the first session supports the service instance for providing the service via the LTE system, when the first session is provided with the service instance service via the LTE system, in other words, when the first session is transferred to the LTE system, if the LTE system does not support selecting the service instance from the service set , the service instance that provides the service for the first session cannot select the service instance from the service set. Therefore, the fact that the first session supports the service instance for providing the service via the LTE system can be considered as that the third service instance does not support the selection of the service instance from the service set. The third service instance may determine, based on the session attribute, binding method indication information corresponding to the session.

[0405] The third service instance or the fourth service instance may send binding relation indication information to another control plane service instance, such that the other control plane service instance sends a session related message to the third service instance. This avoids the case where message redirection is performed relatively many times between the third service instance and the fourth service instance because the first service instance selects the third service instance and the other control plane service instance selects another service instance, such as the fourth service instance.

[0406] The first session is associated with the third instance of the service. If a third service instance is not available, the first service instance selects the second service instance. The first service instance may determine the target service set identifier and select the second service instance from the target service set. The first service instance determines the target service set identifier based on the target identifier. In an implementation, the target identifier includes the target service set identifier, and the first service instance obtains the target service set identifier from the target identifier. In another implementation, the target identifier includes a third service instance identifier, and the first service instance determines the target service set identifier based on the third service instance identifier and the correspondence between the target service set identifier and the third service instance identifier received from the service instance in the target service set.

[0407] The first service instance may send the identifier of the target service set to the NRF, and the NRF sends the identifiers of the available service instances in the target service set to the first service instance. The first service instance selects the second service instance from the available service instances in the target service set.

[0408] An NRF network element may store a mapping between a set of services and one or more service instances.

[0409] The first service instance may send the target service set identifier to the NRF network element. The NRF network element may define one service instance in the target service set as the second service instance based on the target service set identifier and the mapping between the target service set and one or more service instances. The second service instance is the available service instance.

[0410] If the third service instance is unavailable, the first service instance may send the identifier of the third service instance to the NRF network element, and the NRF network element may determine, based on the identifier of the third service instance, the target service set to which the third service instance belongs. The NRF network element may determine the available service instances in the target service set based on the target service set identifier. Available service instances include a second service instance.

[0411] If the target identifier includes a first session group identifier, the first service instance receives the first session group identifier, and the first service instance may determine the second service instance based on the first session group identifier. There is a correspondence between the first session group and the second service instance. Specifically, the second service instance provides a service for a session in the first session group. The first service instance may further determine the second service instance based on the first session group ID and the target service set ID.

[0412] The first service instance may store a mapping between the first session group and the second service instance. The first service instance may determine the second service instance based on the identifier of the first session group and the correspondence between the first session group and the second service instance.

[0413] The NRF network element may store a mapping between the first session group and the second service instance. Specifically, the second service instance provides a service for a session in the first session group. The first service instance may send the first session group identifier to the NRF network element. The NRF network element may determine the second service instance based on the mapping between the first session group and the second service instance. The NRF network element may send the identifier of the second service instance to the first service instance. In other words, the first service instance sends the identifier of the first session group to the NRF network element; and the first service instance receives the identifier of the second service instance, which is sent by the NRF network element, to determine the second service instance.

[0414] In addition, if the first service instance receives the first session group ID and the target service set ID, the first service instance sends the first session group ID and the target service set ID to the NRF network element, so that the NRF selects from the target service set based on the first service set ID. session group the second instance of the service corresponding to the first session group.

[0415] In another implementation, the first service instance may alternatively select the second service instance based on a locally obtained mapping relationship between the target service set and the service instance.

[0416] The first service instance may store a mapping between the service set and one or more service instances. The first service instance may identify one service instance in the target service set as the second service instance based on the target service set identifier and the mapping between the target service set and one or more service instances. The target service set includes one or more service instances.

[0417] Optionally, before step 1410, the first service instance may receive first information sent by the service instance in the target service set, where the first information includes a service instance identifier and a target service set identifier, and the first information may indicate a correspondence between the service instance and the target a set of services. The first service instance obtains a target service set identifier based on the target identifier. The first service instance determines the second service instance based on the target service set identifier. In other words, the first service instance may determine the second service instance based on the target service set identifier and the correspondence between the service instance and the target service set.

[0418] The first service instance may receive a target service set identifier and a service instance identifier that are sent by a service instance in the target service set. Specifically, the first service instance may determine the correspondence between the target service set and the service instance based on the received message; and the first service instance may determine the second service instance of the target service set based on the received target service set identifier.

[0419] The first service instance may receive identifiers sent by one service instance in the service set, all or some of the service instances in the service set to which the service instance belongs, and the service set identifier. Specifically, the first information may include a target service set identifier and service instance plural identifiers. A service instance set is all or some of the service instances in the target service set.

[0420] Optionally, when the plurality of service instances are some service instances in the target service set, the first service instance may receive first information sent by the plurality of service instances to obtain an identifier of each service instance in the target service set. The first service instance may determine a mapping between each of the plurality of service instances in the service set and the service set based on the first information sent by each of the plurality of service instances.

[0421] Alternatively, the first service instance may receive first information sent by each service instance in one service set, the first information including a service instance identifier and a service set identifier. The first service instance may derive a mapping between each service instance in the service set and the service set based on the first information sent by each service instance in the service set.

[0422] The first service instance may receive an identifier of each of one or more service instances in the target service set and an identifier of the target service set to which one or more service instances belong, wherein the identifier of each of the one or more service instances in the target service set and the identifier of the target set of services are sent by the service instance. The plurality of service instances includes a second service instance. The first service instance may store a mapping between the target service set and one or more service instances. When one service instance belongs to a plurality of service sets, the first service instance receives a service instance identifier and identifiers of the plurality of service sets to which the service instance belongs.

[0423] It should be understood that the first service instance may receive from each of one or more service instances in the service set a service set identifier and a service instance identifier. Specifically, each service instance in the target service set sends a service instance identifier and a target service set identifier to the first service instance. The first service instance receives a first service set identifier and a second service instance identifier which are sent by the second service instance, the first service set including the second service instance. The first service instance receives a first service set identifier and a third service instance identifier which are sent by the third service instance, the first service set including the third service instance. The first service set may be a target service set.

[0424] The first service instance may determine the correspondence between each service instance and the service set based on the received identifier of each service instance and the identifier of the service set to which the service instance belongs to determine the service instance in the service set. The first service instance determines the second service instance from the target service set based on the correspondence between the service instance and the service set and the target service set to which the third service instance belongs, and sends a second message to the second service instance. The second service instance is used to provide the service for the first session. The third service instance sends to the first service instance, using the first message, the identifier of the target service set to which the third service instance belongs. Alternatively, the first service instance determines, based on the identifier of the third service instance in the target identifier and the received mapping between the third service instance and the service set, the target service set corresponding to the third service instance.

[0425] For example, when the first service instance establishes a connection between the network element with the service instance in the service set to which the second service instance belongs, the service instance in the service set to which the second service instance belongs sends the identifier of the service set to which the second service instance belongs. , and the service instance identifier for the first service instance. For example, when establishing a connection between a network element with a first service instance, the second service instance sends the identifier of the service set to which the second service instance belongs and the identifier of the second service instance to the first service instance. Thus, the first service instance may establish a mapping relationship between the set and all service instances included in the set. For example, the SMF Set includes SMF 1, SMF 2, and SMF 3. When link N4 is established with the UPF, SMF 1 sends the SMF Set ID and SMF ID 1 to the UPF. When link N4 is established with the UPF, SMF 2 sends the SMF Set ID and SMF ID 2 to the UPF. When link N4 is established with the UPF, SMF 3 sends the SMF Set ID and SMF ID 3 to the UPF. Thus, UPF can establish the following association: (SMF Set ID, SMF ID 1, SMF ID 2, SMF ID 3). Specifically, UPF establishes a mapping relationship between the SMF Set ID and SMF 1, between the SMF Set ID and SMF 2, and between the SMF Set ID and SMF 3. When SMF 1 fails, UPF may choose from the SMF Set based on the SMF Set ID , SMF 2 or SMF 3 as the second service instance to provide the service for the first session. Based on the SMF ID 1, the UPF may determine the SMF ID corresponding to SMF 1 and select SMF 2 or SMF 3 from the SMF as the second service instance.

[0426] When establishing communication between the network element with each service instance, the first service instance can obtain from the service instance the identifier of the service set to which this service instance belongs, and the identifier of the service instance. For example, when the first service instance is the UPF and the target service set is the SMF set, establishing an gateway means establishing an N4 association.

[0427] When the first service instance obtains the target service set identifier corresponding to the first session during session establishment, the target service set is the service set to which the second service instance belongs. The first service instance receives one or more identifiers of one or more service instances included in the target service set. The first service instance may select one service instance in the target service set as the second service instance to provide the service for the first session.

[0428] During registration of a service instance, the service instance may also register the identifier of the target service set to which the service instance belongs to the NRF network element. Each service instance in the target service set may send the service instance identifier and the target service set identifier to the NRF network element. The NRF network element determines the mapping between the target service set and each service instance based on the service instance ID and the target service set ID that are sent by the service instance. Specifically, the NRF network element defines a service instance included in the target service set.

[0429] The first service instance sends the target service set identifier to the NRF network element. The NRF network element defines one service instance in the target service set as the second service instance based on the mapping between the target service set and the service instance. The NRF network element sends the identifier of the second service instance to the first service instance.

[0430] The first service instance may obtain a target service set identifier based on the target identifier.

[0431] The first service instance may obtain the target service set identifier from the target identifier in the first message. Specifically, the target identifier includes the target service set identifier, and the first service instance may obtain the target service set identifier.

[0432] When the target identifier includes the identifier of the third service instance, the first service instance may obtain the identifier of the target service set based on the identifier of the third service instance. The first service instance may determine the target service set identifier based on the third service instance identifier and the correspondence between the third service instance identifier and the target service set identifier, and which may be received by the first service instance from the service instance in the target service set, e.g., sent by the third service instance to the first service instance during N4 association establishment or sent by another service instance in the target service set to the first service instance.

[0433] For example, in a process in which the third service instance establishes a connection between the network element with the first service instance, the third service instance sends the target service set identifier and the third service instance identifier to the first service instance. Alternatively, the first service instance sends the identifier of the third service instance to the NRF network element, and the NRF network element sends the target service set identifier to the first service instance.

[0434] Optionally, the first service instance sends the identifier of the third service instance to the NRF network element, and the NRF network element determines the target service set corresponding to the third service instance.

[0435] In one set of services, one or more service instances may provide backup for another service instance.

[0436] Optionally, before step 1410, the first service instance receives a third message sent by the second service instance or the third service instance.

[0437] The third message may include backup indication information, and the backup indication information is used to indicate that the second service instance is the service instance used to provide backup for the third service instance. Alternatively, the third message may indicate that the second service instance is a service instance used to provide backup for the first session group for which the third service instance provides a service. In other words, the second service instance provides backup for the third service instance, or the second service instance provides backup for the first session group for which the third service instance provides a service. When the third service instance is unavailable, the first service instance determines, based on the backup indication information and the target ID, that the second service instance is to provide the service for the first session.

[0438] For example, service instance 1 sends a third message to the first service instance. The third message is used to indicate that service instance 2 is a service instance used to provide backup for service instance 1. The third message may include a service instance 1 identifier and a service instance 2 identifier. At the first moment, service instance 1 provides the service for the first session, and service instance 2 provides the backup for the first session.

[0439] When service instance 1 is not available, the first service instance determines service instance 2 as the second service instance and sends a second message to service instance 1. In other words, service instance 2 provides the service for the first session at the second instant.

[0440] In this case, the sessions for which the service instance 2 provides a backup may be all sessions for which the service instance 1 provides a service.

[0441] When the service instance providing the service for the session is unavailable, the service instance providing the backup for the session starts to provide the service for the session. A service instance that provides session backup does not need to obtain a session context from another network element. This reduces the delay.

[0442] Service instance 1 sends a third message to the first service instance. The third message is used to indicate that service instance 2 is a service instance used to provide backup for the first session group corresponding to service instance 1. The third message may include a service instance 1 identifier, a service instance 2 identifier, and a first session group identifier. The first session group includes the first session. At the first moment, service instance 1 provides a service for the first session group, and service instance 2 provides a backup for the first session group. In other words, service instance 2 may be associated with a session group for which second service instance 1 provides a service. In an implementation, the third message is a communication message between network elements. For example, when the first service instance is a UPF and the target service set is an SMF set, the third message is an N4 association establishment or update message.

[0443] In another implementation, the third service instance may send the backup service instance identifier to the first service instance using the first message. When the third service instance is unavailable, the first service instance determines, based on the backup service instance ID in the first message, that the backup service instance is the second service instance. The first service instance sends a second message to the second service instance. The backup service instance identifier may be the IP address of the backup service instance.

[0444] The first message may include one or more identifiers of one or more backup service instances corresponding to the third service instance. The target service set may include one or more backup service instances. In particular, the backup service instance corresponding to the ID of each backup service instance can be understood as the service instance in the service set to which the third service instance belongs. In other words, the target service set includes one or more backup service instances and a third service instance. The first message may include one or more identifiers of one or more backup service instances. Specifically, the first message may include one or more identifiers of one or more service instances in the target service set.

[0445] Optionally, the backup service instance is associated with a group of sessions for which the second service instance provides a service, or is associated with all sessions for which the second service instance provides a service. When the backup service instance is associated with a group of sessions, the first message may further include identifiers of the session group associated with the backup service instance.

[0446] Optionally, before step 1410, the first service instance may further receive an identifier that refers to each service instance in the target service set and that is sent by the service instance, a session group identifier for which this service instance provides a service, and a session group identifier, for which the service instance provides a backup.

[0447] The first service instance may determine, based on the session group to which the first session belongs, that the service instance that provides backup for the session group is the second service instance.

[0448] For example, when a service instance in a service set is registered with the NRF, that service instance may further carry one or more identifiers of one or more session groups for which the service instance provides a backup service. For example, Service Instance 1 provides a service for Session Group 1 and provides backup for Session Group 2. In this case, the message sent by Service Instance 1 to the first Service Instance includes a set identifier corresponding to Service Instance 1, a Service Instance 1 identifier, an identifier session group 1 for which service instance 1 provides the service and the identifier of the session group 2 for which service instance 1 provides backup. Similarly, Service Instance 2 provides a service for Session Group 2 and provides backup for Session Group 1. In this case, the message sent by Service Instance 2 to the first Service Instance includes a set ID corresponding to Service Instance 2, a Service Instance 2 ID, the identifier of the session group 2 for which the service instance 2 provides a service, and the identifier of the session group 1 for which the service instance 2 provides a backup. In this case, the first service instance determines the second service instance based on the target service set and the ID of the session group corresponding to the session. For example, session group corresponds to session group 1, and when service instance 1 is unavailable, the first service instance determines based on the ID of session group 1 that service instance 2 provides backup for session group, and therefore selects service instance 2 as the second service instance.

[0449] Optionally, during service instance registration, the service instance may alternatively register with the NRF network element the ID of the target service set to which the service instance belongs and the ID of the session group that the service instance is backing up.

[0450] The first service instance sends the first session group ID to the NRF. Based on the ID of the first session group, the NRF determines the ID of the second service instance that provides the backup for the first session group. The NRF may send the identifier of the second service instance to the first service instance.

[0451] The second message may include a message body, wherein the message body includes a parameter related to the first session. The second message may be used to indicate a second service instance to provide the service for the first session.

[0452] The second message may be a request message sent by the first service instance to the second service instance. For example, the first service instance is a UPF NE, the second service instance is an SMF NE. The second message may be used by the first service instance to send a downlink data notification to the second service instance.

[0453] The second message may include a second service instance identifier.

[0454] The identifier of the second service instance may be located in the fully qualified stream endpoint identifier (F-SEID) field in the second message.

[0455] Alternatively, the target identifier may be used as a new parameter. For example, when a session is created, the second service instance adds an optional field to the session creation request to send the target ID. One or more new data type fields may be defined. One or more fields of the new data types are used to carry the target identifier. The plurality of identifiers included in the target identifier may be carried in the same field or in different fields.

[0456] For example, the F-SEID field in the first message includes the service instance 1 identifier, and the service instance 1 identifier may be, for example, the IP address of the service instance 1. If service instance 1 is not available, the first service instance designates service instance 2 as the second service instance. The F-SEID field in the second message may include a service instance 2 identifier. The F-SEID field in the second message does not include the Service 1 Instance 1 ID.

[0457] If the first service instance is a UPF, the second message may include a first session identifier. The ID of the first session and the second message is determined based on the ID of the first session and the first message. For example, the first session ID in the second message is the same as the first session ID and the first message. The session identifier may be used to identify the session within the service set.

[0458] An embodiment of this application provides a communication method. The communication method includes: the third service instance sends a first message related to the first session to the first service instance, the first message includes a target identifier, the target identifier is used to indicate the first service instance to determine the second service instance, and the second service instance used to provide the service for the first session.

[0459] Optionally, the first message includes binding method indication information, the binding method indication information is used to indicate binding of the first session to a third service instance or binding of the first session to a target service set, and the target service set includes a second service instance and a third service instance.

[0460] Optionally, the target identifier includes the identifier of the third service instance.

[0461] Optionally, the third service instance receives capability indication information sent by the first service instance or network element NRF of the network repository function. The capability indication information is used to indicate that the first service instance supports load balancing based on the target service set, and the target service set includes the second service instance and the third service instance.

[0462] Optionally, the third service instance sends the target service set identifier and the third service instance identifier to the first service instance, the target service set including the second service instance and the third service instance.

[0463] Optionally, the third service instance sends backup indication information to the first service instance, wherein the backup indication information is used to indicate the second service instance to provide backup for the third service instance or to provide backup for the first session group for which the second service instance provides the service, and the first session group includes the first session.

[0464] FIG. 11 is a schematic structural diagram of a handover proxy 900 according to an embodiment of this application. The handover proxy 900 in FIG. 11 may be configured to perform the steps performed by the handover proxy server in the methods of FIG. 3 - fig. 8. The service transfer proxy 900 includes a send block 910 and a receive block 920. Optionally, the service transfer proxy 900 may further include a processing unit 930 . The functions of the service transfer proxy 900 modules are described in detail below.

[0465] The receiving unit 920 is configured to receive the first message sent by the first instance of the service, the first message including the target identifier. The sender 910 is configured to send, based on the first message, a second message to a second service instance that has a binding relationship with the target ID.

[0466] Optionally, the processing unit 930 is configured to: in the absence of a service instance related to the binding to the target identifier, obtain the target service set identifier based on the first message. The processing unit 930 is further configured to select a third service instance from the target service set based on the target service set identifier. The sender 910 is further configured to send a third message to a third service instance based on the first message.

[0467] Optionally, the processing unit 930 is further configured to obtain the target service set identifier from the first message, the first message further including the target service set identifier. Alternatively, the processing unit 930 is further configured to derive the target service set identifier from the target identifier in the first message, the target identifier including the target service set identifier. Alternatively, the processing unit 930 is further configured to determine the service set identifier as the target service set identifier, wherein the service set identifier has a mapping relationship with the target identifier in the first message.

[0468] Optionally, the receiving unit 920 is further configured to receive a fourth message sent by the second service instance, and the processing unit 930 is further configured to establish a binding relationship between the target identifier and the second service instance based on the first message.

[0469] Optionally, the fourth message is a message related to the user equipment, or the fourth message is a dedicated Binding Request message.

[0470] Optionally, the fourth message carries at least one of a binding indication and a binding timer. The binding timer is used to release the binding relationship between the target identifier and the second service instance after the binding timer has expired.

[0471] Optionally, the fourth message contains the target identifier.

[0472] Optionally, the processing unit 930 is further configured to assign a target identifier after receiving the fourth message sent by the second instance of the service.

[0473] Optionally, the processing unit 930 is further configured to add a target identifier to the fourth message when the fourth message is a user equipment related message.

[0474] Optionally, the receiving unit 920 is further configured to: receive an unbind request sent by the second service instance, wherein the unbind request is used to request to release the binding relationship between the target identifier and the second service instance; or starting the binding timer and releasing the binding relationship between the target identifier and the second service instance after the binding timer expires.

[0475] Optionally, the target identifier refers to a single user equipment or group of user equipment.

[0476] Optionally, the target identifier is one of the service indicators configured for the second service instance. The receiving block 920 is further configured to receive a registration request from the second service instance. The sender 910 is further configured to send a registration response to the second service instance, the registration response including the service pointer configured for the second service instance.

[0477] Optionally, the registration request includes the number of service indicators applied by the second service instance. The processing unit 930 is further configured to configure a service indicator for the second service instance based on the number of service indicators that are requested by the second service instance.

[0478] Optionally, the processing unit 930 is further configured to configure a service indicator for the second service instance based on the capacity of the second service instance.

[0479] Optionally, the processing unit 930 is further configured to determine the service set to which the second service instance belongs. The processing unit 930 is further configured to configure a service indicator for the second service instance such that the service indicator corresponding to the second service instance is different from the service indicator corresponding to another service instance in the service set.

[0480] Optionally, the target identifier is one of the service indicators configured for the second service instance. The receiving unit 920 is further configured to receive a registration request from a second service instance, where the registration request includes a service pointer corresponding to the second service instance, such that the service handover proxy associates the second service instance with the service pointer.

[0481] Optionally, the processing unit 930 is further configured to: when the service indicator corresponding to the second service instance conflicts with the service indicator corresponding to another service instance in the service set to which the second service instance belongs, reconfiguring (reconfiguring) the service indicator for the second service instance services. The sender 910 is further configured to send a registration response to the second service instance, the registration response including the service pointer reconfigured for the second service instance.

[0482] Optionally, the first message is a Hypertext Transfer Protocol HTTP message, and the target ID is in the HTTP message header.

[0483] FIG. 12 is a schematic structural diagram of a service instance 1000 according to an embodiment of this application. Service instance 1000 in FIG. 12 may be configured to perform the steps performed by the second service instance in the methods of FIG. 3 - fig. 8. The service instance 1000 includes a send block 1010 and a receive block 1020. Optionally, service instance 1000 in FIG. 12 may further include a processing unit 1030. The functions of the modules of the service instance 1000 are described in detail below.

[0484] The sender 1010 is configured to send a fourth message to the service handover proxy, the fourth message being used to initiate the handover proxy to establish a binding relationship between the second service instance and the target ID, and the target ID is related to the user equipment. The receiving unit 1020 is configured to receive a second message sent by the service transfer proxy, the second message including the target identifier.

[0485] Optionally, the fourth message is a message related to the user equipment, or the fourth message is a dedicated binding request.

[0486] Optionally, the fourth message includes at least one of a target identifier and an association timer.

[0487] Optionally, sender 1010 is further configured to send the target identifier to the first service instance.

[0488] Optionally, the processing unit is further configured to insert the target identifier in the fourth message to send the target identifier to the first service instance.

[0489] Optionally, the sender 1010 is further configured to send a debinding request to the service transfer proxy. The unbind request is used to request to release the binding relationship between the target identifier and the second service instance.

[0490] Optionally, the target identifier refers to a single user equipment or group of user equipment.

[0491] Optionally, the target identifier is one of the service indicators configured for the second service instance. The sender 1010 is further configured to send a registration request to the service transfer proxy server. The receiving unit 1020 is further configured to receive a registration response sent by the service handover proxy, the registration response including a service indicator configured for the second service instance.

[0492] Optionally, the registration request includes the number of service indicators applied by the second service instance.

[0493] Optionally, the sender 1010 is further configured to send a registration request to the service transfer proxy, the registration request including a service pointer configured by the second service instance for the second service instance.

[0494] Optionally, the first message is a Hypertext Transfer Protocol HTTP message, and the target ID is in the HTTP message header.

[0495] Optionally, service instance 1000 may further include a processing unit 1030. The processing unit is configured to process the message received by the receiving unit 1010.

[0496] The service instance 1000 may further perform the steps performed by the first service instance in the methods of FIG. 3 - fig. 8. The service instance 1000 receiving unit 1020 is configured to receive a target identifier that is related to the user equipment and the second service instance. The sender 1010 adds a target identifier to a message that relates to the user equipment and the second service instance, and then sends the message, the target identifier being used to send the message to the second service instance.

[0497] Optionally, the receiving block 1020 is configured to receive a target identifier.

[0498] Optionally, the receiving unit is configured to receive a target identifier from the service transfer proxy related to the second service instance.

[0499] FIG. 13 is a schematic structural diagram of a handover proxy 1100 according to another embodiment of this application. The handover proxy 1100 includes a processor 1110 and a transceiver 1120.

[0500] The processor 1110 and the transceiver 1120 communicate with each other via an internal connection scheme. The processor 1110 is configured to execute an instruction to control the transceiver 1120 to send a signal and/or receive a signal. Optionally, handoff proxy 1110 may further include memory 1130. Processor 1110, transceiver 1120, and memory 1130 communicate with each other via an internal connection path. The memory 1130 is configured to store an instruction. The processor 1110 is configured to execute an instruction stored in the memory 1130 to control the transceiver 1120 to send a signal and/or receive a signal. It should be understood that transceiver 1120 may provide the same functionality as sender 910 and receive 920 in FIG. 11. Processor 1110 and memory 1130 may provide the same functions as processing unit 930 in FIG. eleven.

[0501] The transceiver 1120 is configured to receive the first message sent by the first service instance, the first message including the target identifier. Processor 1110 is configured to determine if a service instance exists corresponding to the target identifier. When processor 1110 finds a second service instance that matches the target identifier, transceiver 1120 is further configured to send, based on the first message, a second message to the second service instance that has a binding relationship with the target identifier.

[0502] FIG. 14 is a schematic structural diagram of a service instance 1200 according to another embodiment of this application. Service instance 1200 may perform the steps of the methods in FIG. 3 - fig. 8. Service instance 1200 includes a transceiver 1220. Transceiver 1220 is configured to receive/send a signal. Optionally, service instance 1200 may further include processor 1210. Processor 1210 and transceiver 1220 communicate with each other via an internal connection path. The processor 1210 is configured to control the transceiver 1220 to send/receive a signal. Optionally, service instance 1200 may further include memory 1230. Processor 1210, transceiver 1220, and memory 1230 communicate with each other via an internal connection path. The memory 1230 is configured to store an instruction. The processor 1210 is configured to execute an instruction stored in the memory 1230 to control the transceiver 1220 to send a signal and/or receive a signal. It should be understood that transceiver 1220 may provide the same functions as sender 910 and receive 920 in FIG. 11. Processor 1210 and memory 1230 may provide the same functions as processing unit 930 in FIG. eleven.

[0503] The transceiver 1220 is configured to send a fourth message to the service handover proxy, the fourth message being used to initiate the handover proxy to establish a binding relationship between the service instance 1200 and the target identifier. The transceiver 1220 is further configured to receive a second message forwarded by the service handover proxy, the second message including the target identifier. Optionally, service instance 1200 may further include a processor 1210. Processor 1210 is configured to execute an instruction.

[0504] The service instance 1200 may further perform the steps performed by the first service instance in the methods of FIG. 3 - fig. 10. The transceiver 1220 of the service instance 1200 is further configured to receive a target identifier that is related to the user equipment and the second service instance. The transceiver 1220 adds the target identifier to the message that relates to the user equipment and the second service instance, and then sends the message, the target identifier being used to send the message to the second service instance. The processor 1210 is configured to execute the instruction.

[0505] It should be understood that the transceiver may be a communication interface. The memory may be an independent component or may be integrated into the processor. Each of the above components or some of the components may be integrated into a chip for implementation, for example, integrated into a baseband chip for implementation.

[0506] FIG. 15 is a block diagram of a communication device 1500 according to an embodiment of this application. The communication device 1500 includes a transceiver unit 1510 and a determination unit 1520.

[0507] The transceiver unit 1510 is configured to receive a first message that relates to the first session and that is sent by the third service instance or the fourth service instance, the first message including the target identifier.

[0508] The determiner 1520 is configured to determine, based on the target identifier, the second service instance that should provide the service for the first session.

[0509] The transceiver unit 1510 is further configured to send a second message related to the first session to the second service instance.

[0510] The communication device determines, based on the target identifier, the service instance that should provide the service for the first session. This increases the flexibility of the service instance selection so that the selected service instance that should provide the service for the first session may subsequently be different from the service instance that previously provided the service for the first session to avoid interruption caused by the first session due to the failure of the third service instance. .

[0511] Optionally, the first message includes binding method indication information. The binding method indication information is used to indicate binding of the first session to the third service instance or binding of the first session to the target service set. The target service set includes a second service instance, a third service instance, and a fourth service instance.

[0512] The communication device may determine, based on the binding method indication information, a service instance selection method.

[0513] Optionally, the target identifier includes the identifier of the third service instance.

[0514] Optionally, the transceiver unit 1510 is further configured to receive a third message sent by the third service instance, wherein the third message includes backup indication information, the backup indication information is used to indicate the second service instance to provide backup for the third service or indicate the second service instance to provide backup for the first session group for which the third service instance provides a service and the first session group includes the first session.

[0515] The determiner 1520 is configured to: when the third service instance is unavailable, determine the second service instance based on the backup indication information and the target ID.

[0516] Based on the backup indication information, the communication device may use the service instance that provides backup for the first session group as a candidate service instance. When the third service instance to which the first session is bound is not available, the backup service instance must provide the service for the first session. This will help avoid interruption of the first session due to the failure of the third instance of the service and improve the user experience.

[0517] Optionally, communication device 1500 further includes a receiving unit. The acquiring unit is configured to obtain a target service set ID based on the target ID.

[0518] The determiner 1520 is configured to determine a second service instance from the target service set based on the target service set identifier, the target service set including the second service instance, the third service instance, and the fourth service instance.

[0519] Optionally, the transceiver unit 1510 is further configured to send the target service set identifier to the NRF network element with the network repository function.

[0520] The transceiver unit 1510 is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance. The target service set includes a second instance of the service.

[0521] The communication device determines, based on the service instance ID that is sent by the NRF network element, that this service instance should provide the service for the first session. This may reduce the requirements for storage capacity and the ability to process the first instance of the service.

[0522] Optionally, the transceiver unit 1510 is further configured to receive first information sent by a service instance in the target service set, the first information including a service instance identifier and a target service set identifier.

[0523] The determiner 1520 is configured to determine the second service instance based on the target service set identifier and the first information.

[0524] Optionally, the acquiring unit is configured to obtain a target service set identifier from the target identifier, the target identifier including the target service set identifier.

[0525] Optionally, the acquisition unit is configured to: when the target identifier includes the identifier of the third service instance, obtain the identifier of the target service set based on the identifier of the third service instance, wherein the target service set includes the third service instance.

[0526] Optionally, the target identifier includes the identifier of the first session group, and the first session group includes the first session.

[0527] The transceiver unit 1510 is further configured to send the first session group ID to the network repository function NRF network element.

[0528] The transceiver unit 1510 is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0529] Optionally, the communication device 1500 is a user plane UPF network element, and the second service instance, the third service instance, and the fourth service instance are session management SMF network elements.

[0530] FIG. 16 is a block diagram of a communication device 1600 according to an embodiment of this application. The communication device 1600 includes a communication interface 1610 and a processor 1620.

[0531] The communication interface 1610 is configured to receive a first message that relates to a first session and that is sent by a third service instance or a fourth service instance, the first message including a target identifier.

[0532] The processor 1620 is configured to determine, based on the target identifier, the second service instance that should provide the service for the first session.

[0533] The communication interface 1610 is further configured to send a second message related to the first session to the second service instance.

[0534] Optionally, the first message includes binding method indication information. The binding method indication information is used to indicate binding of the first session to the third service instance or binding of the first session to the target service set. The target service set includes a second service instance, a third service instance, and a fourth service instance.

[0535] Optionally, the target identifier includes the identifier of the third service instance.

[0536] Optionally, the communication interface 1610 is further configured to receive a third message sent by the third service instance, where the third message includes backup indication information, the backup indication information is used to indicate the second service instance to provide backup for the third service instance, or specifying a second service instance to provide a backup for the first session group for which the third service instance provides a service and the first session group includes the first session.

[0537] The processor 1620 is configured to: when the third service instance is not available, determine the second service instance based on the backup indication information and the target ID.

[0538] Optionally, processor 1620 is further configured to obtain a target service set identifier based on the target identifier. Processor 1620 is further configured to determine a second service instance from the target service set based on the target service set identifier, where the target service set includes a second service instance, a third service instance, and a fourth service instance.

[0539] Optionally, the communication interface 1610 is further configured to send the target service set identifier to the NRF network element with the repository function.

[0540] The communication interface 1610 is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0541] Optionally, the communication interface 1610 is further configured to receive the first information sent by the service instance in the target service set. The first information includes a service instance identifier and a target service set identifier. Processor 1620 is configured to determine a second service instance from the target service set based on the target service set identifier and the first information.

[0542] Optionally, the processor 1620 is further configured to derive a target service set identifier from the target identifier, the target identifier including the target service set identifier.

[0543] Alternatively, processor 1620 is further configured to: when the target identifier includes the third service instance identifier, obtain the target service set identifier based on the third service instance identifier, the target service set including the third service instance.

[0544] Optionally, the target identifier includes the identifier of the first session group, and the first session group includes the first session.

[0545] The communication interface 1610 is further configured to send the first session group ID to the NRF network element of the network repository function.

[0546] The communication interface 1610 is further configured to receive a second service instance identifier that is sent by the NRF network element to determine the second service instance.

[0547] Optionally, the communication device 1600 is a UPF user plane function network element, and the second service instance, the third service instance, and the fourth service instance are network elements of the SMF session control function.

[0548] An embodiment of this application provides a communication device. The communication device may be configured to perform the steps performed by the third service instance in the method of FIG. 10. Specifically, the communication device includes a block configured to perform the method/step/function performed by the third service instance of FIG. ten.

[0549] An embodiment of this application provides a communication system. The communication system includes a transceiver and a processor. The transceiver communicates with the processor through an internal connection path. The processor is configured to control the receiver to receive the signal and control the transmitter to send the signal. Optionally, the communication device further includes a memory. The transceiver, memory, and processor communicate with each other via an internal connection path. The memory is configured to store the instruction. The processor is configured to execute an instruction stored in memory to control a receiver to receive a signal and control a transmitter to send a signal so that the device can perform the method/step/function performed by the third service instance of FIG. ten.

[0550] An embodiment of this application provides a communication system. The communication system includes a first instance of the service. The first service instance is configured to perform the steps performed by the first service instance in the method of FIG. ten.

[0551] Optionally, the system may further include a third service instance. The third service instance is configured to perform the steps performed by the third service instance in the method of FIG. ten.

[0552] Optionally, the system may further include another device. The other device is configured to interact with the first service instance and/or the third service instance. The other device may be, for example, a network element of the access control function. The access control function network element may be configured to perform the method performed by the access control function network element in the solution shown in FIG. ten.

[0553] An embodiment of this application provides a computer program product. A computer program product includes computer program code. The computer program code is run by the computer to implement the functions of the aforementioned service instance and service transfer proxy.

[0554] An embodiment of this application provides a computer-readable medium. The computer-readable medium is configured to store a computer program. The computer program includes an instruction used to implement the functions of the above service instance and the service transfer proxy.

[0555] An embodiment of this application provides a communications chip. The communication chip stores the instruction. The instruction is run on the computer device to implement the functions of the aforementioned service instance and service transfer proxy.

[0556] One skilled in the art may be aware that, in combination with the examples described in the embodiments disclosed herein, the blocks and steps of an algorithm may be implemented using electronic hardware or a combination of computer software and electronic hardware. The performance of functions by hardware or software depends on the specific applications and the state of the design constraints of the technical solutions. A person skilled in the art can use various methods to implement the described functions for each particular application, but such an implementation should not be considered to be outside the scope of this application.

[0557] For a person skilled in the art, it may be clear that for convenience and concise description, the detailed workflow of the above systems, devices and blocks refers to the corresponding processes in the above method embodiments and the details are not described here again.

[0558] In several embodiments presented in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described are merely examples. For example, block division is simply a division of logical functions and may be another division in a real implementation. For example, many blocks or components may be combined or integrated into another system, or certain features may be ignored or not implemented. In addition, interconnections or direct connections or communication connections shown or described may be implemented using some interfaces. Indirect connections or communication connections between devices or units may be implemented in electronic, mechanical or other forms.

[0559] Blocks described as separate parts may or may not be physically separate, and parts displayed as blocks may or may not be physical blocks, namely, may be located in one position or may be distributed over a plurality of network blocks. Some or all of the blocks may be selected based on actual requirements in order to achieve the objectives of the decisions in the mentioned embodiments.

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

[0561] When functions are implemented in the form of a software functional block and sold or used as an independent product, the functions may be stored on a computer-readable storage medium. Based on such an understanding, the technical solutions of this application per se, or a part contributing to the prior art, or a part of the technical solutions can be implemented in the form of a software product. The computer program product is stored on a storage medium and includes several instructions for directing a computing device (which may be a personal computer, a server, a network device, etc.) to perform all or some of the steps of the methods described in the embodiments of this application. A storage medium includes any medium on which program code can be stored, such as a USB flash drive, removable hard disk, read-only memory (Read Only Memory, ROM), Random Access Memory (Random Access Memory, RAM), magnetic disk. or optical disc.

The above description is only specific implementations of this application, but is not intended to limit the scope of protection of this application. Any change or replacement readily detectable by a person skilled in the art within the technical scope disclosed in this application should/should fall within the scope of this application. Therefore, the scope of this application is protected by the claims.

Claims (34)

1. A communication method, comprising the steps of: receiving, by means of the first service instance, a first message that relates to the session and that is sent by the third service instance, the first message containing the target identifier, the target identifier containing the identifier of the third service instance; in case the third service instance is not available, determining by the first service instance, based on the identifier of the third service instance, the second service instance to provide the service for the session; and sending, by way of the first service instance, a second session-related message to the second service instance; wherein the first service instance is a user plane function (UPF) network element, and the second service instance and the third service instance are session management function (SMF) network elements. 2. The method of claim 1, wherein said first service instance, based on an identifier of the third service instance, determines the second service instance that is to provide the service for the session, comprising: obtaining, by means of the first service instance, a target service set identifier based on the identifier of the third service instance; and determining, by means of the first service instance, a second service instance from the target service set based on the target service set identifier, the target service set comprising the second service instance and the third service instance. 3. The method of claim 2, wherein the method further comprises the steps of: receiving, by means of the first service instance, first information sent by the third service instance, the first information containing the identifier of the third service instance and the identifier of the target service set; receiving, by means of the first service instance, second information sent by the second service instance, the second information containing the identifier of the second service instance and the identifier of the target service set; and wherein, in said determination by the first service instance of a second service instance from the target service set based on the target service set identifier, the second service instance is determined by the first service instance based on the target service set identifier, the first information and the second information. 4. The method of claim 1, wherein the first information is included in the N4 association setup message exchanged between the first service instance and the third service instance, the second information is included in the N4 association setup message exchanged between the first service instance and the second service instance. service instance. 5. Communication equipment comprising a processor capable of executing instructions stored in memory to perform the steps of a method according to any one of claims 1-4. 6. A communication method, comprising the steps of: sending, via the third service instance, a first message related to the session to the first service instance, the first message containing a target identifier, the target identifier containing the identifier of the third service instance; receive by means of the first instance of the service the first message; in the case where the third service instance is unavailable, determining by the first service instance, based on the identifier of the third service instance, the second service instance to provide the service for the session; and sending, by way of the first service instance, a second session-related message to the second service instance; wherein the first service instance is a user plane function (UPF) network element, and the second service instance and the third service instance are session management function (SMF) network elements. 7. The method of claim 6, wherein said determining, by a first service instance based on an identifier of a third service instance, a second service instance that is to provide a service for said session, comprises: obtaining, by means of the first service instance, a target service set identifier based on the identifier of the third service instance; and determining, by means of the first service instance, a second service instance from the target service set based on the target service set identifier, the target service set comprising the second service instance and the third service instance. 8. The method according to claim 6 or 7, the method further comprising the steps of: sending, via the third service instance, first information to the first service instance, the first information comprising a target service set identifier and a third service instance identifier, the target service set comprising a second service instance and a third service instance; sending, via the second service instance, second information to the first service instance, the second information comprising a target service set identifier and a third service instance identifier; receiving, by means of the first instance of the service, first information and second information; determining, by means of the first service instance, a second service instance based on the target service set identifier, the first information, and the second information. 9. The method according to any one of claims 6 to 8, wherein the first information is included in the N4 association setup message exchanged between the first service instance and the third service instance, wherein the second information is included in the N4 association setup message exchanged. between the first service instance and the second service instance. 10. Computer storage medium, wherein the computer storage medium stores computer-executable instructions, and when the computer calls the computer-executable instructions, the computer executes the method according to any one of claims 1-4 or the method according to any one of claims 6-9. 11. A communication microcircuit system, comprising: a memory configured to store a computer program; and a processor configured to: recall a computer program from memory and run the computer program so that the device in which the chip system is installed performs the method of any one of claims 1 to 4 or the method of any one of claims 6 to 9. 12. A communication system comprising the communication equipment of claim 5 and a third service instance and a second service instance.

Images