Slice selection method, device and related equipment

Abstract

Embodiments of the present application provide a slice selection method and apparatus, and related devices. In the method, an access and mobility management network element determines information of a first slice supporting emergency services in response to an emergency registration request of a terminal device. The access and mobility management network element sends the information of the first slice to a radio access network device, so that the radio access network device establishes an emergency registration procedure and / or an emergency session procedure of the terminal device by using the first slice supporting emergency services. It can be seen that when the terminal device initiates emergency services, the access and mobility management network element can send a slice corresponding to the emergency services to the radio access network device, so that the radio access network device can normally process the emergency services.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a slice selection method, apparatus, and related equipment. Background Art

[0002] The fifth generation of communications th Network slicing technology in 5G (5G generation) creates isolated network environments for different application scenarios by creating independent virtual logical networks on the same network infrastructure. Network slices are deployed in the core network. When a user equipment (UE) initially registers with the network, the network slice selection process is triggered. A network slice is identified by single network slice selection assistance information (S-NSSAI), which is a collection of S-NSSAIs.

[0003] The existing 5G process supports UE-initiated emergency registration and UE-initiated establishment of emergency protocol data unit (PDU) sessions.

[0004] Scenario 1: When the UE initiates the emergency registration process, the UE does not carry the requested network slice selection assistance information (requested NSSAI). The access and mobility management function (AMF) network element determines the allowed NSSAI based on the UE's subscription data, and sends the allowed NSSAI to the UE and the radio access network (RAN) equipment respectively. The allowed NSSAI includes the single network slice selection assistance information (default subscribed S-NSSAI) for which the UE subscribes by default. Afterwards, the emergency registered UE initiates the emergency PDU session establishment process. The AMF selects the session management function (SMF) network element based on the S-NSSAI (also called emergency S-NSSAI) contained in the locally configured emergency configuration data (emergency configuration data). The AMF sends the emergency S-NSSAI to the corresponding SMF, and the SMF then sends the emergency S-NSSAI to the RAN.

[0005] Scenario 2: When the UE initiates a non-emergency registration process, the UE carries the requested NSSAI. The AMF network element determines the allowed NSSAI based on the requested NSSAI and the UE's subscription data, and sends the allowed NSSAI to the UE and RAN equipment respectively. When a non-emergency registered UE initiates an emergency PDU session establishment process, the AMF selects the session management function (SMF) network element based on the S-NSSAI (also called emergency S-NSSAI) contained in the locally configured emergency configuration data. The AMF sends the emergency S-NSSAI to the corresponding SMF, and the SMF sends the emergency S-NSSAI to the RAN.

[0006] In scenarios 1 and 2 above, the emergency S-NSSAI corresponding to the emergency PDU session sent by the SMF to the RAN during the emergency PDU session establishment process may not be included in the allowed NSSAI received by the RAN from the AMF, or the RAN may not support the emergency S-NSSAI corresponding to the session. Therefore, after receiving the emergency S-NSSAI corresponding to the session, the RAN may perform an exception processing, such as rejecting the establishment of the PDU session. Summary of the Invention

[0007] The embodiments of the present application provide a slice selection method, apparatus, and related devices. The slice selection method can select slices supported by the RAN, thereby facilitating the RAN to support emergency services.

[0008] In a first aspect, an embodiment of the present application provides a first slice selection method, which is performed by an access and mobility management network element. The access and mobility management network element receives a registration request message from a terminal device, where the registration type included in the registration request message is emergency registration. In response to the registration request message from the terminal device, the access and mobility management network element determines information about a first slice that supports emergency services, and that the tracking area of ​​the radio access network device to which the terminal device is currently accessing supports the first slice. The access and mobility management network element then sends information about the first slice to the radio access network device, so that the radio access network device uses the first slice that supports the emergency service to complete the emergency registration process for the terminal device. Furthermore, the radio access network device can use the first slice that supports the emergency service to establish a session for the emergency service. Thus, when the terminal device initiates an emergency service, the access and mobility management network element can send information about the first slice that supports the emergency service to the radio access network device, and that the tracking area of ​​the radio access network device to which the terminal device is currently accessing supports the first slice, so that the radio access network device can process the emergency service normally.

[0009] In one possible design, each tracking area of ​​the network currently located by the terminal device supports the first slice. Therefore, all radio access network devices managed by the access and mobility management network element can support the first slice.

[0010] In one possible design, the access and mobility management network element stores information of the first slice in the context.

[0011] In one possible design, the access and mobility management network element is further configured to learn from the radio access network device that the first slice in the tracking area where the radio access network device is located is used to support emergency services. Thus, the access and mobility management network element can learn the service type supported by the first slice, thereby facilitating the access and mobility management network element to send the first slice for emergency services to the radio access network device.

[0012] In one possible design, the access and mobility management network element determines the first slice based on the registration type and the identifier of the tracking area where the wireless access network device is located.

[0013] In one possible design, during the process of establishing an interface connection (e.g., an N2 interface connection) between an access and mobility management network element and a radio access network device, the access and mobility management network element receives indication information from the radio access network device. The indication information is used to indicate that, in the tracking area where the radio access network device is located, the first slice is used to support emergency services. Thus, when the access and mobility management network element establishes an interface connection with the radio access network device, the access and mobility management network element can obtain information about the first slice of the radio access network device that supports emergency services.

[0014] In one possible design, the access and mobility management network element receives a session establishment request message from a terminal device, where the session establishment request message is used to request the establishment of a session for emergency services. In response to the session establishment request message, the access and mobility management network element selects a session management network element based on the information of the first slice and sends the information of the first slice to the session management network element. It can be seen that when the access and mobility management network element receives the emergency session request message from the terminal device, the access and mobility management network element can send the information of the first slice supporting the emergency service to the session management network element, so that the session management network element sends the information of the first slice to the radio access network device, which is conducive to the terminal device and the radio access network device establishing a session supporting the emergency service.

[0015] In one possible design, the access and mobility management network element sends a registration acceptance message to the terminal device. The registration acceptance message does not include slice information, or the registration acceptance message contains information about the slices that the terminal device is allowed to access, and the information about the slices that the terminal device is allowed to access is null. It can be seen that since the terminal device that is urgently registered does not carry slice information when initiating a session request, the access and mobility management network element does not need to send slice information to the terminal device during the registration process, which is conducive to simplifying the transmission of parameters.

[0016] In a second aspect, embodiments of the present application provide a second slice selection method, performed by an access and mobility management network element. During a non-emergency registration process for a terminal device, the access and mobility management network element obtains information about slices that the terminal device is permitted to access. The access and mobility management network element receives a session establishment request message from the terminal device, requesting establishment of a session for emergency services. In response to the session establishment request message, the access and mobility management network element selects a session management network element based on the emergency service configuration information and sends information about the slices that the terminal device is permitted to access to the session management network element. Alternatively, the access and mobility management network element sends information about a first slice that supports emergency services to a radio access network device, where the tracking area of ​​the radio access network device supports the first slice. Thus, in scenarios involving non-emergency registration and establishing an emergency session for a terminal device, the access and mobility management network element can select information about a slice from the information about slices that the terminal device is permitted to access and send it to the radio access network device, or send information about the first slice to the radio access network device. This enables the radio access network device to establish an emergency session with the terminal device.

[0017] In one possible design, the access and mobility management network element sends updated information about slices that the terminal device is allowed to access to the wireless access network device. The updated information about slices that the terminal device is allowed to access includes information about the first slice.

[0018] In one possible design, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0019] In one possible design, the registration type of the terminal device is non-emergency registration.

[0020] In one possible design, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0021] In a third aspect, an embodiment of the present application provides a third slice selection method, which is performed by a radio access network device. The radio access network device receives a registration request message from a terminal device and sends a registration request message to an access and mobility management network element. The registration type included in the registration request message is emergency registration. The radio access network device receives information about a first slice from the access and mobility management network element. The first slice is used to support emergency services, and the tracking area where the radio access network device is located supports the first slice. Therefore, the radio access network device can obtain information about the first slice that supports emergency services, thereby enabling the first slice to be used to support the emergency services of the terminal device.

[0022] In one possible design, during the process of establishing an interface connection between an access and mobility management network element and a radio access network device, the radio access network device sends indication information to the access and mobility management network element. The indication information is used to indicate that the first slice in the tracking area where the radio access network device is located is used to support emergency services. Thus, when the access and mobility management network element establishes an N2 connection with the radio access network device, the radio access network device can inform the access and mobility management network element of information indicating that the first slice of the radio access network device supports emergency services.

[0023] In a fourth aspect, an embodiment of the present application provides a fourth slice selection method, which is performed by a session management network element. The session management network element receives a session establishment request message from a terminal device, where the session establishment request message is used to request the establishment of a session for emergency services. The session management network element receives information about the slices that the terminal device is allowed to access or information about the first slice from the access and mobility management network element. The session management network element sends information about the slices that the terminal device is allowed to access or information about the first slice to the access and mobility management network element. The first slice is used to support emergency services, and the tracking area of ​​the radio access network device to which the terminal device currently accesses supports the first slice. It can be seen that the session management network element can obtain information about the slices that the terminal device is allowed to access or information about the first slice that supports emergency services from the access and mobility management network element, thereby sending information about the slices that the terminal device is allowed to access or information about the first slice that supports emergency services to the radio access network device, which is beneficial for the radio access network device to establish an emergency session with the terminal device.

[0024] In one possible design, the session management network element sends an N2 SM message to the access and mobility management network element, where the N2SM message includes information about the slice to which the terminal device is allowed to access or information about the first slice.

[0025] In one possible design, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0026] In one possible design, the registration type of the terminal device is non-emergency registration.

