Communication method and communication device

Abstract

The present application relates to a communication method and a communication device, belonging to the field of communication technology, and is used to improve the flexibility of abnormal slice processing. The method includes: an access network device receives abnormal indication information from a mobility management network element, the abnormal indication information is used to indicate a first link corresponding to a first slice in which an abnormality occurs in the mobility management network element, the first link being a transmission link between the access network device and the mobility management network element; the access network device releases a first terminal device, the first terminal device being a terminal device that accesses the first slice through the first link.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art

[0002] With the continuous emergence of a variety of communication services, the concept of network slicing (NS) has been introduced in the fifth generation mobile communication system (5G) to address the differences in network performance requirements of different communication services. A network slice can be composed of a set of logical network functions that support specific communication services.

[0003] One or more network slices can be deployed in certain network elements in the communication system. Taking the access and mobility management function (AMF) network element in the 5G system as an example, one or more network slices can be deployed in the AMF network element. When an abnormality occurs in a slice in the AMF network element, the AMF will notify the access network device that the AMF is abnormal or the slice in the AMF is abnormal. The access network device can only determine that the AMF is abnormal or the slice is abnormal based on the notification of the AMF, and can control other terminal devices to no longer access the AMF or the slice in the AMF where the abnormality occurs. However, it is impossible to perform targeted processing on the terminal devices that have already accessed the slice in the AMF where the abnormality occurs. It can be seen that the relevant technology has low flexibility in handling abnormal slices. Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device for improving the flexibility of abnormal slice processing.

[0005] In a first aspect, a communication method is provided, which can be applied to an access network device or a chip within the access network device. Taking the application of this method to the access network device as an example, in this method, the access network device receives abnormality indication information from a mobility management network element, where the abnormality indication information indicates a first link corresponding to a first slice in the mobility management network element where an abnormality has occurred. The first link is a transmission link between the access network device and the mobility management network element. Furthermore, the access network device releases a first terminal device accessing the first slice via the first link.

[0006] In this solution, for each slice deployed in the mobility management network element, a correspondence between each slice deployed in the mobility management network element and a link (a transmission link between the mobility management network element and the access network device) is pre-established. Through this correspondence, each slice in the mobility management network element can be bound to the link between the access network device and the mobility management network element. In this way, when a slice in the mobility management network element is abnormal, the mobility management network element can find the link corresponding to the abnormal slice based on the aforementioned correspondence, and then send the abnormal indication information for indicating the link to the access network device. Furthermore, after receiving the abnormal indication information, the access network device can clearly determine the corresponding link, and then release the terminal device that accesses the mobility management network element through the link. In this way, the terminal device accessing the abnormal slice in the mobility management network element can be processed promptly and effectively, thereby improving the flexibility and effectiveness of abnormal slice processing.

[0007] In a possible implementation, the abnormality occurring in the first slice includes at least one of a slice failure, a slice overload, and a slice deactivation.

[0008] In this way, various types of slice exceptions can be handled accordingly, improving the flexibility of exception handling.

[0009] In one possible implementation, the access network device determines a first terminal device that meets the priority release condition from all terminal devices currently accessing the first slice through the first link.

[0010] In this solution, when the access network device releases the terminal device that has accessed the abnormal slice, it can only select the terminal devices that meet the priority release conditions for release. In this way, all terminal devices can be treated differently when released, which can improve the flexibility of release and try to meet the actual business conditions of each terminal device.

[0011] In a possible implementation, the access network device receives slice identification information from a mobility management network element, where the slice identification information is used to indicate a slice type of a first slice.

[0012] In this solution, after an abnormality occurs in the first slice, the machine-accessing device can promptly know the slice type of the first slice through the slice identification information sent by the mobility management network element. In this way, terminal devices that require services of the slice type of the first slice will no longer access the first slice, thereby achieving unified perception between the access network side and the core network side, and thus ensuring the reliability of the communication system.

[0013] In one possible implementation, the access network device sends the service message of the first terminal device to a second slice having the same slice type as the first slice.

[0014] In this scheme, after the first terminal device is released, in order to ensure the service continuity of the first terminal device, it can be connected to a new slice as soon as possible, and in order to ensure that the service can be executed accurately, the slice type to which it is reconnected is the same as the slice type of the slice to which it was connected before being released, so as to ensure that its service can continue to be executed effectively.

[0015] In one possible implementation, the second slice is deployed in a mobility management network element, or the second slice is deployed in other mobility management network elements.

[0016] That is to say, when switching slices for the first terminal device, the mobility management network element can be switched, or the mobility management network element can not be switched. Two optional slicing methods are provided, with more switching options and better slicing flexibility.

[0017] In one possible implementation, the access network device receives exception cancellation information from a mobile management network element, and the exception cancellation information is used to indicate that the exception of the first slice has been eliminated; further, the access network device sends the service message of the second terminal device to the first slice through the first link.

[0018] The second terminal device and the first terminal device may be the same terminal device, or may be different terminal devices.

[0019] In this solution, after the abnormality of the first slice that previously occurred is eliminated, the terminal device can be connected to the first slice again, which is equivalent to using the first slice again to improve the utilization rate of the slice.

[0020] A second aspect provides a communication method that can be applied to a mobility management network element (MNE) or a chip within a MNE. Taking the application of this method to a MNE as an example, in this method, the MNE determines that an abnormality has occurred in a first slice deployed within the MNE. Furthermore, the MNE determines, based on a predefined correspondence between slices and links, a first link corresponding to the first slice, where the first link is a transmission link between the MNE and an access network device. The MNE then sends abnormality indication information to the access network device, where the abnormality indication information is used to indicate the first link.

[0021] In this solution, for each slice deployed in the mobility management network element, a correspondence between each slice deployed in the mobility management network element and a link (a transmission link between the mobility management network element and the access network device) is pre-established. Through this correspondence, each slice in the mobility management network element can be bound to the link between the access network device and the mobility management network element. In this way, when a slice in the mobility management network element is abnormal, the mobility management network element can find the link corresponding to the abnormal slice based on the aforementioned correspondence, and then send the abnormal indication information for indicating the link to the access network device. Furthermore, after receiving the abnormal indication information, the access network device can clearly determine the corresponding link, and then release the terminal device that accesses the mobility management network element through the link. In this way, the terminal device accessing the abnormal slice in the mobility management network element can be processed promptly and effectively, thereby improving the flexibility and effectiveness of abnormal slice processing.

[0022] In a possible implementation, the abnormality occurring in the first slice includes at least one of a slice failure, a slice overload, and a slice deactivation.

[0023] In a possible implementation, the mobility management network element sends slice identification information to the access network device, where the slice identification information is used to indicate the slice type of the first slice.

[0024] In one possible implementation, the mobility management network element determines that the first terminal device accesses the second slice deployed in the mobility management network element through a second link. The second slice is of the same slice type as the first slice. The first terminal device is a terminal device released from the first slice by the access network device. In the aforementioned correspondence between the slice and the link, the second link corresponds to the second slice.

[0025] In one possible implementation, the mobility management network element sends exception cancellation information to the access network device, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated.

[0026] In one possible implementation, the mobility management network element determines that the second terminal device accesses the first slice through the first link.

[0027] The technical effects of the above-mentioned possible solutions can be found in the description of the technical effects of the corresponding solutions in the first aspect.

[0028] In one possible implementation, when it is determined that the data volume of the data flow on the third link between the access network device is greater than a threshold, the mobility management network element performs packet loss processing on the data flow; wherein, in the aforementioned correspondence between slices and links, the third link corresponds to the third slice, and the threshold is determined based on the third slice.

[0029] In this solution, based on the predefined correspondence between slices and links, flow control can be performed at the bottom layer of the mobility management network element (i.e., before traffic enters the slice). Flow control is performed earlier in the data flow transmission path, preventing excessive data from entering the slice and minimizing the probability of overload at the slice level. Furthermore, flow control is performed on the link corresponding to each slice based on the correspondence between links and slices, which prevents mutual influence between slices and improves the reliability of the entire network.

[0030] According to a third aspect, a communication device is provided, including:

[0031] A communication unit, configured to receive abnormality indication information from a mobility management network element, where the abnormality indication information is used to indicate a first link corresponding to a first slice in which an abnormality occurs in the mobility management network element, where the first link is a transmission link between the access network device and the mobility management network element;

[0032] A processing unit is used to release the first terminal device, where the first terminal device is a terminal device that accesses the first slice through the first link.

[0033] In a possible implementation, the abnormality occurring in the first slice includes at least one of the following: the first slice fails; or the first slice is overloaded; or the first slice is disabled.

[0034] In a possible implementation, the processing unit is further used to determine a first terminal device that meets the priority release condition from all terminal devices currently accessing the first slice through the first link.

[0035] In a possible implementation, the communication unit is further used to receive slice identification information from a mobility management network element, where the slice identification information is used to indicate a slice type of the first slice.

[0036] In a possible implementation, the communication unit is further used to send the service message of the first terminal device to the second slice, where the second slice has the same slice type as the first slice.

[0037] In a possible implementation, the second slice is deployed in the mobility management network element, or the second slice is deployed in other mobility management network elements.

[0038] In one possible implementation, the communication unit is also used to receive exception cancellation information from a mobile management network element, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated; and to send the service message of the second terminal device to the first slice through the first link.

[0039] The technical effects of various possible technical solutions in the third aspect can be found in the description of the technical effects of the corresponding technical solutions in the first aspect.

[0040] According to a fourth aspect, a communication device is provided, comprising:

