Nothing Special   »   [go: up one dir, main page]

WO2018086123A1 - 会话处理方法、装置和系统 - Google Patents

会话处理方法、装置和系统 Download PDF

Info

Publication number
WO2018086123A1
WO2018086123A1 PCT/CN2016/105750 CN2016105750W WO2018086123A1 WO 2018086123 A1 WO2018086123 A1 WO 2018086123A1 CN 2016105750 W CN2016105750 W CN 2016105750W WO 2018086123 A1 WO2018086123 A1 WO 2018086123A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
type information
response message
service
type
Prior art date
Application number
PCT/CN2016/105750
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 PCT/CN2016/105750 priority Critical patent/WO2018086123A1/zh
Priority to CN201680090770.7A priority patent/CN109964468B/zh
Priority to EP16921082.0A priority patent/EP3515031B1/en
Publication of WO2018086123A1 publication Critical patent/WO2018086123A1/zh
Priority to US16/412,071 priority patent/US10834208B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a session processing method, apparatus, and system.
  • Network slicing is a new type of network and business model that can be customized to better meet the individual needs of consumers and businesses.
  • the user equipment User Equipment, UE
  • the user equipment can access multiple slices of different types, and simultaneously use different services provided by multiple slices.
  • the network side When the network side receives the session request from the UE, the network side establishes a session according to the information carried in the session request.
  • a session can serve different businesses.
  • the UE initiates a session establishment process, and the network side determines whether to reuse an already established session or establish a new session, thus increasing the UE and the network side. Signaling interaction.
  • the present application describes a session processing method, apparatus and system.
  • an embodiment of the present application provides a session processing method, where the method includes: the user equipment UE acquires session type information.
  • the session type information is used to indicate the type of the first session.
  • the UE determines, according to the session type information, whether it needs to initiate the first service. Create a request.
  • the UE may determine whether to reuse the established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the session type information includes a name DNN of the data network supported by the first session, the session type information further including a type of the service supported by the first session and a slice supporting the first session. At least one of the types.
  • the method further includes: the UE acquiring an identifier of the first session.
  • the session type information includes a type of a session supported by a slice in which the shared control plane network function CCNF device attached to the UE is supported, where a slice of the CCNF device to which the UE is attached is supported by a slice.
  • the session includes the first session.
  • the UE determines, according to the session type information, whether to initiate a session establishment request for the first service, including: the UE according to the pre-configured first application and the first application. a name of the accessed data network DNN, and a correspondence between the type of the first service or a slice type required to support the first service, and determining, according to the session type information, whether there is an established session support
  • the user equipment UE acquiring the session type information includes: the UE acquiring the session type information in a session establishment process; or the UE acquiring the session type information in an initial attach process; or The UE acquires the session type information in a tracking area update process.
  • the acquiring, by the user equipment, the session type information includes: the UE receiving a setup session response message from the session management function SMF device, where the setup session response message carries The session type information; or the UE receives an attach accept message from a shared control plane network function CCNF device, the attach accept message carries the session type information; or the UE receives a tracking area update response message from a CCNF device, The tracking area update response message carries the session type information.
  • the embodiment of the present application provides a session processing method, including: a first session management function SMF device receives a request message for requesting to establish a first session, and sends a first setup session response message.
  • the first setup session response message carries session type information.
  • the session type information is used to indicate the type of the first session, and the session type information is used to determine whether a session establishment request is initiated for the first service triggered by the first application.
  • the UE may determine whether to reuse the established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the session type information includes a name DNN of the data network accessed by the first session, the session type information further includes a type of the service supported by the first session, and supports the first session. At least one of the types of slices.
  • the first setup session response message further includes an identification of the first session.
  • the first SMF device sends a first setup session response message, including: the first SMF device sends the first setup session response message to the UE.
  • the first SMF device sends the first setup session response message to the UE.
  • the present application is also applicable to roaming scenarios. If the first SMF device is an SMF device that belongs to the public land mobile network, the first SMF device sends a first setup session response message, including: the first SMF device sends to the SMF device that visits the public land mobile network. The first establishing a session response message.
  • the method further includes: the first SMF device moving from the home public land
  • the SMF device of the network receives a second setup session response message, the second setup session response message carries the DNN accessed by the first session, and a type of service supported by the first session and a slice supporting the first session At least one of the types; the first SMF device obtains the session type information according to a type of service supported by the first SMF device and the second setup session response message.
  • the embodiment of the present application provides a session processing method, including: a shared control plane network function CCNF device receives a request message, and after receiving the request message, sends a response message to the user equipment UE.
  • the response message carries session type information.
  • the session type information is used to indicate the type of the session supported by the slice in which the CCNF is located, and the session type information is used to determine whether a session establishment request is initiated for the first service triggered by the first application.
  • the UE may determine whether to reuse the established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the session type information includes a name DNN of a data network accessed by the session, the session type information further including a type of a service supported by the session and a type of a slice supporting the session. At least one.
  • the request message is an initial attach request message, and the response message is an initial attach accept message; or the request message is a location area update request message, and the response message is a location area update response message.
  • an embodiment of the present application provides a UE, where the UE has the foregoing method in the design.
  • the function of UE behavior can be implemented by hardware, and the structure of the UE includes a receiver and a processor.
  • the corresponding software implementation can also be performed by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • an embodiment of the present application provides a CCNF device, which may include a receiver and a transmitter, for performing the communication function of the CCNF device in the foregoing aspect.
  • an embodiment of the present application provides an SMF device, which may include a receiver and a transmitter, for performing the communication function of the SMF device in the above aspect.
  • an embodiment of the present application provides a communication system, including the CCNF device and the SMF device described in the foregoing aspects.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the UE, which includes a program designed to perform the above aspects.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the CCNF device, which includes a program designed to perform the above aspects.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the SMF device, which includes a program designed to perform the above aspects.
  • the user equipment UE acquires session type information.
  • the session type information is used to indicate the type of the first session.
  • the UE determines, according to the session type information, whether a session establishment request needs to be initiated for the first service. Before initiating a session establishment request, the UE can determine whether to reuse an already established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a session processing method according to an embodiment of the present application.
  • 3A-3D are schematic diagrams of interaction of a session processing method according to an embodiment of the present application.
  • FIG. 4 is still another schematic flowchart of a session processing method according to an embodiment of the present disclosure.
  • FIG. 5 is another schematic flowchart of a session processing method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a UE according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a CCNF device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an SMF device according to an embodiment of the present disclosure.
  • FIG. 9 is still another schematic structural diagram of a UE according to an embodiment of the present application.
  • FIG. 10 is still another schematic structural diagram of a CCNF device according to an embodiment of the present application.
  • FIG. 11 is still another schematic structural diagram of an SMF device according to an embodiment of the present application.
  • User equipment (UE) involved in the present application may include various A wireless communication capable handheld device, an in-vehicle device, a wearable device, a computing device, or other processing device connected to a wireless modem.
  • the UE may also be referred to as a mobile station (MS), a terminal, a terminal equipment, and may also include a subscriber unit, a cellular phone, and a smart phone.
  • Phone wireless data card
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • the access device involved in the embodiment of the present application is a device deployed in a radio access network to provide a wireless communication function for the UE.
  • Access devices may include various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, and the like.
  • the name of the access device function may be different, for example, in an LTE system, called an evolved Node B (eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • eNB evolved Node B
  • 3G 3rd generation
  • the network slice instance involved in the embodiment of the present application is used to flexibly provide one or more network services according to the requirements of the slice requesting party.
  • the network slicing technology divides a physical network into multiple network slicing instances. Each network slicing instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario. By customizing the network and management, we can better meet the individual needs of consumers and businesses, and realize the sharing of multiple services.
  • a "network slice" can be thought of as an instantiated core network architecture.
  • Examples of "network slicing" that are currently considered by the industry include Mobile Broadband, multimedia, Massive Machine Type Communication, and Critical Machine Type Communication.
  • the network slice instance mentioned above is simply referred to as a slice.
  • the Common Control Plane Network Function device in the embodiment of the present application is a control plane device shared by multiple network slice instances, and is responsible for mobility management, forwarding path management, and network protocol in the mobile communication network. (Internet Protocol, IP) address assigned device.
  • the control plane device may be, but not limited to, a Mobility Management Entity (MME) in the core network, an S-GW control plane or a P-GW control plane, or may be an MME, an S-GW control plane, and a P-GW control. Any network element in the plane is fused to form a control plane network element.
  • MME Mobility Management Entity
  • the session management function (SMF) device involved in the embodiment of the present application is a device for managing a session in a network slice instance.
  • NAS-Non Access Signalling non-access network signaling
  • the main function is to allocate the UE IP address, select the user plane function, and execute the session-related policy and charging rules. It is the fusion of the session management related functions, the SGW control plane and the PGW control plane functions in the MME function.
  • UP device also referred to as a forwarding plane device, a user plane network element, a forwarding plane network element, a core network user plane network element, or a core network forwarding plane network element
  • the user plane device may be, but is not limited to, a physical forwarding plane device such as an S-GW, a P-GW, a router, a switch, a Software Defined Network (SDN) switch, or an S-GW forwarding plane or P. - GW forwarding plane and other virtual forwarding plane network elements.
  • SDN Software Defined Network
  • the data network (DN) involved in the embodiment of the present application is a network in which the UE finally establishes a connection and accesses.
  • the DN may be, but not limited to, a Packet Data Network (PDN), such as the Internet, a Virtual Private Network (VPN), an IP Multi-media Service (IMS) network, or Wireless Application Protocol (WAP) network provided by the operator.
  • PDN Packet Data Network
  • VPN Virtual Private Network
  • IMS IP Multi-media Service
  • WAP Wireless Application Protocol
  • FIG. 1 is a schematic diagram of a communication system 100 provided by the present application.
  • the UE 102 can simultaneously access multiple slices (eg, at least two slices of slices A, B, C).
  • the slices A, B, and C share the CCNF device 108, and the shared CCNF device may be a combination of multiple shared control plane devices.
  • a slice selection function (SSF, also referred to as a network slice selection function NSSF) device 106 is used to select slices to provide information to the access device 104 for routing to the corresponding CCNF device 108.
  • SSF also referred to as a network slice selection function NSSF
  • a slice also includes the SMF device and UP unique to the slice.
  • slice A has SMF devices 1, UP1 and UP2; slice B has SMF devices 2, UP3 and UP4; slice C has SMF devices 3, UP5 and UP6.
  • the SSF or NSSF device may also be a sub-device of the shared CCNF device.
  • the present invention assumes that the SSF or NSSF device is a device independent of the CCNF device, and the present invention is equally applicable to SSF or NSSF.
  • the device acts as a child device that shares a CCNF device.
  • the selected SMF device may carry information according to the session request message, such as a service type or a slice type, and a data network name (data network name, DNN), choose the appropriate UP, establish a session.
  • An UP can correspond to one or more DNs, and a DN can also establish a session with multiple UPs. Therefore, a session can serve different DNs for different services. Therefore, when the UE receives a new application request message, it may need to establish a new session, or may provide services for the service through an existing session.
  • the UE may determine whether to reuse an already established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the communication system 100 may be various radio access technology (RAT) systems, such as a code division multiple access (CDMA) system, time division multiple access (time division). Multiple access (TDMA) system, frequency division multiple access (FDMA) system, orthogonal frequency-division multiple access (OFDMA) system, single carrier frequency division multiple access (single carrier FDMA, SC-FDMA) system or other system.
  • RAT radio access technology
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • a CDMA system can implement wireless technologies such as universal terrestrial radio access (UTRA), CDMA2000, and the like.
  • UTRA may include wideband CDMA (WCDMA) technology and other CDMA variant technologies.
  • CDMA2000 can cover the interim standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards.
  • the TDMA system can implement a wireless technology such as a global system for mobile communication (GSM).
  • GSM global system for mobile communication
  • OFDMA system can be implemented Wireless technologies such as evolved universal wireless terrestrial access (evolved UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA.
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • the various versions of 3GPP in long term evolution (LTE) and LTE-based evolution are new versions of UMTS that use E-UTRA.
  • the communication system 100 can also be applied to future-oriented communication technologies such as a 4.5G system or an NR (Next Radio) system.
  • FIG. 2 is a flowchart of a session processing method according to an embodiment of the present application. As shown in Figure 2, the method includes:
  • step 202 the UE acquires session type information.
  • the session type information is used to indicate the type of the first session.
  • the session type information includes a name DNN of the data network supported by the first session, and the session type information further includes at least one of a type of the service supported by the first session and a type of the slice supporting the first session.
  • the first session can support multiple services.
  • the following describes the session type information including the DNN and the service type supported by the first session as an example.
  • the session type information may have a similar format, and the present invention is not here. limit.
  • the UE may obtain session type information in a session establishment process, where the first session is a session established through the session establishment process; or the UE may also update in an initial attach process or a tracking area.
  • the session type information (TAU) process obtains the session type information, where the session type information includes the type of the session supported by the slice where the CCNF device attached to the UE is located, where the slice of the CCNF device to which the UE is attached is supported by the slice.
  • the session includes the first session. How the UE obtains session type information will be further described in conjunction with Figures 3A-3D.
  • the UE After the UE establishes the first session, it saves the session information of the session, as shown in Table 1:
  • the UE can access the service of the service type 1 by accessing the DN1 through the slice A; the service of the service type 2 can be obtained by accessing the DN 2 through the slice A; and the service of the service type 2 can be obtained by accessing the DN 3 through the slice A.
  • the UE can access the service of the service type 3 by accessing the DN1 through the slice B, and can also access the service of the service type 4 by accessing the DN2 through the slice B.
  • Table 1 holds the 3 sessions that the UE has established, and the type of service and DNN that triggers each session establishment.
  • the method further includes: acquiring, by the UE, an identifier of the first session.
  • the identity of the first session is available for the first session.
  • the session type information also includes an identification of the first session; or a message for communicating session type information (such as the setup session response message in FIGS. 3A/3D) also carries a cell indicating the identity of the first session.
  • the session type information may have the format as shown in Table 2:
  • the session type information may further include an identifier of the CCNF device attached to the UE or a network slice identifier (NS-ID), as shown in Table 3 and Table 3'.
  • the session type information may be used to indicate the type of the session supported by the slice supporting the CCNF device, as shown in Table 3; when the session type information includes the identifier of the slice, the session The type information may be used to indicate the type of the session supported by the specific certain slice controlled by the CCNF device.
  • the slice where the CCNF device attached by the UE is located includes slices 1, 2 and 3, and the corresponding slice identifiers are respectively NS-ID 1, NS-ID 2 and NS-ID 3.
  • step 204 when the first application triggers the first service, the UE determines, according to the session type information, whether a session establishment request needs to be initiated for the first service.
  • different applications correspond to different DNNs and business types.
  • the name of the data network accessed by the first application and the first application, and the correspondence between the type of the first service or the slice type required to support the first service may be pre-configured in the UE.
  • the corresponding relationship in the UE is as shown in Table 4:
  • the service type is Voice over Internet Protocol (VoIP), and its DNN is a carrier network name.
  • VoIP Voice over Internet Protocol
  • the service type is MBB
  • its DNN is the domain name of Tencent.
  • the business type is the internal MBB of the enterprise
  • the DNN is the internal network domain name of the enterprise.
  • V2X vehicle-to-everything
  • its DNN can be a BMW network domain name. Therefore, the pre-configured correspondence within the UE may have the format of Table 5:
  • the UE may determine, according to the pre-configured correspondence and the session type information, whether the established session supports the type of the first service and the DNN accessed by the first application. If there is an already established session capable of supporting the type of the first service and the DNN accessed by the first application, the existing session is reused to access the DNN for the first application; if not, the UE needs to initiate a session establishment request for the first service.
  • the UE determines, according to the session type information of Table 1 (or Table 2, Table 3) and the pre-configuration correspondence relationship of Table 4, that the available Some sessions access DNN1 for application 1 without having to initiate a new session establishment request.
  • the UE may determine, according to the session type information, whether to reuse the established session or establish a new session. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the UE may obtain session type information in a session establishment process, and the session establishment process is used to establish a first session.
  • the method includes:
  • the UE 102 sends a create session request message to the access device 104.
  • the setup session request message is forwarded to the CCNF device 108.
  • the establishing a session request message carries a network slice and SM Network Slice Selection Assistance Information (SM NSSAI) and requests the The DNN of the session's business to access.
  • SM NSSAI is at least one of a type of service requested by the UE 102 or a slice type providing the service.
  • step 302 the CCNF device 108 transmits a slice selection request message carrying the SM NSSAI to the SSF device 106 according to the received setup session request message.
  • step 303 after receiving the slice selection request message, the SSF device 106 selects a slice according to the SM NSSAI, and acquires an identifier of the slice, such as an NS-ID.
  • step 304 the SSF device 106 sends a slice selection response message carrying the NS-ID to the CCNF device 108.
  • step 302 to step 304 are optional steps. If the CCNF has obtained the correspondence between the NSSAI and the slice identifier by means of pre-configuration, etc., steps 302 and 304 need not be performed.
  • CCNF device 108 determines an SMF device (e.g., SMF device 1 in Figure 1).
  • step 306 the CCNF device 108 sends a setup session request message to the determined SMF device, the setup session request message carrying the DNN that the UE 102 wants to access through the first session to be established.
  • step 307 after receiving the setup session request message, the SMF device selects the user plane UP according to the DNN.
  • UP is established.
  • a user plane belonging to the home public land mobile network (HPLMN) side is established in a non-roaming scenario.
  • HPLMN home public land mobile network
  • the SMF device acquires session type information and sends a create session response message carrying the session type information to the UE 102.
  • the session type information includes at least one of the DNNs supported by the first session, and at least one of a type of the service supported by the first session and a type of the slice supporting the first session.
  • the SMF device sends the setup session response message to the CCNF device 106.
  • the CCNF device 106 forwards the setup session response message to the access device 104, and the access device 104 forwards the setup session response message to the UE 102.
  • the session type information in the form of Table 2 can be obtained and saved from the setup session response message. Therefore, after the UE obtains the session type information in the session establishment process, when the new first application triggers the first service, the UE may determine whether to reuse the established session or establish a new one according to the session type information before initiating the session establishment request. Conversation. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • Table 2 and Table 4 are saved on the UE side.
  • the network side establishes the session identifier as “session identifier 1” through the process described in steps 301-309. Session, and the UE acquires session type information of the session identifier as "session ID 1.”
  • a new application "Application 2" of the UE initiates a service request, and the UE determines, according to the pre-configuration information of Table 4, that the application requests access to the DNN 2 to obtain the service A of the service type 2, and the UE queries the service type information list. Since the information of the session identifier 1 is included in the table 2, the UE finds that the existing established session cannot match the requirement of the application 2, so the UE sends a new session establishment request to the network side, and the network side sends the session according to the UE. The session is established, and the session identifier is set to "session ID 2", and the session establishment response message returned to the UE carries the session type information of "session identifier 2", that is, the second row and the third row in Table 2.
  • the UE determines, according to the pre-configuration information of Table 4, that the application requests access to the DNN 3 to obtain the service B of the service type 2, and the UE queries the service type information list and finds the "session identifier.
  • the 2" session can support the service requested by the application, and the UE determines that the service A and the service B can share the same IP, and the UE directly sends and receives the data packet of the service B using the session identifier of the session identifier 2.
  • the UE can continuously support the session and the service according to the service support.
  • the session and service continuity mode (SSC) mode further determines the requirements of the service for the IP address.
  • SSC session and service continuity mode
  • the UE may obtain session type information in an initial attach procedure.
  • the method includes:
  • the UE 102 initiates an initial attach request message to the access device 104 to request access to the network.
  • the initial attach request message includes an International Mobile Subscriber Identity (IMSI) for indicating the UE 102.
  • IMSI International Mobile Subscriber Identity
  • step 312 after receiving the initial attach request message, the access device 104 sends a slice selection request message carrying the IMSI to the SSF device 106, and the slice selection request message is used to request the SSF device 106 to select the CCNF device for the UE 102 (eg, CCNF device 108).
  • the access device 104 sends a slice selection request message carrying the IMSI to the SSF device 106, and the slice selection request message is used to request the SSF device 106 to select the CCNF device for the UE 102 (eg, CCNF device 108).
  • the SSF device 106 sends a subscription information request message carrying the IMSI to the subscriber data management (SDM) device, where the subscription information request message is used to request the subscription of the UE 102. information.
  • SDM subscriber data management
  • the SDM device acquires the subscription NSSAI of the UE according to the IMSI.
  • the contracted NSSAI includes one or a group of service types or slice types that the UE 102 subscribes to need to be provided by the network.
  • the contracted NSSAI also includes a signed DNN that requires one or a set of service types or slice types supported by the network.
  • the SSF device 106 selects a CCNF device (e.g., CCNF device 108) based on the contracted NSSAI.
  • a CCNF device e.g., CCNF device 10
  • the SSF device sends a slice selection response message carrying information capable of identifying the CCNF to the access device 104, and the slice selection response message further includes an NSSAI (Accepted NSSAI) allowed by the network.
  • NSSAI Acceptted NSSAI
  • the access device 104 upon receiving the slice selection response message, transmits an initial attach request message to the CCNF device 108.
  • the initial attach request message may carry the IMSI described above.
  • step 318 after receiving the initial attach request message, the CCNF device 108 interacts with the SDM device to implement authentication of the UE.
  • the CCNF device 108 transmits an initial attach accept message carrying the session type information to the UE 102.
  • the session type information includes one or a group of session types supported by the slice in which the CCNF is located, and includes at least a DNN supported by the first session, and a type of the service supported by the first session and a type of the slice supporting the first session. At least one of them.
  • the session type information further includes an identifier of the CCNF device or an identifier of a slice supported by the CCNF.
  • the CCNF device 108 transmits the initial attach accept message to the access device 104, and the access device 104 forwards the initial attach accept message to the UE 102 upon receipt.
  • the session type information in the form of, for example, Table 3 can be obtained and saved from the initial attach accept message. Therefore, after the UE obtains the session type information in the initial attach process, when the new first application triggers the first service, the UE may determine whether to reuse the established session or establish a new one according to the session type information before initiating the session establishment request. Conversation. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the UE side holds Table 1, Table 3 or Table 3', and Table 4.
  • the CCNF device 108 sends an initial attach accept message carrying session type information to the UE 102, where the session type information includes a list of session types supported by all slices in which the CCNF device 108 is located, such as "Session Type 1" supports Service Type 1 and can access DDN1; "Session Type 2" supports Service Type 2 and can access DDN2 and DNN3.
  • Session Type 1 supports Service Type 1 and can access DDN1
  • Session Type 2 supports Service Type 2 and can access DDN2 and DNN3.
  • the UE determines, according to the pre-configuration information of Table 4, that the application requests access to the DNN 3 to obtain the service B of the service type 2, and the UE queries the service type information list 3 and finds "
  • the session type 2" can support both the “service type 2+DNN2" and the “service type 2+DNN3”; and the UE queries through the table 1 that there is already session support "service type 2+DNN2", and the UE combines Table 1 and Table 3,
  • the session of the session identification 2 can be found to support the service requested by the application, and the UE determines that the service 2 can share the same IP with the service 1, and the UE directly uses the session identifier to send and receive data of the service for the session of the session identifier 2. package.
  • the UE can further determine the service request for the IP address according to the “session and service continuity mode (SSC) mode supported by the service.
  • SSC session and service continuity mode
  • the UE may obtain session type information in the TAU procedure.
  • the old CCNF device before the location area update is the CCNF device 108'
  • the new CCNF device after the location area update is the CCNF device 108.
  • the method includes:
  • the UE 102 initiates a TAU Request message to the access device 104 to request a tracking area update.
  • the TAU request message includes a temporary identification (temp ID) for indicating the UE 102 and an NSSAI (Accepted NSSAI) allowed by the network, and the Accepted NSSAI is used as the access device 104 to determine the new CCNF device.
  • temp ID temporary identification
  • NSSAI Accepted NSSAI
  • step 322 after receiving the TAU request message, the access device 104 determines the new CCNF device according to the Accepted NSSAI information.
  • step 323 the access device 104 forwards the TAU request message to the new CCNF device 108.
  • step 324 upon receipt of the TAU Request message, the new CCNF device 108 obtains the context of the UE 102 from the old CCNF device 108'.
  • CCNF device 108 transmits a TAU response message carrying session type information to UE 102.
  • the session type information includes one or a group of session types supported by the slice in which the CCNF is located, and includes at least a DNN supported by the first session, and a type of the service supported by the first session and a type of the slice supporting the first session. At least one of them.
  • the session type information further includes an identifier of the CCNF device or an identifier of a slice supported by the CCNF.
  • the CCNF device 108 sends the TAU response message to the access device 104, and the access device 104 receives the TAU response message after receiving it.
  • the session type information in the form of Table 3 or Table 3' can be obtained and saved from the TAU response message. Therefore, after the UE obtains the session type information in the TAU process, when the new first application triggers the first service, the UE may determine, according to the session type information, whether to reuse the established session or establish a new session. . For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • the example of FIG. 3A can be applied to a session establishment process in a non-roaming scenario.
  • session type information may be obtained in the session establishment process according to the method of FIG. 3D.
  • the session establishment process is used to establish a first session.
  • visiting a public land mobile network (vPLMN) includes visiting a CCNF device (vCCNF), visiting a SSF device (vSSF), visiting a SMF device (vSMF), and visiting a user plane (vUP).
  • the home PLMN (hPLMN) includes a home SMF device (hSMF) and a home user plane (hUP).
  • the method includes:
  • the UE 102 sends a setup session request message to the access device 104.
  • the setup session request message is forwarded to the vCCNF.
  • the establishment session request message carries a network slice and SM Network Slice Selection Assistance Information (SM NSSAI) and a DNN to which the service requesting the session is to be accessed.
  • SM NSSAI is at least one of a type of service requested by the UE 102 or a slice type providing the service.
  • the SM NSSAI is at least one of a type of service requested by the UE 102 or a slice type providing the service.
  • step 332 the vCCNF sends a slice selection request message carrying the SM NSSAI to the vSSF device according to the received setup session request message.
  • the vSSF selects a slice according to the NSSAI to obtain an identifier of the slice.
  • the identity of the slice includes the identity vNS-ID of the slice of the vPLMN and the identity hNS-ID of the slice of the hPLMN.
  • the vSSF may acquire the identity hNS-ID of the slice of the hPLMN selected by the hPLMN from the SSF of the vPLMN.
  • step 334 the vSSF sends a slice selection response message carrying the slice identification to the vCCNF.
  • the vCCNF determines the vSMF based on the vNS-ID.
  • the vCCNF sends a setup session request message to the determined vSMF.
  • the setup session request message carries the DNN and the hNS-ID that the UE 102 wants to access through the first session to be established.
  • the setup session request message is used to request to establish a session between the vSMF and the vUP.
  • the vSMF selects a vUP according to the DNN and the hNS-ID, and establishes a session (such as the first session) between the vSMF and the vUP on the vPLMN side.
  • Steps 331 to 337 may refer to the description of steps 301 to 308 in FIG. 3A, and details are not described herein again.
  • step 338 the vSMF sends a setup session request message to the hSMF, the setup session request message carrying the DNN that the session requested by the UE wants to access.
  • step 339 after receiving the session establishment request message, the hSMF selects hUP according to the DNN to establish hSMF.
  • the hSMF acquires at least one of the type of the service supported by the session on the hPLMN side and the type of the slice supporting the session of the hPLMN side, and transmits the above session type information to the vSMF by establishing a session response message.
  • the establish session response message in step 340 can also include a DNN.
  • the session type information on the hPLMN side included in the establishment session response message may have the format of Table 2.
  • the vSMF determines the final session type information according to the received session type information on the hPLMN side and the service type information supported by the session on the vPLMN side.
  • the session type information on the hPLMN side may have the format of Table 2, the service type information supported by the session on the vPLMN side is as shown in Table 6, and the session identifier 1 is the identifier of the session on the vPLMN side, and the callback supports the service type 1 and the service type. 4. Therefore, combining the information of Table 2 and Table 6, it can be seen that the service type 1 supported by the hPLMN side can also be supported on the vPLMN side, and the service type information supported by the established session determined by the final vSMF can be as shown in Table 7.
  • the vSMF sends a setup session response message carrying the session type information to the UE 102.
  • the session type information includes at least a DNN supported by the first session (a session on the vPLMN side), and at least one of a type of the service supported by the first session and a type of the slice supporting the first session.
  • the vSMF sends the setup session response message to the vCCNF, and after receiving the vCCNF, the vCCNF forwards the setup session response message to the access device 104, and the access device 104 forwards the setup session response to the UE 102. interest.
  • the session type information in the form of, for example, Table 7 can be obtained and saved from the setup session response message. Therefore, after the UE obtains the session type information in the session establishment process, when the new first application triggers the first service, the UE may determine whether to reuse the established session or establish a new one according to the session type information before initiating the session establishment request. Conversation. For the service that can re-establish the established session, no new session is required, the signaling interaction between the UE and the network side is reduced, and the network load is reduced.
  • FIG. 4 is a schematic flowchart of a session processing method according to an embodiment of the present application.
  • the method can be performed by the SMF device of Figure 3A, or by the vSMF device or the hSMF device of Figure 3D. As shown in FIG. 4, the method includes:
  • the first SMF device receives a request message for requesting to establish a first session.
  • the first SMF device sends a first setup session response message, where the first setup session response message carries session type information, where the session type information is used to indicate the type of the first session, the session The type information is used to determine whether a session establishment request needs to be initiated for the first service triggered by the first application.
  • step 404 includes the first SMF device transmitting the first setup session response message to an SMF device that is visiting the public land mobile network.
  • the first SMF device may be a vSMF device or an hSMF device. If the first SMF device is an hSMF device, step 404 includes transmitting the first setup session response message to the vSMF device. If the first SMF device is a vSMF device, before the step 404, the method further includes: the first SMF device receiving a second setup session response message from the hSMF device, according to the first SMF The type of the service supported by the device and the second session establishment response message obtain the session type information. For the step, reference may be made to steps 341 and 342 in FIG. 3D, and details are not described herein again.
  • FIG. 5 is a schematic flowchart of a session processing method according to an embodiment of the present application. The method can be performed by the CCNF device of Figure 3B or Figure 3C. As shown in FIG. 5, the method includes:
  • step 502 the CCNF device receives the request message.
  • the CCNF device sends a response message to the user equipment UE, where the response message carries session type information, where the session type information is used to indicate a session supported by the slice where the CCNF is located.
  • the session type information is used to determine whether a session establishment request is initiated for the first service triggered by the first application.
  • the request message is an initial attach request message
  • the response message is an initial attach accept message.
  • the request message is a location area update request message
  • the response message is a location area update response message.
  • descriptions of steps 323 and 325 in FIG. 3C are omitted, and details are not described herein again.
  • the session processing method provided by the embodiment of the present application is introduced from the perspective of the interaction between the network elements and the network elements.
  • each network element such as a UE, an SMF device, a CCNF device, etc.
  • each network element includes hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. Professionals can use different methods to implement the description for each specific application. Functionality, but such implementation should not be considered beyond the scope of this application.
  • the UE 102 can include a receiving unit 602, a processing unit 604, as shown in FIG.
  • the receiving unit 602 can be used to perform step 202 in FIG. 2, step 309 in FIG. 3A, step 319 in FIG. 3B, step 325 in FIG. 3C, or step 342 in FIG. 3D.
  • Processing unit 604 can be used to perform step 204 in FIG.
  • the UE 102 may further include a sending unit 606, configured to send various messages to other network elements, for example, step 301 in FIG. 3A, step 311 in FIG. 3B, step 321 in FIG. 3C, or in FIG. 3D Step 331.
  • the CCNF device 108 can include a receiving unit 702 and a transmitting unit 704, as shown in FIG.
  • the receiving unit 702 is configured to receive a request message (refer to step 502).
  • the sending unit 704 is configured to send a response message carrying the session type information to the UE (refer to step 504).
  • receiving unit 702 can be used to perform steps 301, 304, 309 in FIG. 3A, step 317 in FIG. 3B, step 323 in FIG. 3C, or steps 331, 334 in FIG. 3D.
  • the transmitting unit 704 can be used to perform steps 302, 306, 309, 342 in FIG. 3A, step 319 in FIG. 3B, step 325 in FIG. 3C, or steps 332, 336, 342 in FIG. 3D.
  • the SMF device 800 can include a receiving unit 802 and a transmitting unit 804, as shown in FIG.
  • the receiving unit 802 is configured to receive a request message for requesting to establish a first session (refer to step 402).
  • the sending unit 804 is configured to send a first setup session response message carrying the session type information (refer to step 404).
  • receiving unit 802 can be used to perform step 306 in FIG. 3A, steps 312, 314 in FIG. 3B, or steps 336, 340 in FIG. 3D.
  • the transmitting unit 804 can be used to perform step 309 in FIG. 3A, steps 313, 316 in FIG. 3B, or step 342 in FIG. 3D.
  • Fig. 9 shows a simplified schematic diagram of one possible design structure of the UE involved in the above embodiment.
  • the UE includes a transceiver 901, a controller/processor 902, and may also include a memory 903 and a modem processor 904.
  • the transceiver 901 includes a receiver for performing step 202 in FIG. 2;
  • the processor 902 is configured to perform step 204 in FIG.
  • the transceiver 901 conditions (e.g., analog conversion, filtering, amplifying, upconverting, etc.) the output samples and generates an uplink signal that is transmitted via an antenna to the access device 104 described in the above embodiments.
  • the antenna receives the downlink signal transmitted by the access device 104 in the above embodiment.
  • Transceiver 901 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples.
  • encoder 9041 receives the traffic data and signaling messages to be transmitted on the uplink and processes (e.g., formats, codes, and interleaves) the traffic data and signaling messages.
  • Modulator 9042 further processes (e.g., symbol maps and modulates) the encoded traffic data and signaling messages and provides output samples.
  • Demodulator 9044 processes (e.g., demodulates) the input samples and provides symbol estimates.
  • Decoder 9043 processes (e.g., deinterleaves and decodes) the symbol estimate and provides decoded data and signaling messages that are sent to the UE.
  • Encoder 9041, modulator 9042, demodulator 9044, and decoder 9043 may be implemented by a composite modem processor 904. These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems).
  • the controller/processor 902 performs control management on the actions of the UE for performing the processing performed by the UE in the above embodiment.
  • the controller/processor 902 can be configured to determine, according to the session type information, whether to initiate a session establishment request for the first service when the first application triggers the first service.
  • the memory 903 is used to store program codes and data for the UE.
  • Fig. 10 shows a simplified schematic diagram of one possible design structure of the CCNF device involved in the above embodiment.
  • the CCNF device may be the CCNF device 108 of FIG.
  • the CCNF device may include a controller/processor 1001, a memory 1002, and a communication unit 1003.
  • the controller/processor 1001 can be used to coordinate resource management and configuration between multiple slices.
  • the memory 1002 can be used for storage control The program code and data of the node.
  • the communication unit 1006 is configured to support the CCNF device to communicate with other network elements.
  • communication unit 1006 includes a receiver and a transmitter.
  • the receiver is configured to support the CCNF device to perform steps 301, 304, 309 in FIG. 3A, step 317 in FIG.
  • the transmitter is configured to support the CCNF device to perform steps 302, 306, 309, 342 in FIG. 3A, step 319 in FIG. 3B, step 325 in FIG. 3C, or steps 332, 336, 342 in FIG. 3D.
  • Fig. 11 shows a simplified schematic diagram of one possible design structure of the SMF device involved in the above embodiment.
  • the SMF device may include a controller/processor 1101, a memory 1102, and a communication unit 1103.
  • the controller/processor 1101 can be used to coordinate resource management and configuration between multiple slices.
  • Memory 1102 can be used to store program code and data for the control node.
  • the communication unit 1106 is configured to support the SMF device to communicate with other network elements.
  • communication unit 1106 includes a receiver and a transmitter.
  • the receiver is configured to support the SMF device to perform step 306 in FIG. 3A, steps 312, 314 in FIG. 3B, or steps 336, 340 in FIG. 3D.
  • the transmitter is configured to support the SMF device to perform step 309 in FIG. 3A, steps 313, 316 in FIG. 3B, or step 342 in FIG. 3D.
  • the controller/processor for performing the above-described UE, CCNF device or SMF device 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 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 present application also discloses a communication system including the CCNF device and the SMF device as described above.
  • the steps of the method or algorithm described in connection with the disclosure of the present application may be implemented in a hardware manner. Now, it can also be implemented by means of 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 the user equipment.
  • the processor and the storage medium may also reside as discrete components in the user equipment.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请涉及无线通信技术领域，提供了一种会话处理方法，该方法公开了：用户设备UE获取会话类型信息。该会话类型信息用于指示第一会话的类型。当第一应用触发第一业务时，UE根据会话类型信息判断是否需要为第一业务发起会话建立请求。通过本实施例提供的方案，在发起会话建立请求前，UE可判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互。

Description

会话处理方法、装置和系统 技术领域
本申请涉及无线通信技术领域，尤其涉及一种会话处理方法、装置和系统。
背景技术
网络切片是一种新式网络和业务模式，可通过定制网络和管理，从而更好地满足消费者和企业每个服务的个性化需求。对于采用网络切片技术的核心网架构，用户终端(User Equipment，UE)可以接入不同类型的多个切片，同时使用多个切片提供的不同的服务。
当网络侧收到UE的会话请求时，网络侧会根据会话请求携带的信息建立会话。一个会话可以为不同的业务提供服务。然而，在现有技术中，只要有新的应用(application)发起业务，UE都发起会话建立过程，由网络侧确定是重用已经建立的会话还是建立新的会话，这样增加了UE和网络侧的信令交互。
发明内容
本申请描述了一种会话处理方法、装置和系统。
一方面，本申请的实施例提供一种会话处理方法，该方法包括：用户设备UE获取会话类型信息。该会话类型信息用于指示第一会话的类型。当第一应用触发第一业务时，UE根据会话类型信息判断是否需要为第一业务发起会 话建立请求。通过本实施例提供的方案，在发起会话建立请求前，UE可判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
在一个可能的设计中，会话类型信息包括所述第一会话支持的数据网络的名称DNN，所述会话类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
在一个可能的设计中，该方法还包括：所述UE获取所述第一会话的标识。
在一个可能的设计中，所述会话类型信息包括所述UE附着的共享控制面网络功能CCNF设备所在的切片所支持的会话的类型，其中，所述UE附着的CCNF设备所在的切片所支持的会话包括所述第一会话。
在一个可能的设计中，所述UE根据所述会话类型信息判断是否需要为所述第一业务发起会话建立请求，包括：所述UE根据预配置的所述第一应用与所述第一应用访问的数据网络的名称DNN，以及所述第一业务的类型或支持第一业务所需的切片类型之间的对应关系，并根据所述会话类型信息，判断是否存在已经建立的会话支持所述第一业务的类型和所述第一应用访问的DNN。这样，对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
在一个可能的设计中，所述用户设备UE获取会话类型信息包括：所述UE在会话建立流程中获取所述会话类型信息；或所述UE在初始附着流程中获取所述会话类型信息；或所述UE在跟踪区更新流程中获取所述会话类型信息。
在一个可能的设计中，所述用户设备UE获取会话类型信息包括：所述UE从会话管理功能SMF设备接收建立会话响应消息，所述建立会话响应消息携带 所述会话类型信息；或所述UE从共享控制面网络功能CCNF设备接收附着接受消息，所述附着接受消息携带所述会话类型信息；或所述UE从CCNF设备接收跟踪区更新响应消息，所述跟踪区更新响应消息携带所述会话类型信息。
另一方面，本申请实施例提供了一种会话处理方法，包括：第一会话管理功能SMF设备接收用于请求建立第一会话的请求消息，发送第一建立会话响应消息。该第一建立会话响应消息中携带会话类型信息。会话类型信息用于指示上述第一会话的类型，该会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。通过本实施例提供的方案，在发起会话建立请求前，UE可判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
在一个可能的设计中，所述会话类型信息包括所述第一会话访问的数据网络的名称DNN，所述会话类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
在一个可能的设计中，所述第一建立会话响应消息还包括所述第一会话的标识。
在一个可能的设计中，所述第一SMF设备发送第一建立会话响应消息，包括：所述第一SMF设备向所述UE发送所述第一建立会话响应消息。例如，在非漫游场景下，第一SMF设备向UE发送所述第一建立会话响应消息。
在一个可能的设计中，本申请也可适用于漫游的场景。若所述第一SMF设备为归属公共陆地移动网络的SMF设备，所述第一SMF设备发送第一建立会话响应消息，包括：所述第一SMF设备向拜访公共陆地移动网络的SMF设备发送 所述第一建立会话响应消息。若所述第一SMF设备为拜访公共陆地移动网络的SMF设备，在所述第一SMF设备发送第一建立会话响应消息之前，所述方法还包括：所述第一SMF设备从归属公共陆地移动网络的SMF设备接收第二建立会话响应消息，所述第二建立会话响应消息携带所述第一会话访问的DNN，以及所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项；所述第一SMF设备根据所述第一SMF设备支持的业务的类型和所述第二建立会话响应消息，获得所述会话类型信息。
另一方面，本申请实施例提供了一种会话处理方法，包括：共享控制面网络功能CCNF设备接收请求消息，收到所述请求消息后，向用户设备UE发送响应消息。该响应消息中携带会话类型信息。会话类型信息用于指示所述CCNF所在的切片支持的会话的类型，该会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。通过本实施例提供的方案，在发起会话建立请求前，UE可判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
在一个可能的设计中，所述会话类型信息包括所述会话访问的数据网络的名称DNN，所述会话类型信息还包括所述会话支持的业务的类型和支持所述会话的切片的类型中的至少一项。
在一个可能的设计中，所述请求消息为初始附着请求消息，所述响应消息为初始附着接受消息；或所述请求消息为位置区更新请求消息，所述响应消息为位置区更新响应消息。
另一方面，本申请实施例提供了一种UE，该UE具有实现上述方法设计中 UE行为的功能。所述功能可以通过硬件实现，UE的结构中包括接收器和处理器。也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
又一方面，本申请实施例提供了一种CCNF设备，可以包括接收器和发送器，用于执行上述方面CCNF设备的通信功能。
又一方面，本申请实施例提供了一种SMF设备，可以包括接收器和发送器，用于执行上述方面SMF设备的通信功能。
又一方面，本申请实施例提供了一种通信系统，该系统包括上述方面所述的CCNF设备和SMF设备。
再一方面，本申请实施例提供了一种计算机存储介质，用于储存为上述UE所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本申请实施例提供了一种计算机存储介质，用于储存为上述CCNF设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本申请实施例提供了一种计算机存储介质，用于储存为上述SMF设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
根据本申请实施例提供的技术方案，用户设备UE获取会话类型信息。该会话类型信息用于指示第一会话的类型。当第一应用触发第一业务时，UE根据会话类型信息判断是否需要为第一业务发起会话建立请求。在发起会话建立请求前，UE可以判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
附图说明
为了更清楚地说明本申请实施例，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。
图1为本申请实施例提供的一种通信系统示意图；
图2为本申请实施例提供的一种会话处理方法的流程示意图；
图3A-3D为本申请实施例提供的一种会话处理方法的交互示意图；
图4为本申请实施例提供的一种会话处理方法的又一流程示意图；
图5为本申请实施例提供的一种会话处理方法的另一流程示意图；
图6为本申请实施例提供的一种UE的结构示意图；
图7为本申请实施例提供的一种CCNF设备的结构示意图；
图8为本申请实施例提供的一种SMF设备的结构示意图；
图9为本申请实施例提供的一种UE的又一结构示意图；
图10为本申请实施例提供的一种CCNF设备的又一结构示意图；及
图11为本申请实施例提供的一种SMF设备的又一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。首先，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、本申请涉及的用户设备(User Equipment，UE)，可以包括各种具有 无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。所述UE也可以称为移动台(mobile station,简称MS)，终端(terminal)，终端设备(terminal equipment)，还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端等。为方便描述，本申请所有实施例中，上面提到的设备统称为UE。
2)、本申请实施例涉及的接入设备，是一种部署在无线接入网中用以为UE提供无线通信功能的装置。接入设备可以包括各种形式的宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备接入设备功能的名称可能会有所不同，例如，在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB),在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。为方便描述，本申请所有实施例中，上述为UE提供无线通信功能的装置统称为接入设备。
3)、本申请实施例涉及的网络切片实例(network slice instance),用于按切片需求方的需求灵活地提供一种或多种网络服务。网络切片技术是将一个物理网络分成多个网络切片实例，每个网络切片实例按照业务场景的需要进行网络功能的定制裁剪及相应网络功能的编排管理。通过定制网络和管理，更好地满足消费者和企业每个服务的个性化需求，实现多种业务在共享 一套宽带网络基础设施的同时保持业务实现的相对独立。其中，个性化需求包括覆盖区域、持续时间、容量、速度、延迟、可靠性、安全性和可用性等。一个“网络切片”可以视为一个实例化的核心网络架构。目前业界所考虑的“网络切片”使用实例包括移动宽带(Mobile Broadband)、多媒体、大规模机器类通信(Massive Machine Type Communication)和关键机器类通信(Critical Machine Type Communication)。为方便描述，本申请所有实施例中，上面提到的网络切片实例简称为切片。
4)、本申请实施例涉及的共享控制面网络功能(Common Control Plane Network Function)设备，是被多个网络切片实例共享的控制面设备，负责移动通信网络中移动性管理、转发路径管理以及网络协议(Internet Protocol，IP)地址分配的设备。控制面设备可以但不限于是核心网中移动管理实体(Mobility Management Entity，MME)，S-GW控制面或P-GW控制面等，也可以是MME、S-GW控制面、和P-GW控制面中任意网元融合形成控制面网元。
5)、本申请实施例涉及的会话管理功能(session management function，SMF)设备，是网络切片实例中用于管理会话的设备。负责处理与UE会话管理相关的非接入网信令(NAS-Non Access Signalling)消息。主要功能是分配UE IP地址，选择用户面功能，执行会话相关的策略和计费规则，是MME功能中会话管理相关的功能、SGW控制面和PGW控制面功能的融合。6)、本申请实施例涉及的用户面(use plane,UP)设备(也可称为转发面设备、用户面网元、转发面网元、核心网用户面网元或核心网转发面网元)，是负责为终端设备提供业务报文转发的设备。用户面设备可以但不限于是S-GW、P-GW、路由器、交换机、软件定义网络(Software Defined Network,SDN)交换机(switch)等物理转发面设备，还可以是S-GW转发面或P-GW转发面等虚拟转发面网元。为方便描述，本申请所有实施例中，上述用户面设备统称为UP。
7)、本申请实施例涉及的数据网络(Data Network，DN)，是UE最终要建立连接并访问的网络。DN可以但不限于是分组数据网络(Packet Data Network,PDN)，例如，因特网(Internet)、虚拟私有网络(Virtual Private Network,VPN)、IP多媒体业务(IP Multi-media Service,IMS)网络，或由运营商提供的无线应用协议(Wireless Application Protocol,WAP)网络。为方便描述，本申请所有实施例中，上述数据网络统称为DN。
8)、“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
9)、在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
对于采用网络切片技术的核心网架构，UE可以接入单个切片，也可以接入不同类型的多个切片，同时使用多个切片提供的不同的服务。图1所示为本申请提供的一种通信系统100的示意图。在图1的通信系统100中，UE 102可同时接入多个切片(例如，切片A、B、C中的至少两个切片)。其中，切片A、B、C共享CCNF设备108，共享的CCNF设备可以是多个共享控制面设备的组合。切片选择功能(slice selection function,SSF,也可称为network slice selection function NSSF)设备106用于选择切片，为接入设备104提供信息以路由到对应的CCNF设备108。除了包括共享的CCNF设备108外，一个切片还包括该切片特有的SMF设备和UP。例如，切片A具有SMF设备1，UP1和UP2；切片B具有SMF设备2，UP3和UP4；切片C具有SMF设备3，UP5和UP6。SSF或NSSF设备也可能是共享CCNF设备的一个子设备。本发明假设SSF或NSSF设备是一个独立于CCNF设备的设备，本发明同样可以应用于SSF或NSSF 设备作为共享CCNF设备的子设备的场景下。
当网络侧收到UE 102的会话请求消息时，被选择的SMF设备会根据会话请求消息携带的信息，如业务类型(service type)或切片类型(slice type)，数据网络名称(data network name，DNN)，选择合适的UP，建立会话。一个UP可以对应一个或多个DN，一个DN也可以与多个UP建立会话。因此，一个会话可以为不同的业务不同的DN提供服务。因此，UE在收到新的应用请求消息时，可能需要建立新的会话，也可能可通过已有的会话为该业务提供服务。根据本申请提供的会话处理方法，在发起会话建立请求前，UE可判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
在本申请实施例中，所述通信系统100可以为各种无线接入技术(radio access technology，RAT)系统，例如码分多址(code division multiple access，CDMA)系统、时分多址(time division multiple access，TDMA)系统、频分多址(frequency division multiple access，FDMA)系统、正交频分多址(orthogonal frequency-division multiple access，OFDMA)系统、单载波频分多址(single carrier FDMA，SC-FDMA)系统或其它系统。术语“系统”可以和“网络”相互替换。CDMA系统可以实现例如通用无线陆地接入(universal terrestrial radio access，UTRA)，CDMA2000等无线技术。UTRA可以包括宽带CDMA(wideband CDMA，WCDMA)技术和其它CDMA变形的技术。CDMA2000可以覆盖过渡标准(interim standard，IS)2000(IS-2000)，IS-95和IS-856标准。TDMA系统可以实现例如全球移动通信系统(global system for mobile communication，GSM)等无线技术。OFDMA系统可以实现 诸如演进通用无线陆地接入(evolved UTRA，E-UTRA)、超级移动宽带(ultra mobile broadband，UMB)、IEEE 802.11(Wi-Fi)，IEEE 802.16(WiMAX)，IEEE 802.20，Flash OFDMA等无线技术。UTRA和E-UTRA是UMTS以及UMTS演进版本。3GPP在长期演进(long term evolution，LTE)和基于LTE演进的各种版本是使用E-UTRA的UMTS的新版本。此外，所述通信系统100还可以适用于面向未来的通信技术，例如4.5G系统或NR(Next Radio)系统。本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图2为根据本申请实施例的会话处理方法的流程图。如图2所示，该方法包括：
在步骤202中，UE获取会话类型信息。会话类型信息用于指示第一会话的类型。
例如，会话类型信息包括该第一会话支持的数据网络的名称DNN，会话类型信息还包括第一会话支持的业务的类型和支持第一会话的切片的类型中的至少一项。例如，第一会话可支持多个业务。以下将以会话类型信息包括DNN和第一会话支持的业务类型为例进行描述，当会话类型信息包括DNN和支持第一会话的切片类型，会话类型信息可具有类似的格式，本发明也不在此限制。
可选的，UE可在会话建立流程中获取会话类型信息，第一会话为通过该会话建立流程建立的会话；或者，UE也可在初始附着流程或跟踪区更新 (tracking area update，TAU)流程中获取会话类型信息，会话类型信息包括所述UE附着的CCNF设备所在的切片所支持的会话的类型，其中，所述UE附着的CCNF设备所在的切片所支持的会话包括所述第一会话。UE如何获取会话类型信息将结合图3A至图3D进一步描述。
UE在建立第一会话后，会保存该会话的会话信息，如表1所示：
会话标识1 业务类型1 DNN1
会话标识2 业务类型2 DNN2
会话标识3 业务类型3 DNN1
… … …
表1
以图1的通信系统为例，UE可以通过切片A访问DN1获取业务类型1的业务；也可以通过切片A访问DN2获取业务类型2的业务；还可以通过切片A访问DN3获取业务类型2的业务。另外，UE可以通过切片B访问DN1获取业务类型3的业务，还可以通过切片B访问DN2获取业务类型4的业务。
表1保存了UE已经建立的3个会话，以及触发每个会话建立的业务类型和DNN。
可选的，该方法还包括：UE获取第一会话的标识。第一会话的标识可用于该第一会话。例如，会话类型信息还包括第一会话的标识；或者，用于传递会话类型信息的消息(如图3A/3D中的建立会话响应消息)还携带用于指示第一会话的标识的信元。当会话类型信息还包括第一会话的标识时，会话类型信息可具有如表2的格式：
Figure PCTCN2016105750-appb-000001
Figure PCTCN2016105750-appb-000002
表2
可选的，会话类型信息还可包括UE附着的CCNF设备的标识或切片的标识(network slice identifier，NS-ID)，如表3和表3’所示。当会话类型信息包括CCNF设备的标识时，该会话类型信息可用于指示支持该CCNF设备所在的切片所支持的会话的类型，如表3所示；当会话类型信息包括切片的标识时，该会话类型信息可用于指示该CCNF设备控制的具体某个切片所支持的会话的类型，如表3’所示，UE附着的CCNF设备所在的切片包括切片1,2和3，对应的切片标识分别是NS-ID 1,NS-ID 2和NS-ID 3。
Figure PCTCN2016105750-appb-000003
表3
Figure PCTCN2016105750-appb-000004
Figure PCTCN2016105750-appb-000005
表3’
在步骤204中，当第一应用触发第一业务时，UE根据会话类型信息判断是否需要为第一业务发起会话建立请求。
例如，不同的应用对应不同的DNN和业务类型。UE内可预配置有第一应用与第一应用访问的数据网络的名称DNN，以及第一业务的类型或支持第一业务所需的切片类型之间的对应关系。例如，UE内预配置的对应关系如表4所示：
应用1 业务类型1 DNN1
应用2 业务类型2 DNN2
应用3 业务类型3 DNN2
表4
例如，对于通话应用，其业务类型为基于IP的语音传输(Voice over Internet Protocol，VoIP)，其DNN为运营商网络名称。对于微信应用，其业务类型为MBB，其DNN为腾讯的域名。对于企业内部的通信应用，其业务类型为企业内部MBB，其DNN为企业内部网络域名。对于无人驾驶应用，其业务类型为车-一切(vehicle-to-everything，V2X)，其DNN可为宝马网络域名。因此，UE内预配置的对应关系可具有表5的格式：
应用 业务类型 DNN
通话应用 VoIP 运营商网络名称
微信应用 MBB 腾讯的域名
企业内部通讯应用 企业内部MBB 企业内部网络域名
无人驾驶应用 V2X 宝马网络域名
表5
UE可根据预配置的对应关系以及会话类型信息，判断是否存在已经建立的会话支持第一业务的类型和第一应用访问的DNN。若存在已经建立的会话能够支持第一业务的类型和第一应用访问的DNN，则重用现有的会话为第一应用访问DNN；若不存在，UE才需要为第一业务发起会话建立请求。
举例来说，当表4中的应用1触发业务类型1的业务时，UE根据如表1(或表2、表3)的会话类型信息和如表4的预配置对应关系，确定可通过现有的会话为应用1访问DNN1，无需发起新的会话建立请求。
因此，通过本实施例提供的方案，在发起会话建立请求前，UE可根据会话类型信息判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
以下将通过图3A至图3D的四个实施例介绍用户设备获取会话类型信息的方式。图3A至图3D将结合图1和图2进行描述。
例如，UE可在会话建立流程中获取会话类型信息，该会话建立流程用于建立第一会话。如图3A所示，该方法包括：
在步骤301中，UE 102向接入设备104发送建立会话请求(create session request)消息。接入设备104收到后，将该建立会话请求消息转发至CCNF设备108。其中，建立会话请求消息携带网络切片以及SMF选择辅助信息(SM Network Slice Selection Assistance Information,SM NSSAI)和请求该 会话的业务要访问的DNN。例如，SM NSSAI为UE 102请求的业务的类型或提供该业务的切片类型中的至少一项。
在步骤302中，CCNF设备108根据接收到的建立会话请求消息，向SSF设备106发送携带SM NSSAI的切片选择请求消息。
在步骤303中，SSF设备106收到切片选择请求消息后，根据SM NSSAI选择切片，并获取该切片的标识，例如NS-ID。
在步骤304中，SSF设备106向CCNF设备108发送携带NS-ID的切片选择响应消息。
其中，步骤302至步骤304为可选步骤。如果CCNF已经通过预配置等方式获取所述NSSAI与切片标识的对应关系，则不需要执行步骤302和304.
在步骤305中，CCNF设备108确定SMF设备(例如，图1中的SMF设备1)。
在步骤306中，CCNF设备108向确定的SMF设备发送建立会话请求消息，该建立会话请求消息携带UE 102通过待建立的第一会话想要访问的DNN。
在步骤307中，SMF设备收到建立会话请求消息后，根据DNN选择用户面UP。
在步骤308中，建立UP。例如，在非漫游场景下建立归属公共陆地移动网(home public land mobile network，HPLMN)侧的用户面。
在步骤309中，SMF设备获取会话类型信息，并向UE102发送携带会话类型信息的建立会话响应(create session response)消息。其中，会话类型信息至少包括第一会话支持的DNN，还包括第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。SMF设备向CCNF设备106发送该建立会话响应消息，CCNF设备106收到后向接入设备104转发该建立会话响应消息，接入设备104收到后向UE102转发该建立会话响应消息。
在UE102收到建立会话响应消息后，即可从建立会话响应消息中获取并保存例如表2形式的会话类型信息。因此，UE在建立会话流程中获得会话类型信息后，当新的第一应用触发第一业务时，在发起会话建立请求前，UE可根据会话类型信息判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
例如，本实施例中UE侧保存了表2和表4。
以图1的通信系统并结合表2为例，假设此时表2中只包括会话标识1的信息，即网络侧通过步骤301-309所述的过程建立了会话标识为“会话标识1”的会话，并且UE获取了会话标识为“会话标识1”的会话类型信息。
UE的某个新应用“应用2”发起业务请求，UE根据表4的预配置信息确定该应用请求访问DNN2获取业务类型2的业务A，此时UE查询业务类型信息列表。由于此时表2中只包括会话标识1的信息，UE发现现有已经建立的会话无法匹配“应用2”的需求，因此UE向网络侧发送新的会话建立请求，网络侧根据UE发送的会话建立请求，建立会话标识为“会话标识2”的会话，并在返回给UE的会话建立响应消息中携带“会话标识2”的会话类型信息，即表2中的第2行和第3行。
当UE的某个新应用“应用3”发起业务请求，UE根据表4的预配置信息确定该应用请求访问DNN3获取业务类型2的业务B，此时UE查询业务类型信息列表，发现“会话标识2”的会话能够支持该应用请求的业务，并且UE判断业务A和业务B可以共用相同的IP，UE直接使用会话标识为“会话标识2”的会话发送和接收业务B的数据包。具体的，UE可以根据业务支持的“会话和业务连续 性(session and service continuity mode，SSC)模式”进一步判断业务对IP地址的要求。
或者，UE可在初始附着流程中获取会话类型信息。如图3B所示，该方法包括：
在步骤311中，UE 102向接入设备104发起初始附着请求消息，以请求接入网络。初始附着请求消息包括用于指示UE 102的国际移动签约标识(International Mobile Subscriber Identity，IMSI)。
在步骤312中，接入设备104收到初始附着请求消息后，向SSF设备106发送携带该IMSI的切片选择请求消息，该切片选择请求消息用于请求SSF设备106为UE 102选择CCNF设备(如CCNF设备108)。
在步骤313中，SSF设备106收到切片选择请求消息后，向签约数据管理(subscriber data management，SDM)设备发送携带该IMSI的签约信息请求消息，该签约信息请求消息用于请求UE 102的签约信息。
在步骤314中，SDM设备收到签约信息请求消息后，根据IMSI获取该UE的签约NSSAI。其中，签约NSSAI包括UE 102签约的需要网络提供的一个或一组服务类型或切片类型。可选的，签约NSSAI还包括签约的需要网络提供的一个或一组服务类型或切片类型支持的DNN。
在步骤315中，SSF设备106根据签约NSSAI选择CCNF设备(例如CCNF设备108)。
在步骤316中，SSF设备向接入设备104发送携带能够标识CCNF的信息的切片选择响应消息，切片选择响应消息中还包括网络允许的NSSAI(Accepted NSSAI)。
在步骤317中，接入设备104收到切片选择响应消息后，向CCNF设备108发送初始附着请求消息。例如，初始附着请求消息可携带上述IMSI。
在步骤318中，CCNF设备108收到初始附着请求消息后，与SDM设备交互，实现对UE的鉴权。
在步骤319中，鉴权完成后，CCNF设备108向UE102发送携带会话类型信息的初始附着接受消息。其中，会话类型信息包括CCNF所在的切片支持的一个或一组会话类型，至少包括第一会话支持的DNN，还包括第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。可选的，会话类型信息还包括CCNF设备的标识或CCNF所支持的切片的标识。CCNF设备108向接入设备104发送该初始附着接受消息，接入设备104收到后向UE102转发该初始附着接受消息。
在UE102收到初始附着接受消息后，即可从初始附着接受消息中获取并保存例如表3形式的会话类型信息。因此，UE在初始附着流程中获得会话类型信息后，当新的第一应用触发第一业务时，在发起会话建立请求前，UE可根据会话类型信息判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
例如，本实施例中UE侧保存了表1，表3或表3’，以及表4。
以图1的通信系统并结合表3为例，所述CCNF设备108向UE102发送携带会话类型信息的初始附着接受消息，其中会话类型信息包括CCNF设备108所在的所有切片支持的会话类型列表，如“会话类型1”支持业务类型1并可访问DDN1；“会话类型2”支持业务类型2并可访问DDN2和DNN3。
假设UE和网络侧已经为“应用2”(要求访问DNN2获取业务类型2)建立了会话，并且UE侧保存了已经建立的会话信息，参考表1，即UE已经保存了表1中的第二条信息；
当UE的某个新应用“应用3”发起业务请求，UE根据表4的预配置信息确定该应用请求访问DNN3获取业务类型2的业务B，此时UE查询业务类型信息列表表3，发现“会话类型2”能够同时支持“业务类型2+DNN2”和“业务类型2+DNN3”；并且UE通过表1查询到已经有会话支持“业务类型2+DNN2”，UE结合表1和表3，发现“会话标识2”的会话能够支持该应用请求的业务，并且UE判断业务2可以和业务1共用相同的IP，UE直接使用会话标识为“会话标识2”的会话发送和接收该业务的数据包。具体的，UE可以根据业务支持的“会话和业务连续性(session and service continuity mode，SSC)模式”进一步判断业务对IP地址的要求。
或者，UE可在TAU流程中获取会话类型信息。在图3C的例子中，位置区更新前的旧CCNF设备为CCNF设备108’，位置区更新后的新CCNF设备为CCNF设备108。如图3C所示，该方法包括：
在步骤321中，UE 102向接入设备104发起TAU请求消息，以请求进行跟踪区更新。例如，TAU请求消息包括用于指示UE 102的临时标识(temp ID)以及网络允许的NSSAI(Accepted NSSAI)，Accepted NSSAI用作接入设备104确定新CCNF设备。
在步骤322中，接入设备104收到TAU请求消息后，根据Accepted NSSAI信息确定新CCNF设备。
在步骤323中，接入设备104将TAU请求消息转发至新CCNF设备108。
在步骤324中，新CCNF设备108收到TAU请求消息后，从旧CCNF设备108’获取UE 102的上下文。
在步骤325中，CCNF设备108向UE102发送携带会话类型信息的TAU响应消息。其中，会话类型信息包括CCNF所在的切片支持的一个或一组会话类型，至少包括第一会话支持的DNN，还包括第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。可选的，会话类型信息还包括CCNF设备的标识或CCNF所支持的切片的标识。例如，CCNF设备108向接入设备104发送该TAU响应消息，接入设备104收到后向UE102转发该TAU响应消息。
在UE102收到TAU响应消息后，即可从TAU响应消息中获取并保存例如表3或表3’形式的会话类型信息。因此，UE在TAU流程中获得会话类型信息后，当新的第一应用触发第一业务时，在发起会话建立请求前，UE可根据会话类型信息判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
可选的，图3A的例子可适用于非漫游场景下的会话建立流程。当UE 102处于漫游场景下，可根据图3D的方法在会话建立流程中获取会话类型信息。该会话建立流程用于建立第一会话。在图3D的例子中，拜访公用陆地移动网(visiting public land mobile network，vPLMN)包括拜访CCNF设备(vCCNF)、拜访SSF设备(vSSF)、拜访SMF设备(vSMF)和拜访用户面(vUP)。归属PLMN(home PLMN，hPLMN)包括归属SMF设备(hSMF)和归属用户面(hUP)。如图3D所示，该方法包括：
在步骤331中，UE 102向接入设备104发送建立会话请求消息。接入设备 104收到后，将该建立会话请求消息转发至vCCNF。其中，建立会话请求消息携带网络切片以及SMF选择辅助信息(SM Network Slice Selection Assistance Information,SM NSSAI)和请求该会话的业务要访问的DNN。例如，SM NSSAI为UE 102请求的业务的类型或提供该业务的切片类型中的至少一项。例如，SM NSSAI为UE 102请求的业务的类型或提供该业务的切片类型中的至少一项。
在步骤332中，vCCNF根据接收到的建立会话请求消息，向vSSF设备发送携带SM NSSAI的切片选择请求消息。
在步骤333中，vSSF根据NSSAI选择切片，获取该切片的标识。例如，切片的标识包括vPLMN的切片的标识vNS-ID和hPLMN的切片的标识hNS-ID。例如，vSSF可从vPLMN的SSF获取hPLMN选择的hPLMN的切片的标识hNS-ID。
在步骤334中，vSSF向vCCNF发送携带切片标识的切片选择响应消息。
在步骤335中，vCCNF根据vNS-ID确定vSMF。
在步骤336中，vCCNF向确定的vSMF发送建立会话请求消息。例如，该建立会话请求消息携带UE 102通过待建立的第一会话想要访问的DNN以及hNS-ID。该建立会话请求消息用于请求建立vSMF与vUP之间的会话。
在步骤337中，vSMF收到建立会话请求消息后，根据DNN和hNS-ID选择vUP，建立vSMF与vUP之间的vPLMN侧的会话(如第一会话)。
步骤331至337可参考图3A中步骤301至308的描述，此处不再赘述。
在步骤338中，vSMF向hSMF发送建立会话请求消息，该建立会话请求消息携带UE请求的会话想要访问的DNN。
在步骤339中，hSMF收到建立会话请求消息后，根据DNN选择hUP，建立hSMF 与hUP之间的hPLMN侧的会话。
在步骤340中，hSMF获取hPLMN侧的会话支持的业务的类型和支持hPLMN侧的会话的切片的类型中的至少一项,并将上述这些会话类型信息通过建立会话响应消息发送至vSMF。此外，步骤340中的建立会话响应消息还可包括DNN。例如，建立会话响应消息中包含的hPLMN侧的会话类型信息可具有表2的格式。
在步骤341中，vSMF根据收到的hPLMN侧的会话类型信息，以及vPLMN侧的会话支持的业务类型信息，确定最终的会话类型信息。
例如，hPLMN侧的会话类型信息可具有表2的格式，vPLMN侧的会话支持的业务类型信息如表6所示，会话标识1为vPLMN侧的会话的标识，该回话支持业务类型1和业务类型4。因此，结合表2和表6的信息，可知hPLMN侧支持的业务类型1也能够在vPLMN侧得到支持，最终vSMF确定的所建立的会话支持的业务类型信息可为表7所示。
Figure PCTCN2016105750-appb-000006
表6
会话标识1 业务类型1 DNN1
表7
在步骤342中，vSMF向UE 102发送携带会话类型信息的建立会话响应消息。其中，会话类型信息至少包括第一会话(vPLMN侧的会话)连接支持的DNN，还包括第一会话支持的业务的类型和支持第一会话的切片的类型中的至少一项。例如，vSMF向vCCNF发送该建立会话响应消息，vCCNF收到后向接入设备104转发该建立会话响应消息，接入设备104收到后向UE102转发该建立会话响应消 息。
在UE102收到建立会话响应消息后，即可从建立会话响应消息中获取并保存例如表7形式的会话类型信息。因此，UE在建立会话流程中获得会话类型信息后，当新的第一应用触发第一业务时，在发起会话建立请求前，UE可根据会话类型信息判断是重用已经建立的会话还是建立新的会话。对于可重用已经建立的会话的业务，无需新建会话，降低了UE和网络侧的信令交互，减轻了网络负载。
图4为根据本申请实施例提供的会话处理方法的流程示意图。该方法可由图3A中的SMF设备执行，也可由图3D中vSMF设备或hSMF设备执行。如图4所示，该方法包括：
在步骤402中，第一SMF设备接收用于请求建立第一会话的请求消息。
在步骤404中，第一SMF设备发送第一建立会话响应消息，所述第一建立会话响应消息中携带会话类型信息，所述会话类型信息用于指示所述第一会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
会话类型信息的详细描述可参考图2的描述，此处不再赘述。
在例如图3A的非漫游场景中，步骤404包括：第一SMF设备向拜访公共陆地移动网络的SMF设备发送所述第一建立会话响应消息。
在例如图3D的漫游场景中，第一SMF设备可以是vSMF设备，也可以是hSMF设备。若第一SMF设备为hSMF设备，步骤404包括：向vSMF设备发送所述第一建立会话响应消息。若第一SMF设备为vSMF设备，在步骤404之前，方法还包括：第一SMF设备从hSMF设备接收第二建立会话响应消息，根据所述第一SMF 设备支持的业务的类型和第二建立会话响应消息，获得所述会话类型信息。该步骤可参考图3D中的步骤341和342，此处不再赘述。
图5为根据本申请实施例提供的会话处理方法的流程示意图。该方法可由图3B或图3C中CCNF设备执行。如图5所示，该方法包括：
在步骤502中，CCNF设备接收请求消息。
在步骤504中，CCNF设备收到所述请求消息后，向用户设备UE发送响应消息，所述响应消息中携带会话类型信息，所述会话类型信息用于指示所述CCNF所在的切片支持的会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
会话类型信息的详细描述可参考图2的描述，此处不再赘述。
例如，请求消息为初始附着请求消息，响应消息为初始附着接受消息，可参考图3B中步骤317和319的描述，此处不再赘述。或者，请求消息为位置区更新请求消息，响应消息为位置区更新响应消息，可参考图3C中步骤323和325的描述，此处不再赘述。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的会话处理方法进行了介绍。可以理解的是，各个网元，例如UE、SMF设备、CCNF设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述 的功能，但是这种实现不应认为超出本申请的范围。
例如，当上述网元通过软件模块来实现相应的功能。UE 102可包括接收单元602、处理单元604，如图6所示。接收单元602可用于执行图2中的步骤202，图3A中的步骤309，图3B中的步骤319，图3C中的步骤325，或图3D中的步骤342。处理单元604可用于执行图2中的步骤204。此外，UE 102还可包括发送单元606，用于向其他网元发送各种消息，例如，图3A中的步骤301，图3B中的步骤311，图3C中的步骤321，或图3D中的步骤331。
CCNF设备108可包括接收单元702和发送单元704，如图7所示。接收单元702用于接收请求消息(可参考步骤502)。发送单元704用于向UE发送携带会话类型信息的响应消息(可参考步骤504)。例如，接收单元702可用于执行图3A中的步骤步骤301、304、309，图3B中的步骤317，图3C中的步骤323，或图3D中的步骤331、334。发送单元704可用于执行图3A中的步骤302、306、309、342，图3B中的步骤319，图3C中的步骤325，或图3D中的步骤332、336、342。
SMF设备800可包括接收单元802和发送单元804，如图8所示。接收单元802用于接收用于请求建立第一会话的请求消息(可参考步骤402)。发送单元804用于发送携带会话类型信息的第一建立会话响应消息(可参考步骤404)。例如，接收单元802可用于执行图3A中的步骤步骤306，图3B中的步骤312、314，或图3D中的步骤336、340。发送单元804可用于执行图3A中的步骤309，图3B中的步骤313、316，或图3D中的步骤342。
图9示出了上述实施例中所涉及的UE的一种可能的设计结构的简化示意图。所述UE包括收发器901，控制器/处理器902，还可以包括存储器903和调制解调处理器904。例如，收发器901包括接收器，用于执行图2中的步骤202； 处理器902用于执行图2中的步骤204。
收发器901调节(例如，模拟转换、滤波、放大和上变频等)该输出采样并生成上行链路信号，该上行链路信号经由天线发射给上述实施例中所述的接入设备104。在下行链路上，天线接收上述实施例中接入设备104发射的下行链路信号。收发器901调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。在调制解调处理器904中，编码器9041接收要在上行链路上发送的业务数据和信令消息，并对业务数据和信令消息进行处理(例如，格式化、编码和交织)。调制器9042进一步处理(例如，符号映射和调制)编码后的业务数据和信令消息并提供输出采样。解调器9044处理(例如，解调)该输入采样并提供符号估计。解码器9043处理(例如，解交织和解码)该符号估计并提供发送给UE的已解码的数据和信令消息。编码器9041、调制器9042、解调器9044和解码器9043可以由合成的调制解调处理器904来实现。这些单元根据无线接入网采用的无线接入技术(例如，LTE及其他演进系统的接入技术)来进行处理。
控制器/处理器902对UE的动作进行控制管理，用于执行上述实施例中由UE进行的处理。例如，控制器/处理器902可以用于在第一应用触发第一业务时，根据会话类型信息判断是否需要为第一业务发起会话建立请求。存储器903用于存储用于所述UE的程序代码和数据。
图10示出了上述实施例中涉及到的CCNF设备的一种可能的设计结构的简化示意图。所述CCNF设备可以为图1中的CCNF设备108。CCNF设备可以包括控制器/处理器1001，存储器1002以及通信单元1003。所述控制器/处理器1001可以用于协调多个切片之间的资源管理和配置。存储器1002可以用于存储控 制节点的程序代码和数据。所述通信单元1006，用于支持该CCNF设备与其他网元进行通信。例如，通信单元1006包括接收器和发送器。作为实例，接收器用于支持CCNF设备执行图3A中的步骤步骤301、304、309，图3B中的步骤317，图3C中的步骤323，或图3D中的步骤331、334。发送器用于支持CCNF设备执行图3A中的步骤302、306、309、342，图3B中的步骤319，图3C中的步骤325，或图3D中的步骤332、336、342。
图11示出了上述实施例中涉及到的SMF设备的一种可能的设计结构的简化示意图。SMF设备可以包括控制器/处理器1101，存储器1102以及通信单元1103。所述控制器/处理器1101可以用于协调多个切片之间的资源管理和配置。存储器1102可以用于存储控制节点的程序代码和数据。所述通信单元1106，用于支持该SMF设备与其他网元进行通信。例如，通信单元1106包括接收器和发送器。作为实例，接收器用于支持SMF设备执行图3A中的步骤步骤306，图3B中的步骤312、314，或图3D中的步骤336、340。发送器用于支持SMF设备执行图3A中的步骤309，图3B中的步骤313、316，或图3D中的步骤342。
用于执行本申请上述UE、CCNF设备或SMF设备的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
此外，本申请还公开了一种通信系统，包括如上述CCNF设备和SMF设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实 现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (31)

  1. 一种会话处理的方法，其特征在于，该方法包括：
    用户设备UE获取会话类型信息，所述会话类型信息用于指示第一会话的类型；
    当第一应用触发第一业务时，所述UE根据所述会话类型信息判断是否需要为所述第一业务发起会话建立请求。
  2. 根据权利要求1所述的方法，其特征在于，所述会话类型信息包括所述第一会话支持的数据网络的名称DNN，所述会话类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
  3. 根据权利要求1或2所述的方法，其特征在于，还包括：
    所述UE获取所述第一会话的标识。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述会话类型信息包括所述UE附着的共享控制面网络功能CCNF设备所在的切片所支持的会话的类型，其中，所述UE附着的CCNF设备所在的切片所支持的会话包括所述第一会话。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述UE根据所述会话类型信息判断是否需要为所述第一业务发起会话建立请求，包括：
    所述UE根据预配置的所述第一应用与所述第一应用访问的数据网络的名称DNN，以及所述第一业务的类型或支持第一业务所需的切片类型之间的对应关系，并根据所述会话类型信息，判断是否存在已 经建立的会话支持所述第一业务的类型和所述第一应用访问的DNN。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述用户设备UE获取会话类型信息包括：
    所述UE在会话建立流程中获取所述会话类型信息；或
    所述UE在初始附着流程中获取所述会话类型信息；或
    所述UE在跟踪区更新流程中获取所述会话类型信息。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述用户设备UE获取会话类型信息包括：
    所述UE从会话管理功能SMF设备接收建立会话响应消息，所述建立会话响应消息携带所述会话类型信息；或
    所述UE从共享控制面网络功能CCNF设备接收附着接受消息，所述附着接受消息携带所述会话类型信息；或
    所述UE从CCNF设备接收跟踪区更新响应消息，所述跟踪区更新响应消息携带所述会话类型信息。
  8. 一种会话处理的方法，其特征在于，该方法包括：
    第一会话管理功能SMF设备接收用于请求建立第一会话的请求消息；
    所述第一SMF设备发送第一建立会话响应消息，所述第一建立会话响应消息中携带会话类型信息，所述会话类型信息用于指示所述第一会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
  9. 根据权利要求8所述的方法，其特征在于，所述会话类型信 息包括所述UE通过所述第一会话访问的数据网络的名称DNN，所述会话类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第一建立会话响应消息还包括所述第一会话的标识。
  11. 根据权利要求8至10任一所述的方法，其特征在于，所述第一SMF设备发送第一建立会话响应消息，包括：
    所述第一SMF设备向所述UE发送所述第一建立会话响应消息。
  12. 根据权利要求8至10任一所述的方法，其特征在于，所述第一SMF设备为归属公共陆地移动网络的SMF设备，所述第一SMF设备发送第一建立会话响应消息，包括：
    所述第一SMF设备向拜访公共陆地移动网络的SMF设备发送所述第一建立会话响应消息。
  13. 根据权利要求8至11任一所述的方法，其特征在于，所述第一SMF设备为拜访公共陆地移动网络的SMF设备，在所述第一SMF设备发送第一建立会话响应消息之前，所述方法还包括：
    所述第一SMF设备从归属公共陆地移动网络的SMF设备接收第二建立会话响应消息，所述第二建立会话响应消息携带所述第一会话访问的DNN，以及所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项；
    所述第一SMF设备根据所述第一SMF设备支持的业务的类型和所述第二建立会话响应消息，获得所述会话类型信息。
  14. 一种会话处理的方法，其特征在于，该方法包括：
    共享控制面网络功能CCNF设备接收请求消息；
    所述CCNF设备收到所述请求消息后，向用户设备UE发送响应消息，所述响应消息中携带会话类型信息，所述会话类型信息用于指示所述CCNF所在的切片支持的会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
  15. 根据权利要求14所述的方法，其特征在于，所述会话类型信息包括所述会话访问的数据网络的名称DNN，所述会话类型信息还包括所述会话支持的业务的类型和支持所述会话的切片的类型中的至少一项。
  16. 根据权利要求14或15所述的方法，其特征在于，
    所述请求消息为初始附着请求消息，所述响应消息为初始附着接受消息；或
    所述请求消息为位置区更新请求消息，所述响应消息为位置区更新响应消息。
  17. 一种用户设备UE，其特征在于，包括：
    接收器，用于获取会话类型信息，所述会话类型信息用于指示第一会话的类型；
    处理器，用于当第一应用触发第一业务时，根据所述会话类型信息判断是否需要为所述第一业务发起会话建立请求。
  18. 根据权利要求17所述的用户设备UE，其特征在于，所述会话类型信息包括所述第一会话支持的数据网络的名称DNN，所述会话 类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
  19. 根据权利要求17或18所述的用户设备UE，其特征在于，所述接收器还用于获取所述第一会话的标识。
  20. 根据权利要求17至19任一所述的用户设备UE，其特征在于，所述会话类型信息包括所述UE附着的共享控制面网络功能CCNF设备所在的切片所支持的会话的类型，其中，所述UE附着的CCNF设备所在的切片所支持的会话包括所述第一会话。
  21. 根据权利要求17至20任一所述的用户设备UE，其特征在于，所述处理器用于根据预配置的所述第一应用与所述第一应用访问的数据网络的名称DNN，以及所述第一业务的类型或支持第一业务所需的切片类型之间的对应关系，并根据所述会话类型信息，判断是否存在已经建立的会话支持所述第一业务的类型和所述第一应用访问的DNN。
  22. 根据权利要求17至21任一所述的用户设备UE，其特征在于，所述接收器用于通过以下方式任一获取所述会话类型信息：
    从会话管理功能SMF设备接收建立会话响应消息，所述建立会话响应消息携带所述会话类型信息；或
    从共享控制面网络功能CCNF设备接收附着接受消息，所述附着接受消息携带所述会话类型信息；或
    从CCNF设备接收跟踪区更新响应消息，所述跟踪区更新响应消息携带所述会话类型信息。
  23. 一种会话管理功能SMF设备，其特征在于，包括：
    接收器，用于接收用于请求建立第一会话的请求消息；
    发送器，用于发送第一建立会话响应消息，所述第一建立会话响应消息中携带会话类型信息，所述会话类型信息用于指示所述第一会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
  24. 根据权利要求23所述的SMF设备，其特征在于，所述会话类型信息包括所述第一会话访问的数据网络的名称DNN，所述会话类型信息还包括所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项。
  25. 根据权利要求23或24所述的SMF设备，其特征在于，所述第一建立会话响应消息还包括所述第一会话的标识。
  26. 根据权利要求23至25任一所述的SMF设备，其特征在于，所述发送器用于向所述UE发送所述第一建立会话响应消息。
  27. 根据权利要求23至25任一所述的SMF设备，其特征在于，所述第一SMF设备为归属公共陆地移动网络的SMF设备，所述发送器用于向拜访公共陆地移动网络的SMF设备发送所述第一建立会话响应消息。
  28. 根据权利要求23至26任一所述的SMF设备，其特征在于，所述第一SMF设备为拜访公共陆地移动网络的SMF设备，所述SMF设备还包括处理器；
    其中，在所述发送器发送第一建立会话响应消息之前，所述接收器还用于从归属公共陆地移动网络的SMF设备接收第二建立会话响 应消息，所述第二建立会话响应消息携带所述第一会话访问的DNN，以及所述第一会话支持的业务的类型和支持所述第一会话的切片的类型中的至少一项；
    所述处理器用于根据所述第一SMF设备支持的业务的类型和所述第二建立会话响应消息，获得所述会话类型信息。
  29. 一种共享控制面网络功能CCNF设备，其特征在于，包括：
    接收器，用于接收请求消息；
    发送器，用于向用户设备UE发送响应消息，所述响应消息中携带会话类型信息，所述会话类型信息用于指示所述CCNF所在的切片支持的会话的类型，所述会话类型信息用于判断是否需要为第一应用触发的第一业务发起会话建立请求。
  30. 根据权利要求29所述的CCNF设备，其特征在于，所述会话类型信息包括所述会话访问的数据网络的名称DNN，所述会话类型信息还包括所述会话支持的业务的类型和支持所述会话的切片的类型中的至少一项。
  31. 根据权利要求29或30所述的CCNF设备，其特征在于，
    所述请求消息为初始附着请求消息，所述响应消息为初始附着接受消息；或
    所述请求消息为位置区更新请求消息，所述响应消息为位置区更新响应消息。
