CN113411815B

CN113411815B - Method and device for accessing network slice

Info

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

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 slice

Technical Field

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

Background

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

When a User Equipment (UE) initially attaches to the network, a network slice selection process is triggered. When a UE needs to access a certain network slice, the UE sends Requested network slice selection assistance information (network slice selection assistance information, nsai), also called Requested nsai, to the core network for the core network to select a network slice for the UE.

In the prior art, if the UE is located in a position where the UE can access one or more radio access network (radio access network, RAN) devices, but the UE does not perceive the network slice types supported by these RAN devices, so the UE accesses the RAN devices in a blind selection manner, and sends a registration request to the core network through the RAN devices, where the registration request message carries a Requested nsai. Since the RAN device for the UE blind-selected access does not necessarily support the Requested nsai, the network slice that the core network ultimately allows the UE to access cannot meet the requirement of the UE, i.e. the network slice that the core network allows the UE to access is different from the Requested nsai, or the registration of the UE fails. Thus, the network access efficiency of the UE is lower, and the user experience is reduced.

For example, in the scenario shown in fig. 1, the UE is currently located in the coverage of RAN1 and the coverage of RAN 2. Wherein, the RAN1 does not support the network slice type requested by the UE, and the RAN2 supports the network slice type requested by the UE. Since the UE does not perceive the network slice types supported by RAN1 and RAN2 respectively, it is assumed that UE1 accesses RAN1 through a blind selection manner 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 the RAN1 does not support the network slice type requested by the UE, and the network slice to which the core network ultimately allows the UE to access cannot meet the requirement of the UE or causes the UE to register failure.

Disclosure of Invention

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

In one aspect, embodiments of the present application provide a method of accessing a network slice, the method comprising: the first AMF network element (e.g., the first AMF network element in fig. 4, 5) receives the requested network slice type from the terminal device (e.g., the UE in fig. 4, 5) via the first RAN device (e.g., the first RAN network element in fig. 4, 5), wherein the first RAN device does not support the requested network slice type. The first AMF network element sends information of a second RAN device (e.g., the second RAN network element in fig. 4, 5) to the terminal 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.

According to the method, 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.

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

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

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

In one possible design, the first AMF network element obtains information of a 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 may determine the second RAN device supporting the requested network slice type from the third RAN device by acquiring information of the third RAN device.

In one 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 may determine the second RAN device supporting the requested network slice type by obtaining the location of the terminal device.

In one possible design, the first AMF network element sends information of the fourth RAN device or a 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 determining the second RAN device. The first AMF network element receives information of the second RAN device from the first network element. Therefore, the terminal equipment can acquire 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.

In one possible design, the first network element is a second AMF network element or an NSSF network element. Thereby the processing time of the product is reduced,

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

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

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

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

In one possible design, the first RAN device is located at a first TA that 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.

In one possible design, the terminal device sends the requested network slice type to the second RAN device. Therefore, the terminal equipment can access the requested network slice through the second RAN equipment, so that the user experience is improved.

In one possible design, the terminal device sends information of a third RAN device to the first AMF network element or the first RAN device, where the RAN device supporting the requested network slice type is the second RAN device. Thus, the first AMF network element may obtain information of the third RAN device, so that a second RAN device supporting the requested network slice type may be determined from the third RAN device.

In one possible design, the terminal device receives, from the first AMF network element, indication information indicating a network slice type requested by the second RAN device to support. Therefore, after receiving the information of the second RAN equipment, the terminal equipment can acquire the network slice type of the second RAN equipment supporting request according to the indication information.

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

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

In one possible design, when the second RAN device is plural, the method further comprises: the terminal device selects one of the plurality of second RAN devices based on signal strength and/or traffic demand. Thus, when the second RAN apparatus is plural, the terminal apparatus can select one second RAN apparatus from the plural second RAN apparatuses.

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

According to the method, the terminal equipment can obtain the information of the second RAN equipment from the first 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.

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

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

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

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

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

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

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

In yet another aspect, embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a chip system comprising a processor for supporting the above-mentioned apparatus or terminal device to implement the functions involved in the above-mentioned aspects, for example, to generate or process the information involved in the above-mentioned method. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the data transmission device. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention, the following description will explain the drawings used in the embodiments of the present invention or the background art.

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

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

fig. 3 is a flow chart of UE blind selection access network slicing;

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

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

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

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