[0041] a processing unit, configured to determine that an abnormality occurs in a first slice deployed in a mobility management network element;

[0042] The processing unit is further configured to determine, based on a predefined correspondence between slices and links, a first link corresponding to the first slice, where the first link is a transmission link between the mobility management network element and the access network device;

[0043] The communication unit is configured to send abnormality indication information to the access network device, where the abnormality indication information is used to indicate the first link.

[0044] In a possible implementation, the abnormality occurring in the first slice includes at least one of the following: the first slice fails; or the first slice is overloaded; or the first slice is disabled.

[0045] In a possible implementation, the communication unit is further used to send slice identification information to the access network device, where the slice identification information is used to indicate the slice type of the first slice.

[0046] In one possible implementation, the processing unit is also used to determine that the first terminal device accesses the second slice deployed in the mobility management network element through a second link, the second slice has the same slice type as the first slice, the first terminal device is a terminal device released from the first slice by the access network device, and in the above-mentioned correspondence between slices and links, the second link corresponds to the second slice.

[0047] In a possible implementation, the communication unit is further used to send exception cancellation information to the access network device, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated.

[0048] In one possible implementation, the processing unit is further used to determine that the second terminal device accesses the first slice through the first link.

[0049] In one possible implementation, the processing unit is also used to determine that the data volume of the data flow on the third link between the access network device is greater than a threshold, and to perform packet loss processing on the data flow; wherein, in the above-mentioned correspondence between the slice and the link, the third link corresponds to the third slice, and the above-mentioned threshold is determined based on the third slice.

[0050] The technical effects of various possible technical solutions in the fourth aspect can be found in the description of the technical effects of the corresponding technical solutions in the second aspect.

[0051] In a fifth aspect, a communication device is provided, comprising: at least one processor; and a communication interface communicatively connected to the at least one processor; the at least one processor executes instructions stored in a memory, so that the communication device executes the method described in the first aspect or any possible implementation of the first aspect through the communication interface.

[0052] In a sixth aspect, a communication device is provided, comprising: at least one processor; and a communication interface communicatively connected to the at least one processor; the at least one processor executes instructions stored in a memory, so that the communication device executes the method described in the second aspect or any possible implementation of the second aspect through the communication interface.

[0053] In a seventh aspect, a computer-readable storage medium is provided, comprising a program or instructions, which, when executed on a computer, enables the method described in the first aspect or any possible implementation of the first aspect to be executed.

[0054] In an eighth aspect, a computer-readable storage medium is provided, comprising a program or instructions, which, when executed on a computer, enables the method described in the second aspect or any possible implementation of the second aspect to be executed.

[0055] In a ninth aspect, a chip is provided, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the method described in the first aspect or any possible implementation of the first aspect is executed.

[0056] In a tenth aspect, a chip is provided, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the method described in the second aspect or any possible implementation of the second aspect is executed.

[0057] In an eleventh aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, enables the method described in the first aspect or any possible implementation of the first aspect to be executed.

[0058] In a twelfth aspect, a computer program product is provided, comprising instructions, which, when run on a computer, enables the method described in the second aspect or any possible implementation of the second aspect to be executed.

[0059] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not limit the scope of protection of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 This is a schematic diagram of the 5G network architecture based on service-oriented architecture;

[0061] Figure 2 A schematic diagram of network slicing;

[0062] Figure 3 Schematic diagram of the process of registering slices for terminal devices to the network side;

[0063] Figure 4a Schematic diagram of deploying a single slice in AMF;

[0064] Figure 4b Schematic diagram of deploying multiple slices in AMF;

[0065] Figure 5 Schematic diagram of establishing a link between AN and AMF;

[0066] Figure 6 Schematic diagram of storing UE context information for AN;

[0067] Figure 7 Schematic diagram of abnormal slices in AMF;

[0068] Figure 8a Schematic diagram of a slice failure in AMF;

[0069] Figure 8b Schematic diagram for deactivation of slices in AMF;

[0070] Figure 8c Schematic diagram of slice overload in AMF;

[0071] Figure 8d Schematic diagram of slice overload recovery in AMF;

[0072] Figure 9 A schematic diagram of establishing the correspondence between slices and links for slices in AMF;

[0073] Figure 10 Schematic diagram of configuring links for terminal devices;

[0074] Figure 11 This is an interactive flow chart of the communication method in an embodiment of the present application;

[0075] Figure 12 is another interactive flow chart of the communication method in an embodiment of the present application;

[0076] Figure 13 is another interactive flow chart of the communication method in an embodiment of the present application;

[0077] Figure 14 This is a schematic diagram of flow control processing for data streams in an embodiment of the present application;

[0078] Figure 15 Schematic diagram of the structure of the communication device in the embodiment of the present application;

[0079] Figure 16 This is a schematic structural diagram of another communication device according to an embodiment of the present application;

[0080] Figure 17 This is a schematic structural diagram of another communication device according to an embodiment of the present application;

[0081] Figure 18 Schematic diagram of the structure of another communication device in an embodiment of the present application. DETAILED DESCRIPTION