PCT/CN2016/105750 2016-11-14 2016-11-14 会话处理方法、装置和系统 WO2018086123A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2016/105750 WO2018086123A1 (zh) 2016-11-14 2016-11-14 会话处理方法、装置和系统
CN201680090770.7A CN109964468B (zh) 2016-11-14 2016-11-14 会话处理方法、装置和系统
EP16921082.0A EP3515031B1 (en) 2016-11-14 2016-11-14 Session processing method, apparatus and system
US16/412,071 US10834208B2 (en) 2016-11-14 2019-05-14 User device determines whether to create a new session based on session type information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/105750 WO2018086123A1 (zh) 2016-11-14 2016-11-14 会话处理方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/412,071 Continuation US10834208B2 (en) 2016-11-14 2019-05-14 User device determines whether to create a new session based on session type information

Publications (1)

Publication Number Publication Date
WO2018086123A1 true WO2018086123A1 (zh) 2018-05-17

Family

ID=62110163

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/105750 WO2018086123A1 (zh) 2016-11-14 2016-11-14 会话处理方法、装置和系统

Country Status (4)

Country Link
US (1) US10834208B2 (zh)
EP (1) EP3515031B1 (zh)
CN (1) CN109964468B (zh)
WO (1) WO2018086123A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021052109A1 (zh) * 2019-09-19 2021-03-25 华为技术有限公司 通信方法及装置
EP3813301A4 (en) * 2018-05-31 2021-05-26 Huawei Technologies Co., Ltd. DATA TRANSFER METHOD, TERMINAL DEVICE AND NETWORK DEVICE
CN113163468A (zh) * 2020-01-22 2021-07-23 中国电信股份有限公司 网络切片的接入方法、系统和终端

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6855838B2 (ja) * 2017-02-27 2021-04-07 ソニー株式会社 端末装置、方法及びプログラム
KR102351352B1 (ko) * 2017-03-20 2022-01-13 지티이 코포레이션 네트워크 슬라이싱 서빙 기능
CN114845381A (zh) * 2017-08-11 2022-08-02 华为技术有限公司 会话信息管理方法和装置
CN115426267A (zh) * 2019-12-31 2022-12-02 华为技术有限公司 用于获取网络切片标识的方法和装置
CN111405682B (zh) * 2020-03-19 2024-04-16 中国联合网络通信集团有限公司 一种数据转发方法及网关
CN113766607B (zh) * 2020-06-03 2023-03-31 华为技术有限公司 接入控制方法及相关设备
EP4171168A4 (en) * 2020-07-31 2023-08-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD, APPARATUS AND DEVICE FOR RELAY SESSION ESTABLISHMENT AND STORAGE MEDIUM
CN114080056B (zh) * 2020-08-13 2024-08-09 中国移动通信有限公司研究院 一种会话更新方法、终端和网络侧设备
US12048049B2 (en) * 2021-07-28 2024-07-23 Verizon Patent And Licensing Inc. Differentiated discontinuous reception based on network services
CN113556784B (zh) * 2021-07-29 2023-05-26 新华三技术有限公司 网络切片实现方法、装置及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022481A (zh) * 2007-03-21 2007-08-22 华为技术有限公司 实现多点会议中私有会话的方法及装置
CN101790134A (zh) * 2009-01-23 2010-07-28 上海华为技术有限公司 建立会话的方法、装置及系统
CN104301287A (zh) * 2013-07-16 2015-01-21 中兴通讯股份有限公司 一种多对多会话的实现方法、网络节点、服务器及系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003105194A2 (en) * 2002-03-12 2003-12-18 Ils Technology, Inc. Diagnostic system and method for integrated remote tool access, data collection, and control
US20040078341A1 (en) * 2002-10-15 2004-04-22 Steichen Terril John System and method for selling digital information online
CN101155329B (zh) * 2006-09-29 2010-11-10 华为技术有限公司 一种融合消息系统
CN101394449B (zh) * 2007-09-19 2011-01-19 华为技术有限公司 一种会话修改方法及系统
FR2950769B1 (fr) * 2009-09-30 2022-09-16 Trustseed Sas Systeme et procede de gestion de sessions de correspondance electronique securisee
US9183560B2 (en) * 2010-05-28 2015-11-10 Daniel H. Abelow Reality alternate
US8681969B1 (en) * 2010-06-30 2014-03-25 Avistar Communications Corporation Facilitating scalable 2-way mobile AV communications
US9119111B2 (en) * 2011-08-12 2015-08-25 Alcatel Lucent Method and apparatus for controlling wireless uplink sessions
US10097642B2 (en) * 2012-05-29 2018-10-09 Openet Telecom Ltd. System and method for using VoLTE session continuity information using logical scalable units
US9055520B2 (en) * 2012-12-19 2015-06-09 Cisco Technology, Inc. Systems, methods and media for mobile management entity (MME) selection by Evolved Node B (eNodeB)
CN112217905B (zh) * 2014-09-19 2024-03-29 康维达无线有限责任公司 服务层会话迁移和共享
JP2016096415A (ja) * 2014-11-13 2016-05-26 株式会社日立製作所 通信システム、管理サーバ及び監視装置
WO2016105004A1 (ko) * 2014-12-26 2016-06-30 엘지전자 주식회사 무선 통신 시스템에서 nbifom 캐퍼빌리티를 송수신하는 방법 및 이를 위한 장치
US9800672B2 (en) * 2015-04-09 2017-10-24 Eugene Edwin Nelson Computer work distribution system and method
US10291579B2 (en) * 2015-07-22 2019-05-14 Lg Electronics Inc. Method for recovering IPV6 fault in mobile communication network and PCRF
CN106060900B (zh) * 2016-05-13 2019-12-10 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022481A (zh) * 2007-03-21 2007-08-22 华为技术有限公司 实现多点会议中私有会话的方法及装置
CN101790134A (zh) * 2009-01-23 2010-07-28 上海华为技术有限公司 建立会话的方法、装置及系统
CN104301287A (zh) * 2013-07-16 2015-01-21 中兴通讯股份有限公司 一种多对多会话的实现方法、网络节点、服务器及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MOTOROLA MOBILITY ET AL.: "Interim Agreement: Determination of NSSAI based on UE Policy", 3GPP SA WG2 MEETING #118 S2-166603, 8 November 2016 (2016-11-08), Reno, Nevada, pages 1 - 3, XP051199576 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3813301A4 (en) * 2018-05-31 2021-05-26 Huawei Technologies Co., Ltd. DATA TRANSFER METHOD, TERMINAL DEVICE AND NETWORK DEVICE
US11431807B2 (en) 2018-05-31 2022-08-30 Huawei Technologies Co., Ltd. Data transmission method, terminal device, and network device
WO2021052109A1 (zh) * 2019-09-19 2021-03-25 华为技术有限公司 通信方法及装置
CN113163468A (zh) * 2020-01-22 2021-07-23 中国电信股份有限公司 网络切片的接入方法、系统和终端

