WO2019029235A1 - 会话信息管理方法和装置 - Google Patents

会话信息管理方法和装置 Download PDF

Info

Publication number
WO2019029235A1
WO2019029235A1 PCT/CN2018/088903 CN2018088903W WO2019029235A1 WO 2019029235 A1 WO2019029235 A1 WO 2019029235A1 CN 2018088903 W CN2018088903 W CN 2018088903W WO 2019029235 A1 WO2019029235 A1 WO 2019029235A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
information
smf
slice
dnn
Prior art date
Application number
PCT/CN2018/088903
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 EP18844446.7A priority Critical patent/EP3657868A4/en
Publication of WO2019029235A1 publication Critical patent/WO2019029235A1/zh
Priority to US16/787,571 priority patent/US11172521B2/en
Priority to US17/729,667 priority patent/USRE49729E1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a session information management method and apparatus.
  • the network segmentation technology provides a network environment that is isolated from each other in different application scenarios by means of a virtual independent logical network on the same network infrastructure, so that different application scenarios can customize network functions and features according to their respective requirements, thereby ensuring the requirements of different services. .
  • a unified data management (UDM) network element is used to store session context information and subscription data of each user equipment (UE).
  • UE user equipment
  • the UE may access one or more network slices.
  • a UE connected to the same data network (data network, DN) through a plurality of slices of different types of time if the communication system 5G NE reference UDM fourth generation (the 4 th generation, 4G) communication system, a home network
  • the home subscriber server (HSS) manages the subscription data of the UE by the data network name (DNN) granularity.
  • DNN data network name
  • the present application describes a method and apparatus for managing session information.
  • an embodiment of the present application provides a session information management method, where the method includes: a session management function SMF network element sends identity information (eg, SUPI), data network name DNN, and slice of a terminal device to a data management network element. Information to request first subscription data of the terminal device associated with the DNN and the slice information; the SMF network element receives the first subscription data from the data management network element.
  • the slice information is used to identify a network slice of the SMF network element service (for example, S-NSSAI or hS-NSSAI or NSI ID).
  • the SMF network element when the SMF network element requests the data management network element for the subscription data of the terminal device, not only the DNN but also the slice information is provided. In this way, the data management network element can send the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the slice-specific parameter requirements. In addition, the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the method further includes: the SMF network element sends the identification information, the SMF information, the DNN, and the slice information of the terminal device to the data management network element to register the SMF network element in the data management network element.
  • the SMF information includes at least one of identification information of the SMF network element and address information of the SMF network element.
  • the purpose of registering the SMF network element in the data management network element is: when the subscription data in the data management network element is updated, the related SMF network element may be determined according to the slice information and the DNN, and the updated subscription data is notified to the SMF network element. . Therefore, according to the foregoing solution, when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. . Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the SMF network element receiving, from the data management network element, the identification information of the terminal device, the second subscription data, the DNN, and the slice information, which are associated with the DNN and the slice information.
  • the first subscription data is updated to the second subscription data.
  • the method further includes: the SMF network element receives the identification information, the DNN, and the slice information of the terminal device from the data management network element, and deletes the connection between the DNN and the slice information of the terminal device on the SMF network element.
  • the first signing data Therefore, when the UDM determines that the subscription data on the SMF needs to be deleted, the UDM can find the SMF corresponding to the subscription data according to the context information of the terminal device, thereby notifying the SMF to delete the subscription data, and deleting the content in the context information of the terminal device. SMF related information. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the SMF network element transmitting the identification information of the terminal device, the DNN, and the slice information to the data management network element, to delete the SMF information associated with the DNN and the slice information. Therefore, after receiving the DNN and the slice information, the UDM can find the SMF information corresponding to the DNN and the slice information according to the context information of the terminal device, thereby deleting the SMF-related information in the context information of the terminal device. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the present application further discloses a session information management method, including: the SMF network element sends the identification information, the SMF information, the DNN, and the slice information of the terminal device to the data management network element to register the SMF in the data management network element.
  • Network element For example, the SMF information includes at least one of identification information of the SMF network element and address information of the SMF network element.
  • the purpose of registering the SMF network element in the data management network element is: when the subscription data in the data management network element is updated, the related SMF network element may be determined according to the slice information and the DNN, and the updated subscription data is notified to the SMF network element.
  • the UDM when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. . Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the SMF network element receiving, from the data management network element, the identification information of the terminal device, the second subscription data, the DNN, and the slice information, which are associated with the DNN and the slice information.
  • the first subscription data is updated to the second subscription data.
  • the method further includes: the SMF network element receives the identification information, the DNN, and the slice information of the terminal device from the data management network element, and deletes the connection between the DNN and the slice information of the terminal device on the SMF network element.
  • the first signing data Therefore, when the UDM determines that the subscription data on the SMF needs to be deleted, the UDM can find the SMF corresponding to the subscription data according to the context information of the terminal device, thereby notifying the SMF to delete the subscription data, and deleting the content in the context information of the terminal device. SMF related information. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the SMF network element transmitting the identification information of the terminal device, the DNN, and the slice information to the data management network element, to delete the SMF information associated with the DNN and the slice information. Therefore, after receiving the DNN and the slice information, the UDM can find the SMF information corresponding to the DNN and the slice information according to the context information of the terminal device, thereby deleting the SMF-related information in the context information of the terminal device. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the present application further discloses a session information management method, including: the data management network element receives the identification information of the terminal device, the data network name DNN, and the slice information from the session management function SMF network element, to request the terminal device to The first subscription data associated with the DNN and the slice information.
  • the data management network element sends the first subscription data to the SMF network element.
  • the slice information is used to identify a network slice of the SMF network element service (for example, S-NSSAI or hS-NSSAI or NSI ID).
  • the SMF network element when the SMF network element requests the data management network element for the subscription data of the terminal device, not only the DNN but also the slice information is provided. In this way, the data management network element can send the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the slice-specific parameter requirements. In addition, the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the method further includes: the data management network element receiving the identification information, the SMF information, the DNN, and the slice information of the terminal device from the SMF network element, to register the SMF network element in the data management network element.
  • the data management network element stores the SMF information associated with the DNN and the slice information in context information of the terminal device.
  • the SMF information includes at least one of identifier information of the SMF network element and address information of the SMF network element.
  • the purpose of registering the SMF network element in the data management network element is: when the subscription data in the data management network element is updated, the related SMF network element may be determined according to the slice information and the DNN, and the updated subscription data is notified to the SMF network element. . Therefore, according to the foregoing solution, when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. . Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the data management network element updating the first subscription data of the terminal device to the second subscription data, determining the DNN and the slice information associated with the first subscription data, and The SMN network element associated with the DNN and the slice information transmits the identification information of the terminal device, the DNN, the slice information, and the second subscription data.
  • the method further includes: deleting, by the data management network element, the first subscription data on the data management network element, deleting the SMF information in the context information of the terminal device, and transmitting the identification information of the terminal device to the SMF network element. , DNN and slice information. Therefore, when the UDM determines that the subscription data on the SMF needs to be deleted, the UDM can find the SMF corresponding to the subscription data according to the context information of the terminal device, thereby notifying the SMF to delete the subscription data, and deleting the content in the context information of the terminal device. SMF related information. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the data management network element receives the identification information, the DNN, and the slice information of the terminal device from the SMF network element, and deletes, in the context information of the terminal device, the association with the DNN and the slice information. SMF information. Therefore, after receiving the DNN and the slice information, the UDM can find the SMF information corresponding to the DNN and the slice information according to the context information of the terminal device, thereby deleting the SMF-related information in the context information of the terminal device. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the present application further discloses a session information management method, including: the data management network element receives the identification information, the SMF information, the DNN, and the slice information of the terminal device from the SMF network element, to register in the data management network element. SMF network element.
  • the data management network element stores the SMF information associated with the DNN and the slice information in context information of the terminal device.
  • the SMF information includes at least one of identifier information of the SMF network element and address information of the SMF network element.
  • the purpose of registering the SMF network element in the data management network element is: when the subscription data in the data management network element is updated, the related SMF network element may be determined according to the slice information and the DNN, and the updated subscription data is notified to the SMF network element. . Therefore, according to the foregoing solution, when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. . Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the data management network element updating the first subscription data of the terminal device to the second subscription data, determining the DNN and the slice information associated with the first subscription data, and The SMN network element associated with the DNN and the slice information transmits the identification information of the terminal device, the DNN, the slice information, and the second subscription data.
  • the method further includes: deleting, by the data management network element, the first subscription data on the data management network element, deleting the SMF information in the context information of the terminal device, and transmitting the identification information of the terminal device to the SMF network element. , DNN and slice information. Therefore, when the UDM determines that the subscription data on the SMF needs to be deleted, the UDM can find the SMF corresponding to the subscription data according to the context information of the terminal device, thereby notifying the SMF to delete the subscription data, and deleting the content in the context information of the terminal device. SMF related information. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the method further includes: the data management network element receives the identification information, the DNN, and the slice information of the terminal device from the SMF network element, and deletes, in the context information of the terminal device, the association with the DNN and the slice information. SMF information. Therefore, after receiving the DNN and the slice information, the UDM can find the SMF information corresponding to the DNN and the slice information according to the context information of the terminal device, thereby deleting the SMF-related information in the context information of the terminal device. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the slice information is used to identify a network slice accessed by the terminal device, or the slice information is used to identify the SMF network element service within the home public land mobile network HPLMN.
  • the first subscription data includes at least one of the following: an aggregated maximum bit rate AMBR of the subscription; a contracted quality of service QoS profile; a contracted charging feature; a static network protocol IP address or a static IP prefix; session and business continuity SSC mode.
  • the embodiment of the present application provides a session management function network element, where the session management function entity has a function of implementing a session management function network element behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the session management function network element includes a processor and a transceiver configured to process the session management function network element to perform the corresponding function in the above method.
  • the transceiver is configured to implement communication between a session management function network element and an access and mobility management function network element/data management network element.
  • the session management function network element can also include a memory for coupling with the processor that holds program instructions and data necessary for the session management function entity.
  • the embodiment of the present application provides a data management network element, where the data management network element has a function of implementing data management network element behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the data management network element includes a processor and a transceiver configured to process the data management network element to perform the corresponding functions in the above methods.
  • the transceiver is configured to implement communication between a data management network element and a session management function network element.
  • the data management network element can also include a memory for coupling with the processor that holds program instructions and data necessary for the session management function entity.
  • embodiments of the present application provide a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • embodiments of the present application provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the present application provides a chip system, including a processor, configured to support the foregoing session management function network element or data management network element to implement the functions involved in the foregoing aspects, for example, generating or processing the foregoing method.
  • the information involved is involved.
  • the chip system further includes a memory for holding program instructions and data necessary for the data transmitting device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of a communication system in a non-roaming or local breakout (LBO) scenario based on network slice according to an embodiment of the present invention
  • 2A and 2B are signaling interaction diagrams of a session information management method according to an embodiment of the present invention.
  • PDU Packet Data Unit
  • FIG. 4 is a signaling interaction diagram of modifying a PDU session according to an embodiment of the present invention.
  • FIG. 5 is a signaling interaction diagram of releasing a PDU session according to an embodiment of the present invention.
  • FIG. 6 is another signaling interaction diagram of releasing a PDU session according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a communication system in a home-routed roaming scenario based on a network slice according to an embodiment of the present invention.
  • FIG. 8 is a signaling interaction diagram of establishing a PDU session according to an embodiment of the present invention.
  • FIG. 9 is a signaling interaction diagram of modifying a PDU session according to an embodiment of the present invention.
  • FIG. 10 is a signaling interaction diagram of releasing a PDU session according to an embodiment of the present invention.
  • FIG. 11 is another signaling interaction diagram of releasing a PDU session according to an embodiment of the present invention.
  • FIGS. 12A and 12B are schematic diagrams showing the structure of an SMF network element according to an embodiment of the present invention.
  • FIGS. 13A and 13B are schematic diagrams showing the structure of a data management network element according to an embodiment of the present invention.
  • the embodiment of the present application proposes a solution based on the communication system shown in FIG. 1 , which is applicable to management of session information in a next-generation mobile network (eg, 5G network) architecture.
  • a next-generation mobile network eg, 5G network
  • the control plane function and the forwarding plane function of the mobile gateway are decoupled, and the separated control plane functions and the third generation partnership project (3GPP) traditional control network element MME And merge into a unified control plane network element.
  • 3GPP third generation partnership project
  • the user plane UPF network element can implement user plane functions (SGW-U and PGW-U) of a serving gateway (SGW) and a packet data network gateway (PGW).
  • the unified control plane network element can be decomposed into an access and mobility management function (AMF) network element and a session management function (SMF) network element.
  • AMF access and mobility management function
  • SMF session management function
  • the AMF network element may be responsible for the attachment, mobility management, and tracking area update process of the terminal device.
  • the SMF network element can be responsible for session management of the terminal device, selection of user plane devices, reselection of user plane devices, internet protocol (IP) address allocation, quality of service (QoS) control, and session establishment. , modification and release, etc.
  • IP internet protocol
  • QoS quality of service
  • the embodiments of the present application can also be applied to other communication technologies for the future.
  • the system 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.
  • an embodiment of the present application provides a network slice-based communication system.
  • Figure 1 applies to scenarios that are not roaming or LBO.
  • the communication system includes at least a terminal device 102, an access network device 104, and a plurality of network slices, such as network slice 1 and network slice 2.
  • the description is referred to as “slice” of "network slice”.
  • each slice may also be referred to as “slice instance” or “network slice instance”, which is not in the present application. This limit.
  • the terminal device 102 can access one or multiple slices simultaneously.
  • the terminal device 102 simultaneously accesses slice 1 and slice 2.
  • slice 1 is an enhanced mobile broadband (eMBB) type of slice
  • slice 2 is a slice of the Ultra-Reliable and Low-Latency Communication (URLLC) type.
  • eMBB enhanced mobile broadband
  • URLLC Ultra-Reliable and Low-Latency Communication
  • Slice 1 and Slice 2 can share a partial control plane, which can also be called a shared control network function (CCNF).
  • the control plane that the slice 1 and the slice 2 can share includes the AMF network element 106.
  • the session management function is slice-specific, and this part of the control function needs to be instantiated within the slice.
  • the user plane functionality also needs to be instantiated within the slice.
  • the session management function and the user plane function are slice-specific and are used to implement slice-specific services.
  • slice 1 includes SMF network element 108a and user plane network element 210a
  • slice 2 includes SMF network element 108b and user plane network element 210b.
  • the terminal device 102 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.
  • the terminal device may also be referred to as a user equipment (UE), a mobile station (MS), a terminal, and may also include a subscriber unit, a cellular phone, a smart phone.
  • UE user equipment
  • MS mobile station
  • subscriber unit a cellular phone
  • smart phone smart phone
  • wireless data card personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device, laptop computer, cordless phone (cordless) Phone) or wireless local loop (WLL) station, machine type communication (MTC) terminal, and the like.
  • PDA personal digital assistant
  • modem modem
  • handheld device laptop computer
  • cordless phone cordless phone
  • WLL wireless local loop
  • MTC machine type communication
  • the access network device involved in the embodiment of the present application is a device deployed in a wired or wireless access network to provide wireless communication functions for the terminal device 102.
  • the access network device may include various forms 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.
  • 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.
  • the name of a device having a base station function may be different, for example, in an LTE system, an evolved Node B (evolved NodeB, eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • gNB gNodeB
  • the AMF network element involved in the embodiment of the present application may be responsible for attachment, mobility management, tracking area update process, and the like of the terminal device.
  • the AMF network element can also be referred to as an AMF device or an AMF network element.
  • AMF network elements In the example of Figure 1, only one AMF network element is shown. However, the invention does not limit the number of AMF network elements. Different AMF network elements can be connected to different slices or to the same slice. AMF network elements can also be referred to as AMF devices or AMF entities. For convenience of description, the following will be simply referred to as "AMF".
  • slice 1 and slice 2 respectively comprise an SMF network element: SMF network elements 108a and 108b.
  • the SMF network element involved in the embodiment of the present application may be responsible for session management of the terminal device, selection of the user plane network element, reselection of the user plane network element, IP address allocation, QoS control, and establishment, modification, and release of the session.
  • the SMF network element may also be referred to as an SMF device or an SMF entity. For convenience of description, the following will be simply referred to as "SMF".
  • slice 1 and slice 2 respectively include one UPF network element: UPF network element 210a and UPF network element 210b.
  • the UPF network element 210a and the UPF network element 210b may be connected to the same or different data networks (DNs) for implementing data transmission of services.
  • a UPF network element may also be referred to as a UPF device or a UPF entity.
  • the communication system also includes a data management device 112.
  • the data management network element is configured to store subscription data of the user, for example, subscription data related to mobility management and subscription data related to session management.
  • the data management network element is a unified data management (UDM) network element.
  • UDM unified data management
  • a UDM network element may also be referred to as a UDM device or a UDM entity. For convenience of description, the following will be simply referred to as "UDM”.
  • the terminal device 102 can access one or multiple slices simultaneously. Each slice can provide different services. In addition, operators can also lay out multiple slices to provide the same service for different groups of users. Different slices can be connected to the same DN.
  • the type of slice can be identified by Single Network Slice Selection Assistance information (S-NSSAI).
  • S-NSSAI is a collection of S-NSSAI. Each S-NSSAI is used by the secondary network to select a particular network slice instance. It is also possible to select the same network slice instance through different S-NSSAI.
  • the slice information for identifying a slice may be at least one of identification information of a slice and type information of a slice, or may be other information that can identify a slice.
  • the identification information of the slice is a network slice instance ID (NSI ID).
  • the type information of the slice includes the above S-NSSAI.
  • S-NSSAI includes Slice/Service Type (SST).
  • SST refers to the performance of the desired network slice in features and services.
  • standardized SSTs include: eMBB, URLLC, or massive internet of things (MIoT).
  • the S-NSSAI further includes a Slice Differentiator (SD).
  • SD Slice Differentiator
  • SD is an optional message that is used to supplement SST to distinguish multiple network slices of the same SST type.
  • the slice information used to identify the slice type may be an SST in the S-NSSAI.
  • the slice information is a combination of SST and SD.
  • the following embodiment describes the slice information as S-NSSAI as an example, however, the present invention is not limited thereto.
  • the invention discloses a session information management method.
  • the session information includes subscription data and session context information of the UE.
  • 2A and 2B depict the present invention from the perspective of subscription data and the session context of the UE, respectively.
  • FIG. 2A illustrates a session information management method according to an embodiment of the present invention.
  • the method may be performed interactively by an SMF network element (e.g., SMF network element 108a or 108b in FIG. 1) and a data management network element (e.g., data management network element 112 in FIG. 1).
  • SMF network element e.g., SMF network element 108a or 108b in FIG. 1
  • data management network element e.g., data management network element 112 in FIG.
  • the method includes:
  • Step 201 The SMF network element sends the identifier information, the DNN, and the slice information of the terminal device to the data management network element to request the first subscription data of the terminal device associated with the DNN and the slice information.
  • the data management network element receives the identification information, the DNN and the slice information of the terminal device from the SMF network element.
  • the slice information is used to identify a network slice of the SMF network element service.
  • the slice of the SMF network element service is the slice accessed by the terminal device.
  • the identification information of the terminal device is a permanent identifier of the terminal device, for example, a subscriber permanent ID (SUPI).
  • SUPI subscriber permanent ID
  • the SMF network element can request the UE to subscribe to the data by calling the network function (NF) service of the UDM.
  • the service requesting the subscription data may be Nudm_Subscriber_Data_Get.
  • the service can be invoked by sending a Nudm_Subscriber_Data_GetRequest.
  • Nudm_Subscriber_Data_GetRequest includes identification information, DNN, and slice information of the terminal device.
  • the input to invoke the service includes identification information of the terminal device, DNN, and slice information.
  • the SMF may request the terminal device's subscription data associated with the DNN and the slice information by transmitting to the UDM other identification messages carrying the identification information of the terminal device, the DNN, and the slice information.
  • the data management network element may search for the first subscription data associated with the DNN and the slice information in the subscription data of the terminal device.
  • the first subscription data includes at least one of the following: an aggregate maximum bit rate (AMBR); a contracted QoS profile; a contracted charging feature; a static IP address or a static IP prefix; a session and a service Session and service cont inuity (SSC) mode.
  • the AMBR may be an AMBR of different granularity, for example, an AMBR of a UE granularity, an AMBR of a session granularity, an AMBR of a DNN granularity, an AMBR of a slice granularity, or an AMBR of a DNN and a slice granularity, and the present invention is not limited thereto.
  • the static IP address or static IP prefix remains unchanged relative to dynamically assigning an IP address or IP prefix in the prior art.
  • the data management network element stores the subscription data of the terminal device in the form of Table 1 below.
  • the data management network element stores subscription data associated with slice 1 (for example, corresponding S-NSSAI 1) and DNN1: subscribed AMBR 1, contracted QoS file 1, signed charging feature 1, static IP address 1; subscription data associated with slice 2 (eg, corresponding S-NSSAI 2) and DNN1: contracted AMBR 2, contracted QoS file 2, contracted charging feature 2, static IP address 2; 1 Signing data associated with DDN2: contracted AMBR 3, contracted QoS file 3, contracted charging feature 3, static IP address 3.
  • the DNN received by the data management network element is DNN1, and the received slice information is S-NSSAI1 corresponding to slice 1, then the first subscription data associated with DNN1 and slice 1 includes at least the signed AMBR 1, the signed QoS file.
  • Signed Charging Features 1. At least one of the static IP addresses 1.
  • Step 202 The data management network element sends the found first subscription data associated with the DNN and the slice information to the SMF network element.
  • the SMF network element receives the first subscription data from the data management network element.
  • the SMF network element when the SMF network element requests the data management network element for the subscription data of the terminal device, not only the DNN but also the slice information is provided.
  • the data management network element can send the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the slice-specific parameter requirements.
  • the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the terminal device may be a car within the car network, may establish PDU session 1 and DN interaction control information on a URLLC slice (eg, slice 1), while establishing a PDU session 2 and DN on an eMBB slice (eg, slice 2) Transmit data streams (such as uploading a surveillance video stream in the cab to a DN or dynamically downloading traffic data from a DN).
  • the terminal device may connect to the same DN through two slices (for example, corresponding to DNN1).
  • the signed AMBR of the PDU session on the two slices, the contracted QoS profile, the contracted charging feature, the static IP address, and the SSC mode may all differ greatly.
  • the data management network element needs to manage these subscription data at the granularity of the slice. If the SMF network element 108a of the slice 1 transmits the slice information of the DNN1 and the slice 1 to the data management network element to request the subscription data, the data management network element transmits the subscription data corresponding to the slice 1 to the SMF network element 108 instead of The subscription data corresponding to the slice 2 is also sent to the SMF network element 108, thereby satisfying the principle that the slice specific parameter requirements and the slices are isolated from each other, and the waste of signaling and resources is also avoided.
  • FIG. 2B illustrates a method for managing session information according to an embodiment of the present invention, including:
  • step 211 the SMF network element acquires DNN and slice information.
  • Step 212 The SMF network element sends the identifier information, the SMF information, the DNN, and the slice information of the terminal device to the data management network element, to register the SMF network element in the data management network element.
  • the data management network element receives the identification information, the SMF information, the data network name DNN and the slice information of the terminal device from the SMF network element.
  • the identification information and the slice information of the terminal device can be referred to the description in FIG. 2A.
  • the SMF information includes at least one of identification information (SMF ID) of the SMF network element and address information (SMF address) of the SMF network element.
  • the SMF network element can register the SMF network element by calling the NF service of the UDM.
  • the service requesting registration of the SMF network element may be Nudm_UEContextManagement_Registration.
  • the service can be invoked by sending a Nudm_UEContextManagement_RegistrationRequest.
  • the Nudm_UEContextManagement_RegistrationRequest includes identification information of the terminal device, SMF information, DNN, and the above slice information.
  • the input to invoke the service includes identification information of the terminal device, SMF information, DNN, and the above-described slice information.
  • the SMF may register the SMF in the UDM by transmitting to the UDM the identification information carrying the terminal device, the SMF information, the DNN, and other request messages of the above-described slice information.
  • Step 213 The data management network element stores the SMF information associated with the DNN and the slice information in the context information of the terminal device.
  • the context information of the terminal device may have the format of Table 2.
  • SMF ID 1 Slice information 1 DNN 1
  • SMF ID 2 Slice information 2 DNN 1
  • Table 2 takes the SMF information as an example of the SMF ID. However, it is also possible to replace the SMF ID with the SMF address, or both the SMF ID and the SMF address. As shown in Table 2 above, the dimension of the slice information is added to the context information of the terminal to distinguish the SMF network elements corresponding to different slices connected to the same DN.
  • steps may be used to register an SMF network element in the data management network element. These steps may constitute a separate embodiment or, alternatively, may be performed after the steps of Figure 2A are completed. If these steps are performed after the steps of FIG. 2A are completed, step 211 can be skipped. Alternatively, the above steps can also be performed simultaneously with the steps in FIG. 2A. For example, if in step 201 of FIG. 2A, the SMF also provides SMF information to the data management network element, the data management network element may register the SMF network element while providing subscription data to the SMF network element.
  • the purpose of registering the SMF network element in the data management network element is: when the subscription data in the data management network element is updated, the related SMF network element may be determined according to the slice information and the DNN, and the updated subscription data is notified to the SMF network element. . Therefore, according to the solution of the embodiment of the present invention, when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the DNN and the slice according to the session context information of the UE. SMF network element. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the foregoing two schemes of FIG. 2A and FIG. 2B may further include the following steps:
  • the subscription data can be updated.
  • the data management network element updates the first subscription data of the terminal device to the second subscription data, determines the DNN and the slice information associated with the first subscription data, and sends the information to the SMF network element associated with the DNN and the slice information. Identification information of the terminal device, the DNN, the slice information, and the second subscription data.
  • the SMF network element receives the identification information of the terminal device, the second subscription data, the DNN, and the slice information from the data management network element, and updates the first subscription data associated with the DNN and the slice information. For the second subscription data.
  • the release process of the PDU session can be triggered by the data management network element.
  • the data management network element sends the identification information of the terminal device, the DNN, and the slice information to the SMF network element.
  • the SMF network element receives the identification information of the terminal device, the DNN and the slice information from the data management network element, and deletes, by the terminal device on the SMF network element, the DNN and the slice information.
  • the first signing data is the identification information of the terminal device, the DNN and the slice information from the data management network element.
  • the data management network element deletes the first subscription data on the data management network element; and deletes the SMF information in the context information of the terminal device.
  • the SMF information on the data management network element can be deleted by the SMF network element.
  • the SMF network element sends the identification information of the terminal device, the DNN, and the slice information to the data management network element to delete the SMF information associated with the DNN and the slice information.
  • the data management network element receives the identification information of the terminal device, the DNN and the slice information from the SMF network element, and deletes the DNN and the slice information in the context information of the terminal device. The associated SMF information.
  • the method of Figure 3 can be applied to the process of establishing a PDU session. As shown in FIG. 3, the method includes:
  • Step 301 The terminal device initiates a PDU session establishment process. For example, the terminal device sends a non-access stratum (NAS) message to the AMF, the NAS message including session management (SM) information (eg, N1SM information), S-NSSAI, and DNN.
  • NAS non-access stratum
  • SM session management
  • N1SM information e.g., N1SM information
  • S-NSSAI S-NSSAI
  • DNN DNN.
  • the session management information carries a PDU session establishment request.
  • step 302 the AMF selects the SMF according to the S-NSSAI.
  • step 303 the AMF sends the DNN and the S-NSSAI to the SMF to notify the SMF to establish a session.
  • the AMF can notify the SMF to establish a session by invoking an NF service (eg, Nsmf_PDUSession_CreateSM) of the SMF for establishing a PDU session.
  • the service can be invoked by sending a request message (eg, Nsmf_PDUSession_CreateSMRequest).
  • Nsmf_PDUSession_CreateSMRequest includes DNN and S-NSSAI.
  • the input to invoke the service includes DNN and S-NSSAI.
  • the AMF may notify the SMF to establish a session by sending other request messages carrying DNN and S-NSSAI to the SMF.
  • Step 304 After receiving the DNN and the S-NSSAI, the SMF sends the identification information, the DNN, and the slice information of the terminal device to the UDM to request the subscription data associated with the DNN and the slice information.
  • the SMF can request the UE to subscribe to the data by calling the service of Nudm_Subscriber_Data_Get.
  • the service can be called by sending Nudm_Subscriber_Data_GetRequest.
  • Nudm_Subscriber_Data_GetRequest includes identification information, DNN, and slice information of the terminal device.
  • the input to invoke the service includes identification information of the terminal device, DNN, and slice information.
  • the input may further include: SMF information (at least one of an SMF ID or an SMF address), the requested subscription data type.
  • the requested subscription data type is SM subscription data.
  • the SMF may request subscription data associated with the DNN and the slice information by transmitting to the UDM other identification messages carrying the identification information of the terminal device, the DNN, and the slice information.
  • Step 305 After receiving the identification information, the DNN, and the slice information of the terminal device, the UDM determines, in the subscription of the terminal device, the subscription data associated with the DNN and the slice information according to the DNN and the slice information.
  • the subscription data of the terminal device stored in the UDM may have the format of Table 1 above.
  • the UDM sends the subscription data associated with the DNN and the slice information to the SMF.
  • the UDM may send a response message to the SMF carrying the UE subscription data associated with the DNN and the slice information.
  • the response message may be a response message Nudm_SubscriberData_GetResponse of the Nudm_Subscriber_Data_Get service.
  • the response message further carries the foregoing slice information and the DNN.
  • steps 304 to 306 can refer to the description of FIG. 2A.
  • Step 307 multi-side interaction, to achieve authentication, authorization, and user plane establishment.
  • Step 308 optionally, if the input in step 304 does not include SMF information, the SMF sends the identification information of the terminal device, the SMF information, the DNN, and the above slice information to the UDM to register the SMF in the UDM.
  • the SMF can register the SMF by calling the service of Nudm_UEContextManagement_Registration.
  • the service can be called by sending a Nudm_UEContextManagement_RegistrationRequest.
  • the Nudm_UEContextManagement_RegistrationRequest includes identification information of the terminal device, SMF information, DNN, and the above slice information.
  • the input to invoke the service includes identification information of the terminal device, SMF information, DNN, and the above-described slice information.
  • the SMF may register the SMF in the UDM by transmitting to the UDM the identification information carrying the terminal device, the SMF information, the DNN, and other request messages of the above-described slice information.
  • the UDM saves the SMF information associated with the DNN and the slice information in the UE context.
  • the UE context may have the format of Table 2 above.
  • steps 308 to 309 can refer to the description of FIG. 2B.
  • step 310 the UDM returns a response message to the SMF.
  • the response message carries the DNN and the slice information.
  • the data management network element may send the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the specific parameter requirement of the slice.
  • the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • steps 304 to 306 may correspond to the interaction process of the NF service to the UDM by the SMF under the service architecture: Nudm_Subscriber_Data_Get.
  • steps 308 to 310 may correspond to an interaction process flow in which the SMF calls the NF service to the UDM in the service architecture: Nudm_UEContextManagement_Registration.
  • the method of Figure 4 can be adapted to modify the flow of a PDU session. As shown in FIG. 4, the method includes:
  • Step 401 When the UDM updates the subscription data, the UDM selects an SMF associated with the DNN and the slice information according to the saved context information of the terminal device.
  • the subscription data saved in the UDM can be configured or maintained by the network management device.
  • the UDM updates the subscription data.
  • the UDM determines the DNN and the slice information associated with the first subscription data, and further determines the SMF network element associated with the DNN and the slice information.
  • the UDM determines the slice information 1 and DNN1 of the slice 1 associated with the subscribed AMBR 1, and then according to the context of, for example, Table 2. Information, select the SMF associated with the DNN1 and slice information 1 (with SMF ID1).
  • Step 402 The UDM sends the DNN and the slice information to the SMF to update the subscription data of the terminal device associated with the DNN and the slice information.
  • the UDM may update the UE subscription data associated with the DNN and the slice information by calling the service of Nudm_Subscriber_Data_UpdateNotification.
  • the service can be invoked by sending Nudm_Subscriber_Data_UpdateNotification Notify.
  • Nudm_Subscriber_Data_UpdateNotification Notify includes identification information of the terminal device, DNN and slice information, and subscription data (such as the second subscription data described above).
  • the input to invoke the service includes identification information of the terminal device, DNN, slice information, and subscription data (such as the second subscription data described above).
  • the UDM may update the subscription data associated with the DNN and the slice information of the terminal device by transmitting to the SMF the identification information carrying the terminal device, the DNN and the slice information and other notification messages of the subscription data.
  • Step 403 The SMF updates the UE subscription data associated with the DNN and the slice information according to the input information.
  • the input includes identification information of the terminal device, DNN1, slice information 1 of slice 1, and Subscribed-session-AMBR 4.
  • the SMF updates the Subscribed-session-AMBR 1 associated with DNN1 and Slice 1 to the subscribed-session-AMBR 4.
  • Step 404 after the subscription data is updated, the SMF returns an acknowledgement message (acknowledge, ACK) carrying the identification information of the terminal device to the UDM.
  • acknowledgement message acknowledge, ACK
  • the output after calling the service includes the identification information of the terminal device.
  • step 404 the subsequent steps of the session modification process may be performed with reference to the prior art.
  • the UDM when the subscription data in the UDM network element is updated, if the updated subscription data only involves a certain slice, the UDM can only notify the SNN corresponding to the DNN and the slice according to the session context information of the UE. Network element. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • steps 402 to 404 may correspond to the interaction process of the NF service to the SMF by the UDM under the service architecture: Nudm_Subscriber_Data_UpdateNotification.
  • the method of FIG. 5 is applicable to a process of releasing a PDU session, and is applicable to a release process of triggering a PDU session by a UDM. As shown in FIG. 5, the method includes:
  • step 501 the UDM determines that the subscription data on the SMF needs to be deleted.
  • the UDM determines the DNN and the slice information associated with the subscription data that needs to be deleted, and then determines the SMF associated with the DNN and the slice information based on the context information of the terminal device.
  • Step 502 The UDM sends the identifier information, the DNN, and the slice information of the terminal device to the SMF, so as to delete the first subscription data of the terminal device on the SMF that is associated with the DNN and the slice information.
  • the UDM can delete the subscription data on the SMF by calling the service of Nudm_UE Context Management_RemoveNotification.
  • the service may be invoked by sending a Nudm_Subscriber_Data_UpdateNotification Notify carrying the identification information of the terminal device, the DNN and the slice information, or the Nudm_Subscriber_Data_UpdateNotification Request carrying the identification information of the terminal device, the DNN and the slice information.
  • the input to invoke the service includes identification information of the terminal device, DNN, and slice information.
  • the UDM may delete the subscription data on the SMF by sending to the SMF other notification messages or request messages carrying the identification information of the terminal device, the DNN, and the slice information.
  • Step 503 The SMF deletes the first subscription data associated with the DNN and the slice information of the terminal device on the SMF.
  • step 504 the SMF returns a response message or a confirmation message.
  • the UDM may delete the first subscription data on the UDM and the SMF information in the context information while deleting the subscription data on the SMF in step 501.
  • the UDM may delete the first subscription data on the UDM first, thereby causing the SMF information in the context information to be deleted.
  • the UDM may also delete the first subscription data and the SMF information in the context information on the UDM by receiving the response message or the confirmation message of step 504. If the first subscription data on the UDM and the SMF information in the context information have been deleted before step 504, steps 505 and 506 may be skipped. Alternatively, steps 505 and 506 can also be performed after the session release process is completed.
  • Step 505 The UDM deletes the first subscription data on the UDM and the SMF information in the context information.
  • step 506 the UDM sends a Result indication to the SMF.
  • Step 507 the SMF decides to trigger the PDU session release process, and performs the subsequent steps of the session release process with reference to the prior art.
  • the UDM when the UDM determines that the subscription data on the SMF needs to be deleted, the UDM may find the SMF corresponding to the subscription data according to the context information of the terminal device, thereby notifying the SMF to delete the subscription data, and at the terminal device.
  • the SMF related information is deleted from the context information.
  • steps 502 to 504 may correspond to the interaction process of the NF service to the SMF by the UDM under the service architecture: Nudm_UE Context Management_RemoveNotification.
  • the method of FIG. 6 is applicable to the process of releasing a PDU session, and is suitable for triggering deletion of SMF information on the UDM by the SMF. As shown in FIG. 6, the method includes:
  • step 601 the SMF decides to release the PDU session.
  • the SMF decides to trigger the PDU session release process.
  • the SMF decides to release the PDU session based on the request from the UDM, the request of the DN, or the locally configured policy.
  • Step 602 refer to the prior art to perform a subsequent process of releasing the PDU session.
  • Step 603 when the SMF determines that the last PDU session of the serving slice and the terminal device on the DN has been released, transmitting the identification information of the terminal device, the DNN and the slice information to the UDM to delete the DNN and the slice.
  • the SMF information associated with the information.
  • the SMF may delete the SMF information associated with the DNN and the slice information by calling a service of the Nudm_UE Context Management_Purge.
  • the service may be invoked by sending a Nudm_UE Context Management_Purge Notify carrying the identification information of the terminal device, the DNN and the slice information, or the Nudm_UE Context Management_Purge Request carrying the identification information of the terminal device, the DNN and the slice information.
  • the input to invoke the service includes identification information of the terminal device, DNN, and slice information.
  • the UDM may delete the SMF information associated with the DNN and the slice information by transmitting to the SMF other notification messages or request messages carrying identification information of the terminal device, DNN, and slice information.
  • Step 604 The UDM deletes the SMF information associated with the slice information and the DNN in the context information of the terminal device.
  • step 605 the UDM sends a result indication to the SMF.
  • the UDM may find the SMF information corresponding to the DNN and the slice information according to the context information of the terminal device, thereby deleting the SMF-related information in the context information of the terminal device. .
  • the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • steps 603 to 605 may correspond to the interaction process of the NF service to the UDM by the SMF under the service architecture: Nudm_UEContextManagement_Purge.
  • FIG. 7 is a schematic structural diagram of a home route roaming scenario to which the present invention is applicable.
  • the terminal device accesses the slice V in the VPLMN through the access network device in the VPLMN.
  • Slice V includes V-SMF and V-UPF.
  • the H-SMF within the HPLMN is connected to the UDM.
  • the terminal device is connected to the DN through V-UPF and H-UPF.
  • H-SMF and H-UPF constitute a slice H within the HPLMN.
  • the method described in Figures 3 through 6 above is performed by the H-SMF and UDM interaction within the HPLMN.
  • the slice information is specifically used to identify a slice within the HPLMN, for example, hS-NSSAI, which may also be referred to as H-slice information.
  • FIG. 8 is a signaling interaction diagram of establishing a PDU session in a home routing roaming scenario.
  • Step 801 The terminal device sends a NAS message to the AMF, where the NSA message includes the SM information, the vS-NSSAI, and the DNN.
  • the session management information carries a PDU session establishment request.
  • vS-NSSAI is used to identify the type of slice in the VPLMN.
  • step 802 the AMF selects the V-SMF according to the vS-NSSAI and maps the vS-NSSAI to the hS-NSSAI.
  • step 803 the AMF sends the DNN and the vS-NSSAI to the V-SMF to notify the V-SMF to establish a session.
  • the AMF may notify the V-SMF to establish a session by invoking an NF service (eg, Nsmf_PDUSession_CreateSM) of the SMF for establishing a PDU session.
  • an NF service eg, Nsmf_PDUSession_CreateSM
  • the inputs that call the service include DNN and h-NSSAI.
  • step 804 the V-SMF notifies the H-SMF to establish a session by calling the service of the Nsmf_PDUSession_CreateSM.
  • the V-SMF passes the DNN and h-NSSAI to the H-SMF.
  • Step 805 After receiving the DNN and the hS-NSSAI, the H-SMF sends the identification information, the DNN, and the slice information of the terminal device to the UDM to request the subscription data associated with the DNN and the slice information.
  • Step 806 After receiving the identification information, the DNN, and the slice information of the terminal device, the UDM determines, in the subscription of the terminal device, the subscription data associated with the DNN and the slice information according to the DNN and the slice information.
  • Step 807 The UDM sends the subscription data associated with the DNN and the slice information to the H-SMF.
  • step 808 multi-side interaction is performed to implement authentication, authorization, and establishment of a user plane.
  • Step 809 optionally, if the input in step 805 does not include H-SMF information, the H-SMF sends the identification information of the terminal device, the SMF information of the H-SMF, the DNN, and the above slice information to the UDM to The H-SMF is registered in the UDM.
  • the UDM saves the SMF information associated with the DNN and the slice information in the UE context.
  • step 811 the UDM returns a response message to the H-SMF.
  • steps 805 to 811 can refer to the description of steps 304 to 310 in FIG.
  • the interaction between the H-SMF and the UDM in Figure 8 is consistent with the interaction between the SMF and the UDM in Figure 3.
  • FIG. 9 is a signaling interaction diagram of modifying a PDU session in a home routing roaming scenario.
  • the steps 901 to 904 can refer to the description of steps 401 to 404 in FIG. 4 .
  • the interaction between the H-SMF and the UDM in Figure 9 is consistent with the interaction between the SMF and the UDM in Figure 4.
  • the method also includes:
  • the H-SMF sends DNN and H-slice information to the V-SMF.
  • the H-SMF invokes the Nsmf_PDU Session_UpdateNotification service to update the subscription data on the specified slice within the VPLMN.
  • the input to invoke the service includes DNN and H-slice information.
  • step 905 After the execution of step 905 is completed, the subsequent steps of the session modification process may be performed with reference to the prior art.
  • FIG. 10 is a signaling interaction diagram of releasing a PDU session in a home routing roaming scenario.
  • steps 1001 to 1007 can refer to the description of steps 501 to 507 in FIG. 5.
  • the interaction between the H-SMF and the UDM in Figure 10 is consistent with the interaction between the SMF and the UDM in Figure 5.
  • the method also includes:
  • the H-SMF sends DNN and H-slice information to the V-SMF.
  • the H-SMF invokes the Nsmf_PDU Session_Release service to delete the subscription data on the V-SMF.
  • the input to invoke the service includes DNN and H-slice information.
  • step 1008 the subsequent steps of the session release process may be performed with reference to the prior art.
  • FIG. 11 is a signaling interaction diagram of releasing a PDU session in a home routing roaming scenario.
  • the steps 1101 to 1105 can refer to the description of steps 601 to 605 in FIG. 6.
  • the interaction between the H-SMF and the UDM in Figure 11 is consistent with the interaction between the SMF and the UDM in Figure 6. The difference is that some of the steps in the session release process in step 1102 involve network elements within the VPLMN.
  • each network element such as the above-mentioned session management function network element or data management network element, etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function.
  • 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 session management function network element may include a receiving module 1201, a processing module 1202, and a sending module 1203, as shown in FIG. 12A.
  • the session management function network element can be used to perform the operations of the SMF or H-SMF in Figures 2 through 11 above.
  • the sending module 1203 is configured to send the identifier information of the terminal device, the data network name DNN, and the slice information to the data management network element, to request the first end of the terminal device that is associated with the DNN and the slice information.
  • a subscription data wherein the slice information is used to identify a network slice of the SMF network element service.
  • the receiving module 1201 is configured to receive the first subscription data from the data management network element.
  • the data management network element can transmit the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the slice-specific parameter requirements.
  • the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the sending module 1203 is further configured to send the identifier information, the SMF information, the DNN, and the slice information of the terminal device to the data management network element, to register the data in the data management network element.
  • the SMF network element, the SMF information includes at least one of identifier information of the SMF network element and address information of the SMF network element.
  • the receiving module 1201 is configured to obtain a data network name DNN and slice information, where the slice information is used to identify a network slice of the SMF network element service.
  • the sending module is configured to send the identifier information, the SMF information, the DNN, and the slice information of the terminal device to the data management network element, to register the SMF network element in the data management network element, where
  • the SMF information includes at least one of identification information of the SMF network element and address information of the SMF network element.
  • the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the receiving module 1201 is further configured to receive, by the data management network element, identifier information, second subscription data, the DNN, and the slice information of the terminal device.
  • the processing module 1202 is configured to update the first subscription data associated with the DNN and the slice information to the second subscription data.
  • the receiving module 1201 is further configured to receive the identifier information of the terminal device, the DNN, and the slice information from the data management network element.
  • the processing module 1202 is configured to delete the first subscription data associated with the DNN and the slice information of the terminal device on the SMF network element.
  • the sending module 1203 is further configured to send the identifier information of the terminal device, the DNN, and the slice information to the data management network element, to delete the association associated with the DNN and the slice information. SMF information.
  • the receiving module 1201, the processing module 1202, and the sending module 1203 in the session management function network element may also implement other operations or functions of the SMF or the H-SMF in the foregoing method, and details are not described herein again.
  • FIG. 12B is a schematic diagram showing another possible structure of the session management function network element involved in the foregoing embodiment.
  • the session management function network element includes a transceiver 1204 and a processor 1205, as shown in Figure 12B.
  • the processor 1205 is configured to process the session management function network element to perform the corresponding functions of the SMF or H-SMF in the above method.
  • the transceiver 1204 is configured to implement communication between the SMF or H-SMF and the access and mobility management function network element/data management network element.
  • the session management function network element can also include a memory 1206 for coupling with a processor that stores program instructions and data necessary for the session management function network element.
  • the data management network element may include a receiving module 1301, a processing module 1302, and a transmitting module 1303, as shown in FIG. 13A.
  • the policy control function device can be used to perform the operations of the data management network element (e.g., UDM device 112) of Figures 2 through 11 above.
  • UDM device 112 e.g., UDM device 112
  • the receiving module 1301 is configured to receive the identification information of the terminal device, the data network name DNN, and the slice information from the session management function SMF network element, to request that the terminal device is associated with the DNN and the slice information.
  • the first subscription data wherein the slice information is used to identify a network slice of the SMF network element service.
  • the sending module 1303 is configured to send the first subscription data to the SMF network element.
  • the data management network element can transmit the first subscription data associated with the DNN and the slice information to the requested SMF, thereby satisfying the slice-specific parameter requirements.
  • the data management network element does not need to send the subscription data associated with other slices to the SMF, which conforms to the principle of isolation between slices, and also avoids waste of signaling and resources.
  • the receiving unit 1301 is further configured to receive the identifier information, the SMF information, the DNN, and the slice information of the terminal device from the SMF network element, to register the SMF in the data management network element.
  • a network element where the SMF information includes at least one of identifier information of the SMF network element and address information of the SMF network element.
  • the processing module 1302 is configured to store, in the context information of the terminal device, the SMF information associated with the DNN and the slice information.
  • the receiving unit 1301 is configured to receive, by the session management function SMF network element, the identification information of the terminal device, the SMF information, the data network name DNN, and the slice information, to register the SMF in the data management network element.
  • a network element where the SMF information includes at least one of identifier information of the SMF network element and address information of the SMF network element.
  • the processing module 1302 is configured to store, in the context information of the terminal device, the SMF information associated with the DNN and the slice information.
  • the UDM can only notify the SMN network element corresponding to the DNN and the slice according to the session context information of the UE. Thereby, the principle of isolation between slices is satisfied, and waste of signaling and resources is avoided.
  • the receiving module 1301 is further configured to receive, by the data management network element, identifier information, second subscription data, the DNN, and the slice information of the terminal device.
  • the processing module 1302 is configured to update the first subscription data associated with the DNN and the slice information to the second subscription data.
  • the receiving module 1301 is further configured to receive the identifier information of the terminal device, the DNN, and the slice information from the data management network element.
  • the processing module 1302 is configured to delete the first subscription data associated with the DNN and the slice information of the terminal device on the SMF network element.
  • the sending module 1303 is further configured to send the identifier information of the terminal device, the DNN, and the slice information to the data management network element, to delete the association associated with the DNN and the slice information. SMF information.
  • receiving module 1301, the processing module 1302, and the sending module 1303 in the data management network element may further implement other operations or functions of the UDM network element 112 in the foregoing method, and details are not described herein again.
  • FIG. 13B is a schematic diagram showing another possible structure of the data management network element involved in the foregoing embodiment.
  • the data management network element includes a transceiver 1304 and a processor 1305, as shown in Figure 13B.
  • the processor 1305 is configured to process the data management network element to perform the functions of the UDM in the above method.
  • the transceiver 1304 is used to implement communication between the UDM and the SMF or H-SMF.
  • the data management network element can also include a memory 1306 for coupling with the processor that holds the program instructions and data necessary for the data management network element.
  • FIGS 12B, 13B only show a simplified design of the above apparatus.
  • each of the above devices may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are within the scope of the present application.
  • the controller/processor for performing the foregoing session management function network element of the present application may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate. Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a session management function network element.
  • the processor and the storage medium may also exist as discrete components in the session management function network element.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • 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 invention 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 Transfer to another website site, computer, server, or data center by wire (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 such as a server, data center, or the like that includes one or more available 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)).