[0082] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0083] Please refer to Figure 1 , which is a schematic diagram of a 5G network architecture based on a server architecture, and is also a schematic diagram of an application scenario of an embodiment of the present application. Figure 1 The 5G network architecture shown may include three parts, namely the terminal equipment part, the data network (DN) part and the operator network part. Among them, the operator network part may include one or more of the following network elements: authentication server function (AUSF) network element, network exposure function (NEF) network element, policy control function (PCF) network element, unified data management (UDM) network element, NRF network element, application function (AF) network element, AMF network element, session management function (SMF) network element, radio access network (RAN) network element, user plane function (UPF) network element and network slice-related network slice authentication function (NSSAAF) (in Figure 1 In the above-mentioned operator network part, the part other than the wireless access network part can be called the core network part.

[0084] In this network architecture, the network slice selection function (NSSF) network element, the network exposure function (NEF) network element, the NRF network element, the policy control function (PCF) network element, the unified data management (UDM) network element, the application function (AF) network element, the authentication server function (AUSF) network element, the AMF network element and the SMF network element can communicate with each other based on the service method. Of course, for two of the network elements to communicate, one network element needs to open the corresponding service method to the other network element. Figure 1 In [1], Namf is the service interface of AMF, Nnssf can be regarded as the service interface of NSSF, and the service interfaces of other network elements can be seen in [1]. Figure 1 In addition, AMF and terminal devices can communicate through the N1 interface, and AMF and RAN can communicate through the N2 interface. For details on the communication interfaces between other network elements, see Figure 1 shown.

[0085] To make it easier to understand, the following Figure 1 A brief introduction to some of the functional network elements shown is given below.

[0086] The mobility management function network element is, for example, a mobility management entity (MME) network element in a fourth generation (4G) system, and an AMF network element in a 5G system. Of course, the embodiments of the present application are not limited thereto, and may also be implemented through other network elements in other communication systems. For example, in future communication systems, it may be a network element having the functions of the above-mentioned AMF network element. Taking the mobility management function network element as an example, the AMF network element is mainly responsible for wireless docking, terminating the RAN control plane (CP) interface, that is, the N2 interface, terminating the non-access-stratum (NAS) and NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, transmitting session management (SM) messages between user equipment (UE) and SMF, or UE mobility notification, etc.

[0087] NSSF network element is responsible for determining the network slice instance, selecting the AMF network element, etc.

[0088] The SMF network element can provide session management functions such as session establishment, modification or release, including tunnel maintenance functions between UPF network elements and access network (AN) nodes, UE Internet Protocol (IP) address allocation and management, dynamic host control protocol (DHCP), selection and control of user plane (UP) functions, configuration of UPF routing functions, termination of policy control function interfaces, billing, roaming functions, or policy control related functions.

[0089] The UDM network element is responsible for managing contract data and notifying the corresponding network element when the contract data is modified.

[0090] The AUSF network element is responsible for authentication functions and for executing the network slice authentication and authorization process.

[0091] The UPF network element is the entity that forwards user-plane data. It serves as the external protocol data unit (PDU) session for data network interconnection and has functions such as message routing and forwarding, message detection, user-plane partial policy enforcement, lawful interception, traffic usage reporting, or QoS processing.

[0092] To make the text more concise, the following text uses abbreviations for each network element, omitting the word "network element". For example, the AMF network element is abbreviated as AMF, the NRF network element is abbreviated as NRF, the access network network element is abbreviated as RAN, the SMF network element is abbreviated as SMF, and so on.

[0093] In addition, in the introduction Figure 1 The network architecture shown in the figure mentions the concept of service methods. Specifically, in 5G systems, it is currently believed that network elements in the control plane can interact using service-based methods, and network elements in the user plane can interact using a point-to-point method. For example, in a 5G system, the NRF, as a network element in the control plane, can expose some service methods, and other devices can interact with the NRF through these service methods.

[0094] In the 5G era, hundreds of billions of IoT devices will be connected to the network. Different application scenarios will have different, and sometimes even conflicting, network requirements. Providing services for these diverse application scenarios through a single network will lead to an extremely complex network architecture, inefficient network management, and low resource utilization. To address this, network slicing technology has been proposed. 5G network slicing provides isolated network environments for different application scenarios by creating virtual, independent logical networks on the same network infrastructure. This allows each application scenario to customize network functions and features to meet its specific needs, effectively ensuring the QoS requirements of different services. The goal of 5G network slicing is to organically combine terminal devices, access network resources, core network resources, and network operations and management systems to provide independent, isolated, and complete networks for different business scenarios or service types.

[0095] For reference Figure 2 , a schematic diagram of network slicing. Figure 2 There are three types of network slices: critical machine type of communication (MTC) slices, massive MTC slices, and mobile broadband (MBB) slices. Figure 2 In the IEEE Spectrum Distributed Cloud (MSDC) slicing framework, terminal devices corresponding to critical MTC slices may include vehicles, etc.; terminal devices corresponding to massive MTC slices may include some meters, such as water meters or gas meters; and terminal devices corresponding to MBB slices may include mobile phones or personal computers (PCs). A specific application scenario for critical MTC slices is, for example, autonomous driving slices. For autonomous driving slices, safety, reliability, and latency are crucial. Due to latency constraints, all required (possibly specialized) functions, including vertical industry applications, are installed on cloud edge nodes. A specific application scenario for massive MTC slices is, for example, Internet of Things (IoT) slices. IoT slices are 5G slices that support large-scale machine-type devices (such as sensors), with some basic control plane functions configurable and omittable. A specific application scenario for MBB slices is, for example, smartphone slices. Smartphone slices are implemented by deploying mature network functions distributed throughout the network, enabling a typical 5G slice using a smartphone.

[0096] When network slicing is deployed in the core network, the network slice selection process is triggered when the terminal device initially attaches to the network. This process depends on one or more parameters, including the user's subscription data, local configuration information, roaming agreement, or operator policy. These parameters must be comprehensively considered during the network slice selection process to select the optimal slice type for the terminal device.

[0097] Network slicing is a logical division of the physical network, which is deployed in the form of network elements in actual applications.

[0098] The mobility management network element in the embodiment of the present application may be Figure 1 The AMF network element shown in can also be a network element in a future communication system that has the functions of the above-mentioned AMF network element.

[0099] The access network (AN) equipment in this application, also known as the radio access network (RAN) equipment, is a device that provides wireless communication functions for terminal devices. Access network equipment includes but is not limited to: the next generation base station (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node ​​B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.

[0100] The terminal device (also referred to as user equipment (UE)) of the present application is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water (such as ships); and can also be deployed in the air (for example, on airplanes, balloons, and satellites). The terminal can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grids, a wireless terminal in transportation safety, a wireless terminal in smart cities, a wireless terminal in smart homes, etc.

[0101] It should be noted that in this application, "network slice instance", "network slice" and "slice" refer to the same content, and one of them is used to describe it in different places, and the two can be interchangeable.

[0102] In a 5G network, when a terminal device needs to use network services, it must first register with the network. The terminal device may initiate the registration process in the following scenarios:

[0103] (1) The terminal device registers to the 5G network for the first time;

[0104] (2) When the terminal device moves out of the originally registered area, it performs mobility registration update;

[0105] (3) The terminal device performs periodic registration updates.

[0106] During the registration process, the establishment of one or more PDU sessions may be triggered. For example, in the scenario where the terminal device is performing a mobility registration update, the terminal device has uplink data to send, and a PDU session will be created in the registration process. Figure 3 Describe the process of registering terminal devices.

[0107] S301: The terminal device sends a registration request (Registration Request) message to the AN. Correspondingly, the AN receives the registration request message from the terminal device.

[0108] The registration request message is sent to the AN via an AN message, for example.

[0109] S302: AN selects AMF based on the radio access technology (RAT) and the identifier of the network slice requested by the registration request message.

[0110] If the registration request message does not carry the 5G globally unique temporary UE identity (GUTI), or although the registration request message carries the 5G GUTI, the 5G GUTI cannot indicate a valid AMF, the AN can select an AMF based on the RAT supported by the terminal device and the identifier of the network slice requested by the registration request message. Alternatively, if the terminal device is in a radio resource control (RRC) connected state, the AN can forward the registration request message directly to the corresponding AMF based on the existing RRC connection, that is, there is no need to execute S502, but S503 can be executed.

[0111] The identifier of a network slice is, for example, an S-NSSAI. The registration request message may carry one or more S-NSSAIs, one of which may indicate a network slice. The network slice indicated by the one or more S-NSSAIs is the network slice that the terminal device requests to access.

[0112] S303. The AN sends a registration request message to the AMF. Correspondingly, the AMF receives the registration request message from the AN.

[0113] That is, AN forwards the Registration Request message to AMF.

[0114] S304. The AMF performs the primary authentication process for the permanent identity of the terminal device, which is called, for example, security procedures PLMN access. When the process succeeds, the AMF obtains the UE's subscription data from the UDM. The subscription data includes an indication of whether each S-NSSAI subscribed to the terminal device needs to perform the NSSAA process. Figure 3 S304 is indicated as a security process PLMN access.

[0115] S305: The AMF determines whether the S-NSSAI for which the NSSAA process needs to be executed is included in the Requested NSSAI based on the subscription data of the terminal device.

[0116] Specifically, the AMF determines, based on the subscription data of the terminal device, that a certain S-NSSAI contained in the Requested NSSAI can be mapped to the HPLMN S-NSSAI, and that the HPLMN S-NSSAI needs to execute the NSSAA process. The AMF then determines that the terminal device needs to execute the NSSAA process after this registration process.

[0117] S306: AMF sends a Registration Accept message to the terminal device. Correspondingly, the terminal device receives the Registration Accept message from AMF.

[0118] The Registration Accept message may carry an Allowed NSSAI, where the Allowed NSSAI includes S-NSSAIs that do not require the NSSAA process. At the same time, the AMF also sends a pending NSSAI to the terminal device, and the terminal device receives the Pending NSSAI from the AMF. The Pending NSSAI may include one or more S-NSSAIs that require the NSSAA process. The Pending NSSAI is used to indicate to the terminal device that these S-NSSAIs that require the NSSAA process are in the pending state.

[0119] S307: After sending the Registration Accept message, the AMF performs the NSSAA procedure on the S-NSSAI in the pending state.

[0120] For example, if the pending NSSAI includes S-NSSAI-1, the AMF may perform the NSSAA procedure for S-NSSAI-1.

[0121] S308: After the NSSAA process is completed, the AMF updates the Allowed NSSAI of the terminal device according to the authentication result of the NSSAA process. Figure 3 S308 is represented as the UE configuration update procedure, that is, the AMF can update the Allowed NSSAI for the terminal device.

[0122] pass Figure 3 According to the process shown, the terminal device can access a slice in the AMF.

[0123] One or more slices can be deployed in AMF. When some slices in AMF are abnormal, the access network device can only determine that the AMF is abnormal or the slice is abnormal based on the notification of AMF, and can control other terminal devices to no longer access the abnormal AMF or the slice with abnormality in AMF. However, targeted processing cannot be performed on the terminal devices that have already accessed the slice with abnormality in AMF, which may affect the normal execution of the terminal device business. It can be seen that the relevant technology has poor flexibility in handling abnormal slices, which may affect the business of the terminal device and reduce the reliability of the communication system.

[0124] In view of this, an embodiment of the present application provides a communication method, in which, for each slice deployed in a mobility management network element (such as an AMF), a correspondence between each slice and a link (a transmission link between the AMF and the AN) can be pre-established. For example, slice 1 and slice 2 are deployed in the AMF, and there are two links, link 1 and link 2, between the AMF and the AN. Then, a correspondence between slice 1 and link 1 and between slice 2 and link 2 can be pre-established. Through this correspondence, each slice in the AMF can be bound to the link between the AN and the AMF. In this way, when a slice in the AMF is abnormal, the AMF can find the link corresponding to the abnormal slice based on the aforementioned correspondence, and then send abnormal indication information indicating the link to the AN. Furthermore, after receiving the abnormal indication information sent by the AMF, the AN can determine the terminal device that accesses the abnormal slice in the AMF through the corresponding link, and then release the terminal device that accesses the abnormal slice through the link. In this way, the terminal device on the abnormal slice can be processed in a timely and effective manner, thereby improving the flexibility and effectiveness of abnormal slice processing and improving the reliability of the communication system.

[0125] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth-generation (5G) communication systems, sixth-generation (6G) communication systems or other future evolution systems, or various other wireless communication systems using wireless access technologies, etc. As long as there is network slicing in the communication system, the technical solutions of the embodiments of the present application can be adopted.

[0126] For ease of understanding, the slice management solution in the embodiment of the present application is described below with reference to the accompanying drawings.

[0127] As mentioned above, one or more slices can be deployed in AMF, that is, in actual deployment, there are single AMF single slice scenarios and single AMF multi-slice scenarios. Among them, a single AMF single slice means that only one network slice instance is deployed in an AMF, such as Figure 4aAs shown, only slice 1 is deployed in one AMF; single AMF multi-slice means that multiple (i.e., at least two) network slice instances are deployed in one AMF, such as Figure 4b As shown in , three network slice instances, slice 1, slice 2, and slice 3, are deployed in an AMF. For the scenario where multiple slices are deployed in an AMF, the slice types of the slices deployed in an AMF can be exactly the same, for example, slice 1, slice 2, and slice 3 are all the aforementioned MBB slices; or, the slice types of all slices deployed in an AMF are not exactly the same, for example, slice 1 and slice 2 are MBB slices, while slice 3 is a massive MTC slice; or, the slice types of all slices deployed in an AMF are different, for example, slice 1 is an MBB slice, slice 2 is a massive MTC slice, and slice 3 is a critical MTC slice.

[0128] AMF can be configured with one or more globally unique AMF identifiers (GUAMI) for interaction in business processes. GUAMI is equivalent to the business identifier of AMF. Figure 4b In the single AMF multi-slice scenario shown, for example, the slice processing processes corresponding to slice 1, slice 2, and slice 3 can each have a GUAMI, or these three slices can share a GUAMI, that is, each slice in an AMF has the same GUAMI. The embodiment of the present application relates to a scenario where multiple slices share one GUAMI.

[0129] See Figure 5 As shown in Figure 1, after the AMF is deployed, a link connection can be established between the AN and the AMF. The link connection between the AN and the AMF can be called a transport network layer (TNL) Association. The process of establishing a link connection between the AN and the AMF is as follows:

[0130] S501: The AN configures the link information between the local end and the AMF.

[0131] S502: AMF configures local link information.

[0132] S503: AMF configures its own GUAMI information.

[0133] S504: AN initiates link establishment.

[0134] Through the link establishment process between AN and AMF, one or more links can be established between AN and AMF, such as Figure 5As shown in , after the link is established, two link connections, Link 1 and Link 2, are established between AN and AMF.

[0135] It should be noted that the link between AN and AMF in the embodiment of the present application can also be referred to as a "communication link" or "connection" or "communication connection".

[0136] The terminal device accesses the slices in the AMF, specifically, accesses the slices in the AMF through the link between AN and AMF. The link through which each terminal device accesses the slices in the AMF can be determined in the following way.

[0137] See Figure 6 As shown, in order to distinguish, Figure 6 The solid arrow path in the figure represents the transmission path corresponding to UE1. Figure 6 The dotted arrow path in FIG represents the transmission path corresponding to UE2.

[0138] Take UE1 accessing AN as an example. When UE1 accesses AMF for the first time, AN first randomly selects a link to send the user information corresponding to UE1 to AMF. For example, link 1 is randomly selected to send user information to AMF. After receiving the user information of UE1, AMF allocates a slice to UE1 according to the user information, for example, slice 2. Further, AMF will select a link (for example, according to the actual load of the link) to reply to AN. For example, AMF selects link 2 to reply to AN. Furthermore, AN will record the link information of the AMF return message. When the information related to UE1 is exchanged with AMF again in the future, link 2 can be directly used to exchange information with AMF. In addition, based on the link information of the received AMF return message, AN can save the context information corresponding to UE1, for example Figure 6 As shown in , the context information of UE1 may include: UE1's identification, UE1 accessing AMF through link 2, GUAMI of the AMF accessed by UE1, and other information.

[0139] Take UE2 accessing AN as an example. When UE2 accesses AMF for the first time, AN first randomly selects a link to send the user information corresponding to UE2 to AMF. For example, it randomly selects link 2 to send user information to AMF. After receiving the user information of UE2, AMF allocates a slice to UE2 according to the user information, for example, it allocates slice 2. Further, AMF will select a link (for example, according to the actual load of the link) to reply to AN. For example, AMF selects link 1 to reply to AN. Furthermore, AN will record the link information of the AMF return message. When it interacts with AMF again to exchange information related to UE2, it can directly use link 1 to exchange information with AMF. In addition, based on the link information of the received AMF return message, AN can save the context information corresponding to UE2, for example Figure 6 As shown in , the context information of UE2 may include: UE2 identification, UE2 access to AMF through link 1, GUAMI of AMF accessed by UE2, and other information.

[0140] That is to say, the context information of each UE is stored in the AN, and the context information of each UE can be used to determine through which link the corresponding UE accesses the slice in the AMF.

[0141] In practice, slices in AMF may experience exceptions. When a slice experiences an exception, the network services of the terminal devices accessing the slice may also be affected. Figure 7 As shown, when an exception occurs in a slice (for example, slice 2) in the AMF, the AMF will send an exception notification to the AN, thereby informing the AMF that a slice exception has occurred in the AMF.

[0142] See also Figure 8a As shown, when slice 2 in the AMF fails, in the related art, the abnormal notification sent by the AMF to the AN is, for example, an AMF status indication message, which carries the GUAMI information of the AMF. In the slice failure scenario, the AN identifies the failed AMF corresponding to the GUAMI information based on the GUAMI information in the AMF status indication message, and releases all users connected to the AMF based on the saved UE context information. At this time, not only the users on the failed slice in the AMF are released, but also the users on the non-failed slices in the AMF are released. This affects the users on the non-failed slices. In other words, the release processing of the users on the non-failed slices is inaccurate.

[0143] See also Figure 8bAs shown, when slice 2 in the AMF is deactivated, in the related art, the abnormal notification sent by the AMF to the AN is also, for example, an AMF status indication, which is similar to the AMF status indication sent in a fault scenario. The AN identifies the AMF with deactivated slice corresponding to the GUAMI information based on the GUAMI information in the AMF status indication. The AN can identify the AMF with deactivated slice, but cannot perform corresponding processing on the users on the deactivated slice.

[0144] See also Figure 8c As shown, when slice 2 in the AMF is overloaded, in the related art, the abnormal notification sent by the AMF to the AN is, for example, an Overload Start message. The Overload Start message carries the NSSAI corresponding to the overloaded slice in the AMF. The AN can determine that the overloaded slice is slice 2 through the NSSAI carried in the Overload Start message. Furthermore, the AN can no longer allow new users to access slice 2 that is currently in an overloaded state, but cannot perform any processing on users who have already accessed slice 2 because the AN cannot identify which users are on the overloaded slice.

[0145] See also Figure 8d As shown, when the overload condition of the slice in AMF2 is eliminated, that is, when it is no longer overloaded, AMF can send an overload stop (Overload Stop) message to AN. The Overload Stop message carries the NSSAI corresponding to the overload recovered slice in AMF. AN can determine that the overload recovered slice is slice 2 through the NSSAI carried in the Overload Start message.

[0146] In order to implement the technical solution in the embodiment of the present application, each slice in the AMF can be configured in advance to correspond to the link between the AN and the AMF. Figure 9 As shown, for example, the NSSAI of slice 1 is NSSAI-1, and the NSSAI of slice 2 is NSSAI-2. According to the configuration information of the slices and links, slice 1 corresponds to link 1, and slice 2 corresponds to link 2. In the specific implementation process, a slice can be bound to one or more links, and the bound links corresponding to each slice are not shared, that is, the links bound to each slice are different. In addition, the correspondence between each slice and link in the AMF can be pre-configured in the AMF and stored locally by the AMF, or it can be specified by the protocol, and there is no need to configure the AMF in this case.

[0147] The following combination Figure 10 The corresponding configuration between each slice and link in AMF is explained.

[0148] S1001. The configuration management module in AMF sends the correspondence between slices and links during the startup phase. Specifically, the correspondence can be sent to the link management module in AMF (for example, the link module in AMF). In the correspondence between slices and links, it is assumed that slice 1 corresponds to link 1, and slice 2 corresponds to link 2.

[0149] S1002. AN randomly selects a link to send the first service message sent by the terminal device to AMF to AMF, for example, link 1 is selected to send, specifically, it can be sent to the link management module in AMF.

[0150] S1003. The link management module in AMF identifies the service message, and identifies the slice to be accessed by the female terminal device as slice 2 through the NSSAI and other identifiers carried in the service message, and then forwards the service message to slice 2.

[0151] S1004. Slice 2 returns the service feedback message to the link management module. Correspondingly, the link management module receives the service feedback message.

[0152] S1005. The link management module determines that the link corresponding to slice 2 is link 2 according to the correspondence between slices and links configured in S1001.

[0153] S1006 . The link management module sends the service feedback message to the AN via link 2 . Correspondingly, the AN saves the information of link 2 .

[0154] S1007: The link management module saves the link information corresponding to link 2 in the context information of the terminal device.

[0155] S1008. When the terminal device needs to send a service message to slice 2 again, AN uses link 2 to send the subsequent service message of the terminal device. Specifically, the subsequent service message of the terminal device can be sent to the link management module in AMF.

[0156] This application embodiment provides a communication method, see Figure 11 The flow chart of the communication method provided in the embodiment of the present application is shown as follows. Figure 11 The process shown is described below.

[0157] S1101. The mobility management network element determines that an abnormality occurs in the first slice deployed in the mobility management network element.

[0158] Taking the mobility management network element as AMF as an example, multiple slices can be deployed in the AMF, that is, the single AMF multiple slice scenario mentioned above. In the specific implementation process, the slices deployed in the AMF may be abnormal, such as slice failure, slice overload, slice deactivation, slice failure and deactivation at the same time, etc. That is to say, the slice abnormality in the embodiment of the present application may refer to at least one of slice failure, slice overload, and slice deactivation.

[0159] For example, if the AMF determines that an exception has occurred in the first slice deployed within itself, in this embodiment of the application, the first slice is used to represent the slice in the AMF where the exception has occurred. The first slice can be a single slice, or the first slice can include multiple slices. In this case, the multiple slices where the exception has occurred are collectively referred to as the first slice. Alternatively, if the first slice refers to the slice where the exception has occurred, then the multiple slices where the exception has occurred can be understood to include multiple slices.

[0160] S1102. The mobility management network element determines a first link corresponding to the first slice according to a predefined correspondence between slices and links.

[0161] The mobility management network element pre-defines the correspondence between each slice deployed in the mobility management network element and the link between the mobility management network element and the access network device. This correspondence can be pre-configured in the AMF or specified by the protocol. Figure 9 As shown, the AMF slice-to-link correspondence is: slice 1 corresponds to link 1, and slice 2 corresponds to link 2. Based on this correspondence, the link corresponding to each slice in the AMF can be determined. Therefore, after determining that the first slice has an abnormality, the link corresponding to the first slice can be determined based on this correspondence. For example, if the first slice is slice 1, then the corresponding link is link 1.

[0162] S1103. The mobility management network element generates exception indication information, where the exception indication information is used to indicate the first link corresponding to the first slice where the exception occurs.

[0163] After determining that an abnormality has occurred in the first slice, the AMF hopes to inform the access network device of the abnormality as soon as possible so that the access network device can process the terminal device connected to the abnormal slice. To this end, the AMF can generate abnormal indication information, which can carry the link information of the link corresponding to the slice where the abnormality has occurred. Taking the above-mentioned first slice where the abnormality has occurred as slice 1 as an example, the AMF can send the link information corresponding to link 1 to the AMF, and can generate abnormal indication information carrying the link information corresponding to link 1. In the specific implementation process, taking the slice abnormality being a slice failure or slice deactivation as an example, the corresponding abnormal indication information can be an AMF status indication message. Taking the slice abnormality being a slice overload as an example, the corresponding abnormal indication information can be an Overload Start message.

[0164] In a possible embodiment, in addition to the link information of the first link corresponding to the first slice, the exception indication information may also include exception type indication information for indicating the exception type. The exception type indication information may indicate the exception type of the slice, such as slice failure, slice overload, or slice deactivation. Optionally, the exception type of the slice may be directly indicated by explicit indication of the exception type indication information, or the exception type of the slice may be determined according to the format of the exception indication information. For example, if the exception indication information is the aforementioned AMF status indication message, it may indicate that the exception type is slice failure or slice deactivation. If the exception indication information is the aforementioned Overload Start message, it may indicate that the exception type is slice overload. In other words, the exception type of the slice may be implicitly indicated by message signaling commonly used in related technologies.

[0165] S1104: The mobility management network element sends abnormality indication information to the access network device. Correspondingly, the access network device receives the abnormality indication information from the mobility management network element.

[0166] After generating the exception indication information, the AMF can send it directly to the access network device so that the access network device can clearly understand that some slices in the current AMF are no longer available due to slice exceptions.

[0167] In another embodiment, the AMF may start timing from the time an abnormality occurs in the slice, and send abnormality indication information to the access network device only when the abnormality lasts for more than a set time (for example, 3S). In other words, the abnormality may be notified to the access network device only after it lasts for a certain period of time. Because in practice, some slice abnormalities are instantaneous and may be recovered quickly, so by setting a time limit, the number of releases to the terminal device can be minimized on the basis of having a small impact on the terminal device, so as to maintain the continuity of the terminal device service as much as possible.

[0168] S1105. The access network device determines a terminal device that accesses the mobility management network element through the first link.

[0169] After receiving the abnormal indication information sent by AMF, the link corresponding to the first slice can be determined. For example, the link corresponding to the first slice is represented by the first link, and the access network device can determine the first link from the multiple links between it and the AMF.

[0170] Furthermore, the access network device stores the context information of each terminal device (such as the aforementioned Figure 6 ), all terminal devices that access the AMF through the first link can be filtered out. Since the correspondence between links and slices has been pre-configured in the AMF, these terminal devices that access the AMF through the first link are actually the first slice in the AMF accessed through the first link. Since the first slice has currently experienced an abnormality, it is likely that network services can no longer be provided to the various terminal devices accessing the first slice. Therefore, in order to ensure the continuity of terminal device services and to facilitate access network testing and the user side to be able to promptly know the slice abnormalities in the core network, the access network device can perform targeted processing on the terminal device currently accessing the first slice.

[0171] S1106. The access network device selects a terminal device that needs to be released from the determined terminal devices. For example, the selected terminal device that needs to be released is referred to as the first terminal device.

[0172] During the specific implementation process, depending on the different types of slice exceptions and the different service types of each terminal device, the terminal device currently accessing the abnormal slice (i.e., the first slice) can be processed in the same way, or it can be processed differently.

[0173] For example, in the scenario of slice failure and slice deactivation, the slice generally can no longer provide network services, so at this time you can choose to release all terminal devices that are currently connected to the first slice, then the first terminal device is all the terminal devices currently connected to the AMF through the first link. For another example, in the scenario of slice overload, the first slice can still provide network services, but because the overload may affect the business operation of some terminal devices, at this time you can select some of the terminal devices that are currently connected to the first slice as the first terminal devices, because in the overload scenario, generally just releasing some terminal devices can solve the overload problem of the slice.

[0174] In one possible implementation, some terminal devices can be randomly selected from all terminal devices as the first terminal devices for release. In another possible implementation, in a slice overload scenario, a terminal device that meets the priority release conditions can be selected from all terminal devices currently accessing the first slice as the first terminal device to be released. For example, a terminal device with poor quality of service (QoS) can be selected as the first terminal device, or the levels of each terminal device can be compared, and a terminal device with a lower level can be selected as the first terminal device. For example, in an overload scenario, the terminal device corresponding to an ordinary user can be selected as the first terminal device, while the terminal device corresponding to a high-level user can continue to be retained in the access service of the first slice to ensure the continuous execution of VIP customer services.

[0175] S1107. The access network device releases the first terminal device.

[0176] As described above, the first terminal device is a terminal device that needs to be released in the first slice that is currently accessed abnormally. The first terminal device may be all terminal devices that are currently accessing the first slice, or the first terminal device may be part of all terminal devices that are currently accessing the first slice.

[0177] Releasing the first terminal device can be understood as terminating the state in which the first terminal device is connected to the first slice, that is, disconnecting the first terminal device from the access to the first slice. In a specific implementation process, the access network device can release the first terminal device by disconnecting the Radio Resource Control (RRC) protocol connection between the access network device and the first terminal device, that is, controlling the terminal device to go offline. The specific release process can be implemented by using the process of disconnecting the RRC connection of the terminal device in the relevant technology, and the embodiments of the present application do not limit this.

[0178] S1108. The mobility management network element sends the slice identification information of the first slice to the access network device. Correspondingly, the access network device receives the slice identification information sent by the mobility management network element. The slice identification information is used to indicate the slice type of the first slice.

[0179] After sending the abnormal indication information to the access network device, the mobility management network element may also send slice identification information of the first slice to the access network device, where the slice identification information is used to indicate the slice type of the first slice.

[0180] The Third Generation Partnership Project (3GPP) protocol defines three types of network slicing: eMBB, uRLLC, and mMTC. Each type of network slicing targets specific services. For example, eMBB slicing targets high-data-rate, high-mobility services; uRLLC slicing can handle high-reliability, low-latency communication scenarios; and mMTC slicing can serve high-volume, low-data-volume, latency-tolerant, and infrequently accessed services (such as sensor and wearable device services).

[0181] After a terminal device using network slicing accesses the network, the network selects a network slice for it through the S-NSSAI carried by the terminal device in the service request. S-NSSAI consists of two parts: slice / service type (SST) and slice differentiator (SD). SST identifies the slice type or the service type supported by the slice. SD is the slice differentiator, which is used to distinguish different network slices with the same SST. For example, a water plant and a power plant each subscribe to their own mMTC slices. The SST of these two slices is the same, but the SD is different. NSSAI is a collection of S-NSSAIs. Because terminal devices can access multiple network slices at the same time, terminal devices and networks use NSSAI to select network slices.

[0182] The access network device can determine the slice type of the slice (e.g., the first slice) in which the exception occurs in the AMF based on the received slice identification information, and can then clearly identify the slice type of the slice previously accessed by the released first terminal device, such as the first slice type. In order to ensure the service continuity of these terminal devices, the access network device can determine another slice belonging to the first slice type, such as the second slice, and then re-access the previously released first terminal device to the second slice. Of course, before accessing the second slice, it can be determined whether the second slice is an abnormal slice (this action should be performed by the core network device). When there is no exception in the second slice, the first terminal device is accessed to the second slice, and network services are provided to the first terminal device through the second slice.

[0183] It should be noted that all the first terminal devices can be re-connected to the second slice, or some of the first terminal devices can be connected to the second slice, and the remaining first terminal devices can be connected to other slices (such as the third slice or the fourth slice). Of course, the slice types of the third slice and the fourth slice here are the same as those of the first slice and the second slice. In this way, it can be ensured that all the first terminal devices can carry out their services normally after re-connecting to the new slice.

[0184] For example, the AMF where the first slice is located is called the old AMF, and the other AMFs are called the new AMF. Taking the second slice mentioned above as an example, the second slice can be a slice deployed in the old AMF, or it can be a slice deployed in the new AMF. That is to say, after the first terminal device switches the slice, it may also switch the AMF, or it may not switch the AMF.

[0185] When the second slice is a slice deployed in the old AMF, that is, the first slice and the second slice are deployed in the same AMF, according to the correspondence between the slice and the link of the AMF described above, for example, the second slice is bound to the second link, and the first terminal device re-accesses the second slice in the old AMF, it accesses the second slice through the second link between the access network device and the old AMF.

[0186] S1109: The mobility management network element sends abnormal cancellation information to the access network device.

[0187] After the abnormality of the first slice is canceled, for example, after the fault of the first slice that previously failed is recovered, for example, after the first slice that was previously overloaded is no longer overloaded, and for example, after the first slice that was previously disabled is restored to normal use, the AMF can notify the access network device of this state change. Specifically, it can send abnormality cancellation information to the access network device. The abnormality cancellation information is used to indicate that the abnormality of the first slice has been eliminated, so that the access network device can promptly perceive that the abnormality of the first slice in the AMF has been restored, which indicates that the first link between the access network device and the AMF is also restored. Furthermore, the terminal device (for example, called the second terminal device) can be connected to the first slice through the first link, and the second terminal device here can be the first terminal device that has not yet re-accessed the slice, or it can be other terminal devices that have not previously accessed the slice. That is, the second terminal device and the first terminal device can be the same, that is, the same terminal device, or the second terminal device and the first terminal device can also be different, that is, different terminal devices. This is not limited in the embodiments of the present application.

[0188] In an embodiment of the present application, when a slice in the AMF is abnormal, based on the binding correspondence between the slice and the link, the AMF can notify the AN of the link corresponding to the abnormal slice. In this way, the AN can determine that the terminal device currently accessing the AMF through the link is a terminal device accessing the abnormal slice in the AMF, so as to accurately identify the terminal device in the abnormal slice, and then release the terminal device accessing the abnormal slice in a timely manner, thereby improving the flexibility of handling abnormal slices. By disconnecting the network access service of the terminal device, these terminal devices can be facilitated to access the new slice as soon as possible, ensuring the continuous execution of the business, avoiding a major impact on the business of the terminal device, and improving the reliability of the communication system.

[0189] To facilitate understanding of the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application are illustrated below using three scenarios: slice abnormality, slice failure, slice overload, and slice deactivation.

[0190] The process description of the technical solution of the embodiment of the present application in the slice failure / disabled scenario is as follows Figure 12 As shown, Figure 12 In this example, the mobility management network element is represented by AMF and the access network device is represented by AN. Figure 12 The AMF includes two AMFs, namely the first AMF and the second AMF. Figure 12 The process shown is described below.

[0191] S1201. When the first AMF determines that slice 1 deployed in the first AMF fails or is disabled, the first AMF sends an AMF status indication message to the AN through the internal link management module. Correspondingly, the AN receives the AMF status indication message sent by the first AMF.

[0192] The first AMF determines that the link corresponding to slice 1 is link 1 based on the correspondence between the slice and the link, for example, the link corresponding to slice 1 is link 1, and the first link information used to represent link 1 can be carried in the AMF status indication message.

[0193] S1202. AN determines, based on the AMF status indication message, that a slice in the first AMF fails or is disabled, and determines the terminal device that accesses the first AMF through the first link.

[0194] S1203. AN releases the first terminal device that accesses the first AMF through the first link.

[0195] The released first terminal device may be all terminal devices that access the first AMF through the first link, or the released first terminal device may be only part of all terminal devices that access the first AMF through the first link.

[0196] S1204. The first AMF sends an AMF configuration update message to the AN. Correspondingly, the AN receives the AMF configuration update message.

[0197] The AMF configuration update message carries the S-NSSAI of the first slice, for example, S-NSSAI-1, and the S-NSSAI-1 can indicate the slice type of the first slice.

[0198] S1205. The AN determines the slice type of the slice that fails or is disabled in the first AMF according to the S-NSSAI carried in the AMF configuration update message.

[0199] The slice type of the slice that fails or is disabled in the first AMF is the slice type to which the first terminal device that was previously released accessed before being released. In order to ensure that the service of the first terminal device can continue, it is necessary to re-access a new slice for the first terminal device, and in order to meet the service requirements of the first terminal device, the type of the newly accessed slice of the first terminal needs to be consistent with the slice type indicated by the S-NSSAI carried in the AMF configuration update message.

[0200] S1206. AN sends the user message of the first terminal device to slice 2 in the first AMF.

[0201] That is, the slice (i.e., slice 2) that the previously released first terminal device re-accesses is still the slice deployed in the first AMF, and the slice type of slice 2 is the same as the slice type of slice 1 in the first AMF. In this embodiment, although the slice is switched for the terminal device, the AMF is not switched.

[0202] Assuming that according to the correspondence between the configured slices and links, the link corresponding to slice 2 is the second link, then the AN can send the user message of the first terminal device to the link management module in the first AMF through the second link, and then the link management module forwards the user message to slice 2.

[0203] S1207. AN sends the user message of the first terminal device to the second AMF.

[0204] In another possible implementation manner, the slice that the first terminal device that was previously released re-accesses is a slice in another AMF, for example, the first terminal device is re-accessed to a slice in the second AMF (in Figure 12 The slices in the second AMF are not shown, so the user message is sent directly to the second AMF for illustration purposes). This indicates that the AMF has been switched. Of course, the slice type of the slice in the second AMF to which the first terminal device re-accesses is the same as the slice type indicated by the S-NSSAI carried in the AMF configuration update message.

[0205] It should be noted that, since the AN has released the first terminal device in step S1203, for example, the RRC connection between the AN and the first terminal device is disconnected, when it is necessary to provide network access services for the first terminal device again, the first terminal device can first establish an RRC connection with the AN. Further, the relevant technology can be used to specify a slice for the first terminal device, for example, the aforementioned Figure 5 The process shown is for the first terminal device to reselect the slice.

[0206] During the specific implementation process, S1206 and S1207 can be executed one by one, or they can be executed at the same time. When S1206 and S1207 are executed at the same time, different first terminals can be re-connected to the slice.

[0207] S1208. After determining that the fault of slice 1 is eliminated or the deactivation is restored, the first AMF may send fault cancellation indication information to the AN. Correspondingly, the AN receives the fault cancellation indication information.

[0208] S1209. AN sends the user message of the second terminal device to slice 1 in the first AMF.

[0209] The fault cancellation indication information is used to indicate that the abnormal state of the slice where the fault / disabled state occurred in the AMF has been eliminated. In this way, the terminal device can access slice 1 again. Correspondingly, the AN can send the user message of the terminal device (such as the second terminal device) that re-accesses slice 1 to slice 1. Specifically, the user message of the second terminal device is sent to the link management module in the AMF, and then the link management module forwards the user message of the second terminal device to slice 1.

[0210] In an embodiment of the present application, AN identifies the corresponding user (i.e., terminal device) that accesses the faulty / deactivated abnormal slice through the corresponding link based on the link information carried in the AMF status indication message, and then releases the user on the abnormal slice, thereby avoiding business accidents caused by the user being unaware of the abnormality on the network side, and also avoiding new users from being connected to the abnormal slice, thereby improving business reliability.

[0211] The process of the technical solution of the embodiment of the present application in the slice overload scenario is described as follows Figure 13 As shown, Figure 13 In this example, the mobility management network element is represented by AMF and the access network device is represented by AN. Figure 13 The AMF includes two AMFs, namely the first AMF and the second AMF. Figure 13 The process shown is described below.

[0212] S1301. When the first AMF determines that slice 1 deployed in the first AMF is overloaded, the first AMF sends an overload start message to the AN through the internal link management module. Correspondingly, the AN receives the overload start message sent by the first AMF.

[0213] The first AMF determines that the link corresponding to slice 1 is link 1 based on the correspondence between the slice and the link, for example, and can further indicate link 1 through the first link information.

[0214] Among them, the overload start message is a notification message used to indicate slice overload. In the embodiment of the present application, the overload start message in the related technology is utilized, and the overload start message is further carried with the first link information for representing link 1 and NSSAI information for identifying slice 1 (for example, NSSAI-1).

[0215] S1302. The AN determines the first link based on the first link information in the overload start message, and determines the terminal device that accesses the first AMF through the first link.

[0216] S1303. AN releases the first terminal device that accesses the first AMF through the first link.

[0217] The released first terminal device may be all terminal devices that access the first AMF through the first link, or the released first terminal device may be only part of all terminal devices that access the first AMF through the first link.

[0218] S1304. The AN determines the slice type of the slice that fails or is disabled in the first AMF according to the S-NSSAI (for example, the S-NSSAI-1 mentioned above) carried in the overload start message.

[0219] The slice type of the slice that fails or is disabled in the first AMF is the slice type to which the first terminal device that was previously released accessed before being released. In order to ensure that the service of the first terminal device can continue, it is necessary to re-access a new slice for the first terminal device, and in order to meet the service requirements of the first terminal device, the type of the newly accessed slice by the first terminal needs to be consistent with the slice type indicated by the S-NSSAI carried in the overload start message.

[0220] S1305. AN sends the user message of the first terminal device to slice 2 in the first AMF.

[0221] That is, the slice (i.e., slice 2) that the previously released first terminal device re-accesses is still the slice deployed in the first AMF, and the slice type of slice 2 is the same as the slice type of slice 1 in the first AMF. In this embodiment, although the slice is switched for the terminal device, the AMF is not switched.

[0222] Assuming that according to the correspondence between the configured slices and links, the link corresponding to slice 2 is the second link, then the AN can send the user message of the first terminal device to the link management module in the first AMF through the second link, and then the link management module forwards the user message to slice 2.

[0223] S1306. AN sends the user message of the first terminal device to the second AMF.

[0224] In another possible implementation manner, the slice that the first terminal device that was previously released re-accesses is a slice in another AMF, for example, the first terminal device is re-accessed to a slice in the second AMF (in Figure 13 The slices in the second AMF are not shown, so the user message is sent directly to the second AMF for illustration purposes). This indicates that the AMF has been switched. Of course, the slice type of the slice in the second AMF to which the first terminal device re-accesses is the same as the slice type indicated by the S-NSSAI carried in the overload start message.

[0225] S1307. After the first AMF determines that the overload of slice 1 is recovered (ie, no longer overloaded), it may send an overload stop message to the AN again. Correspondingly, the AN receives the overload stop message.

[0226] S1308. The first AMF sends the user message of the second terminal device to slice 1 in the first AMF.

[0227] The overload stop message is a message used to indicate overload recovery. The overload stop message can carry the NSSAI information of the overload recovered slice (such as the aforementioned slice 1). Slice 1 can be directly identified through the NSSAI information.

[0228] That is to say, after the overload recovery of slice 1 is clearly confirmed through the overload stop message, the terminal device can be connected to slice 1 again. Correspondingly, AN can send the user message of the terminal device that re-accesses slice 1 (for example, the second terminal device) to slice 1. Specifically, the user message of the second terminal device is sent to the link management module in AMF, and then the link management module forwards the user message of the second terminal device to slice 1.

[0229] It should be noted that the second terminal device that re-accesses slice 1 can be the aforementioned first terminal device, or it can be other terminal devices, and this embodiment of the application does not limit this.

[0230] In an embodiment of the present application, AN identifies the corresponding user (i.e., terminal device) accessing the overloaded slice through the corresponding link based on the link information carried in the overload start message, and then releases part or all of the users on the overloaded slice, thereby avoiding service accidents caused by the user being unaware of the abnormality on the network side, and also avoiding new users being connected to the overloaded slice to further aggravate the overload level of the overloaded slice, thereby improving service reliability.

[0231] It should be noted that, in the above embodiments, the user message of the terminal device can also be understood as the service message corresponding to the terminal device, that is, the service-related message that the terminal device needs to interact with the network side during the execution of the service.

[0232] In the embodiment of the present application, according to the correspondence between the slices and links configured in the AMF, the data on each slice accessed in the AMF can also be flow controlled (referred to as flow control) at the bottom inlet of the AMF to avoid excessive data from entering the upper layer slices and reduce the impact on the slice level. For ease of understanding, the following is combined with Figure 14 Provide explanation.

[0233] See Figure 14As shown, two links, Link 1 and Link 2, are established between AN and AMF, and two slices, Slice 1 and Slice 2, are deployed in AMF. According to the pre-configuration, the correspondence between the slices and links configured in AMF is: Slice 1 corresponds to Link 1, and Slice 2 corresponds to Link 2. Based on this correspondence, the data sent by AN to slice 1 is transmitted through Link 1, and the data sent by AN to slice 2 is transmitted through Link 2.

[0234] During the data exchange process between AN and AMF, the data sent by AN to each slice in AMF is generally received by the link management module in AMF, and then the link management module forwards the data transmitted through each link to the corresponding slice according to the correspondence between the link and the slice. For example, AN sends a data stream of a certain amount of data to the link forwarding module through the third link. The third link generally refers to any link between AN and AMF, such as Figure 14 The link management module determines that the slice corresponding to the third link is the third slice according to the corresponding relationship between the link and the slice. For example, when the third link is Figure 14 When the link is 1 in , the corresponding third slice is slice 1. For example, when the third link is Figure 14 When link 2 is used, the corresponding third slice is slice 2. The link management module can determine whether the data volume of the data flow transmitted through the third link is greater than a threshold associated with the third slice. If so, the link management module can perform flow control, such as packet loss to reduce the data volume. The packet loss rate for packet loss can be dynamically determined based on the difference between the data volume of the data flow and the threshold. For example, the greater the difference, the greater the packet loss rate can be set, and the smaller the difference, the lower the packet loss rate can be set. Alternatively, fixed packet loss can be performed according to a pre-set constant packet loss rate. In this way, flow control can be performed at the traffic inlet of the AMF. At this time, the data flow has not yet reached the upper slice layer. This can prevent overloaded traffic from entering the corresponding slice, thereby minimizing the probability of slice overload. In addition, the threshold used on each link can be dynamically determined based on the actual traffic currently connected to the third slice. For example, if the traffic currently connected to the third slice is large, the threshold can be set as low as possible to minimize the impact on the slice.

[0235] like Figure 14 As shown in , the link management module performs packet loss processing on the data streams transmitted on link 1 and link 2, and the packet loss rates of the packet loss processing on the two links are different because the threshold corresponding to each link can be dynamically changed.

[0236] In the embodiments of the present application, flow control is performed at the bottom-layer entry point of the AMF (i.e., the link management module), that is, at a more advanced position in the data flow, so that excessive data can be prevented from entering the slice, thereby minimizing the probability of overload at the slice level. In addition, flow control is performed on the link corresponding to each slice based on the correspondence between links and slices, which can avoid mutual influence between slices and improve the reliability of the entire network.

[0237] Based on the same technical concept, the embodiment of the present application provides a communication device, which can be an access network device or a chip set inside the access network device. Figures 9 to 14 The functions of the access network device (AN) in the embodiment shown, for example, the communication device includes executing the above Figures 9 to 14 The modules, units or means corresponding to the steps performed by the access network device in the illustrated embodiment may be implemented by software, hardware or by hardware executing the corresponding software implementation. Figure 15 As shown, the communication device in the embodiment of the present application includes a communication unit 1501 and a processing unit 1502, wherein:

[0238] Communication unit 1501 is configured to receive exception indication information from a mobility management network element, where the exception indication information is used to indicate a first link corresponding to a first slice in which an exception occurs in the mobility management network element, where the first link is a transmission link between an access network device and the mobility management network element;

[0239] Processing unit 1502 is used to release the first terminal device, where the first terminal device is a terminal device that accesses the first slice through the first link.

[0240] In a possible implementation manner, the abnormality occurring in the first slice includes at least one of the following: the first slice fails; or the first slice is overloaded; or the first slice is disabled.

[0241] In a possible implementation, the processing unit 1502 is further configured to determine a first terminal device that meets a priority release condition from all terminal devices that currently access the first slice through the first link.

[0242] In a possible implementation, the communication unit 1501 is further configured to receive slice identification information from a mobility management network element, where the slice identification information is used to indicate a slice type of the first slice.

[0243] In a possible implementation, the communication unit 1501 is further configured to send a service message of the first terminal device to a second slice, where the second slice has the same slice type as the first slice.

[0244] In a possible implementation, the second slice is deployed in a mobility management network element, or the second slice is deployed in other mobility management network elements.

[0245] In a possible embodiment, the communication unit 1501 is also used to receive exception cancellation information from a mobile management network element, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated; and to send the service message of the second terminal device to the first slice through the first link.

[0246] Based on the same technical concept, the embodiment of the present application provides a communication device, which can be a mobility management network element (such as AMF) device or a chip set inside the mobility management network element. Figures 9 to 14 The functions of the mobility management network element in the embodiment shown, for example, the communication device includes the execution of the above Figures 9 to 14 The modules, units, or means corresponding to the steps executed by the mobility management network element in the illustrated embodiment may be implemented by software, hardware, or by hardware executing the corresponding software implementation. Figure 16 As shown, the communication device in the embodiment of the present application includes a processing unit 1601 and a communication unit 1602, wherein:

[0247] The processing unit 1601 is configured to determine that an abnormality occurs in a first slice deployed in the mobility management network element;

[0248] The processing unit 1601 is further configured to determine, based on a predefined correspondence between slices and links, a first link corresponding to the first slice, where the first link is a transmission link between the mobility management network element and the access network device;

[0249] The communication unit 1602 is configured to send abnormality indication information to the access network device, where the abnormality indication information is used to indicate the first link.

[0250] In a possible implementation manner, the abnormality occurring in the first slice includes at least one of the following: the first slice fails; or the first slice is overloaded; or the first slice is disabled.

[0251] In a possible implementation, the communication unit 1602 is further configured to send slice identification information to the access network device, where the slice identification information is used to indicate a slice type of the first slice.

[0252] In a possible embodiment, the processing unit 1601 is also used to determine that the first terminal device accesses the second slice deployed in the mobility management network element through a second link. The second slice has the same slice type as the first slice. The first terminal device is a terminal device released from the first slice by the access network device. In the above-mentioned correspondence between slices and links, the second link corresponds to the second slice.

[0253] In a possible implementation, the communication unit 1602 is further configured to send exception cancellation information to the access network device, where the exception cancellation information is configured to indicate that the exception of the first slice has been eliminated.

[0254] In a possible implementation, the processing unit 1601 is further used to determine that the second terminal device accesses the first slice through the first link.

[0255] In one possible embodiment, the processing unit 1601 is also used to determine that the data volume of the data flow on the third link between the access network device is greater than a threshold, and to perform packet loss processing on the data flow; wherein, in the above-mentioned correspondence between the slice and the link, the third link corresponds to the third slice, and the above-mentioned threshold is determined based on the third slice.

[0256] Based on the same technical concept, see Figure 17 , an embodiment of the present application further provides a communication device, including:

[0257] At least one processor 1701; and a communication interface 1703 in communication with at least one processor 1701; at least one processor 1701 executes instructions stored in the memory 1702, so that the communication device executes the above-mentioned instructions through the communication interface 1703. Figures 9 to 14 The method steps are performed by the access network equipment (AN) in the illustrated embodiment.

[0258] Optionally, the memory 1702 is located outside the communication device.

[0259] Optionally, the communication device includes a memory 1702 , which is connected to at least one processor 1701 , and stores instructions that can be executed by at least one processor 1701 . Figure 17 The dashed lines in FIG. 17 indicate that the memory 1702 is optional for the communication device.

[0260] Among them, at least one processor 1701 and memory 1702 can be coupled through an interface circuit or integrated together, which is not limited here.

[0261] The specific connection medium between the processor 1701, the memory 1702 and the communication interface 1703 is not limited in the embodiment of the present application. Figure 17The processor 1701, the memory 1702 and the communication interface 1703 are connected via a bus 1704. Figure 17 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 17 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0262] Based on the same technical concept, see Figure 18 , an embodiment of the present application further provides a communication device, including:

[0263] At least one processor 1101; and a communication interface 1103 in communication with at least one processor 1101; at least one processor 1101 executes instructions stored in the memory 1102, so that the communication device executes the above-mentioned instructions through the communication interface 1103 Figures 9-14 The steps of the method performed by the mobility management network element (AMF) in the illustrated embodiment.

[0264] Optionally, the memory 1182 is located outside the communication device.

[0265] Optionally, the communication device includes a memory 1182, the memory 1182 is connected to the at least one processor 1181, and the memory 1182 stores instructions that can be executed by the at least one processor 1181. Figure 11 The dashed lines indicate that the memory 1182 is optional for the communication device.

[0266] The processor 1181 and the memory 1182 may be coupled via an interface circuit or may be integrated together, which is not limited here.

[0267] The specific connection medium between the processor 1181, the memory 1182 and the communication interface 1183 is not limited in the embodiment of the present application. Figure 11 The processor 1181, the memory 1182 and the communication interface 1183 are connected via a bus 1184. Figure 11 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0268] It should be understood that the processors mentioned in the embodiments of the present application can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor that is implemented by reading software code stored in a memory.