[0027] In one possible design, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0028] In a fifth aspect, an embodiment of the present application provides a first slice selection device. The slice selection device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive a registration request message from a terminal device. The registration type included in the registration request message is emergency registration. The processing unit is configured to determine information about a first slice in response to the registration request message. The first slice is configured to support emergency services, and the tracking area of ​​the wireless access network device currently accessed by the terminal device supports the first slice. The transceiver unit is further configured to send information about the first slice to the wireless access network device.

[0029] In one possible design, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0030] In one possible design, the processing unit is further configured to store information of the first slice in the context.

[0031] In one possible design, the transceiver unit is also used to obtain from the wireless access network device that, in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

[0032] In one possible design, the transceiver unit is configured to learn from the radio access network device that a first slice in a tracking area where the radio access network device is located is used to support emergency services, including:

[0033] During the process of establishing an interface connection between an access and mobility management network element and a radio access network device, indication information from the radio access network device is received. The indication information is used to indicate that a first slice in a tracking area where the radio access network device is located is used to support emergency services.

[0034] In one possible design, the processing unit is further used to determine the first slice based on the registration type and the identifier of the tracking area where the wireless access network device is located.

[0035] In one possible design, the transceiver unit is further configured to receive a session establishment request message from a terminal device, the session establishment request message being used to request establishment of a session for an emergency service. The processing unit is further configured to, in response to the session establishment request message, select a session management network element based on information about the first slice. The transceiver unit is further configured to send information about the first slice to the session management network element.

[0036] In one possible design, the transceiver unit is further used to send a registration acceptance message to the terminal device. The registration acceptance message does not include information about the slice, or the registration acceptance message includes information about the slice that the terminal device is allowed to access, and the information about the slice that the terminal device is allowed to access is null.

[0037] In a sixth aspect, an embodiment of the present application provides a second slice selection device. The slice selection device includes a transceiver unit and a processing unit. The transceiver unit is used to obtain information about slices that the terminal device is allowed to access during the registration process of the terminal device. The transceiver unit is also used to receive a session establishment request message from the terminal device, and the session establishment request message is used to request the establishment of an emergency service session. The processing unit is used to select a session management network element according to the emergency service configuration information in response to the session establishment request message. The transceiver unit is also used to send information about slices that the terminal device is allowed to access to the session management network element; or, to send information about a first slice to a wireless access network device. The first slice is used to support emergency services, and the tracking area where the wireless access network device currently accessed by the terminal device is located supports the first slice.

[0038] In one possible design, the access and mobility management network element sends updated information about slices that the terminal device is allowed to access to the wireless access network device. The updated information about slices that the terminal device is allowed to access includes information about the first slice.

[0039] In one possible design, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0040] In one possible design, the registration type of the terminal device is non-emergency registration.

[0041] In one possible design, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0042] In a seventh aspect, an embodiment of the present application provides a third slice selection device. The slice selection device includes a transceiver unit. The transceiver unit is configured to receive a registration request message from a terminal device and send the registration request message to an access and mobility management network element. The registration type included in the registration request message is emergency registration. The transceiver unit is further configured to receive information about a first slice from the access and mobility management network element, where the first slice is used to support emergency services. The tracking area of ​​the radio access network device currently accessed by the terminal device supports the first slice.

[0043] In one possible design, the transceiver unit is further configured to send indication information to the access and mobility management network element during an interface connection establishment process between the access and mobility management network element and the radio access network device. The indication information is configured to indicate that, in a tracking area where the radio access network device is located, the first slice is used to support emergency services.

[0044] In an eighth aspect, an embodiment of the present application provides a fourth slice selection device. The slice selection device includes a transceiver unit. The transceiver unit is used to receive a session establishment request message from a terminal device, and the session establishment request message is used to request the establishment of an emergency service session. The transceiver unit is also used to receive information about a slice that the terminal device is allowed to access or information about a first slice from an access and mobility management network element. The first slice is used to support emergency services, and the tracking area of ​​the wireless access network device currently accessed by the terminal device supports the first slice. The transceiver unit is also used to send information about the slice that the terminal device is allowed to access or information about the first slice to the access and mobility management network element.

[0045] In one possible design, the session management network element sends an N2 SM message to the access and mobility management network element, where the N2SM message includes information about the slice to which the terminal device is allowed to access or information about the first slice.

[0046] In one possible design, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0047] In one possible design, the registration type of the terminal device is non-emergency registration.

[0048] In one possible design, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0049] In a ninth aspect, an embodiment of the present application provides an access and mobility management network element. The access and mobility management network element may be a device or a chip or circuit disposed in a device. The access and mobility management network element includes a unit and / or module for executing the slice selection method provided in any possible design of the first aspect above, thereby also achieving the beneficial effects of the slice selection method provided in the first aspect.

[0050] In a tenth aspect, an embodiment of the present application provides an access and mobility management network element. The access and mobility management network element may be a device or a chip or circuit disposed in a device. The access and mobility management network element includes a unit and / or module for executing the slice selection method provided in any possible design of the second aspect above, thereby also achieving the beneficial effects of the slice selection method provided in the second aspect.

[0051] In an eleventh aspect, embodiments of the present application provide a wireless access network device. The wireless access network device may be a device or a chip or circuit disposed in the device. The wireless access network device includes a unit and / or module for executing the slice selection method provided in any possible design of the third aspect above, thereby also achieving the beneficial effects of the slice selection method provided in the third aspect.

[0052] In a twelfth aspect, embodiments of the present application provide a session management network element. The session management network element may be a device or a chip or circuit disposed in the device. The session management network element includes a unit and / or module for executing the slice selection method provided in any possible design of the fourth aspect, thereby also achieving the beneficial effects of the slice selection method provided in the fourth aspect.

[0053] In a thirteenth aspect, an embodiment of the present application provides a communication system, which includes an access and mobility management network element provided in the fifth or ninth aspect and a wireless access network device provided in the seventh or eleventh aspect.

[0054] In a fourteenth aspect, an embodiment of the present application provides a communication system, which includes the access and mobility management network element provided in the sixth or tenth aspect and the session management network element provided in the eighth or twelfth aspect.

[0055] In the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes a program or instructions. When the program or instructions are run on a computer, the computer executes the method in any possible implementation of the first to fourth aspects.

[0056] In the sixteenth aspect, an embodiment of the present application provides a computer program or computer program product, including code or instructions, which, when the code or instructions are run on a computer, enables the computer to execute the method in any possible implementation of the first to fourth aspects.

[0057] In the seventeenth aspect, an embodiment of the present application provides a chip or a chip system, which includes at least one processor and an interface, the interface and the at least one processor are interconnected by lines, and the at least one processor is used to run computer programs or instructions to perform the method described in any one of the possible implementation methods of the first to fourth aspects.

[0058] The interface in the chip may be an input / output interface, a pin, or a circuit.

[0059] The chip system in the above aspects may be a system on chip (SOC) or a baseband chip, etc., wherein the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem and an interface module, etc.

[0060] In one possible implementation, the chip or chip system described above in this application further includes at least one memory, in which instructions are stored. The memory may be a storage unit within the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.). BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1a A schematic diagram of a network system based on a service-oriented interface provided in an embodiment of the present application;

[0062] Figure 1b A schematic diagram of a network system based on a point-to-point interface provided in an embodiment of the present application;

[0063] Figure 2 A schematic diagram of a flow chart of a slice selection method provided in an embodiment of the present application;

[0064] Figure 3a An application scenario in which the same network slice identifier is configured for multiple tracking areas provided in an embodiment of the present application;

[0065] Figure 3b An application scenario in which different network slice identifiers are configured for multiple tracking areas provided in an embodiment of the present application;

[0066] Figure 4 A flowchart of a method for slice selection based on emergency configuration data provided in an embodiment of the present application;

[0067] Figure 5 A flowchart of a method for slice selection based on information about slices supported by a wireless access network device provided in an embodiment of the present application;

[0068] Figure 6 A schematic diagram of a flow chart of another slice selection method provided in an embodiment of the present application;

[0069] Figure 7 A flowchart of a slice selection method for a scenario in which a terminal device initiates non-emergency registration and an emergency session, provided in an embodiment of the present application;

[0070] Figure 8 A schematic diagram of a slice selection device provided in an embodiment of the present application;

[0071] Figure 9 A schematic diagram of an access and mobility management network element provided in an embodiment of the present application;

[0072] Figure 10 A schematic diagram of another slice selection device provided in an embodiment of the present application;

[0073] Figure 11 A schematic diagram of a wireless access network device provided in an embodiment of the present application;

[0074] Figure 12 A schematic diagram of another slice selection device provided in an embodiment of the present application;

[0075] Figure 13 A schematic diagram of a session management network element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0077] The fifth generation of communications th The network slicing technology in 5G (5G generation) realizes the provision of isolated network environments for different application scenarios by creating virtual independent logical networks on the same network infrastructure. Among them, the goal of network slicing (also referred to as slicing in the embodiment of the present application) is to organically combine terminal equipment, wireless access network equipment, core network network elements, and network operation and maintenance and management systems to provide independent operation and maintenance and isolated networks for different business scenarios or business types. Among them, the network slices do not affect each other. For example, sudden IoT services will not affect normal mobile broadband services. Among them, instances of different business types are deployed on different network slices, and different instances of the same business type can also be deployed on different network slices, which is conducive to ensuring that network slices do not affect each other.

[0078] When network slicing is deployed in the core network and the user equipment (UE) initially registers with the network, the network slice selection process is triggered. Among them, a network slice is identified by a single network slice selection assistance information (S-NSSAI). S-NSSAI consists of a slice / service type (SST) and a slice differentiator (SD). Among them, SST is used to describe the characteristics of the slice itself and its business characteristics. SD is optional information used to distinguish different network slices with the same SST characteristics. NSSAI is a collection of S-NSSAIs, that is, multiple network slices can be identified by NSSAI. The NSSAI in the 5G network can be a configured NSSAI, a requested NSSAI, or an allowed NSSAI.

