Service continuity guarantee method and device under distributed network architecture

Abstract

The invention provides a service continuity guarantee method and device under a distributed network architecture. The method comprises the following steps: determining a service type requested by terminal UE; sending a service context establishment request message to a corresponding service management function according to the service type of the request; receiving a first message sent by the corresponding service management function, wherein the first message comprises the selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined after the service management function receives the service context establishment request message. Diversified continuity requirements of different applications or services of the UE can be effectively and accurately met.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for ensuring business continuity in a distributed network architecture. Background Art

[0002] The current 5G mobile communication network system is natively designed for centralized control. With the development of the network, the trend of 6G network is a network architecture that combines centralized and distributed control. The 6G network will build distributed network nodes with different functional levels.

[0003] Among them, under the 5G centralized control architecture, 5GC supports three session and service continuity modes (English: session and service continuity mode, abbreviated as: SSC mode). SSC mode1-3 (SSC mode1, SSC mode2 and SSC mode3) are used to support maintaining session connection, supporting disconnection before connection (disconnecting the old session connection first and then establishing a new session connection), and supporting connection before disconnection (establishing a new session connection first and then disconnecting the old session connection).

[0004] However, more business scenarios may emerge under the 6G distributed network architecture. The 6G network will provide new services in addition to the connection services provided by 5G. However, the existing SSC mode mechanism cannot effectively and accurately meet the diverse continuity requirements of different applications or services of UE. Summary of the invention

[0005] The present application provides a method and device for ensuring service continuity under a distributed network architecture, which solves the technical problem in the prior art that the 6G distributed network architecture cannot effectively and accurately meet the diverse continuity requirements of different applications or services of UE.

[0006] In a first aspect, the present application provides a method for ensuring service continuity in a distributed network architecture, which is applied to an access and mobility management function AMF, and the method includes:

[0007] Determine the service type requested by the terminal UE;

[0008] Sending a service context establishment request message to a corresponding service management function according to the requested service type;

[0009] Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0010] In an embodiment of the present application, AMF (or other network functions that perform access and mobility management or service management) determines the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for 6G distributed network architecture scenarios. Therefore, it can effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0011] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0012] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0013] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0014] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0015] Optionally, the determining the service type requested by the terminal UE includes:

[0016] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0017] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0018] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0019] Optionally, sending a service context establishment request message to a corresponding service management function according to the requested service type includes:

[0020] If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF;

[0021] If the requested service type is a computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center;

[0022] If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0023] If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0024] If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0025] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0026] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0027] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0028] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0029] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0030] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0031] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0032] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes:

[0033] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or, if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, then determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0034] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determining of the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type includes:

[0035] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0036] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0037] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0038] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determining of the target network node for supporting cross-network nodes and the corresponding target network function required in the scenario of the requested service type includes:

[0039] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0040] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0041] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0042] Optionally, the method further comprises:

[0043] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0044] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0045] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determining of the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type includes:

[0046] If a third message sent by the current computing power orchestration center is received, the operation of releasing the computing power service between the UE and the current computing power service function node is triggered; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0047] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0048] Among them, the target computing power service function node is the target network function.

[0049] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0050] In a second aspect, the present application provides a method for ensuring business continuity in a distributed network architecture, which is applied to a service management function, and the method includes:

[0051] Receiving a service context establishment request message sent by the AMF in the current network node, wherein the service context establishment request message is sent by the AMF according to the determined requested service type;

[0052] Determining a selected target SSC mode according to the service context establishment request message;

[0053] Send a first message to the AMF, where the first message includes the target SSC mode.

[0054] In an embodiment of the present application, the service management function determines the target SSC mode based on the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for 6G distributed network architecture scenarios. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0055] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0056] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0057] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0058] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0059] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0060] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0061] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0062] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0063] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0064] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0065] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0066] If the requested service type is a security service, the service management function is a security management center.

[0067] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0068] Optionally, determining the selected target SSC mode according to the service context establishment request message includes:

[0069] If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, for any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode; when it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF;

[0070] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0071] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; the target SSC mode determined according to the local policy or by a network data analysis function NWDAF includes:

[0072] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0073] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0074] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes:

[0075] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0076] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0077] In a third aspect, the present application provides a method for ensuring service continuity in a distributed network architecture, the method being applied to a UE, the method comprising:

[0078] Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type;

[0079] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0080] In an embodiment of the present application, the UE sends a service establishment request message to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it can effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0081] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0082] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0083] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0084] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0085] Optionally, the method further comprises:

[0086] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0087] Optionally, determining the requested SSC mode includes:

[0088] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0089] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0090] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0091] In a fourth aspect, the present application provides a service continuity guarantee device under a distributed network architecture, the device is applied to AMF, and the device includes:

[0092] A determination unit, configured to determine a service type requested by the UE;

[0093] A sending unit, configured to send a service context establishment request message to a corresponding service management function according to the requested service type;

[0094] A receiving unit is used to receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0095] In an embodiment of the present application, AMF (or other network functions that perform access and mobility management or service management) determines the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for 6G distributed network architecture scenarios. Therefore, it can effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0096] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0097] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0098] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0099] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0100] Optionally, the determining unit is specifically configured to:

[0101] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0102] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0103] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0104] Optionally, the sending unit is specifically configured to:

[0105] When the requested service type is a connection service, determining that the corresponding service management function is a session management function SMF, and sending a connection service context establishment request message to the SMF;

[0106] When the requested service type is a computing power service, determining that the corresponding service management function is a computing power orchestration center, and sending a computing power service context establishment request message to the computing power orchestration center;

[0107] When the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0108] When the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0109] When the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0110] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0111] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0112] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0113] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0114] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0115] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0116] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0117] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the device further includes: a first processing unit; the first processing unit is configured to:

[0118] For any target SSC mode, when the network first releases the service provided to the user and reestablishes the service and allows the change of the service anchor point and allows the service to cross network nodes in the scenario of the corresponding requested service type in the target SSC mode, or when the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes in the scenario of the corresponding requested service type in the target SSC mode, determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0119] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0120] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0121] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0122] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0123] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0124] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0125] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0126] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0127] Optionally, the device further includes: a second processing unit; the second processing unit is configured to:

[0128] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0129] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0130] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0131] Upon receiving a third message sent by the current computing power orchestration center, triggering an operation of releasing the computing power service between the UE and the current computing power service function node; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0132] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0133] Among them, the target computing power service function node is the target network function.

[0134] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0135] In a fifth aspect, the present application provides a device for ensuring business continuity in a distributed network architecture, the device being applied to a service management function, the device comprising:

[0136] A receiving unit, configured to receive a service context establishment request message sent by the AMF in the current network node, wherein the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF;

[0137] a determining unit, configured to determine a selected target SSC mode according to the service context establishment request message;

[0138] A sending unit is used to send a first message to the AMF, wherein the first message includes the target SSCmode.

[0139] In an embodiment of the present application, the service management function determines the target SSC mode based on the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for 6G distributed network architecture scenarios. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0140] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0141] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0142] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0143] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0144] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0145] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0146] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0147] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0148] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0149] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0150] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0151] If the requested service type is a security service, the service management function is a security management center.

[0152] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0153] Optionally, the determining unit is specifically configured to:

[0154] The service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one. For any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode. When it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0155] When the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0156] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; and the determination unit is specifically configured to:

[0157] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0158] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0159] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the device further includes: a processing unit; the processing unit is configured to:

[0160] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0161] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0162] In a sixth aspect, the present application provides a service continuity guarantee device under a distributed network architecture, the device being applied to a UE, and the device comprising:

[0163] A sending unit, configured to send a service establishment request message to the AMF in the current network node, wherein the service establishment request message includes the requested service type or information indicating the requested service type;

[0164] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0165] In an embodiment of the present application, a service establishment request message is sent to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0166] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0167] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0168] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0169] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0170] Optionally, the device further includes: a determining unit; the determining unit is configured to:

[0171] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0172] Optionally, the determining unit is specifically configured to:

[0173] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0174] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0175] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0176] In a seventh aspect, the present application provides a service continuity guarantee device under a distributed network architecture, the device is applied to AMF, and the device includes a memory, a transceiver, and a processor:

[0177] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0178] Determine the type of service requested by the UE;

[0179] Sending a service context establishment request message to a corresponding service management function according to the requested service type;

[0180] Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0181] In an embodiment of the present application, by determining the requested service type, the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0182] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0183] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0184] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0185] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0186] Optionally, the processor is configured to, when determining the service type requested by the terminal UE, specifically include:

[0187] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0188] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0189] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0190] Optionally, the processor is configured to, when sending a service context establishment request message to a corresponding service management function according to the requested service type, specifically include:

[0191] If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF;

[0192] If the requested service type is a computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center;

[0193] If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0194] If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0195] If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0196] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0197] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0198] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0199] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0200] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0201] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0202] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0203] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the processor is further configured to perform the following operations:

[0204] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or, if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, then determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0205] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor is used to determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0206] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0207] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0208] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0209] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reconstructs the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor is used to determine the target network node for supporting cross-network nodes and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0210] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0211] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0212] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0213] Optionally, the processor is further configured to perform the following operations:

[0214] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0215] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0216] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor is used to determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0217] If a third message sent by the current computing power orchestration center is received, the operation of releasing the computing power service between the UE and the current computing power service function node is triggered; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0218] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0219] Among them, the target computing power service function node is the target network function.

[0220] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0221] In an eighth aspect, the present application provides a device for ensuring business continuity under a distributed network architecture, the device being applied to a service management function, the device comprising: a memory, a transceiver, and a processor:

[0222] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0223] Receiving a service context establishment request message sent by the AMF in the current network node, where the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF;

[0224] Determining a selected target SSC mode according to the service context establishment request message;

[0225] Send a first message to the AMF, where the first message includes the target SSC mode.

[0226] In an embodiment of the present application, the target SSC mode is determined according to the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0227] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0228] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0229] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0230] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0231] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0232] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0233] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0234] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0235] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0236] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0237] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0238] If the requested service type is a security service, the service management function is a security management center.

[0239] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0240] Optionally, the processor is configured to, when determining the selected target SSC mode according to the service context establishment request message, specifically include:

[0241] If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, for any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode; when it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF;

[0242] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0243] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; and the processor is configured to, when determining the target SSC mode according to the local policy or through a network data analysis function NWDAF, specifically include:

[0244] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0245] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0246] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the processor is further configured to perform the following operations:

[0247] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0248] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0249] In a ninth aspect, the present application provides a device for ensuring service continuity under a distributed network architecture, the device being applied to a UE, the device comprising: a memory, a transceiver, and a processor:

[0250] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0251] Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type;

