WO2019076244A1 - 会话建立方法、设备及系统 - Google Patents

会话建立方法、设备及系统 Download PDF

Info

Publication number
WO2019076244A1
WO2019076244A1 PCT/CN2018/109971 CN2018109971W WO2019076244A1 WO 2019076244 A1 WO2019076244 A1 WO 2019076244A1 CN 2018109971 W CN2018109971 W CN 2018109971W WO 2019076244 A1 WO2019076244 A1 WO 2019076244A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdn connection
entity
nssai
mobility management
network slice
Prior art date
Application number
PCT/CN2018/109971
Other languages
English (en)
French (fr)
Inventor
景昊
宗在峰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22165511.1A priority Critical patent/EP4096303B1/en
Priority to EP18868000.3A priority patent/EP3694257B1/en
Priority to KR1020207012625A priority patent/KR102308350B1/ko
Priority to RU2020115877A priority patent/RU2765987C2/ru
Priority to JP2020541843A priority patent/JP7015931B2/ja
Publication of WO2019076244A1 publication Critical patent/WO2019076244A1/zh
Priority to US16/847,357 priority patent/US11589270B2/en
Priority to US18/159,275 priority patent/US12108289B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00222—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between different packet switched [PS] network technologies, e.g. transferring data sessions between LTE and WLAN or LTE and 5G
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a session establishment method, device, and system.
  • a dedicated core network is a private network defined by the 3rd Generation Partnership Project (3GPP) in the fourth generation (4th generation, 4G) for serving specific types of services;
  • Slice is an upgraded version of DCN defined by 3GPP in 5rd generation (5G). It is a logically isolated network for supporting specific network capabilities and network characteristics. It can be end-to-end (E2E). Including the entire network, or part of the network function shared among multiple network slices, is a key technology to meet the 3G mobile communication technology proposed by 3GPP regarding network differentiation requirements.
  • the difference between network slicing and DCN is mainly: one DCN is a private network, there is no association between DCNs, the terminal can only access one DCN; and multiple network slices can share a set of access and mobility management functions (access And mobility management function (AMF) entity, the terminal can simultaneously access multiple network slices sharing the same group of AMF entities.
  • AMF access And mobility management function
  • the network slice selection assistance information (NSSAI) is introduced in the network slice.
  • 5GC 5G core network
  • the terminal provides the requested NSSAI, and the network selects the terminal according to the NSSAI.
  • the network determines the NSSAI that the terminal is allowed to access according to the NSSAI requested by the terminal, that is, Allowed NSSAI.
  • a packet data network (PDN) connection is required in the DCN
  • an access point name (APN) parameter is required
  • PDU protocol data unit
  • a data network name (DNN) and a single NSSAI are required, although in the existing protocol, the APN and the DNN are equivalent, but the terminal is evolved from the DCN supporting the packet.
  • EPC core network
  • the embodiment of the present application provides a session establishment method, device, and system, so that when a terminal switches from an EPC supporting a DCN to a 5GC supporting a network slice, a PDU session can be established in a network slice of the 5GC according to the selected S-NSSAI.
  • the embodiment of the present application provides the following technical solutions:
  • a method for establishing a session includes: acquiring, by a first mobility management entity, information about a PDN connection of a packet data network established when a terminal accesses a packet core network EPC; the first mobility management entity according to the PDN The information of the connection, the single network slice selection auxiliary information S-NSSAI of the network slice corresponding to the PDN connection, and the S-NSSAI of the corresponding network slice of the PDN connection is used to indicate the network slice of the packet data unit PDU session.
  • the first mobile management entity or the second mobility management entity receives the S-NSSAI of the network slice corresponding to the PDN connection, because the first mobility management entity can obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the session establishment method provided by the embodiment of the present application.
  • the PDU session may be established in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the method further comprises: the first mobility management entity acquiring information of the second mobility management entity.
  • the first mobility management entity in the embodiment of the present application may also be referred to as an initial mobility management entity, and the second mobility management entity may also be referred to as a target mobility management entity, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity acquires the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, including: the first mobility management entity is connected according to the PDN
  • the information determines the S-NSSAI of the network slice corresponding to the PDN connection.
  • the information of the PDN connection may include, for example, the access point name APN corresponding to the PDN connection or the information of the control plane function entity corresponding to the PDN connection, which is not specifically limited in this embodiment.
  • the PDN connection information includes an access point name APN corresponding to the PDN connection; the first mobility management entity determines, according to the information of the PDN connection, a network slice corresponding to the PDN connection.
  • the S-NSSAI includes: the first mobility management entity determines the S-NSSAI of the network slice corresponding to the PDN connection according to the APN and the correspondence between the pre-configured APN and the S-NSSAI.
  • the correspondence between the pre-configured APN and the S-NSSAI includes a one-to-many relationship between the APN and the S-NSSAI; the first mobility management entity according to the APN, and the pre-configured Corresponding relationship between the APN and the S-NSSAI, determining the S-NSSAI of the network slice corresponding to the PDN connection, including: the first mobility management entity according to the pre-configured APN and S-NSSAI in a one-to-many relationship At least one of a priority of the NSSAI, load information of the network slice indicated by the each S-NSSAI, and an NSSAI supported by the set of mobility management entities configured in the first mobility management entity, and the APN and the pre-configuration
  • the one-to-many relationship between the APN and the S-NSSAI determines the S-NSSAI of the network slice corresponding to the PDN connection.
  • the information about the PDN connection includes information about a control plane function entity corresponding to the PDN connection; the first mobility management entity determines, according to the information of the PDN connection, a network corresponding to the PDN connection
  • the sliced S-NSSAI includes: the first mobility management entity determines, according to the information of the control plane function entity, the S-NSSAI of the network slice corresponding to the PDN connection.
  • the information of the PDN connection includes information about a control plane function entity corresponding to the PDN connection; and the first mobility management entity according to the information of the PDN connection, Acquiring the S-NSSAI of the network slice corresponding to the PDN connection, comprising: the first mobility management entity sending a request message to the control plane function entity according to the information of the control plane function entity, where the request message is used to request to obtain the PDN connection S-NSSAI of the corresponding network slice; the first mobility management entity receives the S-NSSAI of the network slice corresponding to the PDN connection from the control plane function entity.
  • the first mobility management entity acquires the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, and the first mobility management entity sends the PDN connection information to the network storage function entity.
  • the first mobility management entity receives the S-NSSAI of the network slice corresponding to the PDN connection from the network storage function entity. That is, in the embodiment of the present application, the first mobility management entity may obtain the S-NSSAI of the network slice corresponding to the PDN connection from the network storage function entity.
  • the first mobility management entity acquires information about the PDN connection established when the terminal accesses the EPC, including: the first mobility management entity receives the PDN connection from the third mobility management entity in the EPC. information. That is to say, in the embodiment of the present application, the first mobility management entity may obtain the information of the PDN connection from the third mobility management entity in the EPC.
  • the information of the control plane function entity includes a protocol IP address or a full domain name FQDN of the interconnection between the networks of the control plane function entity.
  • the first mobility management entity acquires the information of the second mobility management entity, including: the first mobility management entity acquiring the S-NSSAI according to the network slice corresponding to the PDN connection. Information of the second mobility management entity.
  • the first mobility management entity obtains information about the second mobility management entity according to the S-NSSAI of the network slice corresponding to the PDN connection, in which one network slice instance may be included in the network slice.
  • the first mobility management entity determines, according to the information of the PDN connection, the network slice instance corresponding to the PDN connection; the first mobility management entity determines, according to the S-NSSAI of the network slice corresponding to the PDN connection and the information of the network slice instance.
  • Information of the second mobility management entity that is to say, in the embodiment of the present application, the information of the second mobility management entity may be determined by the first mobility management entity according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity acquires information about the second mobility management entity according to the S-NSSAI of the network slice corresponding to the PDN connection, including: the first mobility management entity selects a function NSSF entity to the network slice Sending an S-NSSAI of the network slice corresponding to the PDN connection, where the S-NSSAI of the corresponding network slice of the PDN connection is used to determine information of the second mobility management entity; the first mobility management entity receives the first part from the NSSF entity Second, the information of the mobile management entity. That is, in the embodiment of the present application, the information of the second mobility management entity may be determined by the NSSF entity according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity acquires an S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection; and the first mobility management entity acquires the second mobility
  • the information of the management entity includes: the first mobility management entity sends a slice selection request message to the NSSF entity, where the slice selection request message carries the information of the PDN connection, where the information of the PDN connection is used to determine the information of the second mobility management entity.
  • the first mobility management entity receives information of the candidate mobility management entity set from the NSSF entity and the S-NSSAI of the network slice corresponding to the PDN connection; the first mobility management The entity selects the second mobility management entity from the set of candidate mobility management entities according to the information of the candidate mobility management entity set. That is, in the embodiment of the present application, the information of the S-NSSAI of the network slice corresponding to the PDN connection and the candidate mobility management entity set where the second mobility management entity is located may be determined by the NSSF entity.
  • the first mobility management entity acquires an S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection; and the first mobility management entity acquires the second mobility.
  • the information of the management entity includes: the first mobility management entity sends a slice selection request message to the NSSF entity, where the slice selection request message carries the information of the PDN connection, where the information of the PDN connection is used to determine the information of the second mobility management entity.
  • An S-NSSAI of the network slice corresponding to the PDN connection; the first mobility management entity receives information of the S-NSSAI of the network slice corresponding to the PDN connection of the NSSF entity and the second mobility management entity. That is, in the embodiment of the present application, the information of the S-NSSAI and the second mobility management entity of the network slice corresponding to the PDN connection may be determined by the NSSF entity.
  • the first mobility management entity is different from the second mobility management entity; the method further includes: the first mobility management entity sending, to the second mobility management entity, a network slice corresponding to the PDN connection S-NSSAI.
  • the first mobility management entity sends the S-NSSAI of the network slice corresponding to the PDN connection to the second mobility management entity, where the first mobility management entity sends the The second mobility management entity sends the S-NSSAI of the network slice corresponding to the PDN connection. That is, it can be rerouted to the second mobility management entity by the access device.
  • the method further includes: the second mobility management entity sending a registration accept message to the terminal; the second mobility management entity receiving a PDU session establishment request from the terminal, the PDU session establishment request And establishing a PDU session in the network slice corresponding to the PDN connection; the second mobility management entity establishes a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal, the registration accept message carrying the PDN Connecting the S-NSSAI of the corresponding network slice; the first mobility management entity receives a PDU session establishment request from the terminal, the PDU session establishment request carrying the S-NSSAI of the network slice corresponding to the PDN connection; the first mobility management entity Establishing a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection. Based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal; the first mobility management entity receiving a PDU session establishment request from the terminal, the PDU session establishment request carrying the S-NSSAI of the network slice requested by the terminal and the APN corresponding to the PDN connection requested by the terminal; the S-NSSAI and the pre-storage of the network slice requested by the terminal If the S-NSSAI of the corresponding network slice of the PDN connection is the same, and the APN corresponding to the PDN connection requested by the terminal is the same as the APN corresponding to the PDN connection, the first mobility management entity according to the network slice corresponding to the PDN connection The S-NSSAI establishes a PDU session in the network slice corresponding to the PDN connection. Based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal; the first mobility management entity receiving a PDU session establishment request from the terminal, the PDU session establishment request carrying information of the PDN connection; the first mobility management entity establishes in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection PDU session.
  • the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • a second aspect provides a method for establishing a session, the method includes: the terminal sending a registration request message to the first mobility management entity, where the registration request message carries an identifier of the terminal, where the identifier of the terminal is used to obtain subscription data of the terminal,
  • the subscription data includes information about a PDN connection of the packet data network that has been established when the terminal accesses the packet core network EPC; the terminal receives a registration accept message, and the registration accept message carries a single network of the network slice corresponding to the PDN connection.
  • the slice selection assistance information S-NSSAI the terminal sends a packet data unit PDU session establishment request, the PDU session establishment request carries an S-NSSAI of the network slice corresponding to the PDN connection, and the PDU session establishment request is used to request a correspondence in the PDN connection A PDU session is established in the network slice.
  • the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the registration accept message also carries information of the PDN connection that allows the handover; the method further includes: releasing, by the terminal, the PDN connection information that is allowed to be switched, releasing the EPC, except for allowing the handover All PDN connections except the PDN connection. This saves system resources.
  • a method for establishing a session comprising: receiving, by a second mobility management entity, a network slice corresponding to a packet data network PDN that has been established when a terminal of the first mobility management entity accesses the packet core network EPC Single network slice selection assistance information S-NSSAI; the second mobility management entity sends a registration accept message to the terminal; the second mobility management entity receives a packet data unit PDU session establishment request from the terminal, the PDU session establishment request is for request Establishing a PDU session in the network slice corresponding to the PDN connection; the second mobility management entity establishes a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the session establishment method provided by the embodiment of the present application, after the second mobility management entity can receive the S-NSSAI of the network slice corresponding to the PDN connection from the first mobility management entity, and after receiving the PDU session establishment request from the terminal, Establishing a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • a first mobility management entity having the functionality to implement the method described in the first aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a first mobility management entity including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the first mobility management entity is running, the processor executes the computer stored by the memory Executing an instruction to cause the first mobility management entity to perform the session establishment method as described in any of the first aspects above.
  • a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the session establishment described in any of the above first aspects method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the session establishment method of any of the above first aspects.
  • a chip system comprising a processor, configured to support the first mobility management entity to implement the functions involved in the foregoing aspects, for example, to support the first mobility management entity to acquire the PDN according to the information of the PDN connection.
  • a single network slice selection auxiliary information S-NSSAI that connects the corresponding network slice.
  • the chip system further includes a memory for storing necessary program instructions and data of the first mobility management entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a terminal having the function of implementing the method of the first aspect described above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a tenth aspect provides a terminal, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the terminal is running, the processor executes the computer execution instruction stored in the memory to enable the terminal to execute A session establishing method as described in any of the above second aspects.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the session of any of the above second aspects Establish a method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the session establishment method of any of the above second aspects.
  • a chip system comprising a processor for supporting a terminal to implement the functions involved in the foregoing aspects, such as supporting a terminal to send a packet data unit PDU session establishment request, the PDU session establishment request carrying The PDN connects to the S-NSSAI of the corresponding network slice, and the PDU session establishment request is used to request to establish a PDU session in the network slice corresponding to the PDN connection.
  • the chip system further comprises a memory for storing necessary program instructions and data of the terminal.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a second mobility management entity having the functionality to implement the method described in the third aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a second mobility management entity including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the second mobility management entity is running, the processor executes the memory storage The computer executes the instructions to cause the first mobility management entity to perform the session establishment method as described in any of the above third aspects.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the session of any of the above third aspects Establish a method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the session establishment method of any of the above third aspects.
  • a chip system comprising a processor, configured to support a second mobility management entity to implement the functions involved in the foregoing aspects, for example, supporting a network slice corresponding to the second mobility management entity according to the PDN connection.
  • the S-NSSAI establishes a PDU session in the network slice corresponding to the PDN connection.
  • the chip system further includes a memory for storing necessary program instructions and data of the second mobility management entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a session establishment system includes a first mobility management entity and a second mobility management entity, where the first mobility management entity is configured to acquire when the terminal accesses the packet core network EPC.
  • Information of the PDN connection of the packet data network the first mobility management entity is further configured to: after obtaining the single network slice selection auxiliary information S-NSSAI of the network slice corresponding to the PDN connection, according to the information of the PDN connection, to the second The mobility management entity sends an S-NSSAI of the network slice corresponding to the PDN connection, the S-NSSAI of the corresponding network slice of the PDN connection is used to indicate a network slice that establishes a packet data unit PDU session; and the second mobility management entity is configured to receive The S-NSSAI of the network slice corresponding to the PDN connection from the first mobility management entity; the second mobility management entity is further configured to: after sending the registration accept message to the terminal, receive the packet data unit PDU session establishment request from the terminal And establishing a
  • a method for establishing a session includes: a control plane function entity determining a single network slice selection auxiliary information S-NSSAI of a network slice corresponding to the session; and the control plane function entity is configured to slice the network corresponding to the session.
  • the S-NSSAI is stored in the user data management entity; the first mobility management entity obtains the S-NSSAI of the network slice corresponding to the session from the user data management entity, and the S-NSSAI of the network slice corresponding to the session is used to indicate that the session is established.
  • Network slice
  • the first mobility management entity or the second mobility management entity may be configured according to the network corresponding to the session, because the first mobility management entity may acquire the S-NSSAI of the network slice corresponding to the session from the user data management entity.
  • the sliced S-NSSAI establishes a session in the network slice corresponding to the session. That is to say, based on the scheme, when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • control plane function entity determines the S-NSSAI of the network slice corresponding to the session, and the control plane function entity determines one of the S-NSSAIs supported by the control plane function entity as the session correspondence.
  • the network is sliced by S-NSSAI.
  • the method further includes: the first mobility management entity acquiring information of the second mobility management entity.
  • the first mobility management entity in the embodiment of the present application may also be referred to as an initial mobility management entity, and the second mobility management entity may also be referred to as a target mobility management entity, which is not specifically limited in this embodiment of the present application.
  • the manner in which the first mobility management entity acquires the information of the second mobility management entity may refer to the related description in any one of the possible design of the ninth possible design of the first aspect, the seventh possible design of the first aspect, I will not repeat them here.
  • the first mobility management entity is different from the second mobility management entity; the method further includes: the first mobility management entity sending, to the second mobility management entity, the S of the network slice corresponding to the session -NSSAI.
  • the first mobility management entity sends the S-NSSAI of the network slice corresponding to the session to the second mobility management entity, including: the first mobility management entity moves to the second mobile device by using the access device
  • the management entity sends the S-NSSAI of the network slice corresponding to the session. That is, it can be rerouted to the second mobility management entity by the access device.
  • the method further includes: the second mobility management entity sends a registration accept message to the terminal; the second mobility management entity receives a session establishment request from the terminal, the session establishment request is used to request A session is established in the network slice corresponding to the session; the second mobility management entity establishes a session in the network slice corresponding to the session according to the S-NSSAI of the network slice corresponding to the session. That is to say, based on the scheme, when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal, the registration accept message carrying the session correspondence S-NSSAI of the network slice; the first mobility management entity receives a session establishment request from the terminal, the session establishment request carrying an S-NSSAI of the network slice corresponding to the session; the first mobility management entity corresponding to the session The S-NSSAI of the network slice establishes a session in the network slice corresponding to the session.
  • the network when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal; the first mobility management entity receiving a session establishment request of the terminal, the session establishment request carrying the S-NSSAI of the network slice requested by the terminal and the session information corresponding to the session requested by the terminal; the S-NSSAI of the network slice requested by the terminal and the session stored in advance If the S-NSSAI of the corresponding network slice is the same, and the session information corresponding to the session requested by the terminal is the same as the session information corresponding to the session, the first mobility management entity is configured according to the S-NSSAI of the network slice corresponding to the session. A session is established in the network slice corresponding to the session.
  • the network when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the first mobility management entity is the same as the second mobility management entity; the method further includes: the first mobility management entity sending a registration accept message to the terminal; the first mobility management entity receiving The session establishment request of the terminal, the session establishment request carries the information of the session; the first mobility management entity establishes a session in the network slice corresponding to the session according to the S-NSSAI of the network slice corresponding to the session. That is to say, based on the scheme, when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the twenty-first aspect provides a session establishment system, where the session establishment system includes a control plane function entity and a first mobility management entity, and the control plane function entity is configured to determine a single network slice selection auxiliary information of the network slice corresponding to the session.
  • S-NSSAI and storing the S-NSSAI of the network slice corresponding to the session to the user data management entity; the first mobility management entity, configured to obtain the S-NSSAI of the network slice corresponding to the session from the user data management entity
  • the S-NSSAI of the network slice corresponding to the session is used to indicate a network slice that establishes a session.
  • a method for establishing a session includes: the control plane function entity acquires information about a PDN connection of a packet data network that has been established when the terminal accesses the packet core network EPC, and a network slice corresponding to the PDN connection.
  • the control plane function entity sends the information of the PDN connection to the network storage function entity and the S-NSSAI of the network slice corresponding to the PDN connection, which is connected by the first mobility management entity according to the PDN
  • the information is obtained from the network storage function entity, and the S-NSSAI of the network slice corresponding to the PDN connection is used, where the S-NSSAI of the network slice corresponding to the PDN connection is used to indicate that the network slice of the packet data unit PDU session is established.
  • the first AMF entity may obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, so the first AMF entity may receive the handover request from the MME according to the PDN connection.
  • the S-NSSAI of the network slice acquires the second AMF entity information, and then the PDU session can be established in the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • control plane function entity sends the information of the PDN connection to the network storage function entity and the S-NSSAI of the network slice corresponding to the PDN connection, including: the control plane function entity is in the process of establishing the PDN connection. Or, during the establishment of the PDU session, the information about the PDN connection and the S-NSSAI of the network slice corresponding to the PDN connection are sent to the network storage function entity.
  • the session establishing method provided by the embodiment of the present application may further include: the control plane function entity sends the PDN connection information to the third mobility management entity in the EPC, where the third mobility management entity The first mobility management entity sends the information of the PDN connection. Based on the scheme, the first mobility management entity can acquire information of the PDN connection.
  • the control plane function entity acquires the single network slice selection assistance information S-NSSAI of the network slice corresponding to the PDN connection, and the control plane function entity determines the S-NSSAI corresponding to the PDU session as the PDU.
  • the S-NSSAI of the network slice corresponding to the PDN connection when the session is switched to the EPC. Based on the solution, the control plane function entity can obtain the S-NSSAI of the network slice corresponding to the PDN connection.
  • a control plane functional entity is provided, the control surface functional entity having the function of implementing the method described in the third aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a control plane functional entity comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the control plane function entity is running, the processor executes the computer stored in the memory Executing an instruction to cause the first mobility management entity to perform the session establishment method as described in any of the above third aspects.
  • a twenty-fifth aspect a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method of any of the above third aspects Session establishment method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the session establishment method of any of the above third aspects.
  • a chip system comprising a processor, configured to support a control plane function entity to implement the functions involved in the foregoing aspects, for example, supporting a control plane function entity according to a network slice corresponding to the PDN connection S-NSSAI establishes a PDU session in the network slice corresponding to the PDN connection.
  • the chip system further comprises a memory for storing program instructions and data necessary for the control plane function entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the twenty-eighth aspect provides a session establishment system, where the session establishment system includes: a control plane function entity and a first mobility management entity; and a control plane function entity, configured to acquire an established manner when the terminal accesses the packet core network EPC.
  • the control plane function entity is further configured to send the PDN connection information to the network storage function entity and the PDN connection correspondingly
  • a mobility management entity configured to receive an S-NSSAI of a network slice corresponding to the PDN connection from the network storage function entity.
  • the twenty-ninth aspect provides a session establishing method, the method comprising: the network storage function entity receiving first information of a user plane entity corresponding to a packet data network PDN connection from a first mobility management entity; the network storage function entity according to The first information determines a single network slice selection assistance information S-NSSAI of the first network slice corresponding to the PDN connection; the network storage function entity sends the S-NSSAI of the first network slice to the first mobility management entity.
  • the first mobility management entity may acquire the S-NSSAI of the first network slice corresponding to the PDN connection according to the first information of the user plane entity corresponding to the PDN connection.
  • the first mobility management entity may acquire the information of the second mobility management entity according to the S-NSSAI of the first network slice corresponding to the PDN connection, and may further slice the corresponding network.
  • Establish a PDU session That is to say, based on the scheme, when the terminal switches from the EPC supporting the DCN to the 5GC supporting the network slice, the corresponding session can be established and established in the network slice of the 5GC according to the selected S-NSSAI.
  • the method before the network storage function entity receives the first information of the user plane entity corresponding to the PDN of the first mobility management entity, the method further includes: the network storage function entity receiving the entity from the user plane The first information and the S-NSSAI of the first network slice corresponding to the first information.
  • the network storage function may store the correspondence between the first information and the S-NSSAI of the first network slice.
  • the corresponding relationship may be queried, and the S-NSSAI of the first network slice corresponding to the first information is determined, which is not specifically limited in this embodiment of the present application.
  • a method for establishing a session comprising: acquiring, by a user plane entity, information of the user plane entity and a single network slice selection auxiliary information S-NSSAI of the network slice corresponding to the information of the user plane entity;
  • the user plane entity sends the information of the user plane entity to the network storage function entity and the S-NSSAI of the network slice, and the first mobility management entity stores from the network according to the first information of the user plane entity corresponding to the packet data network PDN.
  • the S-NSSAI of the first network slice corresponding to the PDN connection is obtained in the function entity.
  • the first mobility management entity may acquire the S-NSSAI of the first network slice corresponding to the PDN connection according to the first information of the user plane entity corresponding to the PDN connection. Therefore, after receiving the handover request or the registration request, the first mobility management entity may acquire the information of the second mobility management entity according to the S-NSSAI of the first network slice corresponding to the PDN connection, and may further slice the corresponding network.
  • Establish a PDU session That is to say, based on the scheme, when the terminal switches from the EPC supporting the DCN to the 5GC supporting the network slice, the corresponding session can be established and established in the network slice of the 5GC according to the selected S-NSSAI.
  • the user plane entity sends the information of the user plane entity to the network storage function entity and the S-NSSAI of the network slice, where the user plane entity stores the functional entity to the network at the user plane entity.
  • the information of the user plane entity and the S-NSSAI of the network slice are sent to the network storage function entity.
  • a network storage function entity having the function of implementing the method described in the twenty-ninth aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a network storage function entity comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the network storage function entity is running, the processor executes the computer stored in the memory The instruction is executed to cause the network storage function entity to perform the session establishment method according to any one of the twenty-ninth aspects described above.
  • a thirty-third aspect a network storage function entity, comprising: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute the twenty-ninth aspect as described above according to the instruction The session establishment method described in any one of the preceding claims.
  • a thirty-fourth aspect a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform any of the twenty-ninth aspects described above The session establishment method described.
  • a thirty-fifth aspect a computer program product comprising instructions for causing a computer to perform the session establishment method of any one of the twenty-ninth aspects described above, when run on a computer.
  • a device for example, the device may be a chip system
  • the device comprising a processor for supporting a network storage function entity to implement the functions involved in the twenty-ninth aspect, for example
  • the first information determines an S-NSSAI of the first network slice corresponding to the PDN connection.
  • the apparatus further includes a memory for storing program instructions and data necessary for the network storage function entity.
  • the device When the device is a chip system, it may be composed of a chip, and may also include a chip and other discrete devices.
  • a user plane entity having the function of implementing the method of the above-described thirtieth aspect. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a user plane entity comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the user plane entity is running, the processor executes the computer execution instruction stored in the memory
  • the user plane entity performs the session establishment method according to any one of the above-mentioned 30th aspects.
  • a user plane entity comprising: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute according to the instruction according to the thirtieth aspect A method of session establishment as described.
  • a computer readable storage medium storing instructions, when executed on a computer, causing the computer to perform the method of any of the above Session establishment method.
  • a computer program product comprising instructions for causing a computer to perform the session establishment method of any of the above-described thirtieth aspects when executed on a computer.
  • a device for example, the device may be a chip system
  • the device comprising a processor for supporting a user plane entity to implement the functions involved in the thirtieth aspect, for example according to the first Information, determining the S-NSSAI of the first network slice corresponding to the PDN connection.
  • the apparatus further includes a memory for storing program instructions and data necessary for the user plane entity.
  • the device is a chip system, it may be composed of a chip, and may also include a chip and other discrete devices.
  • a session establishment system includes: a first mobility management entity and a network storage function entity; the first mobility management entity, configured to send a PDN connection corresponding to the network storage function entity The first information of the user plane entity; the network storage function entity is configured to receive the first information from the first mobility management entity; the network storage function entity is further configured to determine the PDN connection according to the first information a single network slice selection auxiliary information S-NSSAI corresponding to the first network slice; the network storage function entity is further configured to send the S-NSSAI of the first network slice to the first mobility management entity; the first mobility management entity And for receiving the S-NSSAI of the first network slice from the network storage function entity.
  • the system further includes a user plane entity, and the user plane entity is configured to send the first information and the S- of the first network slice corresponding to the first information to the network storage function entity.
  • FIG. 1 is a schematic diagram of an existing 4G network and 5G network interworking architecture
  • FIG. 2 is a schematic structural diagram of a session establishment system according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart 1 of a session establishment method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart 2 of a session establishing method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart 3 of a session establishing method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart 4 of a session establishing method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a first mobility management entity according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a second mobility management entity according to an embodiment of the present application.
  • FIG. 11 is another schematic structural diagram of a session establishment system according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart 5 of a session establishing method according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart 6 of a session establishing method according to an embodiment of the present disclosure.
  • FIG. 14 is another schematic structural diagram of a session establishment system according to an embodiment of the present application.
  • 15 is a schematic flowchart 7 of a session establishment method according to an embodiment of the present application.
  • 16 is a schematic flowchart 8 of a session establishing method according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a control plane function entity according to an embodiment of the present application.
  • FIG. 18 is another schematic structural diagram of a session establishment system according to an embodiment of the present application.
  • FIG. 19 is a schematic flowchart nin of a session establishing method according to an embodiment of the present disclosure.
  • 20 is a schematic flowchart 10 of a session establishment method according to an embodiment of the present application.
  • FIG. 21 is a schematic flowchart 11 of a session establishing method according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram of a network storage function entity according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram of a user plane entity according to an embodiment of the present application.
  • NSSAI includes multiple S-NSSAIs.
  • S-NSSAI consists of a service type (slice/service type, SST) and a slice differentiator (SD).
  • SST includes standardization and operator-defined types; SD is optional information supplementing SST to distinguish multiple network slices of the same SST.
  • SST includes standardization and operator-defined types; SD is optional information supplementing SST to distinguish multiple network slices of the same SST.
  • the types and effects of NSSAI defined in the 23.501 standard are shown in Table 1.
  • FIG. 1 it is a schematic diagram of an existing 4G network and 5G network interworking architecture.
  • the 4G network and the 5G network share a user plane function (UPF) entity + PDN gateway user plane function (PGW-U) entity, and a session management function (SMF) entity + PDN gateway control plane function (PGW-C) entity, policy control function (PCF) entity + policy and charging rules function (PCRF) entity, home subscriber Home subscriber server (HSS) + unified data management (UDM) entity.
  • UPF user plane function
  • PGW-U PDN gateway user plane function
  • SMF session management function
  • PGW-C PDN gateway control plane function
  • PCF policy control function
  • PCF policy and charging rules function
  • HSS home subscriber Home subscriber server
  • UDM unified data management
  • UPF is the user plane function of the 5G network
  • PGW-U is the gateway user plane function of the 4G network corresponding to the UPF
  • SMF is the session management function of the 5G network
  • PGW-C is the corresponding to the SMF.
  • the PCF is the policy control function of the 5G network
  • the PCRF is the policy charging rule function of the 4G network corresponding to the PCF.
  • the HSS+UDM entity is referred to as a user data management entity
  • the PGW-C entity + SMF entity is referred to as a control plane functional entity
  • the UPF entity + PGW-U entity is referred to as User plane entities are described here in a unified manner, and are not described here.
  • the network device after the above-mentioned connection may also use other names, which is not specifically limited in this embodiment of the present application.
  • the above-mentioned 4G network and 5G network interworking architecture may further include a Mobility Management Entity (MME) and a Serving Gateway (SGW) in a 4G network, and a 5G network.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the terminal accesses the 4G network through an evolved universal terrestrial radio access network (E-UTRAN) device, and the terminal passes the next generation radio access network (NG-RAN) device. Access to 5G networks.
  • the E-UTRAN device communicates with the MME through the S1-MME interface, the E-UTRAN device communicates with the SGW through the S1-U interface, the MME communicates with the SGW through the S11 interface, and the MME communicates with the user data management entity through the S6a interface, and the MME passes the N26 interface.
  • the SGW communicates with the PGW-U entity + UPF entity through the S5-U interface
  • the SGW communicates with the PGW-C entity + SMF entity through the S5-C interface
  • the PGW-U entity + UPF entity passes the N3 interface and the NG-RAN Device communication
  • the PGW-U entity + UPF entity communicates with the PGW-C entity + SMF entity through the N4 interface
  • the PGW-C entity + SMF entity communicates with the PCRF entity + PCF entity through the N7 interface
  • the HSS+UDM entity passes the N10 interface and the PGW -C entity + SMF entity communication
  • HSS+UDM entity communicates with AMF entity through N8 interface
  • PCRF entity + PCF entity communicates with AMF entity through N15 interface
  • PGW-C entity + SMF entity communicates with AMF entity through N11 interface
  • AMF entity The NMF entity communicates with the NG-RAN device through the N2 interface
  • the AMF entity communicates with the terminal through the N1
  • the name of the interface between the network elements in FIG. 1 is only an example. In the specific implementation, the interface name may be other names, which is not specifically limited in this embodiment of the present application.
  • the NG-RAN device in the 5G network may also be referred to as an access device, and the access device refers to a device that accesses the core network, for example, a base station, a broadband network service gateway (broadband network gateway, BNG), aggregation switch, non-3GPP access equipment, etc.
  • the base station may include various types of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like, which are not specifically limited in this embodiment of the present application.
  • the 4G network may also include a general packet radio system (GPRS) service support node (SGSN), etc., 5G.
  • the network may further include an authentication server function (AUSF) entity, a network slice selection function (NSSF) entity, and a network function repository function (NRF) network element.
  • AUSF authentication server function
  • NSSF network slice selection function
  • NRF network function repository function
  • the terminal may provide an APN to the MME when initiating a packet service.
  • the MME performs domain name resolution by using a domain name server (DNS) according to the APN provided by the terminal, so as to obtain an internet protocol (IP) address that is interconnected between the networks of the PGW, and access the user to the corresponding APN.
  • DNS domain name server
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the session establishing system 20 includes a first mobility management entity 201 and a second mobility management entity 202.
  • the first mobility management entity 201 is configured to obtain information about a PDN connection that has been established when the terminal accesses the EPC, and obtain an S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection.
  • the second mobile management entity 202 sends the S-NSSAI of the network slice corresponding to the PDN connection, and the S-NSSAI of the corresponding network slice of the PDN connection is used to indicate the network slice of the PDU session.
  • the second mobility management entity 202 is configured to receive the S-NSSAI of the network slice corresponding to the PDN connection of the first mobility management entity 201, and send a registration accept message to the terminal.
  • the second mobility management entity 202 is further configured to: after receiving the PDU session establishment request from the terminal, establish a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity 201 and the second mobility management entity 202 in the embodiment of the present application may communicate directly or through the forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 201 in the embodiment of the present application may also be referred to as an initial mobility management entity, and the second mobility management entity 202 may also be referred to as a target mobility management entity. Let me repeat.
  • the first mobility management entity may acquire the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, and connect the S-NSSAI of the network slice corresponding to the PDN connection. Sent to the second mobility management entity, so the second mobility management entity can receive the S-NSSAI of the network slice corresponding to the PDN connection from the first mobility management entity, and after receiving the PDU session establishment request from the terminal, according to the PDN The S-NSSAI that connects the corresponding network slice establishes a PDU session in the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the foregoing embodiment is described by using the first mobility management 201 and the second mobility management entity 202 as an example.
  • the first mobility management entity 201 and the second mobility management entity 202 may also be the same. ,at this time:
  • the first mobility management entity 201 is configured to obtain the information about the PDN connection that has been established when the terminal accesses the EPC, and obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, and then send the registration to the terminal. Accept the message.
  • the first mobility management entity 201 is further configured to: after receiving the PDU session establishment request from the terminal, establish a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity may acquire the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, so the first mobility management entity may receive the PDU from the terminal.
  • a PDU session is established in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the foregoing session establishing system 20 may be applied to the 4G network and the 5G network interworking architecture as shown in FIG. 1.
  • the first mobility management entity 201 or the second mobility management entity 202 may correspond to the AMF entity.
  • FIG. 1 is merely an exemplary way of connecting an AMF entity in a 4G network and a 5G network interworking architecture.
  • the first mobility management entity 201 and the second mobility management entity 202 are different mobility management entities
  • the first mobility management entity 201 and the second mobility management entity 202 respectively correspond to different AMF entities
  • each AMF entity is in 4G.
  • the connection mode in the network and the 5G network interworking architecture refer to the AMF entity shown in FIG. 1 , and details are not described herein again.
  • different AMF entities can communicate through the N14 interface, which is uniformly described here, and will not be described below.
  • a session establishing system 110 is provided in this embodiment of the present application.
  • the session establishing system 110 includes a control plane function entity 1101 and a first mobility management entity 1103.
  • the session establishing system 110 may further include a user data management entity 1102 and a second mobility management entity 1104.
  • the control plane function entity 1101 is configured to determine an S-NSSAI of the network slice corresponding to the session, and store the S-NSSAI of the network slice corresponding to the session to the user data management entity 1103.
  • the first mobility management entity 1103 is configured to obtain, from the user data management entity 1103, the S-NSSAI of the network slice corresponding to the session, where the S-NSSAI of the network slice corresponding to the session is used to indicate the network slice of the session.
  • the first mobility management entity 1103 is further configured to send, to the second mobility management entity 1104, the S-NSSAI of the network slice corresponding to the session.
  • the second mobility management entity 1104 is configured to receive the S-NSSAI of the network slice corresponding to the session from the first mobility management entity 1103, and according to the S-NSSAI of the network slice corresponding to the session, in the network slice corresponding to the session. Establish a session.
  • the first mobility management entity 1103 and the second mobility management entity 1104 in the embodiment of the present application may directly communicate, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 1103 in the embodiment of the present application may also be referred to as an initial mobility management entity, and the second mobility management entity 1104 may also be referred to as a target mobility management entity. Let me repeat.
  • the session establishment system 110 provided by the embodiment of the present application is applicable not only to the scenario where the terminal switches from the EPC to the 5GC supporting the network slice, but also to the terminal switching from the 5GC that does not support the network slice to the 5GC that supports the network slice.
  • the embodiment of the present application does not specifically limit this.
  • the session in the EPC includes the PDN connection; the session in the 5GC includes the PDU session, which is uniformly described herein, and is not described here.
  • session establishment in the embodiment of the present application specifically refers to an update to an existing session, which is uniformly described herein, and details are not described herein again.
  • the S-NSSAI of the network slice corresponding to the session may be obtained from the user data management entity, and the S-NSSAI of the network slice corresponding to the session is sent to the session establishment system provided by the embodiment of the present application.
  • a second mobility management entity so the second mobility management entity can receive the S-NSSAI of the network slice corresponding to the session from the first mobility management entity, and according to the S-NSSAI of the network slice corresponding to the session, corresponding to the session Establish a session in the network slice.
  • the network when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the foregoing embodiment is described by using the first mobility management 1103 and the second mobility management entity 1104 as an example.
  • the first mobility management entity 1103 and the second mobility management entity 1104 may also be the same. ,at this time:
  • the control plane function entity 1101 is configured to determine an S-NSSAI of the network slice corresponding to the session, and store the S-NSSAI of the network slice corresponding to the session to the user data management entity 1102.
  • the first mobility management entity 1103 is configured to obtain an S-NSSAI of the network slice corresponding to the session from the user data management entity 1102, and establish an S-NSSAI of the network slice corresponding to the session in the network slice corresponding to the session. Conversation.
  • the first mobility management entity can acquire the S-NSSAI of the network slice corresponding to the session from the user data management entity, the first mobility management entity can receive the session establishment request from the terminal. Then, according to the S-NSSAI of the network slice corresponding to the session, a session is established in the network slice corresponding to the session. That is to say, based on the scheme, when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice, the network can be selected according to the selected S-NSSAI in the 5GC. Establish a session in the slice.
  • the session establishment system 110 can be applied to the 4G network and the 5G as shown in FIG. 1 .
  • the control plane function entity 1101 may correspond to the SMF entity + PGW-C entity in FIG. 1;
  • the user data management entity 1102 may correspond to the HSS entity + UDM entity in FIG. 1;
  • the management entity 1103 or the second mobility management entity 1104 may correspond to the AMF entity in FIG. 1 and is uniformly described herein, and details are not described herein again.
  • FIG. 11 is merely an exemplary way of connecting an AMF entity in a 4G network and a 5G network interworking architecture.
  • the first mobility management entity 1103 and the second mobility management entity 1104 are different mobility management entities
  • the first mobility management entity 1103 and the second mobility management entity 1104 respectively correspond to different AMF entities
  • each AMF entity is in 4G.
  • the connection mode in the network and the 5G network interworking architecture refer to the AMF entity shown in FIG. 1 , and details are not described herein again.
  • different AMF entities can communicate through the N14 interface, which is uniformly described here, and will not be described below.
  • the control plane function entity 1101 may correspond to the SMF in the 5G network.
  • the above-mentioned user data management entity 1102 may correspond to a UDM entity in a 5G network; the first mobility management entity 1103 or the second mobility management entity 1104 may correspond to an AMF entity in a 5G network, which is uniformly described herein, and details are not described herein.
  • the session establishment system 140 includes a control plane function entity 1401 and a first mobility management entity 1402.
  • the control plane function entity 1401 is configured to obtain information about a PDN connection that has been established when the terminal accesses the EPC, and an S-NSSAI of the network slice corresponding to the PDN connection.
  • the control plane function entity 1401 is further configured to send, to the network storage function entity, the information of the PDN connection and the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity 1402 is configured to obtain information about the PDN connection, and send the PDN connection information to the network storage function entity, where the PDN connection information is used to determine the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity 1402 is further configured to receive an S-NSSAI of the network slice corresponding to the PDN connection from the network storage function entity.
  • session establishment in the embodiment of the present application specifically refers to an update to an existing session, which is uniformly described herein, and details are not described herein again.
  • the first AMF entity may obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, so the first AMF entity may receive the handover request from the MME.
  • the second AMF entity information is obtained according to the S-NSSAI of the network slice corresponding to the PDN connection, and then the PDU session can be established in the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the session establishing system 140 in this embodiment of the present application may further include: a network storage function entity 1403.
  • the network storage function entity 1403 is configured to receive and store the information of the PDN connection from the control plane function entity 1401 and the S-NSSAI of the network slice corresponding to the PDN connection.
  • the network storage function entity 1403 is further configured to receive information about the PDN connection from the first mobility management entity, and according to the information of the PDN connection, and the stored information of the PDN connection and the S- of the network slice corresponding to the PDN connection.
  • the NSSAI after determining the S-NSSAI of the network slice corresponding to the PDN connection, sends the S-NSSAI of the network slice corresponding to the PDN connection to the first mobility management entity 1402.
  • control plane function entity 1401 and the network storage function entity 1403 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 1402 and the network storage function entity 1403 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the session establishment system 140 in this embodiment of the present application may further include a third mobility management entity 1404 in the EPC.
  • the control plane function entity 1401 is further configured to send the information of the PDN connection to the third mobility management entity 1404.
  • the third mobility management entity 1404 is configured to receive information about the PDN connection from the control plane function entity 1401, and send the information of the PDN connection to the first mobility management entity.
  • the first mobility management entity 1402 is configured to obtain information about the PDN connection, and includes: information for receiving the PDN connection from the third mobility management entity.
  • control plane function entity 1401 and the third mobility management entity 1404 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 1402 and the third mobility management entity 1404 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity can acquire the information of the PDN connection.
  • the control plane function entity 1401 may correspond to the 4G network shown in FIG.
  • the SMF entity + PGW-C entity in the 5G network interworking architecture the first mobility management entity may correspond to the AMF entity in the 4G network and the 5G network interworking architecture shown in FIG. 1
  • the network storage function entity 1403 may correspond to The NRF entity (not shown) in the 5G network is uniformly described herein, and will not be described below.
  • the session establishment system 180 includes a network storage function entity 1803 and a first mobility management entity 1802.
  • the first mobility management entity 1802 is configured to send the first information of the user plane entity corresponding to the PDN connection to the network storage function entity 1803.
  • the network storage function entity 1803 is configured to receive first information from the first mobility management entity 1801.
  • the network storage function entity 1803 is further configured to determine, according to the first information, an S-NSSAI of the first network slice corresponding to the PDN connection, and send the S-NSSAI of the first network slice to the first mobility management entity 1802.
  • the first mobility management entity 1802 is further configured to receive the S-NSSAI of the first network slice from the network storage function entity 1803.
  • the first AMF entity may obtain the S-NSSAI of the first network slice corresponding to the PDN connection according to the first information of the user plane entity corresponding to the PDN connection, so the first AMF entity
  • the second AMF entity information may be obtained according to the S-NSSAI of the first network slice corresponding to the PDN connection, and may be in the corresponding first network slice.
  • Establish a PDU session That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the session establishing system 180 in this embodiment of the present application may further include: a user plane entity 1801.
  • the user plane entity 1801 is configured to send the first information and the S-NSSAI of the first network slice corresponding to the first information to the network storage function entity 1803.
  • the network storage function entity 1803 is configured to receive the first information from the user plane entity 1801 and the S-NSSAI of the first network slice corresponding to the first information.
  • the user plane entity 1801 and the network storage function entity 1803 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 1802 and the network storage function entity 1803 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • user equipment user equipment
  • UE user equipment
  • MS mobile station
  • a mobility management entity 1802 or a network storage function entity 1803 may be implemented by one entity device, or may be implemented by multiple entity devices, or may be a logical function module in a physical device, which is not specifically limited in this embodiment of the present application. .
  • FIG. 3 is a schematic diagram showing the hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 300 includes at least one processor 301, a communication line 302, a memory 303, and at least one communication interface 304.
  • the processor 301 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 302 can include a path for communicating information between the components described above.
  • the communication interface 304 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 303 can 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 that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory may be present independently and connected to the processor via communication line 302. The memory can also be integrated with the processor.
  • the memory 303 is configured to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute computer execution instructions stored in the memory 303, thereby implementing the session establishment method provided by the following embodiments of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 300 can include multiple processors, such as processor 301 and processor 308 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 300 can also include an output device 305 and an input device 306.
  • Output device 305 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 306 is in communication with processor 301 and can receive user input in a variety of ways.
  • input device 306 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the communication device 300 described above may be a general purpose device or a dedicated device.
  • the communication device 300 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 300.
  • the session establishment system shown in FIG. 2 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 .
  • the method for establishing a session provided by the embodiment of the present application includes the following steps:
  • the terminal accesses the EPC to establish a PDN connection
  • the PDN connection information is stored in the subscription data of the user data management entity terminal.
  • step S401 For the related implementation of the step S401, reference may be made to the implementation in the prior art, and details are not described herein.
  • the information about the PDN connection may be the APN corresponding to the PDN connection, or the information of the control plane function entity (ie, the SMF entity + the PGW-C entity) corresponding to the PDN connection.
  • the information of the control plane function entity corresponding to the PDN connection may include, for example, an IP address or a fully qualified domain name (FQDN) of the control plane function entity, which is not specifically limited in this embodiment.
  • the PDN connection in the embodiment of the present application may be a PDN connection established in the DCN selected by the terminal when the terminal accesses the EPC, or may be a PDN connection established in the non-DCN. No specific limitation.
  • the MME may also send the DCN information to the terminal, which is not specifically implemented in this embodiment. limited.
  • the terminal sends a registration request to the first AMF entity, so that the first AMF entity receives the registration request from the terminal.
  • the registration request carries the identifier of the terminal.
  • the registration request may also carry the NSSAI (requested NSSAI) requested by the terminal, the information of the DCN, the location information of the terminal, and the like, which are not specifically limited in this embodiment of the present application.
  • NSSAI quested NSSAI
  • the first AMF entity obtains the subscription data of the terminal from the user data management entity according to the identifier of the terminal, where the subscription data includes information about the PDN connection that has been established when the terminal accesses the EPC.
  • the subscription data may also include one or more S-NSSAI(s) that are subscribed to, and the embodiment of the present application does not specifically limit this.
  • the subscription data of the terminal may be carried in the Nudm message sent by the user data management entity to the first AMF entity.
  • Nudm is a serviced interface of the UDM entity.
  • the Nudm message is a Nudm subscriber data management in the existing protocol. Its function is: Allow network function (NF) consumers to take when needed. Back to the terminal's subscription data, as well as providing updated terminal subscription data to the contracted NF consumer.
  • NF network function
  • the first AMF entity acquires the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection.
  • the information about the PDN connection includes the APN corresponding to the PDN connection
  • the first AMF entity obtains the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, including:
  • the AMF entity determines the S-NSSAI of the network slice corresponding to the PDN connection according to the APN and the correspondence between the pre-configured APN and the S-NSSAI.
  • the correspondence between the pre-configured APN and the S-NSSAI includes a one-to-one relationship between the APN and the S-NSSAI, or a one-to-many relationship between the APN and the S-NSSAI.
  • the first AMF entity may be based on the APN and the one-to-one relationship between the pre-configured APN and the S-NSSAI. Determine the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S-NSSAI3 according to the APN and the one-to-one relationship between the APN and the S-NSSAI.
  • the first AMF entity is configured according to each of the one-to-many relationship between the pre-configured APN and the S-NSSAI.
  • the priority of the NSSAI, the load information of the network slice indicated by each S-NSSAI, and at least one of the NSSAIs supported by the AMF set configured in the first AMF entity, and the APN and the pre-configured APN and S-NSSAI A one-to-many relationship that determines the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first AMF entity can determine the S-NSSAI of the three network slices according to the APN and the one-to-many relationship between the pre-configured APN and the S-NSSAI, namely S-NSSAI7, S-NSSAI8, and S-NSSAI9.
  • the first AMF entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the priorities of the pre-configured S-NSSAI7, S-NSSAI8, and S-NSSAI9. For example, if the priority of the S-NSSAI7 is higher than the priority of the S-NSSAI8, and the priority of the S-NSSAI8 is higher than the priority of the S-NSSAI9, the first AMF entity may determine the S- of the network slice corresponding to the PDN connection.
  • NSSAI is S-NSSAI7.
  • the first AMF entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the load information of the network slice indicated by the pre-configured S-NSSAI7, S-NSSAI8, and S-NSSAI9. For example, if the load of the network slice indicated by S-NSSAI7 is higher than the load of the network slice indicated by S-NSSAI8, the load of the network slice indicated by S-NSSAI8 is higher than the load of the network slice indicated by S-NSSAI9, then The first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S-NSSAI9.
  • the first AMF entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the NSSAI supported by the AMF set configured in the first AMF entity. For example, if the NSSAI supported by the AMF set configured in the first AMF entity includes S-NSSAI3, S-NSSAI5, and S-NSSAI8, the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S- NSSAI8.
  • the first AMF entity may determine the priority according to the pre-configured S-NSSAI7, S-NSSAI8, and S-NSSAI9 priorities, and the load information of the network slice indicated by S-NSSAI7, S-NSSAI8, and S-NSSAI9.
  • the PDN connects to the S-NSSAI of the corresponding network slice. For example, if the priority of S-NSSAI7 is higher than the priority of S-NSSAI8, the priority of S-NSSAI8 is higher than the priority of S-NSSAI9, and the load of the network slice indicated by S-NSSAI7 is higher than that indicated by S-NSSAI8.
  • the load of the network slice, the load of the network slice indicated by the S-NSSAI8 is higher than the load of the network slice indicated by the S-NSSAI9, and the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S- NSSAI8.
  • the first AMF entity may determine the network slice corresponding to the PDN connection according to the priorities of the pre-configured S-NSSAI7, S-NSSAI8, and S-NSSAI9, and the NSSAI supported by the AMF set configured in the first AMF entity.
  • S-NSSAI For example, if the priority of the S-NSSAI7 is equal to the priority of the S-NSSAI8, the priority of the S-NSSAI8 is higher than the priority of the S-NSSAI9, and the NSSAI supported by the AMF set configured in the first AMF entity includes the S-NSSAI3.
  • S-NSSAI5 and S-NSSAI8 the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S-NSSAI8.
  • the first AMF entity may determine, according to the load information of the network slice indicated by the S-NSSAI7, the S-NSSAI8, and the S-NSSAI9, and the NSSAI supported by the AMF set configured in the first AMF entity, the PDN connection is determined.
  • Network sliced S-NSSAI may be determined, according to the load information of the network slice indicated by the S-NSSAI7, the S-NSSAI8, and the S-NSSAI9, and the NSSAI supported by the AMF set configured in the first AMF entity.
  • the NSSAI supported by the AMF set configured in an AMF entity includes S-NSSAI3, S-NSSAI8, and S-NSSAI9, and the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S-NSSAI9.
  • the first AMF entity may according to pre-configured S-NSSAI7, S-NSSAI8, and S-NSSAI9 priorities, load information of the network slice indicated by S-NSSAI7, S-NSSAI8, and S-NSSAI9, and, first, The NSSAI supported by the AMF set configured in the AMF entity determines the S-NSSAI of the network slice corresponding to the PDN connection. For example, if the priority of S-NSSAI7 is equal to the priority of S-NSSAI8, the priority of S-NSSAI8 is higher than the priority of S-NSSAI9, and the load of the network slice indicated by S-NSSAI7 is higher than that indicated by S-NSSAI8.
  • the load of the network slice, the NSSAI supported by the AMF set configured in the first AMF entity includes S-NSSAI3, S-NSSAI5, and S-NSSAI8, and the first AMF entity may determine that the S-NSSAI of the network slice corresponding to the PDN connection is S-NSSAI8.
  • the first AMF entity may further determine the S-NSSAI of the network slice corresponding to the PDN connection by combining other information.
  • the first AMF entity may also refer to the DCN information.
  • the terminal usage type in the DCN information may be mapped to the SST in the S-NSSAI of the network slice. Therefore, the S-NSSAI of the network slice corresponding to the PDN connection is determined, which is not specifically limited in this embodiment of the present application.
  • the information about the PDN connection includes information about a control plane function entity (ie, an SMF entity + a PGW-C entity) corresponding to the PDN connection; and the SMF entity + the PGW-C entity is The first AMF entity obtains the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, and the first AMF entity determines the PDN connection according to the information of the control plane function entity. Corresponding network sliced S-NSSAI.
  • the network slice information is included in the FQDN, and the S-NSSAI corresponding to the network slice can be determined according to the FQDN.
  • the first AMF entity can reversely query the DNS according to the IP address, thereby obtaining the SMF entity + the PGW-C entity.
  • FQDN because the FQDN contains network slice information, the S-NSSAI corresponding to the network slice can be determined according to the FQDN.
  • the first AMF entity needs to be further determined according to the configuration information, where the configuration information includes the correspondence between the IP address segment and the network slice, and the like. This example does not specifically limit this.
  • the information about the PDN connection includes information about a control plane function entity (ie, an SMF entity + a PGW-C entity) corresponding to the PDN connection; and the SMF entity + the PGW-C entity is The S-NSSAI of the network slice corresponding to the PDN connection is obtained by the first AMF entity according to the information of the PDN connection, and the first AMF entity performs the function of the control plane according to the information of the control plane function entity.
  • the entity sends a request message, which is used to request the S-NSSAI of the network slice corresponding to the PDN connection; the first AMF entity receives the S-NSSAI of the network slice corresponding to the PDN connection from the control plane function entity.
  • the embodiment of the present application is only an exemplary implementation of the foregoing S-NSSAI for obtaining the network slice corresponding to the PDN connection, and of course, the network slice corresponding to the PDN connection may be obtained by other means.
  • the S-NSSAI of the embodiment of the present application does not specifically limit the manner in which the S-NSSAI of the network slice corresponding to the PDN connection is obtained.
  • the first AMF entity acquires information about the second AMF entity.
  • the acquiring, by the first AMF entity, the information of the second AMF entity may include: acquiring, by the first AMF entity, the information of the second AMF entity according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first AMF entity determines the information of the second AMF entity according to the S-NSSAI of the network slice corresponding to the PDN connection, considering that one network slice instance may be included in one network slice. Specifically, the first AMF entity determines, according to the information of the PDN connection, the network slice instance corresponding to the PDN connection; the first AMF entity determines the second according to the S-NSSAI of the network slice corresponding to the PDN connection and the information of the network slice instance. Mobile management entity information.
  • the first AMF entity may further determine the information of the second mobility management entity in combination with other information.
  • the first AMF entity may further perform mapping information according to the network slice and the AMF entity set configured in the first AMF entity, and the first AMF.
  • the mapping information of the DCN and the AMF entity set configured in the entity, the NSSAI requested by the terminal, the NSSAI of the terminal subscription, or the location information of the terminal, etc. determine the information of the second AMF entity, and may refer to the existing implementation manner. Narration.
  • the first AMF entity acquires the information of the second AMF entity according to the S-NSSAI of the network slice corresponding to the PDN connection, where the first AMF entity sends the network corresponding to the PDN connection to the NSSF entity.
  • the sliced S-NSSAI, the S-NSSAI of the corresponding network slice of the PDN connection is used to determine information of the second AMF entity; the first AMF entity receives information of the second AMF entity from the NSSF entity.
  • the specific manner of determining, by the NSSF entity, the information of the second AMF entity according to the S-NSSAI of the network slice corresponding to the PDN connection may refer to the foregoing AMF entity determining the second AMF entity according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the specific manner of the information will not be described here.
  • the first AMF entity may obtain the information of the second AMF entity after determining that the network slice corresponding to the PDN connection cannot be provided, and the second AMF entity and the second An AMF entity is different; or the first AMF entity may be directly obtained by the second AMF entity.
  • the second AMF entity may be the same as the first AMF entity, and may be different. limited.
  • the first AMF entity may not need to obtain the information of the second AMF entity, and the description is uniformly performed herein, and details are not described herein.
  • the session establishment method provided by the embodiment of the present application further includes the following steps:
  • the first AMF entity sends a re-routing message to the access device, so that the access device receives the re-routing message from the first AMF entity.
  • the rerouting message carries the information of the second AMF entity and the S-NSSAI of the network slice corresponding to the PDN connection, where the information of the second AMF entity is used to indicate that the terminal related message is rerouted to the second AMF entity, the PDN
  • the S-NSSAI that connects the corresponding network slice is used to indicate the network slice that established the PDU session.
  • the access device sends an initial terminal message to the second AMF entity, so that the second AMF entity receives the initial terminal message from the receiving device.
  • the initial terminal message carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first AMF entity may directly send the S-NSSAI of the network slice corresponding to the PDN connection to the second AMF entity, without performing steps S406 and S407.
  • the re-routing process is not specifically limited in this embodiment of the present application.
  • the second AMF entity sends a registration accept message to the terminal, so that the terminal receives the registration accept message from the second AMF entity.
  • the registration accept message carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • the registration accepting message may also carry an NSSAI (allowed NSSAI) that is allowed in the registration area, which is not specifically limited in this embodiment of the present application.
  • NSSAI allowed NSSAI
  • the terminal sends a PDU session establishment request to the second AMF entity, so that the second AMF entity receives the PDU session establishment request from the terminal.
  • the PDU session establishment request carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second AMF entity establishes a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second AMF entity establishes a PDU session in the network slice corresponding to the PDN connection in step S410. Specifically, the second AMF entity cooperates with the terminal or other network element to establish a PDU session in the network slice corresponding to the PDN connection.
  • the process of establishing a PDU session may refer to an existing process, and details are not described herein.
  • the registration accept message in step S408 of the embodiment of the present application may further carry information about the PDN connection that is allowed to be switched, so that after receiving the registration accept message, the terminal may further perform information according to the PDN connection that is allowed to be switched. , releasing all PDN connections in the EPC except the PDN connection that allows switching, thereby saving system resources.
  • the registration accept message in step S408 of the embodiment of the present application may further carry the information of the PDN connection that needs to be deleted, so that after receiving the registration accept message, the terminal may further delete the PDN connection information according to the need. , release the corresponding PDN connection in the EPC, which can save system resources.
  • the first AMF entity may obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, and send the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second AMF entity can receive the S-NSSAI of the network slice corresponding to the PDN connection from the first AMF entity, and after receiving the PDU session establishment request from the terminal, according to the network corresponding to the PDN connection.
  • the sliced S-NSSAI establishes a PDU session in the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the actions of the first AMF entity and the second AMF entity in the foregoing steps S401 to S410 may be performed by the processor 301 in the communication device 300 shown in FIG. 3, by calling the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 2 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 5 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • the second AMF entity stores the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second AMF entity sends a registration accept message to the terminal, so that the terminal receives the registration accept message from the second AMF entity.
  • the registration acceptance message carries the NSSAI (allowed NSSAI) allowed in the registration area.
  • the terminal sends a PDU session establishment request to the second AMF entity, so that the second AMF entity receives the PDU session establishment request from the terminal.
  • the PDU session establishment request carries the S-NSSAI of the network slice requested by the terminal and the APN corresponding to the PDN connection requested by the terminal.
  • the S-NSSAI of the network slice that is requested by the terminal is selected by the NSSAI that is allowed by the terminal from the second AMF entity to the terminal.
  • the S-NSSAI of the network slice requested by the terminal is the same as the S-NSSAI of the network slice corresponding to the pre-stored PDN connection
  • the APN corresponding to the PDN connection requested by the terminal is the same as the APN corresponding to the PDN connection.
  • the second AMF entity establishes a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second AMF entity establishes a PDU session in the network slice corresponding to the PDN connection in step S511. Specifically, the second AMF entity cooperates with the terminal or other network element to establish a PDU session in the network slice corresponding to the PDN connection.
  • the process of establishing a PDU session may refer to an existing process, and details are not described herein.
  • the second AMF entity may reject the PDU session establishment request. This is not specifically limited.
  • the PDU session establishment request in step S510 may not carry the S-NSSAI of the network slice requested by the terminal, but carry the information of the PDN connection; and further, the second AMF entity receives the terminal from the terminal.
  • the PDU session may be established in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection, which is not specifically limited in this embodiment of the present application.
  • the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the actions of the first AMF entity and the second AMF entity in the foregoing steps S501 to S511 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 2 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 6 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • the first AMF entity sends a slice selection request message to the NSSF entity, so that the NSSF entity receives the slice selection request message from the first AMF entity.
  • the slice selection request message carries information of a PDN connection.
  • the NSSF entity sends the information of the S-NSSAI and the second AMF entity of the network slice corresponding to the PDN connection to the first AMF entity, so that the first AMF entity receives the S-NSSAI of the network slice corresponding to the PDN connection from the NSSF entity. And information about the second AMF entity.
  • the SFSF entity sends the candidate AMF entity set to the first AMF entity.
  • the first AMF entity selects the second AMF entity from the candidate AMF entity set according to the information of the candidate AMF entity set, and the load information of each AMF entity in the candidate AMF entity set, and the embodiment of the present application does not specifically limited.
  • the embodiment of the present application may also be performed by referring to steps S506-S511 in the embodiment shown in FIG. 5, and details are not repeatedly described herein.
  • the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the actions of the first AMF entity and the second AMF entity in the foregoing steps S601 to S612 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 2 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 7 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • the session establishment method provided by the embodiment of the present application further includes the following steps:
  • step S705 the embodiment of the present application may also be performed by referring to steps S508-S511 in the embodiment shown in FIG. 5, except that the second AMF entity in steps S508-S511 is replaced with the first one.
  • steps S508-S511 in the embodiment shown in FIG. 5, except that the second AMF entity in steps S508-S511 is replaced with the first one.
  • steps S704-S705 in the embodiment of the present application may also be replaced with the steps S604-S607 in the embodiment shown in FIG. 6.
  • steps S604-S607 in the embodiment shown in FIG. 6 For details, refer to the embodiment shown in FIG. 6, and details are not described herein again.
  • the first AMF entity may acquire the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection, so the first AMF entity may establish the PDU session from the terminal.
  • a PDU session is established in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection. That is to say, based on the scheme, when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the PDU session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the action of the first AMF entity in the foregoing steps S701 to S708 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303, and the embodiment of the present application does not impose any restrictions on this. .
  • the session establishment system shown in FIG. 11 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , and the session in the 4G network is a PDN connection; the session in the 5G network is a PDU session, as shown in FIG. 12 .
  • the method for establishing a session provided by the embodiment of the present application includes the following steps:
  • the terminal sends a PDN connection establishment request to the control plane function entity, so that the control plane function entity receives the PDN connection establishment request from the terminal.
  • the information about the PDN connection is carried in the PDN connection establishment request, and is used to request the control plane function entity to establish a corresponding PDN connection for the terminal.
  • the information of the PDN connection may be, for example, an APN corresponding to the PDN connection, which is not specifically limited in this embodiment of the present application.
  • the control plane function entity determines an S-NSSAI of the network slice corresponding to the PDN connection.
  • control plane function entity determines the S-NSSAI of the network slice corresponding to the PDN connection, and specifically includes: the control plane function entity determines one of the S-NSSAIs supported by the control plane function entity to be the PDN connection corresponding.
  • the network is sliced by S-NSSAI.
  • control plane function entity determines the S-NSSAI of the network slice as the S-NSSAI of the network slice corresponding to the PDN connection.
  • the control plane function entity selects one of the S-NSSAIs it supports as the S-NSSAI of the network slice corresponding to the PDN connection.
  • the control plane function entity may select the S-NSSAI according to the APN corresponding to the PDN connection.
  • the APN spaces supported by different network slices supported by the control plane function entity do not overlap.
  • APN 1 to N correspond to S.
  • -NSSAI1 corresponds to S-NSSAI2
  • APN N+1 ⁇ M corresponds to S-NSSAI2, and so on.
  • control plane function entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the subscription information of the terminal and/or the local policy. For example, the control plane function entity obtains the default S-NSSAI set subscribed by the terminal from the user data management entity, and takes the default S-NSSAI set signed by the terminal and the S-NSSAI set supported by the control plane function entity.
  • the control plane function entity determines the S-NSSAI as the S-NSSAI of the network slice corresponding to the PDN connection; if there are still multiple S-NSSAIs in the intersection, the control plane functional entity One of the S-NSSAIs of the network slice corresponding to the PDN connection may be selected according to the local policy, for example, the S-NSSAI of one of the lightly loaded network slices is used as the network slice corresponding to the PDN connection according to the load of the network slice. S-NSSAI.
  • the control plane function entity stores the S-NSSAI of the network slice corresponding to the PDN connection into the user data management entity.
  • control plane function entity sends the S-NSSAI of the network slice corresponding to the PDN connection to the user data management entity, so that the user data management entity receives and stores the S- of the network slice corresponding to the PDN connection from the control plane function entity.
  • NSSAI NSSAI
  • the control plane function entity may send the identifier of the terminal and the PDN connection information to the user data management entity, so that the user data management entity may send the S-NSSAI of the network slice corresponding to the PDN connection to the user data management entity.
  • the S-NSSAI of the network slice corresponding to the PDN connection is associated with the PDN connection of the terminal, that is, the user data management entity may perform the S-NSSAI of the network slice corresponding to the PDN connection, the identifier of the terminal, and the information of the PDN connection. Association.
  • the PDN connection information may be, for example, an APN or an identifier of a control plane function entity or other information, which is not specifically limited in this embodiment of the present application.
  • control plane function entity may further store the instance identifier of the network slice corresponding to the PDN connection to the user data management entity, which is not specifically limited in this embodiment of the present application.
  • control plane function entity After the S1204 and the PDN connection are established, the control plane function entity sends a PDN connection setup response to the terminal, so that the terminal receives the PDN connection setup response from the control plane function entity.
  • the terminal After the terminal moves to the 5G coverage, the terminal sends a registration request to the first AMF entity, so that the first AMF entity receives the registration request from the terminal.
  • the registration request carries the identifier of the terminal.
  • step S1205 For the description of step S1205, reference may be made to step S402 in FIG. 4, and details are not described herein again.
  • step S1206 is similar to step S403. The difference is that the subscription data of the terminal that is obtained by the first AMF entity from the user data management entity in the embodiment of the present application further includes the S-NSSAI of the network slice corresponding to the PDN connection. The embodiment shown in FIG. 4 will not be repeated here.
  • the subscription data of the terminal acquired by the first AMF entity from the user data management entity in the embodiment of the present application may further include the The instance identifier of the network slice corresponding to the PDN connection is not specifically limited in this embodiment of the present application.
  • the subscription data of the terminal that is obtained by the first AMF entity from the user data management entity in step S1206 further includes the instance identifier of the network slice corresponding to the PDN connection
  • the first AMF entity is When the second AMF entity is selected, it is also necessary to consider whether the selected second AMF entity supports the slice instance of the network slice corresponding to the PDN connection, which is uniformly described herein, and is not described here.
  • the manner in which the first AMF entity obtains the information of the second AMF entity may also be the manner in which the first AMF entity in the step S604-S607 obtains the second AMF entity.
  • the embodiment shown in FIG. 6 will not be described here.
  • step S1208-S1212 the same as the step S406-410 or the steps S506-S511, specifically refer to the embodiment shown in FIG. 4 or FIG. 5, and details are not described herein again.
  • the session establishment method shown in FIG. 12 is described by taking a scenario in which the terminal switches from the EPC to the 5GC supporting the network slice.
  • the session establishment method is also applicable to the terminal switching from the 5GC that does not support the network slice to
  • the PDN connection in steps S1201-S1212 is replaced with a PDU session
  • the control plane functional entity is replaced with an SMF entity
  • the user data management entity is replaced by a UDM entity.
  • the foregoing steps S1210-S1212 may not be performed, but are performed as follows: Session update process: the second AMF entity notifies the SMF entity to perform the session update, and the SMF entity updates the user plane path for the session, including the SMF entity selecting a new UPF entity, replacing the old UPF entity with the new UPF entity, or the new UPF The entity is inserted into the user plane path.
  • Session update process the second AMF entity notifies the SMF entity to perform the session update, and the SMF entity updates the user plane path for the session, including the SMF entity selecting a new UPF entity, replacing the old UPF entity with the new UPF entity, or the new UPF The entity is inserted into the user plane path.
  • the first AMF entity may obtain the S-NSSAI of the network slice corresponding to the session from the user data management entity, and send the S-NSSAI of the network slice corresponding to the session to the second An AMF entity, so the second AMF entity can receive the S-NSSAI of the network slice corresponding to the session from the first AMF entity, and after receiving the session establishment request from the terminal, according to the S-NSSAI of the network slice corresponding to the session, A session is established in the network slice corresponding to the session.
  • the actions of the first AMF entity and the second AMF entity in the foregoing steps S1201 to S1212 may be performed by the processor 301 in the communication device 300 shown in FIG. 3 by calling the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 11 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1, and the session in the 4G network is a PDN connection; the session in the 5G network is a PDU session, as shown in FIG.
  • the method for establishing a session provided by the embodiment of the present application includes the following steps:
  • the source access device After the source access device determines that the terminal needs to be handed over to the destination access device, the source access device sends a first handover request to the source MME entity, so that the source MME entity receives the first handover request from the source access device.
  • the first handover request carries information about the target access device.
  • the information of the target access device may be, for example, the location information of the target access device or the identifier of the target access device or the identifier of the target cell, which is not specifically limited in this embodiment of the present application. .
  • the source MME entity selects the first AMF entity.
  • the source MME entity may select the first AMF entity according to the location information of the target access device.
  • the source MME entity sends a second handover request to the first AMF entity, so that the first AMF entity receives the second handover request from the source MME entity.
  • the second handover request carries at least one of the established session information, such as an APN, a DNN, and an identifier of a control plane function entity.
  • step S1308 the same as step S1206, specifically refer to the embodiment shown in FIG. 12, and details are not described herein again.
  • the S-NSSAI of the network slice corresponding to the established PDN connection is not carried in the second handover request in step S1307.
  • the step S1308 is not performed, and the description is not repeated here.
  • the first AMF entity sends a third handover request to the second AMF entity, so that the second AMF entity receives the third handover request from the first AMF entity.
  • the third handover request carries the information carried in the second handover request, and the S-NSSAI of the network slice corresponding to the PDN connection acquired from the user data management entity.
  • the third handover request further carries the NSSAI that is allowed by the terminal, which is not specifically limited in this embodiment.
  • the first AMF entity may send the second handover request to the second AMF entity, or may send the second handover request to the second AMF entity by using the foregoing redirection manner. This is not specifically limited.
  • the subsequent handover process includes a session update process, a registration process, and the like, which are not specifically limited in this embodiment of the present application.
  • the session update process may include: the second AMF entity notifying the control plane management entity to perform session update, and the control plane management entity updates the user plane path for the session, including the control plane management entity selecting a new UPF entity, and replacing the new UPF entity with the new UPF entity.
  • the old UPF entity, or the new UPF entity is inserted into the user plane path.
  • the registration process may include: the terminal sending a registration request to the second AMF entity, so that the second AMF entity receives the registration request from the terminal; and the second AMF entity sends the allowed NSSAI and the registration area to the terminal, specifically Refer to the existing implementation manner, and details are not described herein.
  • the session establishment method shown in FIG. 13 is described by taking a scenario in which the terminal switches from the EPC to the 5GC supporting the network slice.
  • the session establishment method is also applicable to the terminal switching from the 5GC that does not support the network slice to
  • the only difference is that the PDN connection in steps S1301-S1311 is replaced with a PDU session, the source MME entity is replaced with the source AMF entity, the control plane functional entity is replaced with the SMF entity, and the user data is managed.
  • the entity may be replaced by a UDM entity.
  • the session establishment method provided by the embodiment of the present application may be performed according to the selected S-NSSAI when the terminal switches from the EPC to the 5GC supporting the network slice, or when the terminal switches from the 5GC that does not support the network slice to the 5GC that supports the network slice.
  • a session is established in the 5GC's network slice.
  • the actions of the first AMF entity and the second AMF entity in the foregoing steps S1301 to S1311 may be performed by the processor 301 in the communication device 300 shown in FIG. 3, by calling the application code stored in the memory 303. There are no restrictions on this.
  • FIG. 12 and FIG. 13 are all described by taking the AMF entity different from the first AMF entity and the second AMF entity as an example.
  • the first AMF entity and the second AMF entity may also be used. It is the same AMF entity.
  • steps S1207-S1209 need not be performed in FIG. 12; steps are not required in FIG.
  • steps S1207-S1209 need not be performed in FIG. 12; steps are not required in FIG.
  • FIG. 12 or FIG. 13 for details, and details are not described herein again.
  • the session establishment system shown in FIG. 14 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 15 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • the control plane function entity ie, the SMF entity + the PGW-C entity
  • the information of the PDN connection from the control plane functional entity and the S-NSSAI of the network slice corresponding to the PDN connection.
  • the information about the PDN connection may include: information about a control plane function entity corresponding to the PDN connection, an APN corresponding to the PDN connection, a PDN type corresponding to the PDN connection, or at least a PDN address corresponding to the PDN connection.
  • the embodiment of the present application does not specifically limit this.
  • the information about the control plane function entity corresponding to the PDN connection may include, for example, information and control plane of a public land mobile network (PLMN) where the control plane function entity corresponding to the PDN connection is located.
  • PLMN public land mobile network
  • the IP address or the FQDN of the functional entity is not specifically limited in this embodiment of the present application.
  • control plane function entity may be configured according to the information about the control plane function entity corresponding to the PDN connection, the APN corresponding to the PDN connection, the PDN type corresponding to the PDN connection, the PDN address corresponding to the PDN connection, or the control plane function.
  • At least one of the S-NSSAI sets supported by the entity determines the S-NSSAI of the network slice corresponding to the PDN connection.
  • the FQDN of the control plane function entity may include the S-NSSAI of the network slice corresponding to the PDN connection.
  • the control plane function entity may configure a mapping relationship between the APN and the S-NSSAI.
  • control plane function entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the APN corresponding to the PDN connection and the corresponding relationship.
  • control plane function entity supports only one S-NSSAI, and the control plane function entity determines that the S-NSSAI corresponding to the PDN connection is the S-NSSAI supported by the control plane function entity.
  • the control plane function entity may configure a mapping relationship between the PDN type and the S-NSSAI.
  • the control plane function entity may determine the S-NSSAI of the network slice corresponding to the PDN connection according to the PDN type corresponding to the PDN connection and the corresponding relationship. .
  • the embodiment of the present application does not limit the specific implementation manner of the S-NSSAI of the network slice corresponding to the PDN connection.
  • the NRF entity after the NRF entity receives the information about the PDN connection from the control plane function entity and the S-NSSAI of the network slice corresponding to the PDN connection, the information about the PDN connection and the PDN may be established or stored.
  • the corresponding relationship of the S-NSSAI of the corresponding network slice is not specifically limited in this embodiment of the present application.
  • the information of the PDN connection is an identifier of the control plane function entity corresponding to the PDN connection, and the corresponding relationship shown in Table 4 can be stored in the NRF entity:
  • PDN connection information PDN connects the corresponding network slice to the S-NSSAI Control surface function entity identification 1 S-NSSAI1 Control surface function entity identifier 2 S-NSSAI2
  • the session establishing method provided by the embodiment of the present application may further include the following step S1502:
  • the control plane function entity sends the information of the control plane function entity corresponding to the PDN connection to the MME, so that the MME Receiving information from a control plane functional entity corresponding to the PDN connection of the control plane functional entity.
  • step S1501 For a description of the information about the control plane function entity corresponding to the PDN connection, refer to step S1501, and details are not described herein.
  • the MME may store information about the control plane function entity corresponding to the PDN connection. This is not specifically limited.
  • step S1501 there is no necessary sequence of execution between the step S1501 and the step S1502 in the embodiment of the present application, and the step S1501 may be performed first, and then the step S1502 may be performed; or the step S1502 may be performed first, and then the step S1501 is performed; It is also possible to perform the steps S1501 and S1502 at the same time, which is not specifically limited in the embodiment of the present application.
  • session establishment method provided by the embodiment of the present application may further include the following steps:
  • the access device in S1503 and the EPC sends a handover request (Handover Request) 1 to the MME, so that the MME receives the handover request 1 from the access device.
  • a handover request Handover Request
  • the handover request 1 includes information of a target access area.
  • the information of the target access area may include, for example, at least one of the information of the target cell, the information of the target access device, or the information of the target tracking area, which is not specifically limited in this embodiment of the present application.
  • the target cell is a cell to be accessed by the terminal, and the information of the target cell may include, for example, an identifier of the target cell;
  • the target access device is an access device to which the cell to be accessed by the terminal belongs, and the target
  • the information of the access device may include, for example, the identifier or the location information of the target access device;
  • the target tracking area is the tracking area where the cell to be accessed by the terminal is located, and the information of the target tracking area may include, for example, the identifier of the target tracking area, and the like. This embodiment of the present application does not specifically limit this.
  • the switching request 1 may further include information for determining the terminal, such as an identifier of the terminal, which is not specifically limited in this embodiment of the present application.
  • the handover request 1 in the embodiment of the present application may be sent by the access device in the EPC to the MME according to the cell measurement information reported by the terminal, and is not specifically limited in this embodiment.
  • the MME determines the first AMF entity.
  • the MME may determine, according to the information about the target access area carried in the handover request 1, whether the handover requested by the handover request 1 belongs to a handover between different types of networks.
  • the target access area is a 5G network, and therefore, the MME determines that the handover requested by the handover request belongs to a handover across systems.
  • the MME needs to determine the first AMF entity that performs the handover operation according to the information of the target access area carried in the handover request.
  • the MME may select the default AMF entity as the first AMF entity according to the location information of the target access device because there is no information about the network slice corresponding to the PDN connection.
  • the MME may select the first AMF entity according to the usage type of the terminal (Usage type) and the identifier of the target tracking area.
  • the embodiment of the present application is merely an exemplary implementation of two MMEs for determining an AMF entity.
  • the MME can also determine the first AMF entity by using other methods.
  • the existing implementation manner and details are not described herein again.
  • the MME sends a handover request 2 to the first AMF entity, so that the first AMF entity receives the handover request 2 from the MME.
  • the handover request 2 includes information about the established PDN connection.
  • information about the PDN connection For a description of the information about the PDN connection, refer to step S1501, and details are not described herein again.
  • the information about the established PDN connection included in the handover request 2 is the information of the control plane function entity corresponding to the PDN connection
  • the information about the control plane function entity corresponding to the PDN connection may be obtained by using the foregoing step S1502.
  • S1506 The first AMF entity sends a request message to the NRF entity, so that the NRF network element receives the request message from the first AMF entity.
  • the request message carries the information of the PDN connection, and is used to request the S-NSSAI of the network slice corresponding to the PDN connection.
  • the NRF entity determines, according to the information about the PDN connection, the S-NSSAI of the network slice corresponding to the PDN connection.
  • the NRF entity may query the S-NSSAI of the network slice corresponding to the PDN connection according to the PDN connection information, and the S-NSSAI of the network slice corresponding to the PDN connection.
  • the embodiment does not specifically limit this.
  • the NRF entity sends a response message to the first AMF entity, so that the first AMF entity receives the response message from the NRF entity.
  • the response message carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • one or more PDN connections may have been established in the EPC before the terminal, and therefore, the established PDN connection information included in the handover request 2 in step S1505 may be one or more.
  • Information about the PDN connection In this case, the information of each PDN connection may be separately performed by referring to steps S1506-S1508; or the S-NSSAI of the network slice corresponding to one or more PDN connections may be acquired by performing steps S1506-S1508 once.
  • the application examples are not specifically limited thereto.
  • the request message in step S1506 may further carry the PLMN of the PLMN where the control plane function entity is located.
  • the NRF entity of the PLMN in which the control plane function entity is located may be determined according to the identifier of the PLMN where the control plane function entity is located, and then from the NRF entity of the PLMN where the control plane function entity is located.
  • the S-NSSAI of the network slice corresponding to the PDN connection is obtained, which is not specifically limited in this embodiment of the present application.
  • the first AMF entity sends a handover request 3 to the second AMF entity, so that the second AMF entity receives the handover request 3 from the first AMF entity.
  • the handover request 3 may include an S-NSSAI of the network slice corresponding to the PDN connection, and information of the PDN connection acquired from the MME.
  • the other process of the session establishment may include, for example, selecting an intermediate SMF entity or a visited SMF (V-SMF) entity according to the S-NSSAI corresponding to the PDN connection.
  • V-SMF visited SMF
  • the session when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice, the session may be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the session establishment system part shown in FIG. 14 For the related technical effect analysis, refer to the session establishment system part shown in FIG. 14 , and details are not described herein again.
  • control plane function entity and the first AMF entity in the foregoing steps S1501 to S1511 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 14 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 16 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • the control plane function entity ie, the SMF entity + the PGW-C entity
  • the control plane function entity sends the PDN connection information to the NRF entity and the S-NSSAI of the network slice corresponding to the PDN connection. So that the NRF entity receives the information of the PDN connection from the control plane functional entity and the S-NSSAI of the network slice corresponding to the PDN connection.
  • control plane function entity may determine, according to the subscription data of the terminal, that the PDU session may be switched to the EPC, and further determine the information of the PDN connection and the S-NSSAI of the network slice corresponding to the PDN connection. And the information of the PDN connection and the S-NSSAI of the network slice corresponding to the PDN connection are sent to the NRF entity, which is not specifically limited in this embodiment of the present application.
  • step S1501 For a description of the information about the PDN connection in the embodiment of the present application, refer to step S1501, and details are not described herein again.
  • control plane function entity may determine the APN corresponding to the PDN connection by the control plane function entity determining the APN corresponding to the PDN connection according to the DNN corresponding to the PDU session.
  • the DNN corresponding to the PDU session is the same as the APN corresponding to the PDN connection; or the DPN corresponding to the PDN connection may be determined according to the DNN corresponding to the PDU session and the mapping relationship between the DNN and the APN; or the DNN and the PDU corresponding to the PDU session may be used.
  • the S-NSSAI of the session determines the APN corresponding to the PDN connection, and so on, which is not specifically limited in this embodiment of the present application.
  • the control plane function entity may determine the PDN type corresponding to the PDN connection by: for example, the PDN type corresponding to the PDN connection may be the same as the PDU type corresponding to the PDU session; or may be according to the PDU type corresponding to the PDU session.
  • the mapping between the PDU type and the PDN type determines the PDN type corresponding to the PDN connection.
  • the PDU type of the Ether type may be mapped to the PDN type of the non-IP type, and the like, which is not specifically limited in this embodiment.
  • control plane function entity may determine the PDN address corresponding to the PDN connection by: for example, the PDN address corresponding to the PDN connection may be the same as the PDU address corresponding to the PDU session; or, according to the PDU address corresponding to the PDU session
  • the mapping between the PDU address and the PDN address determines the PDN address corresponding to the PDN connection, which is not specifically limited in this embodiment of the present application.
  • control plane function entity may determine the S-NSSAI corresponding to the PDU session as the S-NSSAI of the network slice corresponding to the PDN connection when the PDU session is switched to the EPC. Specifically limited.
  • the NRF entity after the NRF entity receives the information about the PDN connection from the control plane function entity and the S-NSSAI of the network slice corresponding to the PDN connection, the information about the PDN connection and the PDN may be established or stored.
  • the S-NSSAI of the corresponding network slice For the corresponding relationship of the S-NSSAI of the corresponding network slice, refer to step S1501 in the embodiment shown in FIG. 15 for related description, and details are not described herein again.
  • the terminal switches from 5GC to EPC.
  • step S1602 can refer to the existing implementation manner, and details are not described herein again.
  • the session can be established in the network slice of the 5GC according to the selected S-NSSAI.
  • the session establishment system part shown in FIG. 14 and details are not described herein again.
  • control plane function entity and the first AMF entity in the foregoing steps S1601 to S1611 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. There are no restrictions on this.
  • the session establishment system shown in FIG. 18 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 19 , which is a session establishment method provided by the embodiment of the present application. Including the following steps:
  • a user plane entity ie, a UPF entity + a PGW-U entity
  • a control plane function entity ie, an SMF entity + a PGW-C entity
  • a user plane entity ie, a UPF entity + a PGW-U entity
  • the user plane entity sends the information of the user plane entity to the NRF entity and the S-NSSAI of the network slice corresponding to the information of the user plane entity, so that the NRF entity receives the user plane entity from the user plane entity.
  • the information and the corresponding network slice of the S-NSSAI When a user plane entity (ie, a UPF entity + a PGW-U entity) registers with an NRF entity, or a control plane function entity (ie, an SMF entity + a PGW-C entity) and a user plane entity (ie, a UPF entity + a PGW-U entity)
  • the user plane entity sends the information of the user plane entity to the NRF entity and the S-NSSAI
  • the information of the user plane entity may include, for example, the information of the PLMN where the user plane entity is located, the IP address of the user plane entity, or the FQDN or the TEID, the network instance, and the like.
  • the same user plane entity may have information of one or more user plane entities; or, when the user plane entity can serve multiple S-NSSAIs, the same user plane
  • the entity may have information about one or more user plane entities, which is not specifically limited in this embodiment of the present application.
  • one user plane entity may have one or more IP addresses, and different IP addresses correspond to different S-NSSAIs; or one user plane entity has one or more TEIDs, and different TEIDs correspond to different S-NSSAIs.
  • the TEID of a user plane entity may be divided into one or more segments, and different segments correspond to different S-NSSAIs and the like, which are not specifically limited in this embodiment of the present application.
  • the information of the user plane entity may be included in the information of the established PDN connection, and the related description of the PDN connection information may refer to the foregoing embodiments, and details are not described herein again.
  • the NRF entity may establish or store the information of the user plane entity and the corresponding network slice.
  • the corresponding relationship of the S-NSSAI is not specifically limited in this embodiment of the present application.
  • IP address of the user plane entity is taken as an example, and the corresponding relationship shown in Table 5 can be stored in the NRF entity:
  • step S1901 in the embodiment of the present application is an optional step, and the step S1901 may not be performed, but the information of the user plane entity and the corresponding network slice S-NSSAI are configured on the NRF entity by other means.
  • the operator or the operation administration and maintenance (OA&M) directly configures the information of the user plane entity and the corresponding relationship of the S-NSSAI of the corresponding network slice on the NRF entity during the network deployment.
  • S1902 When a connection is established between the control plane function entity and the user plane entity, for example, in the PDN connection establishment process, if the PDN connection of different network slices corresponds to different information of the user plane entity, the user plane entity sends the control plane function entity to the control plane function entity.
  • the PDN connects the information of the corresponding user plane entity, so that the control plane function entity receives the information of the user plane entity corresponding to the PDN connection from the user plane entity.
  • the information of the PDN connection corresponding to the user plane entity in the step S1902 may be all the information or the partial information in the information of the user plane entity in the step S1901, which is not specifically limited in this embodiment of the present application.
  • the information of the user plane entity in step S1901 may be, for example, the IP address of the user plane entity, the IP address 2 of the user plane entity, and the IP address 3 of the user plane entity, and the user plane entity corresponding to the PDN connection in step S1902.
  • the information may be at least one of an IP address of the user plane entity, an IP address 2 of the user plane entity, or an IP address 3 of the user plane entity.
  • the control plane function entity after the control plane function entity receives the information of the user plane entity corresponding to the PDN connection from the user plane entity, the information about the user plane entity corresponding to the PDN connection may be stored. This is not specifically limited.
  • the user plane entity may further send the user corresponding to the PDN connection to the control plane function entity.
  • the information of the user plane entity corresponding to the PDN connection and the corresponding relationship of the S-NSSAI of the corresponding network slice are not specifically limited in this embodiment of the present application.
  • the information of the user plane entity corresponding to the PDN connection includes the IP address 1 of the user plane entity and the IP address 2 of the user plane entity
  • the information corresponding to the user plane entity corresponding to the PDN connection is corresponding according to Table 5 above.
  • the S-NSSAI of the network slice may be, for example, S-NSSAI1 corresponding to the IP address 1 of the user plane entity and S-NSSAI2 corresponding to the IP address 2 of the user plane entity.
  • step S1902 in the embodiment of the present application is an optional step, and the information of the user plane entity corresponding to the PDN connection and corresponding information may be configured on the control plane function entity by using other methods.
  • the corresponding relationship of the network slice S-NSSAI For example, the operator or the operation administration and maintenance (OA&M) device directly configures the information of the user plane entity corresponding to the PDN connection and the corresponding network slice S-NSSAI on the control plane function entity during network deployment.
  • the relationship between the embodiments of the present application is not specifically limited.
  • step S1901 and step S1902 there is no necessary sequence of execution between step S1901 and step S1902 in the embodiment of the present application, which may be performed in step S1901 and then step S1902; or step S1902 may be performed first, and then step S1901 is performed; Steps S1901 and S1902 may be performed at the same time, which is not specifically limited in the embodiment of the present application.
  • the control plane function entity sends the first information of the user plane entity corresponding to the PDN connection to the MME, so that the MME Receiving first information of the user plane entity corresponding to the PDN connection from the control plane function entity.
  • the first information of the PDN connection corresponding to the user plane entity in the step S1903 may be all information or part information in the information of the PDN connection corresponding user plane entity in the step S1902.
  • the information of the PDN connection corresponding to the user plane entity in step S1902 may be, for example, the IP address 1 of the user plane entity and the IP address 2 of the user plane entity
  • the first information of the user plane entity corresponding to the PDN connection in step S1903 may be It is at least one of the IP address 1 of the user plane entity and the IP address 2 of the user plane entity.
  • the control plane function entity is to the MME.
  • the first information of the user plane entity corresponding to the PDN connection that is sent may be: the control plane function entity determines, according to the selected S-NSSAI, the information of the user plane entity corresponding to the received PDN connection from the user plane entity.
  • the information of the user plane entity corresponding to the selected S-NSSAI; or the first information of the user plane entity corresponding to the PDN connection sent by the control plane function entity to the MME may be: the control plane function entity receives the received information according to its configuration.
  • the information selected in the information of the user plane entity corresponding to the PDN connection of the user plane entity is not specifically limited in this embodiment of the present application.
  • the MME may store the first information of the user plane entity corresponding to the PDN connection, for example, The first information of the user plane entity corresponding to the PDN connection is stored in the terminal context, which is not specifically limited in this embodiment of the present application.
  • session establishment method provided by the embodiment of the present application may further include the following steps:
  • the MME sends a handover request 2 to the first AMF entity, so that the first AMF entity receives the handover request 2 from the MME.
  • the handover request 2 includes the first information of the user plane entity corresponding to the established PDN connection (such as the PDN connection in step S1902 or S1903).
  • the first information of the user plane entity corresponding to the PDN connection may be obtained through the foregoing step S1903, and is uniformly described herein, and details are not described herein again.
  • the first AMF entity sends a request message to the NRF entity, so that the NRF network element receives the request message from the first AMF entity.
  • the request message carries the first information of the user plane entity corresponding to the established PDN connection, and is used to request the S-NSSAI of the first network slice corresponding to the PDN connection.
  • the NRF entity determines, according to the first information of the user plane entity corresponding to the PDN connection, the S-NSSAI of the first network slice corresponding to the PDN connection.
  • the NRF entity may query the correspondence between the information of the user plane entity stored in the NRF and the S-NSSAI of the corresponding network slice according to the first information of the user plane entity corresponding to the PDN connection (for example, as shown in Table 5).
  • the S-NSSAI of the first network slice corresponding to the PDN connection is obtained, which is not specifically limited in this embodiment of the present application.
  • the NRF entity sends a response message to the first AMF entity, so that the first AMF entity receives the response message from the NRF entity.
  • the response message carries the S-NSSAI of the first network slice corresponding to the PDN connection.
  • one or more PDN connections may have been established in the EPC before the terminal, and therefore, the user plane entity corresponding to the established PDN connection included in the handover request 2 in step S1906
  • the first information may be the first information of the user plane entity corresponding to the one or more PDN connections.
  • the S-NSSAI of the first network slice corresponding to one or more PDNs may be obtained by performing the steps S1907-S1909. The embodiment does not specifically limit this.
  • the request message in step S1907 may further carry the PLMN identifier of the PLMN where the user plane entity is located.
  • the NRF entity of the PLMN where the first AMF entity is located may determine the NRF entity of the PLMN where the user plane entity is located according to the identifier of the PLMN where the user plane entity is located, and obtain the PDN connection corresponding to the NRF entity of the PLMN where the user plane entity is located.
  • the S-NSSAI of the network slice is not specifically limited in this embodiment of the present application.
  • the first AMF entity sends a handover request 3 to the second AMF entity, such that the second AMF entity receives the handover request 3 from the first AMF entity.
  • the handover request 3 may include an S-NSSAI of the first network slice corresponding to the PDN connection, and information of the PDN connection acquired from the MME.
  • the MME may also obtain information about a control plane function entity corresponding to the PDN connection in the manner shown in FIG. 15, and further include the PDN connection in the handover request 2 sent to the first AMF entity.
  • the information of the corresponding control plane function entity, and the switching request 3 sent by the first AMF entity to the second AMF entity may also include the information of the control plane function entity corresponding to the PDN connection, which is not specifically limited in this embodiment of the present application.
  • the other process of the subsequent handover may include, for example, the S-NSSAI selection control plane function entity or the visited SMF (visited SMF, V-SMF) entity of the first network slice corresponding to the PDN connection, or according to the control plane function.
  • the S-NSSAI selection control plane function entity or the visited SMF (visited SMF, V-SMF) entity of the first network slice corresponding to the PDN connection, or according to the control plane function.
  • the first AMF entity requests the NRF entity to request the S-NSSAI of the first network slice corresponding to the PDN connection according to the first information of the user plane entity corresponding to the PDN connection.
  • the first AMF entity may also request the address of the control plane function entity from the NRF entity according to the FQDN of the control plane function entity corresponding to the PDN connection, and then send the obtained control plane function entity address to the second AMF entity, so that the second The AMF entity selects the corresponding control plane function entity according to the address of the control plane function entity, which is not specifically limited in this embodiment.
  • the session establishment method provided by the embodiment of the present application can interconnect and establish a corresponding session in the 5GC network slice according to the selected S-NSSAI when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice.
  • the actions of the user plane entity, or the control plane function entity, or the first AMF entity in the foregoing steps S1901 to S1912 may be invoked by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. Execution, the embodiment of the present application does not impose any limitation on this.
  • the session establishment system shown in FIG. 18 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 20 , which is a session establishment provided by the embodiment of the present application.
  • the method includes the following steps:
  • step S2001 in the embodiment of the present application is an optional step, and the step S2001 is not performed in the step S2001.
  • the control plane function entity sends the information of the user plane entity to the NRF entity and the S-NSSAI of the corresponding network slice, so that the NRF entity receives the information of the user plane entity from the control plane function entity and the corresponding network slice S-NSSAI. .
  • the information of the user plane entity and the S-NSSAI of the corresponding network slice may be sent by the user plane entity to the control plane function entity.
  • the information of the user plane entity is the information of the user plane entity corresponding to the PDN connection sent by the user plane entity to the control plane function entity, and correspondingly, the S-NSSAI of the network slice corresponding to the information of the user plane entity corresponds to the PDN connection.
  • the S-NSSAI of the network slice corresponding to the information of the user plane entity; or the information of the user plane entity and the S-NSSAI of the corresponding network slice may also be pre-configured on the control plane function entity, this embodiment of the present application No specific limitation.
  • step S2002 in the embodiment of the present application is an optional step, and the step S2002 is not performed, but the information of the user plane entity and the S-NSSAI of the network slice are configured on the NRF entity by other means. relationship.
  • the business or OA&M device directly configures the information of the user plane entity and the S-NSSAI of the network slice on the NRF during network deployment; or, when the control plane function entity registers with the NRF entity, the control plane function entity
  • the corresponding relationship between the information of all the user plane entities under the jurisdiction and the S-NSSAI of the network slice corresponding to the information of the user plane entity is stored in the NRF entity, which is not specifically limited in this embodiment of the present application.
  • the session establishment method provided by the embodiment of the present application can interconnect and establish a corresponding session in the 5GC network slice according to the selected S-NSSAI when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice.
  • the actions of the user plane entity, or the control plane function entity, or the first AMF entity in the foregoing steps S2001 to S2012 may be invoked by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. Execution, the embodiment of the present application does not impose any limitation on this.
  • the session establishment system shown in FIG. 18 is applied to the 4G network and the 5G network interworking architecture shown in FIG. 1 , as shown in FIG. 21 , which is a session establishment provided by the embodiment of the present application.
  • the method includes the following steps:
  • the terminal sends a registration request to the first AMF entity, so that the first AMF entity receives the registration request from the terminal.
  • the registration request carries the identifier of the terminal.
  • the identifier of the terminal may be, for example, a globally unique temporary identity (GUTI), which is not specifically limited in this embodiment of the present application.
  • GUI globally unique temporary identity
  • the registration request may also carry the NSSAI (requested NSSAI) requested by the terminal, and the location information of the terminal, and the like, which is not specifically limited in this embodiment.
  • NSSAI quested NSSAI
  • the first AMF entity acquires an address of the MME according to the identifier of the terminal, and sends a context request message to the MME, so that the MME receives the context request message from the first AMF entity.
  • the context request message is used to request to acquire the context of the terminal.
  • S2106 The MME sends a context of the terminal to the first AMF entity, so that the first AMF entity receives the context of the terminal from the MME.
  • the context of the terminal includes the first information of the user plane entity corresponding to the PDN connection sent by the control plane function entity to the MME in step S1903 or step S2003.
  • the S-NSSAI of the first network slice corresponding to the PDN connection may be stored in the context of the terminal.
  • the embodiment of the present application does not specifically limit this.
  • the first AMF entity sends a context transmission request to the second AMF entity, so that the second AMF entity receives the context transmission request from the first AMF entity.
  • the context transmission request includes context information of the terminal.
  • the MME may also obtain the information of the control plane function entity corresponding to the PDN connection in the manner shown in FIG. 15, and further include the PDN connection in the context of the terminal sent to the first AMF entity.
  • the information of the corresponding control plane function entity, and the information of the terminal that is sent by the first AMF entity to the second AMF entity, may also include the information of the control plane function entity corresponding to the PDN connection, which is not specifically limited in this embodiment.
  • the other processes of the subsequent handover may include, for example, the second AMF entity selecting a control plane function entity or a visited SMF (V-SMF) entity according to the PDN connection corresponding to the PDN connection or selecting information according to information of the control plane function entity.
  • V-SMF visited SMF
  • the first AMF entity requests the NRF entity to request the S-NSSAI of the first network slice corresponding to the PDN connection according to the first information of the user plane entity corresponding to the PDN connection.
  • the first AMF entity may also request the address of the control plane function entity from the NRF entity according to the FQDN of the control plane function entity corresponding to the PDN connection, and then send the obtained control plane function entity address to the second AMF entity, so that the second The AMF entity selects the corresponding control plane function entity according to the address of the control plane function entity, which is not specifically limited in this embodiment.
  • the session establishment method provided by the embodiment of the present application can interconnect and establish a corresponding session in the 5GC network slice according to the selected S-NSSAI when the terminal switches from the ECN supporting the DCN to the 5GC supporting the network slice.
  • the actions of the user plane entity, or the control plane function entity, or the first AMF entity in the foregoing steps S2101 to S2112 may be invoked by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303. Execution, the embodiment of the present application does not impose any limitation on this.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements.
  • the first mobility management entity and the second mobility management entity include corresponding hardware structures and/or software modules for performing respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform the function module division on the terminal, the first mobility management entity, and the second mobility management entity according to the foregoing method.
  • each function module may be divided according to each function, or two or more functions may be used.
  • the functions are integrated in one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8 shows a schematic structural diagram of the first mobility management entity 80 involved in the above embodiment.
  • the first mobility management entity 80 includes: a first obtaining module 801 and a second acquiring module 802.
  • the first acquiring module 801 is configured to obtain information about a PDN connection that has been established when the terminal accesses the EPC.
  • the second obtaining module 802 is configured to obtain, according to the information of the PDN connection, the S-NSSAI of the network slice corresponding to the PDN connection, where the S-NSSAI of the corresponding network slice of the PDN connection is used to indicate the network slice of the PDU session.
  • the second obtaining module 802 is further configured to obtain information about the second mobility management entity.
  • the second obtaining module 802 is configured to acquire, according to the information about the PDN connection, the S-NSSAI of the network slice corresponding to the PDN connection, where the method is configured to: determine, according to the information of the PDN connection, the network slice corresponding to the PDN connection. S-NSSAI.
  • the information about the PDN connection includes the APN corresponding to the PDN connection
  • the second obtaining module 802 is configured to determine, according to the information of the PDN connection, the S-NSSAI of the network slice corresponding to the PDN connection, including: The S-NSSAI of the network slice corresponding to the PDN connection is determined according to the APN and the correspondence between the pre-configured APN and the S-NSSAI.
  • the correspondence between the pre-configured APN and the S-NSSAI includes a one-to-many relationship between the APN and the S-NSSAI; and the second obtaining module 802 is configured to determine, according to the APN, the pre-configured APN and the S-NSSAI.
  • the S-NSSAI of the corresponding network slice of the PDN connection includes: a priority for each S-NSSAI in a one-to-many relationship according to the pre-configured APN and S-NSSAI, and a network slice indicated by each S-NSSAI At least one of the load information and the NSSAI supported by the set of mobility management entities configured in the first mobility management entity 80, and a one-to-many relationship between the APN and the pre-configured APN and S-NSSAI, determining the network slice corresponding to the PDN connection S-NSSAI.
  • the information of the PDN connection includes information about a control plane function entity corresponding to the PDN connection
  • the second obtaining module 802 is configured to determine, according to the information of the PDN connection, the S of the network slice corresponding to the PDN connection.
  • - NSSAI comprising: determining S-NSSAI of the network slice corresponding to the PDN connection according to the information of the control plane function entity.
  • the information about the PDN connection includes information about a control plane function entity corresponding to the PDN connection
  • the second obtaining module 802 is configured to acquire, according to the information of the PDN connection, the S of the network slice corresponding to the PDN connection.
  • - NSSAI comprising: sending a request message to the control plane function entity according to the information of the control plane function entity, the request message is used to request to obtain the S-NSSAI of the network slice corresponding to the PDN connection; and receiving the functional entity from the control plane
  • the PDN connects to the corresponding network slice of the S-NSSAI.
  • the second obtaining module 802 is further configured to obtain the information of the second mobility management entity, where the information about the second mobile management entity is obtained according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the second obtaining module 802 is configured to obtain the information of the second mobility management entity according to the S-NSSAI of the network slice corresponding to the PDN connection, and the method is configured to: determine, according to the information of the PDN connection, the PDN connection. Corresponding network slice instance; determining information of the second mobility management entity according to information of the S-NSSAI and the network slice instance of the network slice corresponding to the PDN connection.
  • the second obtaining module 802 is configured to acquire the information of the second mobility management entity according to the S-NSSAI of the network slice corresponding to the PDN connection, and the method is configured to: send, to the NSSF entity, the PDN connection.
  • the S-NSSAI of the network slice, the S-NSSAI of the corresponding network slice of the PDN connection is used to determine information of the second mobility management entity; and the information of the second mobility management entity from the NSSF entity is received.
  • the second obtaining module 802 is configured to obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection; and the second obtaining module 802 is further configured to obtain the information of the second mobility management entity, including: And configured to send a slice selection request message to the NSSF entity, where the slice selection request message carries the information of the PDN connection, where the information of the PDN connection is used to determine the information of the second mobility management entity and the S-NSSAI of the network slice corresponding to the PDN connection; receiving from the NSSF The information of the set of candidate mobility management entities of the entity and the S-NSSAI of the network slice corresponding to the PDN connection; selecting the second mobility management entity from the set of candidate mobility management entities according to the information of the set of candidate mobility management entities.
  • the second obtaining module 802 is configured to obtain the S-NSSAI of the network slice corresponding to the PDN connection according to the information of the PDN connection; and the second obtaining module 802 is further configured to acquire information about the second mobility management entity.
  • the method includes: sending a slice selection request message to the NSSF entity, where the slice selection request message carries the information of the PDN connection, where the information of the PDN connection is used to determine the information of the second mobility management entity and the S-NSSAI of the network slice corresponding to the PDN connection;
  • the PDN from the NSSF entity connects the information of the S-NSSAI and the second mobility management entity of the corresponding network slice.
  • the first mobility management entity 80 is different from the second mobility management entity.
  • the first mobility management entity 80 further includes a transceiver module 803.
  • the transceiver module 803 is configured to send a PDN connection to the second mobility management entity.
  • the transceiver module 803 is specifically configured to: send, by using the access device, the S-NSSAI of the network slice corresponding to the PDN connection to the second mobility management entity.
  • the first mobility management entity 80 is the same as the second mobility management entity.
  • the first mobility management entity 80 further includes a transceiver module 803 and an establishing module 804.
  • the transceiver module 803 is configured to send a registration to the terminal. Receiving the message, the registration accept message carries the S-NSSAI of the network slice corresponding to the PDN connection; the transceiver module 803 is further configured to receive a PDU session establishment request from the terminal, where the PDU session establishment request carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • the establishing module 804 is configured to establish a PDU session in the network slice corresponding to the PDN connection according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • the first mobility management entity 80 is the same as the second mobility management entity.
  • the first mobility management entity 80 further includes a transceiver module 803 and an establishing module 804.
  • the transceiver module 803 is configured to send a registration to the terminal.
  • the receiving module 803 is further configured to receive a PDU session establishment request from the terminal, where the PDU session establishment request carries the S-NSSAI of the network slice requested by the terminal and the APN corresponding to the PDN connection requested by the terminal; and the establishing module 804 is configured to: If the S-NSSAI of the network slice requested by the terminal is the same as the S-NSSAI of the network slice corresponding to the pre-stored PDN connection, and the APN corresponding to the PDN connection requested by the terminal is the same as the APN corresponding to the PDN connection, the PDN connection is corresponding.
  • the S-NSSAI of the network slice establishes a PDU session in the network slice corresponding to the PDN connection.
  • the first mobility management entity 80 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the first mobility management entity 80 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the first mobility management entity 80 executes the session establishment method in the above method embodiment.
  • the function/implementation process of the first obtaining module 801, the second obtaining module 802, the transceiver module 803, and the establishing module 804 in FIG. 8 can be invoked by the processor 301 in FIG. 3 to call a computer executing instruction stored in the memory 303.
  • the function/implementation process of the first obtaining module 801, the second obtaining module 802, and the establishing module 804 in FIG. 8 may be implemented by the processor 301 in FIG. 3 calling a computer executing instruction stored in the memory 303, in FIG.
  • the function/implementation process of the transceiver module 803 can be implemented by the communication interface 304 in FIG.
  • the first mobility management entity provided by the embodiment of the present application can be used to perform the foregoing session establishment method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • FIG. 9 shows a schematic structural view of a device 90.
  • the device 90 may be a terminal or a chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the device 90 includes: a receiving module 901 and a sending module 902.
  • the sending module 902 is configured to send a registration request message to the first mobility management entity, where the registration request message carries the identifier of the terminal, where the identifier of the terminal is used to acquire the terminal.
  • the subscription data wherein the subscription data includes information about a PDN connection that has been established when the terminal accesses the EPC;
  • the receiving module 901 is further configured to receive a registration accept message, where the registration accept message carries the S-NSSAI of the network slice corresponding to the PDN connection.
  • the sending module 902 is further configured to send a PDU session establishment request, where the PDU session establishment request carries an S-NSSAI of the network slice corresponding to the PDN connection, where the PDU session establishment request is used to request to establish a PDU session in the network slice corresponding to the PDN connection. .
  • the registration accept message further carries information about the PDN connection that is allowed to be switched; the device 90 further includes a processing module 903, and the processing module 903 is configured to release the EPC except for allowing the handover according to the information of the PDN connection that is allowed to be switched. All PDN connections except the PDN connection.
  • the device 90 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • device 90 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute an instruction by calling a computer stored in the memory 303, so that the device 90 executes the session establishment method in the above method embodiment.
  • the function/implementation process of the receiving module 901, the sending module 902, and the processing module 903 in FIG. 9 can be implemented by the processor 301 in FIG. 3 calling a computer executing instruction stored in the memory 303.
  • the function/implementation process of the processing module 903 in FIG. 9 can be implemented by the processor 301 in FIG. 3 calling the computer execution instruction stored in the memory 303, and the function/implementation of the receiving module 901 and the transmitting module 902 in FIG.
  • the process can be implemented by the communication interface 304 in FIG.
  • the function/implementation process of the receiving module 901 and the sending module 902 can also be implemented by using a pin or a circuit or the like.
  • the memory 303 may be a memory unit within the chip, such as a register, a cache, or the like.
  • the memory 303 may be a storage unit located outside the chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the device provided by the embodiment of the present application can be used to perform the foregoing session establishment method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • FIG. 10 shows a schematic structural diagram of a second mobility management entity 100.
  • the second mobility management entity 100 includes a transceiver module 1001 and a processing module 1002.
  • the transceiver module 1001 is configured to receive an S-NSSAI of a network slice corresponding to a PDN connection that is established when the terminal of the first mobility management entity accesses the EPC, and the transceiver module 1001 is further configured to send a registration accept message to the terminal; 1001 is further configured to receive a PDU session establishment request from the terminal, where the PDU session establishment request is used to request to establish a PDU session in a network slice corresponding to the PDN connection; and the processing module 1002 is configured to: according to the S- of the corresponding network slice of the PDN connection NSSAI establishes a PDU session in the network slice corresponding to the PDN connection.
  • the second mobility management entity 100 is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the second mobility management entity 100 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the second mobility management entity 100 executes the session establishment method in the foregoing method embodiment.
  • the function/implementation process of the transceiver module 1001 and the processing module 1002 in FIG. 10 can be implemented by the processor 301 in FIG. 3 calling a computer execution instruction stored in the memory 303.
  • the function/implementation process of the processing module 1002 in FIG. 10 can be implemented by the processor 301 in FIG. 3 calling the computer execution instruction stored in the memory 303, and the function/implementation process of the transceiver module 1001 in FIG.
  • the communication interface 304 in 3 is implemented.
  • the second mobility management entity provided by the embodiment of the present application can be used to perform the foregoing session establishment method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • the first mobility management entity 80, the device 90, and the second mobility management entity 100 are all presented in a form that divides each functional module in an integrated manner.
  • the embodiments of the present application may also be used to divide the respective functional modules of the first mobility management entity, the device, and the second mobility management entity, which are not specifically limited in this embodiment.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support the first mobility management entity to implement the foregoing session establishment method, for example, acquiring the PDN connection according to the information of the PDN connection.
  • Network sliced S-NSSAI the chip system also includes a memory. The memory is used to save necessary program instructions and data of the first mobility management entity.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support the second mobility management entity to implement the foregoing session establishment method, for example, according to the S-NSSAI of the network slice corresponding to the PDN connection.
  • a PDU session is established in the network slice corresponding to the PDN connection.
  • the chip system also includes a memory. The memory is used to save necessary program instructions and data of the second mobility management entity.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • FIG. 17 shows a schematic structural diagram of the control plane functional entity 170 involved in the above embodiment.
  • the control plane function entity 170 includes a transceiver module 1701 and a processing module 1702.
  • the processing module 1702 is configured to obtain information about a PDN connection that has been established when the terminal accesses the EPC, and an S-NSSAI of the network slice corresponding to the PDN connection.
  • the transceiver module 1701 is configured to send, to the network storage function entity, the information of the PDN connection and the S-NSSAI of the network slice corresponding to the PDN connection, where the first mobility management entity obtains the information from the network storage function entity according to the information of the PDN connection.
  • the PDN is connected to the S-NSSAI of the corresponding network slice, wherein the S-NSSAI of the corresponding network slice of the PDN connection is used to indicate a network slice that establishes a packet data unit PDU session.
  • the transceiver module 1701 is specifically configured to: send the PDN connection information to the network storage function entity and the network slice corresponding to the PDN connection in the process of establishing the PDN connection or in the process of establishing the PDU session. -NSSAI.
  • the transceiver module 1701 is further configured to send information about the PDN connection to a third mobility management entity in the EPC, where the third mobility management entity sends the information of the PDN connection to the first mobility management entity.
  • the processing module 1702 is specifically configured to determine, by using the S-NSSAI corresponding to the PDU session, an S-NSSAI of the network slice corresponding to the PDN connection when the PDU session is switched to the EPC.
  • FIG. 10 shows a schematic structural diagram of a second mobility management entity 100.
  • the second mobility management entity 100 includes a transceiver module 1001 and a processing module 1002.
  • the transceiver module 1001 is configured to receive an S-NSSAI of a network slice corresponding to a PDN connection that is established when the terminal of the first mobility management entity accesses the EPC, and the transceiver module 1001 is further configured to send a registration accept message to the terminal; 1001 is further configured to receive a PDU session establishment request from the terminal, where the PDU session establishment request is used to request to establish a PDU session in a network slice corresponding to the PDN connection; and the processing module 1002 is configured to: according to the S- of the corresponding network slice of the PDN connection NSSAI establishes a PDU session in the network slice corresponding to the PDN connection.
  • control plane function entity 170 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the control plane functional entity 170 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the control plane function entity 170 executes the session establishment method in the above method embodiment.
  • the function/implementation process of the transceiver module 1701 and the processing module 1702 in FIG. 17 can be implemented by the processor 301 in FIG. 3 calling a computer execution instruction stored in the memory 303.
  • the function/implementation process of the processing module 1702 in FIG. 17 can be implemented by the processor 301 in FIG. 3 calling the computer execution instructions stored in the memory 303, and the function/implementation process of the transceiver module 1701 in FIG.
  • the communication interface 304 in 3 is implemented.
  • control plane function provided by the embodiment of the present application can be used to perform the above-mentioned session establishment method. Therefore, the technical effects of the method can be referred to the foregoing method embodiments, and details are not described herein.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support a control plane function entity to implement the foregoing session establishment method, for example, acquiring a PDN connection established when the terminal accesses the EPC.
  • the information and the S-NSSAI of the network slice corresponding to the PDN connection are included in the chip system.
  • the chip system also includes a memory. This memory is used to store the necessary program instructions and data for the control plane function entity.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • FIG. 22 shows a schematic structural diagram of a network storage functional entity 220.
  • the network storage function entity 220 includes a processing module 2201 and a transceiver module 2202.
  • the transceiver module 2202 is configured to receive the first information of the user plane entity corresponding to the PDN connection of the first mobility management entity, and the processing module 2201 is configured to determine, according to the first information, the S of the first network slice corresponding to the PDN connection.
  • the transceiver module is further configured to send the S-NSSAI of the first network slice to the first mobility management entity.
  • the transceiver module 2202 is further configured to receive the first information from the user plane entity and the S-NSSAI of the first network slice corresponding to the first information.
  • the network storage function entity 220 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the network storage function entity 220 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the network storage function entity 220 executes the session establishment method in the above method embodiment.
  • the function/implementation process of the transceiver module 2202 and the processing module 2201 in FIG. 22 can be implemented by the processor 301 in FIG. 3 calling a computer execution instruction stored in the memory 303.
  • the function/implementation process of the processing module 2201 in FIG. 22 can be implemented by the processor 301 in FIG. 3 calling the computer execution instructions stored in the memory 303, and the function/implementation process of the transceiver module 2202 in FIG.
  • the communication interface 304 in 3 is implemented.
  • the network storage function entity 220 provided in this embodiment can perform the foregoing session establishment method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • the embodiment of the present application further provides a device (for example, the device may be a chip system), where the device includes a processor, configured to support a network storage function entity to implement the foregoing authentication method, for example, according to the first information,
  • the PDN connects to the S-NSSAI of the corresponding first network slice.
  • the device also includes a memory. This memory is used to store the necessary program instructions and data for the network storage function entity. Of course, the memory may also not be in the device.
  • the device is a chip system, it may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • FIG. 23 shows a schematic structural diagram of a user plane entity 230.
  • the user plane entity 230 includes a processing module 2301 and a transceiver module 2302.
  • the processing module 2301 is configured to acquire the information of the user plane entity and the S-NSSAI of the network slice corresponding to the information of the user plane entity
  • the sending and receiving module is configured to send, to the network storage function entity, the information of the user plane entity and
  • the S-NSSAI of the network slice is obtained by the first mobility management entity according to the first information of the user plane entity corresponding to the PDN connection, and the S-NSSAI of the first network slice corresponding to the PDN connection is obtained from the network storage function entity.
  • the transceiver module 2302 is specifically configured to: when the user plane entity registers with the network storage function entity or during the establishment of the PDN connection or during the establishment of the packet data unit PDU session, the network storage function is The entity sends the information of the user plane entity and the S-NSSAI of the network slice.
  • the user plane entity 230 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the user plane entity 230 can take the form shown in FIG.
  • the processor 301 in FIG. 3 can execute the instruction by calling the computer stored in the memory 303, so that the user plane entity 230 executes the session establishment method in the above method embodiment.
  • the function/implementation process of the transceiver module 2302 and the processing module 2301 in FIG. 23 can be implemented by the processor 301 in FIG. 3 calling a computer execution instruction stored in the memory 303.
  • the function/implementation process of the processing module 2301 in FIG. 23 can be implemented by the processor 301 in FIG. 3 calling the computer execution instruction stored in the memory 303, and the function/implementation process of the transceiver module 2302 in FIG.
  • the communication interface 304 in 3 is implemented.
  • the user plane entity 230 provided in this embodiment can perform the above-mentioned session establishment method. Therefore, the technical effects of the method can be referred to the foregoing method embodiments, and details are not described herein again.
  • the embodiment of the present application further provides a device (for example, the device may be a chip system), where the device includes a processor, configured to support a user plane entity to implement the foregoing authentication method, for example, acquiring information about the user plane entity. And an S-NSSAI of the network slice corresponding to the information of the user plane entity.
  • the device also includes a memory. This memory is used to store the necessary program instructions and data for the user plane entity. Of course, the memory may also not be in the device.
  • the device is a chip system, it may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供会话建立方法、设备及系统，使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。方法包括：第一移动管理实体获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI，所述PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。

Description

会话建立方法、设备及系统
本申请要求了2017年10月16日提交的、申请号为201710963960.1、发明名称为“会话建立方法、设备及系统”的中国申请的优先权，以及2017年11月27日提交的、申请号为201711208402.0、发明名称为“会话建立方法、设备及系统”的中国申请的优先权，以及2018年5月21日提交的、申请号为201810491244.2、发明名称为“会话建立方法、设备及系统”,以及2018年10月8日提交的、申请号为201811169443.8、发明名称为“会话建立方法、设备及系统”的中国申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及会话建立方法、设备及系统。
背景技术
专用核心网(dedicated core network，DCN)是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)在第四代(4th generation，4G)中定义的用于服务特定类型业务的专用网络；而网络切片是3GPP在第五代(5rd generation，5G)中定义的DCN的升级版本，是一个用于支持特定网络能力与网络特性的逻辑隔离的网络，可以端到端(end to end，E2E)的包括整个网络，也可以部分网络功能在多个网络切片中共享，是满足3GPP提出的5G移动通信技术关于网络差异化需求的关键技术。
其中，网络切片与DCN的区别主要在于：一个DCN是一个专用网络，DCN之间没有关联，终端只能接入一个DCN；而多个网络切片可共享一组接入和移动性管理功能(access and mobility management function，AMF)实体，终端可同时接入多个共享同一组AMF实体的网络切片。同时，在网络切片引入了网络切片选择辅助信息(network slice selection assistance information，NSSAI)，当终端接入5G核心网(5G core network，5GC)时，终端提供请求的NSSAI，网络根据NSSAI为终端选择对应的网络切片，并且网络根据终端请求的NSSAI确定终端允许接入的NSSAI，即Allowed NSSAI。
然而，由于在DCN中建立分组数据网络(packet data network，PDN)连接需要接入点名称(access point name，APN)参数，而在网络切片中创建协议数据单元(protocol data unit，PDU)会话时需要数据网络名称(data network name，DNN)和单NSSAI(single NSSAI，S-NSSAI)，虽然在现有的协议中，APN与DNN是等价的，但是，在终端从支持DCN的演进的分组核心网(evolved packet core，EPC)切换到支持网络切片的5GC时，如何确定S-NSSAI，以使得可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话，目前并没有相关的解决方案。
发明内容
本申请实施例提供会话建立方法、设备及系统，使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供一种会话建立方法，该方法包括：第一移动管理实体获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；该第一移动管理实体根据 该PDN连接的信息，获取该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。基于本申请实施例提供的会话建立方法，由于第一移动管理实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，因此第一移动管理实体或者第二移动管理实体接收来自终端的PDU会话建立请求之后，可以根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在第一方面第一种可能的设计中，该方法还包括：该第一移动管理实体获取第二移动管理实体的信息。其中，本申请实施例中的第一移动管理实体也可以称之为初始移动管理实体，第二移动管理实体也可以称之为目标移动管理实体，本申请实施例对此不作具体限定。
在第一方面第二种可能的设计中，该第一移动管理实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体根据该PDN连接的信息，确定该PDN连接对应的网络切片的S-NSSAI。其中，该PDN连接的信息例如可以包括该PDN连接对应的接入点名称APN或者该PDN连接对应的控制面功能实体的信息，本申请实施例对此不作具体限定。
在第一方面第三种可能的设计中，该PDN连接的信息包括该PDN连接对应的接入点名称APN；该第一移动管理实体根据该PDN连接的信息，确定该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体根据该APN，以及预先配置的APN和S-NSSAI的对应关系，确定该PDN连接对应的网络切片的S-NSSAI。
在第一方面第四种可能的设计中，该预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对多关系；该第一移动管理实体根据该APN，以及预先配置的APN和S-NSSAI的对应关系，确定该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体根据该预先配置的APN和S-NSSAI的一对多关系中每个S-NSSAI的优先级、该每个S-NSSAI所指示的网络切片的负荷信息、以及该第一移动管理实体中配置的移动管理实体集合所支持的NSSAI中的至少一个，以及该APN和该预先配置的APN和S-NSSAI的一对多关系，确定该PDN连接对应的网络切片的S-NSSAI。
在第一方面第五种可能的设计中，该PDN连接的信息包括该PDN连接对应的控制面功能实体的信息；该第一移动管理实体根据该PDN连接的信息，确定该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体根据该控制面功能实体的信息，确定该PDN连接对应的网络切片的S-NSSAI。
在第一方面第六种可能的设计中，一种可能的设计中，该PDN连接的信息包括该PDN连接对应的控制面功能实体的信息；该第一移动管理实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体根据该控制面功能实体的信息，向该控制面功能实体发送请求消息，该请求消息用于请求获取该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体接收来自该控制面功能实体的该PDN连接对应的网络切片的S-NSSAI。
在一种可能的设计中，第一移动管理实体根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，包括：第一移动管理实体向网络存储功能实体发送该PDN 连接的信息；第一移动管理实体接收来自网络存储功能实体的该PDN连接对应的网络切片的S-NSSAI。也就是说，本申请实施例中，第一移动管理实体可以从网络存储功能实体中获取该PDN连接对应的网络切片的S-NSSAI。
在一种可能的设计中，第一移动管理实体获取终端接入到EPC时已建立的PDN连接的信息，包括：第一移动管理实体接收来自EPC中的第三移动管理实体的该PDN连接的信息。也就是说，本申请实施例中，第一移动管理实体可以从EPC中的第三移动管理实体中获取该PDN连接的信息。
可选的，该控制面功能实体的信息包括该控制面功能实体的网络之间互连的协议IP地址或全量域名FQDN。
在第一方面第七种可能的设计中，该第一移动管理实体获取第二移动管理实体的信息，包括：该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，获取该第二移动管理实体的信息。
可选的，考虑到一个网络切片中可能包括一个或多个网络切片实例，因此该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，获取该第二移动管理实体的信息，包括：该第一移动管理实体根据PDN连接的信息，确定PDN连接对应的网络切片实例；该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI和该网络切片实例的信息，确定第二移动管理实体的信息。也就是说，本申请实施例中，可以由第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI确定第二移动管理实体的信息。
或者，可选的，该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，获取该第二移动管理实体的信息，包括：该第一移动管理实体向网络切片选择功能NSSF实体发送该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于确定该第二移动管理实体的信息；该第一移动管理实体接收来自该NSSF实体的该第二移动管理实体的信息。也就是说，本申请实施例中，可以由NSSF实体根据该PDN连接对应的网络切片的S-NSSAI确定第二移动管理实体的信息。
在第一方面第八种可能的设计中，该第一移动管理实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI；以及，该第一移动管理实体获取第二移动管理实体的信息，包括：该第一移动管理实体向NSSF实体发送切片选择请求消息，该切片选择请求消息携带该PDN连接的信息，该PDN连接的信息用于确定该第二移动管理实体的信息和该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体接收来自该NSSF实体的候选移动管理实体集合的信息和该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体根据候选移动管理实体集合的信息，从该候选移动管理实体集合中选择该第二移动管理实体。也就是说，本申请实施例中，可以由NSSF实体确定该PDN连接对应的网络切片的S-NSSAI和第二移动管理实体所在的候选移动管理实体集合的信息。
在第一方面第九种可能的设计中，该第一移动管理实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI；以及，该第一移动管理实体获取第二移动管理实体的信息，包括：该第一移动管理实体向NSSF实体发送切片选择请求消息，该切片选择请求消息携带该PDN连接的信息，该PDN连接的信息用于确定该第二移动管理实体的信息和该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体接收来自该NSSF实体的该PDN连接对应的网络切片的S-NSSAI和该第二移动管理实体的信息。也就是说，本申请实施例中，可 以由NSSF实体确定该PDN连接对应的网络切片的S-NSSAI和第二移动管理实体的信息。
在另一种可能的设计中，该第一移动管理实体与该第二移动管理实体不同；该方法还包括：该第一移动管理实体向该第二移动管理实体发送该PDN连接对应的网络切片的S-NSSAI。
在另一种可能的设计中，该第一移动管理实体向该第二移动管理实体发送该PDN连接对应的网络切片的S-NSSAI，包括：该第一移动管理实体通过接入设备向该第二移动管理实体发送该PDN连接对应的网络切片的S-NSSAI。也就是说，可以通过接入设备重路由至第二移动管理实体。
在另一种可能的设计中，该方法还包括：该第二移动管理实体向该终端发送注册接受消息；该第二移动管理实体接收来自该终端的PDU会话建立请求，该PDU会话建立请求用于请求在该PDN连接对应的网络切片中建立PDU会话；该第二移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在另一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息，该注册接受消息携带该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体接收来自该终端的PDU会话建立请求，该PDU会话建立请求携带该PDN连接对应的网络切片的S-NSSAI；该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在另一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息；该第一移动管理实体接收来自该终端的PDU会话建立请求，该PDU会话建立请求携带该终端请求的网络切片的S-NSSAI和该终端请求的PDN连接对应的APN；在该终端请求的网络切片的S-NSSAI与预先存储的该PDN连接对应的网络切片的S-NSSAI相同，且该终端请求的PDN连接对应的APN与该PDN连接对应的APN相同的情况下，该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在另一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息；该第一移动管理实体接收来自该终端的PDU会话建立请求，该PDU会话建立请求携带该PDN连接的信息；该第一移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
第二方面，提供一种会话建立方法，该方法包括：终端向第一移动管理实体发送注册请求消息，该注册请求消息携带该终端的标识，该终端的标识用于获取该终端的签约数据，其中，该签约数据包括在该终端接入到分组核心网EPC时已建立的分组数据网络 PDN连接的信息；该终端接收注册接受消息，该注册接受消息携带该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；该终端发送分组数据单元PDU会话建立请求，该PDU会话建立请求携带该PDN连接对应的网络切片的S-NSSAI，该PDU会话建立请求用于请求在该PDN连接对应的网络切片中建立PDU会话。基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在一种可能的设计中，该注册接受消息还携带允许进行切换的PDN连接的信息；该方法还包括：该终端根据该允许进行切换的PDN连接的信息，释放该EPC中除该允许进行切换的PDN连接之外的其他所有PDN连接。这样可以节省系统资源。
第三方面，提供一种会话建立方法，该方法包括：第二移动管理实体接收来自第一移动管理实体的终端接入到分组核心网EPC时已建立的分组数据网络PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；该第二移动管理实体向终端发送注册接受消息；该第二移动管理实体接收来自该终端的分组数据单元PDU会话建立请求，该PDU会话建立请求用于请求在该PDN连接对应的网络切片中建立PDU会话；该第二移动管理实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。基于本申请实施例提供的会话建立方法，由于第二移动管理实体可以接收来自第一移动管理实体的该PDN连接对应的网络切片的S-NSSAI，并在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
第四方面，提供了一种第一移动管理实体，该第一移动管理实体具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，提供了一种第一移动管理实体，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该第一移动管理实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该第一移动管理实体执行如上述第一方面中任一所述的会话建立方法。
第六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项所述的会话建立方法。
第七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项所述的会话建立方法。
第八方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持第一移动管理实体实现上述方面中所涉及的功能，例如支持第一移动管理实体根据PDN连接的信息，获取PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第一移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第四方面至第八方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第九方面，提供了一种终端，该终端具有实现上述第一方面所述的方法的功能。该功能 可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，提供了一种终端，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该终端运行时，该处理器执行该存储器存储的该计算机执行指令，以使该终端执行如上述第二方面中任一所述的会话建立方法。
第十一方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项所述的会话建立方法。
第十二方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项所述的会话建立方法。
第十三方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持终端实现上述方面中所涉及的功能，例如支持终端发送分组数据单元PDU会话建立请求，该PDU会话建立请求携带PDN连接对应的网络切片的S-NSSAI，该PDU会话建立请求用于请求在该PDN连接对应的网络切片中建立PDU会话。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第九方面至第十三方面中任一种设计方式所带来的技术效果可参见第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第十四方面，提供了一种第二移动管理实体，该第二移动管理实体具有实现上述第三方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十五方面，提供了一种第二移动管理实体，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该第二移动管理实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该第一移动管理实体执行如上述第三方面中任一所述的会话建立方法。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第三方面中任意一项所述的会话建立方法。
第十七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第三方面中任意一项所述的会话建立方法。
第十八方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持第二移动管理实体实现上述方面中所涉及的功能，例如支持第二移动管理实体根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第二移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十四方面至第十八方面中任一种设计方式所带来的技术效果可参见第三方面中不同设计方式所带来的技术效果，此处不再赘述。
第十九方面，提供一种会话建立系统，该会话建立系统包括第一移动管理实体和第二移动管理实体；该第一移动管理实体，用于获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；该第一移动管理实体，还用于根据该PDN连接的信息，获取该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI后，向该第二移动管理实体发送该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片；该第二移动管理实体，用于接收来自该第一移动管理 实体的该PDN连接对应的网络切片的S-NSSAI；该第二移动管理实体，还用于向终端发送注册接受消息后，接收来自该终端的分组数据单元PDU会话建立请求，并根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。
第二十方面，提供了一种会话建立方法，该方法包括：控制面功能实体确定会话对应的网络切片的单网络切片选择辅助信息S-NSSAI；该控制面功能实体将该会话对应的网络切片的S-NSSAI存储至用户数据管理实体；第一移动管理实体从该用户数据管理实体中获取该会话对应的网络切片的S-NSSAI，该会话对应的网络切片的S-NSSAI用于指示建立会话的网络切片。基于该会话建立方法，由于第一移动管理实体可以从用户数据管理实体中获取该会话对应的网络切片的S-NSSAI，因此第一移动管理实体或第二移动管理实体可以根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
在种可能的设计中，该控制面功能实体确定会话对应的网络切片的S-NSSAI，包括：该控制面功能实体将该控制面功能实体所支持的S-NSSAI的其中一个确定为该会话对应的网络切片的S-NSSAI。
在一种可能的设计中，该方法还包括：该第一移动管理实体获取第二移动管理实体的信息。其中，本申请实施例中的第一移动管理实体也可以称之为初始移动管理实体，第二移动管理实体也可以称之为目标移动管理实体，本申请实施例对此不作具体限定。
其中，第一移动管理实体获取第二移动管理实体的信息的方式可参考第一方面第七种可能的设计至第一方面第九种可能的设计中任一种可能的设计中的相关描述，在此不再赘述。
在一种可能的设计中，该第一移动管理实体与该第二移动管理实体不同；该方法还包括：该第一移动管理实体向该第二移动管理实体发送该会话对应的网络切片的S-NSSAI。
在一种可能的设计中，该第一移动管理实体向该第二移动管理实体发送该会话对应的网络切片的S-NSSAI，包括：该第一移动管理实体通过接入设备向该第二移动管理实体发送该会话对应的网络切片的S-NSSAI。也就是说，可以通过接入设备重路由至第二移动管理实体。
在一种可能的设计中，该方法还包括：该第二移动管理实体向该终端发送注册接受消息；该第二移动管理实体接收来自该终端的会话建立请求，该会话建立请求用于请求在该会话对应的网络切片中建立会话；该第二移动管理实体根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
在一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息，该注册接受消息携带该会话对应的网络切片的S-NSSAI；该第一移动管理实体接收来自该终端的会话建立请求，该会话建立请求携带该会话对应的网络切片的S-NSSAI；该第一移动管理实体根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
在一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息；该第一移动管理实体接收来自该终端的会话建立请求，该会话建立请求携带该终端请求的网络切片的S-NSSAI和该终端请求的会话对应的会话信息；在该终端请求的网络切片的S-NSSAI与预先存储的该会话对应的网络切片的S-NSSAI相同，且该终端请求的会话对应的会话信息与该会话对应的会话信息相同的情况下，该第一移动管理实体根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
在一种可能的设计中，该第一移动管理实体与该第二移动管理实体相同；该方法还包括：该第一移动管理实体向该终端发送注册接受消息；该第一移动管理实体接收来自该终端的会话建立请求，该会话建立请求携带该会话的信息；该第一移动管理实体根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
第二十一方面，提供一种会话建立系统，该会话建立系统包括控制面功能实体和第一移动管理实体；该控制面功能实体，用于确定会话对应的网络切片的单网络切片选择辅助信息S-NSSAI，并将该会话对应的网络切片的S-NSSAI存储至用户数据管理实体；该第一移动管理实体，用于从该用户数据管理实体中获取该会话对应的网络切片的S-NSSAI，其中，该会话对应的网络切片的S-NSSAI用于指示建立会话的网络切片。
第二十二方面，提供了一种会话建立方法，该方法包括：控制面功能实体获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息以及该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；控制面功能实体向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，由第一移动管理实体根据该PDN连接的信息从该网络存储功能实体中获取该PDN连接对应的网络切片的S-NSSAI，其中，该PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。基于该方案，由于第一AMF实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，因此第一AMF实体可以在接收来自MME的切换请求之后，根据该PDN连接对应的网络切片的S-NSSAI，获取第二AMF实体信息，进而可以在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
在一种可能的设计中，控制面功能实体向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，包括：控制面功能实体在该PDN连接建立的过程中或者在该PDU会话建立的过程中，向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
在一种可能的设计中，本申请实施例提供的会话建立方法还可以包括：控制面功能实体向该EPC中的第三移动管理实体发送该PDN连接的信息，由该第三移动管理实体向 该第一移动管理实体发送该PDN连接的信息。基于该方案，第一移动管理实体可以获取该PDN连接的信息。
在一种可能的设计中，控制面功能实体获取该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI，包括：控制面功能实体将该PDU会话对应的S-NSSAI确定为该PDU会话切换到该EPC时该PDN连接对应的网络切片的S-NSSAI。基于该方案，控制面功能实体可以获取该PDN连接对应的网络切片的S-NSSAI。
第二十三方面，提供了一种控制面功能实体，该控制面功能实体具有实现上述第三方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第二十四方面，提供了一种控制面功能实体，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该控制面功能实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该第一移动管理实体执行如上述第三方面中任一所述的会话建立方法。
第二十五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第三方面中任意一项所述的会话建立方法。
第二十六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第三方面中任意一项所述的会话建立方法。
第二十七方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持控制面功能实体实现上述方面中所涉及的功能，例如支持控制面功能实体根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存控制面功能实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第二十三方面至第二十七方面中任一种设计方式所带来的技术效果可参见第二十二方面中不同设计方式所带来的技术效果，此处不再赘述。
第二十八方面，提供一种会话建立系统，该会话建立系统包括：控制面功能实体和第一移动管理实体；控制面功能实体，用于获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息以及该PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；控制面功能实体，还用于向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI；第一移动管理实体，用于向该网络存储功能实体发送该PDN连接的信息，该PDN连接的信息用于确定该PDN连接对应的网络切片的S-NSSAI；第一移动管理实体，用于接收来自该网络存储功能实体的该PDN连接对应的网络切片的S-NSSAI。其中，第二十八方面的技术效果可参考第二十二方面，在此不再赘述。
第二十九方面，提供一种会话建立方法，该方法包括：网络存储功能实体接收来自第一移动管理实体的分组数据网络PDN连接对应的用户面实体的第一信息；该网络存储功能实体根据该第一信息，确定该PDN连接对应的第一网络切片的单网络切片选择辅助信息S-NSSAI；该网络存储功能实体向该第一移动管理实体发送该第一网络切片的S-NSSAI。基于本申请实施例提供的会话建立方法，由于第一移动管理实体可以根据PDN连接对应的用户面实体的第一信息，获取该PDN连接对应的第一网络切片的S-NSSAI。因此，第一移动管理实体可以在接收切换请求或者注册请求之后，根据该PDN连接对应的第一网络切片的S-NSSAI，获取第二移动管理实体的信息，进而可以在相应的第一网 络切片中建立PDU会话。也就是说，基于该方案，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中互通并建立相应会话。
在一种可能的设计中，在该网络存储功能实体接收来自第一移动管理实体的PDN对应的用户面实体的第一信息之前，该方法还包括：该网络存储功能实体接收来自该用户面实体的该第一信息和与该第一信息对应的该第一网络切片的S-NSSAI。这样，可选的，网络存储功能可以存储第一信息和第一网络切片的S-NSSAI的对应关系。进而，网络存储功能实体获取第一信息之后，可以查询该对应关系，确定与第一信息对应的第一网络切片的S-NSSAI，本申请实施例对此不作具体限定。
第三十方面，提供了一种会话建立方法，该方法包括：用户面实体获取该用户面实体的信息以及与该用户面实体的信息对应的网络切片的单网络切片选择辅助信息S-NSSAI；该用户面实体向网络存储功能实体发送该用户面实体的信息以及该网络切片的S-NSSAI，由第一移动管理实体根据分组数据网络PDN对应的用户面实体的第一信息，从该网络存储功能实体中获取该PDN连接对应的第一网络切片的S-NSSAI。基于本申请实施例提供的会话建立方法，由于第一移动管理实体可以根据PDN连接对应的用户面实体的第一信息，获取该PDN连接对应的第一网络切片的S-NSSAI。因此，第一移动管理实体可以在接收切换请求或者注册请求之后，根据该PDN连接对应的第一网络切片的S-NSSAI，获取第二移动管理实体的信息，进而可以在相应的第一网络切片中建立PDU会话。也就是说，基于该方案，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中互通并建立相应会话。
在一种可能的设计中，该用户面实体向网络存储功能实体发送该用户面实体的信息以及该网络切片的S-NSSAI，包括：该用户面实体在该用户面实体向该网络存储功能实体注册过程中或者该PDN连接建立的过程中或者在分组数据单元PDU会话建立的过程中，向该网络存储功能实体发送该用户面实体的信息以及该网络切片的S-NSSAI。
第三十一方面，提供了一种网络存储功能实体，该网络存储功能实体具有实现上述第二十九方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三十二方面，提供了一种网络存储功能实体，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该网络存储功能实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该网络存储功能实体执行如上述第二十九方面中任一项所述的会话建立方法。
第三十三方面，提供了一种网络存储功能实体，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第二十九方面中任一项所述的会话建立方法。
第三十四方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二十九方面中任一项所述的会话建立方法。
第三十五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二十九方面中任一项所述的会话建立方法。
第三十六方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理 器，用于支持网络存储功能实体实现上述第二十九方面中所涉及的功能，例如根据第一信息，确定该PDN连接对应的第一网络切片的S-NSSAI。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存网络存储功能实体必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三十一方面至第三十六方面中任一种设计方式所带来的技术效果可参见第二十九方面中不同设计方式所带来的技术效果，此处不再赘述。
第三十七方面，提供了一种用户面实体，该用户面实体具有实现上述第三十方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三十八方面，提供了一种用户面实体，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该用户面实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该用户面实体执行如上述第三十方面中任一项所述的会话建立方法。
第三十九方面，提供了一种用户面实体，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第三十方面中任一项所述的会话建立方法。
第四十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第三十方面中任一项所述的会话建立方法。
第四十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第三十方面中任一项所述的会话建立方法。
第四十二方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持用户面实体实现上述第三十方面中所涉及的功能，例如根据第一信息，确定该PDN连接对应的第一网络切片的S-NSSAI。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存用户面实体必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三十七方面至第四十二方面中任一种设计方式所带来的技术效果可参见第三十方面中不同设计方式所带来的技术效果，此处不再赘述。
第四十三方面，提供了一种会话建立系统，该会话建立系统包括：第一移动管理实体和网络存储功能实体；该第一移动管理实体，用于向该网络存储功能实体发送PDN连接对应的用户面实体的第一信息；该网络存储功能实体，用于接收来自该第一移动管理实体的该第一信息；该网络存储功能实体，还用于根据该第一信息，确定该PDN连接对应的第一网络切片的单网络切片选择辅助信息S-NSSAI；该网络存储功能实体，还用于向该第一移动管理实体发送该第一网络切片的S-NSSAI；该第一移动管理实体，还用于接收来自该网络存储功能实体的该第一网络切片的S-NSSAI。
在一种可能的设计中，该系统还包括用户面实体；该用户面实体，用于向该网络存储功能实体发送该第一信息和与该第一信息对应的该第一网络切片的S-NSSAI；该网络存储功能实体，用于接收来自该用户面实体的该第一信息和与该第一信息对应的该第一网络切片的S-NSSAI。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为现有的4G网络和5G网络互通架构的示意图；
图2为本申请实施例提供的会话建立系统的架构示意图；
图3为本申请实施例提供的通信设备的硬件结构示意图；
图4为本申请实施例提供的会话建立方法的流程示意图一；
图5为本申请实施例提供的会话建立方法的流程示意图二；
图6为本申请实施例提供的会话建立方法的流程示意图三；
图7为本申请实施例提供的会话建立方法的流程示意图四；
图8为本申请实施例提供的第一移动管理实体的结构示意图；
图9为本申请实施例提供的装置的结构示意图；
图10为本申请实施例提供的第二移动管理实体的结构示意图；
图11为本申请实施例提供的会话建立系统的另一种架构示意图；
图12为本申请实施例提供的会话建立方法的流程示意图五；
图13为本申请实施例提供的会话建立方法的流程示意图六；
图14为本申请实施例提供的会话建立系统的另一种架构示意图；
图15为本申请实施例提供的会话建立方法的流程示意图七；
图16为本申请实施例提供的会话建立方法的流程示意图八；
图17为本申请实施例提供的控制面功能实体的结构示意图；
图18为本申请实施例提供的会话建立系统的另一种架构示意图；
图19为本申请实施例提供的会话建立方法的流程示意图九；
图20为本申请实施例提供的会话建立方法的流程示意图十；
图21为本申请实施例提供的会话建立方法的流程示意图十一；
图22为本申请实施例提供的网络存储功能实体的结构示意图；
图23为本申请实施例提供的用户面实体的结构示意图。
具体实施方式
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
NSSAI：
NSSAI中包括多个S-NSSAI。S-NSSAI由服务类型(slice/service type，SST)和切片区分器(slice differentiator，SD)组成。其中，SST包括标准化和运营商自定义的类型；SD是补充SST的可选信息，以区分相同SST的多个网络切片。23.501标准中定义的NSSAI的类型和作用如表一所示。
表一
Figure PCTCN2018109971-appb-000001
4G网络和5G网络互通架构：
如图1所示，为现有的4G网络和5G网络互通架构的示意图。其中，4G网络与5G网络共用用户面功能(user plane function，UPF)实体+PDN网关用户面功能(PDN  gateway user plane function，PGW-U)实体、会话管理功能(session management function，SMF)实体+PDN网关控制面功能(PDN gateway control plane function，PGW-C)实体、策略控制功能(policy control function，PCF)实体+策略和计费规则功能(policy and charging rules function，PCRF)实体、归属签约用户服务器(home subscriber server，HSS)+统一数据管理(unified data management，UDM)实体。这里“+”表示合设，UPF为5G网络的用户面功能，PGW-U是与UPF对应的4G网络的网关用户面功能，SMF是5G网络的会话管理功能，PGW-C是与SMF对应的4G网络中的网关控制面功能，PCF是5G网络的策略控制功能、PCRF是与PCF对应的4G网络的策略计费规则功能。本申请实施例中，为方便表述，将HSS+UDM实体称之为用户数据管理实体，将PGW-C实体+SMF实体称之为控制面功能实体，将UPF实体+PGW-U实体称之为用户面实体，在此进行统一说明，以下不再赘述。当然，上述合设后的网络设备也可以用其他名称，本申请实施例对此不作具体限定。
此外，如图1所示，上述4G网络和5G网络互通架构中还可以包括4G网络中的移动性管理实体(Mobility Management Entity，MME)和服务网关(Serving Gateway，SGW)，以及，5G网络中的AMF实体。
其中，终端通过演进型通用陆地无线接入网(evolved universal terrestrial radio access network，E-UTRAN)设备接入4G网络，终端通过下一代无线接入网(next generation radio access network，NG-RAN)设备接入5G网络。E-UTRAN设备通过S1-MME接口与MME通信，E-UTRAN设备通过S1-U接口与SGW通信，MME通过S11接口与SGW通信，MME通过S6a接口与用户数据管理实体通信，MME通过N26接口与AMF实体通信，SGW通过S5-U接口与PGW-U实体+UPF实体通信，SGW通过S5-C接口与PGW-C实体+SMF实体通信，PGW-U实体+UPF实体通过N3接口与NG-RAN设备通信，PGW-U实体+UPF实体通过N4接口与PGW-C实体+SMF实体通信，PGW-C实体+SMF实体通过N7接口与PCRF实体+PCF实体通信，HSS+UDM实体通过N10接口与PGW-C实体+SMF实体通信，HSS+UDM实体通过N8接口与AMF实体通信，PCRF实体+PCF实体通过N15接口与AMF实体通信，PGW-C实体+SMF实体通过N11接口与AMF实体通信，AMF实体通过N2接口与NG-RAN设备通信，AMF实体通过N1接口与终端通信。
需要说明的是，图1中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，5G网络中的NG-RAN设备也可以称之为接入设备，该接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等，本申请实施例对此不作具体限定。
当然，4G网络和5G网络中还可以有其它的网元，比如，4G网络中还可以包括通用分组无线系统(general packet radio system，GPRS)业务支撑节点(serving GPRS support node，SGSN)等，5G网络中还可以包括鉴权服务功能(authentication server function，AUSF)实体、网络切片选择功能(network slice selection function，NSSF)实体以及网络功能存储功能(network function repository function，NRF)网元等， 本申请实施例对此不作具体限定。
APN：
终端在发起分组业务时可向MME提供APN。MME根据终端所提供的APN，通过域名服务器(domain name server，DNS)进行域名解析，从而获取到PGW的网络之间互连的协议(internet protocol，IP)地址，将用户接入到APN对应的PDN中。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图2所示，为本申请实施例提供的一种会话建立系统20，该会话建立系统20包括第一移动管理实体201和第二移动管理实体202。
其中，第一移动管理实体201，用于获取终端接入到EPC时已建立的PDN连接的信息，并根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI后，向第二移动管理实体202发送该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于指示建立PDU会话的网络切片。
第二移动管理实体202，用于接收来自第一移动管理实体201的该PDN连接对应的网络切片的S-NSSAI，并向终端发送注册接受消息。
第二移动管理实体202，还用于在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。
可选的，本申请实施例中的第一移动管理实体201和第二移动管理实体202可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一移动管理实体201也可以称之为初始移动管理实体，第二移动管理实体202也可以称之为目标移动管理实体，在此进行统一说明，以下不再赘述。
基于本申请实施例提供的会话建立系统，由于第一移动管理实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，并将该PDN连接对应的网络切片的S-NSSAI发送给第二移动管理实体，因此第二移动管理实体可以接收来自第一移动管理实体的该PDN连接对应的网络切片的S-NSSAI，并在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
可选的，上述实施例以第一移动管理201和第二移动管理实体202不同为例进行说明，当然，本申请实施例中，第一移动管理实体201和第二移动管理实体202也可以相 同，此时：
第一移动管理实体201，用于获取终端接入到EPC时已建立的PDN连接的信息，并根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI后，向终端发送注册接受消息。
第一移动管理实体201，还用于在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。
基于本申请实施例提供的会话建立系统，由于第一移动管理实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，因此第一移动管理实体可以在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
可选的，上述会话建立系统20可以应用于如图1所示的4G网络和5G网络互通架构中，此时，上述第一移动管理实体201或第二移动管理实体202可以对应图1中的AMF实体。
需要说明的是，图1中仅是示例性的给出一个AMF实体在4G网络和5G网络互通架构中的连接方式。其中，当第一移动管理实体201和第二移动管理实体202为不同的移动管理实体时，第一移动管理实体201和第二移动管理实体202分别对应不同的AMF实体，每个AMF实体在4G网络和5G网络互通架构中的连接方式均可参考图1所示的AMF实体，在此不再赘述。同时，不同的AMF实体之间可以通过N14接口通信，在此进行统一说明，以下不再赘述。
如图11所示，为本申请实施例提供的一种会话建立系统110，该会话建立系统110包括控制面功能实体1101和第一移动管理实体1103。可选的，该会话建立系统110还可以包括用户数据管理实体1102和第二移动管理实体1104。
其中，控制面功能实体1101，用于确定会话对应的网络切片的S-NSSAI，并将该会话对应的网络切片的S-NSSAI存储至用户数据管理实体1103。
第一移动管理实体1103，用于从用户数据管理实体1103中获取该会话对应的网络切片的S-NSSAI，其中，该会话对应的网络切片的S-NSSAI用于指示建立会话的网络切片。
可选的，第一移动管理实体1103，还用于向第二移动管理实体1104发送该会话对应的网络切片的S-NSSAI。
第二移动管理实体1104，用于接收来自第一移动管理实体1103的该会话对应的网络切片的S-NSSAI，并根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。
可选的，本申请实施例中的第一移动管理实体1103和第二移动管理实体1104可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一移动管理实体1103也可以称之为初始移动管理实体， 第二移动管理实体1104也可以称之为目标移动管理实体，在此进行统一说明，以下不再赘述。
可选的，本申请实施例提供的会话建立系统110不仅适用于终端从EPC切换到支持网络切片的5GC的场景下，也适用于终端从不支持网络切片的5GC切换到支持网络切片的5GC的场景下，本申请实施例对此不作具体限定。其中，EPC中的会话包括PDN连接；5GC中的会话包括PDU会话，在此统一说明，以下不再赘述。
需要说明的是，本申请实施例中的会话建立具体是指对已有会话的更新，在此统一说明，以下不再赘述。
基于本申请实施例提供的会话建立系统，由于第一移动管理实体可以从用户数据管理实体中获取该会话对应的网络切片的S-NSSAI，并将该会话对应的网络切片的S-NSSAI发送给第二移动管理实体，因此第二移动管理实体可以接收来自第一移动管理实体的该会话对应的网络切片的S-NSSAI，并根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
可选的，上述实施例以第一移动管理1103和第二移动管理实体1104不同为例进行说明，当然，本申请实施例中，第一移动管理实体1103和第二移动管理实体1104也可以相同，此时：
控制面功能实体1101，用于确定会话对应的网络切片的S-NSSAI，并将该会话对应的网络切片的S-NSSAI存储至用户数据管理实体1102。
第一移动管理实体1103，用于从用户数据管理实体1102中获取该会话对应的网络切片的S-NSSAI，并根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。
基于本申请实施例提供的会话建立系统，由于第一移动管理实体可以从用户数据管理实体中获取会话对应的网络切片的S-NSSAI，因此第一移动管理实体可以在接收来自终端的会话建立请求之后，根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
可选的，若本申请实施例提供的会话建立系统110应用于终端从EPC切换到支持网络切片的5GC的场景下，则该会话建立系统110可以应用于如图1所示的4G网络和5G网络互通架构中，此时，上述控制面功能实体1101可以对应图1中的SMF实体+PGW-C实体；上述用户数据管理实体1102可以对应图1中的HSS实体+UDM实体；上述第一移动管理实体1103或第二移动管理实体1104可以对应图1中的AMF实体，在此统一说明，以下不再赘述。
需要说明的是，图11中仅是示例性的给出一个AMF实体在4G网络和5G网络互通架构中的连接方式。其中，当第一移动管理实体1103和第二移动管理实体1104为不同 的移动管理实体时，第一移动管理实体1103和第二移动管理实体1104分别对应不同的AMF实体，每个AMF实体在4G网络和5G网络互通架构中的连接方式均可参考图1所示的AMF实体，在此不再赘述。同时，不同的AMF实体之间可以通过N14接口通信，在此进行统一说明，以下不再赘述。
可选的，若本申请实施例提供的会话建立系统110应用于终端从不支持网络切片的5GC切换到支持网络切片的5GC的场景下，则上述控制面功能实体1101可以对应5G网络中的SMF实体；上述用户数据管理实体1102可以对应5G网络中的UDM实体；上述第一移动管理实体1103或第二移动管理实体1104可以对应5G网络中的AMF实体，在此统一说明，以下不再赘述。
如图14所示，为本申请实施例提供的一种会话建立系统140，该会话建立系统140包括控制面功能实体1401和第一移动管理实体1402。
其中，控制面功能实体1401，用于获取终端接入到EPC时已建立的PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
控制面功能实体1401，还用于向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
第一移动管理实体1402，用于获取PDN连接的信息，并向网络存储功能实体发送该PDN连接的信息，该PDN连接的信息用于确定该PDN连接对应的网络切片的S-NSSAI。
第一移动管理实体1402，还用于接收来自网络存储功能实体的该PDN连接对应的网络切片的S-NSSAI。
需要说明的是，本申请实施例中的会话建立具体是指对已有会话的更新，在此统一说明，以下不再赘述。
基于本申请实施例提供的会话建立系统，由于第一AMF实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，因此第一AMF实体可以在接收来自MME的切换请求之后，根据该PDN连接对应的网络切片的S-NSSAI，获取第二AMF实体信息，进而可以在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
可选的，如图14所示，本申请实施例中的会话建立系统140还可以包括：网络存储功能实体1403。
网络存储功能实体1403，用于接收并存储来自控制面功能实体1401的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
网络存储功能实体1403，还用于接收来自第一移动管理实体的该PDN连接的信息，并根据该PDN连接的信息，以及存储的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，确定该PDN连接对应的网络切片的S-NSSAI之后，向第一移动管理实体1402发送该PDN连接对应的网络切片的S-NSSAI。
可选的，本申请实施例中的控制面功能实体1401和网络存储功能实体1403之间可 以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一移动管理实体1402和网络存储功能实体1403之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，如图14所示，本申请实施例中的会话建立系统140还可以包括EPC中的第三移动管理实体1404。
其中，控制面功能实体1401，还用于向第三移动管理实体1404发送该PDN连接的信息。
第三移动管理实体1404，用于接收来自控制面功能实体1401的该PDN连接的信息，并向第一移动管理实体发送该PDN连接的信息。
相应的，第一移动管理实体1402，用于获取PDN连接的信息，包括：用于接收来自第三移动管理实体的该PDN连接的信息。
可选的，本申请实施例中的控制面功能实体1401和第三移动管理实体1404之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一移动管理实体1402和第三移动管理实体1404之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
基于该方案，在终端从支持DCN的EPC切换到支持网络切片的5GC时，第一移动管理实体可以获取该PDN连接的信息。
可选的，若本申请实施例提供的会话建立系统140应用于终端从支持DCN的EPC切换到支持网络切片的5GC的场景下，则上述控制面功能实体1401可以对应图1所示的4G网络和5G网络互通架构中的SMF实体+PGW-C实体；上述的第一移动管理实体可以对应图1所示的4G网络和5G网络互通架构中的AMF实体；上述的网络存储功能实体1403可以对应5G网络中的NRF实体(未示出)，在此统一说明，以下不再赘述。
如图18所示，为本申请实施例提供的一种会话建立系统180，该会话建立系统180包括网络存储功能实体1803和第一移动管理实体1802。
其中，第一移动管理实体1802，用于向网络存储功能实体1803发送PDN连接对应的用户面实体的第一信息。网络存储功能实体1803，用于接收来自第一移动管理实体1801的第一信息。网络存储功能实体1803，还用于根据第一信息，确定该PDN连接对应的第一网络切片的S-NSSAI，并向第一移动管理实体1802发送该第一网络切片的S-NSSAI。第一移动管理实体1802，还用于接收来自网络存储功能实体1803的该第一网络切片的S-NSSAI。
基于本申请实施例提供的会话建立系统，由于第一AMF实体可以根据PDN连接对应的用户面实体的第一信息，获取该PDN连接对应的第一网络切片的S-NSSAI，因此第一AMF实体可以在接收来自MME的请求消息(如切换请求或注册请求)之后，根据该PDN连接对应的第一网络切片的S-NSSAI，获取第二AMF实体信息，进而可以在相应的第一网络切片中建立PDU会话。也就是说，基于该方案，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片 中建立PDU会话。
可选的，如图18所示，本申请实施例中的会话建立系统180还可以包括：用户面实体1801。用户面实体1801，用于向网络存储功能实体1803发送第一信息和与第一信息对应的第一网络切片的S-NSSAI。网络存储功能实体1803，用于接收来自用户面实体1801的第一信息和与第一信息对应的第一网络切片的S-NSSAI。
可选的，本申请实施例中的用户面实体1801和网络存储功能实体1803之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一移动管理实体1802和网络存储功能实体1803之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)等。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，图2中的第一移动管理实体201或者第二移动管理实体202，或者图14中的控制面功能实体1401或者网络存储功能实体1403，或者图18中的用户面实体1801或第一移动管理实体1802或网络存储功能实体1803可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
例如，图2中的第一移动管理实体201或者第二移动管理实体202，或者图14中的控制面功能实体1401或者网络存储功能实体1403，或者图18中的用户面实体1801或第一移动管理实体1802或网络存储功能实体1803可以通过图3中的通信设备来实现。图3所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备300包括至少一个处理器301，通信线路302，存储器303以及至少一个通信接口304。
处理器301可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路302可包括一通路，在上述组件之间传送信息。
通信接口304，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器303可以是只读存储器(read-only memory，ROM)或可存储静态信息和指 令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路302与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器303用于存储执行本申请方案的计算机执行指令，并由处理器301来控制执行。处理器301用于执行存储器303中存储的计算机执行指令，从而实现本申请下述实施例提供的会话建立方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备300可以包括多个处理器，例如图3中的处理器301和处理器308。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备300还可以包括输出设备305和输入设备306。输出设备305和处理器301通信，可以以多种方式来显示信息。例如，输出设备305可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备306和处理器301通信，可以以多种方式接收用户的输入。例如，输入设备306可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备300可以是一个通用设备或者是一个专用设备。在具体实现中，通信设备300可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图3中类似结构的设备。本申请实施例不限定通信设备300的类型。
下面将结合图1至图3，图11、图14以及图18对本申请实施例提供的会话建立方法进行具体阐述。
以图2所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图4所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S401、终端接入EPC建立PDN连接后，将PDN连接的信息存储至用户数据管理实体终端的签约数据中。
其中，步骤S401的相关实现可参考现有技术中的实现方式，在此不予赘述。
可选的，本申请实施例中，PDN连接的信息可以是PDN连接对应的APN，或者PDN连接对应的控制面功能实体(即SMF实体+PGW-C实体)的信息，本申请实施例对此不作具体限定。其中，PDN连接对应的控制面功能实体的信息例如可以包括控制面功能实体的IP地址或者全量域名(fully qualified domain name，FQDN)等，本申请实施例对此不作具体限定。
可选的，本申请实施例中的PDN连接可以是在终端接入到EPC时为终端选择的DCN中建立的PDN连接，也可以是在非DCN中建立的PDN连接，本申请实施例对此不作具体限定。
其中，若本申请实施例中的PDN连接是在终端接入到EPC时为终端选择的DCN中建立的PDN连接，则MME还可以将DCN的信息发送给终端，本申请实施例对此不作具体限定。
S402、终端向第一AMF实体发送注册请求，以使得第一AMF实体接收来自终端的注册请求。其中，该注册请求携带终端的标识。
可选的，该注册请求还可以携带终端请求的NSSAI(requested NSSAI)、DCN的信息、终端的位置信息等，本申请实施例对此不作具体限定。
S403、第一AMF实体根据终端的标识，从用户数据管理实体中获取终端的签约数据，其中，该签约数据包括终端接入到EPC时已建立的PDN连接的信息。
此外，由于5G网络中的网络切片相关的签约数据与4G网络中的签约数据不同，不能直接从DCN信息映射出5G网络的签约网络切片，因此，第一AMF实体从用户数据管理实体获取的终端的签约数据中还可以包括签约的一个或多个S-NSSAI(s)，本申请实施例对此不作具体限定。
可选的，本申请实施例中，可以在用户数据管理实体向第一AMF实体发送的Nudm消息中携带终端的签约数据。其中，Nudm为UDM实体的服务化接口，该Nudm消息在现有协议中为Nudm签约数据管理(subscriber data management)，其功能为：当有需要时允许网络功能(network function，NF)消费者取回终端的签约数据，以及，提供更新的终端的签约数据到签约的NF消费者。
S404、第一AMF实体根据PDN连接的信息，获取PDN连接对应的网络切片的S-NSSAI。
可选的，一种可能的实现方式中，PDN连接的信息包括该PDN连接对应的APN；第一AMF实体根据PDN连接的信息，获取PDN连接对应的网络切片的S-NSSAI，包括：第一AMF实体根据APN，以及预先配置的APN和S-NSSAI的对应关系，确定该PDN连接对应的网络切片的S-NSSAI。其中，预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对一关系，或者APN和S-NSSAI的一对多关系。
在预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对一关系的情况下，第一AMF实体根据APN，以及预先配置的APN和S-NSSAI的一对一关系，可以确定该PDN连接对应的网络切片的S-NSSAI。
示例性的，假设预先配置的APN和S-NSSAI的一对一关系如表二所示：
表二
APN S-NSSAI
APN1 S-NSSAI1
APN2 S-NSSAI2
APN3 S-NSSAI3
…… ……
若PDN连接对应的APN为APN3，则第一AMF实体根据APN，以及预先配置的APN和S-NSSAI的一对一关系，可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI3。
在预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对多关系的情况下，第一AMF实体根据预先配置的APN和S-NSSAI的一对多关系中每个S-NSSAI的优先级、每个S-NSSAI所指示的网络切片的负荷信息、以及第一AMF实体中配置的AMF集合所支持的NSSAI中的至少一个，以及APN和预先配置的APN和S-NSSAI的一对多关系，确定PDN连接对应的网络切片的S-NSSAI。
示例性的，假设预先配置的APN和S-NSSAI的一对多关系如表三所示：
表三
Figure PCTCN2018109971-appb-000002
若PDN连接对应的APN为APN3，则：
首先，第一AMF实体可以根据APN，以及预先配置的APN和S-NSSAI的一对多关系，确定出三个网络切片的S-NSSAI，分别为S-NSSAI7、S-NSSAI8和S-NSSAI9。
其次，第一AMF实体可以根据预先配置的S-NSSAI7、S-NSSAI8和S-NSSAI9的优先级，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7的优先级高于S-NSSAI8的优先级，S-NSSAI8的优先级高于S-NSSAI9的优先级，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI7。
或者，第一AMF实体可以根据预先配置的S-NSSAI7、S-NSSAI8和S-NSSAI9所 指示的网络切片的负荷信息，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7所指示的网络切片的负荷高于S-NSSAI8所指示的网络切片的负荷，S-NSSAI8所指示的网络切片的负荷高于S-NSSAI9所指示的网络切片的负荷，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI9。
或者，第一AMF实体可以根据第一AMF实体中配置的AMF集合所支持的NSSAI，确定该PDN连接对应的网络切片的S-NSSAI。比如，若第一AMF实体中配置的AMF集合所支持的NSSAI包括S-NSSAI3、S-NSSAI5和S-NSSAI8，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI8。
或者，第一AMF实体可以根据预先配置的S-NSSAI7、S-NSSAI8和S-NSSAI9的优先级，以及，S-NSSAI7、S-NSSAI8和S-NSSAI9所指示的网络切片的负荷信息，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7的优先级高于S-NSSAI8的优先级，S-NSSAI8的优先级高于S-NSSAI9的优先级，S-NSSAI7所指示的网络切片的负荷高于S-NSSAI8所指示的网络切片的负荷，S-NSSAI8所指示的网络切片的负荷高于S-NSSAI9所指示的网络切片的负荷，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI8。
或者，第一AMF实体可以根据预先配置的S-NSSAI7、S-NSSAI8和S-NSSAI9的优先级，以及，第一AMF实体中配置的AMF集合所支持的NSSAI，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7的优先级等于S-NSSAI8的优先级，S-NSSAI8的优先级高于S-NSSAI9的优先级，第一AMF实体中配置的AMF集合所支持的NSSAI包括S-NSSAI3、S-NSSAI5和S-NSSAI8，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI8。
或者，第一AMF实体可以根据S-NSSAI7、S-NSSAI8和S-NSSAI9所指示的网络切片的负荷信息，以及，第一AMF实体中配置的AMF集合所支持的NSSAI，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7所指示的网络切片的负荷高于S-NSSAI8所指示的网络切片的负荷，S-NSSAI8所指示的网络切片的负荷高于S-NSSAI9所指示的网络切片的负荷，第一AMF实体中配置的AMF集合所支持的NSSAI包括S-NSSAI3、S-NSSAI8和S-NSSAI9，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI9。
或者，第一AMF实体可以根据预先配置的S-NSSAI7、S-NSSAI8和S-NSSAI9的优先级，S-NSSAI7、S-NSSAI8和S-NSSAI9所指示的网络切片的负荷信息，以及，第一AMF实体中配置的AMF集合所支持的NSSAI，确定该PDN连接对应的网络切片的S-NSSAI。比如，若S-NSSAI7的优先级等于S-NSSAI8的优先级，S-NSSAI8的优先级高于S-NSSAI9的优先级，S-NSSAI7所指示的网络切片的负荷高于S-NSSAI8所指示的网络切片的负荷，第一AMF实体中配置的AMF集合所支持的NSSAI包括S-NSSAI3、S-NSSAI5和S-NSSAI8，则第一AMF实体可以确定该PDN连接对应的网络切片的S-NSSAI为S-NSSAI8。
当然，第一AMF实体还可以再结合其他信息确定该PDN连接对应的网络切片的S-NSSAI。比如，第一AMF实体在确定该PDN连接对应的网络切片的S-NSSAI时，也 可以参考DCN的信息，比如DCN的信息中终端使用类型可以与网络切片的S-NSSAI中的SST进行映射，从而确定该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
可选的，另一种可能的实现方式中，该PDN连接的信息包括该PDN连接对应的控制面功能实体(即SMF实体+PGW-C实体)的信息；由于SMF实体+PGW-C实体是位于网络切片内的，因此，第一AMF实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，包括：第一AMF实体根据控制面功能实体的信息，确定该PDN连接对应的网络切片的S-NSSAI。
示例性的，若控制面功能实体的信息包括SMF实体+PGW-C实体的FQDN，则由于该FQDN中包含了网络切片信息，则根据该FQDN可确定网络切片对应的S-NSSAI。
或者，示例性的，若控制面功能实体的信息包括SMF实体+PGW-C实体的IP地址，则第一AMF实体根据该IP地址可反向查询DNS，从而获得SMF实体+PGW-C实体的FQDN，由于该FQDN中包含了网络切片信息，则根据该FQDN可确定网络切片对应的S-NSSAI。
当然，若根据SMF实体+PGW-C实体的FQDN不能直接确定网络切片，则第一AMF实体还需要进一步根据配置信息确定，该配置信息包括IP地址段与网络切片的对应关系等，本申请实施例对此不作具体限定。
可选的，另一种可能的实现方式中，该PDN连接的信息包括该PDN连接对应的控制面功能实体(即SMF实体+PGW-C实体)的信息；由于SMF实体+PGW-C实体是位于网络切片内的，因此，第一AMF实体根据该PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，包括：第一AMF实体根据控制面功能实体的信息，向控制面功能实体发送请求消息，该请求消息用于请求获取该PDN连接对应的网络切片的S-NSSAI；第一AMF实体接收来自控制面功能实体的该PDN连接对应的网络切片的S-NSSAI。
需要说明的是，本申请实施例仅是示例性的给出了上述几种获取该PDN连接对应的网络切片的S-NSSAI的具体实现，当然还可以通过其他方式获取该PDN连接对应的网络切片的S-NSSAI，本申请实施例对该PDN连接对应的网络切片的S-NSSAI的获取方式不作具体限定。
S405、第一AMF实体获取第二AMF实体的信息。
可选的，第一AMF实体获取第二AMF实体的信息，具体可以包括：第一AMF实体根据PDN连接对应的网络切片的S-NSSAI，获取第二AMF实体的信息。
一种可能的实现方式中，考虑到一个网络切片中可能包括一个或多个网络切片实例，因此，第一AMF实体根据PDN连接对应的网络切片的S-NSSAI，确定第二AMF实体的信息，具体可以包括：第一AMF实体根据PDN连接的信息，确定PDN连接对应的网络切片实例；第一AMF实体根据该PDN连接对应的网络切片的S-NSSAI和该网络切片实例的信息，确定第二移动管理实体的信息。
当然，第一AMF实体还可以再结合其他信息确定第二移动管理实体的信息，比如，第一AMF实体还可以根据第一AMF实体中配置的网络切片与AMF实体集合的映射信息、第一AMF实体中配置的DCN与AMF实体集合的映射信息、终端请求的NSSAI、终端签约的NSSAI或终端的位置信息等，确定第二AMF实体的信息，具体可参考现有的实现方式，在此不予赘述。
或者，一种可能的实现方式中，第一AMF实体根据PDN连接对应的网络切片的S-NSSAI，获取第二AMF实体的信息，包括：第一AMF实体向NSSF实体发送该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于确定第二AMF实体的信息；第一AMF实体接收来自NSSF实体的该第二AMF实体的信息。其中，NSSF实体根据该PDN连接对应的网络切片的S-NSSAI确定第二AMF实体的信息的具体方式可参考上述第一AMF实体根据该PDN连接对应的网络切片的S-NSSAI确定第二AMF实体的信息的具体方式，在此不再赘述。
可选的，本申请实施例中，第一AMF实体可以是在确定自身无法为该PDN连接对应的网络切片提供服务后，再获取第二AMF实体的信息，此时，第二AMF实体与第一AMF实体不同；或者，第一AMF实体也可以是直接获取第二AMF实体的信息，此时，第二AMF实体与第一AMF实体可能相同，也可能不同，本申请实施例对此不作具体限定。
当然，若第一AMF实体确定自身可以为该PDN连接对应的网络切片提供服务，则第一AMF实体可以不用获取第二AMF实体的信息，在此进行统一说明，以下不再赘述。
假设第一AMF实体与第二AMF实体不同，则本申请实施例提供的会话建立方法还包括如下步骤：
S406、第一AMF实体向接入设备发送重路由消息，以使得接入设备接收来自第一AMF实体的重路由消息。该重路由消息携带第二AMF实体的信息和该PDN连接对应的网络切片的S-NSSAI，该第二AMF实体的信息用于指示将该终端相关的消息重路由到第二AMF实体，该PDN连接对应的网络切片的S-NSSAI用于指示建立PDU会话的网络切片。
S407、接入设备向第二AMF实体发送初始终端消息，以使得第二AMF实体接收来自接收设备的初始终端消息。该初始终端消息携带该PDN连接对应的网络切片的S-NSSAI。
可选的，本申请实施例中，在执行完步骤S405之后，也可以是第一AMF实体直接向第二AMF实体发送该PDN连接对应的网络切片的S-NSSAI，无需经过步骤S406和S407的重路由过程，本申请实施例对此不作具体限定。
S408、第二AMF实体向终端发送注册接受消息，以使得终端接收来自第二AMF实体的注册接受消息。该注册接受消息携带该PDN连接对应的网络切片的S-NSSAI。
可选的，该注册接受消息还可以携带注册区域允许的NSSAI(allowed NSSAI)，本申请实施例对此不作具体限定。
S409、终端向第二AMF实体发送PDU会话建立请求，以使得第二AMF实体接收 来自终端的PDU会话建立请求。该PDU会话建立请求携带该PDN连接对应的网络切片的S-NSSAI。
S410、第二AMF实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。
其中，步骤S410中第二AMF实体在PDN连接对应的网络切片中建立PDU会话，具体是指第二AMF实体协同终端或其他网元在PDN连接对应的网络切片中建立PDU会话。该建立PDU会话的过程可参考现有的流程，在此不予赘述。
可选的，本申请实施例步骤S408中的注册接受消息中还可以携带允许进行切换的PDN连接的信息，这样，终端接收到该注册接受消息之后，还可以根据允许进行切换的PDN连接的信息，释放EPC中除该允许进行切换的PDN连接之外的其他所有PDN连接，从而可以节省系统的资源。
或者，可选的，本申请实施例步骤S408中的注册接受消息中还可以携带需要删除的PDN连接的信息，这样，终端接收到该注册接受消息之后，还可以根据需要删除的PDN连接的信息，释放EPC中相应的PDN连接，从而可以节省系统的资源。
基于本申请实施例提供的会话建立方法，由于第一AMF实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，并将该PDN连接对应的网络切片的S-NSSAI发送给第二AMF实体，因此第二AMF实体可以接收来自第一AMF实体的该PDN连接对应的网络切片的S-NSSAI，并在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
其中，上述步骤S401至S410中第一AMF实体和第二AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图2所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图5所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S501-S507、同步骤S401-S407，具体可参考图4所示的实施例，在此不再赘述。
S508、第二AMF实体存储该PDN连接对应的网络切片的S-NSSAI。
S509、第二AMF实体向终端发送注册接受消息，以使得终端接收来自第二AMF实体的注册接受消息。该注册接受消息携带注册区域允许的NSSAI(allowed NSSAI)。
S510、终端向第二AMF实体发送PDU会话建立请求，以使得第二AMF实体接收来自终端的PDU会话建立请求。该PDU会话建立请求携带终端请求的网络切片的S-NSSAI和该终端请求的PDN连接对应的APN。
其中，该终端请求的网络切片的S-NSSAI是终端从第二AMF实体向终端发送的注册区域允许的NSSAI中选择的，具体可参考现有的实现方式，在此不予赘述。
S511、在终端请求的网络切片的S-NSSAI与预先存储的PDN连接对应的网络切片的S-NSSAI相同，且该终端请求的PDN连接对应的APN与该PDN连接对应的APN相 同的情况下，第二AMF实体根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。
其中，步骤S511中第二AMF实体在PDN连接对应的网络切片中建立PDU会话，具体是指第二AMF实体协同终端或其他网元在PDN连接对应的网络切片中建立PDU会话。该建立PDU会话的过程可参考现有的流程，在此不予赘述。
可选的，在终端请求的网络切片的S-NSSAI与预先存储的PDN连接对应的网络切片的S-NSSAI不相同的情况，第二AMF实体可以拒绝该PDU会话建立请求，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S510中的PDU会话建立请求中也可以不携带终端请求的网络切片的S-NSSAI，而是携带PDN连接的信息；进而，第二AMF实体接收来自终端的PDU会话建立请求之后，可以根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话，本申请实施例对此不作具体限定。
基于本申请实施例提供的会话建立方法，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
其中，上述步骤S501至S511中第一AMF实体和第二AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图2所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图6所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S601-S603、同步骤S401-S403，具体可参考图4所示的实施例，在此不再赘述。
S604、第一AMF实体向NSSF实体发送切片选择请求消息，以使得NSSF实体接收来自第一AMF实体的切片选择请消息。该切片选择请求消息携带PDN连接的信息。
S605-S606、同步骤S404-S405，具体可参考图4所示的实施例，在此不再赘述。
S607、NSSF实体向第一AMF实体发送PDN连接对应的网络切片的S-NSSAI和第二AMF实体的信息，以使得第一AMF实体接收来自NSSF实体的该PDN连接对应的网络切片的S-NSSAI和第二AMF实体的信息。
可选的，本申请实施例中，也可以是NSSF实体确定候选AMF实体集合之后，向第一AMF实体发送给候选AMF实体集合。进而由第一AMF实体根据候选AMF实体集合的信息，以及候选AMF实体集合中每个AMF实体的负荷信息等信息，从候选AMF实体集合中选择第二AMF实体，本申请实施例对此不作具体限定。
S608-S612、同步骤S406-S410，具体可参考图4所示的实施例，在此不再赘述。
可选的，本申请实施例在执行步骤S607之后，也可以参考图5所示的实施例中的步骤S506-S511执行，本申请实施例在此不再赘述。
基于本申请实施例提供的会话建立方法，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
其中，上述步骤S601至S612中第一AMF实体和第二AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图2所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图7所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S701-S705、同步骤S401-S405，具体可参考图4所示的实施例，在此不再赘述。
假设第一AMF实体与第二AMF实体相同，则本申请实施例提供的会话建立方法还包括如下步骤：
S706-S708、与步骤S408-S410类似，区别仅在于将步骤S408-S410中的第二AMF实体替换为第一AMF实体，具体可参考图4所示的实施例，在此不再赘述。
可选的，本申请实施例在执行步骤S705之后，也可以参考图5所示的实施例中的步骤S508-S511执行，区别仅在于将步骤S508-S511中的第二AMF实体替换为第一AMF实体，具体可参考图5所示的实施例，在此不再赘述。
可选的，本申请实施例中的步骤S704-S705也可以替换为图6所示的实施例中的步骤S604-S607，具体可参考图6所示的实施例，在此不再赘述。
基于本申请实施例提供的会话建立方法，由于第一AMF实体可以根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，因此第一AMF实体可以在接收来自终端的PDU会话建立请求之后，根据该PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。也就是说，基于该方案，可以使得在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立PDU会话。
其中，上述步骤S701至S708中第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
以图11所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构，4G网络中的会话为PDN连接；5G网络中的会话为PDU会话为例，如图12所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S1201、终端向控制面功能实体发送PDN连接建立请求，以使得控制面功能实体接收来自终端的PDN连接建立请求。其中，该PDN连接建立请求中携带PDN连接的信息，用于请求控制面功能实体为终端建立相应的PDN连接。
其中，该PDN连接的信息例如可以是PDN连接对应的APN，本申请实施例对此不作具体限定。
S1202、控制面功能实体确定该PDN连接对应的网络切片的S-NSSAI。
可选的，控制面功能实体确定该PDN连接对应的网络切片的S-NSSAI，具体可以包括：控制面功能实体将该控制面功能实体所支持的S-NSSAI的其中一个确定为该PDN连接对应的网络切片的S-NSSAI。
比如，若控制面功能实体仅为一个网络切片服务，则控制面功能实体将该网络切片的S-NSSAI确定为该PDN连接对应的网络切片的S-NSSAI。
或者，比如，若控制面功能实体为多个网络切片服务，则控制面功能实体选择其所支持 的S-NSSAI中的一个作为该PDN连接对应的网络切片的S-NSSAI。示例性的，控制面功能实体可以根据该PDN连接对应的APN选择S-NSSAI，此时，控制面功能实体所支持的不同网络切片所支持的APN空间不重叠，如，APN 1～N对应S-NSSAI1，APN N+1～M对应S-NSSAI2，依次类推。或者，示例性的，控制面功能实体可以根据终端的签约信息和/或本地策略等确定该PDN连接对应的网络切片的S-NSSAI。比如，控制面功能实体从用户数据管理实体中获取终端所签约的缺省S-NSSAI集合，并将终端所签约的缺省S-NSSAI集合和控制面功能实体所支持的S-NSSAI集合取交集，若交集中仅有一个S-NSSAI，则控制面功能实体将该S-NSSAI确定为该PDN连接对应的网络切片的S-NSSAI；若交集中仍然有多个S-NSSAI，控制面功能实体可以根据本地策略选择其中的一个作为该PDN连接对应的网络切片的S-NSSAI，比如，根据网络切片的负荷将其中一个负荷较轻的网络切片的S-NSSAI作为该PDN连接对应的网络切片的S-NSSAI。
S1203、控制面功能实体将该PDN连接对应的网络切片的S-NSSAI存储至用户数据管理实体中。
具体的，控制面功能实体向用户数据管理实体发送该PDN连接对应的网络切片的S-NSSAI，以使得用户数据管理实体接收并存储来自控制面功能实体的该PDN连接对应的网络切片的S-NSSAI。
其中，控制面功能实体在向用户数据管理实体发送该PDN连接对应的网络切片的S-NSSAI的同时，还可以向用户数据管理实体发送终端的标识及PDN连接信息，以便用户数据管理实体可以将该PDN连接对应的网络切片的S-NSSAI与终端的PDN连接进行关联，即以便用户数据管理实体可以将该PDN连接对应的网络切片的S-NSSAI、该终端的标识和该PDN连接的信息进行关联。其中，该PDN连接信息例如可以是APN、或控制面功能实体的标识或其他信息，本申请实施例对此不作具体限定。
可选地，控制面功能实体还可以将该PDN连接对应的网络切片的实例标识存储至用户数据管理实体中，本申请实施例对此不作具体限定。
S1204、PDN连接建立完成后，控制面功能实体向终端发送PDN连接建立响应，以使得终端接收来自控制面功能实体的PDN连接建立响应。
其中，PDN连接建立的过程具体可参考现有的实现方式，在此不予赘述。
S1205、终端移动到5G覆盖范围后，终端向第一AMF实体发送注册请求，以使得第一AMF实体接收来自终端的注册请求。其中，该注册请求携带终端的标识。
其中，步骤S1205的描述可参考图4中的步骤S402，在此不再赘述。
S1206、与步骤S403类似，区别在于，本申请实施例中第一AMF实体从用户数据管理实体中获取的终端的签约数据中还包括该PDN连接对应的网络切片的S-NSSAI，具体可参考图4所示的实施例，在此不再赘述。
可选的，若用户数据管理实体中还存储该PDN连接对应的网络切片的实例标识，则本申请实施例中第一AMF实体从用户数据管理实体中获取的终端的签约数据中还可以包括该PDN连接对应的网络切片的实例标识，本申请实施例对此不作具体限定。
S1207、同步骤S405，具体可参考图4所示的实施例，在此不再赘述。
可选的，若步骤S1206中第一AMF实体从用户数据管理实体中获取的终端的签约数据中还包括该PDN连接对应的网络切片的实例标识，则本申请实施例中，第一AMF实体在选择第二AMF实体时，还需要考虑选择的第二AMF实体是否支持该PDN连接对应的网络切 片的切片实例，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中，第一AMF实体获取第二AMF实体的信息的方式也可以如步骤S604-S607中所涉及的第一AMF实体获取第二AMF实体的方式，具体可参考图6所示的实施例，在此不再赘述。
S1208-S1212、同步骤S406-410或者步骤S506-S511，具体可参考图4或图5所示的实施例，在此不再赘述。
需要说明的是，图12所示的会话建立方法以终端从EPC切换到支持网络切片的5GC的场景为例进行说明，当然，上述会话建立方法也适用于终端从不支持网络切片的5GC切换到支持网络切片的5GC的场景下，区别仅在于将步骤S1201-S1212中的PDN连接替换为PDU会话，将控制面功能实体替换为SMF实体，将用户数据管理实体替换为UDM实体即可，具体可参考图12所示的实施例，在此不再赘述。
可选的，若上述会话建立方法应用于终端从不支持网络切片的5GC切换到支持网络切片的5GC的场景下，则在步骤S1209之后，还可以不用执行上述步骤S1210-S1212，而是执行如下会话更新流程：第二AMF实体通知SMF实体进行会话更新，进而SMF实体为会话更新用户面路径，包括SMF实体选择新的UPF实体，用新的UPF实体替换旧的UPF实体，或者将新的UPF实体插入到用户面路径中等，具体可参考现有的实现方式，在此不予赘述。
基于本申请实施例提供的会话建立方法，由于第一AMF实体可以从用户数据管理实体中获取会话对应的网络切片的S-NSSAI，并将该会话对应的网络切片的S-NSSAI发送给第二AMF实体，因此第二AMF实体可以接收来自第一AMF实体的该会话对应的网络切片的S-NSSAI，并在接收来自终端的会话建立请求之后，根据该会话对应的网络切片的S-NSSAI，在该会话对应的网络切片中建立会话。也就是说，基于该方案，在终端从支持DCN的EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
其中，上述步骤S1201至S1212中第一AMF实体和第二AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
以图11所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构，4G网络中的会话为PDN连接；5G网络中的会话为PDU会话为例，如图13所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S1301-S1304、同步骤S1201-S1204，具体可参考图12所示的实施例，在此不再赘述。
S1305、源接入设备确定需要将终端切换到目的接入设备后，源接入设备向源MME实体发送第一切换请求，以使得源MME实体接收来自源接入设备的第一切换请求。其中，该第一切换请求中携带目标接入设备的信息。
可选的，本申请实施例中，目标接入设备的信息例如可以是包括目标接入设备的位置信息或者目标接入设备的标识或者目标小区的标识等，本申请实施例对此不作具体限定。
S1306、源MME实体选择第一AMF实体。
其中，源MME实体选择第一AMF实体的具体实现可参考现有的实现方式，在此不再赘述。示例性的，源MME实体可根据目标接入设备的位置信息选择第一AMF实体。
S1307、源MME实体向第一AMF实体发送第二切换请求，以使得第一AMF实体接收 来自源MME实体的第二切换请求。其中，该第二切换请求中携带已建立的会话信息，如APN、DNN和控制面功能实体的标识中的至少一个。
S1308、同步骤S1206，具体可参考图12所示的实施例，在此不再赘述。
需要说明的是，本申请实施例以在步骤S1307中的第二切换请求中未携带已建立的PDN连接对应的网络切片的S-NSSAI为例进行说明。当然，若步骤S1307中的第二切换请求中携带已建立的PDN连接对应的网络切片的S-NSSAI，则不用执行步骤S1308，在此统一说明，以下不再赘述。
S1309、同步骤S1207，具体可参考图12所示的实施例，在此不再赘述。
S1310、第一AMF实体向第二AMF实体发送第三切换请求，以使得第二AMF实体接收来自第一AMF实体的第三切换请求。其中，该第三切换请求中携带第二切换请求中携带的信息，以及从用户数据管理实体中获取的PDN连接对应的网络切片的S-NSSAI。
可选的，若第一AMF实体获取了终端允许的NSSAI，则第三切换请求中还携带终端允许的NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，第一AMF实体可以直接向第二AMF实体发送第二切换请求，也可以通过上述重定向的方式向第二AMF实体发送第二切换请求，本申请实施例对此不作具体限定。
S1311、第二AMF实体继续后续的切换流程。
具体的，本申请实施例中，后续的切换流程包括会话更新流程以及注册流程等，本申请实施例对此不作具体限定。其中，会话更新流程可以包括：第二AMF实体通知控制面管理实体进行会话更新，进而控制面管理实体为会话更新用户面路径，包括控制面管理实体选择新的UPF实体，用新的UPF实体替换旧的UPF实体，或者将新的UPF实体插入到用户面路径中等，具体可参考现有的实现方式，在此不予赘述。注册流程可以包括：终端向第二AMF实体发送注册请求，以使得第二AMF实体接收来自终端的注册请求；进而，第二AMF实体向终端发送允许的NSSAI及注册区(Registration Area)，具体可参考现有的实现方式，在此不予赘述。
需要说明的是，图13所示的会话建立方法以终端从EPC切换到支持网络切片的5GC的场景为例进行说明，当然，上述会话建立方法也适用于终端从不支持网络切片的5GC切换到支持网络切片的5GC的场景下，区别仅在于将步骤S1301-S1311中的PDN连接替换为PDU会话，将源MME实体替换为源AMF实体，将控制面功能实体替换为SMF实体，将用户数据管理实体替换为UDM实体即可，具体可参考图13所示的实施例，在此不再赘述。
基于本申请实施例提供的会话建立方法，在终端从EPC切换到支持网络切片的5GC时，或者终端从不支持网络切片的5GC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。
其中，上述步骤S1301至S1311中第一AMF实体和第二AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
需要说明的是，图12和图13所示的实施例均是以第一AMF实体与第二AMF实体为不同的AMF实体为例进行说明，当然，第一AMF实体和第二AMF实体也可以是相同的AMF实体，此时仅需要将上述步骤中涉及第一AMF实体和第二AMF实体交互的步骤删除即可， 比如图12中不需要执行步骤S1207-S1209；图12中不需要执行步骤S1309和S1310，具体可参考图12或图13所示的实施例，在此不再赘述。
可选的，以图14所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图15所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S1501、在PDN连接建立过程中，控制面功能实体(即SMF实体+PGW-C实体)向NRF实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，以使得NRF实体接收来自控制面功能实体的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
可选的，本申请实施例中，PDN连接的信息可以包括PDN连接对应的控制面功能实体的信息、PDN连接对应的APN、PDN连接对应的PDN类型、或者PDN连接对应的PDN地址中的至少一个，本申请实施例对此不作具体限定。
可选的，本申请实施例中，PDN连接对应的控制面功能实体的信息例如可以包括PDN连接对应的控制面功能实体所在的公共陆地移动网络(public land mobile network，PLMN)的信息、控制面功能实体的IP地址或者FQDN等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，控制面功能实体可以根据PDN连接对应的控制面功能实体的信息、PDN连接对应的APN、PDN连接对应的PDN类型、PDN连接对应的PDN地址或者控制面功能实体所支持的S-NSSAI集合中的至少一个确定该PDN连接对应的网络切片的S-NSSAI。例如，控制面功能实体的FQDN中可以包括PDN连接对应的网络切片的S-NSSAI。或者，控制面功能实体可配置APN与S-NSSAI的对应关系，进而，控制面功能实体根据PDN连接对应的APN以及该对应关系，即可确定该PDN连接对应的网络切片的S-NSSAI。或者，控制面功能实体仅支持一个S-NSSAI，则控制面功能实体确定PDN连接对应的S-NSSAI即为控制面功能实体所支持的S-NSSAI。或者，控制面功能实体可配置PDN类型与S-NSSAI的对应关系，进而，控制面功能实体根据PDN连接对应的PDN类型以及该对应关系，即可确定该PDN连接对应的网络切片的S-NSSAI。本申请实施例不限定控制面功能实体确定该PDN连接对应的网络切片的S-NSSAI的具体实现方式。
可选的，本申请实施例中，NRF实体接收来自控制面功能实体的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI之后，可以建立或者存储该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI的对应关系，本申请实施例对此不作具体限定。
示例性的，以PDN连接的信息为PDN连接对应的控制面功能实体的标识为例，则NRF实体中可以存储如表四所示的对应关系：
表四
PDN连接的信息 PDN连接对应的网络切片的S-NSSAI
控制面功能实体标识1 S-NSSAI1
控制面功能实体标识2 S-NSSAI2
当然，当PDN连接的信息为其他信息时，只需要将表四中的控制面功能实体的标识替换为相应的信息即可，在此不再一一赘述。
可选的，本申请实施例提供的会话建立方法还可以包括如下步骤S1502：
S1502、在PDN连接建立过程中，若不同的网络切片的PDN连接对应不同的控制面功能实体的信息，则控制面功能实体向MME发送该PDN连接对应的控制面功能实体的信息，以使得MME接收来自控制面功能实体的该PDN连接对应的控制面功能实体的信息。
其中，该PDN连接对应的控制面功能实体的信息的相关描述可参考步骤S1501，在此不 再赘述。
可选的，本申请实施例中，MME接收来自控制面功能实体的该PDN连接对应的控制面功能实体的信息之后，可以存储该该PDN连接对应的控制面功能实体的信息，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的步骤S1501与步骤S1502之间没有必然的执行先后顺序，可以是先执行步骤S1501，再执行步骤S1502；也可以是先执行步骤S1502，再执行步骤S1501；还可以是同时执行步骤S1501和S1502，本申请实施例对此不作具体限定。
进一步的，本申请实施例提供的会话建立方法还可以包括如下步骤：
S1503、EPC中的接入设备向MME发送切换请求(Handover Request)1，以使得MME接收来自接入设备的切换请求1。
其中，该切换请求1中包括目标接入区域的信息。该目标接入区域的信息例如可以包括目标小区的信息、目标接入设备的信息或者目标跟踪区的信息中的至少一个，本申请实施例对此不作具体限定。
其中，本申请实施例中，目标小区为该终端待接入的小区，目标小区的信息例如可以包括目标小区的标识；目标接入设备为该终端待接入的小区所属的接入设备，目标接入设备的信息例如可以包括目标接入设备的标识或者位置信息；目标跟踪区为该终端待接入的小区所在的跟踪区，目标跟踪区的信息例如可以包括目标跟踪区的标识，等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，该切换请求1中还可以包括用于确定终端的信息，如终端的标识，本申请实施例对此不作具体限定。
可选的，本申请实施例中的切换请求1可以是由EPC中的接入设备根据终端上报的小区测量信息决策后进而向MME发送的，本申请实施例对此不作具体限定。
S1504、MME确定第一AMF实体。
可选的，本申请实施例中，MME可以根据切换请求1中携带的目标接入区域的信息，来确定该切换请求1所请求的切换是否属于不同类型网络间的切换。本申请实施例的场景中，目标接入区域为5G网络，因此，MME确定该切换请求所请求的切换属于跨系统的切换。
为了实现跨系统切换，MME需要根据切换请求中携带的目标接入区域的信息确定执行切换操作的第一AMF实体。在一种实现方式中，MME由于没有PDN连接对应的网络切片的信息，因此MME可以根据目标接入设备的位置信息选择缺省的AMF实体作为第一AMF实体。或者，在另外一种实现方式中，MME可以根据终端的使用类型(Usage type)和目标跟踪区的标识选择第一AMF实体。
其中，本申请实施例仅是示例性的提供了两种MME确定一AMF实体的具体实现。当然，MME还可以通过其他方式确定第一AMF实体，具体可参考现有的实现方式，在此不再赘述。
S1505、MME向第一AMF实体发送切换请求2，以使得第一AMF实体接收来自MME的切换请求2。
其中，该切换请求2中包括已经建立的PDN连接的信息。其中，PDN连接的信息的相关描述可参考步骤S1501，在此不再赘述。
可选的，若切换请求2中包括的已经建立的PDN连接的信息为该PDN连接对应的控制面功能实体的信息，则该PDN连接对应的控制面功能实体的信息可以是通过上述步骤S1502获取的，在此统一说明，以下不再赘述。
S1506、第一AMF实体向NRF实体发送请求消息，以使得NRF网元接收来自第一AMF实体的请求消息。
其中，该请求消息携带PDN连接的信息，用于请求该PDN连接对应的网络切片的S-NSSAI。
S1507、NRF实体根据PDN连接的信息，确定该PDN连接对应的网络切片的S-NSSAI。
具体的，NRF实体可以根据PDN连接的信息，查询NRF中存储的PDN连接的信息和该PDN连接对应的网络切片的S-NSSAI，从而获得该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
S1508、NRF实体向第一AMF实体发送响应消息，以使得第一AMF实体接收来自NRF实体的响应消息。
其中，该响应消息携带该PDN连接对应的网络切片的S-NSSAI。
需要说明的是，本申请实施例中，终端之前在EPC中可能已经建立了一个或多个PDN连接，因此，步骤S1505中的切换请求2中包括的已建立的PDN连接信息可能为一个或多个PDN连接的信息。该情况下，对于每一个PDN连接的信息，均可以参照步骤S1506-S1508分别执行；也可以是通过执行一次步骤S1506-S1508，获取一个或多个PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若第一AMF实体所在的PLMN与控制面功能实体所在的PLMN不相同时，步骤S1506中的请求消息中还可以携带该控制面功能实体所在的PLMN的PLMN标识，以使得第一AMF实体所在PLMN的NRF实体可以根据控制面功能实体所在的PLMN的标识确定出该控制面功能实体所在PLMN的NRF实体，进而从该控制面功能实体所在PLMN的NRF实体中获取该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
S1509、同步骤S405，相关描述可参考图4所示的实施例，在此不再赘述。
S1510、第一AMF实体向第二AMF实体发送切换请求3，以使得第二AMF实体接收来自第一AMF实体的切换请求3。
其中，该切换请求3可以包括该PDN连接对应的网络切片的S-NSSAI、以及从MME获取的该PDN连接的信息。
S1511、会话建立的其他流程。
其中，会话建立的其他流程例如可以包括根据PDN连接对应的S-NSSAI选择中间SMF实体或拜访地SMF(visited SMF，V-SMF)实体，具体可参考3GPP TS 23.502:"Procedures for the 5G System；Stage 2"，在此不再赘述。
基于本申请实施例提供的会话建立方法，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。相关技术效果分析可参考图14所示的会话建立系统部分，在此不再赘述。
其中，上述步骤S1501至S1511中控制面功能实体和第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图14所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图16所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S1601、当终端在5GC中建立PDU会话的过程中，控制面功能实体(即SMF实体+PGW-C实体)向NRF实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，以使得NRF实体接收来自控制面功能实体的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
可选的，本申请实施例中，控制面功能实体可以根据终端的签约数据，确定该PDU会话可能会切换到EPC，进而确定该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，并向NRF实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中的PDN连接的信息的相关描述可参考步骤S1501，在此不再赘述。
示例性的，控制面功能实体可以通过如下方式确定PDN连接对应的APN：控制面功能实体可以根据PDU会话对应的DNN确定PDN连接对应的APN。比如，PDU会话对应的DNN与PDN连接对应的APN相同；或者，可以根据PDU会话对应的DNN，以及DNN与APN的映射关系确定PDN连接对应的APN；或者，可以根据PDU会话对应的DNN以及PDU会话的S-NSSAI确定PDN连接对应的APN，等等，本申请实施例对此不作具体限定。
或者，示例性的，控制面功能实体可以通过如下方式确定PDN连接对应的PDN类型：如，PDN连接对应的PDN类型可以与PDU会话对应的PDU类型相同；或者，可以根据PDU会话对应的PDU类型，以及PDU类型与PDN类型的映射关系确定PDN连接对应的PDN类型，比如，可以将以太类型的PDU类型映射为非IP类型的PDN类型，等，本申请实施例对此不作具体限定。
或者，示例性的，控制面功能实体可以通过如下方式确定PDN连接对应的PDN地址：如，PDN连接对应的PDN地址可以与PDU会话对应的PDU地址相同；或者，可以根据PDU会话对应的PDU地址，以及PDU地址与PDN地址的映射关系确定PDN连接对应的PDN地址，本申请实施例对此不作具体限定。
可选的，本申请实施例中，控制面功能实体可以将PDU会话对应的S-NSSAI确定为PDU会话切换到EPC时该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，NRF实体接收来自控制面功能实体的该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI之后，可以建立或者存储该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI的对应关系，相关描述可参考图15所示的实施例中的步骤S1501，在此不再赘述。
S1602、终端从5GC切换到EPC。
其中，步骤S1602的相关实现可参考现有的实现方式，在此不再赘述。
S1603-S1611、同步骤S1503-S1511，相关描述可参考图5所示的实施例，在此不再赘述。
基于本申请实施例提供的会话建立方法，可以在终端从支持DCN的EPC切换到支 持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中建立会话。相关技术效果分析可参考图14所示的会话建立系统部分，在此不再赘述。
其中，上述步骤S1601至S1611中控制面功能实体和第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图18所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图19所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S1901、在用户面实体(即UPF实体+PGW-U实体)向NRF实体注册时或者控制面功能实体(即SMF实体+PGW-C实体)与用户面实体(即UPF实体+PGW-U实体)之间建立连接时，用户面实体向NRF实体发送该用户面实体的信息以及与该用户面实体的信息对应的网络切片的S-NSSAI，以使得NRF实体接收来自用户面实体的该用户面实体的信息以及对应的网络切片的S-NSSAI。
可选的，本申请实施例中，用户面实体的信息例如可以包括用户面实体所在的PLMN的信息、用户面实体的IP地址或者FQDN或者TEID、网络实例(network instance)等，本申请实施例对此不作具体限定。其中，当用户面实体可以服务一个S-NSSAI时，同一个用户面实体可以有一个或多个用户面实体的信息；或者，当用户面实体可以服务多个S-NSSAI时，同一个用户面实体可以有一个或多个用户面实体的信息，本申请实施例对此不作具体限定。比如，一个用户面实体的IP地址可以有一个或多个，不同的IP地址对应不同的S-NSSAI；或者，一个用户面实体的TEID有一个或多个，不同的TEID对应不同的S-NSSAI；或者，一个用户面实体的TEID可以分成一段或多段，不同的分段对应不同的S-NSSAI等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，用户面实体的信息可以包括在已建立的PDN连接的信息中，其中，PDN连接的信息的相关描述可参考上述各实施例，在此不再赘述。
可选的，本申请实施例中，NRF实体接收来自用户面实体的该用户面实体的信息以及对应的网络切片的S-NSSAI之后，可以建立或者存储该用户面实体的信息以及对应的网络切片的S-NSSAI的对应关系，本申请实施例对此不作具体限定。
示例性的，以用户面实体的信息为用户面实体的IP地址为例，则NRF实体中可以存储如表五所示的对应关系：
表五
用户面实体的信息 对应的网络切片的S-NSSAI
用户面实体的IP地址1 S-NSSAI1
用户面实体的IP地址2 S-NSSAI2
用户面实体的IP地址3 S-NSSAI3
当然，当用户面实体的信息为其他信息时，只需要将表五中的用户面实体的IP地址替换为相应的信息即可，在此不再一一赘述。
需要说明的是，本申请实施例中的步骤S1901是个可选的步骤，也可以不执行步骤S1901，而是通过其他方式在NRF实体上配置用户面实体的信息以及对应的网络切片的S-NSSAI的对应关系。比如，运营商或者操作运营管理(operation administration and maintenance，OA&M)在网络部署时直接在NRF实体上配置用户面实体的信息以及对应的网络切片的S-NSSAI的 对应关系，本申请实施例对此不作具体限定。
S1902、在控制面功能实体与用户面实体之间建立连接时，比如PDN连接建立过程中，若不同的网络切片的PDN连接对应用户面实体的不同信息，则用户面实体向控制面功能实体发送该PDN连接对应的用户面实体的信息，以使得控制面功能实体接收来自用户面实体的该PDN连接对应的用户面实体的信息。
其中，本申请实施例中，步骤S1902中的PDN连接对应用户面实体的信息可以为步骤S1901中的用户面实体的信息中的全部信息或者部分信息，本申请实施例对此不作具体限定。比如，步骤S1901中的用户面实体的信息例如可以是用户面实体的IP地址1、用户面实体的IP地址2和用户面实体的IP地址3，则步骤S1902中的PDN连接对应的用户面实体的信息可以是用户面实体的IP地址1、用户面实体的IP地址2或者用户面实体的IP地址3中的至少一个。
可选的，本申请实施例中，控制面功能实体接收来自用户面实体的该PDN连接对应的用户面实体的信息之后，可以存储该PDN连接对应的用户面实体的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，在控制面功能实体与用户面实体之间建立连接时，比如PDN连接建立过程中，用户面实体还可以向控制面功能实体发送与该PDN连接对应的用户面实体的信息对应的网络切片的S-NSSAI，以使得控制面功能实体接收来自用户面实体的与该PDN连接对应的用户面实体的信息对应的第二网络切片的S-NSSAI，进而可以存储该PDN连接对应的用户面实体的信息以及对应的网络切片的S-NSSAI的对应关系，本申请实施例对此不作具体限定。
示例性的，假设该PDN连接对应的用户面实体的信息包括用户面实体的IP地址1和用户面实体的IP地址2，则根据上述表五，与该PDN连接对应的用户面实体的信息对应的网络切片的S-NSSAI例如可以是与用户面实体的IP地址1对应的S-NSSAI1、以及与用户面实体的IP地址2对应的S-NSSAI2。
需要说明的是，本申请实施例中的步骤S1902是个可选的步骤，也可以不执行步骤S1902，而是通过其他方式在控制面功能实体上配置该PDN连接对应的用户面实体的信息以及对应的网络切片的S-NSSAI的对应关系。比如，运营商或者操作运营管理(operation administration and maintenance，OA&M)设备在网络部署时直接在控制面功能实体上配置该PDN连接对应的用户面实体的信息以及对应的网络切片的S-NSSAI的对应关系，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的步骤S1901与步骤S1902之间没有必然的执行先后顺序，可以是先执行步骤S1901，再执行步骤S1902；也可以是先执行步骤S1902，再执行步骤S1901；还可以是同时执行步骤S1901和S1902，本申请实施例对此不作具体限定。
S1903、在PDN连接建立过程中，若不同的网络切片的PDN连接对应不同的用户面实体的信息，则控制面功能实体向MME发送该PDN连接对应的用户面实体的第一信息，以使得MME接收来自控制面功能实体的该PDN连接对应的用户面实体的第一信息。
其中，本申请实施例中，步骤S1903中的PDN连接对应用户面实体的第一信息可以为步骤S1902中的PDN连接对应用户面实体的信息中的全部信息或者部分信息，本申请实施例对此不作具体限定。比如，步骤S1902中的PDN连接对应用户面实体的信息例如可以是用户面实体的IP地址1和用户面实体的IP地址2，则步骤S1903中的PDN连接对应的用户面实体 的第一信息可以是用户面实体的IP地址1和用户面实体的IP地址2中的至少一个。
可选的，本申请实施例中，若步骤S1903中的PDN连接对应用户面实体的第一信息为步骤S1902中的PDN连接对应用户面实体的信息中的部分信息，则控制面功能实体向MME发送的该PDN连接对应的用户面实体的第一信息可以为：控制面功能实体根据所选择的S-NSSAI，从接收到的来自用户面实体的PDN连接对应的用户面实体的信息中确定的与所选择的S-NSSAI对应的用户面实体的信息；或者，控制面功能实体向MME发送的PDN连接对应的用户面实体的第一信息可以为：控制面功能实体根据自身配置从接收到的来自用户面实体的PDN连接对应的用户面实体的信息中所选择的信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，MME接收来自控制面功能实体的该PDN连接对应的用户面实体的第一信息之后，可以存储该PDN连接对应的用户面实体的第一信息，比如可以在终端上下文中存储该PDN连接对应的用户面实体的第一信息，本申请实施例对此不作具体限定。
进一步的，本申请实施例提供的会话建立方法还可以包括如下步骤：
S1904-S1905、同图15所示的实施例中的步骤S1503-S1504，相关描述可参考图15所示的实施例，在此不再赘述。
S1906、MME向第一AMF实体发送切换请求2，以使得第一AMF实体接收来自MME的切换请求2。
其中，该切换请求2中包括已建立的PDN连接(如步骤S1902或S1903中的PDN连接)对应的用户面实体的第一信息。其中，该PDN连接对应的用户面实体的第一信息可以是通过上述步骤S1903获取的，在此统一说明，以下不再赘述。
S1907、第一AMF实体向NRF实体发送请求消息，以使得NRF网元接收来自第一AMF实体的请求消息。
其中，该请求消息携带已建立的PDN连接对应的用户面实体的第一信息，用于请求该PDN连接对应的第一网络切片的S-NSSAI。
S1908、NRF实体根据PDN连接对应的用户面实体的第一信息，确定该PDN连接对应的第一网络切片的S-NSSAI。
具体的，NRF实体可以根据PDN连接对应的用户面实体的第一信息，查询NRF中存储的用户面实体的信息和对应的网络切片的S-NSSAI的对应关系(比如如表五所示的对应关系)，从而获得该PDN连接对应的第一网络切片的S-NSSAI，本申请实施例对此不作具体限定。
S1909、NRF实体向第一AMF实体发送响应消息，以使得第一AMF实体接收来自NRF实体的响应消息。
其中，该响应消息携带该PDN连接对应的第一网络切片的S-NSSAI。
需要说明的是，本申请实施例中，终端之前在EPC中可能已经建立了一个或多个PDN连接，因此，步骤S1906中的切换请求2中包括的已建立的PDN连接对应的用户面实体的第一信息可能为一个或多个PDN连接对应的用户面实体的第一信息。该情况下，对于每一个PDN连接，均可以参照步骤S1907-S1909分别执行；也可以是通过执行一次步骤S1907-S1909，获取一个或多个PDN对应的第一网络切片的S-NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若第一AMF实体所在的PLMN与用户面实体所在的PLMN不相同时，步骤S1907中的请求消息中还可以携带该用户面实体所在的PLMN的PLMN标识，以使得第一AMF实体所在PLMN的NRF实体可以根据用户面实体所在的PLMN的标识确定出该用户面实体所在PLMN的NRF实体，进而从该用户面实体所在PLMN的NRF实体中 获取该PDN连接对应的网络切片的S-NSSAI，本申请实施例对此不作具体限定。
S1910、同图4所示的实施例中的步骤S405，相关描述可参考图4所示的实施例，在此不再赘述。
S1911、第一AMF实体向第二AMF实体发送切换请求3，以使得第二AMF实体接收来自第一AMF实体的切换请求3。
其中，该切换请求3可以包括该PDN连接对应的第一网络切片的S-NSSAI、以及从MME获取的该PDN连接的信息。
可选的，本申请实施例中，MME也可以通过图15所示的方式获取PDN连接对应的控制面功能实体的信息，进而在向第一AMF实体发送的切换请求2中还包括该PDN连接对应的控制面功能实体的信息，进而第一AMF实体向第二AMF实体发送的切换请求3中还可以包括PDN连接对应的控制面功能实体的信息，本申请实施例对此不作具体限定。
S1912、后续切换的其他流程。
其中，后续切换的其他流程例如可以包括第二AMF实体根据PDN连接对应的第一网络切片的S-NSSAI选择控制面功能实体或拜访地SMF(visited SMF，V-SMF)实体或者根据控制面功能实体的信息选择控制面功能实体，具体可参考3GPP TS 23.502:"Procedures for the 5G System；Stage 2"，在此不再赘述。
或者，可选的，本申请实施例中，在第一AMF实体根据PDN连接对应的用户面实体的第一信息，向NRF实体请求该PDN连接对应的第一网络切片的S-NSSAI的同时，第一AMF实体也可以根据该PDN连接对应的控制面功能实体的FQDN，向NRF实体请求控制面功能实体的地址，进而将获得的控制面功能实体的地址发送给第二AMF实体，使得第二AMF实体根据该控制面功能实体的地址选择对应的控制面功能实体，本申请实施例对此不作具体限定。
基于本申请实施例提供的会话建立方法，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中互通并建立相应会话。相关技术效果分析可参考图18所示的会话建立系统部分，在此不再赘述。
其中，上述步骤S1901至S1912中用户面实体、或控制面功能实体、或第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
或者，可选的，以图18所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图20所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S2001、同图19所示的实施例中的步骤S1902，相关描述可参考图19所示的实施例，在此不再赘述。
需要说明的是，本申请实施例中的步骤S2001是个可选的步骤，也可以不执行步骤S2001，直接执行下述步骤S2002，本申请实施例对此不作具体限定。
S2002、控制面功能实体向NRF实体发送用户面实体的信息以及对应的网络切片的S-NSSAI，以使得NRF实体接收来自控制面功能实体的用户面实体的信息以及对应的网络切片的S-NSSAI。
可选的，本申请实施例中，用户面实体的信息以及对应的网络切片的S-NSSAI可以是用户面实体发送给控制面功能实体的。比如，用户面实体的信息为用户面实体发送给控制面功能实体的PDN连接对应的用户面实体的信息，相应的，与用户面实体的信息对应的网络切片 的S-NSSAI为与PDN连接对应的用户面实体的信息对应的网络切片的S-NSSAI；或者，用户面实体的信息以及对应的网络切片的S-NSSAI也可以是预先配置在控制面功能实体上的，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中的步骤S2002是个可选的步骤，也可以不执行步骤S2002，而是通过其他方式在NRF实体上配置用户面实体的信息和网络切片的S-NSSAI的对应关系。比如，营商或者OA&M设备在网络部署时直接在NRF上配置用户面实体的信息以及网络切片的S-NSSAI的对应关系；或者，在控制面功能实体向NRF实体注册时，控制面功能实体将管辖下所有用户面实体的信息与该用户面实体的信息对应的网络切片的S-NSSAI的对应关系存储至NRF实体中，本申请实施例对此不作具体限定。
S2003-2012、同图19所示的实施例中的步骤S1903-S1912，相关描述可参考图19所示的实施例，在此不再赘述。
基于本申请实施例提供的会话建立方法，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中互通并建立相应会话。相关技术效果分析可参考图18所示的会话建立系统部分，在此不再赘述。
其中，上述步骤S2001至S2012中用户面实体、或控制面功能实体、或第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
或者，可选的，以图18所示的会话建立系统应用于如图1所示的4G网络和5G网络互通架构为例，如图21所示，为本申请实施例提供的一种会话建立方法，包括如下步骤：
S2101-S2103、同图19所示的实施例中的步骤S1901-S1903或者图20所示的实施例中的步骤S2001-S2003，相关描述可参考图19或图20所示的实施例，在此不再赘述。
S2104、终端向第一AMF实体发送注册请求，以使得第一AMF实体接收来自终端的注册请求。其中，该注册请求携带终端的标识。
示例性的，本申请实施例中，终端的标识例如可以是全球唯一临时标识(globally unique temporary identity，GUTI)，本申请实施例对此不作具体限定。
可选的，该注册请求还可以携带终端请求的NSSAI(requested NSSAI)以及终端的位置信息等，本申请实施例对此不作具体限定。
S2105、第一AMF实体根据终端的标识获取MME的地址，并向MME发送上下文请求消息，以使得MME接收来自第一AMF实体的上下文请求消息。其中，该上下文请求消息用于请求获取终端的上下文。
S2106、MME向第一AMF实体发送终端的上下文，以使得第一AMF实体接收来自MME的终端的上下文。
其中，该终端的上下文中包括步骤S1903或者步骤S2003中，控制面功能实体向MME发送的该PDN连接对应的用户面实体的第一信息。
S2107-S2110、同图19所示的实施例中的步骤S1907-S1910，相关描述可参考图19所示的实施例，在此不再赘述。
其中，本申请实施例中，在第一AMF实体获取该PDN连接对应的第一网络切片的S-NSSAI之后，可以将该PDN连接对应的第一网络切片的S-NSSAI存储至终端的上下文中，本申请实施例对此不作具体限定。
S2111、第一AMF实体向第二AMF实体发送上下文传输请求，以使得第二AMF实体接 收来自第一AMF实体的上下文传输请求。其中，该上下文传输请求中包括终端的上下文信息。
可选的，本申请实施例中，MME也可以通过图15所示的方式获取PDN连接对应的控制面功能实体的信息，进而在向第一AMF实体发送的终端的上下文中还包括该PDN连接对应的控制面功能实体的信息，进而第一AMF实体向第二AMF实体发送的终端的上下文中还可以包括PDN连接对应的控制面功能实体的信息，本申请实施例对此不作具体限定。
S2112、后续切换的其他流程。
其中，后续切换的其他流程例如可以包括第二AMF实体根据PDN连接对应的S-NSSAI选择控制面功能实体或拜访地SMF(visited SMF，V-SMF)实体或者根据控制面功能实体的信息选择控制面功能实体，具体可参考3GPP TS 23.502:"Procedures for the 5G System；Stage 2"，在此不再赘述。
或者，可选的，本申请实施例中，在第一AMF实体根据PDN连接对应的用户面实体的第一信息，向NRF实体请求该PDN连接对应的第一网络切片的S-NSSAI的同时，第一AMF实体也可以根据该PDN连接对应的控制面功能实体的FQDN，向NRF实体请求控制面功能实体的地址，进而将获得的控制面功能实体的地址发送给第二AMF实体，使得第二AMF实体根据该控制面功能实体的地址选择对应的控制面功能实体，本申请实施例对此不作具体限定。
基于本申请实施例提供的会话建立方法，可以在终端从支持DCN的EPC切换到支持网络切片的5GC时，可以根据选择的S-NSSAI在5GC的网络切片中互通并建立相应会话。相关技术效果分析可参考图18所示的会话建立系统部分，在此不再赘述。
其中，上述步骤S2101至S2112中用户面实体、或控制面功能实体、或第一AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述终端、第一移动管理实体和第二移动管理实体为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端、第一移动管理实体和第二移动管理实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图8示出了上述实施例所涉及第一移动管理实体80的结构示意图。如图8所示，该第一移动管理实体80包括：第一获取模块801和第二获取模块802；第一获取模块801，用于获取终端接入到EPC时已建立的PDN连接的信息；第二获取模块802，用于根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于指示建立PDU会话的网络切 片。
可选的，第二获取模块802，还用于获取第二移动管理实体的信息。
可选的，第二获取模块802用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：用于根据PDN连接的信息，确定PDN连接对应的网络切片的S-NSSAI。
在一种可能的实现方式中，该PDN连接的信息包括该PDN连接对应的APN；第二获取模块802用于根据PDN连接的信息，确定PDN连接对应的网络切片的S-NSSAI，包括：用于根据APN，以及预先配置的APN和S-NSSAI的对应关系，确定PDN连接对应的网络切片的S-NSSAI。
进一步的，预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对多关系；第二获取模块802用于根据APN，以及预先配置的APN和S-NSSAI的对应关系，确定PDN连接对应的网络切片的S-NSSAI，包括：用于根据预先配置的APN和S-NSSAI的一对多关系中每个S-NSSAI的优先级、每个S-NSSAI所指示的网络切片的负荷信息、以及第一移动管理实体80中配置的移动管理实体集合所支持的NSSAI中的至少一个，以及APN和预先配置的APN和S-NSSAI的一对多关系，确定PDN连接对应的网络切片的S-NSSAI。
在另一种可能的实现方式中，该PDN连接的信息包括该PDN连接对应的控制面功能实体的信息；第二获取模块802用于根据PDN连接的信息，确定PDN连接对应的网络切片的S-NSSAI，包括：用于根据控制面功能实体的信息，确定PDN连接对应的网络切片的S-NSSAI。
在另一种可能的实现方式中，该PDN连接的信息包括该PDN连接对应的控制面功能实体的信息；第二获取模块802用于根据PDN连接的信息，获取PDN连接对应的网络切片的S-NSSAI，包括：用于根据控制面功能实体的信息，向控制面功能实体发送请求消息，该请求消息用于请求获取该PDN连接对应的网络切片的S-NSSAI；接收来自该控制面功能实体的该PDN连接对应的网络切片的S-NSSAI。
可选的，第二获取模块802还用于获取第二移动管理实体的信息，包括：用于根据该PDN连接对应的网络切片的S-NSSAI，获取第二移动管理实体的信息。
一种可能的实现方式中，第二获取模块802用于根据该PDN连接对应的网络切片的S-NSSAI，获取第二移动管理实体的信息，包括：用于根据PDN连接的信息，确定PDN连接对应的网络切片实例；根据PDN连接对应的网络切片的S-NSSAI和网络切片实例的信息，确定第二移动管理实体的信息。
一种可能的实现方式中，第二获取模块802用于根据该PDN连接对应的网络切片的S-NSSAI，获取第二移动管理实体的信息，包括：用于向NSSF实体发送该PDN连接对应的网络切片的S-NSSAI，该PDN连接对应的网络切片的S-NSSAI用于确定第二移动管理实体的信息；接收来自NSSF实体的第二移动管理实体的信息。
可选的，第二获取模块802用于根据PDN连接的信息，获取PDN连接对应的网络切片的S-NSSAI；以及，第二获取模块802还用于获取第二移动管理实体的信息，包括：用于向NSSF实体发送切片选择请求消息，切片选择请求消息携带PDN连接的信息，PDN连接的信息用于确定第二移动管理实体的信息和PDN连接对应的网络切片的S-NSSAI；接收来自NSSF实体的候选移动管理实体集合的信息和PDN连接对应的网络切片的S-NSSAI；根据候选移动管理实体集合的信息，从候选移动管理实体集合中选择第二移动管理实体。
或者，可选的，第二获取模块802用于根据PDN连接的信息，获取PDN连接对应的网 络切片的S-NSSAI；以及，第二获取模块802还用于获取第二移动管理实体的信息，包括：用于向NSSF实体发送切片选择请求消息，切片选择请求消息携带PDN连接的信息，PDN连接的信息用于确定第二移动管理实体的信息和PDN连接对应的网络切片的S-NSSAI；接收来自NSSF实体的PDN连接对应的网络切片的S-NSSAI和第二移动管理实体的信息。
在一种可能的实现方式中，第一移动管理实体80与第二移动管理实体不同；第一移动管理实体80还包括收发模块803；收发模块803，用于向第二移动管理实体发送PDN连接对应的网络切片的S-NSSAI。
其中，收发模块803具体用于：通过接入设备向第二移动管理实体发送PDN连接对应的网络切片的S-NSSAI。
在另一种可能的实现方式中，第一移动管理实体80与第二移动管理实体相同；第一移动管理实体80还包括收发模块803和建立模块804；收发模块803，用于向终端发送注册接受消息，注册接受消息携带PDN连接对应的网络切片的S-NSSAI；收发模块803，还用于接收来自终端的PDU会话建立请求，该PDU会话建立请求携带PDN连接对应的网络切片的S-NSSAI；建立模块804，用于根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。
在另一种可能的实现方式中，第一移动管理实体80与第二移动管理实体相同；第一移动管理实体80还包括收发模块803和建立模块804；收发模块803，用于向终端发送注册接受消息；收发模块803，还用于接收来自终端的PDU会话建立请求，该PDU会话建立请求携带终端请求的网络切片的S-NSSAI和终端请求的PDN连接对应的APN；建立模块804，用于在终端请求的网络切片的S-NSSAI与预先存储的PDN连接对应的网络切片的S-NSSAI相同，且终端请求的PDN连接对应的APN与PDN连接对应的APN相同的情况下，根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一移动管理实体80以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到第一移动管理实体80可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得第一移动管理实体80执行上述方法实施例中的会话建立方法。
具体的，图8中的第一获取模块801、第二获取模块802、收发模块803和建立模块804的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图8中的第一获取模块801、第二获取模块802和建立模块804的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图8中的收发模块803的功能/实现过程可以通过图3中的通信接口304来实现。
由于本申请实施例提供的第一移动管理实体可用于执行上述会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，以采用集成的方式划分各个功能模块的情况下，图9示出了一种装置90的结构示意图。该装置90可以是终端，也可以是终端内的芯片，本申请实施例对此不作具体限定。其 中，该装置90包括：接收模块901和发送模块902；发送模块902，用于向第一移动管理实体发送注册请求消息，该注册请求消息携带终端的标识，该终端的标识用于获取终端的签约数据，其中，签约数据包括在终端接入到EPC时已建立的PDN连接的信息；接收模块901，还用于接收注册接受消息，该注册接受消息携带PDN连接对应的网络切片的S-NSSAI；发送模块902，还用于发送PDU会话建立请求，该PDU会话建立请求携带PDN连接对应的网络切片的S-NSSAI，该PDU会话建立请求用于请求在PDN连接对应的网络切片中建立PDU会话。
可选的，注册接受消息还携带允许进行切换的PDN连接的信息；该装置90还包括处理模块903；处理模块903，用于根据允许进行切换的PDN连接的信息，释放EPC中除允许进行切换的PDN连接之外的其他所有PDN连接。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该装置90以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到装置90可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得装置90执行上述方法实施例中的会话建立方法。
具体的，图9中的接收模块901、发送模块902和处理模块903的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图9中的处理模块903的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图9中的接收模块901和发送模块902的功能/实现过程可以通过图3中的通信接口304来实现。
可选的，当该装置90是芯片时，则接收模块901和发送模块902的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置90是芯片时，存储器303可以为芯片内的存储单元，如寄存器、缓存等。当然，当该装置90是终端时，存储器303可以是终端内的位于芯片外部的存储单元，本申请实施例对此不作具体限定。
由于本申请实施例提供的装置可用于执行上述会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，以采用集成的方式划分各个功能模块的情况下，图10示出了一种第二移动管理实体100的结构示意图。该第二移动管理实体100包括：收发模块1001和处理模块1002。收发模块1001，用于接收来自第一移动管理实体的终端接入到EPC时已建立的PDN连接对应的网络切片的S-NSSAI；收发模块1001，还用于向终端发送注册接受消息；收发模块1001，还用于接收来自终端的PDU会话建立请求，该PDU会话建立请求用于请求在PDN连接对应的网络切片中建立PDU会话；处理模块1002，用于根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能 描述，在此不再赘述。
在本实施例中，该第二移动管理实体100以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到第二移动管理实体100可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得第二移动管理实体100执行上述方法实施例中的会话建立方法。
具体的，图10中的收发模块1001和处理模块1002的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图10中的处理模块1002的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图10中的收发模块1001的功能/实现过程可以通过图3中的通信接口304来实现。
由于本申请实施例提供的第二移动管理实体可用于执行上述会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
上述实施例中，第一移动管理实体80、装置90和第二移动管理实体100均以采用集成的方式划分各个功能模块的形式来呈现。当然，本申请实施例也可以对应各个功能划分第一移动管理实体、装置和第二移动管理实体的各个功能模块，本申请实施例对此不作具体限定。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持第一移动管理实体实现上述的会话建立方法，例如根据PDN连接的信息，获取该PDN连接对应的网络切片的S-NSSAI。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存第一移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持第二移动管理实体实现上述的会话建立方法，例如根据PDN连接对应的网络切片的S-NSSAI，在该PDN连接对应的网络切片中建立PDU会话。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存第二移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
比如，以采用集成的方式划分各个功能模块的情况下，图17示出了上述实施例所涉及控制面功能实体170的结构示意图。如图17所示，该控制面功能实体170包括收发模块1701和处理模块1702。其中，处理模块1702，用于获取终端接入到EPC时已建立的PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。收发模块1701，用于向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI，由第一移动管理实体根据该PDN连接的信息从该网络存储功能实体中获取该PDN连接对应的网络切片的S-NSSAI，其中，该PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。
可选的，收发模块1701具体用于：在该PDN连接建立的过程中或者在该PDU会话建立的过程中，向网络存储功能实体发送该PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。
可选的，收发模块1701，还用于向该EPC中的第三移动管理实体发送该PDN连接的信息，由该第三移动管理实体向该第一移动管理实体发送该PDN连接的信息。
可选的，处理模块1702具体用于：将该PDU会话对应的S-NSSAI确定为该PDU会话 切换到该EPC时该PDN连接对应的网络切片的S-NSSAI。
比如，以采用集成的方式划分各个功能模块的情况下，图10示出了一种第二移动管理实体100的结构示意图。该第二移动管理实体100包括：收发模块1001和处理模块1002。收发模块1001，用于接收来自第一移动管理实体的终端接入到EPC时已建立的PDN连接对应的网络切片的S-NSSAI；收发模块1001，还用于向终端发送注册接受消息；收发模块1001，还用于接收来自终端的PDU会话建立请求，该PDU会话建立请求用于请求在PDN连接对应的网络切片中建立PDU会话；处理模块1002，用于根据PDN连接对应的网络切片的S-NSSAI，在PDN连接对应的网络切片中建立PDU会话。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该控制面功能实体170以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到控制面功能实体170可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得控制面功能实体170执行上述方法实施例中的会话建立方法。
具体的，图17中的收发模块1701和处理模块1702的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图17中的处理模块1702的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图17中的收发模块1701的功能/实现过程可以通过图3中的通信接口304来实现。
由于本申请实施例提供的控制面功能实体可用于执行上述会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持控制面功能实体实现上述的会话建立方法，例如获取终端接入到EPC时已建立的PDN连接的信息以及该PDN连接对应的网络切片的S-NSSAI。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存控制面功能实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图22示出了一种网络存储功能实体220的结构示意图。该网络存储功能实体220包括：处理模块2201和收发模块2202。其中，收发模块2202，用于接收来自第一移动管理实体的PDN连接对应的用户面实体的第一信息；处理模块2201，用于根据第一信息，确定PDN连接对应的第一网络切片的S-NSSAI；收发模块，还用于向第一移动管理实体发送第一网络切片的S-NSSAI。
可选的，在收发模块2202，还用于接收来自用户面实体的第一信息和与第一信息对应的第一网络切片的S-NSSAI。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该网络存储功能实体220以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该网络存储功能实体220可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得网络存储功能实体220执行上述方法实施例中的会话建立方法。
具体的，图22中的收发模块2202和处理模块2201的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图22中的处理模块2201的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图22中的收发模块2202的功能/实现过程可以通过图3中的通信接口304来实现。
由于本实施例提供的网络存储功能实体220可执行上述的会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持网络存储功能实体实现上述认证方法，例如根据第一信息，确定PDN连接对应的第一网络切片的S-NSSAI。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存网络存储功能实体必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图23示出了一种用户面实体230的结构示意图。该用户面实体230包括：处理模块2301和收发模块2302。其中，处理模块2301，用于获取该用户面实体的信息以及与该用户面实体的信息对应的网络切片的S-NSSAI；收发模块，用于向网络存储功能实体发送该用户面实体的信息以及该网络切片的S-NSSAI，由第一移动管理实体根据PDN连接对应的用户面实体的第一信息，从该网络存储功能实体中获取该PDN连接对应的第一网络切片的S-NSSAI。
可选的，收发模块2302具体用于：在该用户面实体向该网络存储功能实体注册过程中或者该PDN连接建立的过程中或者在分组数据单元PDU会话建立的过程中，向该网络存储功能实体发送该用户面实体的信息以及该网络切片的S-NSSAI。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该用户面实体230以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该用户面实体230可以采用图3所示的形式。
比如，图3中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得用户面实体230执行上述方法实施例中的会话建立方法。
具体的，图23中的收发模块2302和处理模块2301的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图23中的处理模块2301的功能/实现过程可以通过图3中的处理器301调用存储器303中存储的计算机执行指令来实现，图23中的收发模块2302的功能/实现过程可以通过图3中的通信接口304来实现。
由于本实施例提供的用户面实体230可执行上述的会话建立方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持用户面实体实现上述认证方法，例如获取该用户面实体的信息以及与该用户面实体的信息对应的网络切片的S-NSSAI。在一种可能的设计中，该装置还包括存储器。 该存储器，用于保存用户面实体必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (54)

  1. 一种会话建立方法，其特征在于，所述方法包括：
    第一移动管理实体获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；
    所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI，所述PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一移动管理实体获取第二移动管理实体的信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI。
  4. 根据权利要求3所述的方法，其特征在于，所述PDN连接的信息包括所述PDN连接对应的接入点名称APN；所述第一移动管理实体根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体根据所述APN，以及预先配置的APN和S-NSSAI的对应关系，确定所述PDN连接对应的网络切片的S-NSSAI。
  5. 根据权利要求4所述的方法，其特征在于，所述预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对多关系；
    所述第一移动管理实体根据所述APN，以及预先配置的APN和S-NSSAI的对应关系，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体根据所述预先配置的APN和S-NSSAI的一对多关系中每个S-NSSAI的优先级、所述每个S-NSSAI所指示的网络切片的负荷信息、以及所述第一移动管理实体中配置的移动管理实体集合所支持的NSSAI中的至少一个，以及所述APN和所述预先配置的APN和S-NSSAI的一对多关系，确定所述PD N连接对应的网络切片的S-NSSAI。
  6. 根据权利要求3所述的方法，其特征在于，所述PDN连接的信息包括所述PDN连接对应的控制面功能实体的信息；所述第一移动管理实体根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体根据所述控制面功能实体的信息，确定所述PDN连接对应的网络切片的S-NSSAI。
  7. 根据权利要求1或2所述的方法，其特征在于，所述PDN连接的信息包括所述PDN连接对应的控制面功能实体的信息；所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体根据所述控制面功能实体的信息，向所述控制面功能实体发送请求消息，所述请求消息用于请求获取所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体接收来自所述控制面功能实体的所述PDN连接对应的网络切 片的S-NSSAI。
  8. 根据权利要求1或2所述的方法，其特征在于，所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体向网络存储功能实体发送所述PDN连接的信息；
    所述第一移动管理实体接收来自所述网络存储功能实体的所述PDN连接对应的网络切片的S-NSSAI。
  9. 根据权利要求8所述的方法，其特征在于，所述第一移动管理实体获取终端接入到EPC时已建立的PDN连接的信息，包括：
    所述第一移动管理实体接收来自所述EPC中的第三移动管理实体的所述PDN连接的信息。
  10. 根据权利要求6-9任一项所述的方法，其特征在于，所述控制面功能实体的信息包括所述控制面功能实体的网络之间互连的协议IP地址或全量域名FQDN。
  11. 根据权利要求2-10任一项所述的方法，其特征在于，所述第一移动管理实体获取第二移动管理实体的信息，包括：
    所述第一移动管理实体根据所述PDN连接对应的网络切片的S-NSSAI，获取所述第二移动管理实体的信息。
  12. 根据权利要求2所述的方法，其特征在于，所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI；以及，所述第一移动管理实体获取第二移动管理实体的信息，包括：
    所述第一移动管理实体向NSSF实体发送切片选择请求消息，所述切片选择请求消息携带所述PDN连接的信息，所述PDN连接的信息用于确定所述第二移动管理实体的信息和所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体接收来自所述NSSF实体的候选移动管理实体集合的信息和所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体根据候选移动管理实体集合的信息，从所述候选移动管理实体集合中选择所述第二移动管理实体。
  13. 根据权利要求2所述的方法，其特征在于，所述第一移动管理实体根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI；以及，所述第一移动管理实体获取第二移动管理实体的信息，包括：
    所述第一移动管理实体向NSSF实体发送切片选择请求消息，所述切片选择请求消息携带所述PDN连接的信息，所述PDN连接的信息用于确定所述第二移动管理实体的信息和所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体接收来自所述NSSF实体的所述PDN连接对应的网络切片的S-NSSAI和所述第二移动管理实体的信息。
  14. 根据权利要求2-13任一项所述的方法，其特征在于，所述第一移动管理实体与所述第二移动管理实体不同；所述方法还包括：
    所述第一移动管理实体向所述第二移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI。
  15. 根据权利要求14所述的方法，其特征在于，所述第一移动管理实体向所述第二 移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述第一移动管理实体通过接入设备向所述第二移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI。
  16. 根据权利要求14或15所述的方法，其特征在于，所述方法还包括：
    所述第二移动管理实体向所述终端发送注册接受消息；
    所述第二移动管理实体接收来自所述终端的PDU会话建立请求，所述PDU会话建立请求用于请求在所述PDN连接对应的网络切片中建立PDU会话；
    所述第二移动管理实体根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  17. 根据权利要求2-13任一项所述的方法，其特征在于，所述第一移动管理实体与所述第二移动管理实体相同；所述方法还包括：
    所述第一移动管理实体向所述终端发送注册接受消息，所述注册接受消息携带所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体接收来自所述终端的PDU会话建立请求，所述PDU会话建立请求携带所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  18. 根据权利要求2-13任一项所述的方法，其特征在于，所述第一移动管理实体与所述第二移动管理实体相同；所述方法还包括：
    所述第一移动管理实体向所述终端发送注册接受消息；
    所述第一移动管理实体接收来自所述终端的PDU会话建立请求，所述PDU会话建立请求携带所述终端请求的网络切片的S-NSSAI和所述终端请求的PDN连接对应的APN；
    在所述终端请求的网络切片的S-NSSAI与预先存储的所述PDN连接对应的网络切片的S-NSSAI相同，且所述终端请求的PDN连接对应的APN与所述PDN连接对应的APN相同的情况下，所述第一移动管理实体根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  19. 一种会话建立方法，其特征在于，所述方法包括：
    终端向第一移动管理实体发送注册请求消息，所述注册请求消息携带所述终端的标识，所述终端的标识用于获取所述终端的签约数据，其中，所述签约数据包括在所述终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；
    所述终端接收注册接受消息，所述注册接受消息携带所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述终端发送分组数据单元PDU会话建立请求，所述PDU会话建立请求携带所述PDN连接对应的网络切片的S-NSSAI，所述PDU会话建立请求用于请求在所述PDN连接对应的网络切片中建立PDU会话。
  20. 根据权利要求19所述的方法，其特征在于，所述注册接受消息还携带允许进行切换的PDN连接的信息；所述方法还包括：
    所述终端根据所述允许进行切换的PDN连接的信息，释放所述EPC中除所述允许进行切换的PDN连接之外的其他所有PDN连接。
  21. 一种会话建立方法，其特征在于，所述方法包括：
    第二移动管理实体接收来自第一移动管理实体的终端接入到分组核心网EPC时已建立的分组数据网络PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述第二移动管理实体向终端发送注册接受消息；
    所述第二移动管理实体接收来自所述终端的分组数据单元PDU会话建立请求，所述PDU会话建立请求用于请求在所述PDN连接对应的网络切片中建立PDU会话；
    所述第二移动管理实体根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  22. 一种第一移动管理实体，其特征在于，所述第一移动管理实体包括：第一获取模块和第二获取模块；
    所述第一获取模块，用于获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；
    所述第二获取模块，用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI，所述PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。
  23. 根据权利要求22所述的第一移动管理实体，其特征在于，
    所述第二获取模块，还用于获取第二移动管理实体的信息。
  24. 根据权利要求22或23所述的第一移动管理实体，其特征在于，所述第二获取模块用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI。
  25. 根据权利要求24所述的第一移动管理实体，其特征在于，所述PDN连接的信息包括所述PDN连接对应的接入点名称APN；所述第二获取模块用于根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    用于根据所述APN，以及预先配置的APN和S-NSSAI的对应关系，确定所述PDN连接对应的网络切片的S-NSSAI。
  26. 根据权利要求25所述的第一移动管理实体，其特征在于，所述预先配置的APN和S-NSSAI的对应关系包括APN和S-NSSAI的一对多关系；
    所述第二获取模块用于根据所述APN，以及预先配置的APN和S-NSSAI的对应关系，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    用于根据所述预先配置的APN和S-NSSAI的一对多关系中每个S-NSSAI的优先级、所述每个S-NSSAI所指示的网络切片的负荷信息、以及所述第一移动管理实体中配置的移动管理实体集合所支持的NSSAI中的至少一个，以及所述APN和所述预先配置的APN和S-NSSAI的一对多关系，确定所述PDN连接对应的网络切片的S-NSSAI。
  27. 根据权利要求24所述的第一移动管理实体，其特征在于，所述PDN连接的信息包括所述PDN连接对应的控制面功能实体的信息；所述第二获取模块用于根据所述PDN连接的信息，确定所述PDN连接对应的网络切片的S-NSSAI，包括：
    用于根据所述控制面功能实体的信息，确定所述PDN连接对应的网络切片的S-NSSAI。
  28. 根据权利要求22或23所述的第一移动管理实体，其特征在于，所述PDN连接的信息包括所述PDN连接对应的控制面功能实体的信息；所述第二获取模块用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    用于根据所述控制面功能实体的信息，向所述控制面功能实体发送请求消息，所述请求消息用于请求获取所述PDN连接对应的网络切片的S-NSSAI；接收来自所述控制面功能实体的所述PDN连接对应的网络切片的S-NSSAI。
  29. 根据权利要求22或23所述的第一移动管理实体，其特征在于，所述第二获取模块用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI，包括：
    用于向网络存储功能实体发送所述PDN连接的信息；接收来自所述网络存储功能实体的所述PDN连接对应的网络切片的S-NSSAI。
  30. 根据权利要求29所述的第一移动管理实体，其特征在于，所述第一获取模块具体用于：
    接收来自所述EPC中的第三移动管理实体的所述PDN连接的信息。
  31. 根据权利要求23-30任一项所述的第一移动管理实体，其特征在于，所述第二获取模块还用于获取第二移动管理实体的信息，包括：
    用于根据所述PDN连接对应的网络切片的S-NSSAI，获取所述第二移动管理实体的信息。
  32. 根据权利要求23所述的第一移动管理实体，其特征在于，所述第二获取模块用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI；以及，所述第二获取模块还用于获取第二移动管理实体的信息，包括：
    用于向NSSF实体发送切片选择请求消息，所述切片选择请求消息携带所述PDN连接的信息，所述PDN连接的信息用于确定所述第二移动管理实体的信息和所述PDN连接对应的网络切片的S-NSSAI；接收来自所述NSSF实体的候选移动管理实体集合的信息和所述PDN连接对应的网络切片的S-NSSAI；根据候选移动管理实体集合的信息，从所述候选移动管理实体集合中选择所述第二移动管理实体。
  33. 根据权利要求23所述的第一移动管理实体，其特征在于，所述第二获取模块用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的S-NSSAI；以及，所述第二获取模块还用于获取第二移动管理实体的信息，包括：
    用于向NSSF实体发送切片选择请求消息，所述切片选择请求消息携带所述PDN连接的信息，所述PDN连接的信息用于确定所述第二移动管理实体的信息和所述PDN连接对应的网络切片的S-NSSAI；接收来自所述NSSF实体的所述PDN连接对应的网络切片的S-NSSAI和所述第二移动管理实体的信息。
  34. 根据权利要求23-33任一项所述的第一移动管理实体，其特征在于，所述第一移动管理实体与所述第二移动管理实体不同；所述第一移动管理实体还包括收发模块；
    所述收发模块，用于向所述第二移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI。
  35. 根据权利要求34所述的第一移动管理实体，其特征在于，所述收发模块具体用于：
    通过接入设备向所述第二移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI。
  36. 根据权利要求34或35所述的第一移动管理实体，其特征在于，所述第一移动 管理实体与所述第二移动管理实体相同；所述第一移动管理实体还包括收发模块和建立模块；
    所述收发模块，用于向所述终端发送注册接受消息，所述注册接受消息携带所述PDN连接对应的网络切片的S-NSSAI；
    所述收发模块，还用于接收来自所述终端的PDU会话建立请求，所述PDU会话建立请求携带所述PDN连接对应的网络切片的S-NSSAI；
    所述建立模块，用于根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  37. 根据权利要求23-33任一项所述的第一移动管理实体，其特征在于，所述第一移动管理实体与所述第二移动管理实体相同；所述第一移动管理实体还包括收发模块和建立模块；
    所述收发模块，用于向所述终端发送注册接受消息；
    所述收发模块，还用于接收来自所述终端的PDU会话建立请求，所述PDU会话建立请求携带所述终端请求的网络切片的S-NSSAI和所述终端请求的PDN连接对应的APN；
    所述建立模块，还用于在所述终端请求的网络切片的S-NSSAI与预先存储的所述PDN连接对应的网络切片的S-NSSAI相同，且所述终端请求的PDN连接对应的APN与所述PDN连接对应的APN相同的情况下，根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  38. 一种终端，其特征在于，所述终端包括：接收模块和发送模块；
    所述发送模块，用于向第一移动管理实体发送注册请求消息，所述注册请求消息携带所述终端的标识，所述终端的标识用于获取所述终端的签约数据，其中，所述签约数据包括在所述终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；
    所述接收模块，用于接收注册接受消息，所述注册接受消息携带所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述发送模块，还用于发送分组数据单元PDU会话建立请求，所述PDU会话建立请求携带所述PDN连接对应的网络切片的S-NSSAI，所述PDU会话建立请求用于请求在所述PDN连接对应的网络切片中建立PDU会话。
  39. 根据权利要求38所述的终端，其特征在于，所述注册接受消息还携带允许进行切换的PDN连接的信息；所述终端还包括处理模块；
    所述处理模块，用于根据所述允许进行切换的PDN连接的信息，释放所述EPC中除所述允许进行切换的PDN连接之外的其他所有PDN连接。
  40. 一种第二移动管理实体，其特征在于，所述第二移动管理实体包括：收发模块和处理模块；
    所述收发模块，用于接收来自第一移动管理实体的终端接入到分组核心网EPC时已建立的分组数据网络PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述收发模块，还用于向终端发送注册接受消息；
    所述收发模块，还用于接收来自所述终端的分组数据单元PDU会话建立请求，所述PDU会话建立请求用于请求在所述PDN连接对应的网络切片中建立PDU会话；
    所述处理模块，用于根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  41. 一种会话建立系统，其特征在于，所述会话建立系统包括第一移动管理实体和第二移动管理实体；
    所述第一移动管理实体，用于获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息；
    所述第一移动管理实体，还用于根据所述PDN连接的信息，获取所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI后，向所述第二移动管理实体发送所述PDN连接对应的网络切片的S-NSSAI，所述PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片；
    所述第二移动管理实体，用于接收来自所述第一移动管理实体的所述PDN连接对应的网络切片的S-NSSAI；
    所述第二移动管理实体，还用于向终端发送注册接受消息后，接收来自所述终端的分组数据单元PDU会话建立请求，并根据所述PDN连接对应的网络切片的S-NSSAI，在所述PDN连接对应的网络切片中建立PDU会话。
  42. 一种会话建立方法，其特征在于，所述方法包括：
    控制面功能实体获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息以及所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述控制面功能实体向网络存储功能实体发送所述PDN连接的信息以及所述PDN连接对应的网络切片的S-NSSAI，由第一移动管理实体根据所述PDN连接的信息从所述网络存储功能实体中获取所述PDN连接对应的网络切片的S-NSSAI，其中，所述PDN连接对应的网络切片的S-NSSAI用于指示建立分组数据单元PDU会话的网络切片。
  43. 根据权利要求42所述的方法，其特征在于，所述控制面功能实体向网络存储功能实体发送所述PDN连接的信息以及所述PDN连接对应的网络切片的S-NSSAI，包括：
    所述控制面功能实体在所述PDN连接建立的过程中或者在所述PDU会话建立的过程中或者控制面功能实体向网络存储功能实体注册时，向所述网络存储功能实体发送所述PDN连接的信息以及所述PDN连接对应的网络切片的S-NSSAI。
  44. 一种会话建立系统，其特征在于，所述会话建立系统包括：控制面功能实体和第一移动管理实体；
    所述控制面功能实体，用于获取终端接入到分组核心网EPC时已建立的分组数据网络PDN连接的信息以及所述PDN连接对应的网络切片的单网络切片选择辅助信息S-NSSAI；
    所述控制面功能实体，还用于向网络存储功能实体发送所述PDN连接的信息以及所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体，用于向所述网络存储功能实体发送所述PDN连接的信息，所述PDN连接的信息用于确定所述PDN连接对应的网络切片的S-NSSAI；
    所述第一移动管理实体，还用于接收来自所述网络存储功能实体的所述PDN连接对应的网络切片的S-NSSAI。
  45. 一种会话建立方法，其特征在于，所述方法包括：
    网络存储功能实体接收来自第一移动管理实体的分组数据网络PDN连接对应的用户面实体的第一信息；
    所述网络存储功能实体根据所述第一信息，确定所述PDN连接对应的第一网络切片 的单网络切片选择辅助信息S-NSSAI；
    所述网络存储功能实体向所述第一移动管理实体发送所述第一网络切片的S-NSSAI。
  46. 根据权利要求45所述的方法，其特征在于，在所述网络存储功能实体接收来自第一移动管理实体的PDN对应的用户面实体的第一信息之前，所述方法还包括：
    所述网络存储功能实体接收来自所述用户面实体的所述第一信息和与所述第一信息对应的所述第一网络切片的S-NSSAI。
  47. 一种网络存储功能实体，其特征在于，所述网络存储功能实体包括：处理模块和收发模块；
    所述收发模块，用于接收来自第一移动管理实体的分组数据网络PDN对应的用户面实体的第一信息；
    所述网络存储功能实体根据所述第一信息，确定所述PDN连接对应的第一网络切片的单网络切片选择辅助信息S-NSSAI；
    所述网络存储功能实体向所述第一移动管理实体发送所述第一网络切片的S-NSSAI。
  48. 一种会话建立系统，其特征在于，所述会话建立系统包括：第一移动管理实体和网络存储功能实体；
    所述第一移动管理实体，用于向所述网络存储功能实体发送PDN连接对应的用户面实体的第一信息；
    所述网络存储功能实体，用于接收来自所述第一移动管理实体的所述第一信息；
    所述网络存储功能实体，还用于根据所述第一信息，确定所述PDN连接对应的第一网络切片的单网络切片选择辅助信息S-NSSAI；
    所述网络存储功能实体，还用于向所述第一移动管理实体发送所述第一网络切片的S-NSSAI；
    所述第一移动管理实体，还用于接收来自所述网络存储功能实体的所述第一网络切片的S-NSSAI。
  49. 根据权利要求48所述的系统，其特征在于，所述系统还包括用户面实体；
    所述用户面实体，用于向所述网络存储功能实体发送所述第一信息和与所述第一信息对应的所述第一网络切片的S-NSSAI；
    所述网络存储功能实体，用于接收来自所述用户面实体的所述第一信息和与所述第一信息对应的所述第一网络切片的S-NSSAI。
  50. 一种第一移动管理实体，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述第一移动管理实体运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述第一移动管理实体执行如权利要求1-18任一项所述的会话建立方法。
  51. 一种终端，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述终端运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述终端执行如权利要求19-20任一项所述的会话建立方法。
  52. 一种控制面功能实体，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述控制面功能实体运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述控制面功能实体执行如权利要求42-43任一项所述的会话建立方法。
  53. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-18，或19-20，或42-43任一项所述的会话建立方法。
  54. 一种计算机程序产品，其特征在于，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要1-18，或19-20，或42-43任一项所述的会话建立方法。
