CN113411815A

CN113411815A - Method and device for accessing network slice

Info

Publication number: CN113411815A
Application number: CN202010181190.7A
Authority: CN
Inventors: 朱方园; 孙海洋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-03-16
Filing date: 2020-03-16
Publication date: 2021-09-17
Anticipated expiration: 2040-03-16
Also published as: CN113411815B; WO2021185176A1

Abstract

The application relates to the technical field of wireless communication, and provides a method for accessing network slices, which comprises the following steps: the first AMF network element receives a requested network slice type from a terminal device through a first RAN device, wherein the first RAN device does not support the requested network slice type, and sends information of a second RAN device to the terminal device, wherein the information of the second RAN device is used for identifying the second RAN device, and the second RAN device supports the requested network slice type. Through the scheme provided by the embodiment, the terminal device can obtain the information of the second RAN device from the first AMF network element, and because the second RAN device supports the requested network slice type, the terminal device can access the requested network slice through the second RAN device, thereby improving user experience.

Description

Method and device for accessing network slice

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for accessing a network slice.

Background

The 5th-Generation (5G) communication era will have billions of internet-of-things devices accessing the network, and the demands of different types of application scenarios on the network are different. The network slicing technology provides mutually isolated network environments for different application scenes in a mode of simulating an independent logic network on the same network infrastructure, so that different application scenes can customize network functions and characteristics according to respective requirements, and requirements of different services are met. Since terminal devices have different requirements for rate, capacity, coverage, delay, reliability, security and bandwidth, the network slices that need to be accessed are different.

The selection process of a network slice is triggered when a User Equipment (UE) initially attaches to the network. When the UE needs to access to a certain network slice, the UE sends Requested Network Slice Selection Assistance Information (NSSAI), also called Requested NSSAI, to the core network, where the network slice selection assistance information is used for the core network to select a network slice for the UE.

In the prior art, if a location of a UE can access one or more Radio Access Network (RAN) devices, but the UE does not perceive a network slice type supported by the RAN devices, the UE accesses the RAN devices in a blind selection manner and sends a registration request to a core network through the RAN devices, where a registration request message carries a Requested NSSAI. As the RAN device that the UE blindly selects for access does not necessarily support the Requested NSSAI, the network slice that the core network finally allows the UE to access cannot meet the requirement of the UE, that is, the network slice that the core network allows the UE to access is different from the Requested NSSAI, or the UE registration fails. Therefore, the network access efficiency of the UE is low, and the user experience is reduced.

For example, in the scenario shown in fig. 1, the UE is currently located in the coverage of RAN1 and the coverage of RAN 2. Among them, the RAN1 does not support the UE requested network slice type, and the RAN2 supports the UE requested network slice type. Since the UE does not perceive the network slice types supported by RAN1 and RAN2, respectively, it is assumed that UE1 accesses RAN1 by blind selection and sends a registration request to the core network through RAN1, where the registration request message carries the requested network slice type. The core network determines that the RAN1 does not support the network slice type requested by the UE, and the network slice that the core network ultimately allows the UE to access cannot meet the requirements of the UE or cause the UE to fail to register.

Disclosure of Invention

The embodiment of the invention provides a method and a device for accessing a network slice.

In one aspect, an embodiment of the present application provides a method for accessing a network slice, where the method includes: a first AMF network element (e.g., the first AMF network element in fig. 4, 5) receives a requested network slice type from a terminal device (e.g., the UE in fig. 4, 5) through a first RAN device (e.g., the first RAN network element in fig. 4, 5), wherein the first RAN device does not support the requested network slice type. The first AMF network element sends information of a second RAN device (e.g., the second RAN network element in fig. 4 and 5) to the terminal device, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

According to the method, the terminal device can obtain the information of the second RAN device from the first AMF network element, and the second RAN device supports the requested network slice type, so that the terminal device can access the requested network slice through the second RAN device, and user experience is improved.

In one possible design, the first RAN device is located at a first TA that does not support the requested network slice type, and the second RAN device is located at a second TA that supports the requested network slice type.

In one possible design, a first RAN device is located at a first TA, a second RAN device is located at a second TA, and a location where a terminal device is located at the first TA and is located at the second TA; or the location of the terminal device is located in the coverage area of the first RAN device and in the coverage area of the second RAN device.

In one possible design, the first AMF network element determines the second RAN equipment. For example, the first AMF network element may determine the second RAN equipment in any one or more of the three ways of fig. 4.

In one possible design, the first AMF network element obtains information of a third RAN device, and then determines a RAN device supporting the requested network slice type from the third RAN device as the second RAN device. Thus, the first AMF network element may determine, from the third RAN device, the second RAN device supporting the requested network slice type by acquiring information of the third RAN device.

In one possible design, the first AMF network element obtains a location of the terminal device, and determines the second RAN device according to the location of the terminal device. Therefore, the first AMF network element can determine the second RAN equipment supporting the requested network slice type by acquiring the position of the terminal equipment.

In one possible design, the first AMF network element sends, to the first network element, information of a fourth RAN device or a location where the terminal device is located, where the information of the fourth RAN device or the location where the terminal device is located is used for determining the second RAN device. The first AMF network element receives information of the second RAN device from the first network element. Therefore, the terminal device can obtain the information of the second RAN device from the first AMF network element, and since the second RAN device supports the requested network slice type, the terminal device can access the requested network slice through the second RAN device, thereby improving user experience.

In one possible design, the first network element is a second AMF network element or an NSSF network element. In this way,

in one possible design, the first AMF network element sends indication information to the terminal device, where the indication information is used to indicate that the second RAN device supports the requested network slice type. Therefore, after receiving the information of the second RAN device, the terminal device can obtain the network slice type that the second RAN device supports the request according to the indication information.

In one possible design, the first AMF network element receives first priority information from the terminal device, where the first priority information is used to indicate that the priority of the requested network slice type is high, and the first AMF network element sends a registration reject message to the terminal device according to the first priority information. Since the first priority information indicates that the priority of the requested network slice type is high, it indicates that the UE preferentially accesses the network slice corresponding to the requested network slice type. Because the first RAN device accessed by the UE cannot support the requested network slice type, the first AMF determines to reject the registration procedure.

In one possible design, the first AMF network element receives second priority information from the terminal device, the second priority information indicating that the priority of the requested network slice type is low; and the AMF network element sends a registration acceptance message to the terminal equipment according to the second priority information. Since the second priority information indicates that the priority of the requested network slice type is low, when the first RAN device accessed by the UE cannot support the requested network slice type, the first AMF determines the allowed NSSAI for the UE as a default S-NSSAI (default S-NSSAI), and determines the rejected NSSAI (rejected NSSAI). Wherein the rejected NSSAI is of the same network slice type as the requested NSSAI.

In another aspect, the present application also discloses a method for accessing a network slice, which includes: a terminal device (e.g., a UE in fig. 4 and 5) sends a requested network slice type to a first AMF network element (e.g., the first AMF network element in fig. 4 and 5) through a first RAN device (e.g., the first RAN device in fig. 4 and 5), the first RAN device does not support the requested network slice type, and the terminal device receives information of a second RAN device (e.g., the second RAN device in fig. 4 and 5) from the first AMF network element, the information of the second RAN device is used for identifying the second RAN device, and the second RAN device supports the requested network slice type.

In one possible design, the first RAN device is located at a first TA, and the first TA does not support the requested network slice type; the second RAN device is located at a second TA that supports the requested network slice type.