[0079] The existing 5G process supports UE-initiated emergency registration and UE-initiated emergency protocol data unit (PDU) sessions. In one scenario, when the UE initiates an emergency registration, the UE does not carry the requested NSSAI in the registration request message. The access and mobility management function (AMF) network element sends the allowed NSSAI to the UE and the radio access network (RAN) device respectively. The allowed NSSAI is determined by the AMF based on the default subscribed single network slice selection auxiliary information (default subscribedS-NSSAI). Moreover, after the UE initiates an emergency registration, the UE can only initiate an emergency PDU session. However, the session establishment request message sent by the UE does not carry the S-NSSAI. Then the AMF selects the session management function (SMF) based on the S-NSSAI (also called emergency S-NSSAI) and data network name (DNN) parameters contained in the locally stored emergency configuration data, and forwards the S-NSSAI and / or DNN to the SMF. After the SMF processes the UE's session establishment request message, it will not provide the S-NSSAI to the UE during the session establishment process.

[0080] In another scenario, when the UE initiates a non-emergency registration process, the UE carries the requested NSSAI. The AMF network element determines the UE's allowed NSSAI based on the requested NSSAI and the UE's subscription data, and sends the UE's allowed NSSAI to the UE and RAN equipment respectively. When a non-emergency registered UE initiates an emergency PDU session establishment process, after the AMF receives the PDU session establishment request message, the AMF selects the SMF network element based on the emergency S-NSSAI contained in the locally configured emergency configuration data. The AMF sends the emergency S-NSSAI to the SMF network element. Subsequently, the SMF sends the emergency S-NSSAI to the RAN.

[0081] In the first scenario, the allowed NSSAI in the emergency registration process (called the first type of allowed NSSAI) is determined based on the default subscribed S-NSSAI. In the second scenario, the allowed NSSAI in the non-emergency registration process (called the second type of allowed NSSAI) is determined based on the requested NSSAI and the UE's subscription data. Therefore, the allowed NSSAI determined by the AMF is different in the two different registration processes.

[0082] In the above two scenarios, during the emergency PDU session establishment process, the emergency S-NSSAI corresponding to the session sent by the SMF to the RAN may not include the allowed NSSAI received by the RAN from the AMF (that is, the emergency S-NSSAI is not included in the allowed NSSAI of the first type mentioned above nor in the allowed NSSAI of the second type mentioned above). Therefore, after the RAN receives the emergency S-NSSAI corresponding to the session, the emergency S-NSSAI corresponding to the session may not be included in the allowed NSSAI received by the RAN from the AMF, or the RAN may not support the emergency S-NSSAI corresponding to the session. As a result, the RAN may make abnormal processing, such as rejecting the establishment of the PDU session.

[0083] In addition, in the first scenario, the slice identifier in the allowed NSSAI sent by the AMF to the UE in the above registration process will not be used for the UE to initiate the establishment of an emergency PDU session. Therefore, the allowed NSSAI containing the defaultsubscribed S-NSSAI sent by the AMF to the UE is redundant.

[0084] An embodiment of the present application provides a slice selection method, in which the AMF selects a slice supported by the RAN, thereby enabling the RAN to use the first slice selected by the AMF to support emergency services.

[0085] The slice selection method provided in the embodiment of the present application is applied to Figure 1a or Figure 1b In the network system shown in FIG. Figure 1a This is a schematic diagram of a network system based on a service-oriented interface. Figure 1b Schematic diagram of a network system based on point-to-point interface. Figure 1a or Figure 1bThe network system shown includes three parts, namely, a terminal device part, a data network (DN) and an operator network part.

[0086] The operator network includes one or more of the following network elements: network slice selection function (NSSF) network element, network repository function (NRF) network element, policy control function (PCF) network element, unified data management (UDM) network element, application function (AF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, radio access network (RAN) and user plane function (UPF) network element. In the above-mentioned operator network, the part other than the radio access network part can be called the core network part.

[0087] The AMF is responsible for user mobility management, including mobility status management, assigning temporary user identities, authenticating and authorizing users, etc. The interface between the AMF and the terminal device is the N1 interface, and the interface between the AMF and the RAN is the N2 interface.

[0088] SMF is responsible for UPF network element selection or reselection, Internet protocol (IP) address allocation, PDU session establishment, modification and release, and quality of service (QoS) control.

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

[0090] PCF is used to provide management of non-session policies such as user access control and slice selection, as well as management of session policies such as session binding, session control, QoS control, and billing control.

[0091] The AF is used to provide application layer services to the UE. When providing services to the UE, the AF has requirements for QoS and charging policies. The AF also requires application-related information from the core network.

[0092] UPF is used to interconnect with DN to implement functions such as packet routing and forwarding, and data packet detection.

[0093] NSSF is responsible for the selection of network slices.

[0094] NRF is responsible for the registration and discovery of network elements and maintains the information of network elements.

[0095] Among them, RAN can provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data based on the user level, business requirements, etc. The access network forwards control signals and user data between the terminal device and the core network. The access network can include access network equipment (or called access equipment), which can be, for example, a base station in an LTE system (such as an eNB) or a base station in a new radio (NR) system (such as NG-RAN), a base station of subsequent evolution of 3GPP, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, or a balloon station, etc.

[0096] Among them, a terminal device is a device with wireless transceiver capabilities and can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons, and satellites). The terminal device can be a UE, a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, an in-vehicle terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal device, etc. The terminal device can be fixed or mobile.

[0097] The DN is used to provide business services to users. It can be a private network, such as a local area network (LAN); an external network not controlled by the operator, such as the Internet; or a proprietary network jointly deployed by operators, such as a network that provides an IP multimedia subsystem (IMS).

[0098] The key terms involved in the embodiments of this application are described below.

[0099] Network slice: A logical network that provides specific network functions and network characteristics. In this embodiment, it is also called a slice.

[0100] Network slice instance: A set of network function instances and the required resources (e.g., compute, storage, and network resources) that constitute a deployed network slice.

[0101] Information on slices allowed to be accessed by the terminal device (allowed NSSAI): NSSAI provided by the serving public land mobile network (PLMN). During the registration process of the terminal device, it indicates the S-NSSAI value that the UE can use for the current registration area in the serving PLMN (that is, the S-NSSAI value supported by the tracking area where the RAN currently accessed by the terminal device is located). Among them, allowed NSSAI can contain one or more S-NSSAIs. Any S-NSSAI contained in the allowed NSSAI (that is, S-NSSAI from allowed NSSAI) can also be called information on slices allowed to be accessed by the terminal device.

[0102] Requested Network Slice Selection Assistant Information (requested NSSAI): The NSSAI provided by the UE to the serving PLMN during the registration process. The requested NSSAI is used to indicate the identity of the network slice that the UE requests to access.

[0103] Default subscribed single network slice selection auxiliary information (default subscribed S-NSSAI): When the UE subscribes to the serving PLMN, the UE subscription information contains the S-NSSAI marked as default.

[0104] Figure 2 A flow chart of a slice selection method provided in an embodiment of the present application, wherein the method is implemented by interaction between the access and mobility management network element AMF and the radio access network device RAN. Figure 2 The slice selection method shown is applied to a network scenario when a terminal device initiates an emergency registration.

[0105] 201. The wireless access network device receives a registration request message from a terminal device and sends the registration request message to an access and mobility management network element. The registration type included in the registration request message is emergency registration. Correspondingly, the access and mobility management network element receives the registration request message.

[0106] 202. In response to the registration request message, the access and mobility management network element determines the information of the first slice, which is used to support emergency services; the tracking area where the wireless access network device currently accessed by the terminal device supports the first slice.

[0107] 203. The access and mobility management network element sends information about the first slice to the wireless access network device.

[0108] When the terminal device initiates an emergency registration process, the terminal device sends a registration request message to the RAN. After receiving the registration request message, the RAN sends the registration request message to the AMF. The registration type included in the registration request message is emergency registration, which means that the terminal device is initiating an emergency registration this time. Correspondingly, the AMF receives the registration request message and determines that the registration request message is an emergency registration request message. In response to the registration request message, the AMF determines the information of the slice that supports emergency services and allows the terminal device to access (i.e., the information of the first slice). The information of the first slice is used to identify the first slice. As an implementation method, the information of the first slice can be an identifier of the first slice, such as S-NSSAI.

[0109] In one implementation, when the AMF determines that the current registration of the terminal device is an emergency registration, the AMF selects the S-NSSAI (i.e., the first slice) from the locally stored emergency configuration data as the allowed NSSAI and sends it to the RAN. That is, the AMF determines the information of the first slice based on the locally stored emergency configuration data, that is, the first slice is the slice identified by the emergency S-NSSAI. Among them, the emergency configuration data may contain one or more S-NSSAIs, which is not limited in the embodiment of the present application. When the emergency configuration data contains multiple S-NSSAIs, the AMF can select any slice identified by the S-NSSAI as the first slice. The first slice is used to support emergency services, and the S-NSSAI of the first slice is sent to the RAN by the AMF as the allowed NSSAI. In this implementation, each tracking area (TA) under the network where the terminal device is currently located supports the S-NSSAI contained in the emergency configuration data, which can be understood as each tracking area under the network where the terminal device is currently located supports the first slice. This means that the operator configures the S-NSSAI included in the emergency configuration data for all TAs in the current network to support emergency services. That is, all TAs in the current network are configured with the same S-NSSAI to support emergency services. If the emergency configuration data contains multiple S-NSSAIs, each TA in the network is also configured with multiple S-NSSAIs to support emergency services.