[0269] Exemplarily, the processor may be a central processing unit (CPU), or other general-purpose processors, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0270] It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0271] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

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

[0273] Based on the same technical concept, the embodiment of the present application also provides a communication system, which includes Figure 15 Communication devices and Figure 16 The communication device in, or including Figure 17 Communication devices and Figure 18 The communication device in.

[0274] Based on the same technical concept, the embodiment of the present application also provides a computer-readable storage medium, including a program or instruction, which, when executed on a computer, enables the above Figures 9 to 14 The method performed by the access network equipment (AN) in the illustrated embodiment is executed.

[0275] Based on the same technical concept, the embodiment of the present application also provides a computer-readable storage medium, including a program or instruction, which, when executed on a computer, enables the above Figures 9 to 14 The method performed by the mobility management network element (AMF) in the illustrated embodiment is executed.

[0276] Based on the same technical concept, the embodiment of the present application further provides a chip, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the above Figures 9 to 14 The method performed by the access network equipment (AN) in the illustrated embodiment is executed.

[0277] Based on the same technical concept, the embodiment of the present application further provides a chip, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the above Figures 9 to 14 The method performed by the mobility management network element (AMF) in the illustrated embodiment is executed.

[0278] Based on the same technical concept, the embodiment of the present application also provides a computer program product, including instructions, which, when executed on a computer, enables the above Figures 9 to 14 The method performed by the access network equipment (AN) in the illustrated embodiment is executed.

