CN113411815B - Method and device for accessing network slicing - Google Patents

Abstract

The application relates to the technical field of wireless communication, and provides a method for accessing a network slice, which comprises the following steps: the first AMF network element receives the requested network slice type from the terminal equipment through the first RAN equipment, wherein the first RAN equipment does not support the requested network slice type, and the first AMF network element sends information of the 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. By the scheme provided by the embodiment, the terminal equipment can obtain the information of the second RAN equipment from the first AMF network element, and the terminal equipment can access the requested network slice through the second RAN equipment because the second RAN equipment supports the requested network slice type, so that the user experience is improved.

Description

Method and device for accessing network slicing

technical field

The present invention relates to the field of communication technologies, in particular to a method and device for accessing network slices.

Background technique

In the 5th-Generation (5G) communication era, hundreds of billions of IoT devices will be connected to the network, and different types of application scenarios have different requirements for the network. Network slicing technology provides isolated network environments for different application scenarios by virtualizing independent logical networks on the same network infrastructure, so that different application scenarios can customize network functions and features according to their own needs, thereby ensuring the needs of different services . Since terminal devices have different requirements for speed, capacity, coverage, delay, reliability, security, and bandwidth, the network slices that need to be accessed are also different.

When a user equipment (user equipment, UE) initially attaches to a network, it will trigger a network slice selection process. When the UE needs to access a certain network slice, the UE sends requested network slice selection assistance information (NSSAI), also called Requested NSSAI, to the core network, which is used by the core network to select a network slice for the UE.

In the prior art, if the location where the UE is located can access one or more radio access network (radio access network, RAN) devices, but the UE does not perceive the types of network slices supported by these RAN devices, so the UE connects to into the RAN device, and send a registration request to the core network through the RAN device, wherein the registration request message carries the Requested NSSAI. Since the RAN equipment that the UE blindly selects to access does not necessarily support the Requested NSSAI, the network slice that the core network finally allows the UE to access cannot meet the needs of the UE, that is, the network slice that the core network allows the UE to access is different from the Requested NSSAI, or causes UE registration failed. As a result, the network access efficiency of the UE is low, and the user experience is degraded.

For example, in the scenario shown in FIG. 1 , the UE is currently located in the coverage of RAN1 and the coverage of RAN2. Wherein, RAN1 does not support the type of network slicing requested by the UE, and RAN2 supports the type of network slicing requested by the UE. Since UE is not aware of the network slice types supported by RAN1 and RAN2 respectively, it is assumed that UE1 accesses RAN1 through 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 judges that RAN1 does not support the type of network slice requested by the UE, and the network slice that the core network finally allows the UE to access cannot meet the needs of the UE or cause the UE to fail to register.

Contents of the invention

Embodiments of the present invention provide a method and device for accessing network slices.

On the one hand, embodiments of the present application provide a method for accessing network slices, the method comprising: a first AMF network element (for example, the first AMF network element in FIG. 4 and FIG. 5 ) through a first RAN device ( For example, the first RAN network element in Figure 4 and Figure 5) receives the requested network slice type from the terminal device (for example, the UE in Figure 4 and Figure 5), wherein the first RAN device does not support the requested network slice type . The first AMF network element sends information about the second RAN device (for example, the second RAN network element in FIG. 4 and FIG. 5 ) to the terminal device, where the information about the second RAN device is used to identify the second RAN device, and the second The RAN device supports the requested network slice type.

According to the above method, the terminal device can obtain the information of the second RAN device from the first AMF network element, 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 a possible design, the first RAN device is located in a first TA, and the first TA does not support the requested network slice type, and the second RAN device is located in a second TA, and the second TA supports the requested network slice type.

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

In a possible design, the first AMF network element determines the second RAN device. For example, the first AMF network element may determine the second RAN device through any one or a combination of the three manners in FIG. 4 .

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

In a possible design, the first AMF network element obtains the location of the terminal device, and determines the second RAN device according to the location of the terminal device. Thus, 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.

In a possible design, the first AMF network element sends the information of the fourth RAN device or the location of the terminal device to the first network element, where the information of the fourth RAN device or the location of the terminal device is used for the second Determination of RAN equipment. The first AMF network element receives the information of the second RAN device from the first network element. Thus, 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 Improved user experience.

In a possible design, the first network element is the second AMF network element or the NSSF network element. thus,

In a 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. In this way, after receiving the information of the second RAN device, the terminal device can learn, according to the indication information, that the second RAN device supports the requested network slice type.

In a 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 according to The first priority information sends a registration rejection message to the terminal device. Since the first priority information indicates that the priority of the requested network slice type is high, it means 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, therefore, the first AMF determines to reject the registration process.

In a possible design, the first AMF network element receives second priority information from the terminal device, and the second priority information is used to indicate that the priority of the requested network slice type is low; the AMF network element according to the second priority The message sends a registration acceptance message to the terminal device. 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 that the allowed NSSAI for the UE is the default S -NSSAI (default S-NSSAI), and identify the rejected NSSAI (Rejected NSSAI). Wherein, the rejected NSSAI is of the same network slice type as the requested NSSAI.

In yet another aspect, the present application also discloses a method for accessing network slicing. The method includes: a terminal device (for example, UE in FIG. 4 and FIG. 5 ) through a first RAN device (for example, in FIG. 4 and FIG. The first RAN device) sends the requested network slice type to the first AMF network element (for example, the first AMF network element in Figure 4 and Figure 5), the first RAN device does not support the requested network slice type, and the terminal device from The first AMF network element receives the information of the second RAN device (for example, the second RAN device in Figure 4 and Figure 5), 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 above method, the terminal device can obtain the information of the second RAN device from the first AMF network element, 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 a possible design, 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 in a second TA, and the second TA supports the requested network slice type.

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

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

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

