CN109429214B

CN109429214B - Method, device and system for establishing service session

Info

Publication number: CN109429214B
Application number: CN201710583114.7A
Authority: CN
Inventors: 左功同; 李卓明
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-07-17
Filing date: 2017-07-17
Publication date: 2020-10-16
Anticipated expiration: 2037-07-17
Also published as: CN109429214A

Abstract

The embodiment of the application provides a method, a device and a system for establishing a service session, so that a terminal can still successfully establish a corresponding service session when a current AMF entity may not support a network slice corresponding to a service. In order to achieve the above purpose, the embodiments of the present application provide the following technical solutions: the method comprises the steps that in the process that a terminal registers to a service network through a first access and mobility management function (AMF) entity, the terminal receives network slice information from the first AMF entity; the terminal determines a second AMF entity supporting a network slice corresponding to the service according to the network slice information; and the terminal establishes a service session of the service through the second AMF entity.

Description

Method, device and system for establishing service session

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, a device, and a system for establishing a service session.

Background

A network slice (network slice) is a logical network for supporting specific network capabilities and network characteristics, and may be an end-to-end (E2E) network including the entire network, or a part of network functions may be shared among multiple network slices, which is a key technology for meeting the requirements of the fifth generation (5th generation, 5G) mobile communication technology for transmission network differentiation proposed by the third generation partnership project (3 GPP). Generally, the transmission network characteristics of different network slices are different, and the network slices are required to be isolated from each other and not to be influenced by each other. Network slices such as Augmented Reality (AR) or Virtual Reality (VR) traffic require large bandwidth, low latency traffic; the network slice of the internet of things (IOT) service requires to support mass terminal access, but has a small bandwidth and no requirement for delay.

In a 5G system proposed by the existing 3GPP, a terminal carries Network Slice Selection Assistance Information (NSSAI) pre-configured on the terminal when initiating a registration process, and an access device selects an access and mobility management function (AMF) entity corresponding to a suitable network slice for the terminal according to the NSSAI, and further forwards a registration request to the AMF entity, and the AMF entity receives and processes the registration request, such as authentication and authentication. And after the terminal is successfully registered, the AMF entity returns the NSSAI of the network slice supported by the AMF entity to the terminal. If the NSSAI of the network slice supported by the AMF entity includes a single NSSAI (S-NSSAI) of the NSSAIs carried by the terminal when initiating the registration process, that is, if the AMF entity supports the network slice corresponding to the service, the terminal may successfully establish the corresponding service session.

However, the NSSAI of the network slice supported by the AMF may not include a certain S-NSSAI in the NSSAI carried when the terminal initiates the registration procedure, that is, the AMF entity may not support the network slice corresponding to the service. At this time, there is no relevant solution for how to enable the terminal to successfully establish the corresponding service session.

Disclosure of Invention

The embodiment of the application provides a method, a device and a system for establishing a service session, so that a terminal can still successfully establish a corresponding service session when a current AMF entity may not support a network slice corresponding to a service.

In order to achieve the above purpose, the embodiments of the present application provide the following technical solutions:

in a first aspect, a method for establishing a service session is provided, where in a process that a terminal registers to a serving network through a first access and mobility management function (AMF) entity, the terminal receives network slice information from the first AMF entity; the terminal determines a second AMF entity supporting a network slice corresponding to the service according to the network slice information; and the terminal establishes a service session of the service through the second AMF entity. In the service session establishment method provided by the embodiment of the application, the terminal can receive the network slice information from the first AMF entity, and further can determine, according to the network slice information, a second AMF entity supporting a network slice corresponding to a service, and establish a service session of the service through the second AMF entity. Therefore, based on the scheme, the terminal can be enabled to successfully establish the corresponding service session.

In one possible design, the serving network is a serving network of the terminal home; the network slice corresponding to the service is a network slice signed by the terminal in the registration area of the terminal; the method further comprises the following steps: during the process that the terminal registers to the service network through the first AMF entity, the terminal receives network slice selection auxiliary information NSSAI of the network slice subscribed by the terminal from the first AMF entity. In a non-roaming scenario, the terminal may receive the NSSAI of the network slice signed by the terminal issued by the network side, and thus, the terminal may initiate a service based on the NSSAI of the network slice signed by the terminal issued by the network side, thereby avoiding a problem that the terminal signs a certain network slice, but the terminal is not configured with the S-NSSAI of the corresponding network slice, thereby causing a session establishment failure, and improving a probability of a session establishment success.

Optionally, the network slice information includes NSSAI of network slices supported by all AMF entities in the registration area of the terminal; or, the network slice information includes NSSAI of a network slice supported by an AMF entity that supports a network slice subscribed by the terminal in a registration area of the terminal.

In one possible design, the service network is a service network of a place where the terminal accesses; the network slice corresponding to the service is a network slice corresponding to a network slice signed with the terminal in the registration area of the terminal; the method further comprises the following steps: and in the process that the terminal is registered to the service network through the first AMF entity, the terminal receives NSSAI of the network slice corresponding to the network slice subscribed by the terminal from the first AMF entity. That is, in a roaming scenario, the terminal may receive the NSSAI of the network slice corresponding to the network slice signed with the terminal in the registration area of the terminal issued by the network side, so that the terminal may initiate a service based on the NSSAI of the network slice corresponding to the network slice signed with the terminal, thereby avoiding that the terminal signs a certain network slice, but the terminal is not configured with the S-NSSAI of the network slice corresponding to the network slice, thereby causing a problem of session establishment failure, and improving a probability of session establishment success.

Further, the network slice information includes information of network slices supported by all AMF entities in the registration area of the terminal; or, the network slice information includes NSSAI of a network slice supported by an AMF entity that supports the network slice corresponding to the network slice subscribed to by the terminal in the registration area of the terminal.

In one possible design, the network slice corresponding to the service is a network slice configured on the terminal. That is, the terminal may initiate a service session based on NSSAI of the network slice configured on the terminal.

Optionally, the network slice information includes information of network slices supported by all AMF entities in the registration area of the terminal.

In one possible design, the first AMF entity and the second AMF entity are different AMF entities; the terminal establishes a service session of the service through the second AMF entity, including: the traffic session is established through the second AMF entity after the terminal re-registers with the serving network through the second AMF entity. That is, when the current AMF entity may not support the network slice corresponding to the service, the terminal may still successfully establish the corresponding service session.

In a second aspect, a method for establishing a service session is provided, where the method includes: an access and mobile management function (AMF) entity acquires network slice information in the process that a terminal registers to a service network through the AMF entity; the AMF entity sends the network slice information to the terminal, and the network slice information is used for establishing a service session. In the service session establishment method provided by the embodiment of the application, the AMF entity sends the network slice information to the terminal, so that the terminal can receive the network slice information from the first AMF entity, further determine, according to the network slice information, the second AMF entity supporting the network slice corresponding to the service, and establish the service session of the service through the second AMF entity. Therefore, based on the scheme, the terminal can be enabled to successfully establish the corresponding service session.