[0110] In addition, the S-NSSAI corresponding to the first slice can also be sent directly to the RAN, that is, it does not need to be included in the allowedNSSAI, which is not limited in the embodiments of the present application. It can be understood that the method for the access and mobility management network element to send the information of the first slice to the wireless access network device can be: the access and mobility management network element includes the identifier of the first slice in the allowedNSSAI and sends it to the wireless access network device, or the access and mobility management network element sends it to the wireless access network device in other forms (for example, the identifier of the first slice is sent to the wireless access network device separately), which is not limited in the embodiments of the present application.

[0111] For example, Figure 3a An application scenario in which the same network slice identifier is configured for multiple tracking areas provided in an embodiment of the present application. The tracking areas in this application scenario include TA1, TA2, and TA3. TA1, TA2, and TA3 are configured with the same S-NSSAI to support emergency services. In this case, the network slices supporting emergency services are unified across the entire network, that is, the entire network uses the same slices to support emergency services. Even if the terminal device moves out of the current TA and is located in another TA, the other TAs still support the first slice corresponding to the emergency service, thereby ensuring the continuity of the emergency service.

[0112] In another implementation, when the AMF determines that the type of this registration of the terminal device is an emergency registration, the AMF sends the pre-acquired S-NSSAI that supports emergency services in the tracking area where the RAN is located as the allowed NSSAI to the RAN. Specifically, the AMF can select the S-NSSAI that supports emergency services from the information of the slices supported by the RAN that is pre-received and send it to the RAN as the allowed NSSAI. For example, during the process of establishing the interface connection between the AMF and the RAN, the AMF receives information about the slices supported by the RAN, and receives indication information from the RAN. It is assumed that the slices supported by the RAN include three slices, and the indication information is used to indicate the S-NSSAI that supports emergency services in the tracking area where the RAN is located (wherein the slices that support emergency services are included in the three slices supported by the RAN). In this implementation, the S-NSSAI that supports emergency services in different TAs may be different or the same. However, there is at least one S-NSSAI that supports emergency services in any TA in the entire network. For example, Figure 3bAn application scenario in which different network slice identifiers are configured for multiple tracking areas provided in an embodiment of the present application. The tracking areas in this application scenario include TA1, TA2 and TA3. TA1, TA2 and TA3 are configured with different S-NSSAIs to support emergency services (TA1 is configured with S-NSSAI 1, TA2 is configured with S-NSSAI2, and TA3 is configured with S-NSSAI3, all of which support emergency services). In this case, the network slices supporting emergency services may not be unified across the entire network, that is, different slices may be used in different TAs across the entire network to support emergency services. Regardless of which of the above methods is adopted, the TA where the RAN to which the terminal device is currently accessed is located is able to support the first slice determined by the AMF, and the first slice is used to support emergency services.

[0113] After the AMF determines the information of the first slice, it sends a response message to the RAN. The response message includes an N2 message sent to the RAN and a registration acceptance message sent to the terminal device (the registration acceptance message is transparently transmitted by the RAN). The N2 message includes information about the first slice. For example, the AMF sends an N2 message to the RAN, and the N2 message includes information about the first slice.

[0114] Through the above method, when the terminal device initiates an emergency service, the access and mobility management network element can send information about the first slice that supports the emergency service to the wireless access network device, and the tracking area where the wireless access network device to which the terminal device is currently accessed supports the first slice, so that the wireless access network device can handle the emergency service normally.

[0115] In one implementation, the registration acceptance message does not include the allowed NSSAI, or the allowed NSSAI in the registration acceptance message is an empty allowed NSSAI (empty allowed NSSAI). It should be noted that, in this embodiment, the parameters included in the allowed NSSAI sent by the AMF to the terminal device and the allowed NSSAI sent to the RAN may be different. For the convenience of distinction, the allowed NSSAI sent to the RAN may also be referred to as N2 allowed NSSAI, and the allowed NSSAI sent to the terminal device may be referred to as N1 allowed NSSAI. That is, the registration acceptance message transparently transmitted to the terminal device through the RAN does not include information about the slice, or the registration acceptance message transparently transmitted to the terminal device through the RAN includes N1 allowed NSSAI, and the N1 allowed NSSAI contains empty allowed NSSAI.

[0116] In addition, the S-NSSAI corresponding to the first slice can also be sent directly to the RAN, that is, it does not need to be included in the allowedNSSAI, which is not limited in the embodiments of the present application. It can be understood that the method for the access and mobility management network element to send the information of the first slice to the wireless access network device can be: the access and mobility management network element includes the identifier of the first slice in the allowedNSSAI and sends it to the wireless access network device, or the access and mobility management network element sends it to the wireless access network device in other forms (for example, the identifier of the first slice is sent to the wireless access network device separately), which is not limited in the embodiments of the present application.

[0117] It can be seen that since the terminal device does not carry slice information when initiating a session request, the access and mobility management network element does not need to send slice information to the terminal device, which is conducive to simplifying parameter transmission.

[0118] Below Figure 2 The two implementation methods in the embodiment are described in detail respectively.

[0119] Figure 4 A flowchart of a method for slice selection based on emergency configuration data provided in an embodiment of the present application. Figure 4 The overall process of the embodiment includes the emergency registration process and the emergency session process, which is implemented by the interaction between the terminal device, RAN, AMF and SMF. Specifically, it includes the following steps:

[0120] 401. The terminal device sends a registration request message to the RAN and AMF, where the registration type included in the registration request message is emergency registration.

[0121] Before receiving the registration request message, the AMF pre-configures emergency configuration data, which includes S-NSSAI to support emergency services. Figure 3a In the network scenario shown, the entire network uses the same slice to support emergency services. That is, the emergency configuration data pre-configured by the AMF includes the S-NSSAI that supports emergency services, and the RAN currently serving the UE supports the S-NSSAI. Optionally, the S-NSSAI is the S-NSSAI supported by all RANs in the entire network. Then the first slice determined by the AMF based on the emergency configuration data is also a slice supported by the RAN, which is conducive to completing the emergency registration process and emergency session process of the terminal device.

[0122] 402. AMF determines that the terminal device initiates an emergency registration and determines the information of the first slice based on the emergency configuration data. The first slice is used to support emergency services.

[0123] Optionally, AMF uses the information of the first slice as the information of the slice allowed to be accessed by the terminal device (allowedNSSAI).

[0124] The allowed NSSAI is the N2 allowed NSSAI sent by the AMF to the RAN.

[0125] At the same time, the AMF saves the N2 allowed NSSAI in the context of the terminal device. The AMF can store the N2 allowed NSSAI in the UE context at any time between steps 402 and 405 (for example, Figure 4 The step of AMF storing N2 allowed NSSAI in the UE context is located between steps 403 and 404), which is not limited in this application.

[0126] 403. The AMF sends a response message to the RAN. The response message includes an N2 message sent to the RAN and a registration acceptance message sent to the terminal device. The N2 message includes the N2 allowed NSSAI, and the registration acceptance message includes an empty N1 allowed NSSAI or does not include slice information. Correspondingly, the RAN receives the response message.

[0127] Among them, N2 allowed NSSAI contains the identifier of the first slice.

[0128] 404. RAN sends a registration acceptance message to the terminal device. The registration acceptance message includes an empty N1 allowedNSSAI or does not include slice information.

[0129] 405. The terminal device sends a session establishment request message to the AMF. The session establishment request message does not include slice information (no S-NSSAI). The session establishment request is used to establish an emergency PDU session.

[0130] 406. AMF selects SMF according to information of the first slice, where SMF supports the first slice.

[0131] The specific implementation of step 406 of this embodiment may include the following process: the AMF selects an SMF based on the identifier of the first slice contained in the N2 allowed NSSAI stored in the context of the terminal device. The SMF selected by the AMF supports the first slice.

[0132] 407, AMF sends the information of the first slice to SMF; correspondingly, SMF receives the information of the first slice;

[0133] Among them, the specific implementation method of step 407 of this embodiment may include the following process: AMF calls the SMF service operation Nsmf_PDUSession_CreateSMContext Request, carrying S-NSSAI.

[0134] 408. SMF sends an N2 SM message and an N1 SM message to AMF, wherein the N2 SM message is a message sent to the radio access network device RAN, and the N2 SM message contains information about the first slice; the N1 SM message is a message sent to the terminal device. The N2 SM message (N2 SM message) described in the embodiment of the present application is also called N2 SM information (N2SMinformation). The two have the same meaning and include the same information. The N1 SM message (N1SM message) described in the embodiment of the present application is also called N1 SM information (N1 SM information) or N1 SM container (N1 SMcontainer). The two have the same meaning and include the same information.

[0135] In addition, the N1 SM message also includes a PDU session establishment accept message (PDU session establishment accept), which does not contain slice information.

[0136] The specific implementation of step 408 of this embodiment may include the following process: the SMF calls the service-based operation Namf_Communication_N1N2MessageTransfer, carrying the N2 SM message and the N1 SM message. The N2 SM message is a message sent to the RAN and includes the identifier of the first slice. The N1 SM message is a message sent to the terminal device.

[0137] 409. The AMF sends an N2 PDU Session Request message to the RAN. The N2 PDU Session Request message includes an N2 SM message and an N1 SM message.

[0138] 410. RAN sends an N1 SM message to the terminal device, where the N1 SM message also includes a session establishment accept message, and the session establishment accept message does not include slice information.

[0139] It can be seen that the slice selection method provided in the embodiment of the present application is applicable to the scenarios of emergency registration and emergency session establishment. Among them, the AMF selects the first slice that supports emergency services and sends information about the first slice to the RAN. In addition, the tracking area where the RAN is located supports the first slice. Then, the RAN uses the first slice to complete the emergency registration process and / or emergency session process of the terminal device.