[0252] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0253] In an embodiment of the present application, a service establishment request message is sent to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0254] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0255] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0256] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0257] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0258] Optionally, the processor is further configured to perform the following operations:

[0259] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0260] Optionally, the processor is configured to, when determining the requested SSC mode, specifically include:

[0261] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0262] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0263] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0264] In a tenth aspect, the present application provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute any of the methods described above.

[0265] The present application provides a method and device for ensuring the continuity of services under a distributed network architecture, which comprises determining the service type requested by the UE; sending a service context establishment request message to a corresponding service management function according to the requested service type; receiving a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message. Therefore, by determining the requested service type, the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0266] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present application, nor are they intended to limit the scope of the present application. Other features of the present application will become easy to understand through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0267] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0268] Figure 1 A flow chart of a method for ensuring business continuity in a distributed network architecture provided in an embodiment of the present application;

[0269] Figure 2 An interactive schematic diagram of a method for ensuring business continuity in a distributed network architecture provided in an embodiment of the present application;

[0270] Figure 3 An interactive schematic diagram of a method for ensuring service continuity in a distributed network architecture provided by another embodiment of the present application;

[0271] Figure 4 An interactive schematic diagram of a method for ensuring business continuity in a distributed network architecture provided by another embodiment of the present application;

[0272] Figure 5 An interactive schematic diagram of a method for ensuring service continuity in a distributed network architecture provided by another embodiment of the present application;

[0273] Figure 6 An interactive schematic diagram of a method for ensuring service continuity in a distributed network architecture provided in yet another embodiment of the present application;

[0274] Figure 7 A flowchart of a method for ensuring business continuity in a distributed network architecture provided in another embodiment of the present application;

[0275] Figure 8 A schematic diagram of the structure of a service continuity assurance device under a distributed network architecture provided in an embodiment of the present application;

[0276] Fig. 9 A schematic diagram of the structure of a service continuity assurance device in a distributed network architecture provided by another embodiment of the present application;

[0277] Fig.10 A schematic diagram of the structure of a service continuity assurance device in a distributed network architecture provided in yet another embodiment of the present application;

[0278] Fig.11 A schematic diagram of the structure of a service continuity assurance device in a distributed network architecture provided in yet another embodiment of the present application. DETAILED DESCRIPTION

[0279] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0280] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0281] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0282] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail.

[0283] The 6G distributed network consists of multiple network nodes. According to the differences in the deployment of business functions, it can be logically divided into central network nodes (also called centralized network nodes, centralized nodes, central nodes, etc.) and distributed network nodes (also called distributed nodes). The central node has complete functions, and the distributed node functions are relatively simple, but all distributed nodes have basic functions of the control plane and user plane (access control, message forwarding, etc.) to ensure that the most basic services can be carried out. The functions of different distributed nodes can be customized according to different scenarios, and can work with other distributed nodes and central nodes to provide services to access users. More business scenarios may appear under the 6G distributed network architecture, and the 6G network will provide new services in addition to the connection services provided by 5G.

[0284] The network node here can also be a Small Cloud Unit (SCU).

[0285] Under the 5G centralized control architecture, 5GC supports three types of session and service continuity modes (SSC mode for short), SSC mode 1-3 (SSC mode 1, SSC mode 2 and SSC mode 3) are used to support maintaining session connection, disconnect first and connect later (disconnect the old session connection first and then establish a new session connection), and connect first and disconnect later (establish a new session connection first and then disconnect the old session connection). However, the existing SSC mode mechanism is not applicable enough for providing multiple new services for 6G and a distributed network architecture.

[0286] Therefore, the existing SSC mode mechanism cannot effectively and accurately meet the diverse continuity requirements of different applications or services of UE.

[0287] The inventors further discovered that in order to solve the problem in the prior art that the 6G distributed network architecture cannot effectively and accurately meet the diverse continuity requirements of different applications or services of UE, a more fine-grained SSC mode mechanism can be used to meet the characteristics of the distributed network architecture. By defining a new SSC mode mechanism, it is possible to more accurately support solving the rich continuity requirements of different applications / services of UE.

[0288] Therefore, based on the creative research of the above-mentioned inventors, a method and device for ensuring service continuity under a distributed network architecture proposed in this application are proposed. In this application, by determining the requested service type, the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for 6G distributed network architecture scenarios. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0289] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0290] Embodiments of the present application will be described below with reference to the accompanying drawings.

[0291] See also Figure 1 As shown, Figure 1A flow chart of a method for ensuring business continuity under a distributed network architecture provided in an embodiment of the present application. The execution subject of the method for ensuring business continuity under a distributed network architecture provided in this embodiment is the access and mobility management function (AMF for short), and may also be other network functions that perform access and mobility management or service management. For example, with the service-oriented research on RAN wireless access functions, there may be certain functional reconstructions in the access network and the core network, and the functional network elements responsible for access and mobility management may change. Alternatively, for 6G, the introduction of new services such as new data, intelligence, computing power, perception, and security other than connections may require the introduction of an independent service management function in addition to AMF and SMF, which is responsible for the unified collaborative management of multiple services. The method for ensuring business continuity under a distributed network architecture provided in an embodiment of the present application includes the following steps:

[0292] Step 101: Determine the service type requested by the terminal UE.

[0293] The requested service type is at least one.

[0294] Optionally, determining the service type requested by the terminal UE includes:

[0295] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0296] In this embodiment, one implementation method for determining the service type requested by the UE is: by receiving a service establishment request message sent by the UE, the service establishment request message carries the requested service type or information used to indicate the requested service type, and the requested service type can be determined. The information used to indicate the requested service type here can be indication information based on the UE device type or the service type required by the UE's current application or service. Another implementation method is: AMF or other network functions determine the requested service type based on the UE device type or the UE's current application or service.

[0297] Step 102: Send a service context establishment request message to a corresponding service management function according to the requested service type.

[0298] In this embodiment, one (or one) requested service type corresponds to one service management function. Wherein, one business or application may include multiple service types, and multiple service management functions may be used or corresponded here. It is also possible that multiple service types correspond to the same service management function, that is, multiple service types correspond to one service management function.

[0299] Optionally, the service establishment request message also includes a requested SSC mode, and correspondingly, the service context establishment request message includes a requested SSC mode;

[0300] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0301] In this embodiment, the UE can determine the service type, whether to allow the change of the service anchor point, and whether to allow cross-network nodes based on the service continuity characteristics required by the application / service for the network service, thereby deciding the SSC mode requested by the UE according to the information shown in Table 1.

[0302] Among them, the business continuity characteristics include not only the service continuity requirements, but also the business type (for example, emergency business has higher business continuity requirements, and Internet of Things (IoT) devices have low latency requirements, etc.), terminal mobility (terminals with strong mobility are more inclined to choose SSC mode that can cross network nodes and maintain continuity, and tend to choose network nodes with a larger service range), latency requirements (low latency, for example, they tend to choose to ensure continuity within network nodes), privacy requirements (high privacy, for example, they tend to choose to ensure continuity within network nodes), and other information.

[0303] The terminal mobility here may be the mobility of the terminal itself or the mobility of the carrier where the terminal is located, that is, the terminal mobility characteristics may include the mobility characteristics of the terminal itself or the mobility characteristics of the carrier where the terminal is located.

[0304] Step 103: Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0305] In this embodiment, the target SSC mode is selected as follows: (1) it can be determined by the service management function corresponding to the service type here; (2) it can also be a unified service management function of multiple services such as SMF, computing power orchestration center, data orchestration center, intelligent orchestration center, security management center, etc. For example, a scenario in which a business or application includes multiple services can be determined by the unified service management function.

[0306] In an embodiment of the present application, by determining the requested service type, the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0307] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0308] Among them, computing power services include services related to computing power, such as users requesting the network to provide computing power resources, or users requesting the use of the network's computing power resources to provide computing services or storage services. Data services include services related to data collection, data storage, data processing, data analysis, data provision, etc., such as users requesting the network to store, process, analyze data collected by UE, or users requesting the network to provide stored data to users, or users requesting the network to collect other UE or RAN's perception data or AI data and provide them to users. The data services here also include perception services related to perception data, such as environmental data collected by UE. Intelligent services include services related to artificial intelligence, such as the network intelligently analyzing which network node or network function handles the corresponding problem better or more applicable to the data provided by UE, or users requesting the network to use the AI ​​model in the network to give intelligent analysis results for some raw data. Security services include services related to security and / or trustworthiness of data or information, such as data encryption and decryption, data format conversion, authentication and authorization, access control, authentication, and other services that require security and / or privacy protection.

[0309] It should be noted that the above-mentioned connection services, computing power services, data services, intelligent services, security services, perception services, etc. are related to the concepts of mobile communication transmission services, computing power network / computing power surface / computing network integration, data surface, artificial intelligence, security surface, synaesthesia integration / synaesthesia integration proposed by the industry, and the service methods they provide can be used as the application background of this application.

[0310] In the embodiment of the present application, it is possible to support services corresponding to multiple types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the business continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security (that is, in addition to providing business continuity guarantees for connection services, other services such as computing power, data, intelligence, and security can also be provided), and a combination of multiple service continuity is supported. In this way, the diverse continuity requirements of different UE applications or services can be met.

[0311] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0312] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0313] Among them, the newly defined SSC mode is shown in Table 1:

[0314] Table 1

[0315]

[0316]

[0317] Specifically, the existing SSC modes 1-3 are updated to ensure the continuity of connection capabilities within network nodes:

[0318] SSC mode 1 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of connected services and does not allow changes to the service anchor point or services across network nodes) does not change the protocol data unit session anchor (English: PDU Session Anchor, abbreviated as: PSA), and the user plane path can be modified at the current network node.

[0319] In SSC mode 2 (here, in the scenario of connecting services, the network first releases the services provided to users and reestablishes the services, allows the service anchor point to be changed, and does not allow services to cross network nodes), the session connection in the current network node is disconnected first and then a new session connection is immediately established in the current network node.

[0320] In SSC mode 3, a new session connection is established in the current network node, and then the old session connection in the current network node is immediately disconnected.

[0321] Added SSC mode 4-6 to support building connections between network nodes to ensure connection continuity:

[0322] SSC mode 4 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of connected services and does not allow changes in service anchor points and allows services to cross network nodes) does not change PSA, and can insert an intermediate user plane function (English: Intermediate UPF, abbreviated as: I-UPF) in the new network node to modify the user plane path.

[0323] In SSC mode 5, the network first releases the service provided to the user and reestablishes the service in the scenario of connecting services, and allows the service anchor point to be changed and the service to be cross-network nodes. The network nodes are disconnected first and then reestablished. The session connection in the current network node is disconnected first, and then a new session connection is immediately established in the new network node.