Detailed Description

The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. In the description of the present application, "/" means or, unless otherwise indicated, for example, a/B may represent a or B; the term "and/or" in this application is merely an association relation describing an association object, and means that three kinds of relations may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the present application, "a plurality" means two or more.

Fig. 2 shows a schematic diagram of a 5G communication system provided in an embodiment of the present application. In the 5G mobile network architecture, the control plane function and the forwarding plane function of the mobile gateway are decoupled, and the separated control plane function is combined with a 3GPP conventional control network element mobility management entity (mobility management entity, MME) and the like to form a unified control plane. The user plane function (user plane function, UPF) network element is capable of implementing user plane functions (SGW-U and PGW-U) of a Serving Gateway (SGW) and a packet data network gateway (packet data network gateway, PGW). Further, the unified control plane network element can be broken down into an access and mobility management function (access and mobility management function, AMF) network element and a session management function (session management function, SMF) network element.

As shown in fig. 2, the communication system includes at least a UE 201, a RAN device 202, and an AMF network element 205. Optionally, the communication system further comprises 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 (DN) 204.

The UE 201 in the present system is not limited to the 5G network, and includes: cell phones, internet of things devices, smart home devices, industrial control devices, vehicle devices, and the like. The UE may also be referred to as a Mobile Station (Mobile Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a Terminal device (User Terminal), and a User Agent (User Agent), which are not limited herein. The terminal device may also be a car in car-to-car (V2V) communication, a machine in machine type communication, etc.

The RAN apparatus 202 referred to in the present system is an apparatus for providing a wireless communication function for the UE 201, and may include various forms of base stations, for example: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like. In systems employing different radio access technologies, the names of devices with base station functionality may vary, for example in LTE systems, referred to as evolved NodeB (eNB or eNodeB), in third generation (2rd generation,2G) systems, referred to as Node B (Node B), etc. In a new generation system, called gNB (gNodeB).

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

The SMF network element 206 involved in the present system may be responsible for session management of the terminal device. Session management includes, for example, selection of user plane devices, reselection of user plane devices, network protocol (internet protocol, IP) address assignment, quality of service (quality of service, qoS) control, and establishment, modification, or release of sessions, among others. The SMF network element may also be referred to as an SMF device or an SMF entity.

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

The DN 204 involved in the present system may be 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 the present system may select network slices for the user equipment. NSSF network elements may also be referred to as NSSF devices or NSSF entities.

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

In addition, the embodiment of the application can be also applied to other communication technologies facing the future. The network architecture and the service scenario described in the present application are for more clearly describing the technical solution of the present application, and do not constitute a limitation on the technical solution provided in the present application, and as a person of ordinary skill in the art can know, with evolution of the network architecture and appearance of a new service scenario, the technical solution provided in the present application is also applicable to similar technical problems.

Fig. 3 is a flow chart of a UE blind-select access network slice in the scenario shown in fig. 1. For example, RAN1 in fig. 3 is RAN1 in fig. 1, RAN2 in fig. 3 is RAN2 in fig. 1, AMF network elements in fig. 3 are AMF network elements in the core network in fig. 1, and UEs are located in the coverage of RAN1 and the coverage of RAN 2. As shown in fig. 3, the method may include:

s301, the RAN1 transmits single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-nsai) #1 to the AMF network element.

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

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

Through step S301 and step S302, the AMF network element may learn the network slice type 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 the RAN1 via an NG setup response (NG setup response) message. Thus, the RAN1 can learn the network slice types supported by the AMF.

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

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

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

Through step S303 and step S304, the AMF network element may learn the network slice type 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 the RAN2 via an NG setup response (NG setup response) message. Thus, the RAN2 can learn the network slice types supported by the AMF.

S305, the UE sends a requested nsai to the RAN 1.

Wherein the requested NSSAI is S-NSSAI #2.

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

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

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

Since RAN1 supports S-NSSAI #1, the requested NSSAI is S-NSSAI #2 and AMF determines that TA1 where RAN1 is located does not support the requested NSSAI. But TA1 where RAN1 is located supports default S-nsai (default S-nsai), in order to ensure that the UE can register successfully, AMF determines allowed nsai for the UE as default S-nsai, and registration area (Registration Area). And, the AMF network element determines the rejected nsai to be S-nsai #2.