[0279] Based on the same technical concept, the embodiment of the present application also provides a computer program product, including instructions, which, when executed on a computer, enables the above Figures 9 to 14The method performed by the mobility management network element (AMF) in the illustrated embodiment is executed.

[0280] The embodiments of the present application are 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 program instructions. These computer program 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. 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.

[0281] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A communication method, characterized in that: The method comprises: The access network device receives abnormality indication information from the mobility management network element, where the abnormality indication information is used to indicate a first link corresponding to a first slice in which an abnormality occurs in the mobility management network element, where the first link is a transmission link between the access network device and the mobility management network element; The access network device releases the first terminal device, where the first terminal device is a terminal device that accesses the first slice through the first link.

2. The method according to claim 1, wherein The abnormality of the first slice includes at least one of the following: The first slice fails; or The first slice is overloaded; or, The first slice is deactivated.

3. The method according to claim 1, wherein The method further comprises: The access network device determines the first terminal device that meets the priority release condition from all terminal devices currently accessing the first slice through the first link.

4. The method according to claim 1, wherein The method further comprises: The access network device receives slice identification information from the mobility management network element, where the slice identification information is used to indicate a slice type of the first slice.

5. The method according to claim 4, wherein The method further comprises: The access network device sends the service message of the first terminal device to the second slice, and the slice type of the second slice is the same as that of the first slice.