PCT/CN2018/109971 2017-10-16 2018-10-12 会话建立方法、设备及系统 WO2019076244A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP22165511.1A EP4096303B1 (en) 2017-10-16 2018-10-12 Session establishment method and system
EP18868000.3A EP3694257B1 (en) 2017-10-16 2018-10-12 Method, device, and system for session establishment
KR1020207012625A KR102308350B1 (ko) 2017-10-16 2018-10-12 세션 구축 방법과 시스템, 및 장치
RU2020115877A RU2765987C2 (ru) 2017-10-16 2018-10-12 Система, устройство и способ установки сеанса
JP2020541843A JP7015931B2 (ja) 2017-10-16 2018-10-12 セッション確立方法およびシステム、ならびにデバイス
US16/847,357 US11589270B2 (en) 2017-10-16 2020-04-13 Session establishment method and system, and device
US18/159,275 US12108289B2 (en) 2017-10-16 2023-01-25 Session establishment method and system, and device

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
CN201710963960 2017-10-16
CN201710963960.1 2017-10-16
CN201711208402 2017-11-27
CN201711208402.0 2017-11-27
CN201810491244.2 2018-05-21
CN201810491244 2018-05-21
CN201811169443.8 2018-10-08
CN201811169443.8A CN109673031B (zh) 2017-10-16 2018-10-08 会话建立方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/847,357 Continuation US11589270B2 (en) 2017-10-16 2020-04-13 Session establishment method and system, and device