[0140] Figure 5 A flowchart of a method for slice selection based on information on slices supported by the RAN provided in an embodiment of the present application. Figure 5 The overall process of the embodiment includes the emergency registration process and the emergency session process, which is implemented by the interaction between the terminal device, RAN, AMF and SMF. Specifically, it includes the following steps:

[0141] 501. RAN sends a connection establishment request message of the N2 interface to the AMF. The connection establishment request message includes information about the slices supported in the TA where the RAN is located and indication information. The indication information is used to indicate that in the TA where the RAN is located, the first network slice is used to support emergency services.

[0142] In step 501 of this embodiment, the connection establishment request message received by the AMF from the RAN may be an N2 connection request. The N2 connection request may be used to indicate information about multiple slices (S-NSSAIs) supported by the TA where the RAN is located, and at least one of the multiple slices supports emergency services.

[0143] The TA where the RAN is located can be represented by a tracking area identity (TAI). The slice information can be represented by an S-NSSAI. The slices supported in the TA where the RAN is located include the first network slice.

[0144] The indication information in this embodiment can be used in various ways to indicate: the TA where the RAN is located, and the first network slice used to support emergency services. For example, assume that the N2 connection request in this embodiment indicates that the TA where the RAN is located supports three slices, corresponding to S-NSSAI 1, S-NSSAI 2, and S-NSSAI 3, respectively. Table 1 shows the format of indication information provided in an embodiment of the present application.

[0145] Table 1: Format of an instruction message

[0146] Slice identification Service types supported by slices S-NSSAI 1 Support emergency services S-NSSAI 2 Support non-emergency services S-NSSAI 3 Support non-emergency services

[0147] Optionally, Table 2 is another format of indication information provided in an embodiment of the present application.

[0148] Table 2: Another format of instruction information

[0149]

[0150] Among them, the "service type supported by the slice" in Table 1 or the "identification of the slice supporting emergency services" in Table 2 can be used as indication information to indicate that S-NSSAI 1 is the identifier of the slice supporting emergency services in the TA where the RAN is located. This embodiment does not limit which specific indication method is used. Of course, other methods can also be used to indicate that in the TA where the RAN is located, the first network slice is used to support emergency services. This application does not limit this.

[0151] 502. AMF sends a connection establishment response message to RAN. The connection establishment response message may include information about the slices supported by AMF.

[0152] In step 502, the connection establishment response message sent by the AMF to the RAN may be an N2 connection response. The N2 connection response carries information about the slices supported by the AMF.

[0153] 503. The terminal device sends a registration request message to the RAN and AMF, where the registration type included in the registration request message is emergency registration.

[0154] 504. AMF determines that the terminal device initiates an emergency registration and determines the information of the first slice based on the information of the slice that supports emergency services in the TA where the RAN is located. The first slice is used to support emergency services.

[0155] Optionally, the AMF uses the information of the first slice as the information of the slice allowed to be accessed by the terminal device (allowedNSSAI).

[0156] The allowed NSSAI determined in step 504 of this embodiment is only used to be sent to the RAN and does not need to be sent to the terminal device. The allowed NSSAI determined in step 504 may also be referred to as N2 allowed NSSAI.

[0157] At the same time, the AMF saves the N2 allowed NSSAI in the context of the terminal device. The AMF can store the N2 allowed NSSAI in the UE context at any time between steps 504 and 507 (for example, Figure 5 The step of AMF storing N2 allowed NSSAI in the UE context is located between steps 504 and 505) which is not limited in this application.

[0158] 505. The AMF sends a response message to the RAN. The response message includes an N2 message sent to the RAN and a registration acceptance message sent to the terminal device. The N2 message includes information about the slices allowed to be accessed by the terminal device (i.e., N2 allowed NSSAI); the registration acceptance message includes an empty N1 allowed NSSAI or does not include slice information. Correspondingly, the RAN receives the response message.

[0159] Among them, N2 allowed NSSAI contains the identifier of the first slice.

[0160] 506. RAN sends a registration acceptance message to the terminal device, where the registration acceptance message includes an empty N1 allowedNSSAI or does not include slice information.

[0161] 507. The terminal device sends a session establishment request message to the AMF. The session establishment request message does not include slice information (no S-NSSAI). The session establishment request is used to establish an emergency PDU session.

[0162] 508. The AMF selects an SMF based on the information of the first slice, where the SMF supports the first slice.

[0163] 509. AMF sends the information of the first slice to SMF; correspondingly, SMF receives the information of the first slice.

[0164] 510. SMF sends an N2 SM message and an N1 SM message to AMF, where the N2 SM message is a message sent to the RAN and contains information about the first slice; the N1 SM message is a message sent to the terminal device and also includes a PDU session establishment accept message (PDU session establishment accept), which does not contain information about the slice.

[0165] 511. The AMF sends an N2 PDU Session Request message to the RAN, where the N2 PDU Session Request message includes an N2 SM message and an N1 SM message.

[0166] 512. RAN sends an N1 SM message to the terminal device, where the N1 SM message also includes a session establishment accept message, but the session establishment accept message does not include slice information.

[0167] The specific implementation of the above steps 505-512 can refer to Figure 4 The description of the specific implementation of steps 403-410 in the embodiment will not be repeated here.

[0168] It can be seen that the slice selection method provided in the embodiment of the present application is applicable to the scenarios of emergency registration and emergency session establishment. Among them, there is a slice in the slice set supported by the RAN that can support emergency services. The AMF selects a slice that can support emergency services for the emergency service and sends information about the selected slice to the RAN. Then, the RAN adopts the selected slice to complete the emergency registration process and / or emergency session process of the terminal device.

[0169] Figure 6 A flowchart of another slice selection method provided in an embodiment of the present application, wherein the method is implemented by interaction between the terminal device, RAN, AMF and SMF. Figure 6 The slice selection method shown is applied to a network scenario where a terminal device initiates a non-emergency registration but needs to establish an emergency session, and includes the following steps:

[0170] 601. During the registration process of the terminal device, AMF obtains the information allowedNSSAI of the slices that the terminal device is allowed to access.

[0171] Optionally, during the registration process of the terminal device, the AMF sends the allowed NSSAI to the terminal device and RAN respectively.

[0172] It can be understood that in this embodiment, the allowed NSSAI sent by the AMF to the terminal device contains the same parameters as the allowed NSSAI sent to the RAN. In this embodiment, the registration process initiated by the terminal device is a non-emergency registration process. The detailed steps of the non-emergency registration process can be referred to the description in the existing standard and will not be repeated here.

[0173] Through the non-emergency registration process, AMF can obtain information about the slices that the terminal device is allowed to access (allowed NSSAI) according to the existing mechanism. The method for AMF to obtain the allowed NSSAI can be that the AMF network element determines the allowed NSSAI based on the contract information of the terminal device and the requested NSSAI carried by the terminal device, or the AMF network element obtains the allowed NSSAI from other network elements, which is not limited in the embodiment of this application. The allowedNSSAI sent by AMF to RAN includes the S-NSSAI that RAN can support, which is conducive to RAN completing the non-emergency registration process of the terminal device.

[0174] 602. The AMF receives a session establishment request message from a terminal device. The session establishment request message is used to request establishment of an emergency service session.

[0175] When a terminal device initiates an emergency session process, the terminal device sends a session establishment request message to the AMF. The session establishment request message is used to request the establishment of an emergency service session. For example, the terminal device initiates a PDU session establishment process, indicating that the type of the PDU session is an emergency PDU session. In addition, when initiating the PDU session establishment process, the terminal device does not carry S-NSSAI information.

[0176] 603. In response to the session establishment request message, the AMF selects the SMF according to the emergency service configuration information.

[0177] AMF receives the session establishment request message and learns that the session requested by the terminal device is an emergency session. AMF selects SMF based on the pre-configured emergency service configuration information. Among them, the emergency configuration data pre-configured by AMF includes one or more S-NSSAIs. When the emergency configuration data contains multiple S-NSSAIs, AMF can select any slice indicated by the S-NSSAI as the first slice. In addition, the tracking area where the terminal device is currently located supports the first slice. Optionally, each tracking area under the network where the terminal device is currently located supports the first slice. AMF selects SMF based on the identifier S-NSSAI of the first slice.

[0178] In Example 1, after AMF selects SMF, the interaction between AMF and SMF includes steps 604a and 605a.

[0179] 604a, AMF sends information about the slices that the terminal device is allowed to access to SMF. The information about the slices that the terminal device is allowed to access in step 604a is the information about any slice contained in the allowed NSSAI obtained by AMF in step 601. It should be noted that in order not to affect the subsequent RAN processing of emergency services, AMF can also send the information about the slices that the terminal device is allowed to access (that is, the information about the slices sent by AMF to SMF in step 604a) to RAN in subsequent steps, which is conducive to establishing a session between RAN and the terminal device. In this embodiment, the information about the slices that the terminal device is allowed to access sent by AMF to SMF is collectively referred to as S-NSSAI from allowed NSSAI.

[0180] To ensure that the RAN uses a RAN-supported slice to process emergency session services, the AMF selects a slice (S-NSSAI from allowed NSSAI) from the information about slices allowed for access by the terminal device. That is, since the terminal device is registering normally, the AMF can obtain the allowed NSSAI according to the normal registration process and select a slice from the allowed NSSAI to support the emergency session. It should be noted that the RAN is unaware of the session type, meaning it is unaware of whether the service being transmitted in the current session is an emergency service. After the AMF selects an SMF based on the emergency S-NSSAI and the S-NSSAI from allowed NSSAI that supports emergency services, it sends the S-NSSAI from allowed NSSAI to the SMF. This ensures that when the SMF establishes a session based on this slice, the RAN can also establish a session using this slice, allowing the UE to transmit emergency service data packets using this slice. The AMF's selection of the SMF based on the emergency S-NSSAI and the S-NSSAI from allowed NSSAI ensures that the SMF also supports the S-NSSAI from allowed NSSAI. For example, when the allowed NSSAI contains multiple S-NSSAIs, the AMF can select any S-NSSAI from the allowed NSSAI and send it to the SMF. In this implementation, the specific steps of the AMF sending the information of the slices allowed to be accessed by the terminal device (S-NSSAI from allowed NSSAI) to the SMF can be: the AMF sends a session establishment context request message to the corresponding SMF. The session establishment context request message carries the information of a slice (S-NSSAI from allowed NSSAI) contained in the allowed NSSAI obtained by the AMF in step 601.