In a possible design, the terminal device receives indication information from the first AMF network element, where the indication information is used to indicate that the second RAN device supports the requested network slice type. In this way, after receiving the information of the second RAN device, the terminal device can learn, according to the indication information, that the second RAN device supports the requested network slice type.

In a 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 sends the first priority information from the AMF network element Receive a registration rejection message.

In a 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 sends the first AMF network element Receive a registration acceptance message.

In a possible design, when there are multiple second RAN devices, the method further includes: the terminal device selects one second RAN device from multiple second RAN devices according to signal strength and/or service requirements. Thus, when there are multiple second RAN devices, the terminal device may select one second RAN device from the multiple second RAN devices.

In yet another aspect, the present application also discloses a method for accessing network slicing, the method comprising: the first network element (for example, the first network element in FIG. 6 ) from the first AMF network element (for example, the first network element in FIG. 6 The first AMF network element) receives the requested network slice type and first information, where the requested network slice type is the network slice type that the terminal device (for example, the UE in FIG. 6 ) requests to access. The first network element determines the second RAN device (for example, the second RAN device in FIG. 6 ) 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 second RAN The device information is used to identify the second RAN device, and the second RAN device supports the requested network slice type.

According to the above method, the terminal device can 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 can access the requested network slice through the second RAN device, thereby Improved user experience.

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

In a possible design, the first information is the location of the terminal device.

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

In yet another aspect, the embodiment of the present application provides a device for accessing network slicing, the device has the function of implementing the behavior of the first AMF network element (for example, the first AMF network element in Figure 4 and Figure 5 ) in the above method . The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the above device includes a processor and a transceiver, and the processor is configured to process the device to perform corresponding functions in the above method. The transceiver is used to implement communication between the above apparatus and the terminal device/first RAN device/first network element. The device may also include a memory, coupled to the processor, which stores program instructions and data necessary for the device.

In yet another aspect, an embodiment of the present application provides an apparatus for accessing network slicing, and the apparatus has a function of realizing the behavior of a terminal device (for example, UE in FIG. 4 and FIG. 5 ) in the above method. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the above device includes a processor and a transceiver, and the processor is configured to process the device to perform corresponding functions in the above method. The transceiver is used to implement communication between the above apparatus and the first RAN device/first AMF network element/second RAN device. The device may also include a memory, coupled to the processor, which stores program instructions and data necessary for the device.

In yet another aspect, an embodiment of the present application provides an apparatus for accessing network slicing, and the apparatus has a function of realizing the behavior of the first network element (for example, the first network element in FIG. 6 ) in the above method. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the structure of the above device includes a processor and a transceiver, and the processor is configured to process the device to perform corresponding functions in the above method. The transceiver is used to implement communication between the above apparatus and the first AMF network element/terminal device. The device may also include a memory, coupled to the processor, which stores program instructions and data necessary for the device.

In yet another aspect, the embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, it causes the computer to execute the methods described in the foregoing aspects.

In yet another aspect, the embodiments of the present application provide a computer program product including instructions, which, when run on a computer, cause the computer to execute the methods described in the above aspects.

In yet another aspect, the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to support the above-mentioned device or terminal device to implement the functions involved in the above-mentioned aspect, for example, generate or process the information involved in the above-mentioned method. In a possible design, the chip system further includes a memory, and the memory is configured to store necessary program instructions and data of the data sending device. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will describe the drawings that need to be used in the embodiments of the present invention or the background technology.

FIG. 1 is a schematic diagram of a scene provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a 5G communication system provided according to an embodiment of the present application;

FIG. 3 is a flow chart of UE blindly selecting an access network slice;

FIG. 4 is a method for accessing network slicing provided according to an embodiment of the present application;

FIG. 5 is a flow chart of a method for accessing network slices according to an embodiment of the present application;

FIG. 6 is a flow chart of another method for accessing network slices according to an embodiment of the present application;

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

Detailed ways

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 this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this application is only a description of the relationship between associated objects , which means that there can be three kinds of relationships, for example, A and/or B, can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the present application, "plurality" means two or more.

Fig. 2 shows a schematic diagram of a 5G communication system provided by an embodiment of the present application. In the 5G mobile network architecture, the control plane function of the mobile gateway is decoupled from the forwarding plane function, and the separated control plane function is merged with the traditional 3GPP control network element mobility management entity (MME) into a unified control plane. The user plane function (user plane function, UPF) network element can realize the user plane functions (SGW-U and PGW-U) of the serving gateway (serving gateway, SGW) and the packet data network gateway (packet data network gateway, PGW). Further, the unified control plane network elements can be decomposed into access and mobility management function (access and mobility management function, AMF) network elements and session management function (session management function, SMF) network elements.

As shown in FIG. 2 , the communication system at least includes 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 (network slice selection function, NSSF) network element 207, and a data network (data network, DN) 204.

Among them, the UE 201 involved in this system is not limited to the 5G network, including: mobile phones, Internet of Things devices, smart home devices, industrial control devices, vehicle devices and so on. The UE may also be called a mobile station (Mobile Station), a mobile station (Mobile), a remote station (Remote Station), a remote terminal (Remote Terminal), an access terminal (AccessTerminal), a terminal device (User Terminal), a user agent (User Agent), not limited here. The above-mentioned terminal device may also be a vehicle in vehicle-to-vehicle (Vehicle-to-vehicle, V2V) communication, a machine in machine-type communication, and the like.