6. The method according to claim 5, wherein The second slice is deployed in the mobility management network element, or the second slice is deployed in other mobility management network elements.

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: The access network device receives exception cancellation information from the mobility management network element, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated; The access network device sends the service message of the second terminal device to the first slice through the first link. The first terminal device and the second terminal device are the same terminal device or different terminal devices.

8. A communication method, characterized in that: The method comprises: The mobility management network element determines that an abnormality occurs in a first slice deployed in the mobility management network element; The mobility management network element determines, according to a predefined correspondence between slices and links, a first link corresponding to the first slice, where the first link is a transmission link between the mobility management network element and an access network device; The mobility management network element sends abnormal indication information to the access network device, where the abnormal indication information is used to indicate the first link.

9. The method according to claim 8, wherein The abnormality of the first slice includes at least one of the following: The first slice fails; or The first slice is overloaded; or, The first slice is deactivated.

10. The method according to claim 8, wherein The method further comprises: The mobility management network element sends slice identification information to the access network device, where the slice identification information is used to indicate the slice type of the first slice.

11. The method according to claim 10, wherein The method further comprises: The mobility management network element determines that the first terminal device accesses the second slice deployed in the mobility management network element through a second link. The second slice has the same slice type as the first slice. The first terminal device is a terminal device released from the first slice by the access network device. In the correspondence between the slice and the link, the second link corresponds to the second slice.