[0324] In SSC mode 6, the network establishes other services before releasing the services provided to users, allows the service anchor point to be changed, and allows services to cross network nodes. The network nodes are first established and then disconnected. A new session connection is created in the new network node, and then the old session connection in the current network node is immediately disconnected.

[0325] According to the service types in different dimensions such as computing power, data, intelligence, and security, SSCmode similar to SSC mode1-6 is designed.

[0326] SSC mode 7 (here refers to the SSC mode in which the network needs to continuously provide services to users in the computing service scenario and does not allow the service anchor point to be changed or the service to cross network nodes). The computing service anchor point (i.e., the computing node providing the computing service) does not change, but the computing service path (i.e., the computing routing path from the computing requester to the computing node providing the computing service) can be modified at the current network node.

[0327] SSC mode 8 (here refers to the SSC mode in which the network first releases the service provided to the user and rebuilds the service in the computing service scenario, and allows the change of the service anchor point and does not allow the service to cross network nodes), allows the computing service anchor point to be changed, first disconnects the computing service path in the current network node, and then immediately creates a new computing service path in the current network node;

[0328] SSC mode 9 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the computing service scenario and allows the change of service anchor points and does not allow services to cross network nodes) allows the computing service anchor point to be changed, first creates a new computing service path in the current network node, and then immediately disconnects the old computing service path in the current network node;

[0329] SSC mode 10 (here refers to the SSC mode in which the network needs to continuously provide services to users in the computing service scenario and does not allow the service anchor point to be changed or the service to cross network nodes). The computing service anchor point (i.e., the computing node providing the computing service) does not change, and the computing service path (i.e., the computing routing path from the computing requester to the computing node providing the computing service) can be modified at the new network node;

[0330] SSC mode 11 (here refers to the SSC mode in which the network first releases the service provided to the user and rebuilds the service in the computing service scenario, and allows the change of the service anchor point and does not allow the service to cross network nodes), allows the change of the computing service anchor point, first disconnects the computing service path in the current network node, and then immediately creates a new computing service path in the new network node;

[0331] SSC mode 12 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the computing service scenario and allows the change of service anchor points and does not allow services to cross network nodes) allows the computing service anchor point to be changed, first creates a computing service path in the new network node, and then immediately disconnects the old computing service path in the current network node;

[0332] SSC mode 13 (here refers to the SSC mode in which the network needs to continuously provide services to users in the data service scenario and does not allow the service anchor point to be changed or the service to cross network nodes), the data service anchor point (i.e. the node providing data services) does not change, and the data service path (i.e. the data routing path from the data requester to the node providing data services) can be modified at the current network node;

[0333] SSC mode 14 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the data service scenario, and allows the change of the service anchor point and does not allow the service to cross network nodes), allows the change of the data service anchor point, first disconnects the data service path in the current network node, and then immediately creates a new data service path in the current network node;

[0334] SSC mode 15 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the data service scenario and allows the change of service anchor points and does not allow services to cross network nodes), allowing the change of data service anchor points, first creating a new data service path in the current network node, and then immediately disconnecting the old data service path in the current network node;

[0335] SSC mode 16 (here refers to the SSC mode in which the network needs to continuously provide services to users in the data service scenario and does not allow the service anchor point to be changed or the service to cross network nodes), the computing power service anchor point (that is, the node providing data services) does not change, and the data service path (that is, the data routing path from the data requester to the node providing data services) can be modified at the new network node;

[0336] SSC mode 17 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the data service scenario, and allows the change of the service anchor point and does not allow the service to cross network nodes), allows the change of the data service anchor point, first disconnects the data service path in the current network node, and then immediately creates a new data service path in the new network node;

[0337] SSC mode 18 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the data service scenario and allows the change of service anchor points and does not allow services to cross network nodes) allows the change of data service anchor points, first creates a new data service path in the new network node, and then immediately disconnects the old data service path in the current network node;

[0338] SSC mode 19 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of smart services and does not allow the service anchor point to be changed or the service to cross network nodes), does not change the smart service anchor point (i.e. the node providing the smart service), and can modify the smart service path (i.e. the smart routing path from the smart requester to the node providing the smart service) at the current network node;

[0339] SSC mode 20 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the scenario of smart service, and allows the change of service anchor point and does not allow the service to cross network nodes), allows the change of smart service anchor point, first disconnects the smart service path in the current network node, and then immediately creates a new smart service path in the current network node;

[0340] SSC mode 21 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the scenario of smart services, allows the change of service anchor points, and does not allow services to cross network nodes), allows the change of smart service anchor points, first creates a new smart service path in the current network node, and then immediately disconnects the old smart service path in the current network node;

[0341] SSC mode 22 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of smart services and does not allow the service anchor point to be changed or the service to cross network nodes), does not change the smart service anchor point (i.e. the node providing the smart service), and can modify the smart service path (i.e. the smart routing path from the smart requester to the computing power node providing the smart service) at the new network node;

[0342] SSC mode 23 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the scenario of smart service, and allows the change of service anchor point and does not allow the service to cross network nodes), allows the change of smart service anchor point, first disconnects the smart service path in the current network node, and then immediately creates a new smart service path in the new network node;

[0343] SSC mode 24 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the scenario of smart services and allows the change of service anchor points and does not allow services to cross network nodes) allows the change of smart service anchor points, first creates a new smart service path in the new network node, and then immediately disconnects the old smart service path in the current network node;

[0344] SSC mode 25 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of security services and does not allow the service anchor point to be changed or the service to cross network nodes), does not change the security service anchor point (i.e. the node providing security services), and can modify the security service path (i.e. the security routing path from the security requester to the node providing security services) at the current network node;

[0345] SSC mode 26 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the scenario of security service, and allows the change of service anchor point and does not allow the service to cross network nodes), allows the change of security service anchor point, first disconnects the security service path in the current network node, and then immediately creates a new security service path in the current network node;

[0346] SSC mode 27 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the scenario of security services and allows the change of service anchor points and does not allow services to cross network nodes), allows the change of security service anchor points, first creates a new security service path in the current network node, and then immediately disconnects the old security service path in the current network node;

[0347] SSC mode 28 (here refers to the SSC mode in which the network needs to continuously provide services to users in the scenario of security services and does not allow the service anchor point to be changed or the service to cross network nodes) does not change the security service anchor point (i.e. the node providing security services), but can modify the security service path (i.e. the security routing path from the security requester to the node providing security services) at the new network node;

[0348] SSC mode 29 (here refers to the SSC mode in which the network first releases the service provided to the user and reestablishes the service in the scenario of security service, and allows the change of service anchor point and does not allow the service to cross network nodes), allows the change of security service anchor point, first disconnects the security service path in the current network node, and then immediately creates a new security service path in the new network node;

[0349] SSC mode 30 (here refers to the SSC mode in which the network establishes other services before releasing the services provided to users in the security service scenario and allows the change of service anchor points and does not allow services to cross network nodes) allows the change of security service anchor points, first creates a new security service path in the new network node, and then immediately disconnects the old security service path in the current network node.

[0350] I will not elaborate on this. It should be noted that the above solutions can be combined, for example, an application or business involves both connection services and computing services. The above solutions can be further refined, such as the type of network nodes (central nodes or distributed nodes), the characteristics of network nodes (such as the size of the service range), the number of cross-network nodes, etc., to further refine the SSC mode and achieve a more accurate business continuity guarantee solution design.

[0351] Optionally, sending a service context establishment request message to a corresponding service management function according to the requested service type includes:

[0352] If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF;

[0353] If the requested service type is a computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center;

[0354] If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0355] If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0356] If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0357] The computing power orchestration center is used to include at least one of the following: the orchestration and scheduling management and information management of computing power services, such as computing power information and computing power node identification provided to terminals; computing power services include services related to computing power, such as users requesting the network to provide computing power resources, or users requesting to use the computing power resources of the network to provide computing services or storage services. The data orchestration center is used to include at least one of the following: the orchestration and scheduling and information management of data services, such as some application or business-related data processing; data services include services involving data collection, data storage, data processing, data analysis, data provision, etc., such as users requesting the network to store, process, analyze data collected by UE, or users requesting the network to provide stored data to users, or users requesting the network to collect perception data or AI data from other UEs or RANs and provide them to users. The data services here also include perception services related to perception data, such as environmental data collected by UE. The intelligent orchestration center is used to include at least one of the following: orchestration and scheduling of intelligent services, information management, and provision of AI models; wherein intelligent services include services related to artificial intelligence, such as the network intelligently analyzing which network node or network function handles the corresponding problem better or more applicable to the data provided by the UE, or the user requests the network to use the AI ​​model in the network to give intelligent analysis results for some raw data. The security management center is used to include at least one of the following: orchestration and scheduling of security services, data management, privacy protection, and authorization management, such as encryption and decryption, format conversion, and other management that requires security protection; wherein security services include security and / or trust-related services such as data or information, such as data encryption and decryption, data format conversion, authentication and authorization, access control, authentication, and other services that require security protection and / or privacy protection.

[0358] In the embodiment of the present application, one requested service type corresponds to one service management function, and different requested service types can send establishment requests to different service management functions. Among them, a business or application may include multiple service types, which may correspond to multiple service management functions, and can realize a combination of supporting multiple service continuity.

[0359] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0360] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0361] Specifically, if the service context establishment request message includes a requested SSC mode, for any requested SSC mode, if the requested SSC mode is within the SSC mode range allowed by the contract data, the requested SSC mode is selected as the target SSC mode; if the requested SSC mode is not within the SSC mode range allowed by the contract data, the corresponding service management function (for example, the session management function (English: Session Management Function, abbreviated as: SMF), other service management functions are similar and will not be repeated here.) determines or specifies an SSC mode as the target SSC mode according to local policies or through a network data analysis function (English: Network Data Analytics Function, abbreviated as: NWDAF).

[0362] If the service context establishment request message does not include the requested SSC mode, the corresponding service management function (eg, SMF) determines or specifies an SSC mode as the target SSC mode according to a local policy or through a network data analysis function NWDAF.

[0363] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0364] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0365] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0366] In this embodiment, the service management function may be used to perform at least one of the following:

[0367] Determine the target SSC mode according to at least one of a service request parameter (e.g., a service type and / or relevant data required for the service), subscription data, and a default policy (e.g., a rule for indicating a target SSC mode or indicating a rule for selecting a target SSC mode);

[0368] The target SSC mode is determined through the network data analysis function NWDAF.