[0181] 605a, SMF sends an N2 SM message to AMF, where the N2 SM message includes the S-NSSAI from allowed NSSAI.

[0182] The SMF sends an N2 SM message to the AMF. The N2 SM message includes the S-NSSAI from allowedNSSAI. This indicates that both the terminal device and the RAN support the S-NSSAI from allowedNSSAI, enabling the RAN to complete the emergency session establishment process for the terminal device.

[0183] It can be seen that in order to ensure that the RAN can process the emergency session service through the slices supported by the RAN, Example 1 adopts steps 604a and 605a. The AMF can select the SMF based on the emergency S-NSSAI and S-NSSAI fromallowed NSSAI that support emergency services. Subsequently, the SMF establishes a session based on the S-NSSAI from allowed NSSAI, which is conducive to establishing an emergency session between the RAN and the terminal device.

[0184] In Example 2, after AMF selects SMF, the interaction between AMF and SMF includes steps 604b and 605b.

[0185] 604b, AMF sends the information of the first slice to SMF.

[0186] The AMF selects a slice indicated by the S-NSSAI from the emergency configuration data as the first slice and sends information about the first slice to the SMF. In this implementation, the specific step of the AMF sending information about the first slice to the SMF may be: the AMF sends a session establishment context request message to the corresponding SMF. The session context request message carries information about the first slice.

[0187] 605b, the SMF sends an N2 SM message to the AMF, where the N2 SM message includes information about the first slice. The tracking area where the RAN is located supports the first slice.

[0188] Among them, SMF sends an N2 SM message to AMF, wherein the N2 SM message includes information about the first slice. That is, SMF instructs RAN to establish the emergency session using the resources corresponding to the first slice. AMF sends an N2 message to RAN, wherein the N2 message includes an N2 SM message and updated information about slices that the terminal device is allowed to access (new allowed NSSAI). Among them, the updated information about slices that the terminal device is allowed to access includes information about the first slice. It can be seen that although AMF determines the emergency S-NSSAI (i.e., the identifier of the first slice) based on the emergency service configuration information and uses the emergency S-NSSAI to select the SMF network element, after AMF negotiates the context with SMF, AMF can update the emergency S-NSSAI to the allowed NSSAI, so that the slice information sent by AMF to RAN is all information about slices supported by RAN. It should be noted that the above-mentioned new allowedNSSAI is only used to be sent to RAN and does not need to be provided to the terminal device. It should be noted that in Example 2, it is necessary to limit the tracking area where the terminal device is currently located to support the first slice. Then RAN can complete the emergency session process of the terminal device.

[0189] It can be seen that in order to ensure that the RAN can process the emergency session service through the slice supported by the RAN, steps 604b and 605b are adopted, the network sends the emergency S-NSSAI to the RAN, and the AMF updates the allowedNSSAI stored on the RAN to ensure that the allowed NSSAI stored on the RAN includes the emergency S-NSSAI, which is conducive to establishing an emergency session between the RAN and the terminal device.

[0190] Below Figure 6 The two implementation methods in the embodiment are described in detail respectively.

[0191] Figure 7 A flowchart of a slice selection method in a scenario where a terminal device initiates non-emergency registration and emergency session is provided in an embodiment of the present application. Figure 7 The overall process of the embodiment includes the non-emergency registration process and the emergency session process, which is implemented by the interaction between the terminal device, RAN, AMF and SMF.

[0192] In Example 1, the slice selection method specifically includes the following steps:

[0193] 701. The terminal device sends a registration request message to the RAN and AMF, where the registration type included in the registration request message is non-emergency registration.

[0194] Before receiving the registration request message, AMF pre-configures emergency configuration data, which includes S-NSSAI to support emergency services. For specific implementation methods, refer to Figure 4 The corresponding description in the embodiments will not be repeated here.

[0195] 702, AMF determines that the registration initiated by the terminal device is non-emergency, and determines the slice information (allowed NSSAI) allowed to be accessed by the terminal device based on the slice information supported in the TA where the RAN is located. For specific implementation methods, refer to Figure 6 The description corresponding to step 601 in the embodiment will not be repeated here.

[0196] 703. AMF sends an N2 message and a registration acceptance message to RAN. The N2 message and the registration acceptance message include information about the slices that the terminal device is allowed to access.

[0197] It can be understood that, in this embodiment, the allowed NSSAI sent by the AMF to the terminal device contains the same parameters as the allowed NSSAI sent to the RAN.

[0198] 704. RAN sends a registration acceptance message to the terminal device, and the registration acceptance message includes information about the slices that the terminal device is allowed to access.

[0199] 705, the terminal device sends a session establishment request message to the AMF, the session establishment request message indicates that the session type is an emergency session, and the session establishment request message does not include slice information (no S-NSSAI). For specific implementation methods, refer to Figure 6 The description corresponding to step 602 in the embodiment will not be repeated here.

[0200] 706. AMF selects SMF based on the slice information in the emergency configuration data.

[0201] 707a, AMF sends information about the slices that the terminal device is allowed to access to to SMF (in this embodiment, the information about the slices that the terminal device is allowed to access sent by AMF to SMF is collectively referred to as S-NSSAI from allowed NSSAI).

[0202] Specifically, the AMF determines the information of the slices allowed to be accessed by the terminal device based on the locally stored context. If the information of the slices allowed to be accessed by the terminal device contains multiple S-NSSAIs, the AMF can select one S-NSSAI from them and send it to the SMF. It can be understood that the AMF sends the S-NSSAI (i.e., S-NSSAI from allowed NSSAI) contained in the allowed NSSAI determined in step 702 to the SMF.

[0203] The specific implementation of step 707a in this example may include the following process: the AMF selects the SMF based on the allowed S-NSSAI and calls the SMF service operation Nsmf_PDUSession_CreateSMContext Request, carrying the allowed S-NSSAI, which is included in the allowed NSSAI.

[0204] 708a, SMF sends an N2 SM message and an N1 SM message to AMF, where the N2 SM message is a message sent to the RAN and contains information about the slices allowed to be accessed by the terminal device; the N1 SM message is a message sent to the terminal device and may not include information about the slices.

[0205] The specific implementation of step 708a in this example may include the following process: The SMF invokes the service-based operation Namf_Communication_N1N2MessageTransfer, carrying an N2 SM message and an N1 SM message. The N2 SM message is sent to the RAN and includes the allowed S-NSSAI. The N1 SM message is sent to the terminal device and does not include the S-NSSAI.

[0206] 709a, the AMF sends an N2 PDU Session Request message to the RAN. The N2 PDU Session Request message includes an N2 SM message and an N1 SM message. The N2 SM message includes information about the slices that the terminal device is allowed to access.

[0207] After the AMF sends the N2 SM message to the RAN, the RAN can obtain the S-NSSAI corresponding to the session.

[0208] 710. RAN sends an N1 SM message to the terminal device, where the N1 SM message also includes a session establishment accept message, and the session establishment accept message does not include slice information.

[0209] It can be seen that the slice selection method provided in this example is applicable to the scenarios of non-emergency registration and emergency session establishment. The AMF determines the allowed NSSAI based on the existing mechanism and sends the allowed NSSAI to the terminal device and RAN respectively. Then, when a normally registered terminal device initiates an emergency session, in order to enable the RAN to obtain a slice supported by the RAN to process the session, the AMF selects an S-NSSAI from the allowed NSSAI and sends it to the RAN to ensure that the RAN can establish the PDU session normally.

[0210] In Example 2, the slice selection method specifically includes the following steps:

[0211] 701-706 refer to the corresponding description in the previous embodiment and will not be repeated here.

[0212] 707b, AMF sends information about the first slice to SMF, where the first slice is used to support emergency services.

[0213] The information of the first slice is determined based on the emergency configuration data pre-stored by the AMF. Before the AMF receives the registration request message, the AMF pre-configures the emergency configuration data, which includes the S-NSSAI that supports emergency services. In addition, in this embodiment, it is assumed that all TAs where the RAN is located support the S-NSSAI that supports emergency services in the emergency configuration data. Since the emergency configuration data pre-stored by the AMF includes the S-NSSAI that supports emergency services, the AMF determines the S-NSSAI that supports emergency services in the emergency configuration data as the identifier of the first slice.

[0214] 708b, SMF sends an N2 SM message and an N1 SM message to the AMF, where the N2 SM message is a message sent to the RAN and contains information about the first slice; the N1 SM message is a message sent to the terminal device and does not include slice information.

[0215] The specific implementation of steps 707b and 708b can also be referred to Figure 4 The descriptions of steps 407 and 408 in the embodiment are not repeated here.

[0216] 709b: The AMF sends an N2 PDU Session Request message (N2 PDU Session Request) to the RAN. The N2 PDU Session Request message includes an N2 SM message and an N1 SM message. The N2 SM message includes updated information about slices allowed for access by the terminal device (new allowed NSSAI), including information about the first slice. The N2 SM message also includes information about the first slice.

[0217] For the sake of distinction, the new allowed NSSAI in step 709b is referred to as the first new allowed NSSAI.

[0218] Specifically, the AMF updates the information of the slices allowed to be accessed by the terminal device, including: the AMF adds the information of the first slice to the allowed NSSAI determined in step 702 to obtain a first new allowed NSSAI. After receiving the first new allowed NSSAI, the RAN will save the first new allowed NSSAI locally.