12. The method according to claim 8, wherein The method further comprises: The mobility management network element sends exception cancellation information to the access network device, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated.

13. The method according to claim 12, wherein: The method further comprises: The mobility management network element determines that the second terminal device accesses the first slice through the first link.

14. The method according to any one of claims 8 to 13, wherein: The method further comprises: The mobility management network element determines that a data volume of a data flow on a third link between the mobility management network element and the access network device is greater than a threshold, wherein the third link corresponds to a third slice in the correspondence between the slices and the links, and the threshold is determined based on the third slice; The mobility management network element performs packet loss processing on the data flow.

15. A communication device, characterized in that: include: a communication unit, configured to receive exception indication information from a mobility management network element, wherein the exception indication information is used to indicate a first link corresponding to a first slice in which an exception occurs in the mobility management network element, where the first link is a transmission link between an access network device and the mobility management network element; A processing unit is used to release a first terminal device, where the first terminal device is a terminal device that accesses the first slice through the first link.

16. The device according to claim 15, characterized in that The abnormality of the first slice includes at least one of the following: The first slice fails; or The first slice is overloaded; or, The first slice is deactivated.

17. The device according to claim 15, wherein The processing unit is further configured to: Determine the first terminal device that meets the priority release condition from all terminal devices currently accessing the first slice through the first link.