The RAN device 202 involved in this system is a device for providing wireless communication functions for the UE 201, and may include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access point etc. In systems using different radio access technologies, the name of the equipment with base station functions may be different. For example, in an LTE system, it is called an evolved NodeB (evolved NodeB, eNB or eNodeB). In a 2rd generation (2G) system, it is called a Node B (Node B). In the new generation system, it is called gNB (gNodeB).

The AMF network element 205 involved in this system may be responsible for terminal device registration, mobility management, tracking area update process, and the like. An AMF network element may also be called an AMF device or an AMF entity.

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

The UPF network element 203 involved in this system can implement functions such as forwarding, statistics and detection of user messages. A UPF network element may also be called a UPF device or a UPF entity.

The DN 204 involved in this system may be a service provided by an operator, an Internet access service, or a service provided by a third party.

The NSSF network element 207 involved in this system can select a network slice for the user equipment. An NSSF network element may also be called an NSSF device or an NSSF entity.

Each of the above-mentioned network elements can be a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or an instance of a virtualized function on a virtualization platform. For example, the above-mentioned virtualization platform can be a cloud platform.

In addition, the embodiments of the present application may also be applicable to other future-oriented communication technologies. The network architecture and business scenarios described in this application are to illustrate the technical solution of this application more clearly, and do not constitute a limitation to the technical solution provided by this application. Those of ordinary skill in the art know that with the evolution of network architecture and new business scenarios The technical solutions provided by this application are also applicable to similar technical problems.

FIG. 3 is a flowchart of blind selection of a UE to access a network slice in the scenario shown in FIG. 1 . For example, RAN1 in Figure 3 is RAN1 in Figure 1, RAN2 in Figure 3 is RAN2 in Figure 1, the AMF network element in Figure 3 is the AMF network element in the core network in Figure 1, and the UE is located in the coverage of RAN1 range and coverage of RAN2. As shown in Figure 3, the method may include:

S301. RAN1 sends single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) #1 to an AMF network element.

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

S302. The AMF network element stores the S-NSSAI#1.

Through step S301 and step S302, the AMF network element can know the type of network slice supported by TA1 where RAN1 is located.

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

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

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

S304. The AMF network element stores the S-NSSAI#2.

Through steps S303 and S304, the AMF network element can know the type of network slice supported by TA2 where RAN2 is located.

Optionally, after step S303, the AMF network element sends a list of network slices supported by the AMF network element to RAN2 through an NG setup response (NG setup response) message. Thus, RAN2 can know the type of network slice supported by the AMF.

S305. The UE sends the requested NSSAI to the RAN1.

Wherein, the requested NSSAI is S-NSSAI#2.

For example, the UE selects RAN1 to access the network through blind selection, and sends the requested NSSAI to RAN1 through a registration request message.

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

S307. The AMF network element determines the allowed NSSAI (Allowed NSSAI) and the rejected NSSAI (Rejected NSSAI).

Since RAN1 supports S-NSSAI#1 and the requested NSSAI is S-NSSAI#2, the AMF judges that TA1 where RAN1 is located does not support the requested NSSAI. However, TA1 where RAN1 is located supports the default S-NSSAI (default S-NSSAI). In order to ensure that the UE can register smoothly, the AMF determines for the UE that the allowed NSSAI is the default S-NSSAI and the registration area (RegistrationArea). 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 (Radio Access Technology/Frequency Selection Priority, RFSP).

For example, the RFSP is used by the RAN1 to control the priority of air interface spectrum selection for the UE.

S309. The AMF network element sends a registration acceptance message to RAN1.

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

S310, RAN1 sends a registration acceptance message to UE.

According to the method shown in FIG. 3 , in order to satisfy UE registration, the AMF determines that the allowed NSSAI is the default S-NSSAI for the UE. Since the default S-NSSAI is not the network slice that the UE requests to access, it cannot meet the requirements of the UE (such as Qos, bandwidth, etc.). In addition, after the UE receives the rejected NSSAI, in the current registration area, the UE cannot try to access the network slice corresponding to the rejected NSSAI again, and can only try to access the network slice corresponding to the rejected NSSAI after the UE moves out of the registration area. Therefore, even if the S-NSSAI requested by the UE is S-NSSAI#2, and there is RAN2 in the current location of the UE that can support S-NSSAI#2, since the AMF determines that the rejected S-NSSAI is S-NSSAI#2 in step S307 , so the UE cannot try to access S-NSSAI#2 again at the current location, and needs 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 results in low network access efficiency of the UE and degraded user experience.

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

Figure 4 is a method for accessing network slicing provided by the embodiment of the present application. The applicable scenario of this method is: the first RAN device is located in the first TA, the second RAN device is located in the second TA, and the UE is located in the first TA. The TA is located in the second TA; or, the UE is located in the coverage area of the first RAN device and in the coverage area of the second RAN device.

The method shown in 4 can be used in the 5G communication system in FIG. 2 . Through this method, the terminal device can know the second RAN device that supports the requested network slice type, and then the requested network slice can be accessed through the second RAN device. As shown in Figure 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, and 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 in FIG. 1 , the first RAN device is RAN1 in FIG. 1 , and the terminal device is 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.

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

1) The TA where the first RAN device is located does not support the requested network slice type. It can also be understood that none of the RAN devices in the TA where the first RAN device is located supports the requested network slice type, where the TA where the first RAN device is located contains one or more RAN devices.

For example, the first RAN device is located in the first TA, and the first TA does not support the requested network slice type.

For example, the tracking area identity (tracking area identity, TAI) of the first TA is TAI-1, and the RAN devices in the first TA all support S-NSSAI-1, and none support S-NSSAI-2.

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