S308, the AMF network element determines a radio access technology/frequency selection priority (Radio Access Technology/Frequency Selection Priority, RFSP).

For example, RFSP is used for RAN1 for air-interface spectrum selection priority control for UEs.

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

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

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

According to the method shown in fig. 3, the AMF determines for the UE that the allowed nsai is the default S-nsai in order to satisfy the UE registration. Since the default S-NSSAI is not the network slice that the UE requests access to, UE requirements (e.g., qos, bandwidth, etc.) cannot be met. In addition, after the UE receives the rejected nsai, the UE cannot try to access the network slice corresponding to the rejected nsai again in the current registration area, and can only try to access the network slice corresponding to the rejected nsai after the UE moves out of the registration area. So even if the S-nsai requested by the UE is S-nsai #2 and the RAN2 exists at the current location where the UE is located to support S-nsai #2, since the AMF determines that the rejected S-nsai is S-nsai #2 in step S307, the UE cannot try to access S-nsai #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-nsai #2. Thus, the method shown in fig. 3 results in lower network access efficiency of the UE and reduced user experience.

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

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

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

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

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

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

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

1) The TA where the first RAN device is located does not support the requested network slice type. It is also understood that all RAN devices within the TA where the first RAN device is located do not support the requested network slice type, wherein one or more RAN devices are included within the TA where the first RAN device is located.

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

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

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

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

4) The requested network slice type is not supported by the slice Service Area (SA) in which the first RAN device is located. For example, all RAN devices within 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. The coverage area of the SA may be larger than that of the TA, or the coverage area of the SA may be smaller than that of the TA, which is not limited in this application.

S402, the first AMF network element sends information of 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.

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

The second RAN device is, for example, RAN2 in fig. 1. The information of the second RAN device includes one or more of the following: identification (ID) of the second RAN device or location information of the second RAN device. For example, the location information of the second RAN device is a cell identity (cell ID) of the second RAN device or a TAI 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 is not limited to, the following cases:

1) The TA where the second RAN device is located supports the requested network slice type. It is also understood that all RAN devices within the TA where the second RAN device is located support the requested network slice type, wherein one or more RAN devices are included within the TA where the second RAN device is located.

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

For example, the TAI of the second TA is TAI-2, and both 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 cells (cells) served by the second RAN device include cells supporting the requested network slice type, and the UE is located in the cells supporting the requested network slice type. For example, the second RAN device serves one or more cells in which the UE is located, wherein cell-2 supports the requested network slice type, so that the second RAN device supports the requested network slice type for the UE.

4) The SA where the second RAN device is located supports the requested network slice type. For example, all RAN devices within 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. The coverage area of the SA may be larger than that of the TA, or the coverage area of the SA may be smaller than that of the TA, which is not limited in this application.

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

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

Mode one: the first AMF network element obtains information of the third RAN device, and then the first AMF network element determines, from the third RAN device, the RAN device supporting the requested network slice type as the second RAN device.

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