In one possible design, the AMF entity requests, from a NSRF entity, a network slice library function in a service network, information of a network slice subscribed to by the terminal, in a process that the terminal is registered in the service network through the AMF entity; and the AMF entity sends the information of the network slice signed by the terminal to the terminal. That is, the terminal may receive the information of the network slice signed by the terminal issued by the network side, so that the terminal may initiate a service based on the information of the network slice signed by the terminal issued by the network side, thereby avoiding a problem that the terminal signs a certain network slice, but the terminal is not configured with the information of the corresponding network slice, thereby causing a failure in session establishment, and improving the probability of a success in session establishment.

In one possible design, the terminal is a terminal of a local home subscriber; the information of the network slice signed by the terminal includes the NSSAI of the network slice signed by the terminal in the network slice selection auxiliary information NSSAI of the network slice in the registration area of the terminal.

In one possible design, the terminal is a terminal of a roaming user; the information of the network slice signed by the terminal includes NSSAI of the network slice corresponding to NSSAI of the network slice signed by the terminal among NSSAIs of the network slices in the registration area of the terminal.

In one possible design, before the AMF entity requests, from a NSRF entity in the service network, information of a network slice to which the terminal is subscribed, the method further includes: the AMF entity requests NSSAI of a network slice signed by the terminal from a database entity in a home network of the terminal; the AMF entity requests the NSRF entity for information of a network slice subscribed by the terminal, including: the AMF entity sends NSSAI of the network slice signed by the terminal to the NSRF entity, wherein the NSSAI of the network slice signed by the terminal is used for requesting the information of the network slice signed by the terminal; the AMF entity receives information of a network slice to which the terminal has subscribed from the NSRF entity. That is, in a terminal roaming scenario, mapping and management of the NSSAI of the network slice signed by the terminal and the NSSAI of the network slice in the registration area of the terminal may be completed according to a preconfigured policy or roaming protocol, so that the terminal may initiate a service based on the NSSAI of the network slice corresponding to the network slice signed by the terminal, thereby preventing the terminal from signing a certain network slice, but the terminal is not configured with the S-NSSAI of the network slice corresponding to the network slice, thereby causing a problem of session establishment failure, and improving a probability of session establishment success.

In a third aspect, a terminal is provided, where the terminal has a function of implementing the method of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, a terminal is provided, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store computer executable instructions, and the processor is connected to the memory through the bus, and when the terminal runs, the processor executes the computer executable instructions stored in the memory, so that the terminal performs the service session establishment method according to any one of the first aspect.

In a fifth aspect, a computer-readable storage medium is provided, which stores instructions that, when executed on a computer, enable the computer to execute the service session establishment method of any one of the above first aspects.

A sixth aspect provides a computer program product containing instructions which, when run on a computer, enable the computer to perform the service session establishment method of any one of the above first aspects.

In a seventh aspect, a chip system is provided, where the chip system includes a processor, configured to enable a terminal to implement the functions in the foregoing aspects, for example, determine, according to network slice information, a second AMF entity that supports a network slice corresponding to a service. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the terminal. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

The technical effects brought by any one of the design manners in the third aspect to the seventh aspect may be referred to the technical effects brought by different design manners in the first aspect, and are not described herein again.

In an eighth aspect, there is provided an AMF entity having the functionality to implement the method of the second aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a ninth aspect, there is provided an AMF entity comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store computer executable instructions, and the processor is connected to the memory through the bus, and when the AMF entity runs, the processor executes the computer executable instructions stored in the memory, so as to enable the AMF entity to perform the service session establishment method according to any one of the second aspects.

A tenth aspect provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, make the computer perform the service session establishment method of any one of the above second aspects.

In an eleventh aspect, there is provided a computer program product containing instructions which, when run on a computer, enable the computer to perform the service session establishment method of any one of the second aspects above.

In a twelfth aspect, a chip system is provided, which includes a processor for supporting the AMF entity to implement the functions referred to in the above aspects, such as obtaining network slice information. In one possible design, the system-on-chip further includes a memory for storing necessary program instructions and data for the AMF entity. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

The technical effects brought by any one of the design manners of the eighth aspect to the twelfth aspect can be referred to the technical effects brought by different design manners of the second aspect, and are not described herein again.

In a thirteenth aspect, a service session establishment system is provided, where the service session establishment system includes the terminal in any aspect and the AMF entity in any aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

Fig. 1 is a schematic architecture diagram of a service session establishment system according to an embodiment of the present application;

fig. 2 is a schematic hardware structure diagram of a communication device according to an embodiment of the present application;

fig. 3 is a first flowchart of a service session establishment method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a second method for establishing a service session according to an embodiment of the present application;

fig. 5 is a third schematic flowchart of a service session establishment method according to an embodiment of the present application;

fig. 6 is a fourth flowchart of a service session establishment method provided in the embodiment of the present application;

fig. 7 is a first schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 9 is a first schematic structural diagram of an AMF entity provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of an AMF entity according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Where in the description of the present application, "/" indicates an OR meaning, for example, A/B may indicate A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise specified. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance. For example, the first AMF entity and the second AMF entity in this embodiment may be the same AMF entity or different AMF entities, which is not specifically limited in this embodiment.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

For example, the application scenarios applicable to the embodiments of the present application are first given as follows:

when an end user moves from one scenario to another, different network slices may need to be selected to support the corresponding services, since different services may be required at different locations. For example, when the user of terminal a moves from a location x (e.g., a company) to a location y (e.g., a home) in the current area, the user of terminal a may need to access network slice 1 at the company for office, and may need to access network slice 2 at the home for entertainment, at which time the AMF entity registered at the company may not support network slice 2, which may result in terminal a not being able to successfully access network slice 2. Based on this, the embodiments of the present application provide a session establishment method, device, and system, which enable a terminal to successfully establish a corresponding service session in the scenario.

Fig. 1 is a schematic structural diagram of a service session establishment system 10 according to an embodiment of the present application. The service session establishment system 10 comprises a terminal 101, an access device 102, and at least one AMF entity 103. The at least one AMF entity 103 is an AMF entity in a registration area of the terminal in a service network of the terminal, and may include a first AMF entity 103a, a second AMF entity 103b, … …, and the like, which is not specifically limited in this embodiment.

The first AMF entity 103a is configured to acquire network slice information and send the network slice information to the terminal 101 in a process that the terminal 101 registers to a service network through the first AMF entity 103 a.

And the terminal 101 is configured to receive the network slice information from the first AMF entity 103a, and determine, according to the network slice information, a second AMF entity 103b that supports a network slice corresponding to the service.

The terminal 101 is further configured to establish a service session through the second AMF entity 103 b.

Optionally, the first AMF entity 103a and the second AMF entity 103b in this embodiment may be the same AMF entity or different AMF entities, which is not specifically limited in this embodiment.

Optionally, the service network in this embodiment of the present application may be a Visited Public Land Mobile Network (VPLMN) in a terminal roaming scenario, or may be a Home Public Land Mobile Network (HPLMN) in a terminal non-roaming scenario, which is not specifically limited in this embodiment of the present application.