[0369] Among them, the default policy can be to instruct the selection of one or more SSC modes allowed in the contract data, or to select one or more SSC modes from the contract data through a rule indication (for example, sorting the SSC modes allowed in the contract data in descending order according to the SSC modes that meet the requirements, selecting the first one or the first few, etc.).

[0370] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0371] In this embodiment, the service management function is used to determine the target SSC mode through NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0372] Therefore, the embodiments of the present application can select or determine a suitable SSC mode according to the application / service scenario.

[0373] The following describes in detail a method for ensuring business continuity in a distributed network architecture through a specific embodiment.

[0374] Exemplary embodiment 1 (SSC mode selection (or determination) process in the service request process, when multiple services have not yet been integrated and one service is requested at a time)

[0375] See also Figure 2 As shown, Figure 2 The following is an interactive diagram of a method for ensuring business continuity in a distributed network architecture provided by an embodiment of the present application. The method for ensuring business continuity in a distributed network architecture provided by this embodiment includes the following steps:

[0376] Step 1: The UE sends a service establishment request to the access network (AN) or the radio access network (RAN), namely (R)AN.

[0377] The service establishment request initiated by the UE includes a requested service type (such as connection service, computing service, data service, intelligent service, security service, etc.); optionally, it can also carry a requested SSC mode (as shown in Table 1) and other parameters corresponding to the service (for example, other parameters required for the service corresponding to the service type).

[0378] Based on the service continuity characteristics required by the application / service for the network service, the UE determines the service type, whether to allow the change of the service anchor point, and whether to allow cross-network nodes, and thus decides the SSC mode requested by the UE according to the information shown in Table 4.1.

[0379] Among them, the business continuity characteristics include not only the service continuity requirements, but also the business type (emergency business has higher requirements for business continuity, IoT devices have low requirements for latency, etc.), terminal mobility (terminals with strong mobility are more inclined to choose SSC mode that can cross network nodes and maintain continuity, and tend to choose network nodes with a larger service range), latency requirements (low latency may mean that they tend to choose to ensure continuity within network nodes), privacy requirements (high privacy may mean that they tend to choose to ensure continuity within network nodes), and other information.

[0380] For example, if the UE has high mobility, in order to avoid high overhead caused by frequent disconnection and re-establishment or establishment and disconnection processes, SSC mode 4, which maintains connection and supports cross-network node connection, is preferred.

[0381] Step 2: After receiving the service establishment request, the access management function (i.e., access and mobility management function AMF) selects the corresponding service management function based on the service type. For example, the connection service selects the session management function SMF, the computing power service selects the computing power orchestration center, the data service selects the data orchestration center, the intelligent service selects the intelligent orchestration center, and the security service selects the security management center; other services are similar and will not be repeated here.

[0382] Step 3: Based on the selection result of step 2, a service context establishment request is initiated to the corresponding network function.

[0383] For example, any of the following items is included (that is, one of multiple steps 3a, 3b, and 3c can be selected. The steps involved in the following embodiment 1 also select steps corresponding to steps 3a, 3b, and 3c. For example, step 3a corresponds to the following step 6a. Others are similar and will not be repeated here.): Step 3a, the access management function sends a connection service (session) context establishment request to the session management function;

[0384] Step 3b: The access management function sends a computing power service context establishment request to the computing power orchestration center;

[0385] Step 3b: The access management function sends a data service context establishment request to the data orchestration center.

[0386] Step 4: The corresponding service management function obtains relevant contract data through the contract data management function (here, the unified data management function (English: Unified Data Management, referred to as: UDM)), and the contract data includes one or more allowed SSC modes. Alternatively, the contract data is updated.

[0387] Step 5: The service management function responds to the access management function and executes other related processes.

[0388] Step 6: The service management function performs SSC mode selection, which means that the service management function performs an operation of determining or selecting the SSC mode.

[0389] For example, in step 6a, the session management function selects SSC mode;

[0390] Step 6b: The computing power orchestration center selects SSC mode;

[0391] Step 6c: The data arrangement center selects SSC mode.

[0392] If the UE request message carries the requested SSC mode, the service management function combines the UE request with the SSC mode allowed by the subscription data. If the SSC mode requested by the UE is within the range allowed by the subscription data, the SSC mode is selected.

[0393] Otherwise, if the UE does not request an SSC mode, or the SSC mode requested by the UE is not within the range allowed by the subscription data, the service management function completes the SSC mode selection based on the local policy or the NWDAF analysis result.

[0394] The local policy may be determined or confirmed based on at least one of the service request parameters, subscription data, and default policy. For example, if the UE requests computing power services, the subscription data allows SSC mode 1\2\3\7\8\9\10\11\12, and the default policy is to sort by the SSC mode that meets the requirements in descending order, then the selection result is SSC mode 7.

[0395] Based on the analysis results of NWDAF, taking the service management function as SMF as an example, SMF requests NWDAF to provide intelligent analysis of SSCmode selection. After receiving the request, NWDAF collects service information, UE equipment information, contract information, core network function NFs information, etc., analyzes one or more SSC modes suitable for the service requested by the UE, and returns it to SMF for reference (this process can also be done through PCF). SMF makes SSC mode selection based on local information and NWDAF analysis results.

[0396] It should be noted that the current 3GPP regulations stipulate that the SSC mode associated with a protocol data unit (PDU) session will not change during the validity period of the PDU session. With 6G, considering the changes in user needs, it is not ruled out that this restriction may be lifted.

[0397] Step 7: The message sent by the service management function to the access management function includes the selected SSC mode, which refers to the target SSC mode.

[0398] For example, in step 7a, the session management function transmits a message to the access management function, including the selected SSCmode;

[0399] Step 7b: The computing power orchestration center transmits a message to the access management function, including the selected SSC mode;

[0400] Step 7c: The data orchestration center transmits a message to the access management function, including the selected SSC mode.

[0401] Step 8: Execute other service establishment related processes.

[0402] Exemplary embodiment 2 (SSC mode selection (or determination) process in the service request process, when multiple services are integrated and multiple services are requested at one time)

[0403] See also Figure 3 As shown, Figure 3 This is an interactive diagram of a method for ensuring business continuity in a distributed network architecture provided by another embodiment of the present application. The method for ensuring business continuity in a distributed network architecture provided by this embodiment includes the following steps:

[0404] Step 1: UE sends a service establishment request to (R)AN.

[0405] The service establishment request initiated by the UE includes one or more requested service types (for example, at least two of connection services, computing power services, data services, intelligent services, security services, etc., which can be expressed here as a list of service types that can be included in the service establishment request); optionally, it can also carry one or more requested SSC modes (which can be expressed here as a list of requested SSC modes that can also be included in the service establishment request), as well as other parameters corresponding to various services (for example, other parameters required for services corresponding to various service types).

[0406] For steps 2-8, see Example 1.

[0407] It should be noted that the difference between the second embodiment and the first embodiment is that, in step 1, the service establishment request initiated by the UE includes one or more requested service types and corresponding multiple requested SSC modes.

[0408] In the second embodiment, steps a, b, and c may be one or more.

[0409] The network function for processing the service establishment request sent by the UE may be an access management function or a new service management function, which is not limited here.

[0410] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes:

[0411] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or, if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, then determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0412] In this embodiment, for any target SSC mode, if the target SSC mode is a certain service type, it is allowed to change the service anchor point, allow to break first and then build, and allow services across network nodes, or it is allowed to change the service anchor point, allow to build first and then break, and allow services across network nodes, such as SSC mode5, SSC mode6, SSC mode11, SSC mode12, SSC mode17, SSC mode18, SSC mode23, SSC mode24, SSC mode29, and SSC mode30 shown in Table 1, determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type. The target network functions here include, for example, target AMF, target SMF, target UPF, computing service function node, computing power orchestration center, data service function node, data orchestration center, network functions for intelligent analysis, network functions for security management, etc.

[0413] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determining of the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type includes:

[0414] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0415] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0416] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0417] In this embodiment, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes, the target SSC mode here is SSC mode 5 shown in Table 1, that is, in the connection service scenario, the service anchor point can be changed, disconnection before reconstruction is allowed, and the service can be allowed to cross network nodes.

[0418] Specifically, when the SMF in the current network node determines to change the current user plane function UPF, it determines to trigger the execution of the target SSC mode process according to the constraint conditions, and sends a session request for the same data network name (English: Data Network Name, abbreviated as: DNN) and single network slice selection auxiliary information (English: Single Network Slice Selection Assistance Information, abbreviated as: S-NSSAI) to the AMF (or a new service management function). After receiving the session request for the same DNN and S-NSSAI sent by the UE, the AMF determines whether the current network node where the AMF is located is connected to the data network corresponding to the DNAI in the target DNAI info according to the locally stored target DNAIinfo; if it is determined that the data network corresponding to the DNAI cannot be accessed, the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0419] AMF (here refers to the AMF in the current network node) sends target DNAI info to the target AMF. When the target AMF receives the new session establishment request, it determines the target SMF in the target network node according to the target DNAI info, and the target SMF determines the target UPF in the target network node.

[0420] Optionally, the method further comprises:

[0421] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0422] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0423] In this embodiment, when the AMF selects the target SMF and the target SMF selects the target UPF, in addition to selecting the target SMF and target UPF that can access the target DNAI based on the existing mechanism, it is also necessary to determine whether to establish a session connection within the new network node or a collaborative session connection involving multiple network nodes based on the SSC mode, UE mobility, service type, etc., so as to determine the relationship between the target SMF and the SMF (here refers to the SMF in the current network node), whether it is necessary to continue to insert the I-UPF, etc. Based on the above results, a session connection of the new network node is established, or a collaborative session connection involving the current network node and the new network node is established.

[0424] For example, for the SSC mode process, the scenario of connecting to the service:

[0425] SSC mode 1-3 may be consistent with the existing mechanism. SSC mode 4-6 may involve different network nodes.

[0426] Among them, the SSC mode 4 anchor point remains unchanged, allowing the execution of the PDU session modification process triggered by the network involving the update of the user plane path across network nodes. For details, see TS23.502 4.3.3. The main difference is that the I-UPF corresponding to the new user plane path may be located in another network node, so the interaction process between network nodes will be involved.

[0427] The main difference between the SSC mode 5 process and the SSC mode 2 process is that it involves interactions across network nodes. One implementation method is:

[0428] Exemplary embodiment 3

[0429] See also Figure 4 As shown, Figure 4 This is an interactive diagram of a method for ensuring business continuity in a distributed network architecture provided by another embodiment of the present application. The method for ensuring business continuity in a distributed network architecture provided by this embodiment includes the following steps:

[0430] Step 1, SMF1 in network node 1 (here, it may refer to the current network node) decides to perform the SSC mode process to determine that changing the UPF may be beneficial. Among them, SMF determines UPF relocation needs to be performed means that SMF determines that the UPF change needs to be performed.