In one possible design, the terminal device sends the requested network slice type to the second RAN device. Thus, the terminal device may access the requested network slice through the second RAN device, thereby improving user experience.

In one possible design, the terminal device sends information of a third RAN device to the first AMF network element or the first RAN device, and a RAN device supporting the requested network slice type in the third RAN device is the second RAN device. Thus, the first AMF network element may obtain information of the third RAN device, and may determine the second RAN device supporting the requested network slice type from the third RAN device.

In one possible design, the terminal device receives indication information from the first AMF network element, the indication information indicating that the second RAN device supports the requested network slice type. Therefore, after receiving the information of the second RAN device, the terminal device can obtain the network slice type that the second RAN device supports the request according to the indication information.

In one possible design, the terminal device sends first priority information to the first AMF network element, where the first priority information is used to indicate that the priority of the requested network slice type is high, and the terminal device receives a registration reject message from the AMF network element.

In one possible design, the terminal device sends second priority information to the first AMF network element, where the second priority information is used to indicate that the priority of the requested network slice type is low, and the terminal device receives a registration accept message from the AMF network element.

In one possible design, when there are a plurality of second RAN devices, the method further includes: the terminal device selects a second RAN device from the plurality of second RAN devices based on signal strength and/or traffic demand. Thus, when the number of the second RAN devices is plural, the terminal device may select one second RAN device from the plural second RAN devices.

In another aspect, the present application also discloses a method for accessing a network slice, which includes: the first network element (e.g., the first network element in fig. 6) receives the requested network slice type and the first information from the first AMF network element (e.g., the first AMF network element in fig. 6), wherein the requested network slice type is the network slice type requested to be accessed by the terminal device (e.g., the UE in fig. 6). The first network element determines a second RAN device (e.g., the second RAN device in fig. 6) according to the network slice type and the first information, and sends information of the second RAN device to the first AMF network element, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

According to the method, the terminal device can obtain the information of the second RAN device from the first network element, and the second RAN device supports the requested network slice type, so that the terminal device can access the requested network slice through the second RAN device, and user experience is improved.

In one possible design, the first information is information of a third RAN device, and the first network element determines that a RAN device supporting the requested network slice type in the third RAN device is the second RAN device. Thus, the first network element may determine, from the third RAN apparatus, the second RAN apparatus supporting the requested network slice type by acquiring information of the third RAN apparatus.

In one possible design, the first information is a location where the terminal device is located.

In one possible design, the first network element includes a second AMF network element or an NSSF network element.

In still another aspect, the present embodiment provides an apparatus for accessing a network slice, where the apparatus has a function of implementing the behavior of the first AMF network element (e.g., the first AMF network element in fig. 4 and 5) in the foregoing method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In one possible design, the structure of the apparatus includes a processor and a transceiver, and the processor is configured to process the apparatus to perform the corresponding functions of the method. The transceiver is used for realizing the communication between the device and the terminal equipment/the first RAN equipment/the first network element. The apparatus may also include a memory, coupled to the processor, that retains program instructions and data necessary for the apparatus.

In still another aspect, the present application provides an apparatus for accessing network slice, where the apparatus has a function of implementing a behavior of a terminal device (e.g., a UE in fig. 4 and 5) in the foregoing method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In one possible design, the structure of the apparatus includes a processor and a transceiver, and the processor is configured to process the apparatus to perform the corresponding functions of the method. The transceiver is used for realizing the communication between the device and the first RAN equipment/the first AMF network element/the second RAN equipment. The apparatus may also include a memory, coupled to the processor, that retains program instructions and data necessary for the apparatus.

In still another aspect, the present application provides an apparatus for accessing network slice, where the apparatus has a function of implementing a behavior of a first network element (e.g., the first network element in fig. 6) in the foregoing method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In one possible design, the structure of the apparatus includes a processor and a transceiver, and the processor is configured to process the apparatus to perform the corresponding functions of the method. The transceiver is used for realizing the communication between the device and the first AMF network element/terminal equipment. The apparatus may also include a memory, coupled to the processor, that retains program instructions and data necessary for the apparatus.

In yet another aspect, the present application provides a computer-readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a computer program product containing instructions which, when executed on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a chip system, which includes a processor, for enabling the apparatus or the terminal device to implement the functions referred to in the above aspects, for example, to generate or process the information referred to in the above methods. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the data transmission device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments or background of the present invention will be described below.

Fig. 1 is a schematic view of a scenario provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a 5G communication system provided in an embodiment of the present application;

fig. 3 is a flow chart of UE blindly selecting access network slices;

fig. 4 is a method for accessing a network slice according to an embodiment of the present disclosure;

fig. 5 is a flowchart of a method for accessing a network slice according to an embodiment of the present application;

fig. 6 is a flowchart of yet another method for accessing a network slice according to an embodiment of the present application;

fig. 7A and 7B are schematic structural diagrams of an apparatus for accessing a network slice according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. In the description of the present application, "/" indicates an OR meaning, for example, A/B may indicate A or B; in the present application, "and/or" is only an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the present application, "a plurality" means two or more.

Fig. 2 shows a schematic diagram of a 5G communication system provided in an embodiment of the present application. In the 5G mobile network architecture, the control plane function and the forwarding plane function of the mobile gateway are decoupled, and the separated control plane function is merged with a Mobility Management Entity (MME) of a 3GPP conventional control network element into a unified control plane (control plane). A User Plane Function (UPF) network element can implement a Serving Gateway (SGW) and a packet data network gateway (PGW) user plane functions (SGW-U and PGW-U). Further, the unified control plane network element may be decomposed into an access and mobility management function (AMF) network element and a Session Management Function (SMF) network element.

As shown in fig. 2, the communication system includes at least a UE 201, a RAN device 202, and an AMF network element 205. Optionally, the communication system further includes a UPF network element 203, an SMF network element 206, a Network Slice Selection Function (NSSF) network element 207, and a Data Network (DN) 204.