Optionally, as shown in fig. 1, the Session establishing system 10 may further include other communication devices, such as a Session Management Function (SMF) entity 104, a database entity 105, or a network slice library Function (NSRF) entity 106, which is not specifically limited in this embodiment of the present invention.

It should be noted that, each device in fig. 1 may communicate directly with each other, or may communicate through forwarding of other network devices, which is not specifically limited in this embodiment of the present application.

It should be noted that fig. 1 illustrates an example where the first AMF entity 103a and the second AMF entity 103b are both connected to the SMF entity 104. Of course, when the first AMF entity 103a and the second AMF entity 103b are different AMF entities, different SMF entities may also be connected to each other, which is not specifically limited in this embodiment of the application.

It should be noted that fig. 1 illustrates an example in which the SMF entity 104 and the NSRF entity 106 are respectively deployed in other areas of the service network. Of course, at least one of the SMF entity 104 and the NSRF entity 106 may also be deployed in the registration area of the terminal 101, which is not specifically limited in this embodiment.

It should be noted that fig. 1 illustrates an example in which the HPLMN is used as the terminal in a non-roaming scenario, and the database entity 105 is deployed inside the service network. Of course, if the service network is a VPLMN in the terminal roaming scenario, the database entity 105 is deployed outside the service network. That is, the database entity 105 is deployed at the home of the terminal.

It should be noted that the session establishment system 10 may be applied to a 5G system proposed by 3GPP, and may also be applied to other networks in the future, which is not specifically limited in the embodiment of the present application. Where in other networks the AMF entity, SMF entity, database entity or NSRF entity may be other names, it will be understood by those skilled in the art that the names do not limit the device itself. For example, the database entity may be replaced by a Home Subscriber Server (HSS), a User Subscription Database (USD), or a Unified Data Management (UDM) entity, and the like, which are described in the Unified description herein and will not be described in detail below.

Optionally, the terminal (terminal) referred to in the embodiments of the present application may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; subscriber units (subscriber units), cellular phones (cellular phones), smart phones (smart phones), wireless data cards, Personal Digital Assistants (PDAs), tablet computers, wireless modems (modems), handheld devices (dhhandles), laptop computers (laptops), cordless phones (cordsets) or Wireless Local Loop (WLL) stations, Machine Type Communication (MTC) terminals, User Equipment (UE), Mobile Stations (MSs), terminal devices (terminal devices), and the like may also be included. For convenience of description, the above-mentioned devices are collectively referred to as a terminal in this application.

Optionally, the access device referred to in this embodiment of the present application refers to a device accessing a core network, and may be, for example, a base station, a broadband network service gateway (BNG), an aggregation switch, a non-3 GPP access device, and the like. The base stations may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc.

Optionally, the AMF entity in the embodiment of the present application may be responsible for functions such as registration management, mobility management, and lawful interception, besides the functions described in fig. 1, which is not specifically limited in the embodiment of the present application.

Optionally, the SMF entity related in this embodiment of the present application is configured to perform session management, and includes: session establishment, session modification, session release, Internet Protocol (IP) address allocation and management between terminal networks, selection and control of User Plane Function (UPF) entities, lawful interception and other control functions related to the session.

Optionally, the database entity related in the embodiment of the present application is configured to store subscription data of a user. In addition, the database entity may further include functions such as authentication, processing a user identifier, subscription management, and the like, which is not specifically limited in this embodiment of the present application.

Optionally, the NSRF entity in this embodiment of the application separates a function of a Network Slice Selection Function (NSSF) from the AMF entity, and is responsible for selecting and managing a network slice, for example, maintaining information of the network slice in a service network; or, in a roaming scenario, the visited (V) -NSRF entity can complete mapping of network slices in the HPLMN and the VPLMN, and maintain a mapping relationship, etc. Of course, the functionality of the NSRF entity may also be integrated in the AMF entity, which is not specifically limited in the embodiment of the present application.

Alternatively, as shown in fig. 2, both the terminal 101 and the AMF entity 103 in fig. 1 may be implemented by the communication device in fig. 2.

Fig. 2 is a schematic diagram illustrating a hardware structure of a communication device according to an embodiment of the present application. The communication device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.

The processor 201 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present invention.

The communication bus 202 may include a path that conveys information between the aforementioned components.

The communication interface 204 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 203 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 203 is used for storing application program codes for executing the scheme of the application, and the processor 201 controls the execution. The processor 201 is configured to execute the application program code stored in the memory 203, so as to implement the service session establishment method provided by the following embodiments of the present application.

In particular implementations, processor 201 may include one or more CPUs such as CPU0 and CPU1 in fig. 2, for example, as one embodiment.

In particular implementations, communication device 200 may include multiple processors, such as processor 201 and processor 208 in fig. 2, for example, as an example. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, communication device 200 may also include an output device 205 and an input device 206, as one embodiment. The output device 205 is in communication with the processor 201 and may display information in a variety of ways. For example, the output device 205 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 206 is in communication with the processor 201 and can accept user input in a variety of ways. For example, the input device 206 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The communication device 200 described above may be a general purpose communication device or a special purpose communication device. In a specific implementation, the communication device 200 may be a desktop, a laptop, a web server, a personal assistant (PDA), a mobile phone, a tablet, a wireless terminal device, an embedded device, or a device with a similar structure as in fig. 2. The embodiment of the present application does not limit the type of the communication device 200.

The service session establishment method provided in the embodiment of the present application will be specifically described below with reference to fig. 1 and fig. 2.

Assuming that the terminal 101 in fig. 1 is a terminal of a local home subscriber, the service network is the HPLMN, and the NSRF entity is deployed separately from the AMF entity. When the user of the terminal 101 moves from a company to home, the first AMF entity registered at the company may not support a network slice of video traffic, which may result in the user of the terminal 101 not being able to successfully access the network slice at home to view video. Based on this, the following two session establishment methods are provided in the embodiments of the present application, so that the terminal 101 can successfully establish a corresponding service session in the scenario.

Fig. 3 is a schematic flow chart of a service session establishment method according to an embodiment of the present application. The service session establishing method relates to the interaction among a terminal, an access device, a first AMF entity, an NSRF entity, a second AMF entity, an SMF entity and a database entity, and comprises the following steps:

s301, the terminal sends a registration request 1 to the first AMF entity. Accordingly, the first AMF entity receives a registration request 1 from the terminal.

S302, the first AMF entity obtains the subscription data of the terminal from the database entity.

And S303, the first AMF entity completes the authentication of the terminal and the service network according to the subscription data of the terminal.

S304, after the authentication is successful, the first AMF entity sends an NSSAI request to the NSRF entity. Accordingly, the NSRF entity receives a NSSAI request from the first AMF entity. The NSSAI request is used to request the NSSAI of the network slice subscribed to by the terminal, from among the NSSAIs of the network slices in the registration area of the terminal.