[0431] Here, a time interval T0 is added as a constraint condition. The process is allowed to be triggered again only when the time interval from the last triggering of the process is greater than or equal to T0, so as to avoid more overhead caused by frequent SSC mode processes due to high UE mobility. The value of T0 is based on SSC mode, service type, UE mobility modification, and network status.

[0432] Step 1a. SMF1 receives the target DNAI (DNAI in target DNAI info) from SM-PCF. If PSA cannot connect to this target DNAI, SMF1 will notify AMF1 of the target DNAI info and indicate whether SMF reselection is required. AMF1 stores the target DNAI info and uses it for SMF selection. It can control the UPF connected to the DNAI to the same DNN and S-NSSAI when the next PDU session is established.

[0433] Step 2, execute the PDU session release process, the PDU Session Release Command message includes the PDU Session ID and the release reason Cause, where Cause indicates that the UE needs to re-establish the PDU Session to the same DN.

[0434] Step 3a, UE sends a PDU session establishment request to AMF1.

[0435] Step 3b, when AMF1 receives a session request for the same DNN and S-NSSAI, it determines according to the target DNAI info stored locally in AMF1 that the current network node (here network node 1) cannot access the DNAI, and then selects the target network node and the target AMF.

[0436] Among them, in addition to the existing mechanism, the method for selecting the target network node and the target AMF also needs to judge the node type (central node, distributed node) and service range of the selected network node (UE with high mobility tends to choose a network node with a larger service range) based on SSC mode, UE mobility, service type, etc.

[0437] Step 3c, AMF1 sends target DNAI info to the selected AMF2. This information is used by AMF2 to perform SMF selection when it receives a new session establishment request.

[0438] When AMF2 selects SMF2 and SMF2 selects UPF2, in addition to selecting SMF2 and UPF2 that can access target DNAI based on the existing mechanism, it is also necessary to determine whether the session connection is established in a new network node or a collaborative session connection involving multiple network nodes based on SSC mode, UE mobility, service type, etc., so as to determine the relationship between SMF2 and SMF1, whether it is necessary to continue to insert I-UPF, etc.

[0439] Step 3, according to the above result, establish a session connection of network node 2, or a collaborative session connection involving network node 1 and network node 2. Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determination of the target network node for supporting cross-network nodes and the corresponding target network function required in the scenario of the requested service type includes:

[0440] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0441] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0442] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0443] In this embodiment, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes, the target SSC mode here is SSC mode 5 shown in Table 1, that is, in the connection service scenario, the service anchor point can be changed, disconnection before reconstruction is allowed, and the service can be allowed to cross network nodes.

[0444] Specifically, the SMF in the current network node sends target DNAIinfo to the AMF (or the new service management function), and the AMF determines whether the current network node where the AMF is located is connected to the data network corresponding to the DNAI in the target DNAIinfo based on the target DNAI info; if it is determined that the data network corresponding to the DNAI cannot be accessed, the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node are determined based on at least one of the target SSCmode, the mobility of the UE, and the service type of the UE.

[0445] AMF (here refers to the AMF in the current network node) sends target DNAI info to the target AMF. When the target AMF receives the new session establishment request, it determines the target SMF in the target network node according to the target DNAI info, and the target SMF determines the target UPF in the target network node.

[0446] The main difference between the SSC mode 5 process and the SSC mode 2 process is that it involves interactions across network nodes. Another implementation method is:

[0447] Exemplary, Example 4

[0448] See also Figure 5 As shown, Figure 5 This is an interactive diagram of a method for ensuring business continuity in a distributed network architecture provided by another embodiment of the present application. The method for ensuring business continuity in a distributed network architecture provided by this embodiment includes the following steps:

[0449] Step 1, SMF1 in network node 1 (here, it may refer to the current network node) decides to perform the SSC mode process to determine that changing the UPF may be beneficial. Among them, SMF determines UPF relocation needs to be performed means that SMF determines that the UPF change needs to be performed.

[0450] Here, a time interval T0 is added as a constraint condition. The process is allowed to be triggered again only when the time interval from the last triggering of the process is greater than or equal to T0, so as to avoid more overhead caused by frequent SSC mode processes due to high UE mobility. The value of T0 is based on SSC mode, service type, UE mobility modification, and network status.

[0451] In step 1a, SMF1 receives the target DNAI (DNAI in target DNAI info) from SM-PCF. If PSA cannot connect to this target DNAI, SMF1 will notify AMF1 of the target DNAI info and indicate whether SMF reselection is required. AMF1 stores the target DNAI info and uses it for SMF selection. It can control the UPF connected to the DNAI to the same DNN and S-NSSAI when the next PDU session is established.

[0452] Step 1b, when the target DNAI info received by AMF1 shows that the current network node (here, network node 1) cannot access the DNAI, the target network node selection and the target AMF selection are performed. The target network node and the target AMF selection method are applicable to the existing mechanism.

[0453] Step 1c, AMF1 sends target DNAI info to the selected AMF2, which is used by AMF2 to perform SMF selection when it receives a new session establishment request.

[0454] Step 2, the PDU Session Release Command (here refers to the PDU session release instruction or command) carries the network node identifier and AMF identifier selected by AMF1.

[0455] Step 3, the PDU Session Establishment Request (here refers to the PDU session establishment request) carries the network node identifier and the AMF identifier, which is used for RAN to quickly complete the request forwarding after receiving the request. After AMF2 receives the session request for the same DNN and S-NSSAI, it completes the selection of SMF2 according to the locally stored target DNAI info, and further instructs SMF2 to complete the selection of UPF2.

[0456] For example, the main difference between the SSC mode 6 process and the SSC mode 3 process is that it involves interaction across network nodes. The main difference is similar to the above-mentioned SSC mode 5 process, which will not be repeated here.

[0457] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the determining of the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type includes:

[0458] If a third message sent by the current computing power orchestration center is received, the operation of releasing the computing power service between the UE and the current computing power service function node is triggered; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0459] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0460] Among them, the target computing power service function node is the target network function.

[0461] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0462] For computing service scenarios, SSC mode 7-9 is similar to SSC mode 1-3 corresponding to connection services. The difference is that the network functions involved are changed from SMF and UPF to computing orchestration center and computing service node, and the trigger factor is that the computing orchestration center decides to change the computing service node.

[0463] For example, the fifth embodiment (SSC mode 8 is used as an example).

[0464] See also Figure 6 As shown, Figure 6 This is an interactive diagram of a method for ensuring service continuity in a distributed network architecture provided by another embodiment of the present application. The method for ensuring service continuity in a distributed network architecture provided by this embodiment includes the following steps:

[0465] Step 1: Computing power orchestration center 1 decides to modify the computing power service node (i.e., computing power service function node) due to changes in the load of the current computing power service node (here referring to computing power service node 1) or changes in the business demand for computing power resources.

[0466] Step 1a, message interaction between AMF and computing power orchestration center 1 (including target DNAI info).

[0467] Step 2: The computing power orchestration center 1 triggers the computing power service release process, which means that the computing power orchestration center 1 triggers the release of the computing power service between the UE and the computing power service node 1.

[0468] Step 3: Create a computing service between the UE and computing service node 2.

[0469] It should be noted that other service types and corresponding SSC mode processes are similar to those in the above embodiment and will not be described in detail here.

[0470] For example, if business continuity does not need to be limited to the range of network nodes, the above-mentioned SSC mode 1-3 and SSC mode 4-6 can be merged (similarly, SSC mode 7-9 and SSC mode 10-12 can be merged; SSC mode 13-15 and SSC mode 16-18 can be merged; SSC mode 19-21 and SSC mode 22-24 can be merged; SSC mode 25-27 and SSC mode 28-30 can be merged, and other service types are similar and will not be repeated here), that is, only new service capabilities are expanded, and there is no restriction on whether cross-network nodes are allowed.

[0471] In this application, SSC mode is defined based on service type (connection, computing power, data, intelligence, security, etc.), whether to allow changes to service anchor points (yes / no), allowed service continuity (maintain continuity, break first and then build, build first and then break), whether to allow cross-network nodes (yes / no), etc. The original SSC mode 1-3 is updated to ensure the continuity of connection capabilities within the network node: SSC mode 4-6 is added to support the construction of connections between network nodes to ensure connection continuity. According to the service types in different dimensions such as computing power, data, intelligence, and security, SSC modes similar to SSC mode 1-6 are designed. As shown in Table 1 above, SSC mode 7-12 is the SSC mode when the service type is computing power service, SSC mode 13-18 is the SSC mode when the service type is data service, SSC mode 19-24 is the SSC mode when the service type is only intelligent service, and SSC mode 25-30 is the SSC mode when the service type is security service. Supports the combination of the embodiments corresponding to the above service types, for example, an application or business involves both connection services and computing services. Supports further refinement of the above solutions, such as further refinement of the SSC mode based on the type of network nodes (central nodes or distributed nodes), the characteristics of network nodes (such as the size of the service range), the number of cross-network nodes, etc., to achieve more accurate business continuity guarantee solution design.

[0472] Therefore, a more fine-grained SSC mode mechanism is used to meet the characteristics of distributed network architecture and the business continuity assurance needs of future diversified services, and to meet their needs in terms of security, latency, mobility, etc.

[0473] Specifically, (1) different SSC modes are designed with related mechanisms within and between network nodes to better suit 6G distributed network architecture scenarios; (2) corresponding business continuity guarantee mechanisms are provided for 6G's new connection+ services, including business continuity in data, computing power, intelligence, security, etc.; (3) a more fine-grained SSC mode design is used to meet diverse business continuity requirements; (4) the above designs can improve network performance and user experience.

[0474] Figure 7 A flow chart of a method for ensuring business continuity under a distributed network architecture provided in another embodiment of the present application, wherein the execution subject of the method for ensuring business continuity under the distributed network architecture is a service management function, and the method for ensuring business continuity under the distributed network architecture may include the following steps:

[0475] Step 201: Receive a service context establishment request message sent by the AMF in the current network node, where the service context establishment request message is sent by the AMF according to a determined requested service type;

[0476] Step 202: Determine the selected target SSC mode according to the service context establishment request message;

[0477] Step 203: Send a first message to the AMF, where the first message includes the target SSC mode.

[0478] In an embodiment of the present application, the service management function determines the target SSC mode based on the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for 6G distributed network architecture scenarios. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0479] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0480] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0481] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0482] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0483] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0484] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0485] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0486] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0487] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0488] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0489] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0490] If the requested service type is a security service, the service management function is a security management center.

[0491] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0492] Optionally, determining the selected target SSC mode according to the service context establishment request message includes:

[0493] If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, for any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode; when it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF;

[0494] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0495] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; the target SSC mode determined according to the local policy or by a network data analysis function NWDAF includes:

[0496] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0497] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0498] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes:

[0499] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0500] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0501] Another embodiment of the present application provides a method for ensuring service continuity in a distributed network architecture. The execution subject of the method for ensuring service continuity in a distributed network architecture is a UE. The method for ensuring service continuity in a distributed network architecture may include the following steps:

[0502] Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type;

[0503] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0504] In an embodiment of the present application, the UE sends a service establishment request message to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it can effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0505] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0506] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0507] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0508] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0509] Optionally, the method further comprises:

[0510] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0511] Optionally, determining the requested SSC mode includes:

[0512] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0513] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0514] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is an SMF in the current network node, and the method further includes:

[0515] When it is determined to change the current UPF, the triggering of the target SSC mode process is determined according to the constraint conditions, and a second message is sent to the AMF, where the second message includes target DNAI info.

[0516] Optionally, determining, by the AMF in the current network node, a target network node for supporting a cross-network node service and a corresponding target network function required in a scenario of the requested service type includes:

[0517] If it is determined by the AMF according to the target DNAI info in the second message that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, a target network node for accessing the data network corresponding to the DNAI and a target AMF in the target network node are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0518] The AMF is used to send the target DNAI info to the target AMF after determining the target network node and the target AMF, wherein the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0519] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0520] Optionally, the method further comprises:

[0521] Determining, by the AMF, a method for establishing a session connection according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0522] The method for establishing the session connection is to establish a session connection within the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node; the method for establishing the session connection is used to support the establishment of a session connection of the corresponding network node.

[0523] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is the current computing power orchestration center, and the method further includes:

[0524] Determine to modify the computing service function node based on the load change information of the current computing service node or the change in the business demand for computing resources;

[0525] Send a third message to the AMF, where the third message is used to support the AMF in triggering the release of the computing service between the UE and the current computing service node, and instruct the AMF to determine the target network node, the target AMF in the target network node, the target computing orchestration center, and the corresponding target computing service function node according to the targetDNAI info included in the third message, and create a computing service between the UE and the target computing service function node;

[0526] Among them, the target computing power service function node is the target node.

[0527] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0528] It should be noted here that the business continuity guarantee method under the distributed network architecture can be referred to in its specific implementation process. Figure 1-Figure 7 The embodiments shown here will not be described in detail in detail.

[0529] Figure 8 A schematic diagram of the structure of a service continuity guarantee device under a distributed network architecture provided in an embodiment of the present application, such as Figure 8 As shown, the service continuity guarantee device under the distributed network architecture provided in this embodiment is applied to AMF, and the service continuity guarantee device under the distributed network architecture provided in this embodiment includes: a transceiver 800, which is used to receive and send data under the control of a processor 810.

[0530] Among them, Figure 8In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 810 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 800 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 810 when performing operations.

[0531] The processor 810 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0532] In this embodiment, the memory 820 is used to store a computer program; the transceiver 800 is used to send and receive data under the control of the processor; the processor 810 is used to read the computer program in the memory and perform the following operations:

[0533] Determine the type of service requested by the UE;

[0534] Sending a service context establishment request message to a corresponding service management function according to the requested service type;

[0535] Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0536] In an embodiment of the present application, by determining the requested service type, the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0537] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0538] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0539] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0540] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0541] Optionally, the processor 810 is configured to, when determining the service type requested by the terminal UE, specifically include:

[0542] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0543] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0544] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0545] Optionally, the processor 810 is configured to, when sending a service context establishment request message to a corresponding service management function according to the requested service type, specifically include:

[0546] If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF;

[0547] If the requested service type is a computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center;

[0548] If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0549] If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0550] If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0551] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0552] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0553] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0554] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0555] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0556] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0557] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0558] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the processor 810 is further configured to perform the following operations:

[0559] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or, if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, then determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0560] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor 810 is used to determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0561] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0562] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0563] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0564] Optionally, if the service type is a connected service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reconstructs the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor 810 is used to determine the target network node for supporting cross-network nodes and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0565] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0566] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0567] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0568] Optionally, the processor 810 is further configured to perform the following operations:

[0569] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0570] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0571] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the processor 810 is used to determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type, specifically including:

[0572] If a third message sent by the current computing power orchestration center is received, the operation of releasing the computing power service between the UE and the current computing power service function node is triggered; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0573] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0574] Among them, the target computing power service function node is the target network function.

[0575] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0576] It should be noted here that the service continuity assurance device under the distributed network architecture provided in the present application can implement all the method steps implemented by the method embodiment described in the first aspect above, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0577] Fig. 9 A schematic diagram of the structure of a service continuity assurance device under a distributed network architecture provided in another embodiment of the present application. The service continuity assurance device under the distributed network architecture provided in this embodiment is applied to AMF. The service continuity assurance device 900 under the distributed network architecture provided in this embodiment includes:

[0578] The determining unit 901 is configured to determine a service type requested by the UE;

[0579] The sending unit 902 is used to send a service context establishment request message to the corresponding service management function according to the requested service type;

[0580] The receiving unit 903 is used to receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0581] In an embodiment of the present application, AMF (or other network functions that perform access and mobility management or service management) determines the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for 6G distributed network architecture scenarios. Therefore, it can effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0582] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0583] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0584] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0585] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0586] Optionally, the determining unit 901 is specifically configured to:

[0587] A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

[0588] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0589] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0590] Optionally, the sending unit 902 is specifically configured to:

[0591] When the requested service type is a connection service, determining that the corresponding service management function is a session management function SMF, and sending a connection service context establishment request message to the SMF;

[0592] When the requested service type is a computing power service, determining that the corresponding service management function is a computing power orchestration center, and sending a computing power service context establishment request message to the computing power orchestration center;

[0593] When the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center;

[0594] When the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center;

[0595] When the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

[0596] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0597] Optionally, if the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data;

[0598] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

[0599] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy;

[0600] The service request parameters include at least one of the following: service type, relevant data required for the service;

[0601] The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

[0602] Optionally, the target SSC mode is determined by the service management function through NWDAF based on service information, UE equipment information, subscription information and at least one of the network functions NFs of the core network.

[0603] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the device further includes: a first processing unit; the first processing unit is configured to:

[0604] For any target SSC mode, when the network first releases the service provided to the user and reestablishes the service and allows the change of the service anchor point and allows the service to cross network nodes in the scenario of the corresponding requested service type in the target SSC mode, or when the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes in the scenario of the corresponding requested service type in the target SSC mode, determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

[0605] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0606] After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition;

[0607] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node;

[0608] The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

[0609] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0610] When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node;

[0611] Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0612] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0613] Optionally, the device further includes: a second processing unit; the second processing unit is configured to:

[0614] Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node;

[0615] According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

[0616] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes; the first processing unit is specifically used to:

[0617] Upon receiving a third message sent by the current computing power orchestration center, triggering an operation of releasing the computing power service between the UE and the current computing power service function node; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info;

[0618] According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node;

[0619] Among them, the target computing power service function node is the target network function.

[0620] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0621] It should be noted here that the service continuity assurance device under the distributed network architecture provided in the present application can implement all the method steps implemented by the method embodiment described in the first aspect above, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0622] The service continuity guarantee device under the distributed network architecture provided in the embodiment of the present application is applied to the service management function. The service continuity guarantee device under the distributed network architecture provided in the embodiment of the present application includes:

[0623] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer program in the memory and performing the following operations:

[0624] Memory, transceiver, processor:

[0625] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0626] Receiving a service context establishment request message sent by the AMF in the current network node, where the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF;

[0627] Determining a selected target SSC mode according to the service context establishment request message;

[0628] Send a first message to the AMF, where the first message includes the target SSC mode.

[0629] In an embodiment of the present application, the target SSC mode is determined according to the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0630] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0631] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0632] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0633] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0634] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0635] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0636] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0637] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0638] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0639] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0640] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0641] If the requested service type is a security service, the service management function is a security management center.

[0642] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0643] Optionally, the processor is configured to, when determining the selected target SSC mode according to the service context establishment request message, specifically include:

[0644] If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, for any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode; when it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF;

[0645] If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0646] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; and the processor is configured to, when determining the target SSC mode according to the local policy or through a network data analysis function NWDAF, specifically include:

[0647] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0648] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0649] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the processor is further configured to perform the following operations:

[0650] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0651] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reconstructs the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is an SMF in the current network node, and the processor is further used to perform the following operations:

[0652] When it is determined to change the current UPF, the triggering of the target SSC mode process is determined according to the constraint conditions, and a second message is sent to the AMF, where the second message includes target DNAI info.

[0653] Optionally, the processor is configured to, when determining, through the AMF in the current network node, a target network node for supporting a cross-network node service and a corresponding target network function required in a scenario of the requested service type, specifically include:

[0654] If it is determined by the AMF according to the target DNAI info in the second message that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, a target network node for accessing the data network corresponding to the DNAI and a target AMF in the target network node are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0655] The AMF is used to send the target DNAI info to the target AMF after determining the target network node and the target AMF, wherein the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0656] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0657] Optionally, the processor is further configured to perform the following operations:

[0658] Determining, by the AMF, a method for establishing a session connection according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0659] The method for establishing the session connection is to establish a session connection within the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node; the method for establishing the session connection is used to support the establishment of a session connection of the corresponding network node.

[0660] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is the current computing power orchestration center, and the processor is further used to perform the following operations:

[0661] Determine to modify the computing service function node based on the load change information of the current computing service node or the change in the business demand for computing resources;

[0662] Send a third message to the AMF, where the third message is used to support the AMF in triggering the release of the computing service between the UE and the current computing service node, and instruct the AMF to determine the target network node, the target AMF in the target network node, the target computing orchestration center, and the corresponding target computing service function node according to the targetDNAI info included in the third message, and create a computing service between the UE and the target computing service function node;

[0663] Among them, the target computing power service function node is the target node.

[0664] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0665] It should be noted that the physical device corresponding to the core network side (here refers to the service management function side) is as follows Figure 8As shown in , all the method steps implemented by the core network side method embodiment can be implemented, and the same technical effect can be achieved. The parts and beneficial effects that are the same as those in method embodiment () will not be described in detail here.

[0666] Fig.10 A schematic diagram of a structure of a service continuity assurance device under a distributed network architecture provided in another embodiment of the present application, wherein the device is applied to a service management function, and the service continuity assurance device 1000 under the distributed network architecture includes:

[0667] The receiving unit 1001 is configured to receive a service context establishment request message sent by the AMF in the current network node, where the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF;