The UE 201 involved in the present system is not limited to the 5G network, and includes: the system comprises a mobile phone, an internet of things device, an intelligent household device, an industrial control device, a vehicle device and the like. The UE may also be referred to as a Mobile Station (Mobile Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a Terminal device (User Terminal), and a User Agent (User Agent), which are not limited herein. The terminal device may be an automobile in Vehicle-to-Vehicle (V2V) communication, a device in device communication, or the like.

The RAN apparatus 202 involved in the present system is a device for providing a UE 201 with a wireless communication function, and may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. In systems using different radio access technologies, names of devices having a base station function may be different, for example, in an LTE system, the device is called an evolved node B (eNB or eNodeB), and in a third generation (2G) system, the device is called a node B (node B). In a new generation system, called gnb (gnnodeb).

The AMF network element 205 involved in the present system may be responsible for registration of terminal equipment, mobility management, tracking area update procedures, and the like. The AMF network element may also be referred to as an AMF device or an AMF entity.

The SMF network element 206 involved in the present system may be responsible for session management of the terminal device. For example, session management includes selection of a user plane device, reselection of the user plane device, network protocol (IP) address allocation, quality of service (QoS) control, and establishment, modification, or release of a session. An SMF network element may also be referred to as an SMF device or an SMF entity.

The UPF network element 203 involved in the system can implement functions of forwarding, counting, detecting and the like of user messages. A UPF network element may also be referred to as a UPF device or UPF entity.

The DN 204 involved in the present system may be an operator provided service, an internet access service, or a third party provided service.

The NSSF network element 207 involved in the present system may select a network slice for the user equipment. An NSSF network element may also be referred to as an NSSF device or an NSSF entity.

The network elements may be network elements implemented on dedicated hardware, or may be software instances running on dedicated hardware, or may be instances of virtualization functions on a virtualization platform, for example, the virtualization platform may be a cloud platform.

In addition, the embodiment of the application can also be applied to other communication technologies facing the future. The network architecture and the service scenario described in this application are for more clearly illustrating the technical solution of this application, and do not constitute a limitation to the technical solution provided in this application, and it can be known by those skilled in the art that the technical solution provided in this application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of new service scenarios.

Fig. 3 is a flowchart of UE blindly selecting access network slices in the scenario shown in fig. 1. For example, RAN1 in fig. 3 is RAN1 in fig. 1, RAN2 in fig. 3 is RAN2 in fig. 1, the AMF network element in fig. 3 is an AMF network element in the core network in fig. 1, and the UE is located in the coverage of RAN1 and the coverage of RAN 2. As shown in fig. 3, the method may include:

s301, RAN1 sends Single Network Slice Selection Assistance Information (S-NSSAI) #1 to the AMF Network element.

For example, the RAN1 sends, to the AMF network element, a network slice list supported by a Tracking Area (TA) 1 in which the RAN1 is located through an NG setup request (NG setup request) message, where the network slice list includes S-NSSAI # 1. Wherein the NG interface is an interface between the RAN1 and the AMF network element.

S302, storing S-NSSAI #1 by the AMF network element.

Through steps S301 and S302, the AMF network element may know the network slice types supported by the TA1 where the RAN1 is located.

Optionally, after step S301, the AMF network element sends a network slice list supported by the AMF network element to the RAN1 through an NG setup response (NG setup response) message. Thus, the RAN1 may know the network slice types supported by the AMF.

S303, RAN2 send S-NSSAI #2 to the AMF network element.

For example, the RAN2 sends, to the AMF network element, a network slice list supported by the tracking area TA2 in which the RAN2 is located, which includes S-NSSAI #2, through an NG setup request (NG setup request) message. Wherein the NG interface is an interface between the RAN2 and the AMF network element.

And S304, storing S-NSSAI #2 by the AMF network element.

Through step S303 and step S304, the AMF network element may know the network slice types supported by the TA2 where the RAN2 is located.

Optionally, after step S303, the AMF network element sends the network slice list supported by the AMF network element to the RAN2 through an NG setup response (NG setup response) message. Thus, the RAN2 may know the network slice types supported by the AMF.

S305, the UE sends the requested NSSAI to the RAN 1.

Wherein the requested NSSAI is S-NSSAI # 2.

For example, the UE selects RAN1 for network entry by blind selection and sends the requested NSSAI to RAN1 via a registration request message.

S306, the RAN1 sends the requested NSSAI to the AMF network element.

S307, the AMF network element determines allowed nssai (allowed nssai) and rejected nssai (rejected nssai).

Since RAN1 supports S-NSSAI #1 and the requested NSSAI is S-NSSAI #2, AMF determines that TA1 in which RAN1 is located does not support the requested NSSAI. However, the TA1 in which the RAN1 is located supports default S-NSSAI (default S-NSSAI), and in order to ensure that the UE can be successfully registered, the AMF determines the allowed NSSAI for the UE to be the default S-NSSAI and a Registration Area (Registration Area). And, the AMF network element determines that the rejected NSSAI is S-NSSAI # 2.

S308, the AMF network element determines a Radio Access Technology/Frequency Selection Priority (RFSP).

For example, RFSP is used for RAN1 to prioritize the selection of air interface spectrum for UEs.

S309, the AMF network element sends a registration accept message to the RAN 1.

For example, the AMF network element sends a registration accept message to the RAN1 via an N2 message. The N2 message also includes the allowed NSSAI, the rejected NSSAI and the registration area in RFSP and S307 in step S308.

S310, RAN1 sends a registration accept message to the UE.

According to the method shown in fig. 3, the AMF determines the allowed NSSAI for the UE to be the default S-NSSAI in order to satisfy the UE registration. Since the default S-NSSAI is not the network slice that the UE requests access to, the UE requirements (e.g., Qos, bandwidth, etc. requirements) cannot be met. In addition, after the UE receives the rejected NSSAI, in the current registration area, the UE cannot attempt to access the network slice corresponding to the rejected NSSAI again, and only after the UE moves out of the registration area, the UE can attempt to access the network slice corresponding to the rejected NSSAI. So even if the S-NSSAI requested by the UE is S-NSSAI #2 and the RAN2 can support S-NSSAI #2 in the current location where the UE is located, since the AMF determines that the rejected S-NSSAI is S-NSSAI #2 in step S307, the UE cannot attempt to access S-NSSAI #2 again in the current location, and it is necessary to wait for the UE to move out of the registration area before attempting to access S-NSSAI # 2. Therefore, the method shown in fig. 3 causes the network access efficiency of the UE to be low, and the user experience to be degraded.

The following takes the 5G communication system shown in fig. 2 as an example, and the technical solution of the present application is described in detail through some embodiments. The following several embodiments may be combined with each other and may not be described in detail in some embodiments for the same or similar concepts or processes.

Fig. 4 is a method for accessing a network slice according to an embodiment of the present application, where the method is applicable to a scenario that: the first RAN equipment is located at a first TA, the second RAN equipment is located at a second TA, and the position of the UE is located at the first TA and the second TA; alternatively, the UE is located in a coverage area of the first RAN device and in a coverage area of the second RAN device.

The method shown in fig. 4 may be used in the 5G communication system in fig. 2. By the method, the terminal device can acquire the second RAN device supporting the requested network slice type, and the second RAN device can access the requested network slice. As shown in fig. 4, the method may include:

s401, the first AMF network element receives the requested network slice type from the terminal device through the first RAN device, where the first RAN device does not support the requested network slice type.

For example, the first AMF network element is located in the core network of fig. 1, the first RAN device is RAN1 in fig. 1, and the terminal device is the UE in fig. 1.

For example, the network slice type requested by the UE is S-NSSAI-2, the network slice type supported by the first RAN device is S-NSSAI-1, and the first RAN device does not support S-NSSAI-2.

In the embodiment of the present application, the first RAN device does not support the requested network slice type, which may include but is not limited to the following cases:

1) the TA in which the first RAN device is located does not support the requested network slice type. It may also be understood that all RAN devices within the TA in which the first RAN device is located, including one or more RAN devices, do not support the requested network slice type.

For example, the first RAN device is located at a first TA that does not support the requested network slice type.

For example, the Tracking Area Identity (TAI) of the first TA is TAI-1, and the RAN devices in the first TA both support S-NSSAI-1 and both do not support S-NSSAI-2.

2) The first RAN device itself does not support the requested network slice type.

3) A cell (cell) served by the first RAN device includes a cell that does not support the requested network slice type, and the UE is located in the cell that does not support the requested network slice type. For example, the first RAN device serves one or more cells in which the UE is located in cell-1, where cell-1 does not support the requested network slice type, so for the UE, the first RAN device does not support the requested network slice type.

4) The slice Service Area (SA) in which the first RAN device is located does not support the requested network slice type. For example, none of the RAN devices within the SA in which the first RAN device is located supports the requested network slice type, wherein one or more of the RAN devices are included within the SA in which the first RAN device is located. The coverage of the SA may be larger than that of the TA, or the coverage of the SA may be smaller than that of the TA, which is not limited in this application.