Wherein the information of the third RAN device is used to identify the third RAN device. Optionally, the information of the third RAN device includes one or more of the following: identification (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 identification (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 information of RAN2 in fig. 1.

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

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

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

TABLE 1

Or, the first AMF network element may obtain the TAI where each RAN device deployed in the service area of the first AMF network element is located, and the capability of the network slice supported by the TA. As shown in table 2, the RAN equipment deployed in the service area of the first AMF network element includes RAN-1 and RAN-2, and the first AMF network element may obtain: the TAI of the RAN-1 is TAI-1, and the type of the network slice supported by the TAI-1 is S-NSSAI-1; the TAI where the RAN-2 is located is TAI-2, and the type of network slice supported by the 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 information of RAN-2, the first AMF network element determines, through table 1 or table 2, that the network slice type supported by the third RAN device is S-nsai-2.

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

As in step S401, the network slice type requested by the UE is S-nsai-2. In step 1, the first AMF network element determines that the network slice type supported by RAN-2 is S-nsai-2. Thus, the first AMF network element determines RAN-2 as the second RAN device.

When the first AMF network element obtains multiple third devices from the terminal device, for example, the information of the third RAN device includes information of RAN-2 and information of RAN-3, where RAN-2 and RAN-3 are both RAN devices deployed in the service area of the first AMF network element. One possible scenario is: in the step 1, assuming that the first AMF network element acquires that the network slice type supported by the RAN-3 is S-nsai-3, in the step 2, the first AMF network element determines that the RAN-3 does not support the requested network slice, and then the first AMF network element determines that the second RAN device is RAN-2. Another possible scenario is: in the step 1, assuming that the network slice types supported by the RAN-2 and the RAN-3 are both S-nsai-2, in the step 2, the first AMF network element determines that the RAN-2 and the RAN-3 support the requested network slice, and then the first AMF network element determines that the second RAN device is the RAN-2 and the RAN-3.

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

Mode two: the first AMF network element obtains the position of the terminal equipment, and then the first AMF network element determines the second RAN equipment according to the position of the terminal equipment.

For example, the location of the terminal device may be the TAI of the first RAN device to which the terminal device is currently accessing.

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

For example, the second information may be as shown in table 3: the RAN deployed within the first AMF service area includes RAN-1 and RAN-2. Wherein, TAI of the RAN-1 is TAI-1, neighboring RANs deployed around the RAN-1 are RAN-2, and TAI of the RAN-2 is TAI-2; the TAI of the RAN-2 is TAI-2, the neighboring RAN deployed around the RAN-2 is RAN-1, and the TAI of the RAN-1 is TAI-1.

TABLE 3 Table 3

Since the location of the terminal device is TAI-1, the first AMF network element can determine, through table 3, that the neighboring RAN deployed around the RAN-1 is RAN-2. And because the first AMF network element may acquire the capability of the network slice supported by each RAN device deployed within the service area of the first AMF network element. As shown in table 1, the first AMF network element may obtain the network slice type supported by RAN-2 as S-nsai-2. As in step S401, if the network slice type requested by the UE is S-nsai-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 mode, the first AMF network element may determine the second RAN device supporting the requested network slice type by acquiring the location of the terminal device.

Mode three: the first AMF network element sends information of the fourth RAN device or the position of the terminal device to the first network element, wherein the information of the fourth RAN device or the position of the terminal device is used for determining the second RAN device. The first AMF network element then receives information of the second RAN device from the first network element.

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

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

Mode three may be achieved by either of the following two methods:

the first method is as follows: and if the first AMF network element sends the information of the fourth RAN equipment to the first network element.

For example, the first AMF network element may receive information of the fourth RAN device from the terminal device or the first RAN device. The fourth RAN device is a RAN device other than the first RAN device that the terminal device can link to. In other words, the fourth RAN device is a RAN device to which the terminal device can access the network; or the fourth RAN equipment is RAN equipment capable of establishing RRC link with the terminal equipment; alternatively, the fourth RAN device is a RAN device that the terminal device may send a registration request. For example, the terminal device determines the fourth RAN device based on the measurement of the signal strength. Or the first AMF network element may obtain information of other RANs disposed around each RAN from the network management system, where the first AMF network element determines, by using a location where the terminal device is located, that an adjacent RAN disposed around the first RAN device is a fourth RAN device.

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

The second method is as follows: and if the first AMF network element sends the position of the terminal equipment to the first network element.

The method for acquiring the position of the terminal equipment by the first AMF network element comprises the following steps: the first AMF network element obtains the location information from a first RAN device to which the terminal device is currently accessing.

The first AMF network element may obtain information of other RANs disposed around each RAN from the network management system, where the first AMF network element determines, through a location where the terminal device is located (i.e., a TAI where the first RAN device is located), that an adjacent RAN device disposed around the first RAN device is a fifth RAN device.

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

Thus, in the third mode, the first network element receives the requested network slice type and the first information from the first AMF network element, then determines the second radio access network RAN device according to the network slice type and the first information, and sends the information of the second RAN device to the first AMF network element. Wherein the information of the second RAN device is used to identify the second RAN device, the second RAN device supporting the requested network slice type. The first information is information of the third RAN equipment or a position of the terminal equipment.

According to the method of the embodiment of the 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, and because the second RAN device supports the requested network slice type, the terminal device can access the requested network slice through the second RAN device, thereby improving the user experience.

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

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

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

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

The registration request message includes the requested network slice type. Optionally, the registration request message further includes information of the third RAN device. Wherein the information of the third RAN device is used to identify the third RAN device. For example, the UE determines, as the third RAN device, other RAN devices than the first RAN device that the UE can link to, based on the measurement result of the actual signal. The description of the information of the third RAN apparatus may refer to the description of the information of the third RAN apparatus in the first mode of fig. 4, which is not repeated herein.

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

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

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

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

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

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

After step 503, the UE may access the requested network slice through the second RAN device in either way a or b. If in step 501, the UE further carries the first priority information in the registration request message, then the method a is adopted, where the method includes the first AMF network element sending a registration reject message to the UE according to the first priority information. In step 501, if the UE carries the second priority information in the registration request message, the method b is adopted, and the method includes that the first AMF network element sends a registration accept 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 reject message to the first RAN device. Accordingly, the first RAN device receives a registration reject message from the first AMF network element.

Wherein the registration reject message includes 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, the UE is indicated to access the network slice corresponding to the requested network slice type preferentially. Because the first RAN device accessed by the UE cannot support the requested network slice type, the first AMF determines to reject the registration procedure.

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

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

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

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

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

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

If the number of the second RAN devices is a plurality of, the UE selects the second device with the strongest signal as the target RAN device according to the link quality or signal strength between the UE and each second RAN device, and determines to initiate re-registration to the target RAN device.

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

The initial registration request includes a network slice type (Requested nsai) 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 accept message to the UE. Accordingly, the UE receives a registration accept message from the second RAN device.

Wherein the registration accept message includes the allowed nsais. 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 accept message to the first RAN device. Accordingly, the first RAN device receives a registration accept message from the first AMF network element.

Wherein the registration accept message includes 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 to which the UE has access cannot support the requested network slice type, the first AMF determines that the allowed nsai is a default S-nsai (default S-nsai) for the UE and determines a reject NSSAI (Rejected NSSAI). Wherein the rejected nsai is the same network slice type as the requested nsai.

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

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

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

For example, after the UE obtains the information of the second RAN device from the registration accept 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 the number of the second RAN devices is a plurality of, the UE selects the second device with the strongest signal as the target RAN device according to the link quality or signal strength between the UE and each second RAN device, and determines to initiate registration update to the target RAN device.

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

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

508b, the UE successfully registers to the AMF network element, and updates the allowable nsai.

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

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

According to the method of the embodiment of the present invention, in the communication system shown in fig. 2, the terminal device may obtain, through the first and second modes of fig. 4, information of the second RAN device supporting the requested network slice type, and since the second RAN device supports the requested network slice type, the terminal device may 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 a network slice according to an embodiment of the present application. Fig. 6 is a specific implementation of the third mode in fig. 4, and is applicable to the communication system shown in fig. 2. Fig. 6 will be described in conjunction with fig. 4 and 5. As shown in fig. 6, the method may include:

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

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

Steps 601 and 602 may be described with reference to steps 501 and 502 of fig. 5, and are not described in detail herein.

604. The first AMF network element sends information of the fourth RAN device or a location of the terminal device to the first network element. Correspondingly, the first network element receives information of the fourth RAN device or a location of the terminal device from the first AMF network element.

The first AMF network element also sends a requested nsai 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 nsai to the first network element through a request message or a server 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 may call a service operation signal acquisition request (namf_information_get_request) of the second AMF network element to send information of the fourth RAN device or a location of the terminal device and a requested nsai to the second AMF network element. When the first network element is an NSSF network element, the first AMF network element may invoke a service operation network slice selection request (nnnssf_nsselection_get_request) of the NSSF network element to send information of the fourth RAN device or a location where the terminal device is located and the requested NSSAI to the NSSF network element.

When the first network element is the second AMF, the first AMF network element determines the identification of the second AMF network element capable of serving the fourth RAN device according to the information of the fourth RAN device.

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

The implementation of step 605 may refer to the first method and the second method provided in the third mode of fig. 4, and will not be described herein. If in step 604 the first AMF network element sends information of the fourth RAN device to the first network element, a first method is used; if the first AMF network element sends the location of the terminal device to the first network element in step 604, a second method is used.

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

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

For example, the first network element sends the information of the second RAN device to the first AMF network element via a response message or a serviceization call. When the first network element is a second AMF network element, the second AMF network element may call a service operation signal acquisition response (namf_information_get_response) of the second AMF network element to send information of the second RAN device to the first AMF network element; when the first network element is an NSSF network element, the NSSF network element may invoke a service operation network slice selection response (nnssf_nsselection_get_response) of the NSSF network element to send information of the second RAN device to the first AMF network element.

After step 606, the UE accesses the requested network slice through the second RAN device in either way c or d. Wherein mode c includes steps 607a-612a, reference may be made to the description of steps 504a-509a of mode a in fig. 5, which is not repeated herein. Mode c differs from mode a in that steps 610a-612a are the registration of the UE with the second AMF network element, and steps 507a-509a are the registration of the UE with the first AMF network element. Mode d includes steps 607b-612b, and reference is made to the description of steps 504b-509b of mode b in fig. 5, which is not repeated here. Mode d differs from mode b in that steps 610b-612b are UE registration with the second AMF network element and steps 507b-509b are UE registration 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 may obtain, by using the third method of fig. 4, information of the second RAN device supporting the requested network slice type, and since the second RAN device supports the requested network slice type, the terminal device may register with the second AMF through the second RAN device and access the requested network slice, thereby improving user experience. In the embodiments provided in the present application, each scheme of the method for accessing to the network slice provided in the embodiments of the present application is described from the perspective of each network element itself and from the perspective of interaction between each network element. It will be appreciated that the respective network elements and devices, e.g. the first AMF network element, the first RAN device, the terminal device, the second RAN device and the first network element, comprise corresponding hardware structures and/or software modules for performing the respective functions in order to achieve the above-mentioned functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

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

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

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

Therefore, in the embodiment of the invention, 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, thereby improving the user experience.

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

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

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

Optionally, the processing module 702 is configured to obtain 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 obtain a location of the terminal device, and determine the second RAN device according to the location of the terminal device.

Optionally, the sending module 703 is configured to send, to the first network element, information of a fourth RAN device or a location where the terminal device is located, where the information of the fourth RAN device or the location where the terminal device is located is used for determining the second RAN device; the receiving module 701 is configured to receive 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 the second RAN device supports the requested network slice type.

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

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

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

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

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

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

Optionally, the sending module 703 is further configured to send information of a third RAN device to the first AMF network element or the first RAN device, where 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 the second RAN device supports the requested network slice type.

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

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

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

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

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 apparatus for accessing a network slice comprises:

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

Therefore, in the embodiment of the invention, the terminal equipment can obtain the information of the second RAN equipment from the first 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.

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

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

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

In addition, the receiving module 701, the processing module 702, and the sending module 703 in the device accessing the network slice may also implement other operations or functions of the first network element in fig. 6, which are not described herein. Fig. 7B shows another possible structural schematic diagram of the apparatus for accessing a network slice involved in the above embodiment. The means for accessing the network slice includes a transceiver 704 and a processor 705 as shown in fig. 7B. For example, the processor 705 may be a general purpose microprocessor, a data processing circuit, an application specific integrated circuit (application specific integrated circuit, ASIC), or a field-programmable gate array (field-programmable gate arrays, FPGA) circuit. The means for accessing the network slice may also include a memory 706, e.g., a random access memory (random access memory, RAM). The memory is used to couple with the processor 705 which holds the computer program 7061 necessary for the means for accessing the network slice.

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

The computer programs 7061 or 7071, when executed on a computer (e.g., the processor 705), may cause the computer to perform the methods described above.

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

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

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

One or more of the above modules or units may be implemented in software, hardware, or a combination of both. When any of the above modules or units are implemented in software, the software exists in the form of computer program instructions and is stored in a memory, a processor can be used to execute the program instructions and implement the above method flows. The processor may include, but is not limited to, at least one of: a central processing unit (central processing unit, CPU), microprocessor, digital Signal Processor (DSP), microcontroller (microcontroller unit, MCU), or artificial intelligence processor, each of which may include one or more cores for executing software instructions to perform operations or processes. The processor may be built into a SoC (system on a chip) or an application specific integrated circuit (application specific integrated circuit, ASIC) or may be a separate semiconductor chip. The processor may further include necessary hardware accelerators, such as field programmable gate arrays (field programmable gate array, FPGAs), PLDs (programmable logic devices), or logic circuits implementing dedicated logic operations, in addition to the cores for executing software instructions for operation or processing.

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., 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, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

The foregoing embodiments have been provided for the purpose of illustrating the general principles of the present invention in further detail, and are not to be construed as limiting the scope of the invention, but are merely intended to cover any modifications, equivalents, improvements, etc. based on the teachings of the invention.

Claims

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 alternatively, the process may be performed,

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,

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

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,

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

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,

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

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.