[0668] A determining unit 1002 is configured to determine a selected target SSCmode according to the service context establishment request message;

[0669] The sending unit 1003 is used to send a first message to the AMF, where the first message includes the target SSCmode.

[0670] In an embodiment of the present application, the service management function determines the target SSC mode based on the requested service type in the received service context establishment request message, thereby implementing different SSC modes required for different service types and being more suitable for 6G distributed network architecture scenarios. Therefore, it is possible to effectively and accurately provide SSC modes corresponding to different service types, thereby meeting the diverse continuity requirements of different applications or services of UE.

[0671] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0672] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0673] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0674] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0675] Optionally, the requested service type or information used to indicate the requested service type is carried in a service establishment request message sent by the UE to the AMF.

[0676] Optionally, the service establishment request message further includes a requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode;

[0677] The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

[0678] Optionally, if the requested service type is a connection service, the service management function is a session management function SMF;

[0679] If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information;

[0680] If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing;

[0681] If the requested service type is an intelligent service, the service management function is an intelligent orchestration center;

[0682] If the requested service type is a security service, the service management function is a security management center.

[0683] In the embodiment of the present application, one (or one) requested service type corresponds to one service management function, wherein one business or application may include multiple service types, which may correspond to multiple service management functions, or multiple service types may correspond to the same service management function, i.e., multiple service types correspond to one service management function. It is possible to realize a combination that supports the continuity of multiple services.

[0684] Optionally, the determining unit 1002 is specifically configured to:

[0685] The service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one. For any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode. When it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0686] When the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

[0687] Optionally, the local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; and the determining unit 1002 is specifically configured to:

[0688] Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or,

[0689] The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

[0690] Optionally, the target SSC mode is an SSC mode selected under at least one requested service type, and the device further includes: a first processing unit; the first processing unit is configured to:

[0691] For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

[0692] Optionally, if the service type is a connection service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and reconstructs the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is an SMF in the current network node, and the device further includes: a second processing unit; the second processing unit is used to:

[0693] When it is determined to change the current UPF, the triggering of the target SSC mode process is determined according to the constraint conditions, and a second message is sent to the AMF, where the second message includes target DNAI info.

[0694] Optionally, the first processing unit is specifically configured to:

[0695] If it is determined by the AMF according to the target DNAI info in the second message that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, a target network node for accessing the data network corresponding to the DNAI and a target AMF in the target network node are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0696] The AMF is used to send the target DNAI info to the target AMF after determining the target network node and the target AMF, wherein the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI;

[0697] Among them, the target AMF, target SMF and target UPF are all the target network functions.

[0698] Optionally, the device further includes: a third processing unit; the third processing unit is configured to:

[0699] Determining, by the AMF, a method for establishing a session connection according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE;

[0700] The method for establishing the session connection is to establish a session connection within the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node; the method for establishing the session connection is used to support the establishment of a session connection of the corresponding network node.

[0701] Optionally, if the service type is a computing power service, and the target SSC mode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service and allows the service anchor point to be changed and allows the service to cross network nodes, the service management function is the current computing power orchestration center, and the device further includes: a fourth processing unit; the fourth processing unit is used to:

[0702] Determine to modify the computing service function node based on the load change information of the current computing service node or the change in the business demand for computing resources;

[0703] Send a third message to the AMF, where the third message is used to support the AMF in triggering the release of the computing service between the UE and the current computing service node, and instruct the AMF to determine the target network node, the target AMF in the target network node, the target computing orchestration center, and the corresponding target computing service function node according to the targetDNAI info included in the third message, and create a computing service between the UE and the target computing service function node;

[0704] Among them, the target computing power service function node is the target node.

[0705] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0706] It should be noted here that the service continuity assurance device under the distributed network architecture provided in the present application can implement all the method steps implemented by the method embodiment described in the second aspect above, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0707] Fig.11 A schematic diagram of a structure of a service continuity guarantee device in a distributed network architecture provided by another embodiment of the present application is shown as follows: Fig.11 As shown, the service continuity guarantee device under the distributed network architecture provided in this embodiment is applied to UE, and the service continuity guarantee device under the distributed network architecture provided in this embodiment includes: a transceiver 1100, which is used to receive and send data under the control of a processor 1110.

[0708] Among them, Fig.11 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1110 and various circuits of memory represented by memory 1120 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1100 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and other transmission media. For different user devices, the user interface 1130 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0709] The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1110 when performing operations.

[0710] Optionally, the processor 1110 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0711] The processor 1110 is used to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions by calling the program stored in the memory 1120. The processor 1110 and the memory 1120 can also be arranged physically separately.

[0712] In this embodiment, the memory 1120 is used to store a computer program; the transceiver 1100 is used to send and receive data under the control of the processor; the processor 1110 is used to read the computer program in the memory and perform the following operations:

[0713] Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type;

[0714] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0715] In an embodiment of the present application, a service establishment request message is sent to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0716] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0717] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0718] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0719] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0720] Optionally, the processor 1110 is further configured to perform the following operations:

[0721] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0722] Optionally, the processor 1110 is configured to, when determining the requested SSC mode, specifically include:

[0723] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0724] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0725] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0726] It should be noted here that the service continuity assurance device under the distributed network architecture provided in the present application can implement all the method steps implemented by the method embodiment described in the third aspect above, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0727] Another embodiment of the present application provides a service continuity guarantee device in a distributed network architecture, the device is applied to a UE, and the device includes:

[0728] A sending unit, configured to send a service establishment request message to the AMF in the current network node, wherein the service establishment request message includes the requested service type or information indicating the requested service type;

[0729] The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

[0730] In an embodiment of the present application, a service establishment request message is sent to the AMF in the current network node, and the AMF sends a service context establishment request message to the corresponding service management function according to the requested service type, and the corresponding service management function determines the target SSC mode based on the requested service type, thereby realizing different SSC modes required for different service types, which is more suitable for the 6G distributed network architecture scenario. Therefore, it is possible to effectively and accurately provide the corresponding SSC modes for different service types, thereby meeting the diverse continuity requirements of different applications or services of the UE.

[0731] Optionally, the requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

[0732] In the embodiment of the present application, it is possible to support services corresponding to various types of requested services, such as connection services, computing services, data services, intelligent services, and security services, etc. Therefore, the service continuity requirements will also be expanded from connection continuity to multi-dimensional continuity guarantees such as connection, computing power, data, intelligence, and security, and support a combination of multiple service continuity, thereby meeting the diverse continuity requirements of different UE applications or services.

[0733] Optionally, for any requested service type, the target SSC mode includes any of the following: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

[0734] In an embodiment of the present application, the SSC mode is further refined, that is, the SSC mode is defined, based on the service type (for example, connection, computing power, data, intelligence, security, etc.), whether the service anchor point is allowed to be changed (yes / no), the allowed service continuity (maintain continuity, disconnect first and then rebuild, build first and then disconnect), and whether the service is allowed to cross network nodes (yes / no), so as to achieve support for multi-dimensional continuity assurance.

[0735] Optionally, the device further includes: a determining unit; the determining unit is configured to:

[0736] Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

[0737] Optionally, the determining unit is specifically configured to:

[0738] Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes;

[0739] The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

[0740] In the embodiments of the present application, a finer-grained SSC mode mechanism is used to meet the characteristics of the distributed network architecture and the business continuity assurance needs of future diversified services, meet their needs in terms of security, latency, mobility, etc., and improve network performance and user experience.

[0741] It should be noted here that the service continuity assurance device under the distributed network architecture provided in the present application can implement all the method steps implemented by the method embodiment described in the third aspect above, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0742] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0743] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application.

[0744] The embodiment of the present application further provides a non-transitory readable storage medium. The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute any of the above method embodiments.

[0745] Among them, the non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0746] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0747] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0748] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0749] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for ensuring business continuity in a distributed network architecture, characterized in that: Applied to access and mobility management function AMF, the method comprises: Determine the service type requested by the terminal UE; Sending a service context establishment request message to a corresponding service management function according to the requested service type; Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

2. The method according to claim 1, characterized in that: The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

3. The method according to claim 1 or 2, characterized in that: For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

4. The method according to claim 1, characterized in that: The determining the service type requested by the terminal UE includes: A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

5. The method according to claim 4, characterized in that The service establishment request message also includes the requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode; The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether the cross-network node is allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

6. The method according to claim 1 or 2, characterized in that: The sending a service context establishment request message to a corresponding service management function according to the requested service type includes: If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF; If the requested service type is computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center; If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center; If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center; If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

7. The method according to claim 1, characterized in that If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, the target SSC mode corresponding to any requested SSC mode is determined by the service management function using the requested SSC mode as the target SSC mode when determining that the requested SSC mode is within the SSC mode range allowed by the subscription data, or is determined by the service management function according to a local policy or by a network data analysis function NWDAF when determining that the requested SSC mode is not within the SSC mode range allowed by the subscription data; If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined by the service management function according to a local policy or by a network data analysis function NWDAF.

8. The method according to claim 7, characterized in that The local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; The service request parameters include at least one of the following: service type, relevant data required for the service; The default policy is used to indicate a target SSC mode or a rule for selecting a target SSC mode.

9. The method according to claim 7 or 8, characterized in that: The target SSC mode is determined by the service management function through NWDAF based on service information, UE device information, subscription information and at least one of the network functions NFs of the core network.

10. The method according to claim 1, characterized in that The target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes: For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or, if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, then determine the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type.

11. The method according to claim 10, characterized in that If the service type is a connected service, and the target SSCmode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; The determining of a target network node for supporting a cross-network node service and a corresponding target network function required in a scenario of the requested service type includes: After receiving a session request for the same data network name DNN and single network slice selection auxiliary information S-NSSAI sent by the UE, according to the locally stored target data network access identifier information target DNAI info, if it is determined that the current network node where the AMF is located cannot access the data network corresponding to the data network access identifier DNAI in the target DNAI info, determine the target network node for accessing the data network corresponding to the DNAI and the target AMF in the target network node; wherein the session request is received after the SMF in the current network node determines to change the current user plane function UPF and determines to trigger the execution of the target SSC mode process according to the constraint condition; Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node when receiving the new session establishment request and to instruct the target SMF to determine the target UPF in the target network node; The target network node and the target AMF are determined based on at least one of the target SSC mode, the mobility of the UE, and the service type of the UE.