S305, the NSRF entity sends a NSSAI response to the first AMF entity. Accordingly, the first AMF entity receives a NSSAI response from the NSRF entity. The NSSAI response includes the NSSAI of the network slice to which the terminal has signed up.

S306, the first AMF entity obtains NSSAI of the network slice supported by at least one AMF entity.

Optionally, in this embodiment of the present application, the NSSAI of the network slice supported by at least one AMF entity includes NSSAI of network slices supported by all AMF entities in a terminal registration area in a service network of the terminal; or the NSSAI of the network slice supported by the at least one AMF entity includes NSSAI of a network slice supported by an AMF entity supporting a network slice subscribed by the terminal within a registration area of the terminal.

For example, it is assumed that three AMF entities are provided in the registration area of the terminal in the service network of the terminal, which are AMF entity 1, AMF entity 2 and AMF entity 3, respectively; and the terminal signs a network slice 1, a network slice 3 and a network slice 4; the AMF entity 1 supports a network slice 1, a network slice 2 and a network slice 4; the AMF entity 2 supports a network slice 3 and a network slice 4; AMF entity 3 supports network slice 2, network slice 4 and network slice 5, with the results shown in table one:

watch 1

As can be seen from the table one, the AMF entities supporting the network slice subscribed by the terminal in the registration area of the terminal include AMF entity 1 and AMF entity 2, that is, the network slice supported by AMF entity 1 and the network slice supported by AMF entity 2 may cover the network slice subscribed by the terminal, and based on this, the first AMF entity may obtain NSSAI of the network slices supported by AMF entity 1 and AMF entity 2. Wherein the NSSAI of the network slice supported by the AMF entity 1 comprises S-NSSAI of the network slice 1, S-NSSAI of the network slice 2 and S-NSSAI of the network slice 4; the NSSAIs of the network slices supported by the AMF entity 2 include S-NSSAI of network slice 3 and S-NSSAI of network slice 4.

Of course, the first AMF entity may also obtain NSSAI of network slices supported by all AMF entities in the terminal registration area, that is, the first AMF entity obtains NSSAI of network slices supported by AMF entity 1, AMF entity 2, and AMF entity 3. Wherein the NSSAI of the network slice supported by the AMF entity 1 comprises S-NSSAI of the network slice 1, S-NSSAI of the network slice 2 and S-NSSAI of the network slice 4; the NSSAIs of the network slices supported by the AMF entity 2 include S-NSSAI of network slice 3 and S-NSSAI of network slice 4; the NSSAI of the network slice supported by the AMF entity 3 includes S-NSSAI of the network slice 2, S-NSSAI of the network slice 4, and S-NSSAI of the network slice 5, which is not particularly limited in the embodiment of the present application.

Optionally, at least one AMF entity in this embodiment of the present application may include the first AMF entity, or may not include the first AMF entity, which is not specifically limited in this embodiment of the present application.

S307, the first AMF entity sends a registration response 1 to the terminal. Accordingly, the terminal receives the registration response message 1. The registration response 1 includes NSSAI of the network slice supported by the at least one AMF entity and NSSAI of the network slice subscribed to by the terminal.

Wherein the registration response 1 is used to indicate that the terminal is successfully registered in the serving network through the first AMF entity.

Optionally, the NSSAI of the network slice supported by the at least one AMF entity and the NSSAI of the network slice subscribed by the terminal may also be sent to the terminal through different messages, which is not specifically limited in this embodiment of the present application.

S308, the terminal determines a second AMF entity supporting the network slice corresponding to the service according to the NSSAI of the network slice supported by the at least one AMF entity.

Optionally, in this embodiment of the present application, the network slice corresponding to the service is a network slice signed by a terminal issued by a network side, that is, the terminal initiates the service based on an NSSAI of the network slice signed by the terminal issued by the network side, so that a problem that the session establishment fails because the terminal signs a certain network slice but the terminal is not configured with an S-NSSAI of a corresponding network slice is avoided, and a probability of success of the session establishment is improved.

If the plurality of AMF entities support the network slice corresponding to the service, the second AMF entity supporting the network slice corresponding to the service may be any one of the plurality of AMF entities.

Or, optionally, if the plurality of AMF entities support the network slice corresponding to the service and the plurality of AMF entities include the first AMF entity, the second AMF entity supporting the network slice corresponding to the service may be the first AMF entity, that is, the first AMF entity is the same as the second AMF entity.

If the second AMF entity is the same as the first AMF entity, that is, the network slice supported by the first AMF entity includes the network slice corresponding to the service, step S309 is executed;

if the second AMF entity is different from the first AMF entity, that is, the network slice supported by the first AMF entity does not include the network slice corresponding to the service, then steps S310 to S312 are performed.

S309, if the second AMF entity is the same as the first AMF entity, the terminal establishes a service session of the service through the first AMF entity.

Specifically, the service session establishment process may refer to the prior art, and is not described herein again.

And S310, if the second AMF entity is different from the first AMF entity, the terminal sends a registration request 2 to the second AMF entity. Accordingly, the second AMF entity receives a registration request 2 from the terminal.

And S311, the second AMF entity sends a registration response 2 to the terminal. Accordingly, the terminal receives the registration response message 2.

Wherein the registration response 2 is used to indicate that the terminal is successfully registered in the serving network through the second AMF entity.

And S312, the terminal establishes a service session of the service through the second AMF entity.

For example, assuming that the first AMF entity is AMF entity 1 in table one and the network slice supported by the service is network slice 1 in table one, the terminal may determine, according to NSSAI of the network slice supported by at least one AMF entity, that the second AMF entity supporting the network slice corresponding to the service is AMF entity 1, and then the terminal may establish a service session of the service through AMF entity 1.

Or, assuming that the first AMF entity is AMF entity 1 in table one and the network slice supported by the service is network slice 3 in table one, the terminal may determine, according to NSSAI of the network slice supported by at least one AMF entity, that the second AMF entity supporting the network slice corresponding to the service is AMF entity 2, and then the terminal may re-register in the service network through AMF entity 2, and then establish a service session of the service through AMF entity 2.

In the service session establishment method provided in the embodiment of the application, the terminal may receive the NSSAI of the network slice supported by the at least one AMF entity from the first AMF entity, and further may determine, according to the NSSAI of the network slice supported by the at least one AMF entity, a second AMF entity that supports the network slice corresponding to the service, and establish the service session of the service through the second AMF entity. Therefore, based on the scheme, the terminal can successfully establish the corresponding service session when the NSSAI based on the network slice signed by the terminal initiates the service.

The actions of the terminal in steps S301 to S312 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present application.

The actions of the first AMF entity in steps S301 to S312 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present invention.

The embodiment shown in fig. 3 is described by taking an NSSAI originating service of a network slice that is issued by a terminal on the basis of a network side and signed by the terminal as an example. Optionally, as shown in fig. 4, the terminal may also initiate a service based on the NSSAI of the network slice configured on the terminal, and at this time, the network side does not need to issue the NSSAI of the network slice signed by the terminal. Specifically, the service session establishing method relates to interaction among a terminal, an access device, a first AMF entity, an NSRF entity, a second AMF entity, an SMF entity and a database entity, and comprises the following steps:

s401 to S403 are the same as steps S301 to S303, and reference may be made to the embodiment shown in fig. 3 for details, which are not described herein again.

S404, the first AMF entity obtains NSSAI of the network slice supported by at least one AMF entity.

The related description of step S404 can refer to step S306, and is not repeated herein.

S405, the first AMF entity sends a registration response 1 to the terminal. Accordingly, the terminal receives the registration response message 1. The registration response 1 comprises NSSAI of network slices supported by at least one AMF entity.

S406, the terminal determines a second AMF entity supporting the network slice corresponding to the service according to the NSSAI of the network slice supported by the at least one AMF entity.

Optionally, the network slice corresponding to the service in the embodiment of the present application is a network slice configured on the terminal, that is, the terminal initiates the service based on information of the network slice configured on the terminal, which is not specifically limited in the embodiment of the present application.

If the second AMF entity is the same as the first AMF entity, that is, the network slice supported by the first AMF entity includes the network slice corresponding to the service, step S407 is executed;

if the second AMF entity is different from the first AMF entity, that is, the network slice supported by the first AMF entity does not include the network slice corresponding to the service, steps S408-S410 are performed.

S407 is the same as step S309, and reference may be made to the embodiment shown in fig. 3 for details, which are not repeated herein.

S408-S410 are the same as steps S310-S312, and reference may be made to the embodiment shown in fig. 3 for details, which are not repeated herein.

In the service session establishment method provided in the embodiment of the application, the terminal may receive the NSSAI of the network slice supported by the at least one AMF entity from the first AMF entity, and further may determine, according to the NSSAI of the network slice supported by the at least one AMF entity, a second AMF entity that supports the network slice corresponding to the service, and establish the service session of the service through the second AMF entity. Therefore, based on the scheme, the terminal can successfully establish the corresponding service session when the NSSAI based on the network slice configured on the terminal initiates the service.

The actions of the terminal in steps S401 to S410 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present application.

The actions of the first AMF entity in steps S401 to S410 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present invention.

Alternatively, it is assumed that the terminal 101 in fig. 1 roams from the HPLMN to the VPLMN, that is, the terminal 101 in fig. 1 is a terminal of a roaming user, the service network is a VPLMN, and the NSRF entity is deployed separately from the AMF entity. When the user of the terminal 101 moves from a company to home, the first AMF entity registered at the company may not support a network slice of video traffic, which may result in the user of the terminal 101 not being able to successfully access the network slice at home to view video. Based on this, the following two session establishment methods are provided in the embodiments of the present application, so that the terminal 101 can successfully establish a corresponding service session in the scenario.

Fig. 5 is a schematic flow chart of a service session establishment method according to an embodiment of the present application. The service session establishing method relates to the interaction among a terminal, an access device, a first AMF entity, a V-NSRF entity, an H-NSRF entity, a second AMF entity, a V-SMF entity, an H-SMF entity and a database entity, and comprises the following steps:

s501, the terminal sends a registration request 1 to the first AMF entity. Accordingly, the first AMF entity receives a registration request 1 from the terminal.

S502, the first AMF entity obtains the subscription data of the terminal from the database entity. Wherein, the data signed by the terminal includes NSSAI of the network slice signed by the terminal.

And S503, the first AMF entity completes the authentication of the terminal and the service network according to the subscription data of the terminal.

S504, after the authentication is successful, the first AMF entity sends NSSAI request to the V-NSRF entity. Accordingly, the NSRF entity receives a NSSAI request from the first AMF entity. The NSSAI request comprises NSSAI of a network slice signed by the terminal, and is used for requesting NSSAI of a network slice corresponding to the network slice signed by the terminal in NSSAI of the network slice in the registration area of the terminal.

And S505, the V-NSRF entity maps the NSSAI of the network slice signed by the terminal with the NSSAI of the network slice in the registration area of the terminal to obtain the NSSAI of the network slice corresponding to the network slice signed by the terminal in the NSSAI of the network slice in the registration area of the terminal.

Optionally, the V-NSRF entity may complete mapping and management of NSSAI of a network slice subscribed to by the terminal and NSSAI of a network slice in a registration area of the terminal according to a preconfigured policy or roaming agreement.

For example, it is assumed that NSSAI of a network slice subscribed to by a terminal in the HPLMN is shown in table two, and NSSAI of a network slice in the registration area of the terminal in the VPLMN is shown in table three:

watch two

NSSAI	Corresponding network slice	Planning bandwidth cap	Planning time delay	……
					1	Slice HA (experience low business)	10Mbps	100ms	……
2	Slice HB (high business experience)	1Gbps	10ms	……

Watch III

NSSAI	Corresponding network slice	Planning bandwidth cap	Planning time delay	……
					100	Slice VA (experience low business)	15Mbps	200ms	……
200	Slice VB (high business experience)	900Mbps	15ms	……
					300	Slice VC (others)	10Mbps	500ms	……

The mapping result of the NSSAI of the network slice subscribed by the terminal and the NSSAI of the network slice in the registration area of the terminal may be as follows:

NSSAI 1——NSSAI 100

NSSAI 2——NSSAI 200

Others——NSSAI 300

that is, in addition to the precise mapping, for example, NSSAI1 of the network slice HA signed by the terminal is mapped with NSSAI 100 of the network slice VA in the registration area of the terminal, NSSAI 2 of the network slice HB signed by the terminal is mapped with NSSAI 200 of the network slice VB in the registration area of the terminal; a default NSSAI-V may also be configured, which may be a default choice when other rules fail to match, such as NSSAI-H being neither 1 nor 2, NSSAI-V is used 300.

It should be noted that the foregoing is only an example to provide one mapping manner, and of course, other mapping manners may also exist, and this is not specifically limited in this embodiment of the application.

S506, the V-NSRF entity sends NSSAI response to the first AMF entity. Accordingly, the first AMF entity receives a NSSAI response from the V-NSRF entity. The NSSAI response includes the NSSAI of the network slice corresponding to the network slice subscribed to the terminal among the NSSAIs of the network slices in the registration area of the terminal.

And S507, the first AMF entity acquires NSSAI of the network slice supported by at least one AMF entity.

Optionally, in this embodiment of the present application, the NSSAI of the network slice supported by at least one AMF entity includes NSSAI of network slices supported by all AMF entities in a registration area of a terminal in a service network of the terminal; or the NSSAI of the network slice supported by the at least one AMF entity includes the NSSAI of the network slice supported by the AMF entity that supports the network slice corresponding to the network slice subscribed to by the terminal in the registration area of the terminal.

For example, it is assumed that three AMF entities are provided in the registration area of the terminal, which are AMF entity 1, AMF entity 2, and AMF entity 3; in the registration area of the terminal, the network slices corresponding to the network slices signed by the terminal comprise a network slice 1, a network slice 3 and a network slice 4; the AMF entity 1 supports a network slice 1, a network slice 2 and a network slice 4; the AMF entity 2 supports a network slice 3 and a network slice 4; AMF entity 3 supports network slice 2, network slice 4 and network slice 5, with the results shown in table four above:

watch four

As can be seen from table four, the AMF entities supporting the network slice corresponding to the network slice subscribed to by the terminal in the registration area of the terminal include AMF entity 1 and AMF entity 2, that is, the network slice supported by AMF entity 1 and the network slice supported by AMF entity 2 may cover the network slice corresponding to the network slice subscribed to by the terminal, and based on this, the first AMF entity may obtain NSSAI of the network slices supported by AMF entity 1 and AMF entity 2. Wherein the NSSAI of the network slice supported by the AMF entity 1 comprises S-NSSAI of the network slice 1, S-NSSAI of the network slice 2 and S-NSSAI of the network slice 4; the NSSAIs of the network slices supported by the AMF entity 2 include S-NSSAI of network slice 3 and S-NSSAI of network slice 4.

Of course, the first AMF entity may also obtain NSSAI of network slices supported by all AMF entities in the terminal registration area, that is, the first AMF entity obtains NSSAI of network slices supported by AMF entity 1, AMF entity 2, and AMF entity 3. Wherein the NSSAI of the network slice supported by the AMF entity 1 comprises S-NSSAI of the network slice 1, S-NSSAI of the network slice 2 and S-NSSAI of the network slice 4; the NSSAIs of the network slices supported by the AMF entity 2 include S-NSSAI of network slice 3 and S-NSSAI of network slice 4; the NSSAIs of the network slices supported by the AMF entity 3 include S-NSSAI of network slice 2, S-NSSAI of network slice 4, and S-NSSAI of network slice 5.

And S508, the first AMF entity sends a registration response 1 to the terminal. Accordingly, the terminal receives the registration response message 1 from the first AMF entity. The registration response 1 includes NSSAI of a network slice supported by at least one AMF entity and NSSAI of a network slice corresponding to a network slice subscribed to by the terminal.

Optionally, the NSSAI of the network slice supported by the at least one AMF entity and the NSSAI of the network slice corresponding to the network slice subscribed by the terminal may also be sent to the terminal through different messages, which is not specifically limited in this embodiment of the present application.

S509, the terminal determines, according to the NSSAI of the network slice supported by the at least one AMF entity, a second AMF entity supporting the network slice corresponding to the service.

Optionally, in this embodiment of the present application, the network slice corresponding to the service is a network slice issued by the network side and corresponding to a network slice signed with the terminal, that is, the terminal initiates the service based on the NSSAI of the network slice issued by the network side and corresponding to the network slice signed with the terminal, so that a problem that session establishment fails because the terminal signs a certain network slice but the terminal is not configured with the S-NSSAI of the network slice corresponding to the network slice is avoided, and a probability of session establishment success is improved.

If the second AMF entity is the same as the first AMF entity, that is, the network slice supported by the first AMF entity includes the network slice corresponding to the service, then step S510 is executed;

if the second AMF entity is different from the first AMF entity, that is, the network slice supported by the first AMF entity does not include the network slice corresponding to the service, steps S511-S513 are performed.

And S510, if the second AMF entity is the same as the first AMF entity, the terminal establishes a service session of the service through the first AMF entity.

And S511, if the second AMF entity is different from the first AMF entity, the terminal sends a registration request 2 to the second AMF entity. Accordingly, the second AMF entity receives a registration request 2 from the terminal.

And S512, the second AMF entity sends a registration response 2 to the terminal. Accordingly, the terminal receives the registration response message 2.

And S513, the terminal establishes a service session of the service through the second AMF entity.

Optionally, in step S510 or S513, since the service session is established through the first AMF entity or the second AMF entity, the service session needs to interact with a Home, H, and SMF in the HPLMN, the V-NSRF entity needs to determine a network slice where the H-SMF is located, and then sends information of the network slice where the H-SMF is located to the corresponding AMF entity to perform a service session establishment procedure. In the embodiment of the present application, the V-NSRF entity may determine the network slice where the H-SMF is located by the following two ways:

firstly, the V-NSRF entity determines the network slice where the H-SMF is located according to the NSSAI of the network slice signed by the terminal in step S505 and the NSSAI of the network slice in the registration area of the terminal;

second, the V-NSRF entity requests the H-NSRF entity for the network slice in which the H-SMF resides.

Of course, the V-NSRF entity may also determine the network slice where the H-SMF is located by other means, which is not specifically limited in this embodiment.

The actions of the terminal in steps S501 to S513 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present application.

The actions of the first AMF entity in steps S501 to S513 may be executed by the processor 201 in the communication device 200 shown in fig. 2 by calling the application program code stored in the memory 203, which is not limited in this embodiment of the present invention.

The embodiment shown in fig. 5 is described by taking an NSSAI originating service of a network slice issued by a terminal on the basis of a network side and signed by the terminal as an example. Optionally, as shown in fig. 6, the terminal may also initiate a service based on the NSSAI of the network slice configured on the terminal, and at this time, the network side does not need to issue the NSSAI of the network slice signed by the terminal. Specifically, the service session establishing method relates to the interaction among a terminal, an access device, a first AMF entity, a V-NSRF entity, an H-NSRF entity, a second AMF entity, a V-SMF entity, an H-SMF entity and a database entity, and comprises the following steps:

S601-S603 are the same as S501-S503, and reference may be made to the embodiment shown in fig. 5 for details, which are not repeated herein.

S604, the first AMF entity obtains NSSAI of the network slice supported by at least one AMF entity.

Step S506 may be referred to for the related description of step S604, and is not repeated herein.

S605, the first AMF entity sends a registration response 1 to the terminal. Accordingly, the terminal receives the registration response message 1 from the first AMF entity. The registration response 1 comprises NSSAI of network slices supported by at least one AMF entity.

S606, the terminal determines a second AMF entity supporting the network slice corresponding to the service according to the information of the network slice supported by the at least one AMF entity.

If the second AMF entity is the same as the first AMF entity, that is, the network slice supported by the first AMF entity includes the network slice corresponding to the service, step S607 is executed;

if the second AMF entity is different from the first AMF entity, that is, the network slice supported by the first AMF entity does not include the network slice corresponding to the service, steps S608 to S710 are performed.

S607 is the same as step S510, and reference may be made to the embodiment shown in fig. 6, which is not repeated herein.

S608-S610 are the same as steps S511-S513, and reference may be made to the embodiment shown in fig. 6 for details, which are not repeated herein.

The actions of the terminal in steps S601 to S610 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present application.

The actions of the first AMF entity in steps S601 to S610 may be executed by the processor 201 in the communication device 200 shown in fig. 2 calling the application program code stored in the memory 203, which is not limited in this embodiment of the present invention.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that the above-mentioned terminal and AMF entity, in order to implement the above-mentioned functions, include corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the terminal and the AMF entity may be divided into the functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