[0219] After the AMF sends the N2 SM message to the RAN, the RAN can obtain the updated information about the slices that the terminal device is allowed to access. In other words, for the RAN, the first slice is also a slice that the terminal device is allowed to access, and the RAN can use the first slice to support the emergency session service of the terminal device.

[0220] 710 refers to the corresponding description in the previous embodiment and will not be repeated here.

[0221] For any of the above examples, optionally, step 710 may further include the following steps:

[0222] 711. The terminal device sends a session release request message to the AMF. The session release request message is used to release the session requested to be established by the terminal device in step 705.

[0223] 712. AMF sends a session release request message to SMF.

[0224] 713. The SMF sends a session release response message to the AMF. The session release request message includes an N2 SM resource release request message (N2 SM resource release request).

[0225] 714. AMF sends an N2 SM resource release request message and updated information about the slices allowed to be accessed by the terminal device (new allowed NSSAI) to the RAN.

[0226] For the sake of distinction, the new allowed NSSAI in step 714 may be referred to as the second new allowed NSSAI.

[0227] Specifically, AMF updates the information of the slices that the terminal device is allowed to access, including: AMF deletes the information of the first slice from the new allowed NSSAI in step 709b, and obtains the second new allowed NSSAI.

[0228] After receiving the second new allowed NSSAI, the RAN will store the second new allowed NSSAI locally.

[0229] It can be seen that the slice selection method provided in this example 2 is applicable to the scenarios of non-emergency registration and emergency session establishment. The AMF determines the allowed NSSAI according to the existing mechanism, and sends the allowed NSSAI to the terminal device and RAN respectively. Then, when a normally registered terminal device initiates an emergency session, in order to enable the RAN to obtain a slice supported by the RAN to process the session, the AMF sends the emergency S-NSSAI (that is, the identifier of the first slice) to the RAN, and at the same time, the AMF updates the allowed NSSAI stored on the RAN to ensure that the allowed NSSAI stored on the RAN contains the emergency S-NSSAI. This enables the wireless access network device to establish an emergency session with the terminal device.

[0230] Combined with the above Figures 2 to 7 The slice selection method of the embodiment of the present application is described in detail. Figures 8 to 13 , describes in detail the slice selection device and related equipment of the embodiment of the present application. It should be understood that Figures 8 to 13 The slice selection device and related equipment shown can achieve Figures 2 to 7 To avoid repetition, one or more steps in the method flow shown are not described in detail here.

[0231] Figure 8 A schematic diagram of a slice selection device provided in an embodiment of the present application. Figure 8 The slice selection device shown is used to implement the above Figures 2 to 7 The method performed by the access and mobility management network element in the embodiment shown. The slice selection device includes a transceiver unit 801 and a processing unit 802. The transceiver unit 801 is used to receive a registration request message from a terminal device, and the registration type included in the registration request message is emergency registration. The processing unit 802 is used to determine the information of the first slice in response to the registration request message. The first slice is used to support emergency services, and the tracking area of ​​the wireless access network device currently accessed by the terminal device supports the first slice. The transceiver unit 801 is also used to send the information of the first slice to the wireless access network device.

[0232] In one implementation, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0233] In one implementation, the processing unit 802 is further configured to store information of the first slice in the context.

[0234] In one implementation, the transceiver unit 801 is further used to obtain from the wireless access network device that, in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

[0235] In one implementation, the transceiver unit 801 is configured to obtain from the radio access network device that, in a tracking area where the radio access network device is located, a first slice is used to support an emergency service, including:

[0236] During the process of establishing an interface connection between an access and mobility management network element and a radio access network device, indication information from the radio access network device is received. The indication information is used to indicate that a first slice in a tracking area where the radio access network device is located is used to support emergency services.

[0237] In one implementation, the transceiver unit 801 is further configured to receive a session establishment request message from a terminal device, the session establishment request message being used to request establishment of a session for emergency services. The processing unit 802 is further configured to, in response to the session establishment request message, select a session management network based on information about the first slice. The transceiver unit 801 is further configured to send information about the first slice to the session management network element.

[0238] In one implementation, the transceiver unit 801 is further configured to send a registration acceptance message to the terminal device. The registration acceptance message does not include information about the slice, or the registration acceptance message includes information about the slice that the terminal device is allowed to access, and the information about the slice that the terminal device is allowed to access is null.

[0239] In one implementation, the transceiver unit 801 is used to obtain information about slices that the terminal device is allowed to access during the registration process of the terminal device. The transceiver unit 801 is also used to receive a session establishment request message from the terminal device, and the session establishment request message is used to request the establishment of an emergency service session. The processing unit 802 is used to respond to the session establishment request message and select a session management network element according to the emergency service configuration information. The transceiver unit 801 is also used to send information about the slices that the terminal device is allowed to access to the session management network element; or, to send information about the first slice to the wireless access network device. The first slice is used to support emergency services, and the tracking area where the wireless access network device is located supports the first slice.

[0240] In one implementation, the registration type of the terminal device is non-emergency registration.

[0241] In one implementation, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0242] In one implementation, Figure 8 The relevant functions implemented by each unit in the system can be implemented by a transceiver, a processor and a memory. Figure 9 A schematic diagram of an access and mobility management network element provided in an embodiment of the present application. The access and mobility management network element may be a device (e.g., a chip) capable of executing the slice selection method provided in an embodiment of the present application. The access and mobility management network element may include a transceiver 901, at least one processor 902, and a memory 903. The transceiver 901, the processor 902, and the memory 903 may be interconnected via one or more communication buses, or may be connected in other ways.

[0243] The transceiver 901 can be used to send data or receive data. It is understood that the transceiver 901 is a general term that can include a receiver and a transmitter.

[0244] The processor 902 may be configured to process data from the access and mobility management network element. The processor 902 may include one or more processors, such as one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof. If the processor 902 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0245] The memory 903 is used to store program code, etc. The memory 903 may include volatile memory, such as random access memory (RAM); non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); or a combination of the aforementioned types of memory.

[0246] The processor 902 and the memory 903 may be coupled via an interface or may be integrated together, which is not limited in this embodiment.

[0247] The transceiver 901 and the processor 902 may be used to execute the slice selection method provided in the embodiment of the present application, and the specific implementation is as follows:

[0248] The transceiver 901 is configured to receive a registration request message from a terminal device, where the registration type included in the registration request message is emergency registration;

[0249] Processor 902 is used to determine the information of the first slice in response to the registration request message; the first slice is used to support emergency services, and the tracking area where the wireless access network device currently accessed by the terminal device supports the first slice.

[0250] In one implementation, the transceiver 901 and the processor 902 may be used to execute the slice selection method provided in the embodiment of the present application. The specific implementation is as follows:

[0251] The transceiver 901 is used to obtain information about the slices that the terminal device is allowed to access during the registration process of the terminal device;

[0252] The transceiver 901 is further configured to receive a session establishment request message from a terminal device, the session establishment request message being used to request establishment of an emergency service session;

[0253] Processor 902 is configured to select a session management network element according to the emergency service configuration information in response to the session establishment request message;

[0254] The transceiver 901 is also used to send information about the slice that the terminal device is allowed to access to the session management network element; or, to send information about the first slice to the wireless access network device, where the first slice is used to support emergency services, and the tracking area where the wireless access network device is located supports the first slice.

[0255] Among them, such as Figure 9 For other possible implementations of the access and mobility management network element shown above, please refer to the Figure 8 The descriptions of the various implementations of the slice selection device shown are omitted here.

[0256] It is understandable that the above method embodiments can all be referred to as Figure 8 and Figure 9 The beneficial effects that can be achieved in the slice selection device and access and mobility management network element are described in the corresponding description in the aforementioned method embodiment and will not be repeated here.

[0257] Figure 10 A schematic diagram of another slice selection device provided in an embodiment of the present application. Figure 10 The slice selection apparatus shown is used to implement the method performed by the radio access network device in the above-described embodiment. The slice selection apparatus includes a transceiver unit 1001. Transceiver unit 1001 is configured to receive a registration request message from a terminal device and send the registration request message to an access and mobility management network element, where the registration type included in the registration request message is emergency registration. Transceiver unit 1001 is further configured to receive information about a first slice from the access and mobility management network element. The first slice is configured to support emergency services, and the tracking area in which the radio access network device is located supports the first slice.

[0258] In one implementation, the transceiver unit 1001 is further configured to send indication information to the access and mobility management network element during the process of establishing an interface connection between the access and mobility management network element and the radio access network device. The indication information is configured to indicate that, in the tracking area where the radio access network device is located, the first slice is used to support emergency services.

[0259] In one implementation, Figure 10 The relevant functions implemented by the units in can be implemented by transceivers, processors and memories. Figure 11A schematic diagram of a radio access network device provided in an embodiment of the present application. The radio access network device may be a device (e.g., a chip) capable of executing the slice selection method provided in an embodiment of the present application. The radio access network device may include a transceiver 1101, at least one processor 1102, and a memory 1103. The transceiver 1101, the processor 1102, and the memory 1103 may be interconnected via one or more communication buses, or may be connected via other means.

[0260] The transceiver 1101 is controlled by the processor 1102 and can be used to send or receive data. It is understood that the transceiver 1101 is a general term and can include a receiver and a transmitter.

[0261] The processor 1102 may include one or more processors, for example, the processor 1102 may be one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof. When the processor 1102 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0262] The memory 1103 is used to store program code, etc. The memory 1103 may include a volatile memory, such as a random access memory (RAM); a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk (HDD), or a solid-state drive (SSD); or a combination of the aforementioned types of memory.

[0263] The processor 1102 and the memory 1103 may be coupled via an interface or integrated together, which is not limited in this embodiment.