12. The method according to claim 10, characterized in that If the service type is a connected service, and the target SSCmode is an SSC mode in which the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed and allows the service to cross network nodes; The determining of a target network node for supporting cross-network nodes and a corresponding target network function required in a scenario of the requested service type includes: When receiving a second message sent by the SMF in the current network node where the AMF is located, according to the target DNAI info in the second message, if it is determined that the current network node cannot access the data network corresponding to the DNAI in the target DNAI info, determine the target network node for accessing the network corresponding to the DNAI and the target AMF in the target network node; Sending the target DNAI info to the target AMF, where the target DNAI info is used to instruct the target AMF to determine the target SMF in the target network node according to the target DNAI info when receiving the new session establishment request, and to instruct the target SMF to determine the target UPF in the target network node; the new session establishment request is used to indicate a session request for the same DNN and S-NSSAI; Among them, the target AMF, target SMF and target UPF are all the target network functions.

13. The method according to claim 11 or 12, characterized in that: The method further comprises: Determine a session connection establishment method according to at least one of the target SSC mode, the mobility of the UE, and the service type of the UE; wherein the session connection establishment method is to establish a session connection in the target network node or to establish a collaborative session connection of multiple network nodes including at least the current network node and the target network node; According to the determined session connection establishment mode, a session connection of a corresponding network node is established.

14. The method according to claim 10, characterized in that If the service type is computing power service, and the target SSCmode is an SSC mode in which the network first releases the service provided to the user and rebuilds the service, and allows the service anchor point to be changed and allows the service to cross network nodes; The determining of a target network node for supporting a cross-network node service and a corresponding target network function required in a scenario of the requested service type includes: If a third message sent by the current computing power orchestration center is received, the operation of releasing the computing power service between the UE and the current computing power service function node is triggered; wherein the third message is sent by the current computing power orchestration center when determining to modify the computing power service function node based on the load change information of the current computing power service function node or the information that the demand for computing power resources of the business has changed, and the third message includes target DNAI info; According to the target DNAI info, determine the target network node, the target AMF in the target network node, the target computing power orchestration center and the corresponding target computing power service function node, and create a computing power service between the UE and the target computing power service function node; Among them, the target computing power service function node is the target network function.

15. A method for ensuring business continuity in a distributed network architecture, characterized in that: Applied to the service management function, the method comprises: Receiving a service context establishment request message sent by the AMF in the current network node, wherein the service context establishment request message is sent by the AMF according to the determined requested service type; Determining a selected target SSC mode according to the service context establishment request message; Send a first message to the AMF, where the first message includes the target SSC mode.

16. The method according to claim 15, characterized in that The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

17. The method according to claim 15 or 16, characterized in that For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

18. The method according to claim 15, characterized in that The requested service type or information used to indicate the requested service type is carried in the service establishment request message sent by the UE to the AMF.

19. The method according to claim 18, characterized in that The service establishment request message also includes the requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode; The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

20. The method according to claim 15 or 16, characterized in that If the requested service type is a connection service, the service management function is a session management function SMF; If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information; If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing; If the requested service type is an intelligent service, the service management function is an intelligent orchestration center; If the requested service type is a security service, the service management function is a security management center.

21. The method according to claim 15, characterized in that The step of determining the selected target SSC mode according to the service context establishment request message includes: If the service context establishment request message includes a requested SSC mode, and the requested SSC mode is at least one, for any requested SSC mode, when it is determined that the requested SSC mode is within the SSC mode range allowed by the subscription data, the requested SSC mode is used as the target SSC mode; when it is determined that the requested SSC mode is not within the SSC mode range allowed by the subscription data, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF; If the service context establishment request message does not include the requested SSC mode, the target SSC mode is determined according to a local policy or through a network data analysis function NWDAF.

22. The method according to claim 21, characterized in that The local policy is a policy for supporting determination of a target SSC mode based on at least one of a service request parameter, subscription data, and a default policy; The target SSC mode determined according to the local policy or by the network data analysis function NWDAF includes: Determine the target SSC mode according to at least one of a service request parameter, subscription data, and a default policy; wherein the service request parameter includes at least one of the following: a service type, and relevant data required for the service, and the default policy is used to indicate the target SSC mode or indicate a rule for selecting the target SSC mode; or, The target SSC mode is determined by NWDAF based on service information, UE device information, subscription information, and at least one of the network functions NFs of the core network.

23. The method according to claim 15, characterized in that The target SSC mode is an SSC mode selected under at least one requested service type, and the method further includes: For any target SSC mode, if the target SSC mode, in the scenario of the corresponding requested service type, the network first releases the service provided to the user and re-establishes the service and allows the change of the service anchor point and allows the service to cross network nodes, or if the target SSC mode, in the scenario of the corresponding requested service type, the network first establishes other services before releasing the service provided to the user and allows the change of the service anchor point and allows the service to cross network nodes, the target network node for supporting cross-network node services and the corresponding target network function required in the scenario of the requested service type are determined through the AMF in the current network node.

24. A method for ensuring business continuity in a distributed network architecture, characterized in that: The method is applied to a UE, and the method includes: Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type; The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

25. The method according to claim 24, characterized in that The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

26. The method according to claim 24 or 25, characterized in that For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

27. The method according to claim 24, characterized in that The method further comprises: Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

28. The method according to claim 27, characterized in that The determining the requested SSC mode includes: Determine, according to at least one of its own mobility characteristics, the mobility characteristics of the carrier where the UE is located, and the service continuity characteristics required by the application or service for the network service, the service type, whether to allow the change of the service anchor point, the allowed service continuity, and whether to allow cross-network nodes; The requested SSC mode is determined according to the service type, the result of whether the service anchor point is allowed to be changed, the result of the allowed service continuity, and the result of whether the cross-network node is allowed.

29. A device for ensuring business continuity in a distributed network architecture, characterized in that: The device is applied to AMF, and the device comprises: A determination unit, configured to determine a service type requested by the UE; A sending unit, configured to send a service context establishment request message to a corresponding service management function according to the requested service type; A receiving unit is used to receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

30. A service continuity guarantee device under a distributed network architecture, characterized in that: The device is applied to a service management function, and the device comprises: A receiving unit, configured to receive a service context establishment request message sent by the AMF in the current network node, wherein the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF; a determining unit, configured to determine a selected target SSC mode according to the service context establishment request message; A sending unit is used to send a first message to the AMF, where the first message includes the target SSC mode.

31. A service continuity guarantee device under a distributed network architecture, characterized in that: The device is applied to a UE, and the device includes: A sending unit, configured to send a service establishment request message to the AMF in the current network node, wherein the service establishment request message includes the requested service type or information indicating the requested service type; The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

32. A service continuity guarantee device under a distributed network architecture, characterized in that: The device is applied to AMF, and the device includes a memory, a transceiver, and a processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Determine the type of service requested by the UE; Sending a service context establishment request message to a corresponding service management function according to the requested service type; Receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

33. The device according to claim 32, characterized in that The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

34. The device according to claim 32 or 33, characterized in that For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

35. The device according to claim 32, characterized in that The processor is used to determine the service type requested by the terminal UE, specifically including: A service establishment request message sent by a UE is received, where the service establishment request message includes a requested service type or information indicating the requested service type.

36. The device according to claim 32 or 33, characterized in that The processor is configured to, when sending a service context establishment request message to a corresponding service management function according to the requested service type, specifically include: If the requested service type is a connection service, determine that the corresponding service management function is a session management function SMF, and send a connection service context establishment request message to the SMF; If the requested service type is a computing power service, determine that the corresponding service management function is a computing power orchestration center, and send a computing power service context establishment request message to the computing power orchestration center; If the requested service type is a data service, determining that the corresponding service management function is a data orchestration center, and sending a data service context establishment request message to the data orchestration center; If the requested service type is an intelligent service, determining that the corresponding service management function is an intelligent orchestration center, and sending an intelligent service context establishment request message to the intelligent orchestration center; If the requested service type is a security service, the corresponding service management function is determined to be a security management center, and a security service context establishment request message is sent to the security management center.

37. A device for ensuring business continuity in a distributed network architecture, characterized in that: The device is applied to service management functions, and includes: a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving a service context establishment request message sent by the AMF in the current network node, where the service context establishment request message is sent by the AMF according to the received requested service type, and the requested service type is carried in the service establishment request message sent by the UE to the AMF; Determining a selected target SSC mode according to the service context establishment request message; Send a first message to the AMF, where the first message includes the target SSC mode.

38. The device according to claim 37, characterized in that The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

39. The device according to claim 37 or 38, characterized in that For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

40. The device according to claim 37, characterized in that The requested service type or information used to indicate the requested service type is carried in the service establishment request message sent by the UE to the AMF.

41. The device according to claim 40, characterized in that The service establishment request message also includes the requested SSC mode, and correspondingly, the service context establishment request message includes the requested SSC mode; The requested SSC mode is determined by the UE based on the service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed. The service type, whether the service anchor point is allowed to be changed, the allowed service continuity, and whether cross-network nodes are allowed are determined by the UE based on its own mobility characteristics, based on the mobility characteristics of the carrier where the UE is located, and based on at least one of the service continuity characteristics required by the application or service for the network service.

42. The device according to claim 37 or 38, characterized in that If the requested service type is a connection service, the service management function is a session management function SMF; If the requested service type is computing power service, the service management function is a computing power orchestration center, and the computing power orchestration center is used to manage at least computing power information; If the requested service type is a data service, the service management function is a data orchestration center, which is used to manage services related to data processing; If the requested service type is an intelligent service, the service management function is an intelligent orchestration center; If the requested service type is a security service, the service management function is a security management center.

43. A service continuity guarantee device under a distributed network architecture, characterized in that: The device is applied to UE, and includes: a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Send a service establishment request message to the AMF in the current network node, where the service establishment request message includes the requested service type or information indicating the requested service type; The AMF is used to send a service context establishment request message to a corresponding service management function according to the requested service type, and receive a first message sent by the corresponding service management function, wherein the first message includes a selected target session and a service continuity mode SSC mode; wherein the target SSC mode is determined by the service management function after receiving the service context establishment request message.

44. The device according to claim 43, characterized in that The requested service type includes at least one of the following: connection service, computing power service, data service, intelligent service and security service.

45. The device according to claim 43 or 44, characterized in that For any requested service type, the target SSC mode includes any of the following items: an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and does not allow the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network needs to continuously maintain the service provided to the user and does not allow the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first releases the service provided to the user and reestablishes the service and allows the service anchor point to be changed, and allows the service to cross network nodes; an SSC mode used to indicate that in the scenario of the requested service type, the network first establishes other services before releasing the service provided to the user and allows the service anchor point to be changed, and allows the service to cross network nodes.

46. ​​The device according to claim 43, characterized in that The processor is further configured to perform the following operations: Determine the requested SSC mode; the service establishment request message also includes the requested SSC mode, and the service context establishment request message includes the requested SSC mode.

47. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any one of claims 1 to 28.

Images