Publications (1)

Publication Number Publication Date
WO2019076244A1 true WO2019076244A1 (zh) 2019-04-25

Family

ID=66142402

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/109971 WO2019076244A1 (zh) 2017-10-16 2018-10-12 会话建立方法、设备及系统

Country Status (7)

Country Link
US (2) US11589270B2 (zh)
EP (2) EP4096303B1 (zh)
JP (1) JP7015931B2 (zh)
KR (1) KR102308350B1 (zh)
CN (2) CN109673031B (zh)
RU (1) RU2765987C2 (zh)
WO (1) WO2019076244A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3826367A1 (en) * 2019-11-14 2021-05-26 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices in wireless communication system
US20210250852A1 (en) * 2019-06-07 2021-08-12 Verizon Patent And Licensing Inc. Application driven dynamic network slice selection
WO2022014291A3 (en) * 2020-07-17 2022-03-10 Nec Corporation Service continuity across network slices

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3698573B1 (en) * 2017-10-17 2022-06-01 Telefonaktiebolaget LM Ericsson (publ) Pdn and pdu session type mapping and capability discovery
KR102577006B1 (ko) * 2018-08-13 2023-09-11 삼성전자 주식회사 4g 및 5g 네트워크 이동 시 네트워크 슬라이스 지원 방법 및 장치
CN113923647A (zh) * 2019-01-16 2022-01-11 华为技术有限公司 一种小区注册方法及终端设备
CN110167202B (zh) * 2019-04-26 2021-04-20 维沃移动通信有限公司 会话处理方法、装置、终端及介质
CN110381450B (zh) * 2019-07-18 2021-10-22 中国联合网络通信集团有限公司 一种群组建立方法及装置
CN110944365B (zh) * 2019-11-28 2021-10-22 武汉虹旭信息技术有限责任公司 一种基于5g核心网的多参考点关联方法及系统
CN110944367B (zh) * 2019-12-20 2021-12-24 广东工业大学 一种4g与5g互操作的方法
CN111093285A (zh) * 2019-12-27 2020-05-01 中兴通讯股份有限公司 一种会话创建方法、网元及计算机可读存储介质
US20230164652A1 (en) * 2020-02-13 2023-05-25 Telefonaktiebolaget Lm Ericsson (Publ) Re-selection of a pgw-c/smf in the desired network slice
KR20220133963A (ko) * 2020-02-26 2022-10-05 지티이 코포레이션 접근성 및 이동성 관리 기능 재할당을 이용한 등록
CN111698290B (zh) * 2020-05-19 2021-06-15 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质
EP4189930A1 (en) * 2020-08-03 2023-06-07 Nokia Technologies Oy Apparatus, method and computer program
US20230276220A1 (en) * 2020-08-10 2023-08-31 Telefonaktiebolaget Lm Ericsson (Publ) Methods and Apparatuses for Mobility between Different Communication Systems
WO2022077246A1 (en) * 2020-10-14 2022-04-21 Zte Corporation System and methods for identifying edge application server
JP7310036B1 (ja) * 2020-11-06 2023-07-18 サムスン エレクトロニクス カンパニー リミテッド 無線通信システムにおけるネットワークスライスの利用のための通信を実行する方法及び装置
CN113115473B (zh) * 2021-03-01 2022-09-30 深圳艾灵网络有限公司 网络切片控制方法及装置、服务器、系统及存储介质
CN115087053A (zh) * 2021-03-12 2022-09-20 中国移动通信有限公司研究院 会话创建方法、装置及amf
CN115134800B (zh) * 2021-03-24 2024-03-26 中国电信股份有限公司 5g专网接入方法、专网网关、5gc系统以及存储介质
WO2023120752A1 (ko) * 2021-09-02 2023-06-29 주식회사 넷큐브 폐쇄망 서비스를 제공하는 네트워크 슬라이싱 온보딩 시스템 및 그 방법
EP4285647A4 (en) * 2021-10-26 2024-07-03 Samsung Electronics Co Ltd METHOD AND DEVICE FOR SUPPORTING ALTERNATIVE NETWORK SLICE IN WIRELESS COMMUNICATION SYSTEM
WO2023136590A1 (en) * 2022-01-11 2023-07-20 Samsung Electronics Co., Ltd. Enforcing network slice simultaneous registration group (nssrg) in evolved packet system (eps) in a wireless communication system
CN114980276B (zh) * 2022-06-17 2024-09-27 中国电信股份有限公司 专网切片接入方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559868A (zh) * 2015-09-25 2017-04-05 电信科学技术研究院 一种跟踪区更新方法及装置
WO2017062244A1 (en) * 2015-10-06 2017-04-13 Intel IP Corporation Dual radio operation between access systems using 3gpp radio access technology
CN106851589A (zh) * 2016-12-30 2017-06-13 北京小米移动软件有限公司 无线网络接入方法、装置及系统
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8576795B2 (en) * 2007-03-16 2013-11-05 Qualcomm Incorporated Method and apparatus for handoff between source and target access systems
US11265935B2 (en) * 2016-01-18 2022-03-01 Samsung Electronics Co., Ltd. Resource assignment for general packet radio service tunneling protocol (GTP) entities in 5G
WO2017197563A1 (zh) * 2016-05-16 2017-11-23 华为技术有限公司 用于数据传输的方法和装置
US10362511B2 (en) * 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system
EP3563610B1 (en) * 2016-12-30 2020-03-04 Telefonaktiebolaget LM Ericsson (publ) Network slice selection
EP4102889A1 (en) * 2017-01-09 2022-12-14 IDAC Holdings, Inc. Quality of service management for interworking between different communication architectures
US11523319B2 (en) * 2017-01-09 2022-12-06 Lg Electronics Inc. Method for managing PDU session in wireless communication system and device for same
EP3606116B1 (en) * 2017-03-20 2021-12-01 LG Electronics Inc. Method for interaction between layers in wireless communication system and apparatus therefor
WO2018170755A1 (zh) * 2017-03-21 2018-09-27 华为技术有限公司 一种通信方法及设备
CN110050436B (zh) * 2017-03-27 2021-03-02 华为技术有限公司 数据传输方法、用户设备和控制面节点
KR102588974B1 (ko) * 2017-06-19 2023-10-12 아이디에이씨 홀딩스, 인크. 5g 슬라이스 식별자의 프라이버시 보호를 위한 방법 및 시스템
KR102336313B1 (ko) * 2017-06-19 2021-12-07 삼성전자 주식회사 네트워크 가상화 및 세션 관리 방법 및 장치
CN111165014B (zh) * 2017-09-28 2022-06-17 Lg电子株式会社 用于在无线通信系统中发送和接收与从5gs到eps的切换有关的信号的方法及其装置
US20200359291A1 (en) * 2017-10-09 2020-11-12 Telefonaktiebolaget Lm Ericsson (Publ) Methods for establishing connection for packet data transfer of a wireless communication device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559868A (zh) * 2015-09-25 2017-04-05 电信科学技术研究院 一种跟踪区更新方法及装置
WO2017062244A1 (en) * 2015-10-06 2017-04-13 Intel IP Corporation Dual radio operation between access systems using 3gpp radio access technology
CN106851589A (zh) * 2016-12-30 2017-06-13 北京小米移动软件有限公司 无线网络接入方法、装置及系统
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"TS 23.501 - Interworking Between 5GC Slicing Mechanisms and eDecor", SA WG2 MEETING #122BIS, S2-175769, 25 August 2017 (2017-08-25), pages 2 - 3, XP051325617 *
HUAWEI ET AL.: "TS 23.502: Providing S-NSSAI to the RAN and UE During PDU Session Establishment", 3GPP TSG SA WG2 MEETING #120, S2-172068, 31 March 2017 (2017-03-31), pages 3 - 6, XP051257640 *
See also references of EP3694257A4

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210250852A1 (en) * 2019-06-07 2021-08-12 Verizon Patent And Licensing Inc. Application driven dynamic network slice selection
US11943704B2 (en) * 2019-06-07 2024-03-26 Verizon Patent And Licensing Inc. Application driven dynamic network slice selection
EP3826367A1 (en) * 2019-11-14 2021-05-26 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices in wireless communication system
CN114731736A (zh) * 2019-11-14 2022-07-08 三星电子株式会社 用于在无线通信系统中提供网络切片的互通的装置和方法
US11558910B2 (en) 2019-11-14 2023-01-17 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices in wireless communication system
EP4329351A3 (en) * 2019-11-14 2024-06-12 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices subject to nssaa in wireless communication system
US12114380B2 (en) 2019-11-14 2024-10-08 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices in wireless communication system
WO2022014291A3 (en) * 2020-07-17 2022-03-10 Nec Corporation Service continuity across network slices