S402, the first AMF network element sends information of the second RAN device to the terminal device, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

Wherein the number of the second RAN devices is one or more.

The second RAN device is, for example, RAN2 in fig. 1. The information of the second RAN device includes one or more of the following information: an Identity (ID) of the second RAN device or location information of the second RAN device. For example, the location information of the second RAN device is a cell identity (cell ID) of the second RAN device or a TAI in which the second RAN device is located.

In an embodiment of the present application, the second RAN device supports the requested network slice type, which may include but is not limited to the following cases:

1) the TA in which the second RAN device is located supports the requested network slice type. It may also be understood that all RAN devices within the TA in which the second RAN device is located support the requested network slice type, where the TA in which the second RAN device is located includes one or more RAN devices.

For example, the second RAN device is located at a second TA that supports the requested network slice type.

For example, the TAI of the second TA is TAI-2, and the RAN devices in the second TA all support S-NSSAI-2. Wherein, the number of the TAI-2 is one or more.

2) The second RAN device itself supports the requested network slice type.

3) The second RAN equipment serves a cell (cell) including a cell supporting the requested network slice type in which the UE is located. For example, the second RAN equipment serves one or more cells in which the UE is located in cell-2, where cell-2 supports the requested network slice type, so for the UE, the second RAN equipment supports the requested network slice type.

4) The SA in which the second RAN device is located supports the requested network slice type. For example, all RAN devices within the SA in which the second RAN device is located, including one or more RAN devices, support the requested network slice type. The coverage of the SA may be larger than that of the TA, or the coverage of the SA may be smaller than that of the TA, which is not limited in this application.

Optionally, the first AMF network element further sends indication information to the terminal device, where the indication information is used to indicate that the second RAN device supports the requested network slice type.

Optionally, before step S402, the method further includes: the first AMF network element determines a second RAN equipment. For example, the first AMF network element may determine the second RAN equipment in any one or more of the following three ways.

The first method is as follows: the first AMF network element acquires information of the third RAN device, and then the first AMF network element determines the RAN device supporting the requested network slice type from the third RAN device to be the second RAN device.

For example, the first AMF network element obtains information of the third RAN device from the terminal device or the first RAN device. The third RAN device is another RAN device than the first RAN device to which the terminal device can link. In other words, the third RAN device is a RAN device to which the terminal device can access the network; or, the third RAN device is a RAN device that can establish a Radio Resource Control (RRC) link with the terminal device; alternatively, the third RAN device is a RAN device that the terminal device may send a registration request. For example, the terminal device determines a third RAN device from the measurement of signal strength.

Wherein the information of the third RAN device is used to identify the third RAN device. Optionally, the information of the third RAN device includes one or more of the following information: an Identity (ID) of the third RAN device or location information of the third RAN device. For example, the location information of the third RAN device is a cell identity (cell ID) of the third RAN device or a TAI in which the third RAN device is located. For example, the information of the third RAN device sent by the UE to the first AMF network element includes information of RAN2 in fig. 1.

After the first AMF network element obtains the information of the third RAN device, the process of determining the second RAN device is as follows:

step 1, the first AMF network element determines the network slice type supported by the third RAN equipment according to the information of the third RAN equipment.

For example, referring to the NG establishment procedure of steps S301-S304 in fig. 3, the first AMF network element may obtain the capability of the network slice supported by each RAN device deployed in the service area of the first AMF network element. As shown in table 1, the RAN device deployed in the service area of the first AMF network element includes RAN-1 and RAN-2, and the first AMF network element may obtain: the network slice type supported by RAN-1 is S-NSSAI-1, and the network slice type supported by RAN-2 is S-NSSAI-2.

TABLE 1

Or, the first AMF network element may obtain a TAI where each RAN device deployed in a service area of the first AMF network element is located, and a capability of a network slice supported by the TA. As shown in table 2, the RAN device deployed in the service area of the first AMF network element includes RAN-1 and RAN-2, and the first AMF network element may obtain: the TAI where RAN-1 is located is TAI-1, and the network slice type supported by the TAI-1 is S-NSSAI-1; the TAI where RAN-2 is located is TAI-2, and the network slice type supported by TAI-2 is S-NSSAI-2.

TABLE 2

Assuming that the information of the third RAN device sent by the UE to the first AMF network element includes the information of RAN-2, the first AMF network element determines that the network slice type supported by the third RAN device is S-NSSAI-2 through table 1 or table 2.

And step 2, the first AMF network element determines the RAN equipment supporting the requested network slice type from the third RAN equipment as the second RAN equipment.

In step S401, the network slice type requested by the UE is S-NSSAI-2. In step 1, the first AMF network element determines that the network slice type supported by RAN-2 is S-NSSAI-2. Thus, the first AMF network element determines RAN-2 to be the second RAN device.

When there are a plurality of third devices acquired by the first AMF network element from the terminal device, for example, the information of the third RAN device includes information of RAN-2 and information of RAN-3, and RAN-2 and RAN-3 are both RAN devices deployed in the service area of the first AMF network element. One possible scenario is: in the step 1, it is assumed that the network slice type supported by the RAN-3 obtained by the first AMF network element is S-NSSAI-3, and in the step 2, the first AMF network element determines that the RAN-3 does not support the requested network slice, and then the first AMF network element determines that the second RAN device is RAN-2. Another possible scenario is: in the step 1, it is assumed that the network slice types supported by the RAN-2 and the RAN-3 obtained by the first AMF network element are both S-NSSAI-2, and in the step 2, the first AMF network element determines that the RAN-2 and the RAN-3 support the requested network slice, and then the first AMF network element determines that the second RAN device is RAN-2 and RAN-3.

Thus, in the first manner, the first AMF network element may determine, from the third RAN device, the second RAN device supporting the requested network slice type by acquiring information of the third RAN device.

The second method comprises the following steps: and the first AMF network element acquires the position of the terminal equipment, and then determines the second RAN equipment according to the position of the terminal equipment.

For example, the location where the terminal device is located may be a TAI where a first RAN device currently accessed by the terminal device is located.

The method for acquiring the position of the terminal equipment by the first AMF network element comprises the following steps: and the first AMF network element acquires the position information from the first RAN equipment which is currently accessed by the terminal equipment. For example, the first AMF network element obtains, from the RAN-1 device currently accessed by the terminal device, the location where the terminal device is located is TAI-1, where the TAI where the RAN-1 device is located is TAI-1. The first AMF network element may obtain second information from the network management system, where the second information includes one or more of the following information: topology information, policy information, and configuration information. And then the first AMF network element acquires the information of other RAN equipment which is deployed around the RAN according to the second information.

For example, the second information may be as shown in table 3: the RANs deployed within the first AMF service area include RAN-1 and RAN-2. Wherein, the TAI where RAN-1 is located is TAI-1, the adjacent RAN deployed around RAN-1 is RAN-2, and the TAI where RAN-2 is located is TAI-2; the TAI where RAN-2 is located is TAI-2, the adjacent RAN which is deployed around RAN-2 is RAN-1, and the TAI where RAN-1 is located is TAI-1.

TABLE 3