For example, in the case of dividing each functional module by corresponding functions, fig. 7 shows a possible structural diagram of the terminal 70 involved in the above embodiment. The terminal 70 comprises a receiving module 701, a determining module 702 and a establishing module 703. A receiving module 701, configured to receive network slice information from a first AMF entity in a process that the terminal 70 registers to a serving network through the first AMF entity; a determining module 702, configured to determine, according to the network slice information, a second AMF entity supporting a network slice corresponding to the service; the establishing module 703 is configured to establish a service session of a service through the second AMF entity.

Optionally, the service network is a service network of a home of the terminal 70; the network slice corresponding to the service is a network slice subscribed by the terminal 70 in the registration area of the terminal 70. The receiving module 701 is further configured to receive an NSSAI of a network slice subscribed by the terminal 70 from the first AMF entity in the process that the terminal 70 registers to the service network through the first AMF entity.

Optionally, the service network is a service network of a place accessed by the terminal 70; the network slice corresponding to the service is a network slice corresponding to a network slice contracted with the terminal 70 in the registration area of the terminal 70. The receiving module 701 is further configured to receive, from the first AMF entity, NSSAI of a network slice corresponding to a network slice subscribed to by the terminal 70 in the process that the terminal 70 registers in the service network through the first AMF entity.

Optionally, the first AMF entity and the second AMF entity are different AMF entities. At this time, the establishing module 703 is specifically configured to: the traffic session is established through the second AMF entity after the terminal 70 re-registers with the serving network through the second AMF entity.

In the case of dividing the functional modules in an integrated manner, fig. 8 shows a possible structural schematic diagram of the terminal 80 involved in the above embodiment, where the terminal 80 includes: a processing module 802 and a communication module 801. The processing module 802 may be configured to perform operations that can be performed by the determining module 702 and the establishing module 703 in fig. 7; the communication module 801 may be configured to execute operations that can be executed by the receiving module 701 in fig. 7, which may specifically refer to the embodiment shown in fig. 7, and details of the embodiment of the present application are not repeated herein.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the terminal is presented in a form of dividing each functional module corresponding to each function, or the terminal is presented in a form of dividing each functional module in an integrated manner. As used herein, a module may refer to an Application-Specific Integrated Circuit (ASIC), an electronic Circuit, a processor and memory that execute one or more software or firmware programs, an Integrated logic Circuit, and/or other devices that provide the described functionality. In a simple embodiment, those skilled in the art will appreciate that either terminal 70 or terminal 80 may take the form shown in FIG. 2. For example, the receiving module 701, the determining module 702, and the establishing module 703 in fig. 7 may be implemented by the processor 201 and the memory 203 of fig. 2. Specifically, the receiving module 701, the determining module 702, and the establishing module 703 may be executed by the processor 201 calling an application program code stored in the memory 203, which is not limited in this embodiment of the present application. Alternatively, for example, the processing module 802 and the communication module 801 in fig. 8 may be implemented by the processor 201 and the memory 203 in fig. 2. Specifically, the processing module 802 and the communication module 801 may be executed by the processor 201 calling an application program code stored in the memory 203, which is not limited in any way by the embodiment of the present application.

Since the terminal provided in the embodiment of the present application may be configured to execute the service session establishment method, the technical effect obtained by the terminal may refer to the method embodiment, and will not be described herein again.

Alternatively, for example, in the case of dividing each functional module by corresponding functions, fig. 9 shows a possible structural diagram of the AMF entity 90 involved in the above embodiment. The AMF entity 90 includes: an acquisition module 901 and a sending module 902. An obtaining module 901, configured to obtain network slice information in a process that a terminal registers in a service network through the AMF entity 90; a sending module 902, configured to send network slice information to the terminal, where the network slice information is used to establish a service session.

Optionally, the obtaining module 901 is further configured to request, from an NSRF entity in the service network, information of a network slice subscribed by the terminal in the process that the terminal registers in the service network through the AMF entity 90; the sending module 902 is further configured to send information of the network slice subscribed by the terminal to the terminal.

Optionally, the obtaining module 901 is further configured to request an NSSAI of a network slice subscribed by the terminal from a database entity in a home network of the terminal before requesting, from an NSRF entity in the service network, information of the network slice subscribed by the terminal.

Furthermore, the obtaining module 901 is specifically configured to: the NSSAI of the network slice signed by the terminal is sent to an NSRF entity, and the NSSAI of the network slice signed by the terminal is used for requesting the information of the network slice signed by the terminal; information of a network slice to which a terminal from the NSRF entity has subscribed is received.

In the case of dividing the functional modules in an integrated manner, fig. 10 shows a possible structural diagram of the AMF entity 100 involved in the above embodiment, where the AMF entity 100 includes: a processing module 1002 and a communication module 1001. The processing module 1002 is configured to execute the operations that can be executed by the obtaining module 901 in fig. 9; the communication module 1001 may be configured to execute operations that can be executed by the sending module 902 in fig. 9, which may specifically refer to the embodiment shown in fig. 9, and this embodiment is not described herein again.

In this embodiment, the AMF entity is presented in a form of dividing each functional module corresponding to each function, or in a form of dividing each functional module in an integrated manner. As used herein, a module may refer to an Application-Specific Integrated Circuit (ASIC), an electronic Circuit, a processor and memory that execute one or more software or firmware programs, an Integrated logic Circuit, and/or other devices that provide the described functionality. In a simple embodiment, one skilled in the art will recognize that either the AMF entity 90 or the AMF entity 100 may take the form shown in fig. 2. For example, the obtaining module 901 and the sending module 902 in fig. 9 may be implemented by the processor 201 and the memory 203 in fig. 2. Specifically, the obtaining module 901 and the sending module 902 may be executed by the processor 201 calling an application program code stored in the memory 203, which is not limited in this embodiment of the application. Alternatively, for example, the processing module 1002 and the communication module 1001 in fig. 10 may be implemented by the processor 201 and the memory 203 in fig. 2. Specifically, the processing module 1002 and the communication module 1001 may be executed by the processor 201 calling an application program code stored in the memory 203, which is not limited in this embodiment.

Since the AMF entity provided in the embodiment of the present application may be used to execute the service session establishment method, the technical effect obtained by the AMF entity may refer to the method embodiment, and is not described herein again.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a terminal to implement the functions in the foregoing aspects, for example, determine, according to network slice information, a second AMF entity that supports a network slice corresponding to a service. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the terminal. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support an AMF entity to implement the functions referred to in the foregoing aspects, for example, to obtain network slice information. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the AMF entity. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, 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. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for establishing a service session, the method comprising:

in the process that a terminal registers to a service network through a first access and mobile management function (AMF) entity, the terminal receives network slice information from the first AMF entity, wherein the network slice information comprises information of network slices supported by all AMF entities in a registration area of the terminal and network slice information signed by the terminal in the registration area of the terminal;

the terminal determines a second AMF entity supporting a network slice corresponding to the service according to the network slice information;

and the terminal establishes the service session of the service through the second AMF entity.