Also Published As

Publication number Publication date
RU2020115877A3 (zh) 2022-01-10
KR102308350B1 (ko) 2021-10-01
EP3694257B1 (en) 2022-09-28
CN109673031B (zh) 2020-11-17
US20200260340A1 (en) 2020-08-13
EP3694257A1 (en) 2020-08-12
JP7015931B2 (ja) 2022-02-03
EP4096303B1 (en) 2023-11-29
RU2765987C2 (ru) 2022-02-07
KR20200055128A (ko) 2020-05-20
CN112312500A (zh) 2021-02-02
EP4096303A1 (en) 2022-11-30
US20230164644A1 (en) 2023-05-25
EP3694257A4 (en) 2020-12-16
RU2020115877A (ru) 2021-11-18
CN109673031A (zh) 2019-04-23
US12108289B2 (en) 2024-10-01
JP2020537466A (ja) 2020-12-17
US11589270B2 (en) 2023-02-21

Similar Documents

Publication Publication Date Title
WO2019076244A1 (zh) 会话建立方法、设备及系统
US11870856B2 (en) Session establishment method and apparatus
CN108462735B (zh) 一种选择会话管理功能实体的方法和装置
CN110035423B (zh) 会话管理方法、设备及系统
WO2019042182A1 (zh) 数据传输方法、设备及系统
CN109819488A (zh) 一种会话切换方法、设备及系统
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
JP7145197B2 (ja) ハンドオーバ方法、デバイス及びシステム
WO2019137521A1 (zh) 会话管理方法、设备及系统
WO2019096318A1 (zh) 一种会话切换方法、设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18868000

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020541843

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207012625

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018868000

Country of ref document: EP

Effective date: 20200507