Abstract

本申请涉及无线通信技术领域，提供了一种会话信息管理方法，包括：SMF网元向数据管理网元发送终端设备的标识信息、DNN和切片信息，以请求终端设备的与该DNN和切片信息关联的第一签约数据，其中，切片信息用于标识SMF网元服务的网络切片。SMF网元从数据管理网元接收上述第一签约数据。通过本实施例提供的方案，可以满足各个切片不同的需求以及切片之间的隔离。

Description

会话信息管理方法和装置 技术领域
本申请涉及无线通信技术领域，尤其涉及一种会话信息管理方法和装置。
背景技术
第五代(the 5 th generation，5G)通信时代将有数以千亿计的物联网设备接入网络，不同类型应用场景对网络的需求是差异化的。网络切片技术通过在同一网络基础设施上虚拟独立逻辑网络的方式，为不同的应用场景提供相互隔离的网络环境，使得不同应用场景可以按照各自的需求定制网络功能和特性，从而保障不同业务的需求。
在5G通信系统中，统一数据管理(unified data management，UDM)网元用于负责存储各用户设备(user equipment，UE)的会话上下文信息和签约数据。
UE可能接入一个或者多个网络切片。当UE通过不同类型的多个切片连接到同一个数据网络(data network，DN)时，若5G通信系统中的UDM网元参考第四代(the 4 th generation，4G)通信系统网络中的归属用户服务器(home subscriber server，HSS)以数据网络名称(data network name，DNN)粒度来管理UE的签约数据，签约数据无法满足各个切片不同的需求，且无法实现切片间的隔离。
发明内容
本申请描述了一种会话信息管理方法和装置。
一方面，本申请的实施例提供了一种会话信息管理方法，该方法包括：会话管理功能SMF网元向数据管理网元发送终端设备的标识信息(例如，SUPI)、数据网络名称DNN和切片信息，以请求终端设备的与所述DNN和切片信息关联的第一签约数据；SMF网元从数据管理网元接收第一签约数据。其中，切片信息用于标识SMF网元服务的网络切片(例如，S-NSSAI或hS-NSSAI或NSI ID)。
根据上述方案，当SMF网元向数据管理网元请求终端设备的签约数据时，不仅提供了DNN，还提供了切片信息。这样，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：SMF网元向数据管理网元发送终端设备的标识信息、SMF信息、DNN和切片信息，以在数据管理网元中注册SMF网元。例如，SMF信息包括SMF网元的标识信息和SMF网元的地址信息中的至少一项。
在数据管理网元中注册SMF网元的目的在于：当数据管理网元中的签约数据更新时，可以根据切片信息和DNN确定相关的SMF网元，向该SMF网元通知更新后的签约数据。因此，根据上述方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：SMF网元从数据管理网元接收终端设备的标 识信息、第二签约数据、所述DNN和切片信息，将与所述DNN和切片信息关联的第一签约数据更新为第二签约数据。
在一种可能的设计中，该方法还包括：SMF网元从数据管理网元接收终端设备的标识信息、DNN和切片信息，删除SMF网元上的终端设备的与所述DNN和切片信息关联的第一签约数据。由此，当UDM确定需要删除SMF上的签约数据时，UDM可以根据终端设备的上下文信息找到与该签约数据对应的SMF，从而通知该SMF删除签约数据，并在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：SMF网元向数据管理网元发送终端设备的标识信息、DNN和所述切片信息，以删除与所述DNN和切片信息关联的SMF信息。由此，UDM收到DNN和切片信息后，可以根据终端设备的上下文信息找到与该DNN和切片信息对应的SMF信息，从而在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
再一方面，本申请还公开了一种会话信息管理方法，包括：SMF网元向数据管理网元发送终端设备的标识信息、SMF信息、DNN和切片信息，以在数据管理网元中注册SMF网元。例如，SMF信息包括SMF网元的标识信息和SMF网元的地址信息中的至少一项。在数据管理网元中注册SMF网元的目的在于：当数据管理网元中的签约数据更新时，可以根据切片信息和DNN确定相关的SMF网元，向该SMF网元通知更新后的签约数据。因此，根据上述方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：SMF网元从数据管理网元接收终端设备的标识信息、第二签约数据、所述DNN和切片信息，将与所述DNN和切片信息关联的第一签约数据更新为第二签约数据。
在一种可能的设计中，该方法还包括：SMF网元从数据管理网元接收终端设备的标识信息、DNN和切片信息，删除SMF网元上的终端设备的与所述DNN和切片信息关联的第一签约数据。由此，当UDM确定需要删除SMF上的签约数据时，UDM可以根据终端设备的上下文信息找到与该签约数据对应的SMF，从而通知该SMF删除签约数据，并在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：SMF网元向数据管理网元发送终端设备的标识信息、DNN和所述切片信息，以删除与所述DNN和切片信息关联的SMF信息。由此，UDM收到DNN和切片信息后，可以根据终端设备的上下文信息找到与该DNN和切片信息对应的SMF信息，从而在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
又一方面，本申请还公开了一种会话信息管理方法，包括：数据管理网元从会话管理功能SMF网元接收终端设备的标识信息、数据网络名称DNN和切片信息，以请求终端设备的与DNN和切片信息关联的第一签约数据。数据管理网元向所述SMF网元发送第一签约数据。其中，切片信息用于标识SMF网元服务的网络切片(例如，S-NSSAI或hS-NSSAI或 NSI ID)。
根据上述方案，当SMF网元向数据管理网元请求终端设备的签约数据时，不仅提供了DNN，还提供了切片信息。这样，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：数据管理网元从SMF网元接收终端设备的标识信息、SMF信息、DNN和切片信息，以在数据管理网元中注册所述SMF网元。数据管理网元在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。其中，SMF信息包括SMF网元的标识信息和SMF网元的地址信息中的至少一项。
在数据管理网元中注册SMF网元的目的在于：当数据管理网元中的签约数据更新时，可以根据切片信息和DNN确定相关的SMF网元，向该SMF网元通知更新后的签约数据。因此，根据上述方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：数据管理网元将终端设备的第一签约数据更新为第二签约数据，确定与所述第一签约数据关联的DNN和切片信息，向与所述DNN和切片信息关联的SMF网元发送终端设备的标识信息、DNN、切片信息和第二签约数据。
在一种可能的设计中，该方法还包括：数据管理网元删除数据管理网元上的第一签约数据，在终端设备的上下文信息中删除SMF信息；向SMF网元发送终端设备的标识信息、DNN和切片信息。由此，当UDM确定需要删除SMF上的签约数据时，UDM可以根据终端设备的上下文信息找到与该签约数据对应的SMF，从而通知该SMF删除签约数据，并在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：数据管理网元从SMF网元接收终端设备的标识信息、DNN和切片信息，在终端设备的上下文信息中删除与所述DNN和切片信息关联的SMF信息。由此，UDM收到DNN和切片信息后，可以根据终端设备的上下文信息找到与该DNN和切片信息对应的SMF信息，从而在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
又一方面，本申请还公开了一种会话信息管理方法，包括：数据管理网元从SMF网元接收终端设备的标识信息、SMF信息、DNN和切片信息，以在数据管理网元中注册所述SMF网元。数据管理网元在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。其中，SMF信息包括SMF网元的标识信息和SMF网元的地址信息中的至少一项。
在数据管理网元中注册SMF网元的目的在于：当数据管理网元中的签约数据更新时，可以根据切片信息和DNN确定相关的SMF网元，向该SMF网元通知更新后的签约数据。因此，根据上述方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：数据管理网元将终端设备的第一签约数据更新为第二签约数据，确定与所述第一签约数据关联的DNN和切片信息，向与所述DNN和切片信息关联的SMF网元发送终端设备的标识信息、DNN、切片信息和第二签约数据。
在一种可能的设计中，该方法还包括：数据管理网元删除数据管理网元上的第一签约数据，在终端设备的上下文信息中删除SMF信息；向SMF网元发送终端设备的标识信息、DNN和切片信息。由此，当UDM确定需要删除SMF上的签约数据时，UDM可以根据终端设备的上下文信息找到与该签约数据对应的SMF，从而通知该SMF删除签约数据，并在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在一种可能的设计中，该方法还包括：数据管理网元从SMF网元接收终端设备的标识信息、DNN和切片信息，在终端设备的上下文信息中删除与所述DNN和切片信息关联的SMF信息。由此，UDM收到DNN和切片信息后，可以根据终端设备的上下文信息找到与该DNN和切片信息对应的SMF信息，从而在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
在以上各个方面和可能的设计中，切片信息用于标识所述终端设备接入的网络切片，或者，所述切片信息用于标识在归属地公共陆地移动网络HPLMN内所述SMF网元服务的网络切片。第一签约数据包括以下中的至少一项：签约的聚合最大比特速率AMBR；签约的服务质量QoS档案；签约的计费特征；静态的网络协议IP地址或静态的IP前缀；会话和业务连续性SSC模式。
又一方面，本申请实施例提供了一种会话管理功能网元，该会话管理功能实体具有实现上述方法中会话管理功能网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，会话管理功能网元的结构中包括处理器和收发器，所述处理器被配置为处理会话管理功能网元执行上述方法中相应的功能。所述收发器用于实现会话管理功能网元与接入和移动性管理功能网元/数据管理网元之间的通信。所述会话管理功能网元还可以包括存储器，所述存储器用于与处理器耦合，其保存会话管理功能实体必要的程序指令和数据。
又一方面，本申请实施例提供了一种数据管理网元，该数据管理网元具有实现上述方法中数据管理网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，数据管理网元的结构中包括处理器和收发器，所述处理器被配置为处理数据管理网元执行上述方法中相应的功能。所述收发器用于实现数据管理网元与会话管理功能网元之间的通信。所述数据管理网元还可以包括存储器，所述存储器用于与处理器耦合，其保存会话管理功能实体必要的程序指令和数据。
又一方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
又一方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
又一方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持上述会 话管理功能网元或数据管理网元实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存数据发送设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
下面将对实施例描述中所需要使用的附图作简单地介绍。
图1为本发明实施例适用的基于网络切片的非漫游或本地疏导(local breakout，LBO)场景下的通信系统的示意图；
图2A和图2B为根据本发明实施例的会话信息管理方法的信令交互图；
图3为根据本发明实施例的建立分组数据单元(Packet Data Unit，PDU)会话的信令交互图；
图4为根据本发明实施例的修改PDU会话的信令交互图；
图5为根据本发明实施例的释放PDU会话的信令交互图；
图6为根据本发明实施例的释放PDU会话的另一信令交互图；
图7为本发明实施例适用的基于网络切片的归属地路由漫游(home-routed roaming)场景下的通信系统的示意图；
图8为根据本发明实施例的建立PDU会话的信令交互图；
图9为根据本发明实施例的修改PDU会话的信令交互图；
图10为根据本发明实施例的释放PDU会话的信令交互图；
图11为根据本发明实施例的释放PDU会话的另一信令交互图；
图12A、12B为根据本发明实施例的SMF网元的结构示意图；
图13A、13B为根据本发明实施例的数据管理网元的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述。
本申请实施例基于图1所示的通信系统中提出了一种解决方案，可适用于在下一代移动网络(如5G网络)架构中实现会话信息的管理。例如，在5G移动网络架构中，移动网关的控制面功能和转发面功能解耦，其分离出来的控制面功能与第三代合作伙伴计划(third generation partnership project，3GPP)传统的控制网元MME等合并成统一的控制面(control plane)网元。用户面UPF网元能实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能(SGW-U和PGW-U)。进一步的，统一的控制面网元可以分解成接入和移动性管理功能(access and mobility management function，AMF)网元和会话管理功能(session management function，SMF)网元。其中，AMF网元可负责终端设备的附着、移动性管理、跟踪区更新流程等。SMF网元可负责终端设备的会话管理，用户面设备的选择、用户面设备的重选、网络协议(internet protocol，IP)地址分配、服务质量(quality of service，QoS)控制，以及会话的建立、修改和释放等。
此外，本申请实施例还可以适用于面向未来的其他通信技术。本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，本申请实施例提供了一种基于网络切片的通信系统。图1适用于非漫游或LBO的场景。例如，该通信系统至少包括终端设备102、接入网设备104和多个网络切片，例如：网络切片1和网络切片2。在以下描述中，以“网络切片”的简称“切片”进行描述，此外，各个切片也可称为“切片实例(slice instance)”或“网络切片实例(network slice instance)”，本申请并不在此限制。
终端设备102可接入一个或同时接入多个切片。在图1的例子中，终端设备102同时接入切片1和切片2。例如，切片1为增强移动宽带(Enhanced Mobile Broadband，eMBB)类型的切片，切片2为极高可靠极低时延通信(Ultra-Reliable and Low-Latency Communication，URLLC)类型的切片。切片1和切片2可以共享部分控制面，也可称为共享的控制面功能(common control network function，CCNF)。其中，切片1和切片2可以共享的控制面包括了AMF网元106。此外，会话管理功能是切片特有的，这部分控制功能需要实例化在切片内。为了实现数据路由的隔离，用户面功能也需要实例化在切片内。换句话说，会话管理功能和用户面功能是切片专有的，用于实现切片特定的服务。例如，在图1的例子中，切片1中包括SMF网元108a以及用户面网元210a；切片2中包括SMF网元108b以及用户面网元210b。
其中，本申请实施例中所涉及到的终端设备102(terminal device)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。所述终端设备也可以称为用户设备(user equipment，UE)，移动台(mobile station,MS)，终端(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)终端等。
本申请实施例中所涉及到的接入网设备是一种部署在有线或无线接入网中用以为终端设备102提供无线通信功能的装置。所述接入网设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB),在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。在新一代系统中，称为gNB(gNodeB)。
本申请实施例中所涉及到的AMF网元可负责终端设备的附着、移动性管理、跟踪区更新流程等。AMF网元也可称为AMF设备或AMF网元。在图1的例子中，仅示出了一个AMF网元。然而，本发明并不限制AMF网元的数量。不同的AMF网元可以连接至不同的切片，也可以连接至相同的切片。AMF网元也可称为AMF设备或AMF实体。为便于描述，以下将简称为“AMF”。
在图1的例子中，切片1和切片2分别包括一个SMF网元：SMF网元108a和108b。本申请实施例中所涉及到的SMF网元可负责终端设备的会话管理，用户面网元的选择、用户面网元的重选、IP地址分配、QoS控制，以及会话的建立、修改和释放。SMF网元也可称为SMF设备或SMF实体。为便于描述，以下将简称为“SMF”。
此外，在图1的例子中，切片1和切片2分别包括一个UPF网元：UPF网元210a和UPF网元210b。UPF网元210a和UPF网元210b可连接至相同或不同的数据网络(data network，DN)，用于实现业务的数据传输。UPF网元也可称为UPF设备或UPF实体。
本通信系统还包括数据管理设备112。该数据管理网元用于存储用户的签约数据，例如：移动性管理相关的签约数据以及会话管理相关的签约数据。例如，数据管理网元为统一数据管理(unified data management，UDM)网元。UDM网元也可称为UDM设备或UDM实体。为便于描述，以下将简称为“UDM”。
在上述基于网络切片的通信系统下，终端设备102可以接入一个或同时接入多个切片。各个切片可提供不同的业务。此外，运营商也可布局多个切片来为不同的用户组提供相同的业务。不同的切片可以连接至同一个DN。
切片的类型可通过单网络切片选择辅助信息(Single Network Slice Selection Assistance information，S-NSSAI)标识。NSSAI是S-NSSAI的集合。每个S-NSSAI用于辅助网络选择一个特定的网络切片实例。通过不同的S-NSSAI也可能选择到相同的网络切片实例。
在本申请以下描述中，用于标识切片的切片信息可以是切片的标识信息和切片的类型信息中的至少一项，或者，也可以是其他可以标识切片的信息。例如，切片的标识信息为网络实例标识(network slice instance ID，NSI ID)。切片的类型信息包括上述S-NSSAI。其中，S-NSSAI包括切片/服务类型(Slice/Service Type,SST)。SST指的是期望的网络切片在特征和服务的表现。例如，标准化的SST包括：eMBB、URLLC、或海量物联网(massive internet of things,MIoT)。可选的，S-NSSAI还包括切片区分指示(Slice Differentiator,SD)。SD是一个可选的信息，用于补充SST来区分相同SST类型的多个网络切片。在一种可能的实现方式中，用于标识切片类型的切片信息可以是S-NSSAI中的SST。在另一种可能的实现方式中，该切片信息为SST和SD的组合。为便于描述，以下实施例以切片信息为S-NSSAI为例进行描述，然而，本发明对此并不限制。
本发明公开了一种会话信息管理方法。会话信息包括签约数据和UE的会话上下文信息。图2A和图2B分别从签约数据和UE的会话上下文的角度，描述本发明。
图2A示出了根据本发明实施例的一种会话信息管理方法。该方法可由SMF网元(例如，图1中的SMF网元108a或108b)和数据管理网元(例如，图1中的数据管理网元112)交互执行。该方法包括：
步骤201，SMF网元向数据管理网元发送终端设备的标识信息、DNN和切片信息，以请求终端设备的与该DNN和切片信息关联的第一签约数据。
相应的，数据管理网元从SMF网元接收终端设备的标识信息、DNN和切片信息。
其中，切片信息用于标识该SMF网元服务的网络切片。在非漫游或LBO的场景下，该 SMF网元服务的切片即该终端设备接入的切片。
终端设备的标识信息为终端设备的永久标识，例如，用户永久标识(subscriber permanent ID，SUPI)。
例如，SMF网元可以通过调用UDM的网络功能(network function，NF)服务，以请求UE签约数据。请求获取签约数据的服务可以是Nudm_Subscriber_Data_Get。例如，可通过发送Nudm_Subscriber_Data_GetRequest调用该服务。Nudm_Subscriber_Data_GetRequest包括终端设备的标识信息、DNN和切片信息。换句话说，调用该服务的输入包括终端设备的标识信息、DNN和切片信息。或者，SMF可以通过向UDM发送携带终端设备的标识信息、DNN和切片信息的其他请求消息，以请求终端设备的与该DNN和切片信息关联的签约数据。
数据管理网元收到终端设备的标识信息、DNN和切片信息后，可在该终端设备的签约数据中查找与该DNN和切片信息关联的第一签约数据。
例如，第一签约数据包括包括以下中的至少一项：签约的(aggregate maximum bit rate，AMBR)；签约的QoS档案；签约的计费特征；静态的IP地址或静态的IP前缀；会话和业务连续性(session and service cont inuity,SSC)模式。其中，AMBR可以是不同粒度的AMBR，例如，UE粒度的AMBR、会话粒度的AMBR、DNN粒度的AMBR、切片粒度的AMBR、或DNN及切片粒度的AMBR，本发明在此并不限制。相对于现有技术中动态分配IP地址或IP前缀，静态IP地址或静态IP前缀保持不变。
例如，数据管理网元中以如下表1的形式保存终端设备的签约数据。
签约的AMBR 1 切片1 DNN1
签约的QoS档案1 切片1 DNN1
签约的计费特征1 切片1 DNN1
静态的IP地址1 切片1 DNN1
签约的AMBR 2 切片2 DNN1
签约的QoS档案2 切片2 DNN1
签约的计费特征2 切片2 DNN1
静态的IP地址2 切片2 DNN1
签约的AMBR 3 切片1 DNN2
签约的QoS档案3 切片1 DNN2
签约的计费特征3 切片1 DNN2
静态的IP地址3 切片1 DNN2
表1
如上述表1表示，数据管理网元内存储了与切片1(例如对应S-NSSAI 1)和DNN1关联的签约数据：签约的AMBR 1、签约的QoS档案1、签约的计费特征1、静态的IP地址1；与切片2(例如对应S-NSSAI 2)和DNN1关联的签约数据：签约的AMBR 2、签约的QoS档案2、签约的计费特征2、静态的IP地址2；以及与切片1和DDN2关联的签约数据：签约的AMBR 3、签约的QoS档案3、签约的计费特征3、静态的IP地址3。假设数据管理网元收到的DNN为DNN1，收到的切片信息为对应切片1的S-NSSAI 1，则与DNN1和切片1关联的第一签约数据至少包括签约的AMBR 1、签约的QoS档案1、签约的计费特征1、静态的IP 地址1中的至少一项。
步骤202，数据管理网元将查找到的与该DNN和切片信息关联的第一签约数据发送至SMF网元。相应的，SMF网元从数据管理网元接收上述第一签约数据。
因此，根据本发明实施例的方案，当SMF网元向数据管理网元请求终端设备的签约数据时，不仅提供了DNN，还提供了切片信息。这样，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。
以图1的场景为车联网为例。终端设备可以是该车联网内的汽车，可能会在URLLC切片(例如，切片1)上建立PDU会话1与DN交互控制信息，同时在eMBB切片(例如，切片2)上建立PDU会话2与DN传输数据流(比如向DN上传驾驶室内的监控视频流，或者从DN动态下载路况数据)。终端设备可能会通过两个切片连接到同一个DN(例如，对应DNN1)。这两个切片上的PDU会话的签约的AMBR、签约的QoS档案、签约的计费特征、静态的IP地址、SSC模式都可能有很大的差别。因此，数据管理网元需要以切片为粒度管理这些签约数据。若切片1的SMF网元108a通过向数据管理网元发送DNN1和切片1的切片信息以请求签约数据时，数据管理网元会把与切片1对应的签约数据发送至SMF网元108，而不会把与切片2对应的签约数据也发送至SMF网元108，从而满足了该切片特定的参数需求和切片间相互隔离的原则，也避免了信令和资源的浪费。
图2B示出了根据本发明实施例的一种会话信息管理方法，包括：
步骤211，SMF网元获取DNN和切片信息。
步骤212，SMF网元向数据管理网元发送终端设备的标识信息、SMF信息、DNN和切片信息，以在数据管理网元中注册所述SMF网元。相应的，数据管理网元从SMF网元接收终端设备的标识信息、SMF信息、数据网络名称DNN和切片信息。
其中，终端设备的标识信息和切片信息可参考图2A中的描述。SMF信息包括SMF网元的标识信息(SMF ID)和SMF网元的地址信息(SMF address)中的至少一项。
例如，SMF网元可以通过调用UDM的NF服务，以注册该SMF网元。请求注册SMF网元的服务可以是Nudm_UEContextManagement_Registration。例如，可通过发送Nudm_UEContextManagement_RegistrationRequest调用该服务。Nudm_UEContextManagement_RegistrationRequest包括终端设备的标识信息、SMF信息、DNN和上述切片信息。换句话说，调用该服务的输入包括终端设备的标识信息、SMF信息、DNN和上述切片信息。或者，SMF可以通过向UDM发送携带终端设备的标识信息、SMF信息、DNN和上述切片信息的其他请求消息，以在UDM中注册该SMF。
步骤213，数据管理网元在终端设备的上下文信息中存储与上述DNN和切片信息关联的SMF信息。
例如，终端设备的上下文信息可以具有表2的格式。
SMF ID 1 切片信息1 DNN 1
SMF ID 2 切片信息2 DNN 1
表2
表2以SMF信息为SMF ID为例，然而，还可以以SMF地址替换SMF ID，或同时保存SMF ID和SMF地址。如上述表2所示，终端的上下文信息中增加了切片信息的维度，以区分连接至同一个DN的不同切片所对应的SMF网元。
需要说明的是，以上步骤可用于在数据管理网元中注册SMF网元。这些步骤可以构成一个独立的实施例，或者，也可在图2A的步骤完成后执行。若这些步骤在图2A的步骤完成后执行，可跳过步骤211。或者，以上步骤也可与图2A中的步骤同时执行。例如，若在图2A中的步骤201中，SMF还向数据管理网元提供了SMF信息，数据管理网元可以在向该SMF网元提供签约数据的同时注册该SMF网元。
在数据管理网元中注册SMF网元的目的在于：当数据管理网元中的签约数据更新时，可以根据切片信息和DNN确定相关的SMF网元，向该SMF网元通知更新后的签约数据。因此，根据本发明实施例的方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
可选的，上述图2A和图2B的两种方案还可以包括以下步骤：
在一种可能的设计中，在SMF网元被注册在数据管理网元中后，可以更新签约数据。例如：
数据管理网元将终端设备的第一签约数据更新为第二签约数据，确定与第一签约数据关联的DNN和切片信息；向与所述DNN和所述切片信息关联的SMF网元发送所述终端设备的标识信息、所述DNN、所述切片信息和所述第二签约数据。
SMF网元从数据管理网元接收所述终端设备的标识信息、第二签约数据、所述DNN和所述切片信息，将与所述DNN和所述切片信息关联的所述第一签约数据更新为所述第二签约数据。
这部分内容将结合后面的图4做进一步描述。
在一种可能的设计中，可由数据管理网元触发PDU会话的释放流程。例如：
数据管理网元向SMF网元发送终端设备的标识信息、所述DNN和所述切片信息。相应的，SMF网元从所述数据管理网元接收终端设备的标识信息、所述DNN和所述切片信息，删除SMF网元上的所述终端设备的与所述DNN和所述切片信息关联的第一签约数据。
此外，数据管理网元删除所述数据管理网元上的第一签约数据；并在所述终端设备的上下文信息中删除所述SMF信息。
这部分内容将结合后面的图5做进一步描述。
在一种可能的设计中，可由SMF网元触发删除数据管理网元上的SMF信息。例如：
SMF网元向数据管理网元发送终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。相应的，数据管理网元从所述SMF网元接收所述终端设备的标识信息、所述DNN和所述切片信息；在所述终端设备的上下文信息中删除与所述DNN和所述切片信息关联的所述SMF信息。
这部分内容将结合后面的图6做进一步描述。
以下将结合图3至图6的实施例介绍本申请实施例的会话信息管理方法。
图3的方法可适用于建立PDU会话的流程。如图3所示，该方法包括：
步骤301，终端设备发起PDU会话建立流程。例如，终端设备向AMF发送非接入层(non-access stratum，NAS)消息，该NAS消息包括会话管理(session management，SM)信息(例如，N1SM信息)、S-NSSAI和DNN。该会话管理信息携带PDU会话建立请求。
步骤302，AMF根据S-NSSAI选择SMF。
步骤303，AMF向SMF发送DNN和S-NSSAI，以通知SMF建立会话。
例如，AMF可以通过调用SMF的用于建立PDU会话的NF服务(例如，Nsmf_PDUSession_CreateSM)，以通知SMF建立会话。其中，可通过发送请求消息(例如，Nsmf_PDUSession_CreateSMRequest)调用该服务。Nsmf_PDUSession_CreateSMRequest包括DNN和S-NSSAI。换句话说，调用该服务的输入包括DNN和S-NSSAI。或者，AMF可以通过向SMF发送携带DNN和S-NSSAI的其他请求消息，以通知SMF建立会话。
步骤304，SMF收到DNN和S-NSSAI后，向UDM发送终端设备的标识信息、DNN和切片信息，以请求与该DNN和切片信息关联的签约数据。
例如，SMF可以通过调用Nudm_Subscriber_Data_Get的服务，以请求UE签约数据。其中，可通过发送Nudm_Subscriber_Data_GetRequest调用该服务。Nudm_Subscriber_Data_GetRequest包括终端设备的标识信息、DNN和切片信息。换句话说，调用该服务的输入包括终端设备的标识信息、DNN和切片信息。此外，输入还可以包括：SMF信息(SMF ID或SMF地址中的至少一项)，请求的签约数据类型。例如，请求的签约数据类型为SM签约数据。或者，SMF可以通过向UDM发送携带终端设备的标识信息、DNN和切片信息的其他请求消息，以请求与该DNN和切片信息关联的签约数据。
步骤305，UDM收到终端设备的标识信息、DNN和切片信息之后，在该终端设备的签约中，根据DNN和切片信息确定与该DNN和切片信息关联的签约数据。
例如，UDM内存储的终端设备的签约数据可以具有上述表1的格式。
步骤306，UDM向SMF发送与该DNN和切片信息关联的签约数据。例如，UDM可以向SMF发送携带与该DNN和切片信息关联的UE签约数据的响应消息。例如，该响应消息可以是Nudm_Subscriber_Data_Get服务的响应消息Nudm_SubscriberData_GetResponse。可选的，该响应消息还携带上述切片信息和DNN。
以上步骤304至306可参考图2A的描述。
步骤307，多侧交互，实现鉴权、授权和用户面的建立。
步骤308，可选的，如果步骤304中的输入不包括SMF信息，则SMF将终端设备的标识信息、SMF信息、DNN和上述切片信息发送至UDM，以在UDM中注册该SMF。
例如，SMF可以通过调用Nudm_UEContextManagement_Registration的服务来注册该SMF。其中，可通过发送Nudm_UEContextManagement_RegistrationRequest调用该服务。Nudm_UEContextManagement_RegistrationRequest包括终端设备的标识信息、SMF信息、DNN和上述切片信息。换句话说，调用该服务的输入包括终端设备的标识信息、SMF信息、DNN和上述切片信息。或者，SMF可以通过向UDM发送携带终端设备的标识信息、SMF信息、DNN和上述切片信息的其他请求消息，以在UDM中注册该SMF。
步骤309，UDM在UE上下文中保存与DNN和上述切片信息关联的SMF信息。例如，UE上下文可以具有上述表2的格式。
以上步骤308至309可以参考图2B的描述。
步骤310，UDM向SMF返回响应消息。
可选的，该响应消息中携带上述DNN和切片信息。
根据本发明实施例的方案，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。此外，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
需要说明的是，以上的步骤304至306可对应服务化架构下的SMF向UDM调用NF服务：Nudm_Subscriber_Data_Get的交互流程。步骤308至310可对应服务化架构下SMF向UDM调用NF服务：Nudm_UEContextManagement_Registration的交互流程流程。
图4的方法可适用于修改PDU会话的流程。如图4所示，该方法包括：
步骤401，当UDM更新签约数据时，UDM根据保存的终端设备的上下文信息，选择与该DNN和切片信息关联的SMF。
例如，UDM内保存的签约数据可以由网管设备来配置或维护。当终端设备的某项签约数据发生变化时，例如，由于用户更换套餐导致AMBR变化，UDM更新签约数据。
具体的，UDM将终端设备的第一签约数据更新为第二签约数据后，确定与第一签约数据关联的DNN和切片信息，进而确定与所述DNN和所述切片信息关联的SMF网元。
例如，当表1中的签约数据签约的session-AMBR 1更新为签约的session-AMBR 4时，UDM确定与签约的AMBR 1关联的切片1的切片信息1和DNN1，然后根据例如表2的上下文信息，选择与该DNN1和切片信息1关联的SMF(具有SMF ID1)。
步骤402，UDM向SMF发送DNN和切片信息，以更新终端设备的与该DNN和切片信息关联的签约数据。
例如，UDM可以通过调用Nudm_Subscriber_Data_UpdateNotification的服务，以更新与该DNN和切片信息关联的UE签约数据。其中，可通过发送Nudm_Subscriber_Data_UpdateNotification Notify调用该服务。Nudm_Subscriber_Data_UpdateNotification Notify包括终端设备的标识信息、DNN和切片信息和签约数据(如上述第二签约数据)。换句话说，调用该服务的输入包括终端设备的标识信息、DNN、切片信息和签约数据(如上述第二签约数据)。或者，UDM可以通过向SMF发送携带终端设备的标识信息、DNN和切片信息和签约数据的其他通知消息，以更新终端设备的与该DNN和切片信息关联的签约数据。
步骤403，SMF根据输入的信息，更新终端设备的与该DNN和切片信息关联的UE签约数据。
举例来说，输入包括终端设备的标识信息、DNN1、切片1的切片信息1、和Subscribed-session-AMBR 4。由此，SMF将该终端设备的与DNN1和切片1关联的Subscribed-session-AMBR 1更新为Subscribed-session-AMBR 4。
步骤404，签约数据更新后，SMF向UDM返回携带终端设备的标识信息的确认消息 (acknowledge，ACK)。换句话说，调用该服务后的输出包括终端设备的标识信息。
步骤404执行完毕后，可参考现有技术执行会话修改流程的后续步骤。
根据本发明实施例的方案，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
需要说明的是，以上的步骤402至404可对应服务化架构下的UDM向SMF调用NF服务：Nudm_Subscriber_Data_UpdateNotification的交互流程。
图5的方法可适用于释放PDU会话的流程，适用于由UDM触发PDU会话的释放流程。如图5所示，该方法包括：
步骤501，UDM确定需要删除SMF上的签约数据。
例如，UDM确定与需要删除的签约数据关联的DNN和切片信息，进而根据终端设备的上下文信息确定与该DNN和切片信息关联的SMF。
步骤502，UDM向SMF发送终端设备的标识信息、DNN和切片信息，以删除SMF上的所述终端设备的与所述DNN和所述切片信息关联的第一签约数据。
例如，UDM可以通过调用Nudm_UE Context Management_RemoveNotification的服务，以删除SMF上的签约数据。其中，可通过发送携带终端设备的标识信息、DNN和切片信息的Nudm_Subscriber_Data_UpdateNotification Notify或携带终端设备的标识信息、DNN和切片信息的Nudm_Subscriber_Data_UpdateNotification Request调用该服务。换句话说，调用该服务的输入包括终端设备的标识信息、DNN和切片信息。或者，UDM可以通过向SMF发送携带终端设备的标识信息、DNN和切片信息的其他通知消息或请求消息，以删除SMF上的签约数据。
步骤503，SMF删除SMF上的所述终端设备的与所述DNN和所述切片信息关联的第一签约数据。
步骤504，SMF返回响应消息或确认消息。
需要说明的是，UDM可以在步骤501确定需要删除SMF上的签约数据的同时删除UDM上的第一签约数据和上下文信息中的该SMF信息。例如，UDM可以先删除UDM上的第一签约数据，由此导致上下文信息中的该SMF信息被删除。或者，UDM也可以在收到步骤504的响应消息或确认消息后才通过以下步骤505删除UDM上的第一签约数据和上下文信息中的该SMF信息。如果在步骤504之前中已删除UDM上的第一签约数据和上下文信息中的该SMF信息，可跳过步骤505和506。或者，步骤505和506也可在会话释放流程完成后才执行。
步骤505，UDM删除UDM上的第一签约数据和上下文信息中的该SMF信息。
步骤506，UDM向SMF发送结果指示(Result indication)。
步骤507，SMF决定触发PDU会话释放流程，并参考现有技术执行会话释放流程的后续步骤。
根据本发明实施例的方案，当UDM确定需要删除SMF上的签约数据时，UDM可以根据终端设备的上下文信息找到与该签约数据对应的SMF，从而通知该SMF删除签约数据，并在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离 的原则，且避免了信令和资源的浪费。
需要说明的是，以上的步骤502至504可对应服务化架构下的UDM向SMF调用NF服务：Nudm_UE Context Management_RemoveNotification的交互流程。
图6的方法可适用于释放PDU会话的流程，适用于由SMF触发删除UDM上的SMF信息。如图6所示，该方法包括：
步骤601，SMF决定释放PDU会话。换句话说，SMF决定触发PDU会话释放流程。例如，SMF基于来自UDM的请求、DN的请求或本地配置的策略决定释放PDU会话。
步骤602，可参考现有技术执行PDU会话释放的后续流程。
步骤603，当SMF判断所服务切片和DN上终端设备的最后一个PDU会话已经释放，向UDM发送终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
例如，SMF可以通过调用Nudm_UE Context Management_Purge的服务，以删除与所述DNN和所述切片信息关联的所述SMF信息。其中，可通过发送携带终端设备的标识信息、DNN和切片信息的Nudm_UE Context Management_Purge Notify或携带终端设备的标识信息、DNN和切片信息的Nudm_UE Context Management_Purge Request调用该服务。换句话说，调用该服务的输入包括终端设备的标识信息、DNN和切片信息。或者，UDM可以通过向SMF发送携带终端设备的标识信息、DNN和切片信息的其他通知消息或请求消息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
步骤604，UDM在终端设备的上下文信息中删除与该切片信息和DNN关联的SMF信息。
步骤605，UDM向SMF发送结果指示。
根据本发明实施例的方案，UDM收到DNN和切片信息后，可以根据终端设备的上下文信息找到与该DNN和切片信息对应的SMF信息，从而在终端设备的上下文信息中删除这个SMF相关的信息。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
需要说明的是，以上的步骤603至605可对应服务化架构下的SMF向UDM调用NF服务：Nudm_UEContextManagement_Purge的交互流程。
图7示出了本发明适用的归属地路由漫游场景的架构示意图。其中，当终端设备从归属地的HPLMN漫游至拜访的公用陆地移动网(visited public land mobile network，VPLMN)内时，终端设备通过VPLMN内的接入网设备接入VPLMN内的切片V。切片V包括V-SMF和V-UPF。此外，HPLMN内的H-SMF与UDM相连。终端设备通过V-UPF和H-UPF连接至DN。H-SMF和H-UPF构成HPLMN内的切片H。
在漫游的场景下，由HPLMN内的H-SMF和UDM交互，执行类似于上述图3至图6所述的方法。切片信息具体用于标识HPLMN内切片，例如，hS-NSSAI，也可称为H-切片信息。
例如，图8为归属地路由漫游场景下建立PDU会话的信令交互图。
步骤801，终端设备向AMF发送NAS消息，该NSA消息包括SM信息、vS-NSSAI和DNN。该会话管理信息携带PDU会话建立请求。其中，vS-NSSAI用于标识VPLMN内切片的类型。
步骤802，AMF根据vS-NSSAI选择V-SMF，并将vS-NSSAI映射至hS-NSSAI。
步骤803,AMF向V-SMF发送DNN和vS-NSSAI，以通知V-SMF建立会话。
例如，AMF可以通过调用SMF的用于建立PDU会话的NF服务(例如，Nsmf_PDUSession_CreateSM)，以通知V-SMF建立会话。调用该服务的输入包括DNN和h-NSSAI。
步骤804，V-SMF通过调用Nsmf_PDUSession_CreateSM的服务，通知H-SMF建立会话。换句话说，V-SMF向H-SMF传递DNN和h-NSSAI。
步骤805，H-SMF收到DNN和hS-NSSAI后，向UDM发送终端设备的标识信息、DNN和切片信息，以请求与该DNN和切片信息关联的签约数据。
步骤806，UDM收到终端设备的标识信息、DNN和切片信息之后，在该终端设备的签约中，根据DNN和切片信息确定与该DNN和切片信息关联的签约数据。
步骤807，UDM向H-SMF发送与该DNN和切片信息关联的签约数据。
步骤808，多侧交互，实现鉴权、授权和用户面的建立。
步骤809，可选的，如果步骤805中的输入不包括H-SMF信息，，则H-SMF将终端设备的标识信息、H-SMF的SMF信息、DNN和上述切片信息发送至UDM，以在UDM中注册该H-SMF。
步骤810，UDM在UE上下文中保存与DNN和上述切片信息关联的SMF信息。
步骤811，UDM向H-SMF返回响应消息。
以上步骤805至811可参考图3中步骤304至310的描述。图8中H-SMF和UDM之间的交互与图3中SMF与UDM之间的交互一致。
图9为归属地路由漫游场景下修改PDU会话的信令交互图。其中，步骤901至904可参考图4中步骤401至404的描述。图9中H-SMF和UDM之间的交互与图4中SMF与UDM之间的交互一致。该方法还包括：
步骤905，H-SMF向V-SMF发送DNN和H-切片信息。例如，H-SMF调用Nsmf_PDU Session_UpdateNotification的服务,以在VPLMN内更新指定切片上的签约数据。例如，调用该服务的输入包括DNN和H-切片信息。
步骤905执行完毕后，可参考现有技术执行会话修改流程的后续步骤。
图10为归属地路由漫游场景下释放PDU会话的信令交互图。其中，步骤1001至1007可参考图5中步骤501至507的描述。图10中H-SMF和UDM之间的交互与图5中SMF与UDM之间的交互一致。该方法还包括：
步骤1008，H-SMF向V-SMF发送DNN和H-切片信息。例如，H-SMF调用Nsmf_PDU Session_Release的服务,以删除V-SMF上的签约数据。例如，调用该服务的输入包括DNN和H-切片信息。
步骤1008，可参考现有技术执行会话释放流程的后续步骤。
图11为归属地路由漫游场景下释放PDU会话的信令交互图。其中，步骤1101至1105可参考图6中步骤601至605的描述。图11中H-SMF和UDM之间的交互与图6中SMF与UDM之间的交互一致。区别在于，步骤1102中会话释放流程中的一些步骤涉及到VPLMN内的网元。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的会话信息管理方法等各方案进行了介绍。可以理解的是，各个网元，例如上述会话管理功能网元或数据管理网元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算 机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
例如，当上述网元通过软件模块来实现相应的功能。会话管理功能网元可包括接收模块1201、处理模块1202和发送模块1203，如图12A所示。该会话管理功能网元可用于执行上述图2至图11中SMF或H-SMF的操作。例如：
在一个实施例中，发送模块1203用于向数据管理网元发送终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片。接收模块1201用于从所述数据管理网元接收所述第一签约数据。
由此，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。
可选的，发送模块1203还用于向所述数据管理网元发送所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
在另一个实施例中，接收模块1201用于获取数据网络名称DNN和切片信息，其中，所述切片信息用于标识所述SMF网元服务的网络切片。发送模块用于用于向数据管理网元发送终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
由此，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
对于上述两种实施例中的任一，可选的，接收模块1201还用于从所述数据管理网元接收所述终端设备的标识信息、第二签约数据、所述DNN和所述切片信息。处理模块1202用于将与所述DNN和所述切片信息关联的所述第一签约数据更新为所述第二签约数据。
可选的，接收模块1201还用于从所述数据管理网元接收所述终端设备的标识信息、所述DNN和所述切片信息。处理模块1202用于删除所述SMF网元上的所述终端设备的与所述DNN和所述切片信息关联的所述第一签约数据。
可选的，发送模块1203还用于向所述数据管理网元发送所述终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
此外，会话管理功能网元中的接收模块1201、处理模块1202和发送模块1203还可实现上述方法中SMF或H-SMF的其他操作或功能，此处不再赘述。
图12B示出了上述实施例中所涉及的会话管理功能网元的另一种可能的结构示意图。会话管理功能网元包括收发器1204和处理器1205，如图12B所示。例如，处理器1205被配置为处理会话管理功能网元执行上述方法中SMF或H-SMF相应的功能。收发器1204用于实现SMF或H-SMF与接入和移动性管理功能网元/数据管理网元之间的通信。所述会话管理功能网元还可以包括存储器1206，所述存储器用于与处理器耦合，其保存会话管理 功能网元必要的程序指令和数据。
数据管理网元可包括接收模块1301、处理模块1302和发送模块1303，如图13A所示。该策略控制功能设备可用于执行上述图2至图11中数据管理网元(例如，UDM设备112)的操作。例如：
在一个实施例中，接收模块1301用于从会话管理功能SMF网元接收终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片。发送模块1303用于向所述SMF网元发送所述第一签约数据。
由此，数据管理网元可以将与该DNN和切片信息关联的第一签约数据发送至请求的SMF，从而满足了该切片特定的参数需求。此外，数据管理网元无需把与其他切片关联的签约数据发送至该SMF，符合切片间相互隔离的原则，也避免了信令和资源的浪费。
可选的，接收单元1301还用于从所述SMF网元接收所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。处理模块1302用于在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
在另一个实施例中，接收单元1301用于从会话管理功能SMF网元接收终端设备的标识信息、SMF信息、数据网络名称DNN和切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。处理模块1302用于在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
由此，当UDM网元中的签约数据更新时，若这个更新的签约数据只涉及某个切片，UDM能够根据UE的会话上下文信息，仅通知与DNN和该切片对应的SMF网元。由此，满足了切片之间相互隔离的原则，且避免了信令和资源的浪费。
对于上述两种实施例中的任一，可选的，接收模块1301还用于从所述数据管理网元接收所述终端设备的标识信息、第二签约数据、所述DNN和所述切片信息。处理模块1302用于将与所述DNN和所述切片信息关联的所述第一签约数据更新为所述第二签约数据。
可选的，接收模块1301还用于从所述数据管理网元接收所述终端设备的标识信息、所述DNN和所述切片信息。处理模块1302用于删除所述SMF网元上的所述终端设备的与所述DNN和所述切片信息关联的所述第一签约数据。
可选的，发送模块1303还用于向所述数据管理网元发送所述终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
此外，数据管理网元中的接收模块1301、处理模块1302和发送模块1303还可实现上述方法中UDM网元112的其他操作或功能，此处不再赘述。
图13B示出了上述实施例中所涉及的数据管理网元的另一种可能的结构示意图。数据管理网元包括收发器1304和处理器1305，如图13B所示。例如，处理器1305被配置为处理数据管理网元执行上述方法中UDM的功能。收发器1304用于实现UDM与SMF或H-SMF之间的通信。数据管理网元还可以包括存储器1306，所述存储器用于与处理器耦合，其保存数据管理网元必要的程序指令和数据。
可以理解的是，图12B、图13B仅仅示出了上述设备的简化设计。在实际应用中，上述每个设备可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本申请的设备都在本申请的保护范围之内。
用于执行本申请上述上述会话管理功能网元的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于会话管理功能网元中。当然，处理器和存储介质也可以作为分立组件存在于会话管理功能网元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (30)

  1. 一种会话信息管理方法，其特征在于，包括：
    会话管理功能SMF网元向数据管理网元发送终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    所述SMF网元从所述数据管理网元接收所述第一签约数据。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述SMF网元向所述数据管理网元发送所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
  3. 一种会话信息管理方法，其特征在于，包括：
    会话管理功能SMF网元获取数据网络名称DNN和切片信息，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    所述SMF网元向数据管理网元发送终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
  4. 根据权利要求2或3所述的方法，其特征在于，还包括；
    所述SMF网元从所述数据管理网元接收所述终端设备的标识信息、第二签约数据、所述DNN和所述切片信息；
    所述SMF将与所述DNN和所述切片信息关联的所述第一签约数据更新为所述第二签约数据。
  5. 根据权利要求2或3所述的方法，其特征在于，还包括：
    所述SMF网元从所述数据管理网元接收所述终端设备的标识信息、所述DNN和所述切片信息；
    所述SMF网元删除所述SMF网元上的所述终端设备的与所述DNN和所述切片信息关联的所述第一签约数据。
  6. 根据权利要求2至5中任一项所述的方法，其特征在于，还包括：
    所述SMF网元向所述数据管理网元发送所述终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
  7. 一种会话信息管理方法，其特征在于，包括：
    数据管理网元从会话管理功能SMF网元接收终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    所述数据管理网元向所述SMF网元发送所述第一签约数据。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述数据管理网元从所述SMF网元接收所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信 息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项；
    所述数据管理网元在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
  9. 一种会话信息管理方法，其特征在于，包括：
    数据管理网元从会话管理功能SMF网元接收终端设备的标识信息、SMF信息、数据网络名称DNN和切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述切片信息用于标识所述SMF网元服务的网络切片，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项；
    所述数据管理网元在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
  10. 根据权利要求8或9所述的方法，其特征在于，还包括：
    所述数据管理网元将所述终端设备的所述第一签约数据更新为第二签约数据；
    所述数据管理网元确定与所述第一签约数据关联的所述DNN和所述切片信息；
    所述数据管理网元向与所述DNN和所述切片信息关联的所述SMF网元发送所述终端设备的标识信息、所述DNN、所述切片信息和所述第二签约数据。
  11. 根据权利要求8或9所述的方法，其特征在于，还包括：
    所述数据管理网元删除所述数据管理网元上的所述第一签约数据；
    所述数据管理网元在所述终端设备的上下文信息中删除所述SMF信息；
    所述数据管理网元向所述SMF网元发送所述终端设备的标识信息、所述DNN和所述切片信息。
  12. 根据权利要求8至11中任一所述的方法，其特征在于，还包括：
    所述数据管理网元从所述SMF网元接收所述终端设备的标识信息、所述DNN和所述切片信息；
    所述数据管理网元在所述终端设备的上下文信息中删除与所述DNN和所述切片信息关联的所述SMF信息。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述切片信息用于标识所述终端设备接入的网络切片，或者，所述切片信息用于标识在归属地公共陆地移动网络HPLMN内所述SMF网元服务的网络切片。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，所述第一签约数据包括以下中的至少一项：
    签约的聚合最大比特速率AMBR；
    签约的服务质量QoS档案；
    签约的计费特征；
    静态的网络协议IP地址或静态的IP前缀；
    会话和业务连续性SSC模式。
  15. 一种会话管理功能网元，其特征在于，包括：
    发送模块，用于向数据管理网元发送终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    接收模块，用于从所述数据管理网元接收所述第一签约数据。
  16. 根据权利要求14所述的会话管理功能网元，其特征在于，所述发送模块还用于向所述数据管理网元发送所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
  17. 一种会话管理功能网元，其特征在于，包括：
    接收模块，用于获取数据网络名称DNN和切片信息，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    发送模块，用于向数据管理网元发送终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项。
  18. 根据权利要求16或17所述的会话管理功能网元，其特征在于，所述接收模块还用于从所述数据管理网元接收所述终端设备的标识信息、第二签约数据、所述DNN和所述切片信息；
    所述会话管理功能网元还包括处理模块，用于将与所述DNN和所述切片信息关联的所述第一签约数据更新为所述第二签约数据。
  19. 根据权利要求16或17所述的会话管理功能网元，其特征在于，所述接收模块还用于从所述数据管理网元接收所述终端设备的标识信息、所述DNN和所述切片信息；
    所述会话管理功能网元还包括处理模块，用于删除所述SMF网元上的所述终端设备的与所述DNN和所述切片信息关联的所述第一签约数据。
  20. 根据权利要求16至19中任一项所述的会话管理功能网元，其特征在于，所述发送模块还用于向所述数据管理网元发送所述终端设备的标识信息、所述DNN和所述切片信息，以删除与所述DNN和所述切片信息关联的所述SMF信息。
  21. 一种数据管理网元，其特征在于，包括：
    接收模块，用于从会话管理功能SMF网元接收终端设备的标识信息、数据网络名称DNN和切片信息，以请求所述终端设备的与所述DNN和所述切片信息关联的第一签约数据，其中，所述切片信息用于标识所述SMF网元服务的网络切片；
    发送模块，用于向所述SMF网元发送所述第一签约数据。
  22. 根据权利要求21所述的数据管理网元，其特征在于，所述接收单元还用于从所述SMF网元接收所述终端设备的标识信息、SMF信息、所述DNN和所述切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项；
    所述数据管理网元还包括处理模块，用于在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
  23. 一种数据管理网元，其特征在于，包括：
    接收模块，用于从会话管理功能SMF网元接收终端设备的标识信息、SMF信息、数据网络名称DNN和切片信息，以在所述数据管理网元中注册所述SMF网元，其中，所述切片信息用于标识所述SMF网元服务的网络切片，所述SMF信息包括所述SMF网元的标识信息和所述SMF网元的地址信息中的至少一项；
    处理模块，用于在所述终端设备的上下文信息中存储与所述DNN和所述切片信息关联的所述SMF信息。
  24. 根据权利要求22或23所述的数据管理网元，其特征在于，所述处理模块还用于将所述终端设备的所述第一签约数据更新为第二签约数据，确定与所述第一签约数据关联的所述DNN和所述切片信息，所述发送模块还用于向与所述DNN和所述切片信息关联的所述SMF网元发送所述终端设备的标识信息、所述DNN、所述切片信息和所述第二签约数据。
  25. 根据权利要求22或23所述的数据管理网元，其特征在于，所述处理模块还用于删除所述数据管理网元上的所述第一签约数据，在所述终端设备的上下文信息中删除所述SMF信息，所述发送模块还用于向所述SMF网元发送所述终端设备的标识信息、所述DNN和所述切片信息。
  26. 根据权利要求22至25中任一项所述的数据管理网元，其特征在于，所述接收单元还用于从所述SMF网元接收所述终端设备的标识信息、所述DNN和所述切片信息；所述处理单元还用于在所述终端设备的上下文信息中删除与所述DNN和所述切片信息关联的所述SMF信息。
  27. 根据权利要求15至20中任一项所述的会话管理功能网元，或21至26中任一项所述的数据管理网元，其特征在于，所述切片信息用于标识所述终端设备接入的网络切片，或者，所述切片信息用于标识在归属地公共陆地移动网络HPLMN内所述SMF网元服务的网络切片。
  28. 根据权利要求15至20中任一项所述的会话管理功能网元，或21至26中任一项所述的数据管理网元，其特征在于，所述第一签约数据包括以下中的至少一项：
    签约的聚合最大比特速率AMBR；
    签约的服务质量QoS档案；
    签约的计费特征；
    静态的网络协议IP地址或静态的IP前缀；
    会话和业务连续性SSC模式。
  29. 一种会话管理功能网元，其特征在于，包括：
    通信接口；
    存储器，用于存储指令；
    至少一个处理器，用于执行所述存储器中的所述指令，使得所述会话管理功能网元执行如权利要求1至7、13或14中任一项所述的方法。
  30. 一种数据管理网元，其特征在于，包括：
    通信接口；
    存储器，用于存储指令；
    至少一个处理器，用于执行所述存储器中的所述指令，使得所述数据管理网元执行如权利要求8至14中任一项所述的方法。