Since the location of the terminal device is TAI-1, the first AMF network element may determine, through table 3, that the RAN-2 is an adjacent RAN deployed around RAN-1. And because the first AMF network element can obtain the capability of the network slice supported by each RAN device deployed in the service area of the first AMF network element. As shown in table 1, the first AMF network element may acquire that the network slice type supported by RAN-2 is S-NSSAI-2. In step S401, if the network slice type requested by the UE is S-NSSAI-2, the first AMF network element determines that the RAN-2 supports the requested network slice type, thereby determining that the RAN-2 is the second RAN device.

Therefore, in the second mode, the first AMF network element can determine the second RAN device supporting the requested network slice type by acquiring the location of the terminal device.

The third method comprises the following steps: and the first AMF network element sends information of the fourth RAN equipment or the position of the terminal equipment to the first network element, wherein the information of the fourth RAN equipment or the position of the terminal equipment is used for determining the second RAN equipment. The first AMF network element then receives information of the second RAN device from the first network element.

In the third mode, the first AMF network element further sends the requested network slice type to the first network element.

For example, the first network element is a second AMF network element or an NSSF network element. For example, the fourth RAN device does not have an interface with the first AMF network element. The second AMF network element serves a fourth RAN device.

The third method can be realized by any one of the following two methods:

the first method comprises the following steps: and if the first AMF network element sends the information of the fourth RAN equipment to the first network element.

For example, the first AMF network element may receive information of the fourth RAN device from the terminal device or the first RAN device. The fourth RAN device is another RAN device other than the first RAN device to which the terminal device can link. In other words, the fourth RAN device is a RAN device to which the terminal device can access the network; or, the fourth RAN device is a RAN device that can establish an RRC link with the terminal device; alternatively, the fourth RAN device is a RAN device that the terminal device may send a registration request. For example, the terminal device determines the fourth RAN device from measurements of signal strength. Or, the first AMF network element may obtain information of other RANs deployed around each RAN from the network management system, and determine, by using the location of the terminal device, that a RAN adjacent to the first RAN device deployed around the RAN is a fourth RAN device.

Wherein the information of the fourth RAN device is used to identify the fourth RAN device. Optionally, the information of the fourth RAN device includes one or more of the following information: an ID of the fourth RAN device, a cell identity of the fourth RAN device, or a TAI in which the fourth RAN device is located. The method is applicable to the following scenes: the first AMF network element determines that an interface does not exist between the fourth RAN device and the first AMF network element, and the fourth RAN device is served by the second AMF network element. In this scenario, the first AMF network element sends information of the fourth RAN device to the first network element, and the first network element determines the second RAN device according to the information of the fourth RAN device. For example, the first network element determines, according to the information of the fourth RAN device, the network slice type supported by the fourth RAN device, and the second AMF network element determines, from the fourth RAN device, the RAN device supporting the requested network slice type as the second RAN device. For example, the process of determining the second RAN device by the first network element according to the information of the fourth RAN device may refer to the process of determining the second RAN device by the first AMF network element according to the information of the third RAN device in step 1 and step 2 in the first manner, which is not described herein again.

The second method comprises the following steps: and if the first AMF network element sends the position of the terminal equipment to the first network element.

The method for acquiring the position of the terminal equipment by the first AMF network element comprises the following steps: and the first AMF network element acquires the position information from the first RAN equipment which is currently accessed by the terminal equipment.

The first AMF network element may obtain information of other RANs peripherally deployed near each RAN from the network management system, and determine, by using the location where the terminal device is located (i.e., the TAI where the first RAN device is located), that the RAN device nearby peripherally deployed by the first RAN device is the fifth RAN device.

The method is applicable to the following scenes: the first AMF network element determines that an interface does not exist between the fifth RAN device and the first AMF network element, and the fifth RAN device is served by the second AMF network element. In this scenario, the first AMF network element sends the location of the terminal device to the first network element, and the first network element determines the second RAN device according to the location of the terminal device. For example, the process of determining, by the first network element, the second RAN device according to the location of the terminal device may refer to a process of determining, by the first AMF network element, the second RAN device according to the location of the terminal device in a second manner, which is not described herein again.

Thus, by means of the third method, the first network element receives the requested network slice type and the first information from the first AMF network element, then determines the second radio access network RAN device according to the network slice type and the first information, and sends the information of the second RAN device to the first AMF network element. Wherein the information of the second RAN device is used to identify the second RAN device, which supports the requested network slice type. And the first information is information of the third RAN equipment or the position of the terminal equipment.

According to the method of the embodiment of the present invention, in the communication system shown in fig. 2, the terminal device may obtain information of the second RAN device from the first AMF network element, and since the second RAN device supports the requested network slice type, the terminal device may access the requested network slice through the second RAN device, thereby improving user experience.

Fig. 5 is a flowchart of a method for accessing a network slice according to an embodiment of the present disclosure. Fig. 5 is applicable to the communication system shown in fig. 2, and is a specific implementation of the first mode and the second mode in fig. 4. Fig. 5 will be described in conjunction with fig. 4. As shown in fig. 5, the method may include:

501. the UE sends the requested network slice type and registration request message to the first RAN device. Accordingly, the first RAN device receives the requested network slice type and registration request message from the UE.

For example, the UE requests a network slice type (Requested NSSAI) of S-NSSAI-2.

For example, the UE sends the requested network slice type to the first RAN device via an RRC message. Optionally, the UE further sends information of the third RAN device to the first RAN device through an RRC message. Wherein the information of the third RAN device is used to identify the third RAN device.

The registration request message includes the requested network slice type. Optionally, the registration request message further includes information of the third RAN device. Wherein the information of the third RAN device is used to identify the third RAN device. For example, the UE determines, according to the measurement result of the actual signal, that another RAN device other than the first RAN device to which the UE can link is a third RAN device. For the description of the information of the third RAN device, reference may be made to the description of the information of the third RAN device in the first embodiment of fig. 4, which is not described herein again.

Optionally, the UE further carries the first priority information or the second priority information in the registration request message. The first priority information is used for indicating that the priority of the requested network slice type is high, and the second priority information is used for indicating that the priority of the requested network slice type is low. For example, the registration request message further includes the first priority information or the second priority information.

502. The first RAN device sends the requested network slice type to the first AMF network element. Accordingly, the first AMF network element receives the requested network slice type from the first RAN device.

For example, the first RAN device sends the requested network slice type to the first AMF network element via a registration request message.

The first RAN device also sends location information (user location information) where the UE is currently located to the first AMF network element. For example, the location information may be identified by a TAI in which the first RAN equipment is located. Optionally, if, in step 501, the UE further sends the information of the third RAN device to the first RAN device through an RRC message, in step 502, the first RAN device sends the information of the third RAN device to the first AMF network element.

503. The first AMF network element determines a second RAN equipment.

The implementation of step 503 may refer to the first and second ways in fig. 4 for the first AMF network element to determine the second RAN equipment. If the first AMF network element obtains the information of the third RAN device in step 502, the method one is adopted: the first AMF network element determines from the third RAN device that the RAN device supporting the requested network slice type is the second RAN device. If the first AMF network element does not acquire the information of the third RAN device in step 502, the method two is adopted: and the first AMF network element determines the second RAN equipment according to the position of the UE.

After step 503, the UE may access the requested network slice through the second RAN device in any of manner a or manner b. If, in step 501, the UE also carries the first priority information in the registration request message, then the method a is adopted, which includes that the first AMF network element sends a registration rejection message to the UE according to the first priority information. In step 501, if the UE carries the second priority information in the registration request message, the method b is adopted, including that the first AMF network element sends a registration acceptance message to the UE according to the second priority information.