Also Published As

Publication number Publication date
US20190268422A1 (en) 2019-08-29
CN109964468B (zh) 2021-07-09
EP3515031A1 (en) 2019-07-24
CN109964468A (zh) 2019-07-02
EP3515031A4 (en) 2019-08-21
EP3515031B1 (en) 2021-04-07
US10834208B2 (en) 2020-11-10

Similar Documents

Publication Publication Date Title
WO2018086123A1 (zh) 会话处理方法、装置和系统
EP3720048B1 (en) User policy acquisition
EP3281453B1 (en) Method and control node for selection of a network partition and corresponding routing of a received message
WO2018205147A1 (zh) 一种基于切片的通信方法和设备
WO2020014214A1 (en) Core network assisted service discovery
US20210029509A1 (en) Positioning Method and Related Device
US10893410B2 (en) Method and device for establishing a peer-to-peer connection in a mobile communication network
WO2022215331A1 (en) Method of user equipment (ue), method of access and mobility management function (amf), method of unified data management (udm), ue, amf and udm
WO2022259830A1 (en) Method of user equipment (ue) and user equipment (ue)
CN109997379B (zh) 用于管理会话的方法
EP3409002B1 (en) Method and device for data communication over a peer-to-peer connection in a mobile communication network
US11089641B2 (en) Session continuity between software-defined network-controlled and non-software-defined network-controlled wireless networks
JP2024505266A (ja) 第１のコアネットワーク装置の方法、第２のコアネットワーク装置の方法、および無線アクセスネットワークの方法
WO2023068118A1 (en) Communication apparatus, first communication apparatus, method of communication apparatus, and method of first communication apparatus
WO2023238805A1 (en) Method of communication apparatus and communication apparatus
WO2023068119A1 (en) Method of ue, method of geographically selected amf apparatus, ue, geographically selected amf apparatus, and method of communication terminal
US20200195576A1 (en) Technique for Providing Content Via a Mobile Communications Network
JP2024542225A (ja) Ｕｅの方法、ｕｅ、ａｍｆの方法およびａｍｆ
JP2024529854A (ja) 無線端末により実行される方法及び無線端末

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: 16921082

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016921082

Country of ref document: EP

Effective date: 20190418

NENP Non-entry into the national phase

Ref country code: DE