PCT/CN2018/088903 2017-08-11 2018-05-29 会话信息管理方法和装置 WO2019029235A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18844446.7A EP3657868A4 (en) 2017-08-11 2018-05-29 METHOD AND DEVICE FOR MANAGING MEETING INFORMATION
US16/787,571 US11172521B2 (en) 2017-08-11 2020-02-11 System and method for management of session information in data communication network
US17/729,667 USRE49729E1 (en) 2017-08-11 2022-04-26 Session information management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710683732.9A CN109548137B (zh) 2017-08-11 2017-08-11 会话信息管理方法和装置
CN201710683732.9 2017-08-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/787,571 Continuation US11172521B2 (en) 2017-08-11 2020-02-11 System and method for management of session information in data communication network

Publications (1)

Publication Number Publication Date
WO2019029235A1 true WO2019029235A1 (zh) 2019-02-14

Family

ID=65271119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088903 WO2019029235A1 (zh) 2017-08-11 2018-05-29 会话信息管理方法和装置

Country Status (4)

Country Link
US (2) US11172521B2 (zh)
EP (1) EP3657868A4 (zh)
CN (2) CN109548137B (zh)
WO (1) WO2019029235A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022041923A1 (zh) * 2020-08-27 2022-03-03 中兴通讯股份有限公司 网络切片连接方法、终端及计算机可读存储介质

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11039497B2 (en) * 2017-09-18 2021-06-15 Qualcomm Incorporated User plane based small data service
CN111770207B (zh) * 2019-03-31 2022-02-25 华为技术有限公司 一种获取终端设备互联网协议ip地址方法、设备及系统
CN111769964A (zh) * 2019-04-01 2020-10-13 华为技术有限公司 一种通信方法及装置
EP3967104A4 (en) * 2019-05-06 2023-01-25 Telefonaktiebolaget LM Ericsson (publ) METHOD AND DEVICE FOR SESSION MANAGEMENT
CN111917806B (zh) * 2019-05-07 2022-06-28 华为技术有限公司 通信方法及装置
CN112312359A (zh) * 2019-07-23 2021-02-02 中兴通讯股份有限公司 一种实现信息关联的方法及装置
CN110365796B (zh) * 2019-08-01 2022-04-29 腾讯科技（深圳）有限公司 业务请求处理方法、装置
CN112449350B (zh) * 2019-08-30 2022-11-18 华为技术有限公司 一种利用区块链为终端提供业务的方法、装置及系统
EP4027714A4 (en) * 2019-09-27 2022-09-07 Huawei Technologies Co., Ltd. METHOD, DEVICE AND CONTROL SYSTEM OF AMBR
WO2021138822A1 (zh) * 2020-01-07 2021-07-15 华为技术有限公司 签约信息获取方法及装置
CN113498217B (zh) * 2020-04-03 2023-07-07 华为技术有限公司 一种通信方法和通信装置
CN113541981B (zh) * 2020-04-14 2023-07-14 中国移动通信集团浙江有限公司 网络切片的成员管理方法及系统
CN111511044B (zh) * 2020-04-16 2023-05-05 蓓安科仪（北京）技术有限公司 基于5g网络实现远程医疗的数据通信方法
CN113556793B (zh) * 2020-04-26 2023-03-24 中国电信股份有限公司 non-GBR数据传输控制方法、系统和SMF及用户终端
CN113825251A (zh) * 2020-06-18 2021-12-21 华为技术有限公司 会话建立方法、装置、系统及计算机存储介质
CN113993094B (zh) * 2020-07-27 2022-09-16 华为技术有限公司 通信方法、第一策略控制网元及通信系统
CN114600485B (zh) * 2020-08-13 2023-10-10 华为技术有限公司 签约数据的配置方法及装置
CN114449552B (zh) * 2020-11-06 2023-08-15 中移物联网有限公司 一种切片网络管理方法、装置及电子设备
US11470546B2 (en) * 2020-11-06 2022-10-11 Samsung Electronics Co., Ltd. Method and apparatus for performing communication to use network slice in wireless communication system
KR102487567B1 (ko) * 2020-11-06 2023-01-12 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스의 이용을 위한 통신 방법 및 장치
CN114521004A (zh) * 2020-11-19 2022-05-20 中国移动通信集团有限公司 数据发送方法、装置、设备及存储介质
EP4367944A1 (en) * 2021-07-08 2024-05-15 Qualcomm Incorporated Application function (af) provisioning static internet protocol (ip) addresses to user equipments

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110087789A1 (en) * 2009-10-13 2011-04-14 Nokia Corporation Subscription based network routing tables and enforcement for overlay networks
CN106375987B (zh) * 2015-07-22 2021-08-20 中兴通讯股份有限公司 一种网络切片的选择方法及系统
WO2017063708A1 (en) * 2015-10-15 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for attaching user equipment to a mobile communications network
CN106937362B (zh) * 2015-12-31 2020-04-14 华为技术有限公司 网络切片管理装置和网络切片管理方法
CN113194478A (zh) * 2016-08-10 2021-07-30 日本电气株式会社 无线电接入网络节点、无线电终端、核心网络节点及方法
CN113891432A (zh) * 2016-08-16 2022-01-04 Idac控股公司 Wtru以及wtru中实施的用于无线通信的方法
WO2018070689A1 (ko) * 2016-10-11 2018-04-19 엘지전자(주) 무선 통신 시스템에서의 반영형 서비스 퀄리티 적용 방법 및 이를 위한 장치
CN109964468B (zh) * 2016-11-14 2021-07-09 华为技术有限公司 会话处理方法、装置和系统
CN106982458B (zh) * 2017-03-09 2019-12-17 华为技术有限公司 一种网络切片的选择方法及装置
EP3592033A4 (en) * 2017-03-21 2020-04-22 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
KR102224248B1 (ko) * 2017-06-09 2021-03-08 삼성전자주식회사 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
US10268474B2 (en) * 2017-07-18 2019-04-23 Cisco Technology, Inc. Network slice selection in a mobile network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Network Slice Instance Selection", SA WG2 MEETING #122, S2-175296, 3 July 2017 (2017-07-03), XP051310264 *
HUAWEI ET AL.: "TS 23.501: Slice Selection", SA WG2 MEETING #122, S2-174439, 30 June 2017 (2017-06-30), XP051303290 *
HUAWEI: "Network Slice Instance Selection", SA WG2 MEETING #122, S2-175045, 29 June 2017 (2017-06-29), XP051303743 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022041923A1 (zh) * 2020-08-27 2022-03-03 中兴通讯股份有限公司 网络切片连接方法、终端及计算机可读存储介质