Wherein mode a includes steps 504a-509 a.

504a, the first AMF network element sends a registration reject message to the first RAN equipment. Accordingly, the first RAN device receives a registration rejection message from the first AMF network element.

The registration reject message includes information of the second RAN apparatus in step 503.

Since the first priority information indicates that the priority of the requested network slice type is high, it indicates that the UE preferentially accesses the network slice corresponding to the requested network slice type. Because the first RAN device accessed by the UE cannot support the requested network slice type, the first AMF determines to reject the registration procedure.

Optionally, the registration reject message further includes first indication information, where the first indication information is used to indicate that the second RAN device supports the requested network slice type.

Optionally, the registration rejection message further includes a cause value, where the cause value is used to indicate that the reason for the rejection is: the requested network slice type is not available.

For example, the registration reject message is used to instruct the first AMF network element to reject the registration request of the UE.

505a, the first RAN device sends a registration reject message to the UE. Accordingly, the UE receives a registration reject message from the first RAN device.

506a, the UE determines to initiate a re-registration with the second RAN equipment.

For example, after acquiring the information of the second RAN device from the registration reject message, the UE determines to initiate re-registration to the second RAN device according to the link quality or signal strength between the UE and the second RAN device and/or the service requirement of the UE.

And if the number of the second RAN equipment is multiple, the UE selects the second equipment with the strongest signal as the target RAN equipment according to the link quality or the signal strength between the UE and each second RAN equipment, and determines to initiate re-registration to the target RAN equipment.

507a, the UE sends an initial registration request to the second RAN device. Accordingly, the second RAN device receives an initial registration request from the UE.

The initial registration request includes a network slice type (Requested NSSAI) Requested by the UE in step 501.

508a, the UE is successfully registered to the AMF network element.

509a, the second RAN device sends a registration accept message to the UE. Accordingly, the UE receives a registration accept message from the second RAN device.

Wherein the registration acceptance message includes the allowed NSSAI. For example, in step 501, the NSSAI requested by the UE is S-NSSAI-2, and the allowed NSSAI is S-NSSAI-2.

Method b includes steps 504b-509 b.

504b, the first AMF network element sends a registration accept message to the first RAN equipment. Accordingly, the first RAN device receives a registration acceptance message from the first AMF network element.

The registration accept message includes the information of the second RAN device in step 503.

Since the second priority information indicates that the priority of the requested network slice type is low, when the first RAN device accessed by the UE cannot support the requested network slice type, the first AMF determines the allowed NSSAI for the UE as a default S-NSSAI (default S-NSSAI), and determines the rejected NSSAI (rejected NSSAI). Wherein the rejected NSSAI is of the same network slice type as the requested NSSAI.

Optionally, the registration acceptance message further includes second indication information, where the second indication information is used to indicate that the second RAN device supports the requested network slice type.

505b, the first RAN device sends a registration accept message to the UE. Accordingly, the UE receives a registration accept message from the first RAN device.

506b, the UE determines to initiate a registration update to the second RAN device.

For example, after acquiring the information of the second RAN device from the registration acceptance message, the UE determines to initiate registration update to the second RAN device according to the link quality or signal strength between the UE and the second RAN device and/or the service requirement of the UE.

And if the number of the second RAN equipment is multiple, the UE selects the second equipment with the strongest signal as the target RAN equipment according to the link quality or the signal strength between the UE and each second RAN equipment, and determines to initiate registration update to the target RAN equipment.

507b, the UE sends a registration update request to the second RAN device. Accordingly, the second RAN device receives a registration update request from the UE.

Wherein the registration update request includes the requested NSSAI, which is the rejected NSSAI in step 504 b.

508b, the UE successfully registers to the AMF network element and updates the allowed NSSAI.

509b, the second RAN device sends a registration update accept message to the UE. Accordingly, the UE receives a registration update accept message from the second RAN device.

Wherein the registration update accept message includes the updated allowed NSSAI. For example, in step 501, the NSSAI requested by the UE is S-NSSAI-2, and the updated allowed NSSAI is S-NSSAI-2.

According to the method of the embodiment of the present invention, in the communication system shown in fig. 2, the terminal device may obtain information of the second RAN device supporting the requested network slice type through the first and second modes of fig. 4, and since the second RAN device supports the requested network slice type, the terminal device may register to the first AMF through the second RAN device and access the requested network slice, thereby improving user experience.

Fig. 6 is a flowchart of a method for accessing a network slice according to an embodiment of the present disclosure. Fig. 6 is applicable to the communication system shown in fig. 2, and is a specific implementation of the third mode in fig. 4. Fig. 6 will be described in conjunction with fig. 4 and 5. As shown in fig. 6, the method may include:

601. the UE sends the requested network slice type and registration request message to the first RAN device. Accordingly, the first RAN device receives the requested network slice type and registration request message from the UE.

602. The first RAN device sends the requested network slice type to the first AMF network element. Accordingly, the first AMF network element receives the requested network slice type from the first RAN device.

Steps 601 and 602 can refer to the description of steps 501 and 502 in fig. 5, and are not described herein again.

604. And the first AMF network element sends the information of the fourth RAN equipment or the position of the terminal equipment to the first network element. Accordingly, the first network element receives the information of the fourth RAN device or the location of the terminal device from the first AMF network element.

The first AMF network element also sends the requested NSSAI to the first network element.

For example, the first AMF network element sends the information of the fourth RAN device or the location where the terminal device is located, and the requested NSSAI to the first network element through a request message or a service invocation.

For example, the first network element is a second AMF network element or an NSSF network element. When the first network element is the second AMF network element, the first AMF network element may invoke a service operation signal acquisition request (Namf _ information _ Get _ request) of the second AMF network element to send information of the fourth RAN device or a location where the terminal device is located, and a NSSAI of the request to the second AMF network element. When the first network element is an NSSF network element, the first AMF network element may invoke a network slice selection request (NSSF _ NSSelection _ Get _ request) for a service operation of the NSSF network element to send, to the NSSF network element, information of the fourth RAN device or a location where the terminal device is located, and a NSSAI of the request.

And when the first network element is the second AMF, the first AMF network element determines the identifier of the second AMF network element capable of serving the fourth RAN equipment according to the information of the fourth RAN equipment.

605. The first network element determines a second RAN equipment.

The implementation of step 605 may refer to the first method and the second method provided in the third embodiment of fig. 4, and details are not described here. If the first AMF network element sends the information of the fourth RAN device to the first network element in step 604, the first method is adopted; if the first AMF network element sends the location of the terminal device to the first network element in step 604, the second method is used.

If the first AMF network element sends the information of the fourth RAN device to the first network element in step 604, optionally, step 603 is further included: the first AMF network element determines the fourth device.

606. And the first network element sends the information of the second RAN equipment to the first AMF network element. Accordingly, the first AMF network element receives information of the second RAN device from the first network element.

For example, the first network element sends the information of the second RAN device to the first AMF network element through a response message or a service invocation. When the first network element is a second AMF network element, the second AMF network element may invoke a service operation signal acquisition response (Namf _ information _ Get _ response) of the second AMF network element to send information of the second RAN device to the first AMF network element; when the first network element is an NSSF network element, the NSSF network element may call a network slice selection response (NSSF _ NSSelection _ Get _ response) of a service operation of the NSSF network element to send information of the second RAN device to the first AMF network element.