3) The 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, and the UE is located in cell-1 in the one or more cells, where cell-1 does not support the requested network slice type, so for the UE, the first RAN device does not The requested network slice type is supported.

4) The slice service area (slicing area, SA) where the first RAN device is located does not support the requested network slice type. For example, all RAN devices in the SA where the first RAN device is located do not support the requested network slice type, where the SA where the first RAN device is located contains one or more RAN devices. Wherein, the coverage area of the SA may be larger than the coverage area of the TA, or the coverage area of the SA may be smaller than the coverage area of the TA, which is not limited in this application.

S402. The first AMF network element sends 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.

Wherein, the quantity of the second RAN device is one or more.

For example, the second RAN device is RAN2 in FIG. 1 . The information of the second RAN device includes one or more of the following information: an identity (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 identifier (cell ID) of the second RAN device or a TAI where the second RAN device is located.

Wherein, in the embodiment of the present application, the second RAN device supports the requested network slice type, which may include but not limited to the following situations:

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

For example, the second RAN device is located in the second TA, and the second TA supports the requested network slice type.

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

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

3) The cell (cell) served by the second RAN device includes a cell supporting the requested network slice type, and the UE is located in the cell supporting the requested network slice type. For example, the second RAN device serves one or more cells, and the UE is located in cell-2 in the one or more cells, where cell-2 supports the requested network slice type, so for the UE, the second RAN device supports the request The type of network slicing.

4) The SA where the second RAN device is located supports the requested network slice type. For example, all RAN devices in the SA where the second RAN device is located support the requested network slice type, where the SA where the second RAN device is located contains one or more RAN devices. Wherein, the coverage area of the SA may be larger than the coverage area of the TA, or the coverage area of the SA may be smaller than the coverage area 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 the second RAN device. For example, the first AMF network element may determine the second RAN device through any one or a combination of the following three manners.

Way 1: The first AMF network element obtains the information of the third RAN device, and then 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.

