WO2018170696A1 - 会话管理方法、接入管理功能设备和会话管理设备 - Google Patents

会话管理方法、接入管理功能设备和会话管理设备 Download PDF

Info

Publication number
WO2018170696A1
WO2018170696A1 PCT/CN2017/077371 CN2017077371W WO2018170696A1 WO 2018170696 A1 WO2018170696 A1 WO 2018170696A1 CN 2017077371 W CN2017077371 W CN 2017077371W WO 2018170696 A1 WO2018170696 A1 WO 2018170696A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
network element
terminal
session
flow
Prior art date
Application number
PCT/CN2017/077371
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
Priority to ES17902485T priority Critical patent/ES2851299T3/es
Priority to KR1020197029014A priority patent/KR102432103B1/ko
Priority to BR112019019352A priority patent/BR112019019352A2/pt
Priority to EP17902485.6A priority patent/EP3591999B1/en
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/077371 priority patent/WO2018170696A1/zh
Priority to CN202011096305.9A priority patent/CN112218341B/zh
Priority to AU2017405723A priority patent/AU2017405723B2/en
Priority to JP2019549427A priority patent/JP6888110B2/ja
Priority to CN201780087527.4A priority patent/CN110431862B/zh
Priority to KR1020217037974A priority patent/KR20210145318A/ko
Priority to EP20197358.3A priority patent/EP3826337B1/en
Publication of WO2018170696A1 publication Critical patent/WO2018170696A1/zh
Priority to US16/575,585 priority patent/US10980071B2/en
Priority to US17/226,398 priority patent/US11622395B2/en
Priority to US18/194,234 priority patent/US20230328813A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • 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/14—Backbone network devices

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a session management method, an access management function device, and a session management device.
  • next generation mobile communication network namely the 5th Generation (5G) mobile communication network.
  • 5G 5th Generation
  • 4G 4th Generation
  • 2G or 3G networks similar to 4G and 3G or 4G and 2G networks are adopted.
  • Inter-operating processes such as switching using Mobility Management (MM) context mapping or Session Management (SM) context mapping.
  • MM Mobility Management
  • SM Session Management
  • the embodiment of the present application provides a session management method, which can simplify the interoperation process between different communication networks.
  • a first aspect provides a session management method, including: an access and mobility management network element acquiring subscription data of a terminal in a first communication network and subscription data of the terminal in a second communication network, where The subscription data of the terminal in the first communication network includes a DNN, the subscription data of the terminal in the second communication network includes an APN corresponding to the DNN, and the access and mobility management network element corresponds to the APN.
  • the bearer allocation bearer identifier in the PDN connection; the access and mobility management network element receives the flow identifier of the flow in the PDU session corresponding to the DNN sent by the session management network element; the access and mobility management network The element sends the bearer identifier and the stream identifier to the terminal.
  • the access and mobility management network element reserves session resources for the second communication network, thereby simplifying the interoperation process between different communication networks.
  • the bearer in the PDN connection corresponding to the APN is a default bearer
  • the flow in the PDU session corresponding to the DNN is a default flow
  • the method further includes: the access and mobility management network element receiving the registration request message or the PDU sent by the terminal a session establishment request message; after the access and mobility management network element receives the registration request message or the PDU session establishment request message, the method further includes: the access and mobility management network element to the The session management network element sends a PDU session establishment request message, where the PDU session establishment request message includes a bearer identifier of the default bearer.
  • the default flow identifier is allocated to the default flow in the default flow establishment process in the PDU session, so that the session resource is reserved for the second communication network, and the interoperation process between the different communication networks is simplified.
  • the bearer in the PDN connection corresponding to the APN is a dedicated bearer
  • the flow in the PDU session corresponding to the DNN is a proprietary flow
  • the method further includes: the access and mobility management network element receiving the The private bearer sent by the session management NE And the access and mobility management network element sends a dedicated bearer identity allocation response message to the session management network element, where the dedicated bearer identity allocation response message includes a bearer identifier of the dedicated bearer.
  • the dedicated flow identifier is allocated to the private flow in the process of establishing a private flow in the PDU session, so that the session resource is reserved for the second communication network, and the mutual communication between the different communication networks is simplified. Operating procedures.
  • the method further includes: the access and mobility management network element receiving a handover request sent by the access network device; the accessing and moving The session management network element sends a session context request message to the session management network element; the access and mobility management network element receives a session context response message sent by the session management network element, where the session context response message includes: The bearer identifier and the policy and charging control rule of the default bearer in the PDN connection, and/or the bearer identifier and the policy and charging control rule of the dedicated bearer in the PDN connection; the access and mobility management network element Sending a relocation request to the mobility management entity, the location request includes indication information, the indication information being used to instruct the mobility management entity to reselect the serving gateway.
  • the first communication network reserves session management resources for the second communication network before the handover, and the first communication network sends the session management resources to the handover communication process.
  • the second communication network the second communication network can quickly build services according to these session management resources, ensure business continuity, and simplify the handover process.
  • a second aspect provides a session management method, including: a session management network element acquires a flow identifier of a flow in a PDU session corresponding to a DNN of the terminal, where the DNN is a subscription of the terminal in the first communication network. a DNN in the data; the session management network element acquires a bearer identifier of a bearer in a PDN connection corresponding to the APN of the terminal, where the APN is an APN in the subscription data of the terminal in the second communication network; The session management network element sends the bearer identifier and the flow identifier to an access and mobility management network element.
  • the bearer in the PDN connection corresponding to the APN is a default bearer
  • the flow in the PDU session corresponding to the DNN is a default flow
  • the session The management network element obtains the bearer identifier of the bearer in the PDN connection corresponding to the APN of the terminal, where the session management network element receives the PDU session establishment request message sent by the access and mobility management network element, where the PDU The session establishment request message includes the bearer identifier.
  • the bearer in the PDN connection corresponding to the APN is a dedicated bearer
  • the flow in the PDU session corresponding to the DNN is a proprietary flow
  • the session management network element receives the dedicated bearer identity allocation response message sent by the access and mobility management network element, where the dedicated bearer identity allocation response message includes the bearer identifier of the dedicated bearer.
  • the session management network element sends the bearer identifier and the flow identifier to the access and mobility management network element, including: The session management network element sends session management information to the access and mobility management network element, where the session management information includes an authorized QoS rule of the flow and an authorized QoS rule of the bearer, where The authorized QoS rule of the flow description includes the flow identifier, and the authorized QoS rule of the bearer includes the bearer identifier.
  • the session management network element acquires a flow identifier of the flow in the PDU session corresponding to the DNN of the terminal, including: the session management network element according to the The PCC rule of the terminal in the first communication network, the number of services corresponding to the PCC rule of the terminal in the first communication network According to the flow aggregation to the proprietary flow that has been established by the terminal, the flow identifier of the proprietary flow acquired by the session management network element is the flow identifier of the proprietary flow that the terminal has established.
  • the session management network element aggregates the service data flow corresponding to the PCC rule of the terminal in the first communication network to the proprietary established by the terminal according to the PCC rule of the terminal in the first communication network.
  • the number of dedicated flows in one PDU session is more than the number of dedicated bearers in one PDN connection, and a correspondence is established between the proprietary flow and the dedicated bearer.
  • the session management network element acquires a bearer identifier of the bearer in the PDN connection corresponding to the APN of the terminal, including: the session management network element Aggregating the service data flow corresponding to the PCC rule in the second communication network to the dedicated bearer that the terminal has established, according to the PCC rule of the terminal in the second communication network, the session management network
  • the bearer identifier of the dedicated bearer obtained by the element is the bearer identifier of the dedicated bearer that the terminal has established.
  • a policy and charging control method including: a policy and a charging network element acquiring a service requirement of a terminal; and the policy and charging network element sending a packet data unit connection access network PDU to the session management network element.
  • a CAN session management message the PDU-CAN session management message comprising a policy and charging control PCC rule of the terminal in the first communication network and the terminal in the second communication network.
  • the policy and charging network element receives a PDU-CAN session establishment request message sent by the session management network element, where the PDU-CAN session establishment request The message includes a subscription context corresponding to the DNN of the terminal in the first communication network and a PDN subscription context corresponding to the APN of the terminal in the second communication network.
  • the PCC rule of the terminal in the first communication network and the terminal in the second communication network includes: the terminal is in the first communication network a quality of service classification identifier, an authorized aggregated maximum bit rate Session-AMBR of the default stream in the PDU session corresponding to the DNN, a quality of service classification identifier of the terminal in the second communication network, and a corresponding APN The authorized APN-AMBR of the default bearer in the PDN connection.
  • the policy and the charging network element acquiring the service requirement of the terminal, including: the policy and the charging network element receiving the terminal or the application function
  • the service requirement sent by the network element, the service requirement includes at least one of Internet Protocol IP filtering information, media bandwidth requirements for QoS control, and application bandwidth requirements.
  • the PCC rule of the terminal in the first communication network and the terminal in the second communication network includes: the terminal is in the first communication network a quality of service classification identifier, a quality of service classification identifier of the terminal in the second communication network, and at least one of: an uplink and downlink packet filter, a guaranteed bit rate GBR, a maximum bit rate MBR, and a reservation and allocation priority ARP.
  • the service requirement further includes: a service continuity requirement.
  • the fourth aspect provides an access and mobility management device, including: an obtaining unit, configured to acquire subscription data of the terminal in the first communication network, and subscription data of the terminal in the second communication network, where The subscription data of the terminal in the first communication network includes a DNN, the subscription data of the terminal in the second communication network includes an APN corresponding to the DNN, and an allocation unit is configured to be in the PDN connection corresponding to the APN. And a receiving unit, configured to receive a flow identifier of a flow in the PDU session corresponding to the DNN sent by the session management network element, and a sending unit, configured to send the bearer identifier and the flow to the terminal Logo.
  • a fifth aspect provides an access and mobility management device, including: an obtaining unit, configured to acquire a flow identifier of a flow in a PDU session corresponding to a DNN of the terminal, and obtain a PDN connection corresponding to the APN of the terminal.
  • a bearer identifier of the bearer wherein the DNN is a DNN in the subscription data of the terminal in the first communication network, the APN is an APN in the subscription data of the terminal in the second communication network, and a sending unit, And the sending, by the access and mobility management network element, the bearer identifier and the flow identifier.
  • the sixth aspect provides a policy and charging control device, including: an obtaining unit, configured to acquire a service requirement of the terminal; and a sending unit, configured to send a PDU-CAN session management message to the session management network element, where the PDU-CAN session
  • the management message includes a policy and charging control PCC rule of the terminal in the first communication network and the terminal in the second communication network.
  • a seventh aspect a computer program product, comprising computer program instructions, when the computer program instructions are run on a computer, causing the computer to perform the method of any one of the first to third aspects .
  • FIG. 1 is a schematic diagram of an architecture of an application of the technical solution in the embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 3 is another schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a policy and charging control method according to an embodiment of the present application.
  • FIG. 5 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 6 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 7 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 8 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method for handover of a UE across a communication network according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of an access and mobility management device in accordance with an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a session management device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a policy and charging control device according to an embodiment of the present application.
  • FIG. 13 is another schematic structural diagram of an access and mobility management device according to an embodiment of the present application.
  • the terminal involved in the embodiments of the present application may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment). , UE), mobile station (MS), terminal device, and the like.
  • User Equipment User Equipment
  • UE user equipment
  • MS mobile station
  • terminal device and the like.
  • the present application only exemplifies the terminal as the UE.
  • the technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.
  • FIG. 1 is a schematic diagram of a communication architecture applied by the technical solution of the embodiment of the present application.
  • the UE accesses the core network through an Evolved Universal Terrestrial Radio Access Network (EUTRAN), and the UE can also pass a Next Generation Radio Access Network (NG).
  • the RAN) device accesses the core network.
  • the devices in the core network include a Mobility Management Entity (MME), a Serving Gateway (SGW), a subscription server, a policy and charging network element, a session management network element, and a user plane function network element.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • AMF Access and Mobility Management Function
  • each network element can be connected through an interface shown in the figure.
  • the MME and the AMF are connected through an Nx interface
  • the SGW and the user plane function network element are connected through an S5-U interface.
  • the subscription server is configured to store subscription data of the UE.
  • the subscription server may include a Home Subscriber Server (HSS) and Unified Data Management (UDM).
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • the HSS and UDM are deployed in one, and the UDM function can be added to the HSS, or the HSS function can be added to the UDM, or the HSS and UDM functions can be implemented simultaneously on the other device.
  • the contract server is represented by HSS+UDM.
  • the policy and charging network element includes a Policy and charging rules function (PCRF) and a policy control function (PCF).
  • PCRF Policy and charging rules function
  • PCF policy control function
  • the combination of PCRF and PCF can add PCF function in PCRF, or add PCRF function in PCF, or realize PCRF and PCF functions in another device.
  • Figure 1. Policy and charging network elements are represented by PCRF + PCF.
  • the session management network element includes a Session Management Function (SMF) and a Packet Data Network Gateway-Control Plane (PGW-C).
  • SMF Session Management Function
  • PGW-C Packet Data Network Gateway-Control Plane
  • SMF and PGW-C can be deployed together to add PGW-C functionality to SMF, or to add SMF functionality to PGW-C, or to implement SMF and PGW-C functions on another device.
  • the session management network element is represented by SMF + PGW-C.
  • the user plane function network element includes a User Plane Function (UPF) and a Packet Data Network Gateway-User plane (PGW-U).
  • UPF User Plane Function
  • PGW-U Packet Data Network Gateway-User plane
  • the combination of UPF and PGW-U can add PGW-U function in UPF, or add UPF function in PGW-U, or realize UPF and PGW-U functions in another device.
  • the session management network element is represented by UPF+PGW-U.
  • the communication architecture shown in Figure 1 includes a first communication network and a second communication network.
  • the first communication network includes AMF, UDM, PCF, SMF, and UPF.
  • the first communication network may be a 5G communication network.
  • the second communication network includes EUTRAN, MME, SGW, HSS, PCRF, PGW-C, and PGW-U.
  • the second communication network may be a 4.5G or 4G communication network.
  • the UE may access the first communication network or the second communication network, and may implement interoperation between the UE and the second communication network.
  • FIG. 2 is a schematic flowchart of a session management method according to an embodiment of the present application.
  • the session management method includes:
  • the access and mobility management network element acquires subscription data of the terminal in the first communication network and subscription data of the terminal in the second communication network.
  • the subscription data of the terminal in the first communication network includes a data network name (DNN), and the subscription data of the terminal in the second communication network includes an access point name corresponding to the DNN ( Access Point Name, APN).
  • the access and mobility management network element is an AMF.
  • the first communication network is a 5G communication network.
  • the second communication network can be a 4G communication network.
  • the subscription data of the terminal in the first communication network further includes a subscription context corresponding to the DNN
  • the subscription data of the terminal in the second communication network further includes the packet corresponding to the APN.
  • Packet Data Network (PDN) signing context PDN
  • the DNN includes a default DNN, and the APN includes a default APN, where the default DNN corresponds to the default APN.
  • the DNN includes a non-default DNN, and the APN includes a non-default APN. The non-default DNN corresponds to the non-default APN.
  • the access and mobility management network element acquires subscription data of the terminal in the first communication network and subscription data of the terminal in the second communication network, including: the access and mobility management network. Transmitting, by the meta-registration server, a location update request message, where the access and mobility management network element receives a location update response message sent by the subscription server, where the location update response message includes the terminal in the first communication network.
  • the subscription server is a UDM.
  • the access and mobility management network element sends a location update request to the subscription server, where the access and mobility management network element sends a first location update request to the UDM, where the access and The mobility management network element sends a second location update request to the UDM; the access and mobility management network element receives a location update response sent by the subscription server, and the location update response includes the terminal in the The subscription data in a communication network and the subscription data in the second communication network, comprising: the access and mobility management network element receiving a first location update response sent by the UDM, the first location update response Including the subscription data of the terminal in the first communication network, the access and mobility management network element receives a second location update response sent by the UDM, and the second location update response includes the second Signing data in the communication network.
  • the access and mobility management network element is a bearer (Default bearer) bearer identifier in the PDN connection corresponding to the APN.
  • the bearer identifier of the default bearer corresponds to the flow identifier of the default stream.
  • the bearer identifier of the default bearer corresponds to the flow identifier of the default stream.
  • the bearer identifier of the dedicated bearer corresponds to the flow identifier of the proprietary stream.
  • the bearer identifier of the dedicated bearer corresponds to the flow identifier of the proprietary flow
  • the bearer identifier of the dedicated bearer corresponds to the flow identifier of the flow of the plurality of proprietary flows, or the bearer of the multiple dedicated bearers is aggregated.
  • the bearer identifier corresponds to the stream identifier of a proprietary stream.
  • the bearer in the PDN connection corresponding to the APN is a default bearer
  • the flow in the PDU session corresponding to the DNN is a default flow.
  • the method further includes: the access and mobility management network element receiving the registration request sent by the terminal A message or PDU session setup request message.
  • the method further includes: the access and mobility management network element sends a PDU session to the session management network element. Establishing a request message, where the PDU session establishment request message includes a bearer identifier of the default bearer.
  • the session management network element is an SMF.
  • the registration request message or the PDU session establishment request message further includes indication information.
  • the indication information is used to indicate that the access and mobility management network element has the capability to communicate with the first communication network and the second communication network, and/or to indicate the access And the terminal of the mobility management network element has a single-rigistration or dual-registration capability.
  • the bearer in the PDN connection corresponding to the APN is a dedicated bearer
  • the flow in the PDU session corresponding to the DNN is a proprietary flow.
  • the method further includes: the access and mobility management network element receiving a private bearer identity allocation request message sent by the session management network element, where the access and mobility management network element sends a dedicated bearer identity allocation response message to the session management network element, where the dedicated bearer identity allocation response message is sent A bearer identifier of the proprietary bearer is included.
  • the PDU session establishment request message sent by the access and mobility management network element to the session management network element further includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN.
  • the optional PDU session establishment request message further includes indication information, where the indication information is used to indicate the session management network element
  • the terminal has the capability of communicating between the first communication network and the second communication network, and/or is used to indicate that the terminal management network element has a single registration capability.
  • the access and mobility management network element receives a flow identifier (flow ID) of a flow in a PDU session corresponding to the DNN sent by the session management network element.
  • flow ID flow identifier
  • the access and mobility management network element determines that the terminal has the first communication network and the The second communication network is capable of communicating and having an interface with the mobility management entity, and/or the terminal has a single registration capability.
  • the access and mobility management network element before the access and mobility management network element receives the session management message sent by the session management network element, the access and mobility management network element has the first communication network and the location according to the terminal.
  • the second communication network is capable of communicating and having an interface with the mobility management entity, and/or the terminal has a single registration capability, and the session management network element is selected.
  • the access and mobility management network element receives session management information sent by the session management network element, where the session management information includes an authorized quality of service (QoS) rule and a The authorized QoS rule of the bearer, wherein the authorized QoS rule of the flow includes the flow identifier, and the authorized QoS rule of the bearer includes the bearer identifier.
  • QoS quality of service
  • the session management information includes a flow identifier of the default flow, a Session-Aggregate Maximum Bit Rate (Session-AMBR) of the default flow, and a bearer identifier of the default bearer.
  • Session-AMBR Session-Aggregate Maximum Bit Rate
  • the session management information includes a flow identifier of a Guaranteed Bit Rate (GBR) flow, an uplink packet filter (UL Packet filter) of the GBR flow, a bearer identifier of the GBR dedicated bearer, and the Traffic flow template (TFT) of GBR proprietary bearer.
  • GRR Guaranteed Bit Rate
  • UL Packet filter uplink packet filter
  • TFT Traffic flow template
  • the uplink packet filter and the uplink service template stream are consistent in content.
  • the access and mobility management network element sends the bearer identifier and the flow identifier to the terminal.
  • the access and mobility management network element sends the session management information to the terminal, where the session management information includes the bearer identifier and the flow identifier.
  • the method in this embodiment further includes: the access and mobility management network element receives a handover request sent by the access network device; the access and mobility management network element sends a session to the session management network element. a context request message; the access and mobility management network element receives a session context response message sent by the session management network element, where the session context response message includes: a bearer identifier and a policy and a default bearer in the PDN connection a Policy and Charging Control (PCC) rule, and/or a bearer identifier and a PCC rule of a dedicated bearer in the PDN connection; the access and mobility management network element sends the mobility management entity to the mobility management entity a relocation request, the relocation request including indication information, the indication information being used to instruct the mobility management entity to reselect a serving gateway.
  • the address information of the serving gateway may also be set to 0.0.0.0, thereby instructing the mobility management network element to reselect the serving gateway.
  • FIG. 3 is another schematic flowchart of a session management method according to an embodiment of the present application.
  • the session management method includes:
  • the session management network element acquires a flow identifier of a flow in a PDU session corresponding to the DNN of the terminal, where the DNN is a DNN in the subscription data of the terminal in the first communication network.
  • the session management network element allocates a flow identifier for the flow in the PDU session corresponding to the DNN of the terminal.
  • the session management network element aggregates the service data flow corresponding to the PCC rule of the terminal in the first communication network to the terminal that has been established according to the PCC rule of the terminal in the first communication network.
  • the flow identifier of the proprietary flow obtained by the session management network element is the flow identifier of the proprietary flow that the terminal has established.
  • the session management network element acquires the bearer identifier of the bearer in the PDN connection of the packet data network corresponding to the access point name APN of the terminal, where the APN is the subscription data of the terminal in the second communication network. APN.
  • the subscription data of the terminal in the first communication network further includes a subscription context corresponding to the DNN
  • the subscription data of the terminal in the second communication network further includes a PDN subscription context corresponding to the APN
  • the PDU session establishment request message received by the session management network element further includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN.
  • the PDU session establishment request message further includes indication information, where the indication information is used to indicate that the terminal management network element has the capability of communicating between the first communication network and the second communication network. And/or for indicating that the terminal management network element has a single registration capability.
  • the bearer in the PDN connection corresponding to the APN is a default bearer
  • the flow in the PDU session corresponding to the DNN is a default flow.
  • the session management network element aggregates, according to the PCC rule of the terminal in the second communication network, the service data flow corresponding to the PCC rule of the terminal in the second communication network to the terminal that has been established.
  • the bearer identifier of the dedicated bearer obtained by the session management network element is the bearer identifier of the dedicated bearer that the terminal has established.
  • the bearer in the PDN connection corresponding to the APN is a dedicated bearer
  • the flow in the PDU session corresponding to the DNN is a private flow
  • the session management network element acquires the packet data corresponding to the APN of the terminal.
  • the bearer identifier of the bearer in the network PDN connection includes: the session management network element sends a dedicated bearer identity allocation request message to the access and mobility management network; the session management network element receives the access and the mobile The dedicated bearer identifier allocation response message sent by the sex management network element, where the dedicated bearer identity allocation response message carries the bearer identifier of the dedicated bearer.
  • the session management network element sends the bearer identifier and the flow identifier to the access and mobility management network element.
  • the session management network element sends the bearer identifier and the flow identifier to the access and mobility management network element, including: the session management network element to the access and mobility management network
  • the session sends the session management information, where the session management information includes the authorized quality of service QoS rule of the flow and the authorized QoS rule of the bearer, where the authorized QoS rule of the flow includes the flow identifier
  • the bearer authorized QoS rule includes the bearer identifier.
  • the session management information includes a flow identifier of the default flow, an authorized Session-AMBR of the default flow, a bearer identifier of the default bearer, and an authorized APN-AMBR of the default bearer.
  • the session management information includes a flow identifier of the GBR flow, an uplink packet filter (UL Packet filter) of the GBR flow, a bearer identifier of the GBR dedicated bearer, and an uplink service template flow of the GBR dedicated bearer. (Traffic Flow Template, TFT).
  • the uplink packet filter and the uplink service template stream are consistent in content.
  • the method in this embodiment may further include: the session management network element sends a PDU Connectivity Access Network (PDU-CAN) session establishment request message to the policy and charging network element, where the PDU- The CAN session establishment request message includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN; the session management network element receives a PDU-CAN session establishment response message sent by the policy and the charging network element, The PDU-CAN session setup response message includes a policy and charging control PCC rule of the terminal in the first communication network and the second communication network.
  • the PDU-CAN session establishment request message further includes indication information, where the indication information is used to indicate that the policy and the charging network element have the terminal in the first communication network and the second communication network. The ability to communicate, and/or to indicate that the policy and the charging network element have a single registration capability.
  • the PCC rule includes a QoS Class Identifier (QCI) of the terminal in the first communication network network, a QCI of the terminal in the second communication network, and at least one of: an uplink and a downlink packet filter.
  • QCI QoS Class Identifier
  • UL+DL Packet filters Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), and Allocation and Retention Priority (ARP).
  • the method in this embodiment may further include: the session management network element receives a PDU-CAN session modification request message sent by the policy and the charging network element, where the PDU-CAN session establishment response message includes the terminal being The policy and charging control PCC rules in the first communication network and the second communication network.
  • the policy and charging network element is a PCF.
  • FIG. 4 is a schematic flowchart of a policy and charging control method according to an embodiment of the present application.
  • the policy and charging control method includes:
  • the policy and charging network element obtains the service requirements of the terminal.
  • the policy and the charging network element acquire the service requirement of the terminal, where the policy and the charging network element receive the PDU-CAN session establishment request message sent by the session management network element, where the PDU-CAN session is established.
  • the request message includes a subscription context corresponding to the data network name DNN of the terminal in the first communication network and a packet data network PDN subscription context corresponding to the access point name APN of the terminal in the second communication network.
  • the PDU-CAN session establishment request message further includes indication information, where the indication information is used to indicate that the policy and the charging network element have the terminal in the first communication network and the second communication network. The ability to communicate, and/or to indicate that the policy and the charging network element have a single registration capability.
  • the policy and the charging network element acquiring the service requirement of the terminal, where the policy and the charging network element receive the service request sent by the terminal or the application function network element, where the service request includes the Internet At least one of protocol IP filtering information, media bandwidth requirements for QoS control, and application bandwidth requirements.
  • the application function network element is an Application Function (AF).
  • the policy and charging network element receives the PDU-CAN session modification request from the session management network element or receives the service notification message from the application function. The policy and charging network element receives the PDU from the session management network element.
  • the CAN session modification request occurs in the UE-initiated private flow establishment process, and the policy and charging network element receives the service notification message from the application function and occurs in the AF-initiated private flow.
  • the PDU-CAN session modification request or service notification message includes the service requirements of the terminal.
  • the service requirement further includes: a service continuity requirement.
  • the policy and charging network element sends a PDU-CAN session management message to the session management network element, where the PDU-CAN session management message includes a policy of the terminal in the first communication network and the terminal in the second communication network.
  • the billing control PCC rules With the billing control PCC rules.
  • the PDU-CAN session management message is a PDU-CAN session setup response message.
  • the PCC rule of the terminal in the first communication network and the terminal in the second communication network includes: the terminal is in the QCI of the first communication network, and the authorization of the default stream in the PDU session corresponding to the DNN is - The AMBR, the QCI of the terminal in the second communication network, and the authorized APN-AMBR of the default bearer in the PDN connection corresponding to the APN.
  • the PDU-CAN session management message is a PDU-CAN session modification response message or a PDU-CAN session modification request message.
  • the PDU-CAN session management message occurs in the UE-initiated private flow establishment process for the PDU-CAN session modification response message, and the PDU-CAN session management request message occurs in the AF-initiated proprietary flow establishment process.
  • the PCC rules of the terminal in the first communication network and the terminal in the second communication network include: the QCI of the terminal in the first communication network, the QCI of the terminal in the second communication network, and at least one of: Uplink and downlink packet filters (UL+DL Packet filters), GBR, MBR and ARP.
  • UL+DL Packet filters Uplink and downlink packet filters
  • the first communication network is a 5G communication network
  • the second communication network is a 4G network.
  • the step flow and the network element related to the present application are shown in the embodiment of the present application, and other technical contents well known to those skilled in the art are not shown in the drawings.
  • the drawing does not show an access network device for transmitting and receiving information with a UE through an air interface.
  • SMF, PCF, UPF, and UDM are respectively used to represent the case where the corresponding core network devices in the 5G network and the 4G network are deployed in a unified manner.
  • FIG. 5 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • the content similar to the embodiment of FIG. 2 to FIG. 4 is described in the text corresponding to the embodiment of FIG. 2 to FIG. 4, and details are not described herein again.
  • FIG. 5 shows a session management method of the UE during the registration process.
  • the session management method of this embodiment includes:
  • the UE sends a registration request (Registration Request) to the AMF.
  • the registration request may include indication information, where the indication information is used to indicate that the UE has the capability to communicate on the 5G and 4G networks, and/or to indicate that the AMF UE has the capability of single registration or dual registration.
  • the UE completes an authentication and security process with the network side device.
  • the AMF sends a location update request (update location request) message to the UDM.
  • the AMF sends a location update request message to the UDM.
  • the location update request message includes indication information for indicating that the UE has the capability to communicate on the 5G and 4G networks.
  • the indication information may be an interoperation indication information.
  • the AMF when the HSS and the UDM are deployed in a unified manner, the AMF sends a first location update request and a second location update request message to the UDM, respectively.
  • the AMF may initiate a location update procedure.
  • the AMF receives a location update response (update location response) message sent by the UDM.
  • the location update response message includes subscription data of the UE in the 5G network and subscription data in the 4G network.
  • the subscription data in the 5G network includes the DNN
  • the subscription data in the 4G network includes the APN.
  • the DNN includes a default DNN, and the APN includes a default APN.
  • the DNN includes a non-default DNN, and the APN includes a non-default APN.
  • the subscription data in the 5G network may include only one default DNN.
  • the subscription data in the 5G network may also include one or more non-default DNNs.
  • the subscription data in the 4G network may include only one default APN.
  • the subscription data in the 4G network may also include one or more non-default APNs, such as an IP Multimedia Subsystem (IMS) APN or a non-third generation partnership program (3rd). Generation Partnership Project, 3GPP) APN.
  • IMS IP Multimedia Subsystem
  • 3rd Generation Partnership Project
  • the default DNN and the default APN are in one-to-one correspondence, and the non-default DNN and the non-default APN are in one-to-one correspondence.
  • Non-default DNNs and non-default APNs may also have no one-to-one correspondence. For example: the number of non-default DNNs is greater than the number of non-default APNs.
  • only one default stream may be included in a session corresponding to the DNN.
  • One or more proprietary streams may also be included in one PDU session corresponding to the DNN.
  • a PDN connection corresponding to the APN may include only one default bearer.
  • One or more dedicated bearers may also be included in one PDN connection corresponding to the DNN.
  • the subscription data of the UE in the 5G network further includes a subscription context corresponding to the DNN.
  • the subscription data of the UE in the 4G network further includes a PDN subscription context corresponding to the APN.
  • the PDN subscription context includes QoS parameters, such as a subscription APN-AMBR and/or a subscription QoS profile.
  • the location update response received by the AMF includes a correspondence between the DNN and the APN.
  • the correspondence between the DNN and the APN can be represented by a list, and the corresponding relationship can be reflected by the positional relationship between the DNN and the APN in the message, and details are not described herein again.
  • the AMF may obtain the correspondence between the DNN and the APN according to the domain name in the subscription data of the UE in the 5G and 4G networks.
  • the PDN signing context includes 4g.ims.org
  • the DNN corresponding contracting context includes 5g.ims.org
  • AMF includes ims.org according to the domain name to correspond to DNN and APN.
  • the AMF receives the location update response sent by the UDM.
  • the location update response includes subscription data of the UE in the 5G network and subscription data in the 4G network.
  • the AMF respectively receives the first location update response and the second location update response sent by the UDM.
  • the first location update response includes subscription data of the UE in the 5G network
  • the second location update response includes subscription data of the UE in the 4G network.
  • the 505 AMF allocates a bearer ID to the default bearer in the PDN connection corresponding to the APN.
  • the AMF sends a PDU Session Setup Request message to the SMF.
  • the PDU session establishment request message includes a bearer identifier of a default bearer allocated by the AMF.
  • the PDU session establishment request message may further include indication information.
  • the indication information is used to indicate that the UE has the capability to communicate on the 5G and 4G networks, and/or to indicate that the SMF UE has a single registration capability.
  • the PDU session establishment request message may further include a PDN subscription context corresponding to the APN and a subscription context corresponding to the DNN.
  • the UE may have the capability of communicating on the 5G and 4G networks and the communication interface between the AMF and the MME, and/or the UE has a single registration capability, and the UE may have a single registration capability. SMF.
  • the 507 SMF allocates a flow identifier for the default stream in the PDU session corresponding to the DNN.
  • the flow identifier of the default flow allocated by the SMF is in one-to-one correspondence with the bearer identifier of the default bearer allocated by the AMF.
  • the 508 SMF obtains the PCC rules of the UE in the 5G and 4G networks through the PDU-CAN session establishment procedure.
  • the PCC rule includes the QCI of the UE in the 5G network, the AMBR after the PDU session authorization corresponding to the DNN, the QCI of the UE in the 4G network, the AMBR after the PDN connection authorization corresponding to the APN, and the ARP.
  • the SMF sends a PDU-CAN session establishment request message to the PCF.
  • the PDU-CAN session establishment request message includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN, and may further include indication information, where the indication information is used to indicate that the UE has the capability to communicate on the 5G and 4G networks, and/or For Indicates that the PCF UE has a single registration capability.
  • the SMF receives the PDU-CAN Session Setup Response message sent by the PCF, wherein the PDU-CAN Session Setup Response message includes the PCC rules of the UE in the 5G and 4G networks.
  • step 507 may be performed first and then step 508 may be performed, or step 508 may be performed first and then step 507 may be performed, which is not limited herein.
  • the 509 SMF sends a PDU session setup response message to the AMF.
  • the PDU session establishment response message includes a flow identifier of a default flow in the PDU session corresponding to the DMN allocated by the SMF.
  • the PDU session setup response message may further include the AMF assigning a bearer identifier to the default bearer in the PDN connection corresponding to the APN.
  • the PDU session establishment response message may further include session management information.
  • the session management information includes a QoS rule after the default flow authorization in the PDU session and a QoS rule after the default bearer authorization in the PDN connection.
  • the default traffic authorization QoS rule in the PDU session includes the flow identifier of the default flow
  • the default bearer authorization QoS rule in the PDN connection includes the bearer identifier of the default bearer.
  • the QoS rule after the default flow authorization in the PDU session may further include an AMBR after the PDU session is authorized.
  • the default QoS rule for the bearer in the PDN connection includes the AMBR after the PDN connection is authorized.
  • the AMF sends a registration accept message to the UE.
  • the registration accept message includes a flow identifier of a default flow allocated by the SMF and a bearer identifier of a default bearer allocated by the AMF.
  • the registration accept message may further include a QoS rule after the default flow authorization in the PDU session and a QoS rule after the default bearer authorization in the PDN connection.
  • the registration accepts the session management information included in the PDU session establishment response message.
  • the AMF obtains the subscription data of the UE in the 5G network and the 4G network in advance, and in the PDU session establishment process of the 5G network, the AMF allocates the corresponding flow in the 4G network to the default flow in the session.
  • the default bearer avoids the mapping between the default stream in the PDU session in the 5G network and the default bearer in the PDN connection in the 4G network.
  • FIG. 6 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • the content similar to the embodiment of FIG. 2 to FIG. 5 is described in the text corresponding to the embodiment of FIG. 2 to FIG. 5 , and details are not described herein again.
  • FIG. 6 shows a session management method in a process in which a UE actively initiates a PDU session.
  • the session management method of this embodiment includes:
  • the UE sends a PDU Session Establishment Request message to the AMF.
  • the PDU session establishment request message may include indication information.
  • the indication information is used to indicate that the UE has the capability to communicate on the 5G and 4G networks and/or to indicate that the SMF UE has the capability of single registration or dual registration.
  • the AMF allocates a bearer identifier to the default bearer in the PDN connection corresponding to the APN.
  • the AMF sends a PDU Session Setup Request message to the SMF.
  • This step is similar to the content of step 506, and details are not described herein again.
  • the 604 SMF allocates a flow identifier for the default stream in the PDU session corresponding to the DNN.
  • This step is similar to the content of step 507, and details are not described herein again.
  • the 605 SMF obtains the PCC rules of the UE in the 5G and 4G networks through the PDU-CAN session establishment procedure.
  • This step is similar to the content of step 508, and details are not described herein again.
  • the SMF sends a session establishment request message to the UPF.
  • the session establishment request message includes indication information, where the indication information is used to indicate that the UE has the capability to communicate on the 5G and 4G networks.
  • the session establishment request message may be an N4 session establishment request message.
  • the SMF sends an N4 session establishment request message to the UPF, and the SMF sends an Sxb session establishment request message to the PGW-U.
  • the SMF receives the session establishment response message sent by the UPF.
  • the session establishment response message includes a tunnel ID of the UPF and a tunnel ID of the PGW-U.
  • the SMF receives the session establishment response message sent by the UPF through the N4 interface, where the session establishment response message includes the tunnel ID of the UPF.
  • the SMF receives the session establishment response message sent by the PGW-U through the Sxb interface, and the session establishment response message includes the tunnel ID of the PGW-U.
  • the SMF establishes a channel for data transmission with the UPF.
  • the 608 SMF sends a PDU session setup response message to the AMF.
  • This step is similar to the content of step 509, and details are not described herein again.
  • the AMF sends a PDU Session Setup Accept message to the UE.
  • the PDU session establishment accept message includes a flow identifier of a default flow allocated by the SMF and a bearer identifier of a default bearer allocated by the AMF.
  • the PDU session establishment accept message may further include a QoS rule after the default flow authorization in the PDU session and a QoS rule after the default bearer authorization in the PDN connection.
  • the PDU session establishment accept message includes the session management information included in the PDU session setup response message in step 608.
  • the 610 AMF receives a PDU Session Establishment Confirmation (ACK) message sent by the UE.
  • ACK PDU Session Establishment Confirmation
  • the AMF allocates a corresponding default bearer in the 4G network for the default flow in the session, and avoids using the mapping method to establish a default flow in the PDU session in the 5G network.
  • the corresponding bearer relationship in the PDN connection in the 4G network is simpler. For example, when the UE switches from a 5G network to a 4G network, the process is simpler.
  • FIG. 7 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • the content similar to the embodiment of FIG. 2 to FIG. 6 is described in the text corresponding to the embodiment of FIG. 2 to FIG. 6 , and details are not described herein again.
  • FIG. 7 shows a flow of a dedicated (Dedicate) flow establishment in a UE initiated PDU session.
  • the session management method of this embodiment includes:
  • the UE sends a PDU session modification request message to the AMF.
  • the PDU session modification request message includes a service requirement of the UE.
  • the service requirements include at least one of Internet Protocol (IP) filtering information, media bandwidth requirements for QoS control, and application bandwidth requirements.
  • IP Internet Protocol
  • the business requirements may also include business continuity requirements.
  • the AMF sends a PDU session modification request message to the SMF.
  • the 703 SMF obtains the PCC rules of the UE in the 5G and 4G networks through the PDU-CAN session modification procedure.
  • the PCC rule includes a QCI of the UE in the 5G network, a QCI of the UE in the 4G network, and at least one of the following: an uplink and a downlink packet filter (UL+DL Packet filters), a GBR, an MBR, and an ARP.
  • the UE may use the same uplink and downlink packet filters (UL+DL Packet filters), GBR, MBR, and ARP parameters in the 5G and 4G networks.
  • the SMF sends a PDU-CAN session modification request message to the PCF, where the PDU-CAN session establishment request message includes a service requirement of the UE.
  • the PCF generates the 5G and 4G networks for the UE according to the service requirements of the UE. PCC rules in .
  • the SMF receives the PDU-CAN Session Setup Response message sent by the PCF, wherein the PDU-CAN Session Setup Response message includes the PCC rules of the UE in the 5G and 4G networks.
  • the PCF may also receive a service notification message sent by an application function (AF), where the service notification message includes a service requirement of the UE.
  • the PCF sends a PDU-CAN Session Modification Request message to the SMF, wherein the PDU-CAN Session Modification Request message includes the PCC rules of the UE in the 5G and 4G networks.
  • AF application function
  • the PCF sends a PDU-CAN Session Modification Request message to the SMF, wherein the PDU-CAN Session Modification Request message includes the PCC rules of the UE in the 5G and 4G networks.
  • the SMF sends a dedicated bearer identity allocation request message to the AMF.
  • the AMF allocates a bearer identifier to a dedicated bearer in the PDN connection corresponding to the APN.
  • the AMF sends a dedicated bearer identity allocation response message to the SMF.
  • the dedicated bearer identity allocation response message includes a bearer identifier of the dedicated bearer allocated by the AMF.
  • the 707 SMF allocates a flow identifier for the proprietary stream in the PDU session corresponding to the DNN.
  • step 703, steps 704-706, and step 707 may be interchanged, and is not limited herein.
  • the SMF sends a PDU session modification accept message to the AMF.
  • the PDU session modification accept message includes a flow identifier of a proprietary stream in the PDU session corresponding to the DMN allocated by the SMF.
  • the SMF generates QoS rules of the UE in the 5G and 4G networks according to the PCC rules of the UE in the 5G and 4G networks.
  • the PDU session modification accept message may further include session management information.
  • the session management information includes a QoS rule after the private stream authorization in the PDU session and a QoS rule after the dedicated bearer authorization in the PDN connection.
  • the QoS rule after the private stream authorization in the PDU session includes the flow identifier of the proprietary flow
  • the QoS rule after the dedicated bearer authorization in the PDN connection includes the bearer identifier of the dedicated bearer.
  • the proprietary flow is a GBR flow
  • the dedicated bearer is a GBR bearer.
  • the QoS rule after the proprietary flow authorization includes the UL packet filter of the GBR flow
  • the QoS rule of the dedicated bearer authorization includes the traffic flow template (TFT) carried by the GBR.
  • TFT traffic flow template
  • the uplink packet filter and the uplink service template stream are consistent in content.
  • the AMF sends a PDU Session Modification Accept message to the UE.
  • the session modification accept message includes a flow identifier of the proprietary stream allocated by the SMF and a bearer identifier of the dedicated bearer allocated by the AMF.
  • the session modification accept message may further include a QoS rule after the private stream authorization in the PDU session and a QoS rule after the dedicated bearer authorization in the PDN connection.
  • the session establishment accept message includes the session management information included in the PDU session modification accept message in step 708.
  • the AMF receives a session modification acknowledgement (ACK) message sent by the UE.
  • ACK session modification acknowledgement
  • the AMF sends a session modification confirmation message to the SMF.
  • the SMF sends a session establishment request message to the UPF.
  • This step is similar to step 606 and will not be described here.
  • the 713 SMF receives the session establishment response message sent by the UPF.
  • the response message includes a tunnel ID of the UPF and a tunnel ID of the PGW-U.
  • This step is similar to step 607 and will not be described here.
  • the AMF allocates the corresponding dedicated bearer in the 4G network for the proprietary stream in the session, thereby avoiding the use of the mapping method to establish the 5G network.
  • PDU will The correspondence between the proprietary stream in the voice and the proprietary bearer in the PDN connection in the 4G network.
  • FIG. 8 is still another schematic flowchart of a session management method according to an embodiment of the present application.
  • the content similar to the embodiment of FIG. 2 to FIG. 7 is described in the text corresponding to the embodiment of FIG. 2 to FIG. 7, and details are not described herein again.
  • FIG. 8 illustrates another flow of UE-initiated private stream establishment in a PDU session.
  • the session management method of this embodiment includes:
  • Steps 801-803 of this embodiment are similar to steps 701-703, and are not described herein again.
  • the 804 SMF allocates a flow identifier for the proprietary stream in the PDU session corresponding to the DNN.
  • the 805 SMF sends a PDU session modification accept message to the AMF.
  • the PDU session modification accept message includes a flow identifier of a proprietary stream in the PDU session corresponding to the DMN allocated by the SMF.
  • the SMF generates QoS rules of the UE in the 5G and 4G networks according to the PCC rules of the UE in the 5G and 4G networks.
  • the PDU session modification accept message may further include session management information.
  • the session management information includes a QoS rule after the private stream authorization in the PDU session and a QoS rule after the dedicated bearer authorization in the PDN connection.
  • the QoS rule after the private stream authorization in the PDU session includes the flow identifier of the proprietary stream.
  • the proprietary flow is a GBR flow
  • the dedicated bearer is a GBR bearer.
  • the QoS rule after the proprietary flow authorization includes the UL packet filter of the GBR flow
  • the QoS rule of the dedicated bearer authorization includes the traffic flow template (TFT) carried by the GBR.
  • TFT traffic flow template
  • the uplink packet filter and the uplink service template stream are consistent in content.
  • the AMF allocates a bearer identifier to a dedicated bearer in the PDN connection corresponding to the APN.
  • the AMF sends a PDU Session Modification Accept message to the UE.
  • the PDU session modification accept message includes a flow identifier of the proprietary stream allocated by the SMF and a bearer identifier of the dedicated bearer allocated by the AMF.
  • the session modification accept message may further include a QoS rule after the private stream authorization in the PDU session and a QoS rule after the dedicated bearer authorization in the PDN connection.
  • the session establishment accept message includes a bearer identifier of the dedicated bearer allocated by the AMF and session management information included in the PDU session modification accept message in step 805.
  • Steps 808-811 of this embodiment are similar to steps 710-713. The difference is that, in step 809, the PDU session modification confirmation message includes the bearer identifier of the dedicated bearer allocated by the AMF.
  • the SMF in the process of establishing a proprietary flow in a PDU session initiated by the UE, the SMF first allocates a flow identifier for the proprietary flow in the PDU session corresponding to the DNN, and then sends the identifier of the proprietary flow to the AMF, saving
  • the process of the dedicated bearer identity allocation request message and the dedicated bearer identity allocation response message in FIG. 7 is simpler.
  • the SMF assigns a stream identification to the proprietary stream.
  • the present application may also provide an alternative solution: the SMF aggregates the service data flow corresponding to the PCC rule of the UE in the 5G network to a proprietary flow that the UE has established according to the PCC rule of the UE in the 5G network, and the SMF will UE.
  • the stream identifier of the established private stream is used as the identifier of the proprietary stream to be established.
  • the SMF may determine, according to the QCI and the ARP in the PCC rule, whether to aggregate the service data flow corresponding to the PCC rule into a proprietary flow that the UE has established.
  • traffic data flows can be aggregated into a private stream that has been established with the same QCI and ARP.
  • the alternative solution can be applied to the case where the number of private flows in one PDU session in the 5G network is greater than the number of dedicated bearers in one PDN connection in the 4G network, thereby preventing the proprietary flows and the dedicated bearers from being able to Build one by one Correspondence problem.
  • the proprietary flow and the dedicated bearer can establish a one-to-one correspondence, the present alternative solution can also be adopted, which is not limited herein.
  • the AMF allocates a bearer identity for the dedicated bearer.
  • the present application may also provide an alternative solution: the SMF aggregates the service data flow corresponding to the PCC rule of the UE in the 4G network to a dedicated bearer that the UE has established according to the PCC rule of the UE in the 4G network, and the SMF will UE.
  • the bearer identifier of the established dedicated bearer is used as the identifier of the dedicated bearer corresponding to the service data flow.
  • the SMF may determine, according to the QCI and the ARP in the PCC rule, whether to aggregate the service data flow corresponding to the PCC rule into a dedicated bearer that the UE has established. For example, traffic data flows can be aggregated into a dedicated bearer with the same QCI and ARP that has been established.
  • the embodiment of the present application further provides a process for establishing a private flow in a PDU session initiated by a network side.
  • the session management method in this embodiment includes:
  • the PCF receives the service request of the UE sent by the application function network element.
  • the service requirements include at least one of IP filtering information, media bandwidth requirements for QoS control, and application bandwidth requirements.
  • the business requirements may include business continuity requirements.
  • the PCF generates PCC rule PCC rules in the 5G and 4G networks for the UE according to the service requirements of the UE.
  • the PCC rule includes a QCI of the UE in the 5G network, a QCI of the UE in the 4G network, and at least one of the following: an uplink and a downlink packet filter, a GBR, an MBR, and an ARP.
  • the PCF sends a PDU-CAN Session Modification Request message to the SMF.
  • the PDU-CAN session modification request message includes the PCC rules of the UE in the 5G and 4G networks.
  • next steps in this embodiment are similar to steps 704-713 or 804-811, and are not described herein again.
  • FIG. 9 is a schematic flowchart of a handover of a UE across a communication network according to an embodiment of the present application. The method includes:
  • the UE completes the process of PDU session and flow establishment in the 5G network.
  • the access network device in the 5G network sends a handover request to the AMF.
  • the AMF sends a session context request message to the SMF.
  • the AMF receives the session context response message sent by the SMF.
  • the session context response message includes a bearer identifier and a PCC rule of a default bearer in the PDN connection, and/or a bearer identifier and a PCC rule of the dedicated bearer in the PDN connection.
  • the 905 AMF sends a relocation request to the MME.
  • the relocation request includes indication information, where the indication information is used to instruct the MME to reselect the SGW.
  • the address information of the SGW may also be set to 0.0.0.0, thereby instructing the MME to reselect the SGW.
  • the MME sends a session establishment request message to the selected SGW.
  • the MME receives the session establishment response message sent by the SGW.
  • the 5G network side reserves session management resources for the 4G network.
  • the 5G network brings these session management resources to the 4G network, and the 4G network. Manage resources based on these sessions to quickly build services, ensure business continuity, and simplify the switching process.
  • FIG. 10 is a schematic block diagram of an access and mobility management device in accordance with an embodiment of the present application.
  • the access and mobility management device includes an obtaining unit 1001, an allocating unit 1002, a receiving unit 1003, and a transmitting unit 1004.
  • the obtaining unit 1001 and the allocating unit 1002 may be processors of an access and mobility management device
  • the receiving unit 1003 and the sending unit 1004 may be an access and mobility management device for transmitting and receiving information.
  • Communication Interface Specifically, the receiving unit 1003 and the sending unit 1004 can refer to the communication interface of the access and mobility tube network element in the communication architecture shown in FIG. 1.
  • the obtaining unit 1001 is configured to acquire subscription data of the terminal in the first communication network and subscription data of the terminal in the second communication network.
  • the subscription data of the terminal in the first communication network includes a data network name DNN
  • the subscription data of the terminal in the second communication network includes an access point name APN corresponding to the DNN.
  • the subscription data of the terminal in the first communication network further includes a subscription context corresponding to the DNN
  • the subscription data of the terminal in the second communication network further includes a PDN subscription context corresponding to the APN
  • the PDU session establishment request message sent by the sending unit to the session management network element further includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN.
  • the allocating unit 1002 is configured to allocate a bearer identifier for the bearer in the PDN connection corresponding to the APN.
  • the receiving unit 1003 is configured to receive a flow identifier of a flow in the PDU session corresponding to the DNN sent by the session management network element.
  • the sending unit 1004 is configured to send the bearer identifier and the stream identifier to the terminal.
  • the receiving unit 1003 is further configured to receive a registration request message or a PDU session establishment request message sent by the terminal before the bearer identifier is allocated to the bearer in the PDN connection corresponding to the APN; the sending unit is further used to After receiving the registration request message or the PDU session establishment request message, the receiving unit sends a PDU session establishment request message to the session management network element, where the bearer in the PDN connection corresponding to the APN is a default bearer.
  • the flow in the PDU session corresponding to the DNN is a default flow, and the PDU session establishment request message includes a bearer identifier of the default bearer.
  • the receiving unit 1003 is further configured to receive a dedicated bearer identity allocation request message sent by the session management network element, where the sending unit is further configured to send a dedicated bearer identity allocation response message to the session management network element, where
  • the bearer in the PDN connection corresponding to the APN is a dedicated bearer, and the flow in the PDU session corresponding to the DNN is a private flow, and the dedicated bearer identity allocation response message includes a bearer identifier of the dedicated bearer.
  • the receiving unit 1003 is configured to receive session management information that is sent by the session management network element, where the session management information includes an authorized quality of service QoS rule of the flow and an authorized QoS rule of the bearer, where The authorized QoS rule of the flow includes the flow identifier, and the authorized QoS rule of the bearer includes the bearer identifier.
  • the sending unit 1004 is further configured to send a location update request message to the subscription server; the receiving unit is further configured to receive a location update response message sent by the subscription server, where the location update response message includes the terminal in the The subscription data in a communication network and the subscription data of the terminal in the second communication network.
  • the receiving unit 1003 is further configured to receive a handover request sent by the access network device, where the sending unit is further configured to send a session context request message to the session management network element, where the receiving unit is further configured to receive the session management a session context response message sent by the network element, where the session context response message includes: a bearer identifier and a policy and charging control rule of a default bearer in the PDN connection, and/or a bearer identifier of a dedicated bearer in the PDN connection And the policy and charging control rule; the sending unit is further configured to send a positioning request to the mobility management entity, where the positioning request includes indication information, where the indication information is used to instruct the mobility management entity to reselect the serving gateway.
  • the obtaining unit 1001 and the allocating unit 1002 in this embodiment are also used to implement the functions of the access and mobility management device in the embodiments of FIGS. 2-9 regarding data and signal processing.
  • the receiving unit 1003 and the sending unit 1004 are also used to implement the functions of the access and mobility management network elements for transmitting and receiving information in the embodiments of FIG. 2-9.
  • FIG. 11 is a schematic block diagram of a session management device according to an embodiment of the present application.
  • the session management device includes an acquisition unit 1101, a transmission unit 1102, and a reception unit 1103.
  • the obtaining unit 1101 may be a processor of the session management device
  • the sending unit 1102 and the receiving unit 1103 may be a communication interface used by the session management device to send and receive information.
  • the sending unit 1102 and the receiving unit 1103 can refer to the communication interface of the session management network element in the communication architecture shown in FIG. 1.
  • the acquiring unit 1101 is configured to acquire a flow identifier of a flow in a PDU session corresponding to the DNN of the terminal, and obtain a bearer identifier of the bearer in the PDN connection corresponding to the APN of the terminal, where the DNN is the first communication in the terminal A DNN in the subscription data in the network, the APN being an APN in the subscription data of the terminal in the second communication network.
  • the sending unit 1102 is configured to send the bearer identifier and the stream identifier to an access and mobility management network element.
  • the receiving unit 1103 is configured to receive a PDU session establishment request message sent by the access and mobility management network element, where the bearer in the PDN connection corresponding to the APN is a default bearer, and the flow in the PDU session corresponding to the DNN As a default stream, the PDU session establishment request message includes the bearer identifier.
  • the subscription data of the terminal in the first communication network further includes a subscription context corresponding to the DNN
  • the subscription data of the terminal in the second communication network further includes a PDN subscription context corresponding to the APN
  • the PDU session establishment request message further includes a subscription context corresponding to the DNN and a PDN subscription context corresponding to the APN.
  • the sending unit 1102 is further configured to send a PDU-CAN session establishment request message to the policy and charging network element, where the PDU-CAN session establishment request message includes a subscription context corresponding to the DNN and the APN corresponding to the APN. a PDN subscription context; the receiving unit is further configured to receive a PDU-CAN session establishment response message sent by the policy and the charging network element, where the PDU-CAN session establishment response message includes the terminal in the first communication The network and the policy and charging control PCC rules of the terminal in the second communication network.
  • the sending unit 1102 is further configured to send a dedicated bearer identity allocation request message to the access and mobility management network, where the receiving unit is configured to receive the exclusive sent by the access and mobility management network element.
  • a bearer identifier allocation response message where the bearer in the PDN connection corresponding to the APN is a private bearer, the flow in the PDU session corresponding to the DNN is a private flow, and the dedicated bearer identity allocation response message includes the The bearer ID of the proprietary bearer.
  • the receiving unit 1103 is further configured to receive a PDU-CAN session modification request message sent by the receiving policy and the charging network element, where the PDU-CAN session modification request message includes the terminal in the first communication network and the The PCC rules of the terminal in the second communication network.
  • the sending unit 1103 is configured to send session management information to the access and mobility management network element, where the session management information includes an authorized QoS rule of the flow and an authorized a QoS rule, wherein the authorized QoS rule of the flow includes the flow identifier, and the authorized QoS rule of the bearer includes the bearer identifier.
  • the acquiring unit 1101 is configured to aggregate, according to the PCC rule of the terminal in the first communication network, the service data flow corresponding to the PCC rule in the first communication network to the established In a flow, the flow identifier of the private flow obtained by the session management network element is a flow identifier of the private flow that the terminal has established.
  • the acquiring unit according to a PCC rule of the terminal in the second communication network, is configured to be in the terminal
  • the service data flow corresponding to the PCC rule in the second communication network is aggregated into the dedicated bearer that has been established by the terminal, and the bearer identifier of the dedicated bearer obtained by the session management network element is a dedicated bearer that has been established by the terminal. Bearer ID.
  • the obtaining unit 1101 in this embodiment is further configured to implement the functions of the session management network element regarding data and signal processing in the embodiments of FIG. 2-9.
  • the sending unit 1102 and the receiving unit 1103 are also used to implement the function of the session management network element for transmitting and receiving information in the embodiment of FIG. 2-9.
  • FIG. 12 is a schematic structural diagram of a policy and charging control device according to an embodiment of the present application.
  • the policy and charging control device includes an obtaining unit 1201, a transmitting unit 1202, and a receiving unit 1203.
  • the obtaining unit 1201 may be a processor of a policy and charging control device
  • the sending unit 1202 and the receiving unit 1203 may be a communication interface used by the policy and charging control device to send and receive information.
  • the sending unit 1202 and the receiving unit 1203 can refer to the communication interface of the policy and charging control network element in the communication architecture shown in FIG. 1.
  • the obtaining unit 1201 is configured to acquire a service requirement of the terminal.
  • the sending unit 1202 is configured to send a PDU-CAN session management message to the session management network element, where the PDU-CAN session management message includes policy and charging control of the terminal in the first communication network and the terminal in the second communication network. PCC rules.
  • the receiving unit 1203 is configured to receive a PDU-CAN session establishment request message sent by the session management network element, where the PDU-CAN session establishment request message includes a subscription context corresponding to the DNN of the terminal in the first communication network, and the terminal is in the The PDN subscription context corresponding to the APN in the second communication network.
  • the PCC rule of the terminal in the first communication network and the terminal in the second communication network includes: the terminal is in the QoS classification identifier of the first communication network, and the PDU session corresponding to the DNN The authorized Session-AMBR of the default stream, the QoS classification identifier of the terminal in the second communication network, and the authorized APN-AMBR of the default bearer in the PDN connection corresponding to the APN.
  • the receiving unit 1203 is configured to receive the service request sent by the terminal or an application function network element, where the service requirement includes an Internet Protocol IP filtering information, a media bandwidth requirement for the QoS control, and an application. At least one of the bandwidth requirements.
  • the PCC rule of the terminal in the first communication network and the terminal in the second communication network includes: a quality of service classification identifier of the terminal in the first communication network, and the terminal is in the second communication network.
  • the service requirement further includes: a service continuity requirement.
  • the obtaining unit 1201 in this embodiment is further configured to implement the functions of the policy and charging control network element regarding data and signal processing in the embodiments of FIG. 2-9.
  • the sending unit 1202 and the receiving unit 1203 are also used to implement the function of transmitting and receiving information about the policy and charging control device network element in the embodiment of FIG. 2-9.
  • FIG. 13 is another schematic structural diagram of an access and mobility management device according to an embodiment of the present application.
  • the access and mobility management device includes a processor 1301, a memory 1302, and a communication interface 1303.
  • the processor 1301, the memory 1302, and the communication interface 1303 may be connected to each other through a bus 1304.
  • the bus 1304 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus or the like.
  • the bus 404 can be divided into an address bus, a data bus, a control bus, and the like.
  • the communication interface 1303 may also be a plurality of communication interfaces.
  • the communication interface may include an N2 interface, an Nx interface, and an N11 interface. Port, N15 interface and N18 interface.
  • the access and mobility management device (for example, AMF) connects to other core network devices through corresponding interfaces, and uses the corresponding interface to send and receive information.
  • the processor 1301 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof.
  • the PLD may be a Complex Programmable Logic Device (CPLD), a Field-Programmable Gate Array (FPGA), a Generic Array Logic (GAL), or any combination thereof.
  • CPLD Complex Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • GAL Generic Array Logic
  • the memory can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • memory 1302 may also be a memory unit within processor 1301.
  • the instructions stored in the memory 1302 may cause the processor 1301 to perform operations of acquiring subscription data of the terminal in the first communication network and subscription data of the terminal in the second communication network through the communication interface 1303, wherein the terminal is
  • the subscription data in the first communication network includes a DNN
  • the subscription data in the second communication network includes an APN corresponding to the DNN
  • a bearer identifier is allocated to the bearer in the PDN connection corresponding to the APN
  • the interface 1303 receives the flow identifier of the flow in the PDU session corresponding to the DNN sent by the session management network element, and sends the bearer identifier and the flow identifier to the terminal through the communication interface 1303.
  • the processor in this embodiment is further configured to implement the functions of the access and mobility management device for data and signal processing in the embodiments of FIGS. 2-9, and perform corresponding data and signal processing steps.
  • the communication interface 1303 is further configured to implement the functions of the access and mobility management network element for transmitting and receiving information in the embodiment of FIG. 2 to FIG. 9 and perform corresponding information transmission and reception.
  • the embodiment of the present application further provides another session management device.
  • the session management device has a similar structure to the access and mobility management in FIG.
  • the communication interface may include an N4 interface, an N7 interface, an N11 interface, and an N10 interface in the communication architecture shown in FIG. 1.
  • the session management device (for example, SMF) connects to other core network devices through corresponding interfaces, and uses the corresponding interface to send and receive information.
  • the instructions stored in the memory of the session management device may cause the processor to: obtain a flow identifier of the flow in the PDU session corresponding to the DNN of the terminal, where the DNN is the terminal in the first communication network
  • the access and mobility management network element sends the bearer identifier and the flow identifier.
  • the processor in this embodiment is further configured to implement the functions of the session management network element regarding data and signal processing in the embodiments of FIG. 2-9, and perform corresponding data and signal processing steps.
  • the communication interface is also used to implement the function of the session management network element for transmitting and receiving information in the embodiment of FIG. 2 to FIG. 9 and to perform corresponding information transmission and reception.
  • the embodiment of the present application further provides another policy and charging control device.
  • the policy and charging control device has a similar structure to the access and mobility management in FIG. But the communication interface may include N7 in the communication architecture shown in FIG. Interface and N15 interface.
  • the policy and charging control device (for example, PCR) is connected to other core network devices through corresponding interfaces, and uses the corresponding interface to send and receive information.
  • the instructions stored in the memory of the policy and charging control device may cause the processor to perform the following operations: acquiring a service requirement of the terminal; and transmitting a PDU-CAN session management message to the session management network element through the communication interface, the PDU-CAN
  • the session management message includes a policy and charging control PCC rule of the terminal in the first communication network and the terminal in the second communication network.
  • the processor in this embodiment is further configured to implement the functions of the policy and charging control device regarding data and signal processing in the embodiments of FIG. 2-9, and perform corresponding data and signal processing steps.
  • the communication interface is also used to implement the function of transmitting and receiving information about the policy and charging control device in the embodiment of FIG. 2 to FIG. 9 and performing corresponding information transmission and reception.
  • Embodiments of the present invention also provide a computer storage medium or computer program product for storing processor-executable instructions stored in the above-described memory.
  • the computer program product can include one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic disk), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种会话管理方法、接入管理功能设备和会话管理设备。该方法包括：接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的APN；所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配承载标识；所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识；所述接入和移动性管理网元向所述终端发送所述承载标识和所述流标识。本申请的实施例中，接入和移动性管理网元为第二通信网络预留会话资源，从而能够简化不同通信网络之间的互操作流程。