2. The method according to claim 1, wherein the serving network is a serving network of the terminal home; the network slice corresponding to the service is a network slice signed by the terminal in a registration area of the terminal; the method further comprises the following steps:

and in the process that the terminal registers to the service network through the first AMF entity, the terminal receives network slice selection auxiliary information NSSAI of a network slice signed by the terminal from the first AMF entity.

3. The method according to claim 2, wherein the network slice information includes NSSAI of network slices supported by all AMF entities within the registration area of the terminal; or the network slice information includes NSSAI of a network slice supported by an AMF entity that supports the network slice subscribed by the terminal in the registration area of the terminal.

4. The method according to claim 1, wherein the service network is a service network of a place where the terminal accesses; the network slice corresponding to the service is a network slice corresponding to a network slice signed with the terminal in a registration area of the terminal; the method further comprises the following steps:

and in the process that the terminal is registered to the service network through the first AMF entity, the terminal receives NSSAI of the network slice corresponding to the network slice signed with the terminal from the first AMF entity.

5. The method according to claim 4, wherein the network slice information includes information of network slices supported by all AMF entities within the registration area of the terminal; or the network slice information includes NSSAI of a network slice supported by an AMF entity that supports the network slice corresponding to the network slice subscribed to by the terminal in the registration area of the terminal.

6. The method of claim 1, wherein the network slice corresponding to the service is a network slice configured on the terminal.

7. The method according to any of claims 1-6, wherein the first AMF entity and the second AMF entity are different AMF entities;

the terminal establishes a service session of the service through the second AMF entity, and the service session comprises the following steps:

establishing the traffic session through the second AMF entity after the terminal re-registers with the serving network through the second AMF entity.

8. A method for establishing a service session, the method comprising:

an access and mobile management function (AMF) entity acquires network slice information in the process that a terminal registers to a service network through the AMF entity, wherein the network slice information comprises network slice information signed by the terminal in a registration area of the terminal and information of network slices supported by at least one AMF entity;

and the AMF entity sends the network slice information to the terminal, and the network slice information is used for establishing a service session between the terminal and the AMF supporting the network slice corresponding to the service.

9. The method of claim 8, further comprising:

the AMF entity requests information of a network slice signed by the terminal from a network slice library function NSRF entity in a service network in the process that the terminal is registered to the service network through the AMF entity;

and the AMF entity sends the information of the network slice signed by the terminal to the terminal.

10. The method of claim 9, wherein the terminal is a terminal of a local home subscriber;

the information of the network slice signed by the terminal comprises NSSAI of the network slice in the registration area of the terminal in the network slice selection auxiliary information NSSAI of the network slice signed by the terminal.

11. The method of claim 9, wherein the terminal is a terminal of a roaming user;

the information of the network slice signed by the terminal comprises NSSAI of the network slice corresponding to NSSAI of the network slice signed by the terminal in NSSAI of the network slice in the registration area of the terminal.

12. The method according to claim 11, before the AMF entity requests information of a network slice to which the terminal is subscribed from a NSRF entity in the service network, further comprising:

the AMF entity requests NSSAI of a network slice signed by the terminal from a database entity in a home network of the terminal;

the AMF entity requests the NSRF entity for information of a network slice subscribed by the terminal, including:

the AMF entity sends NSSAI of the network slice signed by the terminal to the NSRF entity, wherein the NSSAI of the network slice signed by the terminal is used for requesting the information of the network slice signed by the terminal;

the AMF entity receives information of a network slice to which the terminal has subscribed from the NSRF entity.

13. A terminal, characterized in that the terminal comprises: the device comprises a receiving module, a determining module and an establishing module;

the receiving module is configured to receive network slice information from a first access and mobility management function (AMF) entity in a process that a terminal registers in a service network through the AMF entity, where the network slice information includes information of network slices supported by all AMF entities in a registration area of the terminal and network slice information subscribed by the terminal in the registration area of the terminal;

the determining module is configured to determine, according to the network slice information, a second AMF entity supporting a network slice corresponding to a service;

the establishing module is configured to establish a service session of the service through the second AMF entity.

14. The terminal of claim 13, wherein the serving network is a serving network of a home of the terminal; the network slice corresponding to the service is a network slice signed by the terminal in a registration area of the terminal;

the receiving module is further configured to receive network slice selection assistance information NSSAI of a network slice subscribed by the terminal from the first AMF entity in a process in which the terminal registers to the service network through the first AMF entity.

15. The terminal of claim 14, wherein the network slice information includes NSSAI of network slices supported by all AMF entities within a registration area of the terminal; or the network slice information includes NSSAI of a network slice supported by an AMF entity that supports the network slice subscribed by the terminal in the registration area of the terminal.

16. The terminal of claim 13, wherein the service network is a service network of a place where the terminal accesses; the network slice corresponding to the service is a network slice corresponding to a network slice signed with the terminal in a registration area of the terminal;

the receiving module is further configured to receive, from the first AMF entity, an NSSAI of a network slice corresponding to the network slice subscribed to by the terminal in a process in which the terminal registers in the service network through the first AMF entity.

17. The terminal according to claim 16, wherein the network slice information includes information of network slices supported by all AMF entities within a registration area of the terminal; or the network slice information includes NSSAI of a network slice supported by an AMF entity that supports the network slice corresponding to the network slice subscribed to by the terminal in the registration area of the terminal.

18. The terminal of claim 13, wherein the network slice corresponding to the service is a network slice configured on the terminal.

19. A terminal according to any of claims 13-18, characterised in that the first AMF entity and the second AMF entity are different AMF entities;

the establishing module is specifically configured to:

20. An access and mobility management function, AMF, entity, characterized in that the AMF entity comprises: the device comprises an acquisition module and a sending module;

the acquisition module is used for acquiring network slice information in the process that the terminal registers in a service network through the AMF entity, wherein the network slice information comprises network slice information signed by the terminal in a registration area of the terminal and information of network slices supported by at least one AMF entity;

the sending module is configured to send the network slice information to the terminal, where the network slice information is used for establishing a service session between the terminal and an AMF supporting a network slice corresponding to a service.

21. The AMF entity of claim 20,

the obtaining module is further configured to request, from a network slice library function NSRF entity in a service network, information of a network slice subscribed by the terminal in a process in which the terminal registers in the service network through the AMF entity;

the sending module is further configured to send information of the network slice signed by the terminal to the terminal.

22. The AMF entity of claim 21, wherein the terminal is a terminal of a local home subscriber;

23. The AMF entity of claim 21, wherein the terminal is a terminal of a roaming user;

24. The AMF entity of claim 23,

the obtaining module is further configured to request an NSSAI of the network slice subscribed by the terminal from a database entity in a home network of the terminal before the NSRF entity in the service network requests information of the network slice subscribed by the terminal;

the acquisition module is specifically configured to:

transmitting NSSAI of the network slice signed by the terminal to the NSRF entity, wherein the NSSAI of the network slice signed by the terminal is used for requesting information of the network slice signed by the terminal;

receiving information of a network slice to which the terminal has subscribed from the NSRF entity.