For example, the first AMF network element acquires the information of the third RAN device from the terminal device or the first RAN device. The third RAN device is other RAN devices except the first RAN device to which the terminal device can be linked. In other words, the third RAN device is a RAN device that the terminal device can access the network; or, the third RAN device is a RAN device that can establish a radio resource control (Radio Resource Control, RRC) link with the terminal device; or, the third RAN device is a RAN device that can establish a radio resource control (Radio Resource Control, RRC) link with the terminal device; The three RAN devices are RAN devices to which the terminal device can send a registration request. For example, the terminal device determines the third RAN device according to the signal strength measurement.

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 (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 identifier (cell ID) of the third RAN device, or a TAI where 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 the 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 device according to the information of the third RAN device.

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

Table 1

Alternatively, the first AMF network element may obtain the TAI where each RAN device deployed in the service area of the first AMF network element is located, and the network slice capability supported by the TA. As shown in Table 2, the RAN devices deployed in the service area of the first AMF network element include RAN-1 and RAN-2, and the first AMF network element can obtain: the TAI where RAN-1 is located is TAI-1, TAI-1 The supported network slice type 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 from Table 1 or Table 2 that the network slice type supported by the third RAN device is S-NSSAI- 2.

Step 2: 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.

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 that RAN-2 is the second RAN device.

When there are multiple third devices obtained by the first AMF network element from the terminal device, for example, the information of the third RAN device includes the information of RAN-2 and the information of RAN-3, and both RAN-2 and RAN-3 are the first A RAN device deployed in the service area of the AMF network element. A possible situation is: in the above step 1, assuming that the first AMF network element obtains that the network slice type supported by RAN-3 is S-NSSAI-3, in the above step 2, the first AMF network element determines that the RAN-3 3 If the requested network slice is not supported, the first AMF network element determines that the second RAN device is RAN-2. Another possible situation is: in the above step 1, assuming that the first AMF network element obtains that the network slice types supported by RAN-2 and RAN-3 are both S-NSSAI-2, in the above step 2, the first The AMF network element determines that RAN-2 and RAN-3 support the requested network slice, and then the first AMF network element determines that the second RAN devices are RAN-2 and RAN-3.

Therefore, in the first way, the first AMF network element can determine the second RAN device supporting the requested network slice type from the third RAN device by acquiring the information of the third RAN device.

Method 2: The first AMF network element obtains the location of the terminal device, and then the first AMF network element determines the second RAN device according to the location of the terminal device.

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

The method for the first AMF network element to obtain the location of the terminal device includes: the first AMF network element obtains the location information from the first RAN device currently accessed by the terminal device. For example, the first AMF network element acquires the location of the terminal device as TAI-1 from the RAN-1 device currently accessed by the terminal device, where the TAI where the RAN-1 device is located is TAI-1. The first AMF network element may obtain the second information from the network management system, and the second information includes one or more of the following information: topology information, policy information, and configuration information. Then the first AMF network element acquires information about other RAN devices deployed around each RAN according to the second information.

For example, the second information may be as shown in Table 3: RANs deployed in the first AMF service area include RAN-1 and RAN-2. Among them, the TAI where RAN-1 is located is TAI-1, the adjacent RAN deployed around RAN-1 is RAN-2, the TAI where RAN-2 is located is TAI-2; the TAI where RAN-2 is located is TAI-2, and the RAN The adjacent RAN deployed around -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 can determine that the adjacent RAN deployed around RAN-1 is RAN-2 through Table 3. And because the first AMF network element can obtain the network slicing capability supported by each RAN device deployed in the service area of the first AMF network element. As shown in Table 1, the network slice type supported by the RAN-2 that the first AMF network element can acquire 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 RAN-2 supports the requested network slice type, thereby determining that RAN-2 is the second RAN device.

Thus, in the second manner, the first AMF network element can determine the second RAN device that supports the requested network slice type by acquiring the location of the terminal device.

Mode 3: The first AMF network element sends the information of the fourth RAN device or the location of the terminal device to the first network element, wherein the information of the fourth RAN device or the location of the terminal device is used to determine the second RAN device. Then the first AMF network element receives the information of the second RAN device from the first network element.

In manner three, the first AMF network element also 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, there is no interface between the fourth RAN device and the first AMF network element. The second AMF network element serves the fourth RAN device.

Mode 3 can be implemented by any of the following two methods:

The first method: if the first AMF network element sends the information of the fourth RAN device to the first network element.

For example, the first AMF network element may receive the information of the fourth RAN device from the terminal device or the first RAN device. The fourth RAN device is other RAN devices except the first RAN device to which the terminal device can be linked. In other words, the fourth RAN device is a RAN device that 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; or, the fourth RAN device is a terminal device that can send a registration Requested RAN device. For example, the terminal device determines the fourth RAN device according to the signal strength measurement. Alternatively, the first AMF network element may obtain information about other RANs deployed around each RAN from the network management system, and the first AMF network element determines that the adjacent RAN deployed around the first RAN device is the fourth RAN based on the location of the terminal device. RAN equipment.

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 identifier of the fourth RAN device, or a TAI where the fourth RAN device is located. The applicable scenario of the method is as follows: the first AMF network element determines that there is no interface 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 the 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 the network slice type supported by the fourth RAN device according to the information of the fourth RAN device, and the second AMF network element determines from the fourth RAN device that the RAN device supporting the requested network slice type is the second RAN device . For example, the process for the first network element to determine the second RAN device based on the information of the fourth RAN device can refer to the process of the first AMF network element determining the second RAN device based on the information of the third RAN device in Step 1 and Step 2 of Method 1. , which will not be repeated this time.

The second method: if the first AMF network element sends the location of the terminal device to the first network element.

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

The method for the first AMF network element to obtain the location of the terminal device includes: the first AMF network element obtains the location information from the first RAN device currently accessed by the terminal device.

The first AMF network element can obtain information about other RANs deployed around each RAN from the network management system, and the first AMF network element determines the surrounding area of the first RAN device through the location of the terminal device (that is, the TAI where the first RAN device is located) The deployed adjacent RAN device is the fifth RAN device.

The applicable scenario of the method is as follows: the first AMF network element determines that there is no interface 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 the first network element determining the second RAN device according to the location of the terminal device may refer to the process of the first AMF network element determining the second RAN device according to the location of the terminal device in the second method, which will not be repeated this time.

Thus, through the third method, the first network element receives the requested network slice type and first information from the first AMF network element, and then determines the second radio access network RAN device according to the network slice type and the first information, and sends the request to the second radio access network RAN device An AMF network element sends the information of the second RAN device. Wherein, 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 first information is the information of the third RAN device or the location of the terminal device.

According to the method of the embodiment of the present invention, in the communication system shown in FIG. 2, the terminal device can obtain the information of the second RAN device from the first AMF network element. Since the second RAN device supports the requested network slice type, the terminal device The requested network slice can be accessed by the second RAN device, thereby improving user experience.

FIG. 5 is a flow chart of a method for accessing network slices provided by an embodiment of the present application. FIG. 5 is applicable to the communication system shown in FIG. 2 , and is a specific implementation of the first and second modes in FIG. 4 . FIG. 5 will be described in conjunction with FIG. 4 . As shown in Figure 5, the method may include:

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

For example, the network slice type (Requested NSSAI) requested by the UE is S-NSSAI-2.

For example, the UE sends the requested network slice type to the first RAN device through an RRC message. Optionally, the UE also sends the 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 requested network slice type is included in the registration request message. Optionally, the registration request message also 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, according to the measurement result of the actual signal, the UE determines that other RAN devices other than the first RAN device that the UE can link to are the 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 manner in FIG. 4 , which will not be repeated here.

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

502. The first RAN device sends the requested network slice type to the first AMF network element. Correspondingly, 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 through a registration request message.

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

503. The first AMF network element determines the second RAN device.

The implementation manner of step 503 may refer to the manner 1 and manner 2 in which the first AMF network element determines the second RAN device in FIG. 4 . If in step 502, the first AMF network element obtains the information of the third RAN device, adopt method 1: 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 equipment. If in step 502, the first AMF network element does not acquire the information of the third RAN device, the second method is adopted: the first AMF network element determines the second RAN device according to the location of the UE.

After step 503, the UE may access the network slice requested by the second RAN device through any one of manner a or manner b. If in step 501, the UE still carries the first priority information in the registration request message, adopt mode a, including the first AMF network element sending a registration rejection message to the UE according to the first priority information. In step 501, the UE carries the second priority information in the registration request message, then adopting mode b, including the first AMF network element sending a registration acceptance message to the UE according to the second priority information.

Wherein, mode a includes steps 504a-509a.

504a. The first AMF network element sends a registration rejection message to the first RAN device. Correspondingly, the first RAN device receives a registration rejection message from the first AMF network element.

Wherein, the registration rejection message includes the information of the second RAN device in step 503 .

Since the first priority information indicates that the priority of the requested network slice type is high, it means 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 process.

Optionally, the registration rejection 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 reason value, which is used to indicate that the reason for the rejection is: the requested network slice type is unavailable.

For example, the registration rejection 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 rejection message to the UE. Correspondingly, the UE receives a registration rejection message from the first RAN device.

506a. The UE determines to initiate re-registration with the second RAN device.

For example, after the UE obtains the information of the second RAN device from the registration rejection message, it determines to initiate re-registration with 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. .

If there are multiple second RAN devices, the UE selects the second device with the strongest signal as the target RAN device according to the link quality or signal strength with each second RAN device, and determines to send a message to the target RAN device. The device initiates a re-registration.

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

Wherein, the initial registration request includes the network slice type (RequestedNSSAI) requested by the UE in step 501 .

508a. The UE successfully registers with the AMF network element.

509a. The second RAN device sends a registration acceptance message to the UE. Correspondingly, the UE receives a registration acceptance 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.

Mode b includes steps 504b-509b.

504b. The first AMF network element sends a registration acceptance message to the first RAN device. Correspondingly, the first RAN device receives a registration acceptance message from the first AMF network element.

Wherein, the registration acceptance 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 that the allowed NSSAI for the UE is the default S -NSSAI (default S-NSSAI), and identify 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 acceptance message to the UE. Correspondingly, the UE receives a registration acceptance message from the first RAN device.

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

For example, after the UE obtains the information of the second RAN device from the registration acceptance message, it determines to initiate a 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. .

If there are multiple second RAN devices, the UE selects the second device with the strongest signal as the target RAN device according to the link quality or signal strength with each second RAN device, and determines to send a message to the target RAN device. The device initiates a registration update.

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

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

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

509b. The second RAN device sends a registration update acceptance message to the UE. Correspondingly, the UE receives a registration update acceptance message from the second RAN device.

Wherein, the registration update acceptance 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 can obtain the information of the second RAN device that supports the requested network slice type through methods 1 and 2 in FIG. 4 , because the second RAN The device supports the requested network slice type, so the terminal device can register with 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 network slicing provided by an embodiment of the present application. FIG. 6 is applicable to the communication system shown in FIG. 2 and is a specific realization of the third method in FIG. 4 . FIG. 6 will be described in conjunction with FIG. 4 and FIG. 5 . As shown in Figure 6, the method may include:

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

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

For steps 601 and 602, reference may be made to the description of steps 501 and 502 in FIG. 5 , and details are not repeated here.

604. The first AMF network element sends the information of the fourth RAN device or the location of the terminal device to the first network element. Correspondingly, 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 of the terminal device, and the requested NSSAI to the first network element through a request message or a service call.

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 can call the service operation signal acquisition request (Namf_information_Get_request) of the second AMF network element to send the information of the fourth RAN device or the terminal to the second AMF network element Where the device is located, and the requested NSSAI. When the first network element is an NSSF network element, the first AMF network element can call the service-oriented operation network slice selection request (Nnssf_NSSelection_Get_request) of the NSSF network element to send the information of the fourth RAN device or the location of the terminal device to the NSSF network element, and the requested NSSAI.

When the first network element is the second AMF, the first AMF network element determines the identity of the second AMF network element that can serve the fourth RAN device according to the information of the fourth RAN device.

605. The first network element determines the second RAN device.

For the implementation of step 605, reference may be made to the first method and the second method provided in the third method in FIG. 4 , which will not be repeated here. If in step 604, the first AMF network element sends the information of the fourth RAN device to the first network element, then adopt the first method; if in step 604, the first AMF network element sends the information of the terminal device to the first network element location, use the second method.

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

606. The first network element sends the information of the second RAN device to the first AMF network element. Correspondingly, the first AMF network element receives the 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 call. When the first network element is the second AMF network element, the second AMF network element can call the service operation signal of the second AMF network element to obtain a response (Namf_information_Get_response) to send the information of the second RAN device to the first AMF network element; when When the first network element is an NSSF network element, the NSSF network element may call the service-oriented operation network slice selection response (Nnssf_NSSelection_Get_response) of the NSSF network element to send the 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 through any one of manner c or manner d. Wherein, way c includes steps 607a-612a, and reference may be made to the description of steps 504a-509a of way a in FIG. 5, which will not be repeated here. The difference between mode c and mode a is that steps 610a-612a are for UE to register with the second AMF network element, and steps 507a-509a are for UE to register with the first AMF network element. Way d includes steps 607b-612b, for which reference may be made to the description of steps 504b-509b of way b in FIG. 5, which will not be repeated here. The difference between mode d and mode b is that steps 610b-612b are for UE to register with the second AMF network element, and steps 507b-509b are for UE to register with 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 can obtain the information of the second RAN device supporting the requested network slice type through the third method in FIG. 4, because the second RAN device supports the request Therefore, the terminal device can register to the second AMF through the second RAN device and access the requested network slice, thereby improving user experience. In the above-mentioned embodiments provided in the present application, the schemes of the method for accessing network slicing provided in the embodiments of the present application are introduced from the perspectives of each network element itself and interaction between network elements. It can be understood that each network element and device, such as the above-mentioned first AMF network element, first RAN device, terminal device, second RAN device and first network element, in order to realize the above functions, it includes corresponding hardware for performing each function structure and/or software modules. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

For example, when the aforementioned network elements implement corresponding functions through software modules. The apparatus for accessing network slicing may include a receiving module 701, a processing module 702, and a sending module 703, as shown in FIG. 7A.

In an embodiment, the apparatus for accessing network slices may be used to execute the operations of the first AMF network element in FIG. 4 and FIG. 5 above. For example, the device for accessing network slicing includes:

The receiving module 701 is configured to receive the requested network slice type from the terminal device through the first RAN device (for example, the first RAN network element in FIG. 4 and FIG. 5 ), wherein the first RAN device does not support the requested network slice type ; The sending module 703 is configured to send the information of the second RAN device (for example, the second RAN network element in FIG. 4 and FIG. 5 ) to the terminal device (for example, the UE in FIG. 4 and FIG. 5 ), where the second The information of the 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 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 Network slicing of requests, thus improving user experience.

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

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

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

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

Optionally, the processing module 702 is configured to acquire the 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 the information of the fourth RAN device or the location of the terminal device to the first network element, 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 used to receive the information of the second RAN device 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 also configured to The priority information sends a registration rejection message to the terminal device.

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 also configured to The priority information sends a registration acceptance message to the terminal device.

In addition, the receiving module 701, the processing module 702, and the sending module 703 in the device for accessing network slicing can also implement other operations or functions of the first AMF network element in FIG. 4 and FIG. 5, which will not be repeated here.

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

The sending module 703 is configured to send a request to the first AMF network element (for example, the first AMF network element in Figure 4 and Figure 5) through the first RAN device (for example, the first RAN device in Figure 4 and Figure 5 ) network slicing type, wherein the first RAN device does not support the requested network slicing type; the receiving module 701 is configured to receive the second RAN device (for example, the second RAN device in FIG. 4 and FIG. 5 ) from the first AMF network element ), wherein 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 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 Network slicing of requests, thus improving user experience.

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

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

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 the information of the third RAN device to the first AMF network element or the first RAN device, and the 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 also used to send the 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 also used to send the first priority information from the AMF The network element receives the registration rejection message.