Description

会话管理方法、接入管理功能设备和会话管理设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种会话管理方法、接入管理功能设备和会话管理设备。
背景技术
随着物联网、车联网等网络需求的出现，用户对于下一代移动通信网络，即第5代(5th Generation,5G)移动通信网络的诉求越来越多。在5G网络中，为了保障5G网络与4G(4th Generation,4G)网络或其他网络之间(例如：2G或3G网络)的互操作(interworking)，采用类似于4G与3G或4G与2G网络之间的互操作流程，例如：采用移动性管理(Mobility Management,MM)上下文映射或者会话管理(Session Management,SM)上下文映射的方案进行切换。
然而，这种采用上下文映射进行切换的方案流程复杂，不利于保障5G网络的部署进程。
发明内容
本申请实施例提供了一种会话管理方法，能够简化不同通信网络之间的互操作流程。
第一方面，提供了一种会话管理方法，包括：接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的APN；所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配承载标识；所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识；所述接入和移动性管理网元向所述终端发送所述承载标识和所述流标识。
本实施例中，接入和移动性管理网元为第二通信网络预留会话资源，从而能够简化不同通信网络之间的互操作流程。
结合第一方面，在第一方面的第一种可能的实现方式中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配承载标识之前，所述方法还包括：所述接入和移动性管理网元接收所述终端发送的注册请求消息或者PDU会话建立请求消息；所述接入和移动性管理网元接收所述注册请求消息或者所述PDU会话建立请求消息后，所述方法还包括：所述接入和移动性管理网元向所述会话管理网元发送PDU会话建立请求消息，所述PDU会话建立请求消息包括所述默认承载的承载标识。
本实施例实现了在PDU会话中的默认流建立过程中，为该默认流分配对应的默认承载标识，从而实现为第二通信网络预留会话资源，简化不同通信网络之间的互操作流程。
结合第一方面，在第一方面的第二种可能的实现方式中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流；所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识之前，所述方法还包括：所述接入和移动性管理网元接收所述会话管理网元发送的专有承载标 识分配请求消息；所述接入和移动性管理网元向所述会话管理网元发送专有承载标识分配响应消息，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
本实施例实现了在PDU会话中的专有流建立过程中，为该专有流分配对应的专有承载标识，从而实现为第二通信网络预留会话资源，简化不同通信网络之间的互操作流程。
结合第一方面，在第一方面的第三种可能的实现方式中，该方法还包括：所述接入和移动性管理网元接收接入网设备发送的切换请求；所述接入和移动性管理网元向所述会话管理网元发送会话上下文请求消息；所述接入和移动性管理网元接收所述会话管理网元发送的会话上下文响应消息，所述会话上下文响应消息包括：所述PDN连接中默认承载的承载标识和策略与计费控制规则，和/或，所述PDN连接中专有承载的承载标识和策略与计费控制规则；所述接入和移动性管理网元向移动性管理实体发送重定位请求，所述定位请求包括指示信息，所述指示信息用于指示所述移动性管理实体重新选择服务网关。
本实施例中，为了保障终端在不同网络间的切换，在切换之前，第一通信网络为第二通信网络预留会话管理资源，在切换过程中，第一通信网络将这些会话管理资源发送给第二通信网络，第二通信网络根据这些会话管理资源能够迅速搭建业务，保证业务连续，并且简化了切换流程。
第二方面，提供了一种会话管理方法，包括：会话管理网元获取终端的DNN对应的PDU会话中的流的流标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN；所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，其中，所述APN为所述终端在第二通信网络中的签约数据中的APN；所述会话管理网元向接入和移动性管理网元发送所述承载标识和所述流标识。
结合第二方面，在第二方面的第一种可能的实现方式中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：所述会话管理网元接收所述接入和移动性管理网元发送的PDU会话建立请求消息，所述PDU会话建立请求消息包括所述承载标识。
结合第二方面，在第二方面的第二种可能的实现方式中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流；所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：所述会话管理网元向所述接入和移动性管理网发送专有承载标识分配请求消息；所述会话管理网元接收所述接入和移动性管理网元发送的专有承载标识分配响应消息，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
结合第二方面，在第二方面的第三种可能的实现方式中，所述会话管理网元向所述接入和移动性管理网元发送所述承载标识和所述流标识，包括：所述会话管理网元向所述接入和移动性管理网元发送会话管理信息，所述会话管理信息包括所述流的授权后的QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
结合第二方面，在第二方面的第四种可能的实现方式中，所述会话管理网元获取终端的DNN对应的PDU会话中的流的流标识，包括：所述会话管理网元根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数 据流聚合到所述终端已经建立的专有流中，所述会话管理网元获取的专有流的流标识为所述终端已经建立的专有流的流标识。
本实例中，会话管理网元根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有流中，从而能够是实现在一个PDU会话中的专有流的数量多于一个PDN连接中专有承载的数量的情况，专有流和专有承载之间建立对应关系。
结合第二方面，在第二方面的第五种可能的实现方式中，所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：所述会话管理网元根据所述终端在第二通信网络中的PCC规则，将所述终端在第二通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有承载中，所述会话管理网元获取的专有承载的承载标识为所述终端已经建立的专有承载的承载标识。
第三方面，提供了一种策略与计费控制方法，包括：策略与计费网元获取终端的业务要求；所述策略与计费网元向会话管理网元发送分组数据单元连接访问网络PDU-CAN会话管理消息，所述PDU-CAN会话管理消息包括所述终端在第一通信网络和所述终端在第二通信网络的策略与计费控制PCC规则。
结合第三方面，在第三方面的第一种可能的实现方式中，所述策略与计费网元接收会话管理网元发送的PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述终端在第一通信网络中的DNN对应的签约上下文和所述终端在第二通信网络中的APN对应的PDN签约上下文。
结合第三方面，在第三方面的第二种可能的实现方式中，所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的服务质量分类识别码、所述DNN对应的PDU会话中的默认流的授权后的聚合最大比特速率Session-AMBR、所述终端在第二通信网络的服务质量分类识别码、以及所述APN对应的PDN连接中的默认承载的授权后的APN-AMBR。
结合第三方面，在第三方面的第三种可能的实现方式中，所述策略与计费网元获取终端的业务要求，包括：所述策略与计费网元接收所述终端或者应用功能网元发送的所述业务要求，所述业务要求包括互联网协议IP过滤信息、用于服务质量QoS控制的媒体带宽要求和应用带宽要求中的至少一个。
结合第三方面，在第三方面的第四种可能的实现方式中，所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的服务质量分类识别码、所述终端在第二通信网络的服务质量分类识别码以及如下中的至少一个：上行和下行包过滤器、保证比特速率GBR、最大比特率MBR和预留和分配优先级ARP。
结合第三方面，在第三方面的第五种可能的实现方式中，所述业务要求还包括：业务连续性要求。
第四方面，提供了一种接入和移动性管理设备，包括：获取单元，用于获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的APN；分配单元，用于为所述APN对应的PDN连接中的承载分配承载标识；接收单元，用于接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识；发送单元，用于向所述终端发送所述承载标识和所述流标识。
第五方面，提供了一种接入和移动性管理设备，包括：获取单元，用于获取终端的DNN对应的PDU会话中的流的流标识，获取所述终端的APN对应的PDN连接中的承载的承载标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN，所述APN为所述终端在第二通信网络中的签约数据中的APN；发送单元，用于向接入和移动性管理网元发送所述承载标识和所述流标识。
第六方面，提供了一种策略与计费控制设备，包括：获取单元用于获取终端的业务要求；发送单元用于向会话管理网元发送PDU-CAN会话管理消息，所述PDU-CAN会话管理消息包括所述终端在第一通信网络和所述终端在第二通信网络的策略与计费控制PCC规则。
第七方面，提供了一种计算机程序产品，包括计算机程序指令，当所述计算机程序指令在计算机上运行时，使得所述计算机执行如第一方面到第三方面中任意一项所述的方法。
附图说明
图1是本申请实施例的技术方案应用的一种架构的示意图。
图2是本申请实施例的会话管理方法的一示意性流程图。
图3是本申请实施例的会话管理方法的另一示意性流程图。
图4是根据本申请实施例的策略与计费控制方法的一示意性流程图。
图5是根据本申请实施例的会话管理方法的再一示意性流程图。
图6是根据本申请实施例的会话管理方法的再一示意性流程图。
图7是根据本申请实施例的会话管理方法的再一示意性流程图。
图8是根据本申请实施例的会话管理方法的再一示意性流程图。
图9是根据本申请实施例的UE跨通信网络切换方法的一示意性流程图。
图10是根据本申请实施例的接入和移动性管理设备的示意性框图。
图11是根据本申请实施例的会话管理设备的示意性框图。
图12是根据本申请实施例的策略与计费控制设备的示意性结构图。
图13是根据本申请实施例的接入和移动性管理设备的另一示意性结构图。
具体实施方式
本申请实施例所涉及到的终端可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile Station，MS)，终端设备(terminal device)等等。为方便描述，本申请仅以终端为UE进行举例说明。下面将结合附图，对本申请实施例中的技术方案进行描述。
图1是本申请实施例的技术方案应用的一种通信架构的示意图。在该通信架构中，UE通过演进型通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network,EUTRAN)接入核心网网络，UE也可以通过下一代无线接入网(Next Generation Radio Access Network,NG RAN)设备接入核心网网络。核心网网络中的设备包括移动性管理实体(Mobility Management Entity,MME)、服务网关(Serving Gateway,SGW)、签约服务器、策略和计费网元、会话管理网元、用户面功能网元以及接入和移动性管理网元。可选的， 接入和移动性管理网元可以为接入和移动性管理功能(Access and Mobility Management Function,AMF)。可选的，在本申请中，各网元之间可以通过附图所示的接口连接。例如：MME和AMF之间通过Nx接口连接，SGW和用户面功能网元之间通过S5-U接口连接。
在本实施例中，签约服务器用于存储UE的签约数据。可选的，签约服务器可以包括归属签约服务器(Home Subscriber Server,HSS)和统一数据管理(Unified Data Management,UDM)。HSS和UDM合一部署，可以在HSS中增加UDM功能，或者在UDM中增加HSS功能，或者在另一设备同时实现HSS和UDM的功能。图1中，签约服务器用HSS+UDM表示。
策略和计费网元包括策略和计费规则功能(Policy and charging rules function,PCRF)和策略控制功能(policy control function,PCF)。PCRF和PCF合一部署，可以在PCRF中增加PCF功能，或者在PCF中增加PCRF功能，或者在另一设备同时实现PCRF和PCF的功能。图1，策略和计费网元用PCRF+PCF表示。
会话管理网元包括会话管理功能(Session Management Function,SMF)和分组数据网络网关控制面(Packet Data Network Gateway-Control plane,PGW-C)。SMF和PGW-C合一部署，可以在SMF中增加PGW-C功能，或者在PGW-C中增加SMF功能，或者在另一设备同时实现SMF和PGW-C的功能。图1中，会话管理网元用SMF+PGW-C表示。
用户面功能网元包括用户面功能(User Plane Function,UPF)和分组数据网络网关用户面(Packet Data Network Gateway-User plane,PGW-U)。UPF和PGW-U合一部署，可以在UPF中增加PGW-U功能，或者在PGW-U中增加UPF功能，或者在另一设备同时实现UPF和PGW-U的功能。图1中，会话管理网元用UPF+PGW-U表示。
图1所示的通信架构包括第一通信网络和第二通信网络。其中，第一通信网络包括AMF、UDM、PCF、SMF和UPF。可选的，第一通信网络可以是5G通信网络。第二通信网络包括EUTRAN、MME、SGW、HSS、PCRF、PGW-C以及PGW-U。可选的，第二通信网络可以是4.5G或者4G通信网络。在图1所示的通信架构中，UE可以接入第一通信网络也可以接入第二通信网络，并可以实现UE在第一通信网络和第二通信网络之间的互操作。
图2是本申请实施例的会话管理方法的一示意性流程图。在本实施例中，该会话管理方法包括：
201 接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。其中，所述终端在第一通信网络中的签约数据包括数据网络名称(Data Network Name,DNN)，所述终端在第二通信网络中的签约数据包括与所述DNN对应的接入点名称(Access Point Name,APN)。可选的，该接入和移动性管理网元为AMF。
可选的，第一通信网络是5G通信网络。第二通信网络可以是4G通信网络。
可选的，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文(subscription context)，所述终端在第二通信网络中的签约数据还包括所述APN对应的分组数据网(Packet Data Network,PDN)签约上下文。
可选的，所述DNN包括默认DNN，所述APN包括默认APN，所述默认DNN和所述默认APN对应。可选的，所述DNN包括非默认DNN，所述APN包括非默认APN。所述非默认DNN和所述非默认APN对应。
可选的，所述接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，包括：所述接入和移动性管理网元向签约服务器发送位置更新请求消息；所述接入和移动性管理网元接收所述签约服务器发送的位置更新响应消息，所述位置更新响应消息包括所述终端在所述第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。可选的，签约服务器为UDM。
可选的，所述接入和移动性管理网元向签约服务器发送位置更新请求，包括：所述接入和移动性管理网元向所述UDM发送第一位置更新请求，所述接入和移动性管理网元向所述UDM发送第二位置更新请求；所述接入和移动性管理网元接收所述签约服务器发送的位置更新响应，所述位置更新响应包括所述终端在所述第一通信网络中的签约数据和所述第二通信网络中的签约数据，包括：所述接入和移动性管理网元接收所述UDM发送的第一位置更新响应，所述第一位置更新响应包括所述终端在所述第一通信网络中的签约数据，所述接入和移动性管理网元接收所述UDM发送的第二位置更新响应，所述第二位置更新响应包括所述第二通信网络中的签约数据。
202 所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配(Default bearer)承载标识。
可选的，默认承载的承载标识对应默认流的流标识。例如：默认承载的承载标识一一对应默认流的流标识。
可选的，专有承载的承载标识对应专有流的流标识。例如：专有承载的承载标识一一对应专有流的流标识，或者专有承载的承载标识与多个专有流聚合后的流的流标识对应，或者多个专有承载聚合后的承载的承载标识与一个专有流的流标识对应。
可选的，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流(flow)为默认流。所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配承载标识之前，所述方法还包括：所述接入和移动性管理网元接收所述终端发送的注册请求消息或者PDU会话建立请求消息。所述接入和移动性管理网元接收所述注册请求消息或者所述PDU会话建立请求消息后，所述方法还包括：所述接入和移动性管理网元向会话管理网元发送PDU会话建立请求消息，所述PDU会话建立请求消息包括所述默认承载的承载标识。可选的，会话管理网元为SMF。
可选的，所述注册请求消息或者PDU会话建立请求消息还包括指示信息。该指示信息用于指示所述接入和移动性管理网元所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力，和/或，用于指示所述接入和移动性管理网元所述终端具有单注册(single-rigistration)或者双注册的能力(dual-registration)。
可选的，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流。所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识之前，所述方法还包括：所述接入和移动性管理网元接收所述会话管理网元发送的专有承载标识分配请求消息，所述接入和移动性管理网元向所述会话管理网元发送专有承载标识分配响应消息，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
可选的，所述接入和移动性管理网元向所述会话管理网元发送的PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。可选的所述PDU会话建立请求消息还包括指示信息，该指示信息用于指示所述会话管理网元所 述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力，和/或，用于指示所述会话管理网元所述终端具有单注册能力。
203 所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识(flow ID)。
可选的，所述接入和移动性管理网元接收会话管理网元发送的会话管理消息之前，所述接入和移动性管理网元确定所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力以及与移动性管理实体之间存在接口，和/或，所述终端具有单注册能力。
可选的，所述接入和移动性管理网元接收会话管理网元发送的会话管理消息之前，所述接入和移动性管理网元根据所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力以及与移动性管理实体之间存在接口，和/或，所述终端具有单注册能力，选择所述会话管理网元。
可选的，所述接入和移动性管理网元接收会话管理网元发送的会话管理信息，所述会话管理信息包括所述流的授权后的服务质量(Quality of Service,QoS)规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
可选的，所述会话管理信息包括默认流的流标识、所述默认流的授权后的会话的聚合最大比特速率(Session-Aggregate Maximum Bit Rate,Session-AMBR)、默认承载的承载标识和所述默认承载的授权后的APN-AMBR。
可选的，所述会话管理信息包括保证比特速率(Guaranteed Bit Rate,GBR)流的流标识、所述GBR流的上行包过滤器(UL Packet filter)、GBR专有承载的承载标识和所述GBR专有承载的业务模板流(Traffic Flow Template，TFT)。可选的，这里的上行包过滤器和上行业务模板流所包含的内容一致。
204 所述接入和移动性管理网元向所述终端发送所述承载标识和所述流标识。
可选的，所述接入和移动性管理网元向所述终端发送所述会话管理信息，该会话管理信息包括所述承载标识和所述流标识。
可选的，本实施例的方法还包括：述接入和移动性管理网元接收接入网设备发送的切换请求；所述接入和移动性管理网元向所述会话管理网元发送会话上下文请求消息；所述接入和移动性管理网元接收所述会话管理网元发送的会话上下文响应消息，所述会话上下文响应消息包括：所述PDN连接中默认承载的承载标识和策略与计费控制(Policy and Charging Control,PCC)规则(rule)，和/或，所述PDN连接中专有承载的承载标识和PCC规则；所述接入和移动性管理网元向移动性管理实体发送重定位请求，所述重定位请求包括指示信息，所述指示信息用于指示所述移动性管理实体重新选择服务网关。可选的，也可以将服务网关的地址信息设置为0.0.0.0，从而指示移动性管理网元重新选择服务网关。
图3是本申请实施例的会话管理方法的另一示意性流程图。在本实施例中，与图2实施例相似的内容参见图2实施例对应的文字描述，在此不再赘述。该会话管理方法包括：
301 会话管理网元获取终端的DNN对应的PDU会话中的流的流标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN。
可选的，所述会话管理网元为终端的DNN对应的PDU会话中的流分配流标识。
可选的，所述会话管理网元根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有流中，所述会话管理网元获取的专有流的流标识为所述终端已经建立的专有流的流标识。
302 所述会话管理网元获取所述终端的接入点名称APN对应的分组数据网PDN连接中的承载的承载标识，其中，所述APN为所述终端在第二通信网络中的签约数据中的APN。
所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文。可选的，所述会话管理网元接收的所述PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。可选的，所述PDU会话建立请求消息还包括指示信息，该指示信息用于指示所述会话管理网元所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力，和/或，用于指示所述会话管理网元所述终端具有单注册能力。
可选的，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流。所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：所述会话管理网元接收所述接入和移动性管理网元发送的PDU会话建立请求消息，所述PDU会话建立请求消息包括所述承载标识。
可选的，所述会话管理网元根据所述终端在第二通信网络中的PCC规则，将所述终端在第二通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有承载中，所述会话管理网元获取的专有承载的承载标识为所述终端已经建立的专有承载的承载标识。
可选的，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流；所述会话管理网元获取所述终端的APN对应的分组数据网PDN连接中的承载的承载标识，包括：所述会话管理网元向所述接入和移动性管理网发送专有承载标识分配请求消息；所述会话管理网元接收所述接入和移动性管理网元发送的专有承载标识分配响应消息，所述专有承载标识分配响应消息携带所述专有承载的承载标识。
303 所述会话管理网元向所述接入和移动性管理网元发送所述承载标识和所述流标识。
可选的，所述会话管理网元向所述接入和移动性管理网元发送所述承载标识和所述流标识，包括：所述会话管理网元向所述接入和移动性管理网元发送会话管理信息，所述会话管理信息包括所述流的授权后的服务质量QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
可选的，所述会话管理信息包括默认流的流标识、所述默认流的授权后的Session-AMBR、默认承载的承载标识和所述默认承载的授权后的APN-AMBR。
可选的，所述会话管理信息包括GBR流的流标识、所述GBR流的上行包过滤器(UL Packet filter)、GBR专有承载的承载标识和所述GBR专有承载的上行业务模板流(Traffic Flow Template，TFT)，可选的，这里的上行包过滤器和上行业务模板流所包含的内容一致。
可选的，本实施例的方法还可以包括：所述会话管理网元向策略与计费网元发送PDU连接访问网络(PDU Connectivity Access Network,PDU-CAN)会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文；所述会话管理网元接收所述策略与计费网元发送的PDU-CAN会话建立响应消息，所述PDU-CAN会话建立响应消息包括所述终端在所述第一通信网络和所述第二通信网络中的策略与计费控制PCC规则。可选的，所述PDU-CAN会话建立请求消息还包括指示信息，该指示信息用于指示所述策略与计费网元所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力，和/或，用于指示所述策略与计费网元所述终端具有单注册能力。
可选的，PCC规则包括终端在第一通信网络网络中的服务质量分类识别码(QoS Class Identifier QCI)、终端在第二通信网络中的QCI以及如下中的至少一个：上行和下行包过滤器(UL+DL Packet filters)、保证比特速率(Guaranteed Bit Rate,GBR)、最大比特率(Maximum Bit Rate,MBR)和预留和分配优先级(Allocation and Retention Priority,ARP)。
可选的，本实施例的方法还可以包括：所述会话管理网元接收策略与计费网元发送的PDU-CAN会话修改请求消息，所述PDU-CAN会话建立响应消息包括所述终端在所述第一通信网络和所述第二通信网络中的策略与计费控制PCC规则。可选的，策略与计费网元为PCF。
图4是根据本申请实施例的策略与计费控制方法的一示意性流程图。在本实施例中，与图2和图3实施例相似的内容参见图2和图3实施例对应的文字描述，在此不再赘述。该策略与计费控制方法包括：
401 策略与计费网元获取终端的业务要求。
可选的，所述策略与计费网元获取终端的业务要求，包括：所述策略与计费网元接收会话管理网元发送的PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述终端在第一通信网络中的数据网络名称DNN对应的签约上下文和所述终端在第二通信网络中的接入点名称APN对应的分组数据网PDN签约上下文。可选的，所述PDU-CAN会话建立请求消息还包括指示信息，该指示信息用于指示所述策略与计费网元所述终端具有在所述第一通信网络和所述第二通信网络进行通信的能力，和/或，用于指示所述策略与计费网元所述终端具有单注册能力。
可选的，所述策略与计费网元获取终端的业务要求，包括：所述策略与计费网元接收所述终端或者应用功能网元发送的所述业务要求，所述业务要求包括互联网协议IP过滤信息、用于QoS控制的媒体带宽要求和应用带宽要求中的至少一个。可选的，应用功能网元为应用功能(Application Function,AF)。可选的，策略与计费网元从会话管理网元接收PDU-CAN会话修改请求或者从应用功能接收业务通知消息。策略与计费网元从会话管理网元接收PDU-CAN会话修改请求发生在UE发起的专有流建立过程，策略与计费网元从应用功能接收业务通知消息发生在AF发起的专有流建立过程。该PDU-CAN会话修改请求或者业务通知消息包括所述终端的业务要求。可选的，所述业务要求还包括：业务连续性要求。
402 所述策略与计费网元向会话管理网元发送PDU-CAN会话管理消息，所述PDU-CAN会话管理消息包括所述终端在第一通信网络和所述终端在第二通信网络的策略与计费控制PCC规则。
可选的，该PDU-CAN会话管理消息为PDU-CAN会话建立响应消息。所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的QCI、所述DNN对应的PDU会话中的默认流的授权后的Session-AMBR、所述终端在第二通信网络的QCI、以及所述APN对应的PDN连接中的默认承载的授权后的APN-AMBR。
可选的，该PDU-CAN会话管理消息为PDU-CAN会话修改响应消息或者PDU-CAN会话修改请求消息。PDU-CAN会话管理消息为PDU-CAN会话修改响应消息发生在UE发起的专有流建立过程，PDU-CAN会话管理消息为PDU-CAN会话修改请求消息发生在AF发起的专有流建立过程。所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的QCI、所述终端在第二通信网络的QCI以及如下中的至少一个：上行和下行包过滤器(UL+DL Packet filters)、GBR、MBR和ARP。
下面以第一通信网络为5G通信网络，第二通信网络为4G网络，对本申请的各实施例进行举例说明。为了清楚、简洁的描述本申请的实施例，本申请实施例中仅仅示出了与本申请相关的步骤流程和网元，其他为本领域技术人员熟知的技术内容，附图并未示出。例如：附图并未示出用于与UE通过空口进行信息收发的接入网设备。
在图5-图9的附图中，为了清楚简洁的描述，分别用SMF,PCF,UPF,UDM代表5G网络和4G络中对应的核心网设备合一部署的情况。
图5是根据本申请实施例的会话管理方法的再一示意性流程图。在本实施例中，与图2～图4实施例相似的内容参见图2～图4实施例对应的文字描述，在此不再赘述。具体的，图5示出了UE在注册过程中的会话管理方法。本实施例的会话管理方法包括：
501 UE向AMF发送注册请求(Registration Request)。
可选的，注册请求可以包括指示信息，该指示信息用于指示UE具有在5G和4G网络进行通信的能力，和/或，用于指示AMF UE具有单注册或者双注册的能力。
502 UE与网络侧设备完成鉴权(authentication)和安全(security)流程。
503 AMF向UDM发送位置更新请求(update location request)消息。
可选的，当HSS和UDM合一部署时，AMF向UDM发送位置更新请求消息。位置更新请求消息包括指示信息，该指示信息用于指示UE具有在5G和4G网络进行通信的能力。可选的，指示信息可以是互操作指示信息。
可选的，当HSS和UDM合一部署时，AMF分别向UDM发送第一位置更新请求和第二位置更新请求消息。可选的，如果AMF相对于上一次注册发生改变，或者AMF中针对当前UE没有合法的签约上下文，或者UE提供的SUPI在AMF中没有合法上下文与之对应，AMF可以发起位置更新流程。
504 AMF接收UDM发送的位置更新响应(update location response)消息。
位置更新响应消息包括UE在5G网络中的签约数据和在4G网络中的签约数据。其中，5G网络中的签约数据包括DNN，4G网络中的签约数据包括APN。
可选的，DNN包括默认DNN，APN包括默认APN。可选的，DNN包括非默认DNN，APN包括非默认APN。可选的，5G网络中的签约数据可以仅包括一个默认DNN。5G网络中的签约数据还可以包括一个或者多个非默认DNN。4G网络中的签约数据可以仅包括一个默认APN。4G网络中的签约数据还可以包括一个或者多个非默认APN,例如：IP多媒体子系统(IP Multimedia Subsystem,IMS)APN或者非第三代合作伙伴计划(3rd  Generation Partnership Project,3GPP)APN。
可选的，默认DNN和默认APN一一对应，非默认DNN和非默认APN一一对应。非默认DNN和非默认APN也可以不一一对应。例如：非默认DNN的数量多于非默认APN的数量。
可选的，DNN对应的一个会话中可以仅包括一个默认流。DNN对应的一个PDU会话中还可以包括一个或者多个专有流。APN对应的一个PDN连接中可以仅包括一个默认承载。DNN对应的一个PDN连接中还可以包括一个或者多个专有承载。
可选的，UE在5G网络中的签约数据还包括DNN对应的签约上下文。UE在4G网络中的签约数据还包括APN对应的PDN签约上下文。可选的，PDN签约上下文中包括QoS参数，例如：签约APN-AMBR和/或签约QoS模板(profile)。
可选的，AMF接收到的位置更新响应中包括DNN和APN之间的对应关系。例如：可以通过列表的方式体现DNN和APN之间的对应关系，也可以通过DNN和APN在消息中的位置关系体现对应关系，在此不再赘述。
可选的，AMF接收到位置更新响应后，可以根据UE在5G和4G网络中的签约数据中的域名获取DNN和APN之间的对应关系。例如：PDN签约上下文中包括4g.ims.org，DNN对应的签约上下文中包括5g.ims.org，AMF根据域名中都包括ims.org将DNN和APN对应。
可选的，当HSS和UDM合一部署时，AMF接收UDM发送的位置更新响应。位置更新响应包括UE在5G网络中的签约数据和在4G网络中的签约数据。
可选的，当HSS和UDM合一部署时，AMF分别接收UDM发送的第一位置更新响应和第二位置更新响应。第一位置更新响应包括UE在5G网络中的签约数据，第二位置更新响应包括UE在4G网络中的签约数据。
505 AMF为APN对应的PDN连接中的默认承载分配承载标识(bearer ID)。
506 AMF向SMF发送PDU会话建立请求消息。其中，PDU会话建立请求消息包括AMF分配的默认承载的承载标识。
可选的，PDU会话建立请求消息还可以包括指示信息。该指示信息用于指示UE具有在5G和4G网络进行通信的能力，和/或，用于指示SMF UE具有单注册能力。
可选的，PDU会话建立请求消息还可以包括APN对应的PDN签约上下文和DNN对应的签约上下文。
可选的，AMF在向SMF发送PDU会话建立请求消息前，可以根据示UE具有在5G和4G网络进行通信的能力以及AMF和MME间存在通信接口，和/或，UE具有单注册能力，选择SMF。
507 SMF为DNN对应的PDU会话中的默认流分配流标识。
可选的，SMF分配的默认流的流标识与AMF分配的默认承载的承载标识一一对应。
508 SMF通过PDU-CAN会话建立流程获取UE在5G和4G网络中的PCC规则。
可选的，PCC规则包括UE在5G网络中的QCI、DNN对应的PDU会话授权后的AMBR、UE在4G网络中的QCI、APN对应的PDN连接授权后的AMBR、以及ARP。
可选的，SMF向PCF发送PDU-CAN会话建立请求消息。其中，PDU-CAN会话建立请求消息包括DNN对应的签约上下文和APN对应的PDN签约上下文，还可以包括指示信息，该指示信息用于指示UE具有在5G和4G网络进行通信的能力，和/或，用于 指示PCF UE具有单注册能力。SMF接收PCF发送的PDU-CAN会话建立响应消息，其中，PDU-CAN会话建立响应消息包括UE在5G和4G网络中的PCC规则。
在本实施例中，可以先执行步骤507再执行步骤508，也可以先执行步骤508再执行步骤507，在此不再限定。
509 SMF向AMF发送PDU会话建立响应消息。其中，PDU会话建立响应消息包括SMF分配的DNN对应的PDU会话中的默认流的流标识。
可选的，PDU会话建立响应消息还可以包括AMF为APN对应的PDN连接中的默认承载分配承载标识。
可选的，PDU会话建立响应消息还可以包括会话管理信息。其中，会话管理信息包括PDU会话中默认流授权后的QoS规则和PDN连接中默认承载授权后的QoS规则。可选的，PDU会话中默认流授权后的QoS规则包括默认流的流标识，PDN连接中默认承载授权后的QoS规则包括默认承载的承载标识。
可选的，PDU会话中默认流授权后的QoS规则还可以包括PDU会话授权后的AMBR。PDN连接中默认承载授权后的QoS规则包括PDN连接授权后的AMBR。
510 AMF向UE发送注册接受消息。其中，注册接受消息包括SMF分配的默认流的流标识与AMF分配的默认承载的承载标识。
可选的，注册接受消息还可以包括PDU会话中默认流授权后的QoS规则和PDN连接中默认承载授权后的QoS规则。
可选的，注册接受包括PDU会话建立响应消息中包括的会话管理信息。
本实施例中，在UE注册过程中，AMF预先获取UE在5G和4G网络中的签约数据,并在5G网络的PDU会话建立过程中，AMF为该会话中的默认流在4G网络中分配对应的默认承载，避免了采用映射的方法建立5G网络中PDU会话中的默认流和4G网路中的PDN连接中默认承载的对应关系。采用本实施的方法，UE在不同网络间的互操作更加简单。例如：UE从5G网络切换到4G网络时，流程更加简单。
图6是根据本申请实施例的会话管理方法的再一示意性流程图。在本实施例中，与图2～图5实施例相似的内容参见图2～图5实施例对应的文字描述，在此不再赘述。具体的，图6示出了UE主动发起PDU会话流程中的会话管理方法。本实施例的会话管理方法包括：
601 UE向AMF发送PDU会话建立请求消息。
可选的，PDU会话建立请求消息可以包括指示信息。该指示信息用于指示UE具有在5G和4G网络进行通信的能力和/或，用于指示SMF UE具有单注册或者双注册的能力。
602 AMF为APN对应的PDN连接中的默认承载分配承载标识。
603 AMF向SMF发送PDU会话建立请求消息。
该步骤与步骤506的内容相似，在此不再赘述。
604 SMF为DNN对应的PDU会话中的默认流分配流标识。
该步骤与步骤507的内容相似，在此不再赘述。
605 SMF通过PDU-CAN会话建立流程获取UE在5G和4G网络中的PCC规则。
该步骤与步骤508的内容相似，在此不再赘述。
606 SMF向UPF发送会话建立请求消息。
可选的，该会话建立请求消息包括指示信息，该指示信息用于指示UE具有在5G和4G网络进行通信的能力。
可选的，当UPF和PGW-U合一部署时，该会话建立请求消息可以为N4会话建立请求消息。当UPF和PGW-U分开部署时，SMF向UPF发送N4会话建立请求消息，SMF向PGW-U发送Sxb会话建立请求消息。
607 SMF接收UPF发送的会话建立响应消息。其中，该话建立响应消息包括UPF的隧道ID以及PGW-U的隧道ID。
可选的，当UPF和PGW-U分开部署时，SMF通过N4接口接收UPF发送的会话建立响应消息，该会话建立响应消息包括UPF的隧道ID。SMF通过Sxb接口接收PGW-U发送的会话建立响应消息，该会话建立响应消息包括PGW-U的隧道ID。
通过步骤606和607，SMF与UPF建立数据传输的通道。
608 SMF向AMF发送PDU会话建立响应消息。
该步骤与步骤509的内容相似，在此不再赘述。
609 AMF向UE发送PDU会话建立接受消息。其中，PDU会话建立接受消息包括SMF分配的默认流的流标识与AMF分配的默认承载的承载标识。
可选的，PDU会话建立接受消息还可以包括PDU会话中默认流授权后的QoS规则和PDN连接中默认承载授权后的QoS规则。
可选的，PDU会话建立接受消息包括步骤608中PDU会话建立响应消息中包括的会话管理信息。
610 AMF接收UE发送的PDU会话建立确认(ACK)消息。
本实施例中，在UE发起的PDU会话建立过程中，AMF为该会话中的默认流在4G网络中分配对应的默认承载，避免了采用映射的方法建立5G网络中PDU会话中的默认流和4G网路中的PDN连接中默认承载的对应关系。采用本实施的方法，UE在不同网络间的互操作更加简单。例如：UE从5G网络切换到4G网络时，流程更加简单。
图7是根据本申请实施例的会话管理方法的再一示意性流程图。在本实施例中，与图2～图6实施例相似的内容参见图2～图6实施例对应的文字描述，在此不再赘述。具体的，图7示出了UE发起PDU会话中专有(Dedicate)流建立的一种流程。本实施例的会话管理方法包括：
701 UE向AMF发送PDU会话修改请求消息。
可选的，PDU会话修改请求消息包括UE的业务要求。其中，业务要求包括互联网协议(IP)过滤信息、用于QoS控制的媒体带宽要求和应用带宽要求中的至少一个。
可选的，业务要求还可以包括业务连续性要求。
702 AMF向SMF发送PDU会话修改请求消息。
703 SMF通过PDU-CAN会话修改流程获取UE在5G和4G网络中的PCC规则。
可选的，PCC规则包括UE在5G网络中的QCI、UE在4G网络中的QCI以及如下中的至少一个：上行和下行包过滤器(UL+DL Packet filters)、GBR、MBR和ARP。可选的，UE在5G和4G网络中可以采用相同的上行和下行包过滤器(UL+DL Packet filters)、GBR、MBR和ARP参数。
可选的，SMF向PCF发送PDU-CAN会话修改请求消息，其中，PDU-CAN会话建立请求消息包括UE的业务要求。PCF根据UE的业务要求为UE生成在5G和4G网络 中的PCC规则。SMF接收PCF发送的PDU-CAN会话建立响应消息，其中，PDU-CAN会话建立响应消息包括UE在5G和4G网络中的PCC规则。
可选的，PCF还可以接收来自应用功能设备(Application Function,AF)发送的业务通知消息，业务通知消息中包括UE的业务要求。此时，PCF向SMF发送PDU-CAN会话修改请求消息，其中，PDU-CAN会话修改请求消息包括UE在5G和4G网络中的PCC规则。
704 SMF向AMF发送专有承载标识分配请求消息。
705 AMF为APN对应的PDN连接中的专有承载分配承载标识。
706 AMF向SMF发送专有承载标识分配响应消息。其中，专有承载标识分配响应消息包括AMF分配的专有承载的承载标识。
707 SMF为DNN对应的PDU会话中的专有流分配流标识。
在本实施例中，步骤703，步骤704-706，步骤707间的顺序可以互换，在此不做限定。
708 SMF向AMF发送PDU会话修改接受消息。其中，PDU会话修改接受消息包括SMF分配的DNN对应的PDU会话中的专有流的流标识。
可选的，SMF根据UE在5G和4G网络中的PCC规则生成UE在5G和4G网络中的QoS规则。
可选的，PDU会话修改接受消息还可以包括会话管理信息。其中，会话管理信息包括PDU会话中专有流授权后的QoS规则和PDN连接中专有承载授权后的QoS规则。可选的，PDU会话中专有流授权后的QoS规则包括专有流的流标识，PDN连接中专有承载授权后的QoS规则包括专有承载的承载标识。
可选的，专有流为GBR流，专有承载为GBR承载。专有流授权后的QoS规则包括GBR流的上行包过滤器(UL Packet filter)，专有承载授权后的QoS规则包括GBR承载的业务模板流(Traffic Flow Template，TFT)。可选的，这里的上行包过滤器和上行业务模板流所包含的内容一致。
709 AMF向UE发送PDU会话修改接受消息。会话修改接受消息包括SMF分配的专有流的流标识与AMF分配的专有承载的承载标识。
可选的，会话修改接受消息还可以包括PDU会话中专有流授权后的QoS规则和PDN连接中专有承载授权后的QoS规则。
可选的，会话建立接受消息包括步骤708中的PDU会话修改接受消息中包括的会话管理信息。
710 AMF接收UE发送的会话修改确认(ACK)消息。
711 AMF向SMF发送会话修改确认消息。
712 SMF向UPF发送会话建立请求消息。
该步骤与步骤606相似，在此不再赘述。
713 SMF接收UPF发送的会话建立响应消息。其中，所述响应消息包括UPF的隧道ID以及PGW-U的隧道ID。
该步骤与步骤607相似，在此不再赘述。
本实施例中，在UE发起的PDU会话中专有流的建立过程中，AMF为该会话中的专有流在4G网络中分配对应的专有承载，避免了采用映射的方法建立5G网络中PDU会 话中的专有流和4G网路中的PDN连接中专有承载的对应关系。采用本实施的方法，UE在不同网络间的互操作更加简单。例如：UE从5G网络切换到4G网络时，流程更加简单。
图8是根据本申请实施例的会话管理方法的再一示意性流程图。在本实施例中，与图2～图7实施例相似的内容参见图2～图7实施例对应的文字描述，在此不再赘述。具体的，图8示出了UE发起PDU会话中专有流建立的另一种流程。本实施例的会话管理方法包括：
本实施例的步骤801-803与步骤701-703相似，在此不再赘述。
804 SMF为DNN对应的PDU会话中的专有流分配流标识。
805 SMF向AMF发送PDU会话修改接受消息。其中，PDU会话修改接受消息包括SMF分配的DNN对应的PDU会话中的专有流的流标识。
可选的，SMF根据UE在5G和4G网络中的PCC规则生成UE在5G和4G网络中的QoS规则。
可选的，PDU会话修改接受消息还可以包括会话管理信息。其中，会话管理信息包括PDU会话中专有流授权后的QoS规则和PDN连接中专有承载授权后的QoS规则。可选的，PDU会话中专有流授权后的QoS规则包括专有流的流标识。
可选的，专有流为GBR流，专有承载为GBR承载。专有流授权后的QoS规则包括GBR流的上行包过滤器(UL Packet filter)，专有承载授权后的QoS规则包括GBR承载的业务模板流(Traffic Flow Template，TFT)。可选的，这里的上行包过滤器和上行业务模板流所包含的内容一致。
806 AMF为APN对应的PDN连接中的专有承载分配承载标识。
807 AMF向UE发送PDU会话修改接受消息。PDU会话修改接受消息包括SMF分配的专有流的流标识与AMF分配的专有承载的承载标识。
可选的，会话修改接受消息还可以包括PDU会话中专有流授权后的QoS规则和PDN连接中专有承载授权后的QoS规则。
可选的，会话建立接受消息包括AMF分配的专有承载的承载标识和步骤805中PDU会话修改接受消息中包括的会话管理信息。
本实施例的步骤808-811与步骤710-713相似，区别在于，步骤809中，PDU会话修改确认消息中包括AMF分配的专有承载的承载标识。
本实施例中，在UE发起的PDU会话中专有流的建立过程中，SMF先为DNN对应的PDU会话中的专有流分配流标识，然后将该专有流的标识发送给AMF,节省了图7中的专有承载标识分配请求消息和专有承载标识分配响应消息，流程更加简单。
在图7和图8实施例中的专有流的建立过程中，SMF为专有流分配流标识。本申请还可以提供一种替换方案：SMF根据UE在5G网络中的PCC规则，将UE在5G网络中的PCC规则对应的业务数据流聚合到UE已经建立的一个专有流中，SMF将UE已经建立的专有流的流标识作为待建立的专有流的标识。可选的，SMF可以根据PCC规则中的QCI和ARP，决定是否将PCC规则对应的业务数据流聚合到UE已经建立的一个专有流中。例如：可以将业务数据流聚合到已经建立的一个具有相同QCI和ARP的专有流中。可选的，该替换方案可以应用到5G网络中一个PDU会话中的专有流的数量多于4G网络中一个PDN连接中专有承载的数量的情况，从而避免专有流和专有承载无法建立一一 对应关系的问题。当然，在专有流和专有承载可以建立一一对应关系的情况下，也可以采用本替换方案，在此不做限定。
在图7和图8实施例中的专有流的建立过程中，AMF为专有承载分配承载标识。本申请还可以提供一种替换方案：SMF根据UE在4G网络中的PCC规则，将UE在4G网络中的PCC规则对应的业务数据流聚合到UE已经建立的一个专有承载中，SMF将UE已经建立的专有承载的承载标识作为该业务数据流对应的专有承载的标识。可选的，SMF可以根据PCC规则中的QCI和ARP，决定是否将PCC规则对应的业务数据流聚合到UE已经建立的一个专有承载中。例如：可以将业务数据流聚合到已经建立的一个具有相同QCI和ARP的专有承载中。
图7和图8示出了UE发起PDU会话中专有流建立的流程。本申请实施例还提供一种网络侧发起PDU会话中专有流建立的流程。具体的，该实施例中的会话管理方法包括：
PCF接收应用功能网元发送的UE的业务要求。业务要求包括IP过滤信息、用于QoS控制的媒体带宽要求和应用带宽要求中的至少一个。可选的，业务要求可以包括业务连续性要求。
PCF根据UE的业务要求为UE生成在5G和4G网络中的PCC规则PCC规则。可选的，PCC规则包括UE在5G网络中的QCI、UE在4G网络中的QCI以及如下中的至少一个：上行和下行包过滤器、GBR、MBR和ARP。
PCF向SMF发送PDU-CAN会话修改请求消息。其中，PDU-CAN会话修改请求消息包括UE在5G和4G网络中的PCC规则。
本实施例接下来的步骤与步骤704-713或804-811相似，在此不再赘述。
本申请还提供一种UE跨通信网络切换方法。图9是本申请实施例的UE跨通信网络切换的一示意性流程图。该方法包括：
901 UE在5G网络中完成PDU会话和流建立的过程。
该过程可以参见本申请前文描述的会话管理方法和策略与计费控制方法，在此不再赘述。
902 当UE需要从5G网络切换到4G网络时，5G网络中的接入网设备向AMF发送切换请求。
903 AMF向SMF发送会话上下文请求消息。
904 AMF接收SMF发送的会话上下文响应消息。其中，会话上下文响应消息包括PDN连接中默认承载的承载标识和PCC规则，和/或，PDN连接中专有承载的承载标识和PCC规则。
905 AMF向MME发送重定位请求(relocation request)。其中，重定位请求包括指示信息，指示信息用于指示MME重新选择SGW。
可选的，重定位请求中，也可以将SGW的地址信息设置为0.0.0.0，从而指示MME重新选择SGW。
906 MME向选择的SGW发送会话建立请求消息。
907 MME接收SGW发送的会话建立响应消息。
本实施例中，为了保障5G网络到4G网络的切换，在切换之前，5G网络侧为4G网络预留会话管理资源，在切换过程中，5G网络将这些会话管理资源带给4G网络，4G网络根据这些会话管理资源能够迅速搭建业务，保证业务连续，并且简化了切换流程。
图10是根据本申请实施例的接入和移动性管理设备的示意性框图。该接入和移动性管理设备包括获取单元1001、分配单元1002、接收单元1003和发送单元1004。可选的，可选的，该获取单元1001和分配单元1002可以是接入和移动性管理设备的处理器，接收单元1003和发送单元1004可以是接入和移动性管理设备用于收发信息的通信接口。具体的，接收单元1003和发送单元1004可以参见图1所示通信架构中，接入和移动性管网元的通信接口。
获取单元1001用于获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。其中，所述终端在第一通信网络中的签约数据包括数据网络名称DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的接入点名称APN。
可选的，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文；所述发送单元向所述会话管理网元发送的PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
分配单元1002用于为所述APN对应的PDN连接中的承载分配承载标识。
接收单元1003用于接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识。
发送单元1004用于向所述终端发送所述承载标识和所述流标识。
所述接收单元1003还用于在为所述APN对应的PDN连接中的承载分配承载标识之前，接收所述终端发送的注册请求消息或者PDU会话建立请求消息；所述发送单元还用于在所述接收单元接收到所述注册请求消息或者所述PDU会话建立请求消息后，向所述会话管理网元发送PDU会话建立请求消息，其中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述PDU会话建立请求消息包括所述默认承载的承载标识。
所述接收单元1003还用于接收所述会话管理网元发送的专有承载标识分配请求消息；所述发送单元还用于向所述会话管理网元发送专有承载标识分配响应消息，其中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
所述接收单元1003用于接收所述会话管理网元发送的会话管理信息，所述会话管理信息包括所述流的授权后的服务质量QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
所述发送单元1004还用于向签约服务器发送位置更新请求消息；所述接收单元还用于接收所述签约服务器发送的位置更新响应消息，所述位置更新响应消息包括所述终端在所述第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。
所述接收单元1003还用于接收接入网设备发送的切换请求；所述发送单元还用于向所述会话管理网元发送会话上下文请求消息；所述接收单元还用于接收所述会话管理网元发送的会话上下文响应消息，所述会话上下文响应消息包括：所述PDN连接中默认承载的承载标识和策略与计费控制规则，和/或，所述PDN连接中专有承载的承载标识和策略与计费控制规则；所述发送单元还用于向移动性管理实体发送定位请求，所述定位请求包括指示信息，所述指示信息用于指示所述移动性管理实体重新选择服务网关。
本实施例中的获取单元1001和分配单元1002还用于实现图2-图9实施例中接入和移动性管理设备关于数据和信号处理的功能。接收单元1003和发送单元1004还用于实现图2-图9实施例中接入和移动性管理网元关于信息收发的功能。
图11是根据本申请实施例的会话管理设备的示意性框图。该会话管理设备包括获取单元1101、发送单元1102和接收单元1103。可选的，该获取单元1101可以是会话管理设备的处理器，发送单元1102和接收单元1103可以是会话管理设备用于收发信息的通信接口。具体的，发送单元1102和接收单元1103可以参见图1所示通信架构中，会话管理网元的通信接口。
获取单元1101用于获取终端的DNN对应的PDU会话中的流的流标识，获取所述终端的APN对应的PDN连接中的承载的承载标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN，所述APN为所述终端在第二通信网络中的签约数据中的APN。
发送单元1102用于向接入和移动性管理网元发送所述承载标识和所述流标识。
接收单元1103用于接收所述接入和移动性管理网元发送的PDU会话建立请求消息，其中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述PDU会话建立请求消息包括所述承载标识。
可选的，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文；所述PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
可选的，所述发送单元1102还用于向策略与计费网元发送PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文；所述接收单元还用于接收所述策略与计费网元发送的PDU-CAN会话建立响应消息，所述PDU-CAN会话建立响应消息包括所述终端在所述第一通信网络和所述终端在所述第二通信网络中的策略与计费控制PCC规则。
可选的，所述发送单元1102还用于向所述接入和移动性管理网发送专有承载标识分配请求消息；接收单元用于接收所述接入和移动性管理网元发送的专有承载标识分配响应消息，其中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
可选的，所述接收单元1103还用于接收接收策略与计费网元发送的PDU-CAN会话修改请求消息，所述PDU-CAN会话修改请求消息包括所述终端在第一通信网络和所述终端在第二通信网络中的PCC规则。
可选的，所述发送单元1103用于向所述接入和移动性管理网元发送会话管理信息，所述会话管理信息包括所述流的授权后的QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
可选的，所述获取单元1101根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有流中，所述会话管理网元获取的专有流的流标识为所述终端已经建立的专有流的流标识。
可选的，所述获取单元根据所述终端在第二通信网络中的PCC规则，将所述终端在 第二通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有承载中，所述会话管理网元获取的专有承载的承载标识为所述终端已经建立的专有承载的承载标识。
本实施例中的获取单元1101还用于实现图2-图9实施例中会话管理网元关于数据和信号处理的功能。发送单元1102和接收单元1103还用于实现图2-图9实施例中会话管理网元关于信息收发的功能。
图12是根据本申请实施例的策略与计费控制设备的示意性结构图。该策略与计费控制设备包括获取单元1201、发送单元1202和接收单元1203。可选的，该获取单元1201可以是策略与计费控制设备的处理器，发送单元1202和接收单元1203可以是策略与计费控制设备用于收发信息的通信接口。具体的，发送单元1202和接收单元1203可以参见图1所示通信架构中，策略与计费控制网元的通信接口。
获取单元1201用于获取终端的业务要求。
发送单元1202用于向会话管理网元发送PDU-CAN会话管理消息，所述PDU-CAN会话管理消息包括所述终端在第一通信网络和所述终端在第二通信网络的策略与计费控制PCC规则。
接收单元1203用于接收会话管理网元发送的PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述终端在第一通信网络中的DNN对应的签约上下文和所述终端在第二通信网络中的APN对应的PDN签约上下文。
可选的，所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的服务质量分类识别码、所述DNN对应的PDU会话中的默认流的授权后的Session-AMBR、所述终端在第二通信网络的服务质量分类识别码、以及所述APN对应的PDN连接中的默认承载的授权后的APN-AMBR。
可选的，所述接收单元1203用于接收所述终端或者应用功能网元发送的所述业务要求，所述业务要求包括互联网协议IP过滤信息、用于服务质量QoS控制的媒体带宽要求和应用带宽要求中的至少一个。
可选的，所述终端在第一通信网络和所述终端在第二通信网络的PCC规则包括：所述终端在第一通信网络的服务质量分类识别码、所述终端在第二通信网络的服务质量分类识别码以及如下中的至少一个：上行和下行包过滤器、保证比特速率GBR、最大比特率MBR和预留和分配优先级ARP。可选的，所述业务要求还包括：业务连续性要求。
本实施例中的获取单元1201还用于实现图2-图9实施例中策略与计费控制网元关于数据和信号处理的功能。发送单元1202和接收单元1203还用于实现图2-图9实施例中策略与计费控制设备网元关于信息收发的功能。
图13是根据本申请实施例的接入和移动性管理设备的另一示意性结构图。该接入和移动性管理设备包括处理器1301、存储器1302和通信接口1303。处理器1301、存储器1302以及通信接口1303可以通过总线1304相互连接。总线1304可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线404可以分为地址总线、数据总线、控制总线等。
图13中虽然仅仅示出了一个通信接口1303，该通信接口1303还可以是多个通信接口。例如：在图1所示的通信架构中，该通信接口可以包括N2接口、Nx接口、N11接 口、N15接口和N18接口。接入和移动性管理设备(例如AMF)通过对应的接口与其他核心网设备连接，并利用对应的接口进行信息的收发。
处理器1301可以是中央处理器(Central Processing Unit，CPU)，网络处理器(Network Processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(Application-Specific Integrated Circuit，ASIC)，可编程逻辑器件(Programmable Logic Device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(Complex Programmable Logic Device,CPLD)，现场可编程逻辑门阵列(Field-Programmable Gate Array，FPGA)，通用阵列逻辑(Generic Array Logic，GAL)或其任意组合。图13中虽然仅仅示出了一个处理器1301，但处理器1301还可以是多个处理器或处理单元。
该存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。在图13中，存储器1302还可以是处理器1301内的存储单元。
存储器1302中存储的指令可以使得处理器1301执行如下操作：通过通信接口1303获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的接APN；为所述APN对应的PDN连接中的承载分配承载标识；通过通信接口1303接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识；通过通信接口1303向所述终端发送所述承载标识和所述流标识。
本实施例中的处理器还用于实现图2-图9实施例中接入和移动性管理设备关于数据和信号处理的功能，并执行对应的数据和信号处理步骤。通信接口1303还用于实现图2-图9实施例中接入和移动性管理网元关于信息收发的功能，并执行对应的信息收发的步骤。
本申请实施例还提供另一种会话管理设备。该会话管理设备与图13中的接入和移动性管理具有相似的结构。但通信接口可以包括图1所示的通信架构中的N4接口、N7接口、N11接口、N10接口。会话管理设备(例如SMF)通过对应的接口与其他核心网设备连接，并利用对应的接口进行信息的收发。
对应的，会话管理设备的存储器中存储的指令可以使得处理器执行如下操作：获取终端的DNN对应的PDU会话中的流的流标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN；获取所述终端的APN对应的PDN连接中的承载的承载标识，其中，所述APN为所述终端在第二通信网络中的签约数据中的APN；通过通信接口向接入和移动性管理网元发送所述承载标识和所述流标识。
本实施例中的处理器还用于实现图2-图9实施例中会话管理网元关于数据和信号处理的功能，并执行对应的数据和信号处理步骤。通信接口还用于实现图2-图9实施例中会话管理网元关于信息收发的功能，并执行对应的信息收发的步骤。
本申请实施例还提供另一种策略与计费控制设备。该策略与计费控制设备与图13中的接入和移动性管理具有相似的结构。但通信接口可以包括图1所示的通信架构中的N7 接口和N15接口。策略与计费控制设备(例如PCR)通过对应的接口与其他核心网设备连接，并利用对应的接口进行信息的收发。
对应的，策略与计费控制设备的存储器中存储的指令可以使得处理器执行如下操作：获取终端的业务要求；通过通信接口向会话管理网元发送PDU-CAN会话管理消息，所述PDU-CAN会话管理消息包括所述终端在第一通信网络和所述终端在第二通信网络的策略与计费控制PCC规则。
本实施例中的处理器还用于实现图2-图9实施例中策略与计费控制设备关于数据和信号处理的功能，并执行对应的数据和信号处理步骤。通信接口还用于实现图2-图9实施例中策略与计费控制设备关于信息收发的功能，并执行对应的信息收发的步骤。
本发明的实施例还提供一种计算机存储介质或者计算机程序产品，用于存储上述存储器中存储的处理器可执行指令。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (33)

  1. 一种会话管理方法，其特征在于，包括：
    接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括数据网络名称DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的接入点名称APN；
    所述接入和移动性管理网元为所述APN对应的分组数据网PDN连接中的承载分配承载标识；
    所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的分组数据单元PDU会话中的流的流标识；
    所述接入和移动性管理网元向所述终端发送所述承载标识和所述流标识。
  2. 根据权利要求1所述的方法，其特征在于，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，
    所述接入和移动性管理网元为所述APN对应的PDN连接中的承载分配承载标识之前，所述方法还包括：
    所述接入和移动性管理网元接收所述终端发送的注册请求消息或者PDU会话建立请求消息；
    所述接入和移动性管理网元接收所述注册请求消息或者所述PDU会话建立请求消息后，所述方法还包括：
    所述接入和移动性管理网元向所述会话管理网元发送PDU会话建立请求消息，所述PDU会话建立请求消息包括所述默认承载的承载标识。
  3. 根据权利要求2所述的方法，其特征在于，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文；
    所述接入和移动性管理网元向所述会话管理网元发送的PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
  4. 根据权利要求1所述的方法，其特征在于，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流；
    所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识之前，所述方法还包括：
    所述接入和移动性管理网元接收所述会话管理网元发送的专有承载标识分配请求消息；
    所述接入和移动性管理网元向所述会话管理网元发送专有承载标识分配响应消息，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
  5. 根据权利要求1-4中任意一项所述的方法，其特征在于，所述接入和移动性管理网元接收会话管理网元发送的所述DNN对应的PDU会话中的流的流标识，包括：
    所述接入和移动性管理网元接收会话管理网元发送的会话管理信息，所述会话管理信息包括所述流的授权后的服务质量QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
  6. 根据权利要求1-5中任意一项所述的方法，其特征在于，所述接入和移动性管理网元获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，包括：
    所述接入和移动性管理网元向签约服务器发送位置更新请求消息；
    所述接入和移动性管理网元接收所述签约服务器发送的位置更新响应消息，所述位置更新响应消息包括所述终端在所述第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。
  7. 根据权利要求1-6中任意一项所述的方法，其特征在于，所述方法还包括：
    所述接入和移动性管理网元接收接入网设备发送的切换请求；
    所述接入和移动性管理网元向所述会话管理网元发送会话上下文请求消息；
    所述接入和移动性管理网元接收所述会话管理网元发送的会话上下文响应消息，所述会话上下文响应消息包括：
    所述PDN连接中默认承载的承载标识和策略与计费控制规则，和/或，
    所述PDN连接中专有承载的承载标识和策略与计费控制规则；
    所述接入和移动性管理网元向移动性管理实体发送重定位请求，所述重定位请求包括指示信息，所述指示信息用于指示所述移动性管理实体重新选择服务网关。
  8. 一种会话管理方法，其特征在于，包括：
    会话管理网元获取终端的数据网络名称DNN对应的分组数据单元PDU会话中的流的流标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN；
    所述会话管理网元获取所述终端的接入点名称APN对应的分组数据网PDN连接中的承载的承载标识，其中，所述APN为所述终端在第二通信网络中的签约数据中的APN；
    所述会话管理网元向接入和移动性管理网元发送所述承载标识和所述流标识。
  9. 根据权利要求8所述的方法，其特征在于，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，
    所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：
    所述会话管理网元接收所述接入和移动性管理网元发送的PDU会话建立请求消息，所述PDU会话建立请求消息包括所述承载标识。
  10. 根据权利要求9所述的方法，其特征在于，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文；
    所述PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向策略与计费网元发送PDU连接访问网络PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文；
    所述会话管理网元接收所述策略与计费网元发送的PDU-CAN会话建立响应消息，所述PDU-CAN会话建立响应消息包括所述终端在所述第一通信网络和所述终端在所述第二通信网络中的策略与计费控制PCC规则。
  12. 根据权利要求8所述的方法，其特征在于，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流；
    所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：
    所述会话管理网元向所述接入和移动性管理网发送专有承载标识分配请求消息；
    所述会话管理网元接收所述接入和移动性管理网元发送的专有承载标识分配响应消息，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：所述会话管理网元接收策略与计费网元发送的PDU-CAN会话修改请求消息，所述PDU-CAN会话修改请求消息包括所述终端在第一通信网络和所述终端在所述第二通信网络中的PCC规则。
  14. 根据权利要求8-13中任意一项所述的方法，其特征在于，所述会话管理网元向所述接入和移动性管理网元发送所述承载标识和所述流标识，包括：
    所述会话管理网元向所述接入和移动性管理网元发送会话管理信息，所述会话管理信息包括所述流的授权后的QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
  15. 根据权利要求13所述的方法，其特征在于，所述会话管理网元获取终端的DNN对应的PDU会话中的流的流标识，包括：
    所述会话管理网元根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有流中，所述会话管理网元获取的专有流的流标识为所述终端已经建立的专有流的流标识。
  16. 根据权利要求13所述的方法，其特征在于，所述会话管理网元获取所述终端的APN对应的PDN连接中的承载的承载标识，包括：
    所述会话管理网元根据所述终端在第二通信网络中的PCC规则，将所述终端在第二通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有承载中，所述会话管理网元获取的专有承载的承载标识为所述终端已经建立的专有承载的承载标识。
  17. 一种接入和移动性管理设备，其特征在于，包括：
    获取单元，用于获取终端在第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据，其中，所述终端在第一通信网络中的签约数据包括数据网络名称DNN，所述终端在第二通信网络中的签约数据包括与所述DNN对应的接入点名称APN；
    分配单元，用于为所述APN对应的分组数据网PDN连接中的承载分配承载标识；
    接收单元，用于接收会话管理网元发送的所述DNN对应的分组数据单元PDU会话中的流的流标识；
    发送单元，用于向所述终端发送所述承载标识和所述流标识。
  18. 根据权利要求17所述的接入和移动性管理设备，其特征在于，
    所述接收单元还用于在为所述APN对应的PDN连接中的承载分配承载标识之前，接收所述终端发送的注册请求消息或者PDU会话建立请求消息；
    所述发送单元还用于在所述接收单元接收到所述注册请求消息或者所述PDU会话建立请求消息后，向所述会话管理网元发送PDU会话建立请求消息，其中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述PDU会话建立请求消息包括所述默认承载的承载标识。
  19. 根据权利要求18所述的接入和移动性管理设备，其特征在于，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数据还包括所述APN对应的PDN签约上下文；所述发送单元向所述会话管理网元发送的PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
  20. 根据权利要求17所述的接入和移动性管理设备，其特征在于，
    所述接收单元还用于接收所述会话管理网元发送的专有承载标识分配请求消息；
    所述发送单元还用于向所述会话管理网元发送专有承载标识分配响应消息，其中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
  21. 根据权利要求17到20中任意一项所述的接入和移动性管理设备，其特征在于，
    所述接收单元用于接收所述会话管理网元发送的会话管理信息，所述会话管理信息包括所述流的授权后的服务质量QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
  22. 根据权利要求17到21中任意一项所述的接入和移动性管理设备，其特征在于，
    所述发送单元还用于向签约服务器发送位置更新请求消息；
    所述接收单元还用于接收所述签约服务器发送的位置更新响应消息，所述位置更新响应消息包括所述终端在所述第一通信网络中的签约数据和所述终端在第二通信网络中的签约数据。
  23. 根据权利要求17到22中任意一项所述的接入和移动性管理设备，其特征在于，
    所述接收单元还用于接收接入网设备发送的切换请求；
    所述发送单元还用于向所述会话管理网元发送会话上下文请求消息；
    所述接收单元还用于接收所述会话管理网元发送的会话上下文响应消息，所述会话上下文响应消息包括：所述PDN连接中默认承载的承载标识和策略与计费控制规则，和/或，所述PDN连接中专有承载的承载标识和策略与计费控制规则；
    所述发送单元还用于向移动性管理实体发送重定位请求，所述重定位请求包括指示信息，所述指示信息用于指示所述移动性管理实体重新选择服务网关。
  24. 一种会话管理设备，其特征在于，包括：
    获取单元，用于获取终端的数据网络名称DNN对应的分组数据单元PDU会话中的流的流标识，获取所述终端的接入点名称APN对应的分组数据网PDN连接中的承载的承载标识，其中，所述DNN为所述终端在第一通信网络中的签约数据中的DNN，所述APN为所述终端在第二通信网络中的签约数据中的APN；
    发送单元，用于向接入和移动性管理网元发送所述承载标识和所述流标识。
  25. 根据权利要求24所述的会话管理设备，其特征在于，还包括：
    接收单元，用于接收所述接入和移动性管理网元发送的PDU会话建立请求消息，其中，所述APN对应的PDN连接中的承载为默认承载，所述DNN对应的PDU会话中的流为默认流，所述PDU会话建立请求消息包括所述承载标识。
  26. 根据权利要求25所述的会话管理设备，其特征在于，所述终端在第一通信网络中的签约数据还包括所述DNN对应的签约上下文，所述终端在第二通信网络中的签约数 据还包括所述APN对应的PDN签约上下文；所述PDU会话建立请求消息还包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文。
  27. 根据权利要求26所述的会话管理设备，其特征在于，
    所述发送单元还用于向策略与计费网元发送PDU连接访问网络PDU-CAN会话建立请求消息，所述PDU-CAN会话建立请求消息包括所述DNN对应的签约上下文和所述APN对应的PDN签约上下文；
    所述接收单元还用于接收所述策略与计费网元发送的PDU-CAN会话建立响应消息，所述PDU-CAN会话建立响应消息包括所述终端在所述第一通信网络和所述终端在所述第二通信网络中的策略与计费控制PCC规则。
  28. 根据权利要求24所述的会话管理设备，其特征在于，
    所述发送单元还用于向所述接入和移动性管理网发送专有承载标识分配请求消息；
    所述会话管理设备还包括：
    接收单元，用于接收所述接入和移动性管理网元发送的专有承载标识分配响应消息，其中，所述APN对应的PDN连接中的承载为专有承载，所述DNN对应的PDU会话中的流为专有流，所述专有承载标识分配响应消息包括所述专有承载的承载标识。
  29. 根据权利要求28所述的会话管理设备，其特征在于，
    所述接收单元还用于接收接收策略与计费网元发送的PDU-CAN会话修改请求消息，所述PDU-CAN会话修改请求消息包括所述终端在第一通信网络和所述终端在第二通信网络中的PCC规则。
  30. 根据权利要求24-29中任意一项所述的会话管理设备，其特征在于，所述发送单元用于向所述接入和移动性管理网元发送会话管理信息，所述会话管理信息包括所述流的授权后的QoS规则和所述承载的授权后的QoS规则，其中，所述流的授权后的QoS规则包括所述流标识，所述承载的授权后的QoS规则包括所述承载标识。
  31. 根据权利要求29所述的会话管理设备，其特征在于，
    所述获取单元根据所述终端在第一通信网络中的PCC规则，将所述终端在第一通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有流中，所述会话管理网元获取的专有流的流标识为所述终端已经建立的专有流的流标识。
  32. 根据权利要求29所述的会话管理设备，其特征在于，
    所述获取单元根据所述终端在第二通信网络中的PCC规则，将所述终端在第二通信网络中的PCC规则对应的业务数据流聚合到所述终端已经建立的专有承载中，所述会话管理网元获取的专有承载的承载标识为所述终端已经建立的专有承载的承载标识。
  33. 一种计算机程序产品，包括计算机程序指令，当所述计算机程序指令在计算机上运行时，使得所述计算机执行如权利要求1-16中任意一项所述的方法。
PCT/CN2017/077371 2017-03-20 2017-03-20 会话管理方法、接入管理功能设备和会话管理设备 WO2018170696A1 (zh)

Priority Applications (14)

Application Number Priority Date Filing Date Title
CN202011096305.9A CN112218341B (zh) 2017-03-20 2017-03-20 承载标识分配方法、装置、系统以及计算机可读存储介质
BR112019019352A BR112019019352A2 (pt) 2017-03-20 2017-03-20 método para alocar identificador de portador, aparelho, sistema de comunicação, e mídia de armazenamento legível por computador
EP17902485.6A EP3591999B1 (en) 2017-03-20 2017-03-20 Session management method, access management function device and session management device
JP2019549427A JP6888110B2 (ja) 2017-03-20 2017-03-20 ベアラ識別子を割り当てるための方法、装置、通信システム及びコンピュータ読み取り可能記憶媒体
PCT/CN2017/077371 WO2018170696A1 (zh) 2017-03-20 2017-03-20 会话管理方法、接入管理功能设备和会话管理设备
KR1020197029014A KR102432103B1 (ko) 2017-03-20 2017-03-20 베어러 식별자를 할당하기 위한 방법, 장치, 통신 시스템, 및 컴퓨터 판독가능 저장 매체
AU2017405723A AU2017405723B2 (en) 2017-03-20 2017-03-20 Session management method, access management function device and session management device
ES17902485T ES2851299T3 (es) 2017-03-20 2017-03-20 Método de gestión de sesión, dispositivo de función de gestión de acceso y dispositivo de gestión de sesión
CN201780087527.4A CN110431862B (zh) 2017-03-20 2017-03-20 承载标识分配方法、装置、系统以及计算机可读存储介质
KR1020217037974A KR20210145318A (ko) 2017-03-20 2017-03-20 베어러 식별자를 할당하기 위한 방법, 장치, 통신 시스템, 및 컴퓨터 판독가능 저장 매체
EP20197358.3A EP3826337B1 (en) 2017-03-20 2017-03-20 Session management methods, access management function device and session management device
US16/575,585 US10980071B2 (en) 2017-03-20 2019-09-19 Method for allocating bearer identifier, apparatus, and system
US17/226,398 US11622395B2 (en) 2017-03-20 2021-04-09 Method for allocating bearer identifier, apparatus, and system
US18/194,234 US20230328813A1 (en) 2017-03-20 2023-03-31 Method for Allocating Bearer Identifier, Apparatus, and System

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077371 WO2018170696A1 (zh) 2017-03-20 2017-03-20 会话管理方法、接入管理功能设备和会话管理设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/575,585 Continuation US10980071B2 (en) 2017-03-20 2019-09-19 Method for allocating bearer identifier, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2018170696A1 true WO2018170696A1 (zh) 2018-09-27

Family

ID=63585912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077371 WO2018170696A1 (zh) 2017-03-20 2017-03-20 会话管理方法、接入管理功能设备和会话管理设备

Country Status (9)

Country Link
US (3) US10980071B2 (zh)
EP (2) EP3826337B1 (zh)
JP (1) JP6888110B2 (zh)
KR (2) KR102432103B1 (zh)
CN (2) CN110431862B (zh)
AU (1) AU2017405723B2 (zh)
BR (1) BR112019019352A2 (zh)
ES (1) ES2851299T3 (zh)
WO (1) WO2018170696A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972216A (zh) * 2018-09-30 2020-04-07 华为技术有限公司 通信方法和装置
CN111031581A (zh) * 2018-10-09 2020-04-17 中兴通讯股份有限公司 一种4/5g互切换场景下锚定smf+pgw-c的方法及系统
JP2020522957A (ja) * 2017-06-06 2020-07-30 チャイナ アカデミー オブ テレコミュニケーションズ テクノロジー セッション管理方法および装置
WO2021136360A1 (zh) * 2020-01-03 2021-07-08 中国移动通信有限公司研究院 服务区域切换处理方法及设备
CN114945159A (zh) * 2019-10-30 2022-08-26 大唐移动通信设备有限公司 直接通信的处理方法、装置、中继终端及远端终端
EP3928554A4 (en) * 2019-02-18 2022-11-23 Telefonaktiebolaget LM Ericsson (publ) CONNECTION ESTABLISHMENT METHODS AND APPARATUS
US12016068B2 (en) 2019-05-06 2024-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for session management

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018170696A1 (zh) * 2017-03-20 2018-09-27 华为技术有限公司 会话管理方法、接入管理功能设备和会话管理设备
KR102329925B1 (ko) 2017-08-14 2021-11-23 삼성전자 주식회사 4g/5g 동시 등록된 이동 통신 단말을 위한 네트워크 이동시 데이터 동기화 제공 방안
WO2019057305A1 (en) * 2017-09-25 2019-03-28 Motorola Mobility Llc DETERMINING DYNAMIC POLICY RULES IN A MOBILE NETWORK USING SUBSCRIPTION DATA IN AN APPLICATION SERVER
CN110035401B (zh) * 2018-01-12 2020-06-23 电信科学技术研究院有限公司 一种默认服务质量QoS控制方法及设备
MX2021001172A (es) * 2018-07-31 2021-04-19 Ericsson Telefon Ab L M Un metodo y dispositivos para actualizar una ubicacion de un equipo de usuario, ue, cuando dicho ue se mueva de un primer tipo de red de telecomunicaciones a un segundo tipo de red de telecomunicaciones.
WO2020102238A1 (en) 2018-11-13 2020-05-22 Butterfield Kyle Auxiliary energy system architecture
KR102686161B1 (ko) * 2019-05-03 2024-07-18 삼성전자 주식회사 이동통신 시스템에서 시간 또는 서비스 지역에 따른 단말의 세션 설정 관리 방법 및 장치
US11412092B2 (en) * 2019-06-24 2022-08-09 Qualcomm Incorporated User equipment policy management in evolved packet systems and fifth generation systems interworking
EP4032344A1 (en) * 2019-10-07 2022-07-27 Telefonaktiebolaget LM Ericsson (publ) Dnn manipulation using selection priority
KR20210058479A (ko) * 2019-11-14 2021-05-24 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스의 인터워킹을 제공하기 위한 장치 및 방법
CN115004635A (zh) * 2020-01-07 2022-09-02 华为技术有限公司 签约信息获取方法及装置
US20230164652A1 (en) * 2020-02-13 2023-05-25 Telefonaktiebolaget Lm Ericsson (Publ) Re-selection of a pgw-c/smf in the desired network slice
EP4311169A3 (en) 2020-03-23 2024-03-20 Samsung Electronics Co., Ltd. Method and apparatus for managing data session in wireless communication system
GB2593673B (en) * 2020-03-23 2023-03-08 Samsung Electronics Co Ltd Data session management
CN113709905B (zh) * 2020-05-22 2023-10-13 华为技术有限公司 一种通信方法、装置及计算机可读存储介质
CN113747547B (zh) * 2020-05-28 2023-05-05 维沃移动通信有限公司 业务获取方法、装置、通信设备及可读存储介质
US11930427B2 (en) * 2020-10-08 2024-03-12 Mediatek Inc. Configuration enhancements on access point name (APN) or data network name (DNN) selection in user equipment (UE)
CN115250505B (zh) * 2021-04-28 2024-07-16 中国移动通信集团四川有限公司 应用于通信网络的通信方法及系统
WO2023184157A1 (en) * 2022-03-29 2023-10-05 Lenovo (Beijing) Limited 5gs user plane handling enhancement for xr service
CN114710797B (zh) * 2022-04-13 2024-04-09 中国联合网络通信集团有限公司 网络信令处理方法、装置、设备和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588548A (zh) * 2008-05-22 2009-11-25 华为技术有限公司 通信数据接入方法和系统及接入网关
WO2017034352A1 (ko) * 2015-08-25 2017-03-02 엘지전자 주식회사 기지국 접속 방법 및 이를 수행하는 사용자 장치

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011120235A1 (zh) * 2010-04-02 2011-10-06 华为技术有限公司 Sae架构下实现业务数据流旁路的方法、装置及系统
CN102986271B (zh) * 2010-06-28 2015-08-19 华为技术有限公司 目标侧承载的承载标识的获取方法、承载管理网元和分组数据网关
EP2991282A4 (en) * 2013-05-15 2016-04-13 Huawei Tech Co Ltd INFORMATION TRANSMISSION METHOD, MACHINE, COMMUNICATION DEVICE AND COMMUNICATION SYSTEM
EP2854447B1 (en) 2013-09-30 2017-06-28 Alcatel Lucent On-demand qos for data connections
US9730062B2 (en) 2015-04-30 2017-08-08 Intel IP Corporation AT command for secure ESM information
US10548046B2 (en) * 2015-08-17 2020-01-28 Lg Electronics Inc. Method of transmitting and receiving packet in wireless communication system and apparatus therefor
JP6777451B2 (ja) * 2016-08-10 2020-10-28 株式会社Ｎｔｔドコモ 基地局
WO2018170696A1 (zh) * 2017-03-20 2018-09-27 华为技术有限公司 会话管理方法、接入管理功能设备和会话管理设备
US10681607B2 (en) * 2018-06-22 2020-06-09 Intel Corporation Receive-side scaling for wireless communication devices

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588548A (zh) * 2008-05-22 2009-11-25 华为技术有限公司 通信数据接入方法和系统及接入网关
WO2017034352A1 (ko) * 2015-08-25 2017-03-02 엘지전자 주식회사 기지국 접속 방법 및 이를 수행하는 사용자 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP Technical Specification Group Services and System Aspects ;. System Architecture for the 5G System ; Stage 2 (Release 15", 3GPP TS 23.501 V0.3.0., 28 February 2017 (2017-02-28), pages 1 - 97, XP055540705 *
HUAWEI ET AL., TS 23.501: DESCRIPTION OF DNN . SAWG2 MEETING #119 S2-171064, 17 February 2017 (2017-02-17), XP051217182 *
NOKIA ET AL., 23.501 §5.9.3: DNN VERSUS APN . SA WG2 MEETING #119 S2-170888, 17 February 2017 (2017-02-17), XP051217009 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020522957A (ja) * 2017-06-06 2020-07-30 チャイナ アカデミー オブ テレコミュニケーションズ テクノロジー セッション管理方法および装置
US11012895B2 (en) 2017-06-06 2021-05-18 China Academy Of Telecommunications Technology Session management method and apparatus
CN110972216A (zh) * 2018-09-30 2020-04-07 华为技术有限公司 通信方法和装置
EP3820197A4 (en) * 2018-09-30 2021-09-29 Huawei Technologies Co., Ltd. COMMUNICATION PROCESS AND DEVICE
US12004021B2 (en) 2018-09-30 2024-06-04 Huawei Technologies Co., Ltd. Communications method and apparatus
CN111031581A (zh) * 2018-10-09 2020-04-17 中兴通讯股份有限公司 一种4/5g互切换场景下锚定smf+pgw-c的方法及系统
CN111031581B (zh) * 2018-10-09 2023-01-03 中兴通讯股份有限公司 一种4/5g互切换场景下锚定smf+pgw-c的方法及系统
EP3928554A4 (en) * 2019-02-18 2022-11-23 Telefonaktiebolaget LM Ericsson (publ) CONNECTION ESTABLISHMENT METHODS AND APPARATUS
US12016068B2 (en) 2019-05-06 2024-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for session management
CN114945159A (zh) * 2019-10-30 2022-08-26 大唐移动通信设备有限公司 直接通信的处理方法、装置、中继终端及远端终端
WO2021136360A1 (zh) * 2020-01-03 2021-07-08 中国移动通信有限公司研究院 服务区域切换处理方法及设备

Also Published As

Publication number Publication date
KR20210145318A (ko) 2021-12-01
US20230328813A1 (en) 2023-10-12
US20210227598A1 (en) 2021-07-22
CN112218341A (zh) 2021-01-12
US20200015294A1 (en) 2020-01-09
CN110431862A (zh) 2019-11-08
EP3591999A1 (en) 2020-01-08
KR102432103B1 (ko) 2022-08-11
AU2017405723A1 (en) 2019-10-03
CN112218341B (zh) 2023-07-14
CN110431862B (zh) 2020-11-03
US10980071B2 (en) 2021-04-13
JP2020510345A (ja) 2020-04-02
AU2017405723B2 (en) 2020-12-17
EP3591999A4 (en) 2020-03-04
JP6888110B2 (ja) 2021-06-16
EP3826337C0 (en) 2024-05-29
ES2851299T3 (es) 2021-09-06
US11622395B2 (en) 2023-04-04
BR112019019352A2 (pt) 2020-04-14
EP3826337B1 (en) 2024-05-29
KR20190121375A (ko) 2019-10-25
EP3591999B1 (en) 2020-11-18
EP3826337A1 (en) 2021-05-26

Similar Documents

Publication Publication Date Title
WO2018170696A1 (zh) 会话管理方法、接入管理功能设备和会话管理设备
US9717019B2 (en) Data flow control method, and related device and communications system
CN106465227B (zh) 经由多个无线接入来支持网络ip流移动性的方法和设备
WO2019062499A1 (zh) 一种策略确定的方法及通信装置
CA3030741A1 (en) Method for processing pdu session establishment procedure and amf node
US20140198637A1 (en) Handling User Plane Congestion
JP5463418B2 (ja) 拡張されたアロケーション／リテンションポリシーの解決策
US11589256B2 (en) QoS in hybrid communication networks
WO2018232605A1 (en) METHODS AND SYSTEM FOR TRANSFER BETWEEN SYSTEMS
EP2547049A1 (en) Method, system and corresponding apparatus for implementing policy and charging control
CN107295564B (zh) 一种基于流的承载管理方法、数据传输方法及装置
WO2018082070A1 (zh) 一种数据报文处理方法及控制面网元、用户面网元
WO2020063316A1 (zh) 通信方法和装置
CN103200628A (zh) 一种通过非3gpp接入核心网的方法和系统
CN107006057B (zh) 控制无线局域网接入
EP2854447B1 (en) On-demand qos for data connections
WO2011110012A1 (zh) 服务质量参数的处理方法、设备及系统
WO2018045834A1 (zh) 一种VoLTE业务处理方法及装置
KR101954397B1 (ko) Ｌｔｅ 이동통신 시스템에서 패킷 차단 방법 및 패킷 차단 시스템
CN111567109B (zh) 混合通信网络中的QoS
WO2011054145A1 (zh) 因特网协议地址的通知方法、系统及设备

Legal Events

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

Ref document number: 17902485

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2019549427

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019019352

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20197029014

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017405723

Country of ref document: AU

Date of ref document: 20170320

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017902485

Country of ref document: EP

Effective date: 20190930

ENP Entry into the national phase

Ref document number: 112019019352

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190917