18. The device according to claim 15, wherein The communication unit is further configured to: Receive slice identification information from the mobility management network element, where the slice identification information is used to indicate a slice type of the first slice.

19. The device according to claim 18, wherein The communication unit is further configured to: The service message of the first terminal device is sent to the second slice, and the slice type of the second slice is the same as that of the first slice.

20. The device according to claim 19, wherein The second slice is deployed in the mobility management network element, or the second slice is deployed in other mobility management network elements.

21. The device according to claim 15, wherein The communication unit is further configured to: receiving exception cancellation information from the mobility management network element, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated; Send the service message of the second terminal device to the first slice through the first link.

22. A communication device, characterized in that: include: a processing unit, configured to determine that an abnormality occurs in a first slice deployed in a mobility management network element; The processing unit is further configured to determine, based on a predefined correspondence between slices and links, a first link corresponding to the first slice, where the first link is a transmission link between the mobility management network element and an access network device; A communication unit is used to send abnormal indication information to the access network device, where the abnormal indication information is used to indicate the first link.

23. The device according to claim 22, wherein The abnormality of the first slice includes at least one of the following: The first slice fails; or The first slice is overloaded; or, The first slice is deactivated.

24. The device according to claim 22, wherein The communication unit is further configured to: Slice identification information is sent to the access network device, where the slice identification information is used to indicate the slice type of the first slice.

25. The device according to claim 24, wherein The processing unit is further configured to: Determine that the first terminal device accesses the second slice deployed in the mobility management network element through a second link, the second slice has the same slice type as the first slice, the first terminal device is the terminal device released from the first slice by the access network device, and in the correspondence between the slice and the link, the second link corresponds to the second slice.

26. The device according to claim 22, wherein The communication unit is further configured to: Send exception cancellation information to the access network device, where the exception cancellation information is used to indicate that the exception of the first slice has been eliminated.

27. The device according to claim 26, wherein The processing unit is further configured to: Determine that a second terminal device accesses the first slice through the first link.

28. The device according to any one of claims 22 to 27, characterized in that The processing unit is further configured to: Determine that the data volume of the data flow on the third link between the access network device is greater than a threshold, and perform packet loss processing on the data flow; wherein, in the correspondence between the slice and the link, the third link corresponds to the third slice, and the threshold is determined based on the third slice.

29. A communication device, characterized in that: include: at least one processor; and a memory and a communication interface communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the instructions stored in the memory, so that the device performs the method as described in any one of claims 1-7 or 8-14 through the communication interface.

30. A computer-readable storage medium, characterized in that The method comprises a program or an instruction, which, when being run on a computer, causes the method according to any one of claims 1 to 7 or 8 to 14 to be executed.

Images