After step 606, the UE may access the requested network slice through the second RAN device in any of manner c or manner d. Wherein, the method c includes steps 607a-612a, and refer to the description of steps 504a-509a of the method a in fig. 5, which is not repeated here. Mode c differs from mode a in that steps 610a-612a are the registration of the UE to the second AMF network element and steps 507a-509a are the registration of the UE to the first AMF network element. The method d includes steps 607b-612b, which can refer to the description of steps 504b-509b of the method b in fig. 5, and will not be described herein again. The difference between mode d and mode b is that steps 610b-612b are the registration of the UE to the second AMF network element, and steps 507b-509b are the registration of the UE to the first AMF network element.

According to the method of the embodiment of the present invention, in the communication system shown in fig. 2, the terminal device may obtain, in a third manner shown in fig. 4, information of the second RAN device that supports the requested network slice type, and since the second RAN device supports the requested network slice type, the terminal device may register to the second AMF through the second RAN device and access the requested network slice, thereby improving user experience. In the embodiments provided in the present application, the various aspects of the method for accessing a network slice provided in the embodiments of the present application are introduced from the perspective of each network element itself and from the perspective of interaction between the network elements. It is to be understood that each network element and device, such as the first AMF network element, the first RAN device, the terminal device, the second RAN device and the first network element, for implementing the above functions, includes a corresponding hardware structure and/or software module for performing each function. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

For example, when the network element implements the corresponding functions through software modules. The apparatus of the access network slice may include a receiving module 701, a processing module 702, and a transmitting module 703, as shown in fig. 7A.

In one embodiment, the apparatus for accessing the network slice may be configured to perform the operations of the first AMF network element in fig. 4 and 5. For example, the apparatus for accessing network slicing includes:

a receiving module 701, configured to receive, by a first RAN device (e.g., the first RAN network element in fig. 4 and 5), a requested network slice type from a terminal device, where the first RAN device does not support the requested network slice type; a sending module 703 is configured to send, to a terminal device (e.g., the UE in fig. 4 and 5), information of a second RAN device (e.g., the second RAN network element in fig. 4 and 5), where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

Therefore, in the embodiment of the present invention, the terminal device may obtain the information of the second RAN device from the first AMF network element, and since the second RAN device supports the requested network slice type, the terminal device may access the requested network slice through the second RAN device, thereby improving user experience.

Optionally, the first RAN device is located in a first TA, and the first TA does not support the requested network slice type; the second RAN device is located at a second TA that supports the requested network slice type.

Optionally, the first RAN device is located at a first TA, the second RAN device is located at a second TA, and the terminal device is located at the first TA and the second TA; or the location of the terminal device is located in the coverage area of the first RAN device and in the coverage area of the second RAN device.

Optionally, the apparatus for accessing network slice further includes: a processing module 702 is configured to determine a second RAN device.

Optionally, the processing module 702 is configured to obtain information of a third RAN device, and determine, from the third RAN device, that a RAN device supporting the requested network slice type is a second RAN device.

Optionally, the processing module 702 is configured to obtain a location of the terminal device, and determine the second RAN device according to the location of the terminal device.

Optionally, the sending module 703 is configured to send, to the first network element, information of a fourth RAN device or a location of the terminal device, where the information of the fourth RAN device or the location of the terminal device is used to determine the second RAN device; the receiving module 701 is configured to receive information of the second RAN apparatus from the first network element.

Optionally, the first network element is a second AMF network element or an NSSF network element.

Optionally, the sending module 703 is further configured to send indication information to the terminal device, where the indication information is used to indicate that the second RAN device supports the requested network slice type.

Optionally, the receiving module 701 is further configured to receive first priority information from the terminal device, where the first priority information is used to indicate that the priority of the requested network slice type is high; the sending module 703 is further configured to send a registration rejection message to the terminal device according to the first priority information.

Optionally, the receiving module 701 is further configured to receive second priority information from the terminal device, where the second priority information is used to indicate that the priority of the requested network slice type is low; the sending module 703 is further configured to send a registration acceptance message to the terminal device according to the second priority information.

In addition, the receiving module 701, the processing module 702, and the sending module 703 in the apparatus for accessing network slices may also implement other operations or functions of the first AMF network element in fig. 4 and fig. 5, which are not described herein again.

In another embodiment, the apparatus for accessing a network slice shown in fig. 7A may also be used to perform the operations of the UE in fig. 4 and 5. For example, the apparatus for accessing network slicing includes:

a sending module 703 configured to send, by a first RAN device (e.g., the first RAN device in fig. 4 and 5), a requested network slice type to a first AMF network element (e.g., the first AMF network element in fig. 4 and 5), where the first RAN device does not support the requested network slice type; a receiving module 701, configured to receive, from the first AMF network element, information of a second RAN device (e.g., the second RAN device in fig. 4 and 5), where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

Optionally, the sending module 703 is further configured to send the requested network slice type to the second RAN device.

Optionally, the sending module 703 is further configured to send information of a third RAN device to the first AMF network element or the first RAN device, where a RAN device supporting the requested network slice type in the third RAN device is the second RAN device.

Optionally, the receiving module 701 is further configured to receive indication information from the AMF network element, where the indication information is used to indicate that the second RAN device supports the requested network slice type.

Optionally, the sending module 703 is further configured to send first priority information to the AMF network element, where the first priority information is used to indicate that the priority of the requested network slice type is high; the receiving module 701 is further configured to receive a registration reject message from the AMF network element.

Optionally, the sending module 703 is further configured to send second priority information to the AMF network element, where the second priority information is used to indicate that the priority of the requested network slice type is low; the receiving module 701 is further configured to receive a registration acceptance message from the AMF network element.

Optionally, the apparatus for accessing network slicing further includes a processing module 702, configured to select one second RAN device from the plurality of second RAN devices according to signal strength and/or traffic demand.

In addition, the receiving module 701, the processing module 702, and the sending module 703 in the apparatus for accessing network slices may also implement other operations or functions of the UE in fig. 4 and fig. 5, which are not described herein again.

In another embodiment, the apparatus for accessing a network slice shown in fig. 7A may be further configured to perform the operations of the first network element in fig. 6. For example, the apparatus for accessing network slicing includes:

a receiving module 701, configured to receive a requested network slice type and first information from a first AMF network element, where the requested network slice type is a network slice type requested by a terminal device for access; a processing module 702 configured to determine a second RAN device according to the network slice type and the first information; a sending module 703 is configured to send information of the second RAN device to the first AMF network element, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

Therefore, in the embodiment of the present invention, the terminal device may obtain the information of the second RAN device from the first network element, and since the second RAN device supports the requested network slice type, the terminal device may access the requested network slice through the second RAN device, thereby improving user experience.

Optionally, the first information is information of a third RAN device; the processing module 702 is configured to determine that a RAN device of the third RAN device that supports the requested network slice type is the second RAN device.

Optionally, the first information is a location of the terminal device.

Optionally, the first network element includes a second AMF network element or an NSSF network element.

In addition, the receiving module 701, the processing module 702, and the sending module 703 in the apparatus for accessing network slice may also implement other operations or functions of the first network element in fig. 6, which is not described herein again. Fig. 7B shows another possible structure diagram of the apparatus for access network slicing involved in the above embodiments. The means for accessing the network slice includes a transceiver 704 and a processor 705, as shown in fig. 7B. For example, the processor 705 may be a general purpose microprocessor, a data processing circuit, an Application Specific Integrated Circuit (ASIC), or a field-programmable gate array (FPGA) circuit. The means for accessing the network slice may also include a memory 706, such as a Random Access Memory (RAM). The memory is for coupling with the processor 705, which holds the necessary computer programs 7061 for the means for accessing the network slice.