Optionally, the sending module 703 is also used to send the 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 also used to receive from the AMF The network element receives the registration accept message.

Optionally, the apparatus for accessing network slicing further includes a processing module 702, configured to select a second RAN device from multiple second RAN devices according to signal strength and/or service requirements.

In addition, the receiving module 701 , the processing module 702 and the sending module 703 in the device for accessing network slicing can also implement other operations or functions of the UE in FIG. 4 and FIG. 5 , which will not be repeated here.

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

The receiving module 701 is configured to receive the requested network slice type and first information from the first AMF network element, wherein the requested network slice type is the network slice type that the terminal device requests to access; The type and the first information determine the second RAN device; the sending module 703 is configured to send 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, and the second RAN The device supports the requested network slice type.

Therefore, in the embodiment of the present invention, the terminal device can 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 can access the requested network slice through the second RAN device. network slicing, thereby improving user experience.

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

Optionally, the first information is the 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 device for accessing network slicing can also implement other operations or functions of the first network element in FIG. 6 , which will not be repeated here. Fig. 7B shows another possible structural diagram of the apparatus for accessing network slices involved in the above-mentioned embodiment. The device 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 (application specific integrated circuit, ASIC) or a field-programmable gate array (field-programmable gate arrays, FPGA) circuit. The apparatus for accessing network slices may further include a memory 706, for example, the memory is a random access memory (random access memory, RAM). The memory is used to be coupled with the processor 705, which stores the computer program 7061 necessary for the device accessing the network slice.