[0264] The processor 1102 may call the program code stored in the memory 1103 to perform the following operations:

[0265] Receive a registration request message from the terminal device through the transceiver 1101, and send the registration request message to the access and mobility management network element, where the registration type included in the registration request message is emergency registration;

[0266] Information about the first slice is received from the access and mobility management network element through transceiver 1101. The first slice is used to support emergency services, and the tracking area where the wireless access network device is located supports the first slice.

[0267] Among them, such as Figure 11 For other possible implementations of the wireless access network device shown above, please refer to the Figure 10 The descriptions of the various implementations of the slice selection device shown are omitted here.

[0268] It is understandable that the above method embodiments can all be referred to as Figure 10 and Figure 11 In the slice selection device and wireless access network device, the beneficial effects that can be achieved refer to the corresponding description in the aforementioned method embodiment and will not be repeated here.

[0269] Figure 12 A schematic diagram of another slice selection device provided in an embodiment of the present application. Figure 12 The slice selection device shown is used to implement the method executed by the session management network element in the above embodiment. The slice selection device includes a transceiver unit 1201. The transceiver unit 1201 is used to receive a session establishment request message from a terminal device, and the session establishment request message is used to request the establishment of an emergency service session. The transceiver unit 1201 is also used to receive information about the slice that the terminal device is allowed to access or information about the first slice from the access and mobility management network element. The first slice is used to support emergency services, and the tracking area where the radio access network device currently accessed by the terminal device is located supports the first slice. The transceiver unit 1201 is also used to send information about the slice that the terminal device is allowed to access or information about the first slice to the access and mobility management network element.

[0270] In one implementation, each tracking area of ​​the network where the terminal device is currently located supports the first slice.

[0271] In one implementation, the registration type of the terminal device is non-emergency registration.

[0272] In one implementation, the information of the slices that the terminal device is allowed to access does not include information of the first slice.

[0273] In one implementation, Figure 12 The relevant functions implemented by the units in can be implemented by transceivers, processors and memories. Figure 13 This is a schematic diagram of a session management network element provided in an embodiment of the present application. The session management network element may be a device (e.g., a chip) capable of executing the slice selection method provided in an embodiment of the present application. The session management network element may include a transceiver 1301, at least one processor 1302, and a memory 1303. The transceiver 1301, the processor 1302, and the memory 1303 may be interconnected via one or more communication buses, or may be connected via other means.

[0274] The transceiver 1301 is controlled by the processor 1302 and can be used to send or receive data. It is understood that the transceiver 1301 is a general term that can include a receiver and a transmitter.

[0275] The processor 1302 may include one or more processors, for example, the processor 1302 may be one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof. When the processor 1302 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0276] The memory 1303 is used to store program code, etc. The memory 1303 may include volatile memory, such as random access memory (RAM); non-volatile memory, such as read-only memory (ROM), flash memory, hard disk (HDD), or solid-state drive (SSD); or a combination of the aforementioned types of memory.

[0277] The processor 1302 and the memory 1303 may be coupled via an interface or integrated together, which is not limited in this embodiment.

[0278] The processor 1302 may call the program code stored in the memory 1303 to perform the following operations:

[0279] Receive a session establishment request message from a terminal device through the transceiver 1301, where the session establishment request message is used to request establishment of an emergency service session;

[0280] Receiving, through the transceiver 1301, information about a slice allowed to be accessed by the terminal device or information about a first slice from the access and mobility management network element, where the first slice is used to support emergency services, and the tracking area of ​​the radio access network device currently accessed by the terminal device supports the first slice;

[0281] The information of the slice to which the terminal device is allowed to access or the information of the first slice is sent to the access and mobility management network element through the transceiver 1301.

[0282] Among them, such as Figure 13 For other possible implementations of the session management network element shown, see the above Figure 12 The descriptions of the various implementations of the slice selection device shown are omitted here.

[0283] It is understandable that the above method embodiments can all be referred to as Figure 12 and Figure 13 For the beneficial effects that can be achieved in the slice selection device and session management network element, please refer to the corresponding description in the aforementioned method embodiment and will not be repeated here.

[0284] An embodiment of the present application provides a communication system, which includes the access and mobility management network element, wireless access network equipment and session management network element described in the above embodiments.

[0285] An embodiment of the present application provides a computer-readable storage medium, which stores a program or instruction. When the program or instruction is run on a computer, the computer executes the slice selection method in the embodiment of the present application.

[0286] An embodiment of the present application provides a chip or chip system, which includes at least one processor and an interface, wherein the interface and the at least one processor are interconnected by lines, and the at least one processor is used to run a computer program or instruction to perform the slice selection method in the embodiment of the present application.

[0287] The interface in the chip may be an input or output interface, a pin or a circuit, etc.

[0288] The chip system in the above aspects may be a system on chip (SOC) or a baseband chip, etc., wherein the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem and an interface module, etc.

[0289] In one implementation, the chip or chip system described above in this application further includes at least one memory, in which instructions are stored. The memory may be a storage unit within the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).

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

[0291] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0292] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A slice selection method, characterized in that: include: The access and mobility management network element receives a registration request message from a terminal device, where the registration type included in the registration request message is emergency registration; In response to the registration request message, the access and mobility management network element determines information of a first slice, where the first slice is used to support emergency services, and a tracking area where the radio access network device currently accessed by the terminal device supports the first slice; The access and mobility management network element sends information about the first slice to the wireless access network device.

2. The method according to claim 1, characterized in that Each tracking area of ​​the network where the terminal device is currently located supports the first slice.

3. The method according to claim 2, characterized in that The method further comprises: The access and mobility management network element stores information of the first slice in a context.

4. The method according to claim 1, wherein The method further comprises: The access and mobility management network element learns from the wireless access network device that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

5. The method according to claim 4, characterized in that The access and mobility management network element learns from the radio access network device that, in the tracking area where the radio access network device is located, the first slice is used to support emergency services, including: During the process of establishing an interface connection between the access and mobility management network element and the wireless access network device, the access and mobility management network element receives indication information from the wireless access network device, where the indication information is used to indicate that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

6. The method according to claim 4 or 5, characterized in that The method further comprises: The access and mobility management network element receives a session establishment request message from the terminal device, where the session establishment request message is used to request establishment of an emergency service session; In response to the session establishment request message, the access and mobility management network element selects a session management network element based on the information of the first slice and sends the information of the first slice to the session management network element.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The access and mobility management network element sends a registration acceptance message to the terminal device, and the registration acceptance message does not include slice information, or the registration acceptance message includes information about the slices that the terminal device is allowed to access, and the information about the slices that the terminal device is allowed to access is a null value.

8. A slice selection method, characterized in that: include: The wireless access network device receives a registration request message from the terminal device and sends the registration request message to the access and mobility management network element, where the registration type included in the registration request message is emergency registration; The wireless access network device receives information about a first slice from an access and mobility management network element, where the first slice is used to support emergency services, and the tracking area where the wireless access network device is located supports the first slice.

9. The method according to claim 8, characterized in that The method further comprises: During the process of establishing the interface connection between the access and mobility management network element and the wireless access network device, the wireless access network device sends indication information to the access and mobility management network element, where the indication information is used to indicate that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

10. A slice selection device, characterized in that: include: a transceiver unit, configured to receive a registration request message from a terminal device, wherein the registration type included in the registration request message is emergency registration; A processing unit, configured to determine, in response to the registration request message, information of a first slice, where the first slice is used to support emergency services, and a tracking area where a radio access network device currently accessed by the terminal device supports the first slice; The transceiver unit is also used to send information of the first slice to the wireless access network device.

11. The device according to claim 10, characterized in that Each tracking area of ​​the network where the terminal device is currently located supports the first slice.

12. The device according to claim 11, characterized in that The processing unit is further configured to: Information of the first slice is stored in the context.

13. The device according to claim 10, characterized in that The transceiver unit is further configured to: It is learned from the wireless access network device that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

14. The device according to claim 13, characterized in that The transceiver unit is configured to learn from the radio access network device that the first slice is used to support emergency services in a tracking area where the radio access network device is located, including: During the process of establishing an interface connection between the access and mobility management network element and the wireless access network device, indication information is received from the wireless access network device, where the indication information is used to indicate that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

15. The device according to claim 13 or 14, characterized in that The transceiver unit is also used to receive a session establishment request message from the terminal device, and the session establishment request message is used to request the establishment of an emergency service session; the processing unit is also used to respond to the session establishment request message and select a session management network element based on the information of the first slice; the transceiver unit is also used to send the information of the first slice to the session management network element.

16. The device according to any one of claims 10 to 14, characterized in that The transceiver unit is also used to send a registration acceptance message to the terminal device, and the registration acceptance message does not include slice information, or the registration acceptance message includes information about the slices allowed to be accessed by the terminal device, and the information about the slices allowed to be accessed by the terminal device is a null value.

17. A slice selection device, characterized in that: include: a transceiver unit, configured to receive a registration request message from a terminal device and send the registration request message to an access and mobility management network element, wherein the registration type included in the registration request message is emergency registration; The transceiver unit is also used to receive information about a first slice from an access and mobility management network element, where the first slice is used to support emergency services, and the tracking area where the wireless access network device is located supports the first slice.

18. The device according to claim 17, characterized in that The transceiver unit is also used to send indication information to the access and mobility management network element during the process of establishing an interface connection between the access and mobility management network element and the wireless access network device, wherein the indication information is used to indicate that in the tracking area where the wireless access network device is located, the first slice is used to support emergency services.

19. A communication system, characterized in that: Comprising a slice selection device as claimed in any one of claims 10 to 18.

20. A computer-readable storage medium, characterized in that The method comprises a program or an instruction, and when the program or the instruction is run on a computer, the method according to any one of claims 1 to 9 is executed.

Images