Furthermore, the apparatus for accessing network slices as referred to in the above embodiments further provides a carrier 707, in which a computer program 7071 of the apparatus for accessing network slices is stored, and the computer program 7071 may be loaded into the processor 705. The carrier may be an optical signal, an electrical signal, an electromagnetic signal, or a computer readable storage medium (e.g., a hard disk).

The

computer program

7061 or 7071 described above, when run on a computer (e.g., the processor 705), can cause the computer to perform the methods described above.

For example, in one embodiment, the processor 705 is configured to other operations or functions of a first AMF network element (e.g., the first AMF network element in fig. 4, 5). The transceiver 704 is configured to enable communication between the first AMF network element and the terminal device/first RAN device/first network element.

In another embodiment, the processor 705 is configured for other operations or functions of the terminal device (e.g., the UE of fig. 4, 5). The transceiver 704 is used to enable communication between the terminal device and the first RAN device/first AMF network element/second RAN device.

In another embodiment, the processor 705 is configured as other operations or functions of a first network element (e.g., the first network element in fig. 6). The transceiver 704 is used to enable communication between the first network element and the first AMF network element/terminal device.

One or more of the above modules or units may be implemented in software, hardware or a combination of both. When any of the above modules or units are implemented in software, which is present as computer program instructions and stored in a memory, a processor may be used to execute the program instructions and implement the above method flows. The processor may include, but is not limited to, at least one of: various computing devices that run software, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), a Microcontroller (MCU), or an artificial intelligence processor, may each include one or more cores for executing software instructions to perform operations or processing. The processor may be built in an SoC (system on chip) or an Application Specific Integrated Circuit (ASIC), or may be a separate semiconductor chip. The processor may further include a necessary hardware accelerator such as a Field Programmable Gate Array (FPGA), a PLD (programmable logic device), or a logic circuit for implementing a dedicated logic operation, in addition to a core for executing software instructions to perform an operation or a process.

When the above modules or units are implemented in hardware, the hardware may be any one or any combination of a CPU, a microprocessor, a DSP, an MCU, an artificial intelligence processor, an ASIC, an SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator, or a discrete device that is not integrated, which may run necessary software or is independent of software to perform the above method flows.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

Claims

1. A method of accessing network slices, comprising:

a first access and mobility management function (AMF) network element receives a requested network slice type from a terminal device through first Radio Access Network (RAN) equipment, wherein the first RAN equipment does not support the requested network slice type;

and the first AMF network element sends information of second RAN equipment to the terminal equipment, wherein the information of the second RAN equipment is used for identifying the second RAN equipment, and the second RAN equipment supports the requested network slice type.

2. The method of claim 1,

the first RAN device is located in a first Tracking Area (TA), and the first TA does not support the requested network slice type;

the second RAN device is located at a second TA that supports the requested network slice type.

3. The method according to claim 1 or 2,

the first RAN equipment is located at a first TA, the second RAN equipment is located at a second TA, and the terminal equipment is located at the first TA and the second TA; alternatively, the first and second electrodes may be,

the terminal device is located in a coverage area of the first RAN device and in a coverage area of the second RAN device.

4. The method of any of claims 1 to 3, further comprising:

the first AMF network element determines the second RAN device.

5. The method of claim 4, wherein determining, by the first AMF network element, the second RAN device comprises:

the first AMF network element acquires information of third RAN equipment;

the first AMF network element determines, from the third RAN device, a RAN device supporting the requested network slice type to be the second RAN device.

6. The method of claim 4 or 5, wherein the determining, by the first AMF network element, the second RAN device comprises:

the first AMF network element acquires the position of the terminal equipment;

and the first AMF network element determines the second RAN equipment according to the position of the terminal equipment.

7. The method of claim 4, wherein determining, by the first AMF network element, the second RAN device comprises:

the first AMF network element sends information of fourth RAN equipment or the position of the terminal equipment to a first network element, and the information of the fourth RAN equipment or the position of the terminal equipment is used for determining the second RAN equipment;

the first AMF network element receives information of the second RAN device from the first network element.

8. The method of claim 7, wherein the first network element is a second AMF network element or a Network Slice Selection Function (NSSF) network element.

9. The method of any of claims 1 to 8, further comprising:

and the first AMF network element sends indication information to the terminal equipment, wherein the indication information is used for indicating that the second RAN equipment supports the requested network slice type.

10. A method of accessing network slices, comprising:

a terminal device sends a requested network slice type to a first access and mobility management function (AMF) network element through a first Radio Access Network (RAN) device, wherein the first RAN device does not support the requested network slice type;

and the terminal equipment receives information of second RAN equipment from the first AMF network element, wherein the information of the second RAN equipment is used for identifying the second RAN equipment, and the second RAN equipment supports the requested network slice type.

11. The method of claim 10,

12. The method according to claim 10 or 11,

13. The method of any of claims 10 to 12, further comprising:

the terminal device sends the requested network slice type to the second RAN device.

14. The method of any of claims 10 to 13, further comprising:

and the terminal device sends information of a third RAN device to the first AMF network element or the first RAN device, where a RAN device supporting the requested network slice type in the third RAN device is the second RAN device.

15. An apparatus for accessing network slicing, comprising:

a receiving module, configured to receive a requested network slice type from a terminal device through a first radio access network RAN device, where the first RAN device does not support the requested network slice type;

a sending module, configured to send information of a second RAN device to the terminal device, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

16. The apparatus of claim 15,

17. The apparatus of claim 15 or 16,

18. The apparatus of any one of claims 15 to 17, further comprising:

a processing module to determine the second RAN device.

19. The apparatus of claim 18,

the processing module is used for acquiring information of third RAN equipment;

the processing module is configured to determine, from the third RAN device, that a RAN device supporting the requested network slice type is the second RAN device.

20. The apparatus of claim 18 or 19,

the processing module is used for acquiring the position of the terminal equipment;

the processing module is configured to determine the second RAN device according to a location where the terminal device is located.

21. The apparatus of claim 18,

the sending module is configured to send, to a first network element, information of a fourth RAN device or a location where the terminal device is located, where the information of the fourth RAN device or the location where the terminal device is located is used for determining the second RAN device;

the receiving module is configured to receive information of the second RAN device from the first network element.

22. The apparatus of claim 21, wherein the first network element is a second AMF network element or a Network Slice Selection Function (NSSF) network element.

23. The apparatus of any one of claims 15 to 22,

the sending module is further configured to send indication information to the terminal device, where the indication information is used to indicate that the second RAN device supports the requested network slice type.

24. An apparatus for accessing network slicing, comprising:

a sending module, configured to send a requested network slice type to a first access and mobility management function (AMF) network element through a first Radio Access Network (RAN) device, where the first RAN device does not support the requested network slice type;

a receiving module, configured to receive, from the first AMF network element, information of a second RAN device, where the information of the second RAN device is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

25. The apparatus of claim 24,

26. The apparatus of claim 24 or 25,

27. The apparatus of any one of claims 24 to 26,

the sending module is further configured to send the requested network slice type to the second RAN device.

28. The apparatus of any one of claims 24 to 27,

the sending module is further configured to send information of a third RAN device to the first AMF network element or the first RAN device, where a RAN device supporting the requested network slice type in the third RAN device is the second RAN device.

29. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-14.