In addition, the device for accessing network slicing involved in the above-mentioned embodiment also provides a carrier 707, the computer program 7071 of the device for accessing network slicing is stored in the carrier, and the computer program 7071 can be loaded into the processor 705 in. The above-mentioned carrier may be an optical signal, an electrical signal, an electromagnetic signal or a computer-readable storage medium (for example, a hard disk).

When the above computer program 7061 or 7071 is run on a computer (for example, the processor 705), it can cause the computer to execute the above method.

For example, in one embodiment, the processor 705 is configured to perform other operations or functions of the first AMF network element (eg, the first AMF network element in FIG. 4 and FIG. 5 ). The transceiver 704 is configured to implement 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 as other operations or functions of the terminal device (for example, UE in FIG. 4 and FIG. 5 ). The transceiver 704 is configured to implement 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 to perform other operations or functions of the first network element (for example, the first network element in FIG. 6 ). The transceiver 704 is configured to implement 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 realized by software, hardware or a combination of both. When any of the above modules or units is implemented by software, the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and realize the above method flow. The processor may include but not limited to at least one of the following: a central processing unit (central processing unit, CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (microcontroller unit, MCU), or artificial intelligence Various types of computing devices that run software such as processors, each computing device may include one or more cores for executing software instructions to perform calculations or processing. The processor may be embedded in a SoC (system on chip) or an application specific integrated circuit (ASIC), or may be an independent semiconductor chip. The core of the processor is used to execute software instructions for calculation or processing, and may further include necessary hardware accelerators, such as field programmable gate array (field programmable gate array, FPGA), PLD (programmable logic device), Or a logic circuit that implements a dedicated logic operation.

When the above modules or units are implemented in hardware, the hardware can be CPU, microprocessor, DSP, MCU, artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator or non-integrated discrete device Any one or any combination of them, which can run necessary software or not depend on software to execute the above method flow.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer program instructions are loaded and executed on the computer, all or part of the processes or functions according to the embodiments of the present invention will be generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention and are not intended to limit the scope of the present invention. Protection scope, any modification, equivalent replacement, improvement, etc. made on the basis of the technical solution of the present invention shall be included in the protection scope of the present invention.

Claims (27)

1. A method of accessing a network slice, comprising:

the method comprises the steps that a first access and mobility management function (AMF) network element receives a registration request message from terminal equipment through first Radio Access Network (RAN) equipment, wherein the registration request message comprises a requested network slice type, and the first RAN equipment does not support the requested network slice type;

the first AMF network element sends a registration accept message to the terminal device through the first RAN device, a rejected network slice type in the registration accept message includes the requested network slice type, the registration accept message includes indication information, the indication information is used for indicating a second RAN device to support the requested network slice type, after triggering the terminal device to acquire information of the second RAN device from the registration accept message, a registration update request is determined to initiate to the second RAN device according to link quality or signal strength and/or service requirement between the terminal device and the second RAN device, and a registration update accept message is received from the second RAN device, the registration update request includes the requested network slice type, and a network slice type allowed in the registration update accept message includes the requested network slice type.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the first RAN equipment 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 in a second TA that supports the requested network slice type.

3. A method according to claim 1 or 2, characterized in that,

the first RAN equipment is located in a first TA, the second RAN equipment is located in a second TA, and the location of the terminal equipment is located in the first TA and in 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.

4. The method according to claim 1 or 2, further comprising:

the first AMF network element determines the second RAN device.

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

the first AMF network element acquires information of a third RAN device;

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.

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

the first AMF network element obtains 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 the first AMF network element determining the second RAN device comprises:

the first AMF network element sends information of fourth RAN equipment or the position of the terminal equipment to the 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. A method of accessing a network slice, comprising:

the method comprises the steps that terminal equipment sends a registration request message to a first access and mobility management function (AMF) network element through first Radio Access Network (RAN) equipment, wherein the registration request message comprises a requested network slice type, and the first RAN equipment does not support the requested network slice type;

The terminal equipment receives a registration acceptance message from the first AMF network element through the first RAN equipment, wherein the rejected network slice type in the registration acceptance message comprises the requested network slice type, and the registration acceptance message comprises indication information, and the indication information is used for indicating a second RAN equipment to support the requested network slice type;

after the terminal equipment acquires the information of the second RAN equipment from the registration acceptance message, determining to initiate a registration update request to the second RAN equipment according to the link quality or signal strength and/or service requirement between the terminal equipment and the second RAN equipment, wherein the registration update request comprises the requested network slice type;

the terminal device receives a registration update accept message from the second RAN device, the allowed network slice types in the registration update accept message including the requested network slice type.

10. The method of claim 9, wherein the step of determining the position of the substrate comprises,

the first RAN equipment 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 in a second TA that supports the requested network slice type.

11. The method according to claim 9 or 10, wherein,

the first RAN equipment is located in a first TA, the second RAN equipment is located in a second TA, and the location of the terminal equipment is located in the first TA and in 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.

12. The method according to claim 9 or 10, further comprising:

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

13. The method according to claim 9 or 10, further comprising:

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

14. An apparatus for accessing a network slice, comprising:

a receiving module, configured to receive, by a first radio access network RAN device, a registration request message from a terminal device, where the registration request message includes a requested network slice type, and the first RAN device does not support the requested network slice type;

A sending module, configured to send a registration accept message to the terminal device through the first RAN device, where a rejected network slice type in the registration accept message includes the requested network slice type, and the registration accept message includes indication information, where the indication information is used to indicate that a second RAN device supports the requested network slice type, and after triggering the terminal device to acquire information of the second RAN device from the registration accept message, determine, according to link quality or signal strength and/or service requirement between the terminal device and the second RAN device, to initiate a registration update request to the second RAN device and receive a registration update accept message from the second RAN device, where the registration update request includes the requested network slice type, and where a network slice type allowed in the registration update accept message includes the requested network slice type.

15. The apparatus of claim 14, wherein the device comprises a plurality of sensors,

the first RAN equipment 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 in a second TA that supports the requested network slice type.

16. The device according to claim 14 or 15, wherein,

the first RAN equipment is located in a first TA, the second RAN equipment is located in a second TA, and the location of the terminal equipment is located in the first TA and in 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.

17. The apparatus according to claim 14 or 15, further comprising:

and a processing module, configured to determine the second RAN device.

18. The apparatus of claim 17, wherein the device comprises a plurality of sensors,

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

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

19. The apparatus of claim 17, wherein the device comprises a plurality of sensors,

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.

20. The apparatus of claim 17, wherein the device comprises a plurality of sensors,

the sending module is configured to send information of a fourth RAN device or a location where the terminal device is located to the first network element, 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.

21. The apparatus of claim 20, wherein the first network element is a second AMF network element or a network slice selection function NSSF network element.

22. An apparatus for accessing a network slice, comprising:

a sending module, configured to send a registration request message to a first access and mobility management function AMF network element through a first radio access network RAN device, where the registration request message includes a requested network slice type, and the first RAN device does not support the requested network slice type;

a receiving module, configured to receive, by the first RAN device, a registration accept message from the first AMF network element, where a rejected network slice type in the registration accept message includes the requested network slice type, and the registration accept message includes indication information, where the indication information is used to indicate that a second RAN device supports the requested network slice type;

the sending module is further configured to determine, after obtaining the information of the second RAN device from the registration accept message, to initiate a registration update request to the second RAN device according to a link quality or a signal strength and/or a service requirement between a terminal device and the second RAN device, where the registration update request includes a network slice type of the request;

The receiving module is further configured to receive a registration update accept message from the second RAN device, where the allowed network slice type in the registration update accept message includes the requested network slice type.

23. The apparatus of claim 22, wherein the device comprises a plurality of sensors,

the first RAN equipment 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 in a second TA that supports the requested network slice type.

24. The apparatus of claim 22 or 23, wherein the device comprises a plurality of sensors,

the first RAN equipment is located in a first TA, the second RAN equipment is located in a second TA, and the location of the terminal equipment is located in the first TA and in 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.

25. The apparatus of claim 22 or 23, wherein the device comprises a plurality of sensors,

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

26. The apparatus of claim 22 or 23, wherein the device comprises a plurality of sensors,

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.

27. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1-13.