Also Published As

Publication number Publication date
US20200178321A1 (en) 2020-06-04
EP3657868A1 (en) 2020-05-27
CN109548137A (zh) 2019-03-29
CN114845381A (zh) 2022-08-02
CN109548137B (zh) 2022-04-22
USRE49729E1 (en) 2023-11-14
US11172521B2 (en) 2021-11-09
EP3657868A4 (en) 2020-08-12

Similar Documents

Publication Publication Date Title
USRE49729E1 (en) Session information management method and apparatus
US11381956B2 (en) Obtaining of UE policy
RU2731121C1 (ru) Способ регистрации, способ установки сеанса, оконечное устройство и объект функции управления доступом и мобильностью
KR102092495B1 (ko) 무선 단말, 무선국, 및 이들의 방법
WO2019137142A1 (zh) 策略相关的通信方法、装置和系统
CN109600802B (zh) 数据传输方法、相关设备及系统
CN110121897B (zh) 一种会话建立的方法及设备
WO2019001204A1 (zh) 切片选择方法和装置
WO2019174505A1 (zh) 一种基于网络切片的通信方法及装置
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
WO2019196811A1 (zh) 通信方法和相关装置
WO2019033796A1 (zh) 会话处理方法及相关设备
US20220191765A1 (en) Communication method, apparatus, and system
WO2017147772A1 (zh) 一种消息传输方法及核心网接口设备
WO2020048469A1 (zh) 一种通信的方法及装置
EP3703420B1 (en) Session context processing method, network elements, and terminal device
WO2020073802A1 (zh) 一种鉴权的方法及装置
JP2021503199A (ja) 通信端末、接続を要求する方法、ネットワーク構成要素および通信端末にサービスを提供する方法
CN109474954B (zh) 一种会话建立方法及装置
US11343724B2 (en) User equipment context management method, apparatus, and device
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2022021355A1 (zh) 会话建立方法、装置、设备及存储介质
CN109150752B (zh) 缓存控制方法、网元及控制器
JP7485793B2 (ja) スライスアクセス方法、装置、及びシステム
WO2023280000A1 (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: 18844446

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018844446

Country of ref document: EP

Effective date: 20200219