WO2019034078A1 - 一种会话处理方法及装置 - Google Patents

一种会话处理方法及装置 Download PDF

Info

Publication number
WO2019034078A1
WO2019034078A1 PCT/CN2018/100641 CN2018100641W WO2019034078A1 WO 2019034078 A1 WO2019034078 A1 WO 2019034078A1 CN 2018100641 W CN2018100641 W CN 2018100641W WO 2019034078 A1 WO2019034078 A1 WO 2019034078A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
type
message
terminal
entity
Prior art date
Application number
PCT/CN2018/100641
Other languages
English (en)
French (fr)
Inventor
王远
陈中平
徐长春
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to AU2018317155A priority Critical patent/AU2018317155A1/en
Priority to BR112020003140-2A priority patent/BR112020003140A2/pt
Priority to RU2020110522A priority patent/RU2776678C2/ru
Priority to EP18845744.4A priority patent/EP3668257B1/en
Publication of WO2019034078A1 publication Critical patent/WO2019034078A1/zh
Priority to US16/791,775 priority patent/US11540337B2/en

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • 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/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • 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/02—Data link layer protocols
    • 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
    • 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 present application relates to the field of mobile communications technologies, and in particular, to a session processing method and apparatus.
  • PDU packet data unit
  • the present application provides a session processing method and apparatus for establishing a correct type of PDU session for a terminal.
  • the present application provides a session processing method, including: a terminal initiating an application APP, determining a session type of a packet data unit PDU session according to an application APP; and transmitting, by the terminal, a first message to an access and mobility management function AMF entity, where The first message includes the session type, and the first message is used to request to establish a PDU session of the session type.
  • the terminal when the terminal initiates a first message for requesting to establish a PDU session to the AMF entity, the terminal carries the session type of the PDU session in the first message, so that the network side can establish a corresponding type according to the session type of the PDU session sent by the terminal.
  • the PDU session thus establishing the correct type of PDU session for the terminal, improves the correctness of communication between the terminal and the network side.
  • the determining, by the terminal, the session type of the PDU session the determining, by the terminal, the session type corresponding to the APP according to the first correspondence, wherein the first correspondence is APP Correspondence with the session type of the PDU session.
  • the terminal determines the session type of the PDU session according to the correspondence between the APP and the session type of the PDU session, which is simple and easy to implement.
  • the first correspondence is pre-configured at the terminal; or the first correspondence is obtained by the terminal from the AMF entity.
  • the terminal determines the session type of the PDU session, including: determining, by the terminal, the DN identifier corresponding to the APP according to the second correspondence, and determining, by the terminal, the DN type corresponding to the DN identifier.
  • the terminal determines the session type corresponding to the DN type according to the third correspondence, where the second correspondence is a correspondence between the APP and the DN identifier, and the third correspondence is a DN type and a PDU. The correspondence of the session type of the session.
  • the terminal sends a request message to the AMF entity, and receives the DN identifier and the DN type sent by the AMF entity according to the request message; or, the terminal receives The DN identifier and the DN type broadcast by the radio access network RAN device.
  • the terminal sends first DN information to the AMF entity, where the first DN information includes a DN identifier or includes a DN identifier and a DN type, and the first DN information is used for the
  • the AMF entity determines an SMF entity based on the DN identity, the SMF entity being used to establish a PDU session of the session type.
  • the present application provides a session processing method, including: a session management function SMF entity receives a second message from an access and mobility management function AMF entity, and the second message includes a packet data unit PDU session requested by the terminal.
  • the session type, the second message is used to request to establish a PDU session; the SMF entity establishes a PDU session according to the session type of the PDU session.
  • the SMF entity receives a DN identity from the AMF entity
  • the SMF entity determines a user plane function UPF entity according to the DN identifier and the session type of the PDU session, and the UPF entity is used to establish a PDU session of the session type.
  • the present application provides a session processing method, including: a session management function SMF entity receives a second message from an access and mobility management function AMF entity, and the second message includes a second data network DN information, The second message is used to request to establish a PDU session; the SMF entity determines a session type of the PDU session according to the second DN information.
  • the SMF entity determines, according to the second DN information, a session type of the PDU session, that the SMF entity is identified according to the DN. Determining a DN type, and determining a session type of the PDU session according to the DN type; or
  • the SMF entity determines the session type of the PDU session according to the second DN information, including: determining, by the SMF entity, the PDU session according to the DN type. The type of session.
  • the method further includes:
  • the SMF entity sends a session reject message to the terminal, where the session reject message includes a session type of the PDU session determined by the SMF entity according to the second DN information.
  • the SMF entity establishes a PDU session according to the session type of the PDU session.
  • the SMF entity determines a user plane function UPF entity according to the second DN information, and establishes a PDU session of the session type with the UPF entity.
  • the application provides a session processing method, including: an access and mobility management function AMF entity receives a first message from a terminal and a first data network DN information, where the first message is used to request to establish a PDU session. Determining, by the AMF entity, a session management function SMF entity according to the first DN information; the AMF entity sending, according to the first message, a second message to the SMF entity, where the second message is used to request to establish a PDU a session, wherein a session type of the PDU session corresponds to the first DN information.
  • the first message and the second message include a session type of a PDU session requested by the terminal; or the first DN information includes a DN identifier, and the second message includes the DN And the DN identifier is used by the SMF entity to determine a session type of the PDU session according to the DN identifier.
  • the first DN information includes a DN identifier
  • Determining, by the AMF entity, a session management function SMF entity according to the first DN information including:
  • the AMF entity receives the SMF entity from the NRF entity, the SMF entity being determined by the NRF entity based on the DN identity and the DN type.
  • the AMF entity receives a message requesting registration from a terminal
  • the AMF entity obtains the DN information of the terminal subscription from the database according to the message that the request is registered, and the signed DN information includes a DN identifier and a DN type;
  • the AMF entity sends the DN information of the terminal subscription to the terminal.
  • the message requesting registration includes capability indication information of the terminal, and the capability indication information is used to indicate a data network supported by the terminal;
  • the DN information subscribed by the terminal corresponds to the data network supported by the terminal.
  • the present application provides a device, which may be a terminal or a chip in a terminal.
  • the device has the functionality to implement the various embodiments of the first aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the terminal when the device is a terminal, the terminal comprises: a processing unit and a communication unit, the processing unit may be, for example, a processor, the communication unit may be, for example, a transceiver, the transceiver including a radio frequency Circuitry, optionally, the terminal further includes a storage unit, which may be, for example, a memory.
  • the storage unit is configured to store a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the terminal performs any one of the foregoing first aspects.
  • the session processing method of the item when the device is a terminal, the terminal comprises: a processing unit and a communication unit, the processing unit may be, for example, a processor, the communication unit may be, for example, a transceiver, the transceiver including a radio frequency Circuitry, optionally, the terminal further includes a storage unit, which may be, for example, a memory.
  • the storage unit is configured to store
  • the chip comprises: a processing unit and a communication unit
  • the processing unit may be, for example, a processor
  • the communication unit may be, for example, an input/output interface, Pin or circuit, etc.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the session processing method of any of the above aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc.
  • the storage unit may also be a storage unit located outside the chip in the terminal, such as a read-only memory (read) -only memory, ROM) or other types of static storage devices, random access memory (RAM), etc. that can store static information and instructions.
  • the processor mentioned in any of the above may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more An integrated circuit for controlling program execution of the above-described first aspect session processing method.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the application provides a device, which may be an SMF entity or a chip within an SMF entity.
  • the device has the functionality to implement the various embodiments of the second aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the SMF entity when the device is an SMF entity, the SMF entity comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, a transceiver, the transceiver The radio frequency circuit is included.
  • the SMF entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit is configured to store a computer execution instruction
  • the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the SMF entity to perform the second aspect Any one of the session processing methods.
  • the chip when the device is a chip within an SMF entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/output interface , pins or circuits, etc.
  • the processing unit may execute computer execution instructions stored by the storage unit such that the session processing method of any of the above second aspects is performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the SMF entity, such as a ROM or may be stored. Static information and instructions for other types of static storage devices, RAM, etc.
  • the processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the first aspect session processing method. .
  • the present application provides an apparatus, which may be an SMF entity or a chip within an SMF entity.
  • the device has the functionality to implement the various embodiments of the third aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the SMF entity when the device is an SMF entity, the SMF entity comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, a transceiver, the transceiver The radio frequency circuit is included.
  • the SMF entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit is configured to store a computer execution instruction
  • the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the SMF entity to perform the third aspect described above Any one of the session processing methods.
  • the chip when the device is a chip within an SMF entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/output interface , pins or circuits, etc.
  • the processing unit may execute computer execution instructions stored by the storage unit such that the session processing method of any of the above third aspects is executed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the SMF entity, such as a ROM or may be stored. Static information and instructions for other types of static storage devices, RAM, etc.
  • the processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the first aspect session processing method. .
  • the present application provides an apparatus, which may be an AMF entity or a chip within an AMF entity.
  • the device has the functionality to implement the various embodiments of the fourth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the AMF entity when the device is an AMF entity, the AMF entity comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, a transceiver, the transceiver Including a radio frequency circuit, optionally, the AMF entity further includes a storage unit, which may be, for example, a memory.
  • the AMF entity includes a storage unit, the storage unit is configured to store a computer execution instruction, the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the AMF entity to perform the fourth aspect described above Any one of the session processing methods.
  • the chip when the device is a chip within an AMF entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/output interface , pins or circuits, etc.
  • the processing unit may execute computer execution instructions stored by the storage unit such that the session processing method of any of the above fourth aspects is executed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the AMF entity, such as a ROM or may be stored. Static information and instructions for other types of static storage devices, RAM, etc.
  • the processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the fourth aspect of the above-described session processing method. .
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the present application further provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method of the first aspect described above.
  • the computer can be, for example, a terminal.
  • the present application further provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method described in the second aspect above.
  • the computer may for example be an SMF entity.
  • the present application further provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method described in the third aspect above.
  • the computer may for example be an SMF entity.
  • the present application further provides a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method described in the fourth aspect above.
  • the computer may for example be an AMF entity.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in the session processing method of any of the above first aspects.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in the session processing method of any of the above second aspects.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in the session processing method of any of the above third aspects.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in the session processing method of any of the above fourth aspects.
  • FIG. 1 is a schematic diagram of a possible network architecture to which the present application applies;
  • FIG. 3 is a flowchart of another method for processing a session provided by the present application.
  • FIG. 4 is a schematic structural view of a device provided by the present application.
  • the session processing method of the present application may be performed by a device.
  • the device On the network side, the device may be a session management function (SMF) entity or a chip in an SMF entity, and the device may also be an Access and Mobility Management Function (AMF) entity or an AMF.
  • SMF session management function
  • AMF Access and Mobility Management Function
  • the present application taking the device as an AMF entity, an SMF entity, and a terminal as an example, describes a session processing method, and the device is a chip in an AMF entity, or a chip in an SMF entity, or a chip in a terminal.
  • the implementation method refer to the specific description of the session processing method of the AMF entity, the SMF entity, or the terminal, and the description is not repeated.
  • the network framework diagram includes a terminal, a 3rd Generation Partnership Project (3GPP) access network entity, and a non-3GPP access network (Non -3GPP), N3IWF, AMF entity, session management function (SMF) entity, user plane function (UPF) entity, and data network (DN).
  • 3GPP 3rd Generation Partnership Project
  • Non -3GPP non-3GPP access network
  • N3IWF N3IWF
  • AMF session management function
  • UPF user plane function
  • DN data network
  • the terminal is a device with wireless transceiver function, which can be deployed on land, indoors or outdoors, handheld or on-board; it can also be deployed on the water surface (such as ships); it can also be deployed in the air (such as airplanes, balloons). And satellites, etc.).
  • the terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transport safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the 3GPP access network entity is also referred to as a radio access network (RAN) entity, and may be, for example, a base station in 5G.
  • the Non-3GPP access network refers to an access network other than 3GPP, such as a wireless local area networks (WLAN) access network.
  • the N3IWF is similar to the evolved packet data gateway (ePDG) in the long term evolution (LTE).
  • ePDG evolved packet data gateway
  • LTE long term evolution
  • IPsec Internet protocol security
  • the name of the N3IWF may change.
  • the AMF entity is responsible for the access management and mobility management of the terminal. In practical applications, it includes the mobility management function in the mobility management entity (MME) in the network framework of long term evolutio (LTE). And joined the access management function.
  • MME mobility management entity
  • LTE long term evolutio
  • the SMF entity is responsible for session management, such as session establishment of the user, that is, the session management function in the MME entity.
  • the UPF entity is a functional entity of the end user plane and is mainly responsible for connecting to an external network, and includes related functions of a LTE serving gateway (SGW) and a public data network (PDN) gateway.
  • the DN is responsible for providing data services for the terminal, such as providing Internet access and SMS functions for the terminal.
  • the DN identifier is used to identify a data network.
  • a new attribute is set to the DN type, and the DN type (Type) is used to indicate the type of the data network.
  • the DN type includes an internet, an Ethernet, an unstructured network, and the like.
  • the DN identifier and/or the DN type may also be collectively referred to as DN information, that is, the DN information includes the DN identifier, or the DN information includes the DN type, or the DN information includes the DN identifier and the DN type.
  • a data network name (DNN) is currently used to identify a data network.
  • the DNN is only used as an identifier of the data network, that is, a DN identifier.
  • DN DN identifier
  • the first implementation manner is that the DN identifier and the DN type can be represented by separate cells, that is, the DN identifier is still identified by the DNN defined in the current 3GPP standard, and a new cell DN Type is separately defined to identify the DN. Types of.
  • the second implementation is that the DN identifier and the DN type can be represented by the same cell.
  • the DNN can represent both the DN identity and the DN type. That is, a field is added to the current DNN, which is a DN type, that is, the extended DNN includes a DN identifier and a DN type.
  • the field of the DNN may be defined as being divided into two parts. The value of the former part of the field is used to identify the DN identifier. For example, 0001 identifies an intranet, and the value of the latter part is used to identify the DN. A type, such as 0002, identifies the enterprise intranet as an Ethernet type. Then the full field 00010002 is the specific value of the DNN.
  • the DNN includes two pieces of information, a DN identifier and a DN type.
  • the DN identifier is referred to in the subsequent embodiment, which refers to the DNN (the first implementation manner), or the field used to identify the data network in the DNN (the second implementation manner) .
  • the present application provides a session processing method, including: a terminal initiating an application APP, determining a session type of a packet data unit PDU session according to an application APP; and transmitting, by the terminal, an access and mobility management function AMF entity.
  • the first message includes the session type, and the first message is used to request to establish a PDU session of the session type.
  • the terminal when the terminal initiates a first message for requesting to establish a PDU session to the AMF entity, the terminal carries the session type of the PDU session in the first message, so that the network side can establish a corresponding type according to the session type of the PDU session sent by the terminal.
  • the PDU session thus establishing the correct type of PDU session for the terminal, improves the correctness of communication between the terminal and the network side.
  • the terminal can determine the session type of the PDU session and send it to the network side to establish a PDU session.
  • a flowchart of a session processing method provided by the present application includes:
  • Step 201 The terminal initiates an APP, and determines a session type of the PDU session according to the application APP.
  • the application may be a specific application, such as "Youku”, “Baidu”, etc., or may be a certain type of application, such as a video application, a text application, a picture application, and the like.
  • the session type of the PDU session may be determined according to the APP. Two implementations are given below, as exemplarily illustrated.
  • Implementation manner 1 The terminal determines the session type of the PDU session corresponding to the APP according to the first correspondence.
  • the first correspondence records the correspondence between the APP and the session type of the PDU session corresponding to the APP.
  • the first correspondence may be recorded in the form of a table, or may be recorded in the form of an array, or may be recorded in the form of a function, which is not limited in this application.
  • the UE Route Selection Policies (URSP) table in the prior art can be implemented. As shown in Table 1, it is a URSP table in the prior art.
  • URSP UE Route Selection Policies
  • the traffic filter refers to a data matching rule.
  • the parameter is used to determine whether other policies can be applied according to the APP initiated by the terminal. For example, in the above table 1, when the terminal initiates the Youku APP, because Youku is a video application, Then the strategy determines that other strategies in the table apply to Youku APP. If the terminal initiates WeChat APP, other policies in the table are not applicable. .
  • Direct offload refers to a data offloading strategy. This parameter is used to determine that the APP or a certain type of APP can use data offloading. For example, in Table 1, Prohibited means that video applications cannot use data offloading.
  • the Slice Info refers to the slice information, which is used to determine the slice information that is required to be used by the UE, so that the UE carries the PDU session. For example, in Table 1, the UE determines that the slice information needs to be used when the APP is initiated. S-NSSAI-a.
  • Continuity Types refers to the type of session continuity. This parameter is used to determine the type of session continuity required by the APP. For example, in Table 1, the UE determines the type of session continuity required when launching the APP as SSC mode3. .
  • the DN identifier refers to the identifier of the data network.
  • the parameter is used to indicate the name of the data network.
  • the data network indicated by the DN identifier in Table 1 above is the internet.
  • the Access Type refers to the access type.
  • the parameter is used to determine the access type required by the APP. For example, in the above Table 1, the UE determines that the required access type is the 3GPP access type when initiating the APP.
  • the PDU Type attribute may be added in the above Table 1, and the PDU Type refers to the session of the PDU session. Type, thus establishing the first correspondence.
  • the URSP table is added to the "PDU Type" attribute.
  • the PDU Type corresponding to the DummyApp is determined to be Ethernet according to the first correspondence in the foregoing table 2, that is, the correspondence between the DummyApp and the PDU Type.
  • the first correspondence may be pre-configured in the terminal, or may be obtained by the terminal from the network side, such as an AMF entity.
  • the URSP table may be pre-configured in the terminal; on the other hand, when the terminal moves to the coverage of a certain data network, the URSP of the data network broadcast may be received.
  • the terminal may store the received URSP table locally or update the locally stored URSP table according to the received URSP table.
  • Implementation 2 The terminal determines the session type of the PDU session according to the APP, the DN identifier, and the DN type.
  • the terminal may first obtain the DN information from the network side, such as an AMF entity, including the DN identifier and the DN type. Acquisition methods include but are not limited to:
  • Method 1 The terminal sends a request message to the AMF entity for requesting to obtain the DN identifier and the DN type.
  • the terminal may send a message requesting registration to the AMF entity.
  • the AMF entity After receiving the message requesting registration, the AMF entity obtains the DN information of the terminal subscription from the database, where the DN information includes the DN identifier and The DN type, then, the AMF entity sends the DN identity and the DN type to the terminal, so that the terminal acquires the DN identity and the DN type.
  • the message requesting the registration includes the capability indication information of the terminal, where the capability indication information is used to indicate the data network supported by the terminal, and the signed DN information sent by the AMF entity to the terminal is the DN information corresponding to the data network supported by the terminal.
  • the capability indication information indicates that the data network supported by the terminal is the internet
  • the DN information of the DN subscription sent by the AMF entity to the terminal includes the DN identifier and the DN type of the internet, and does not include the DN identifier and the DN type of other data networks.
  • the AMF entity sends the DN information or the DN identifier to the PCF entity.
  • the PCF entity determines the service range of the DN according to the DN information or the DN identifier and sends the service range to the AMF entity.
  • the AMF entity determines, according to the current location information of the terminal, whether the terminal is currently in the service range of the DN, and if yes, the AMF entity determines to send the DN information to the terminal. For example, the AMF sends a response message to the terminal, including the foregoing DN information, where the DN information includes the DN identifier and the DN type.
  • the AMF entity notifies the terminal of the service range of the DN, and the terminal determines whether the current service scope of the DN is currently.
  • the terminal receives the RAN device, such as the base station, the broadcast DN identifier and the DN type.
  • the RAN device such as the base station, the broadcast DN identifier and the DN type.
  • the terminal can obtain the DN identifier and the DN type from the network side
  • the DN identifier corresponding to the APP is determined according to the second correspondence, where the second correspondence is APP and The corresponding relationship of the DN identifier, for example, the second correspondence may be recorded in the foregoing Table 1.
  • the DN identifier corresponding to the APP may be obtained.
  • the DN identifier is the DN identifier that the terminal can obtain on the network side.
  • the terminal determines the DN type corresponding to the DN identifier, and the DN type is the DN type that the terminal obtains from the network side.
  • the terminal determines, according to the third correspondence, the session type of the PDU session corresponding to the DN type, where the third correspondence is the correspondence between the DN type and the session type of the PDU session.
  • the third correspondence may be pre-configured at the terminal.
  • the correspondence between the APP and the DN identifier pre-configured by the terminal and the correspondence between the DN type and the session type of the PDU session. Therefore, after the terminal obtains the DN identifier and the DN type from the network side, The DN identifier may be determined according to the APP to be initiated, the DN type is determined according to the DN identifier, and the session type of the PDU session is determined according to the DN type.
  • Step 202 The terminal sends a first message to the AMF entity, where the AMF entity receives the first message from the terminal.
  • the first message includes a session type of the PDU session, and the first message is used to request to establish a PDU session of the session type.
  • the terminal when the terminal sends a first message for requesting to establish a PDU session to the AMF entity, the terminal carries the session type of the PDU session in the first message, so that the network side can establish a corresponding session type according to the PDU session sent by the terminal.
  • a type of PDU session to establish the correct type of PDU session for the terminal, ensuring proper communication between the terminal and the network side.
  • Step 203 The terminal sends the first DN information to the AMF entity, and the AMF entity receives the first DN information from the terminal.
  • the first DN information includes a DN identifier, or the first DN information includes a DN identifier and a DN type (the specific form of the first DN information may be any one of the foregoing two implementation manners).
  • step 203 may also be performed before step 202, or step 202 and step 203 are combined into one step, that is, the terminal simultaneously sends the first message and the first DN information to the AMF entity, for example, through the NAS.
  • the message sends the first message and the first DN information.
  • Step 204 The AMF entity determines the SMF entity according to the first DN information.
  • the AMF entity When the first DN information includes the DN identifier, the AMF entity also needs to determine the DN type according to the DN identifier. Further, the AMF entity selects an SMF entity based on the DN identity and the DN type.
  • the AMF entity selects an SMF entity according to the DN identity and the DN type.
  • the AMF entity sends the DN identifier and the DN type to a Network Function Repository Function (NRF) entity, and the NRF entity selects an SMF entity according to the received DN identifier and DN type, and sends it to the AMF entity, thereby AMF.
  • the entity can determine which SMF entity to use.
  • Step 205 The AMF entity sends a second message to the SMF entity.
  • the second message is obtained according to the first message, that is, after receiving the first message, the AMF entity does not acquire the content in the first message, but generates a second message according to the first message, and sends the second message to the SMF entity. That is, the second message includes the first message.
  • the second message further includes second DN information, where the second DN information includes a DN identifier, or the second DN information includes a DN identifier and a DN type (the specific form of the second DN information may be the foregoing Either of the two implementations).
  • the SMF entity determines the DN type based on the DN identity. Further, the SMF entity may determine the type of the PDU session based on the DN type.
  • the SMF entity may determine the type of the PDU session according to the DN type.
  • the SMF entity compares the session type of the PDU session obtained from the second message with the session type of the PDU session determined by the SMF entity. If yes, step 206 is performed. If not, step 207 is performed.
  • Step 206 The SMF entity establishes a PDU session according to the second message.
  • the SMF entity establishes a PDU session according to the session type of the PDU session obtained from the second message. Specifically, the SMF entity acquires a session type of the PDU session carried by the first message in the second message.
  • the SMF entity can directly establish a PDU session according to the session type of the PDU session in the second message.
  • the terminal sends the first message to the AMF entity
  • the session type of the PDU session is carried, and then the AMF entity sends the session type of the PDU session as an SMF entity by using the second message. Therefore, the SMF entity establishes a PDU session according to the session type, and implements establishing a correct type of PDU session.
  • Step 207 The SMF entity sends a session reject message to the terminal by using the AMF entity.
  • the SMF entity sends a session reject message to the terminal, optionally, the session reject message includes The session type of the PDU session determined by the SMF entity according to the DN information.
  • the SMF entity considers that the session type of the PDU session carried by the terminal in the first message sent in the foregoing step 202 is incorrect, and further, other parameters related to the first message are also incorrect. Therefore, the SMF entity sends a session reject message to the terminal, where the session reject message carries the session type of the PDU session determined by the SMF entity, so that the terminal re-initiates the process of requesting to establish a PDU session, and carries the correct PDU session in the new request.
  • the session type, and other parameters that carry the correct one, wherein the session type of the correct PDU session is the session type that the SMF entity sends to the terminal through the session reject message.
  • Step 208 The terminal sends a third message to the AMF entity, and the AMF entity receives the third message from the terminal.
  • This step is similar to the foregoing step 202, but the third message in the step 208 carries the session type of the PDU session carried by the SMF entity through the session reject message, that is, the session type of the correct PDU session.
  • the third message is used to request to establish a PDU session.
  • Step 209 The AMF entity sends a fourth message to the SMF entity, and the SMF entity receives the fourth message from the AMF entity.
  • step 209 is generated according to the third message, and the AMF entity does not know the content in the third message and the fourth message.
  • the fourth message carries the type of session of the correct PDU session.
  • the fourth message is used to request to establish a PDU session.
  • Step 210 The SMF entity establishes a PDU session according to the fourth message.
  • the session type of the PDU session is carried, and then the AMF entity passes the second message to the PDU session.
  • the session type transmission is an SMF entity.
  • the SMF entity determines that the session type of the received PDU session is incorrect, the SMF entity notifies the terminal to re-initiate the third message, and the SMF entity receives the fourth message of the AMF entity, thereby receiving the correct message through the fourth message.
  • the session type and the establishment of a PDU session enable the establishment of the correct type of PDU session.
  • the SMF entity may directly establish a PDU session, that is, the SMF entity directly establishes a PDU session corresponding to the session type according to the session type of the PDU session in the second message. That is, the SMF entity does not determine whether the session type of the PDU session determined by the SMF entity is the same as the session type of the PDU session carried in the second message.
  • the SMF entity establishes a PDU session with the UPF entity when establishing the PDU session. Therefore, the SMF entity also needs to select a UPF entity.
  • the SMF entity determines the UPF entity according to the DN identity and the session type of the PDU session, where the DN identity may be sent by the AMF entity to the SMF entity.
  • the main difference between the embodiment and the first embodiment is that in the second embodiment, the terminal does not send the session type of the PDU session to the network side, but the SMF entity on the network side determines the session type of the PDU session and establishes a PDU session.
  • a flowchart of another session processing method provided by the present application includes:
  • Step 301 The terminal initiates an APP, and determines a DN identifier.
  • the terminal when the terminal initiates the APP, the session type of the PDU session cannot be obtained, but the DN identifier corresponding to the APP can be determined, that is, the terminal can determine the identifier of the data network that needs to be accessed.
  • the terminal may obtain the DN identifier corresponding to the APP according to Table 1 in Embodiment 1 above.
  • This step 301 can be implemented according to the prior art and will not be described again.
  • Step 302 The terminal sends the first message and the first DN information to the AMF entity.
  • the first DN information includes a DN identifier.
  • the first message is used to request to establish a PDU session, and the first DN information can be used by the AMF entity to determine the SMF entity.
  • the method further includes the following steps:
  • Step 303 The AMF entity determines the SMF entity according to the first DN information.
  • the step 303 is similar to the step 204 in the first embodiment, that is, the AMF entity first determines the DN type according to the DN identifier in the DN information, and then the AMF entity determines the SMF entity according to the DN type and the DN identifier, which may be parameterized in step 204. Description, no longer repeat them.
  • Step 304 The AMF entity sends a second message to the SMF entity.
  • the second message is generated according to the first message, where the second message is used to request to establish a PDU session, and the second message further includes second DN information, that is, the second message includes the first message and the second DN. information. And the AMF entity does not know the specific content of the first message.
  • the second DN information includes a DN identity, or the second DN information includes a DN identity and a DN type.
  • Step 305 The SMF entity determines, according to the second message, a session type of the PDU session.
  • the SMF entity After receiving the second DN information, if the second DN information includes the DN identifier, the SMF entity determines the DN type according to the DN identifier, and then determines the session type of the PDU session according to the DN type.
  • the SMF entity acquires the DN type from the second DN information, and then determines the session type of the PDU session according to the DN type.
  • step 305 there are two implementations, one is to directly establish a PDU session, that is, go to step 306, and the other is to notify the terminal to re-initiate the process of requesting to establish a PDU session, that is, go to step 307. The following are explained separately.
  • Step 306 The SMF entity establishes a PDU session.
  • the SMF entity Since the SMF entity has determined the session type of the PDU session in the above step 305, the PDU session of the session type can be directly established.
  • Step 307 The SMF entity sends a session reject message to the terminal by using the AMF entity.
  • the SMF entity may also send a session reject message to the terminal through the AMF entity, where the session type of the PDU session determined by the SMF entity is carried, so that the terminal re-initiates the session establishment process.
  • Step 308 The terminal sends a third message to the AMF entity, and the AMF entity receives the third message from the terminal.
  • Step 309 The AMF sends a fourth message to the SMF entity, and the SMF entity receives the fourth message from the AMF entity.
  • Step 310 The SMF entity establishes a PDU session according to the fourth message.
  • the terminal when the terminal sends the first message to the AMF entity, the DN identifier is carried, and then the AMF entity sends the DN identifier to the SMF entity through the second message.
  • the terminal After the SMF entity determines the session type of the PDU session, the terminal is notified to re-initiate the third message, and the SMF entity receives the fourth message of the AMF entity, thereby receiving the correct session type through the fourth message, and establishing a PDU session, thereby implementing Establish the correct type of PDU session.
  • the SMF entity establishes a PDU session with the UPF entity when establishing the PDU session. Therefore, the SMF entity also needs to select a UPF entity.
  • the SMF entity determines the UPF entity according to the DN identity and the session type of the PDU session, where the DN identity may be sent by the AMF entity to the SMF entity.
  • FIG. 4 it is a schematic diagram of a device provided by the present application.
  • the device may be a terminal, an AMF entity or an SMF entity in any of the foregoing embodiments, and the device may be a terminal in the system architecture shown in FIG. 1 or
  • the chip in the terminal may also be an AMF entity in the system architecture shown in FIG. 1 or a chip in the AMF entity, or may be an SMF entity or a chip in the SMF entity in the system architecture shown in FIG. 1.
  • the apparatus 200 can be used to indicate a method performed by a terminal, an AMF entity, or an SMF entity in any of the session processing methods described above.
  • the apparatus 200 includes at least one processing unit 21, a communication unit 22, and optionally a storage unit 23.
  • the processing unit 21, the communication unit 22, and the storage unit 23 are connected by a communication bus.
  • Processing unit 21 may be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus can include a path for communicating information between the above units.
  • the communication unit 22 may be a device having a transceiving function for communicating with other devices or a communication network, such as an Ethernet, a radio access network (RAN), a wireless local area network (WLAN), or the like.
  • a communication network such as an Ethernet, a radio access network (RAN), a wireless local area network (WLAN), or the like.
  • the storage unit 23 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other information that can store information and instructions.
  • Type of dynamic storage device also can be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the storage unit 23 may be independent and connected to the processing unit 21 via a communication bus.
  • the storage unit 23 can also be integrated with the processing unit.
  • the storage unit 23 is configured to store application code for executing the solution of the present invention, and is controlled by the processing unit 21 for execution.
  • the processing unit 21 is configured to execute an application code stored in the storage
  • processing unit 21 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 200 may include multiple processing units, such as processing unit 21 and processing unit 28 in FIG. Each of these processing units may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the processing unit 21 when the device is a terminal, an AMF entity or an SMF entity, the processing unit 21 may be, for example, a processor, and the communication unit 22 may be, for example, a transceiver, the transceiver including a radio frequency circuit, when the device
  • the storage unit 23 is further included, the storage unit 23 is configured to store a computer execution instruction, the processing unit 21 is connected to the storage unit 23, and the processing unit 21 executes a computer execution instruction stored by the storage unit 23 to cause the base station or terminal
  • the session processing method of any of the above embodiments is performed.
  • the processing unit 21 may be, for example, a processor, and the communication unit 22 may be, for example, an input/ Output interface, pin or circuit.
  • the processing unit 21 may execute computer execution instructions stored by the storage unit to cause the chip to execute the session processing method in the above embodiment.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the base station or terminal, such as a ROM or may be stored. Static information and instructions for other types of static storage devices, RAM, etc.
  • the chip execution session processing method can be understood as: the chip combines other components in the device to complete the session processing method.
  • the communication unit of the chip is connected to the transceiver of the terminal, and the processing unit of the chip initiates the application for the APP, determines the session type of the PDU session, generates a first message, and then passes through the communication unit of the chip. Sending the first message to the transceiver of the terminal, and the transceiver of the terminal sends the first message to the AMF entity.
  • the session processing method of the embodiment of the present invention is implemented by the chip of the terminal.
  • the communication unit of the chip is connected to the transceiver of the SMF entity, the transceiver of the SMF entity receives the second message from the AMF entity, and then sends the message to the communication unit of the chip, and then the chip
  • the processing unit establishes a PDU session according to the session type of the PDU session in the second message.
  • the session processing method of the embodiment of the present invention is implemented by a chip of the SMF entity.
  • the communication unit of the chip is connected to the transceiver of the SMF entity, the transceiver of the SMF entity receives the second message from the AMF entity, and then sends the message to the communication unit of the chip, and then the chip
  • the processing unit determines the session type of the PDU session according to the DN information in the second message.
  • the session processing method of the embodiment of the present invention is implemented by a chip of the SMF entity.
  • the communication unit of the chip is connected to the transceiver of the AMF entity, and the transceiver of the AMF entity receives the first message and DN information from the terminal, and then sends the message to the communication unit of the chip, and then The processing unit of the chip generates a second message according to the first message, and controls the communication unit of the chip to send the second message and the DN information to the transceiver of the AMF entity, and the second message and the DN information are sent by the transceiver of the AMF entity to the SMF entity.
  • the session processing method of the embodiment of the present invention is implemented by a chip of the AMF entity.
  • the device when the device is divided by the method shown in FIG. 4, the device can implement the session processing method in any of the above embodiments of the present application by the cooperation of the processing unit 21 and the communication unit 22.
  • the device shown in FIG. 4 is a chip of a terminal or a terminal, then:
  • the processing unit 21 is configured to initiate an application APP, and determine, according to the application APP, a session type of a packet data unit PDU session;
  • the communication unit 22 is configured to send a first message to the access and mobility management function AMF entity, where the first message includes the session type, and the first message is used to request to establish a PDU session of the session type. .
  • the processing unit 21 is specifically configured to:
  • the first correspondence is a correspondence between the APP and a session type of the PDU session.
  • the first correspondence is pre-configured at the terminal; or,
  • the first correspondence is obtained by the terminal from the AMF entity.
  • the processing unit 21 is specifically configured to:
  • the second correspondence is a correspondence between the APP and the DN identifier
  • the third correspondence is a correspondence between the DN type and the session type of the PDU session.
  • the communication unit 22 is further configured to:
  • the communication unit 22 is further configured to: send, to the AMF entity, first DN information, where the first DN information includes a DN identifier or includes a DN identifier and a DN type, where A DN information is used by the AMF entity to determine an SMF entity according to the DN identity, and the SMF entity is configured to establish a PDU session of the session type.
  • chip of the terminal or the terminal may be used to implement the steps performed by the terminal in the session processing method of the embodiment of the present invention.
  • reference may be made to the above, and details are not described herein again.
  • the device shown in FIG. 4 is a chip of an SMF entity or an SMF entity, then:
  • the communication unit 22 is configured to receive a second message from an access and mobility management function AMF entity, where the second message includes a session type of a packet data unit PDU session requested by the terminal, and the second message is used to request Establish a PDU session;
  • the processing unit 21 is configured to establish a PDU session according to the session type of the PDU session.
  • the communication unit 22 is further configured to receive a DN identifier from the AMF entity;
  • the processing unit 21 is further configured to determine a user plane function UPF entity according to the DN identifier and a session type of the PDU session, where the UPF entity is used to establish a PDU session of the session type.
  • chip of the SMF entity or the SMF entity may be used to implement the steps performed by the SMF entity in the session processing method of the embodiment of the present invention.
  • the chip of the SMF entity or the SMF entity may be used to implement the steps performed by the SMF entity in the session processing method of the embodiment of the present invention.
  • the device shown in FIG. 4 is a chip of an SMF entity or an SMF entity, then:
  • the communication unit 22 is configured to receive a second message from an access and mobility management function AMF entity, where the second message includes second data network DN information, and the second message is used to request to establish a PDU session;
  • the processing unit 21 is configured to determine a session type of the PDU session according to the second DN information.
  • the second DN information includes a DN identifier
  • the processing unit 21 is specifically configured to:
  • the second DN information includes a DN type
  • the processing unit 21 is configured to: determine, by the SMF entity, a session type of the PDU session according to the DN type.
  • the communication unit 22 is configured to send a session reject message to the terminal, where the session reject message includes a session type of the PDU session determined by the processing unit 21 according to the second DN information.
  • processing unit 21 is further configured to:
  • a PDU session is established according to the session type of the PDU session.
  • processing unit 21 is further configured to:
  • chip of the SMF entity or the SMF entity may be used to implement the steps performed by the SMF entity in the session processing method of the embodiment of the present invention.
  • the chip of the SMF entity or the SMF entity may be used to implement the steps performed by the SMF entity in the session processing method of the embodiment of the present invention.
  • the device shown in FIG. 4 is a chip of an AMF entity or an AMF entity, then:
  • the communication unit 22 is configured to receive a first message from the terminal and first data network DN information, where the first message is used to request to establish a PDU session.
  • the processing unit 21 is configured to determine, according to the first DN information, a session management function SMF entity; and, according to the first message, send a second message to the SMF entity, where the second message is used to request to establish a PDU session, wherein a session type of the PDU session corresponds to the first DN information.
  • the first message and the second message include a session type of a PDU session requested by the terminal;
  • the first DN information includes a DN identifier
  • the second message includes the DN identifier, where the DN identifier is used by the SMF entity to determine a session type of the PDU session according to the DN identifier.
  • the first DN information includes a DN identifier; the communication unit 22 is further configured to receive a data network DN identifier from the terminal;
  • the processing unit 21 is specifically configured to determine a DN type according to the DN identifier
  • the communication unit 22 is further configured to send the DN identifier and the DN type to an NRF entity; and receive the SMF entity from the NRF entity, where the SMF entity is used by the NRF entity according to the DN The identification and the DN type are determined.
  • the communication unit 22 is further configured to:
  • the DN information of the terminal subscription includes a DN identifier and a DN type;
  • the message requesting registration includes capability indication information of the terminal, and the capability indication information is used to indicate a data network supported by the terminal;
  • the DN information subscribed by the terminal corresponds to the data network supported by the terminal.
  • chip of the AMF entity or the AMF entity may be used to implement the steps performed by the AMF entity in the session processing method of the embodiment of the present invention.
  • the chip of the AMF entity or the AMF entity may be used to implement the steps performed by the AMF entity in the session processing method of the embodiment of the present invention.
  • the present application also provides a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform operations performed by the terminal in the session processing method described above.
  • the computer can be a terminal.
  • the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform operations performed by the SMF entity in the session processing method described above.
  • the computer can be an SMF entity.
  • the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform operations performed by the AMF entity in the session processing method described above.
  • the computer can be an AMF entity.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in the session processing method performed by the terminal in any of the above embodiments.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in a session processing method performed by an SMF entity in any of the embodiments described above.
  • the application provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the flow in a session processing method performed by an AMF entity in any of the embodiments described above.

Landscapes

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

Abstract

本申请提供一种会话处理方法及装置。该方法包括：终端发起应用APP，根据APP确定分组数据单元PDU会话的会话类型；终端向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。该方法中，终端在向AMF实体发起用于请求建立PDU会话的第一消息时，在第一消息中携带PDU会话的会话类型，使得网络侧可以根据终端发送的PDU会话的会话类型建立相应类型的PDU会话，从而为终端建立正确类型的PDU会话，提高了终端与网络侧之间通信的正确性。

Description

一种会话处理方法及装置
本申请要求在2017年8月15日提交中华人民共和国知识产权局、申请号为201710698731.1、发明名称为“一种会话处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种会话处理方法及装置。
背景技术
在第五代(the 5th generation，5G)移动通信中，定义了多种类型的分组数据单元(packet data unit，PDU)会话，例如包括因特网(Internet)类型会话、以太网(Ethernet)类型会话、非结构(unstructured)类型会话等等。
在有多种类型的PDU会话的情形下，如何为终端建立正确类型的PDU会话，则是一个有待解决的问题。
发明内容
本申请提供一种会话处理方法及装置，用以为终端建立正确类型的PDU会话。
为达到上述目的，本申请提供如下技术方案：
第一方面，本申请提供一种会话处理方法，包括：终端发起应用APP，根据应用APP确定分组数据单元PDU会话的会话类型；终端向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。该方法中，终端在向AMF实体发起用于请求建立PDU会话的第一消息时，在第一消息中携带PDU会话的会话类型，使得网络侧可以根据终端发送的PDU会话的会话类型建立相应类型的PDU会话，从而为终端建立正确类型的PDU会话，提高了终端与网络侧之间通信的正确性。
在一种可能的设计中，所述终端确定PDU会话的会话类型，包括：所述终端根据第一对应关系，确定所述APP对应的所述会话类型；其中，所述第一对应关系为APP与PDU会话的会话类型的对应关系。该方法中，终端根据APP与PDU会话的会话类型的对应关系，确定PDU会话的会话类型，简单易实施。
在一种可能的设计中，所述第一对应关系为预先配置在所述终端；或者，所述第一对应关系由所述终端从所述AMF实体获得。
在一种可能的设计中，所述终端确定PDU会话的会话类型，包括：所述终端根据第二对应关系，确定所述APP对应的DN标识；所述终端确定所述DN标识对应的DN类型；所述终端根据第三对应关系，确定所述DN类型对应的所述会话类型；其中，所述第二对应关系为APP与DN标识的对应关系，所述第三对应关系为DN类型与PDU会话的会话类型的对应关系。
在一种可能的设计中，所述终端向所述AMF实体发送请求消息，并，接收所述AMF实体根据所述请求消息发送的所述DN标识和所述DN类型；或者，所述终端接 收无线接入网络RAN设备广播的所述DN标识和所述DN类型。
在一种可能的设计中，所述终端向所述AMF实体发送第一DN信息，所述第一DN信息包括DN标识或者，包括DN标识和DN类型，所述第一DN信息用于所述AMF实体根据所述DN标识确定SMF实体，所述SMF实体用于建立所述会话类型的PDU会话。
第二方面，本申请提供一种会话处理方法，包括：会话管理功能SMF实体接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括终端请求的分组数据单元PDU会话的会话类型，所述第二消息用于请求建立PDU会话；所述SMF实体根据所述PDU会话的会话类型，建立PDU会话。
在一种可能的设计中，所述SMF实体接收来自所述AMF实体的DN标识；
所述SMF实体根据所述DN标识和所述PDU会话的会话类型，确定用户面功能UPF实体，所述UPF实体用于建立所述会话类型的PDU会话。
第三方面，本申请提供一种会话处理方法，包括：会话管理功能SMF实体接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括第二数据网络DN信息，所述第二消息用于请求建立PDU会话；所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型。
在一种可能的设计中，当所述第二DN信息包括DN标识时，则所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型包括：所述SMF实体根据所述DN标识，确定DN类型，以及根据所述DN类型，确定所述PDU会话的会话类型；或者，
当所述第二DN信息包括DN类型时，则所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型，包括：所述SMF实体根据所述DN类型，确定所述PDU会话的会话类型。
在一种可能的设计中，如果所述第二消息中携带终端请求的PDU会话的会话类型，当所述SMF实体根据所述第二DN信息确定的PDU会话的会话类型与终端请求的PDU会话的会话类型不一致时，所述方法还包括：
所述SMF实体向终端发送会话拒绝消息，所述会话拒绝消息包括所述SMF实体根据所述第二DN信息确定的PDU会话的会话类型。
在一种可能的设计中，所述SMF实体根据所述PDU会话的会话类型，建立PDU会话。
在一种可能的设计中，所述SMF实体根据所述第二DN信息，确定用户面功能UPF实体，以及，与所述UPF实体建立所述会话类型的PDU会话。
第四方面，本申请提供一种会话处理方法，包括：接入与移动性管理功能AMF实体接收来自终端的第一消息和第一数据网络DN信息，所述第一消息用于请求建立PDU会话，所述AMF实体根据所述第一DN信息确定会话管理功能SMF实体；所述AMF实体根据所述第一消息，向所述SMF实体发送第二消息，所述第二消息用于请求建立PDU会话，其中，所述PDU会话的会话类型与所述第一DN信息对应。
在一种可能的设计中，所述第一消息和所述第二消息包括终端请求的PDU会话的会话类型；或者，所述第一DN信息包括DN标识，所述第二消息包含所述DN标识，所述DN标识用于所述SMF实体根据所述DN标识确定所述PDU会话的会话类型。
在一种可能的设计中，所述第一DN信息包括DN标识；
所述AMF实体根据所述第一DN信息确定会话管理功能SMF实体，包括：
所述AMF实体根据所述DN标识，确定DN类型；
所述AMF实体向NRF实体发送所述DN标识和所述DN类型；
所述AMF实体接收来自所述NRF实体的所述SMF实体，所述SMF实体由所述NRF实体根据所述DN标识和所述DN类型确定。
在一种可能的设计中，所述AMF实体接收来自终端的请求注册的消息；
所述AMF实体根据所述请求注册的消息，向数据库获取所述终端签约的DN信息，所述签约的DN信息包括DN标识和DN类型；
所述AMF实体向所述终端发送所述终端签约的DN信息。
在一种可能的设计中，所述请求注册的消息包括所述终端的能力指示信息，所述能力指示信息用于指示所述终端支持的数据网络；
所述终端签约的DN信息与所述终端支持的数据网络对应。
第五方面，本申请提供一种装置，该装置可以是终端，也可以是终端内的芯片。该装置具有实现上述第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为终端时，终端包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述终端还包括存储单元，该存储单元例如可以是存储器。当终端包括存储单元时，该存储单元用于存储计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该终端执行上述第一方面任意一项的会话处理方法。
在另一种可能的设计中，当该装置为终端内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第一方面任意一项的会话处理方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述终端内的位于所述芯片外部的存储单元，如只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(central rocessing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制上述第一方面会话处理方法的程序执行的集成电路。
第六方面，本申请提供一种装置，该装置可以是SMF实体，也可以是SMF实体内的芯片。该装置具有实现上述第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为SMF实体时，SMF实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述SMF实体还包括存储单元，该存储单元例如可以是存储器。当SMF实体包括存储单元时，该存储单元用于存储计算机执行指令，该处理 单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该SMF实体执行上述第二方面任意一项的会话处理方法。
在另一种可能的设计中，当该装置为SMF实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第二方面任意一项的会话处理方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述SMF实体内的位于所述芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制上述第一方面会话处理方法的程序执行的集成电路。
第七方面，本申请提供一种装置，该装置可以是SMF实体，也可以是SMF实体内的芯片。该装置具有实现上述第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为SMF实体时，SMF实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述SMF实体还包括存储单元，该存储单元例如可以是存储器。当SMF实体包括存储单元时，该存储单元用于存储计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该SMF实体执行上述第三方面任意一项的会话处理方法。
在另一种可能的设计中，当该装置为SMF实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第三方面任意一项的会话处理方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述SMF实体内的位于所述芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制上述第一方面会话处理方法的程序执行的集成电路。
第八方面，本申请提供一种装置，该装置可以是AMF实体，也可以是AMF实体内的芯片。该装置具有实现上述第四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为AMF实体时，AMF实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述AMF实体还包括存储单元，该存储单元例如可以是存储器。当AMF实体包括存储单元时，该存储单元用于存储计算机执行指令，该 处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该AMF实体执行上述第四方面任意一项的会话处理方法。
在另一种可能的设计中，当该装置为AMF实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第四方面任意一项的会话处理方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述AMF实体内的位于所述芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制上述第四方面会话处理方法的程序执行的集成电路。
第九方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。所述计算机例如可以是终端。
第十方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。所述计算机例如可以是SMF实体。
第十一方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第三方面所述的方法。所述计算机例如可以是SMF实体。
第十二方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第四方面所述的方法。所述计算机例如可以是AMF实体。
第十三方面，本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第一方面中任意一项的会话处理方法中的流程。
第十四方面，本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第二方面中任意一项的会话处理方法中的流程。
第十五方面，本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第三方面中任意一项的会话处理方法中的流程。
第十六方面，本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述第四方面中任意一项的会话处理方法中的流程。
另外，第二方面至第十六方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请适用的可能的网络架构示意图；
图2为本申请提供的一种会话处理方法流程图；
图3为本申请提供的另一种会话处理方法流程图；
图4为本申请提供的一种装置结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
需要说明的的是，本申请的会话处理方法可由装置执行。在网络侧，该装置可以是会话管理功能(Session Management Function，SMF)实体或SMF实体内的芯片，该装置还可以是接入与移动性管理功能(Access and Mobility Management Function，AMF)实体或AMF实体内的芯片；在终端侧，该装置可以是终端或终端内的芯片。
为方便说明，本申请，以装置为AMF实体、SMF实体及终端为例，对会话处理方法进行说明，对于装置为AMF实体内的芯片、或为SMF实体内的芯片、或为终端内的芯片的实现方法，可参考装置分别为AMF实体、SMF实体、或终端的会话处理方法的具体说明，不再重复介绍。
如图1所示，为本申请适用的可能的网络架构示意图，该网络框架示意图包括终端、第三代合作伙伴计划(3rd Generation Partnership Project,3GPP)接入网络实体、非3GPP接入网络(Non-3GPP)、N3IWF、AMF实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体和数据网络(data Network，DN)等。
其中，终端是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
3GPP接入网实体也称无线接入网(radio access network，RAN)实体，例如可以是5G中的基站。Non-3GPP接入网络是指3GPP以外的接入网络，如无线局域网(wireless local area networks，WLAN)接入网络。N3IWF类似于长期演进(long term evolution，LTE)中的演进的分组数据网关(evolved packet data gateway，ePDG)，在5G中用于UE通过非3GPP技术网络接入时，和UE建立互联网协议安全性(internet protocol security，IPsec)隧道。在未来5G定义中，N3IWF的名字可能会更改。
AMF实体负责终端的接入管理和移动性管理，在实际应用中，其包括了长期演进(long term evolutio，LTE)中网络框架中移动管理实体(mobility management entity，MME)里的移动性管理功能，并加入了接入管理功能。
SMF实体负责会话管理，如用户的会话建立等，也即MME实体里的会话管理功 能。UPF实体是终端用户面的功能实体，主要负责连接外部网络，其包括了LTE的服务网关(serving gateway，SGW)和公用数据网(public data network，PDN)网关(gateway)的相关功能。DN负责为终端提供数据服务，如为终端提供上网功能、短信功能等等。
在本申请中，DN标识，用于标识一个数据网络。新增一个属性为DN类型，DN类型(Type)用于指示数据网络的类型，例如DN类型包括因特网(internet)、以太网(Ethernet)、非结构(unstructured)网络等。
本申请，还可以将DN标识和/或DN类型统称为DN信息，即，DN信息包括DN标识，或者，DN信息包括DN类型，或者DN信息包括DN标识和DN类型。
在一种实现方式中，3GPP标准中，当前定义数据网络名称(data network name，DNN)用于标识一个数据网络，根据目前的DNN定义，DNN仅作为数据网络的标识，即DN标识。本申请中，在新增DN类型之后，有以下两种表示DN类型的实现方式。
第一种实现方式为，可将DN标识和DN类型各自采用单独信元来表示，即DN标识仍然沿用当前3GPP标准中定义的DNN来标识，而单独定义一个新的信元DN Type来标识DN类型。
第二种实现方式为，可将DN标识和DN类型由同一个信元来表示。例如，扩展当前DNN的定义，DNN可以同时表示DN标识和DN类型。即，在当前DNN中增加一个字段，为DN类型，即扩展后的DNN中包括DN标识和DN类型。作为一个实例，可以是将DNN的字段定义为分为两部分，前一部分字段的取值用于标识DN标识，例如0001标识某个企业内网，后一部分字段的取值用于标识该DN的类型，例如0002标识该企业内网为Ethernet类型。则全字段00010002为该DNN的具体取值。在该实现方式中，DNN这一个信元中包括了DN标识和DN类型两个信息。
根据上面的两种实现方式，可以理解，后续实施例中提到DN标识，指的是DNN(第一种实现方式)，或者是DNN中用于标识数据网络的字段(第二种实现方式)。
基于图1所示的系统架构，本申请提供一种会话处理方法，包括：终端发起应用APP，根据应用APP确定分组数据单元PDU会话的会话类型；终端向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。该方法中，终端在向AMF实体发起用于请求建立PDU会话的第一消息时，在第一消息中携带PDU会话的会话类型，使得网络侧可以根据终端发送的PDU会话的会话类型建立相应类型的PDU会话，从而为终端建立正确类型的PDU会话，提高了终端与网络侧之间通信的正确性。
下面结合附图，对本申请提供的会话处理方法进行具体说明。
实施例一
该实施例一中：终端可确定PDU会话的会话类型，并发送至网络侧，建立PDU会话。
如图2所示，为本申请提供的一种会话处理方法流程图，包括：
步骤201、终端发起APP，根据应用APP确定PDU会话的会话类型。
其中，应用(APP)可以是某个具体的应用，如“优酷”、“百度”等，也可以是某类应用，如视频类应用、文字类应用、图片类应用等。
当终端确定要发起某个应用(APP)时，可根据该APP，确定PDU会话的会话类型。下面给出两种实现方式，作为示例性地说明。
实现方式一、终端根据第一对应关系，确定APP对应的PDU会话的会话类型。
其中，该第一对应关系记录了该APP与该APP对应的PDU会话的会话类型之间的对应关系。
该第一对应关系可以是以表格的形式记录，也可以是以数组的形式记录，还可以是以函数的形式记录，本申请不做限定。
例如，作为一种具体的实现方式，可以结合现有技术中的终端路由选择策略(UE Route Selection Policies，URSP)表来实现。如表1所示，为现有技术中的URSP表。
表1
Figure PCTCN2018100641-appb-000001
其中，Traffic filter指的是数据匹配规则，该参数用于根据终端发起的APP判断其他以下策略是否能够适用，例如，上表1中，当终端发起优酷APP时，由于优酷是视频类的APP，则该策略确定表中其他的策略适用于优酷APP。如果当终端发起微信APP时，表中其他策略则不适用。。
Direct offload指的是数据分流策略，该参数用于确定该APP或某一类型的APP能够使用数据分流，例如，上表1中，Prohibited意味着视频类应用不能使用数据分流。
Slice Info指的是切片信息，该参数用于确定发起该APP所需要使用的切片信息，以便UE在发起PDU会话时携带，例如，上表1中，UE在发起该APP时确定需要使用切片信息S-NSSAI-a。
Continuity Types指的是会话连续性的类型，该参数用于确定APP所需会话连续性的类型，例如，上表1中，UE在发起该APP时确定所需的会话连续性的类型为SSC mode3。
DN标识指的是数据网络的标识，该参数用于指示数据网络的名称，例如，上表1中DN标识指示的数据网络是internet。
Access Type指的是接入类型，该参数用于确定APP所需的接入类型，例如，上表1中，UE在发起该APP时确定所需的接入类型为3GPP接入类型。
基于表1，如果需要记录DummyApp与该APP对应的PDU会话的会话类型之间的的对应关系，则可以在上述表1中增加“PDU Type”属性，“PDU Type”指的是PDU会话的会话类型，从而建立了第一对应关系。如表2所示，为增加“PDU Type”属性的URSP表。
表2
Figure PCTCN2018100641-appb-000002
因而，当终端发起应用DummyApp时，可根据上述表2中的第一对应关系，即DummyApp与PDU Type之间的对应关系，确定DummyApp对应的PDU Type为Ethernet。
其中，上述第一对应关系可以是预先配置在终端，也可以是由终端从网络侧，如AMF实体获得。
以上述表2的实现方式为例，一方面，可以是在终端内预先配置上述URSP表；另一方面，当终端移动至某个数据网络的覆盖范围时，可接收到该数据网络广播的URSP表，终端可将接收到的URSP表存储在本地，或根据接收到的URSP表更新本地已经存储的URSP表。
实现方式二、终端根据APP、DN标识、DN类型，确定PDU会话的会话类型。
该方式中，终端首先可从网络侧，如AMF实体获取到DN信息，其中包括DN标识和DN类型。获取方法包括但不限于：
获取方法一、终端向AMF实体发送请求消息，用于请求获取DN标识和DN类型。
例如，终端在移动至某个数据网络时，可发送请求注册的消息至AMF实体，AMF实体接收到请求注册的消息后，向数据库获取该终端签约的DN信息，该DN信息中包括DN标识和DN类型，然后，AMF实体向终端发送DN标识和DN类型，从而，终端获取到DN标识和DN类型。
可选地，请求注册的消息包括终端的能力指示信息，能力指示信息用于指示终端支持的数据网络，则AMF实体向终端发送的签约的DN信息是与终端支持的数据网络对应的DN信息。例如，能力指示信息指示终端支持的数据网络是internet，则AMF实体向终端发送的DN签约的DN信息则包括关于internet的DN标识和DN类型，而不包括其它数据网络的DN标识和DN类型。
可选地，AMF实体向PCF实体发送DN信息或DN标识，可选的，PCF实体根据DN信息或DN标识确定该DN的服务范围并发送给AMF实体。
可选的，AMF实体根据终端的当前位置信息，确定终端当前是否处于该DN的服务范围，如果是，则AMF实体确定将DN信息发送给终端。例如，AMF向终端发送响应消息，包含上述DN信息，DN信息中包含DN标识和DN类型。
可选的，AMF实体通知终端该DN的服务范围，由终端进行判断当前是否处于该DN的服务范围。
获取方法二、终端接收RAN设备，如基站，广播的DN标识和DN类型。
基于终端可从网络侧获取到DN标识和DN类型的前提下，当终端发起应用APP时，先根据第二对应关系，确定该APP对应的DN标识，其中，所述第二对应关系为APP与DN标识的对应关系，例如，该第二对应关系可记录在上述表1中，根据APP，即可获取该APP对应的DN标识。并且，该DN标识即为终端可网络侧获取到的DN标识。
接着，终端确定DN标识对应的DN类型，该DN类型即为终端从网络侧获取到的DN类型。
然后，终端根据第三对应关系，确定DN类型对应的PDU会话的会话类型，该第三对应关系为DN类型与PDU会话的会话类型的对应关系。该第三对应关系可以是预配置在终端。
在该实现方式二中，终端预配置的APP与DN标识的对应关系、DN类型与PDU会话的会话类型之间的对应关系，因此，当终端从网络侧获取到DN标识和DN类型之后，即可根据要发起的APP，确定DN标识，根据DN标识确定DN类型，根据DN类型确定PDU会话的的会话类型。
步骤202、终端向AMF实体发送第一消息，AMF实体接收来自终端的第一消息。
其中，所述第一消息包括PDU会话的会话类型，该第一消息用于请求建立该会话类型的PDU会话。
该实施例中，终端在向AMF实体发送用于请求建立PDU会话的第一消息时，在第一消息中携带PDU会话的会话类型，使得网络侧可以根据终端发送的PDU会话的会话类型建立相应类型的PDU会话，从而为终端建立正确类型的PDU会话，保证了终端与网络侧之间的正确通信。
可选地，在上述步骤202之后，还包括以下步骤：
步骤203、终端向AMF实体发送第一DN信息，AMF实体接收来自终端的第一DN信息。该第一DN信息包括DN标识，或者该第一DN信息包括DN标识和DN类型(第一DN信息具体形式可以是上述两种实现方式的任意一种)。
需要说明的是，该步骤203也可以是在步骤202之前执行，或者，步骤202和步骤203合并为一个步骤，即终端将第一消息和第一DN信息同时发送至AMF实体，例如，通过NAS消息发送第一消息和第一DN信息。
步骤204、AMF实体根据第一DN信息，确定SMF实体。
当该第一DN信息包括DN标识时，AMF实体还需要根据DN标识，确定DN类型。进而，AMF实体根据DN标识和DN类型，选择一个SMF实体。
当该第一DN信息包括DN标识和DN类型时，AMF实体根据DN标识和DN类型，选择一个SMF实体。
例如，AMF实体将DN标识和DN类型发送至网络功能库(Network Function Repository Function，NRF)实体，NRF实体根据接收到的DN标识和DN类型，选择一个SMF实体，并发送至AMF实体，从而AMF实体可确定使用的SMF实体。
步骤205、AMF实体向SMF实体发送第二消息。
该第二消息是根据第一消息得到的，即AMF实体接收到第一消息后，并不获取第一消息中的内容，而是根据第一消息，生成第二消息，并发送至SMF实体，即，第 二消息包括第一消息。
可选地，步骤205中，第二消息中还包括第二DN信息，该第二DN信息包括DN标识，或，第二DN信息包括DN标识和DN类型(第二DN信息具体形式可以是上述两种实现方式的任意一种)。
若AMF实体向SMF实体发送的第二DN信息包括DN标识，则SMF实体还根据DN标识确定DN类型。进一步地，SMF实体可根据DN类型，确定PDU会话的类型。
若AMF实体向SMF实体发送的第二DN信息包括DN标识和DN类型，则SMF实体可根据DN类型，确定PDU会话的类型。
可选地，SMF实体将从第二消息中获取的PDU会话的会话类型，与SMF实体自己确定的PDU会话的会话类型进行比较，若相同，则执行步骤206，若不同，则执行步骤207。
步骤206、SMF实体根据第二消息，建立PDU会话。
具体的，SMF实体根据从第二消息中获取的PDU会话的会话类型，建立PDU会话。具体的，SMF实体获取第二消息中的第一消息携带的PDU会话的会话类型。
由于SMF实体从第二消息中获取的PDU会话的会话类型，与SMF实体自己确定的PDU会话的会话类型相同，则SMF实体可以直接根据第二消息中的PDU会话的会话类型，建立PDU会话。
流程结束。
通过上述步骤201～步骤206，即可实现，由终端向AMF实体发送第一消息时，携带PDU会话的会话类型，然后由AMF实体通过第二消息，将PDU会话的会话类型发送是SMF实体，从而由SMF实体根据会话类型建立PDU会话，实现了建立正确类型的PDU会话。
步骤207、SMF实体通过AMF实体，向终端发送会话拒绝消息。
若SMF实体从第二消息中获取的PDU会话的会话类型，与SMF实体自己确定的PDU会话的会话类型不同，则SMF实体向终端发送会话拒绝消息，可选地，所述会话拒绝消息包括所述SMF实体根据所述DN信息确定的PDU会话的会话类型。
即，SMF实体认为终端在上述步骤202中发送的第一消息中携带的PDU会话的会话类型不正确，进而，与该第一消息有关的其它参数也不正确。因此，SMF实体向终端发送会话拒绝消息，该会话拒绝消息中携带SMF实体确定的PDU会话的会话类型，使得终端重新发起请求建立PDU会话的过程，并在新的请求中携带正确的PDU会话的会话类型，以及携带正确的其它参数，其中，该正确的PDU会话的会话类型即为SMF实体通过会话拒绝消息发送至终端的会话类型。
步骤208、终端向AMF实体发送第三消息，AMF实体接收来自终端的第三消息。
该步骤与上述步骤202类似，但该步骤208中的第三消息携带的是SMF实体通过会话拒绝消息中携带的PDU会话的会话类型，即正确的PDU会话的会话类型。第三消息用于请求建立PDU会话。
步骤209、AMF实体向SMF实体发送第四消息，SMF实体接收来自AMF实体的第四消息。
该步骤与上述步骤205类似，但该步骤209中的第四消息是根据第三消息生成的，并且，AMF实体也并不获知第三消息和第四消息中的内容。第四消息中携带正确的 PDU会话的会话类型。第四消息用于请求建立PDU会话。
步骤210、SMF实体根据第四消息，建立PDU会话。
流程结束。
通过上述步骤201～步骤205，以及步骤207～步骤210，即可实现，由终端向AMF实体发送第一消息时，携带PDU会话的会话类型，然后由AMF实体通过第二消息，将PDU会话的会话类型发送是SMF实体，SMF实体确定接收到的PDU会话的会话类型不正确时，通知终端重新发起第三消息，以及SMF实体接收AMF实体的第四消息，从而通过第四消息，接收正确的会话类型，并建立PDU会话，实现了建立正确类型的PDU会话。
可选地，上述步骤205之后，还可以是SMF实体直接建立PDU会话，即SMF实体根据第二消息中的PDU会话的会话类型，直接建立与该会话类型对应的PDU会话。即SMF实体不判断SMF实体确定的PDU会话的会话类型与第二消息中携带的PDU会话的会话类型是否相同。
可选地，上述步骤206或步骤210中，SMF实体在建立PDU会话时，是与UPF实体一起建立PDU会话的，因此，SMF实体还需要选择一个UPF实体。可选地，SMF实体根据DN标识和PDU会话的会话类型，确定UPF实体，其中，该DN标识可以是由AMF实体发送至SMF实体的。
实施例二
该实施例与上述实施例一的主要区别在于：实施例二中，终端不向网络侧发送PDU会话的会话类型，而是由网络侧的SMF实体确定PDU会话的会话类型，并建立PDU会话。
如图3所示，为本申请提供的另一种会话处理方法流程图，包括：
步骤301、终端发起APP，确定DN标识。
该步骤，终端发起APP时，并不能获取到PDU会话的会话类型，但是可以确定APP对应的DN标识，即终端可以确定需要接入的数据网络的标识。
例如，在一种实现方式中，终端可根据上述实施例1中的表1，来获取APP对应的DN标识。
该步骤301，可根据现有技术实现，不再赘述。
步骤302、终端向AMF实体发送第一消息和第一DN信息。
其中，第一DN信息中包括DN标识。第一消息用于请求建立PDU会话，第一DN信息可由由AMF实体用于确定SMF实体。
可选地，还包括以下步骤：
步骤303、AMF实体根据第一DN信息，确定SMF实体。
该步骤303与实施例一中的步骤204类似，即AMF实体先根据DN信息中的DN标识，确定DN类型，然后，AMF实体根据DN类型和DN标识，确定SMF实体，具体可参数步骤204的描述，不再赘述。
步骤304、AMF实体向SMF实体发送第二消息。
其中，第二消息中是根据第一消息生成的，第二消息用于请求建立PDU会话，该第二消息还包括第二DN信息，也即，第二消息中包括第一消息和第二DN信息。且 AMF实体并不获知第一消息的具体内容。
第二DN信息包括DN标识，或者第二DN信息包括DN标识和DN类型。
步骤305、SMF实体根据第二消息，确定PDU会话的会话类型。
SMF实体接收到第二DN信息后，若第二DN信息中包括DN标识，则SMF实体根据DN标识确定DN类型，然后根据DN类型确定PDU会话的会话类型。
若第二DN信息中包括DN标识和DN类型，则SMF实体从第二DN信息获取DN类型，然后根据DN类型确定PDU会话的会话类型。
在步骤305之后，有两种实现方式，一种是直接建立PDU会话，即转到步骤306，另一种是通知终端重新发起请求建立PDU会话的过程，即转到步骤307。下面分别说明。
步骤306、SMF实体建立PDU会话。
由于上述步骤305中，SMF实体已经确定PDU会话的会话类型，因此可直接建立该会话类型的PDU会话。
流程结束。
步骤307、SMF实体通过AMF实体向终端发送会话拒绝消息。
为提高建立PDU会话的准确性，SMF实体还可以通过AMF实体向终端发送会话拒绝消息，其中携带SMF实体确定的PDU会话的会话类型，使得终端重新发起会话建立流程。
步骤308、终端向AMF实体发送第三消息，AMF实体接收来自终端的第三消息。
步骤309、AMF是向SMF实体发送第四消息，SMF实体接收来自AMF实体的第四消息。
步骤310、SMF实体根据第四消息，建立PDU会话。
上述步骤308～步骤310，与实施例一中的步骤208～步骤210类似，具体可参考前述描述，不再赘述。
流程结束。
通过上述步骤301～步骤305，以及步骤307～步骤310，即可实现，由终端向AMF实体发送第一消息时，携带DN标识，然后由AMF实体通过第二消息，将DN标识发送是SMF实体，SMF实体确定出PDU会话的会话类型后，通知终端重新发起第三消息，以及SMF实体接收AMF实体的第四消息，从而通过第四消息，接收正确的会话类型，并建立PDU会话，实现了建立正确类型的PDU会话。
可选地，上述步骤306或步骤310中，SMF实体在建立PDU会话时，是与UPF实体一起建立PDU会话的，因此，SMF实体还需要选择一个UPF实体。可选地，SMF实体根据DN标识和PDU会话的会话类型，确定UPF实体，其中，该DN标识可以是由AMF实体发送至SMF实体的。
如图4所示，为本申请提供的一种装置示意图，该装置可以是上述任一实施例中的终端、AMF实体或SMF实体，该装置可以是图1所示的系统架构中的终端或终端内的芯片，还可以是图1所示的系统架构中的AMF实体或AMF实体内的芯片，还可以是图1所示的系统架构中的SMF实体或SMF实体内的芯片。
该装置200可用于指示上述任一会话处理方法中由终端、AMF实体或SMF实体执行的方法。
该装置200包括至少一个处理单元21，通信单元22，可选地，还包括存储单元23。所述处理单元21、通信单元22、存储单元23通过通信总线连接。
处理单元21可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
所述通信单元22，可以是具有收发功能的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(wireless local area networks，WLAN)等。
存储单元23可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically erasable programmabler-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储单元23可以是独立存在，通过通信总线与处理单元21相连接。存储单元23也可以和处理单元集成在一起。其中，所述存储单元23用于存储执行本发明方案的应用程序代码，并由处理单元21来控制执行。所述处理单元21用于执行所述存储单元23中存储的应用程序代码。
在具体实现中，作为一种实施例，处理单元21可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置200可以包括多个处理单元，例如图4中的处理单元21和处理单元28。这些处理单元中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在一种可能的设计中，当该装置为终端、AMF实体或SMF实体时，处理单元21例如可以是处理器，通信单元22例如可以是收发器，所述收发器包括射频电路，当该装置还包括存储单元23时，该存储单元23用于存储计算机执行指令，该处理单元21与该存储单元23连接，该处理单元21执行该存储单元23存储的计算机执行指令，以使该基站或终端执行上述任一实施例的会话处理方法。
在另一种可能的设计中，当该装置为终端内的芯片、或AMF实体内的芯片、或SMF实体内的芯片时，处理单元21例如可以是处理器，通信单元22例如可以是输入/输出接口、管脚或电路等。该处理单元21可执行存储单元存储的计算机执行指令，以使该芯片执行上述实施例中的会话处理方法。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述基站或终端内位于所述芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
其中，芯片执行会话处理方法，可以理解为：芯片结合装置内的其它部件，来完成会话处理方法。
比如，当芯片为终端内的芯片时，芯片的通信单元与终端的收发器连接，芯片的 处理单元发起用于APP，确定PDU会话的会话类型，并生成第一消息，然后通过芯片的通信单元，将第一消息发送至终端的收发器，由终端的收发器将第一消息发送至AMF实体。从而，由终端的芯片实现本发明实施例的会话处理方法。
再比如，当芯片为SMF实体内的芯片时，芯片的通信单元与SMF实体的收发器连接，SMF实体的收发器接收来自AMF实体的第二消息，然后发送至芯片的通信单元，然后芯片的处理单元根据第二消息中的PDU会话的会话类型，建立PDU会话。从而，由SMF实体的芯片实现本发明实施例的会话处理方法。
再比如，当芯片为SMF实体内的芯片时，芯片的通信单元与SMF实体的收发器连接，SMF实体的收发器接收来自AMF实体的第二消息，然后发送至芯片的通信单元，然后芯片的处理单元根据第二消息中的DN信息，确定PDU会话的会话类型。从而，由SMF实体的芯片实现本发明实施例的会话处理方法。
再比如，当芯片为AMF实体内的芯片时，芯片的通信单元与AMF实体的收发器连接，AMF实体的收发器接收来自终端的第一消息和DN信息，然后发送至芯片的通信单元，然后芯片的处理单元根据第一消息生成第二消息，并控制芯片的通信单元，向AMF实体的收发器发送第二消息和DN信息，由AMF实体的收发器向SMF实体发送第二消息和DN信息。从而，由AMF实体的芯片实现本发明实施例的会话处理方法。
例如在采用图4所示的方法对装置进行划分时，通过处理单元21和通信单元22的协作，可使该装置实现本申请上述任一实施例中的会话处理方法。
例如，当图4所示的装置为终端或终端的芯片时，则：
所述处理单元21，用于发起应用APP，根据应用APP确定分组数据单元PDU会话的会话类型；
所述通信单元22，用于向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。
在一种可能的设计中，所述处理单元21，具体用于：
根据第一对应关系，确定所述APP对应的所述会话类型；
其中，所述第一对应关系为APP与PDU会话的会话类型的对应关系。
在一种可能的设计中，所述第一对应关系为预先配置在所述终端；或者，
所述第一对应关系由所述终端从所述AMF实体获得。
在一种可能的设计中，所述处理单元21，具体用于：
根据第二对应关系，确定所述APP对应的DN标识；
确定所述DN标识对应的DN类型；
根据第三对应关系，确定所述DN类型对应的所述会话类型；
其中，所述第二对应关系为APP与DN标识的对应关系，所述第三对应关系为DN类型与PDU会话的会话类型的对应关系。
在一种可能的设计中，所述通信单元22，还用于：
向所述AMF实体发送请求消息；
接收所述AMF实体根据所述请求消息发送的所述DN标识和所述DN类型；或者，
接收无线接入网络RAN设备广播的所述DN标识和所述DN类型。
在一种可能的设计中，所述通信单元22，还用于：向所述AMF实体发送第一DN 信息，所述第一DN信息包括DN标识或者，包括DN标识和DN类型，所述第一DN信息用于所述AMF实体根据所述DN标识确定SMF实体，所述SMF实体用于建立所述会话类型的PDU会话。
应理解，该终端或终端的芯片可以用于实现本发明实施例的会话处理方法中由终端执行的步骤，相关特征可以参照上文，此处不再赘述。
例如，当图4所示的装置为SMF实体或SMF实体的芯片时，则：
所述通信单元22，用于接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括终端请求的分组数据单元PDU会话的会话类型，所述第二消息用于请求建立PDU会话；
所述处理单元21，用于根据所述PDU会话的会话类型，建立PDU会话。
在一种可能的设计中，所述通信单元22，还用于接收来自所述AMF实体的DN标识；
所述处理单元21，还用于根据所述DN标识和所述PDU会话的会话类型，确定用户面功能UPF实体，所述UPF实体用于建立所述会话类型的PDU会话。
应理解，该SMF实体或SMF实体的芯片可以用于实现本发明实施例的会话处理方法中由SMF实体执行的步骤，相关特征可以参照上文，此处不再赘述。
例如，当图4所示的装置为SMF实体或SMF实体的芯片时，则：
所述通信单元22，用于接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括第二数据网络DN信息，所述第二消息用于请求建立PDU会话；
所述处理单元21，用于根据所述第二DN信息，确定PDU会话的会话类型。
在一种可能的设计中，所述第二DN信息包括DN标识，所述处理单元21，具体用于：
根据所述DN标识，确定DN类型，以及根据所述DN类型，确定所述PDU会话的会话类型；或者，
所述第二DN信息包括DN类型，所述处理单元21，具体用于：所述SMF实体根据所述DN类型，确定所述PDU会话的会话类型。
在一种可能的设计中，如果所述第二消息中携带终端请求的PDU会话的会话类型，当所述处理单元21根据所述第二DN信息确定的PDU会话的会话类型与终端请求的PDU会话的会话类型不一致时，所述通信单元22，用于向终端发送会话拒绝消息，所述会话拒绝消息包括所述处理单元21根据所述第二DN信息确定的PDU会话的会话类型。
在一种可能的设计中，所述处理单元21，还用于：
根据所述PDU会话的会话类型，建立PDU会话。
在一种可能的设计中，所述处理单元21，还用于：
根据所述第二DN信息，确定用户面功能UPF实体，以及，
与所述UPF实体建立所述会话类型的PDU会话。
应理解，该SMF实体或SMF实体的芯片可以用于实现本发明实施例的会话处理方法中由SMF实体执行的步骤，相关特征可以参照上文，此处不再赘述。
例如，当图4所示的装置为AMF实体或AMF实体的芯片时，则：
所述通信单元22，用于接收来自终端的第一消息和第一数据网络DN信息，所述 第一消息用于请求建立PDU会话，
所述处理单元21，用于根据所述第一DN信息确定会话管理功能SMF实体；以及，根据所述第一消息，向所述SMF实体发送第二消息，所述第二消息用于请求建立PDU会话，其中，所述PDU会话的会话类型与所述第一DN信息对应。
在一种可能的设计中，所述第一消息和所述第二消息包括终端请求的PDU会话的会话类型；或者，
所述第一DN信息包括DN标识，所述第二消息包含所述DN标识，所述DN标识用于所述SMF实体根据所述DN标识确定所述PDU会话的会话类型。
在一种可能的设计中，所述第一DN信息包括DN标识；所述通信单元22，还用于接收来自所述终端的数据网络DN标识；
所述处理单元21，具体用于根据所述DN标识，确定DN类型；
所述通信单元22，还用于向NRF实体发送所述DN标识和所述DN类型；以及，接收来自所述NRF实体的所述SMF实体，所述SMF实体由所述NRF实体根据所述DN标识和所述DN类型确定。
在一种可能的设计中，所述通信单元22，还用于：
接收来自终端的请求注册的消息；
根据所述请求注册的消息，向数据库获取所述终端签约的DN信息，所述签约的DN信息包括DN标识和DN类型；
向所述终端发送所述终端签约的DN信息。
在一种可能的设计中，所述请求注册的消息包括所述终端的能力指示信息，所述能力指示信息用于指示所述终端支持的数据网络；
所述终端签约的DN信息与所述终端支持的数据网络对应。
应理解，该AMF实体或AMF实体的芯片可以用于实现本发明实施例的会话处理方法中由AMF实体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述会话处理方法中由终端执行的操作。该计算机可以是终端。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述会话处理方法中由SMF实体执行的操作。该计算机可以是SMF实体。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述会话处理方法中由AMF实体执行的操作。该计算机可以是AMF实体。
本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述任一实施例中由终端执行的会话处理方法中的流程。
本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述任一实施例中由SMF实体执行的会话处理方法中的流程。
本申请提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该 计算机软件指令可通过处理器进行加载来实现上述任一实施例中由AMF实体执行的会话处理方法中的流程。
本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。

Claims (56)

  1. 一种会话处理方法，其特征在于，包括：
    终端发起应用APP，根据应用APP确定分组数据单元PDU会话的会话类型；
    终端向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。
  2. 根据权利要求1所述的方法，其特征在于，所述终端确定PDU会话的会话类型，包括：
    所述终端根据第一对应关系，确定所述APP对应的所述会话类型；
    其中，所述第一对应关系为APP与PDU会话的会话类型的对应关系。
  3. 根据权利要求2所述的方法，其特征在于，
    所述第一对应关系为预先配置在所述终端；或者，
    所述第一对应关系由所述终端从所述AMF实体获得。
  4. 根据权利要求1所述的方法，其特征在于，所述终端确定PDU会话的会话类型，包括：
    所述终端根据第二对应关系，确定所述APP对应的DN标识；
    所述终端确定所述DN标识对应的DN类型；
    所述终端根据第三对应关系，确定所述DN类型对应的所述会话类型；
    其中，所述第二对应关系为APP与DN标识的对应关系，所述第三对应关系为DN类型与PDU会话的会话类型的对应关系。
  5. 根据权利要求4所述的方法，其特征在于，所述方法包括：
    所述终端向所述AMF实体发送请求消息，并，接收所述AMF实体根据所述请求消息发送的所述DN标识和所述DN类型；或者，
    所述终端接收无线接入网络RAN设备广播的所述DN标识和所述DN类型。
  6. 根据权利要求1至5任一所述的方法，其特征在于，还包括：
    所述终端向所述AMF实体发送第一DN信息，所述第一DN信息包括DN标识或者，包括DN标识和DN类型，所述第一DN信息用于所述AMF实体根据所述DN标识确定SMF实体，所述SMF实体用于建立所述会话类型的PDU会话。
  7. 一种会话处理方法，其特征在于，所述方法包括：
    会话管理功能SMF实体接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括终端请求的分组数据单元PDU会话的会话类型，所述第二消息用于请求建立PDU会话；
    所述SMF实体根据所述PDU会话的会话类型，建立PDU会话。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述SMF实体接收来自所述AMF实体的DN标识；
    所述SMF实体根据所述DN标识和所述PDU会话的会话类型，确定用户面功能UPF实体，所述UPF实体用于建立所述会话类型的PDU会话。
  9. 一种会话处理方法，其特征在于，所述方法包括：
    会话管理功能SMF实体接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括第二数据网络DN信息，所述第二消息用于请求建立PDU会话；
    所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型。
  10. 根据权利要求9所述的方法，其特征在于，
    所述第二DN信息包括DN标识，则所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型包括：所述SMF实体根据所述DN标识，确定DN类型，以及根据所述DN类型，确定所述PDU会话的会话类型；或者，
    所述第二DN信息包括DN类型，则所述SMF实体根据所述第二DN信息，确定PDU会话的会话类型包括：所述SMF实体根据所述DN类型，确定所述PDU会话的会话类型。
  11. 根据权利要求9或10所述的方法，其特征在于，如果所述第二消息中携带终端请求的PDU会话的会话类型，当所述SMF实体根据所述第二DN信息确定的PDU会话的会话类型与终端请求的PDU会话的会话类型不一致时，所述方法还包括：
    所述SMF实体向终端发送会话拒绝消息，所述会话拒绝消息包括所述SMF实体根据所述DN信息确定的PDU会话的会话类型。
  12. 根据权利要求9或10所述的方法，其特征在于，还包括：
    所述SMF实体根据所述PDU会话的会话类型，建立PDU会话。
  13. 根据权利要求9或10所述的方法，其特征在于，还包括：
    所述SMF实体根据所述第二DN信息，确定用户面功能UPF实体，以及，
    与所述UPF实体建立所述会话类型的PDU会话。
  14. 一种会话处理方法，其特征在于，所述方法包括：
    接入与移动性管理功能AMF实体接收来自终端的第一消息和第一数据网络DN信息，所述第一消息用于请求建立PDU会话，所述AMF实体根据所述第一DN信息确定会话管理功能SMF实体；
    所述AMF实体根据所述第一消息，向所述SMF实体发送第二消息，请求所述SMF实体建立PDU会话，其中，所述PDU会话的会话类型与所述第一DN信息对应。
  15. 根据权利要求14所述的方法，其特征在于，
    所述第一消息和所述第二消息包括终端请求的PDU会话的会话类型；或者，
    所述第一DN信息包括DN标识，所述第二消息包含所述DN标识，所述DN标识用于所述SMF实体根据所述DN标识确定所述PDU会话的会话类型。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一DN信息包括DN标识；
    所述AMF实体根据所述第一DN信息确定会话管理功能SMF实体，包括：
    所述AMF实体根据所述DN标识，确定DN类型；
    所述AMF实体向网络功能库NRF实体发送所述DN标识和所述DN类型；
    所述AMF实体接收来自所述NRF实体的所述SMF实体，所述SMF实体由所述NRF实体根据所述DN标识和所述DN类型确定。
  17. 根据权利要求14至16任一所述的方法，其特征在于，所述方法还包括：
    所述AMF实体接收来自终端的请求注册的消息；
    所述AMF实体根据所述请求注册的消息，向数据库获取所述终端签约的DN信息，所述终端签约的DN信息包括DN标识和DN类型；
    所述AMF实体向所述终端发送所述终端签约的DN信息。
  18. 根据权利要求17所述的方法，其特征在于，所述请求注册的消息包括所述终端的能力指示信息，所述能力指示信息用于指示所述终端支持的数据网络；
    所述终端签约的DN信息与所述终端支持的数据网络对应。
  19. 一种装置，其特征在于，包括：处理单元和通信单元；
    所述处理单元，用于发起应用APP，根据应用APP确定分组数据单元PDU会话的会话类型；
    所述通信单元，用于向接入与移动性管理功能AMF实体发送第一消息，所述第一消息包括所述会话类型，所述第一消息用于请求建立所述会话类型的PDU会话。
  20. 根据权利要求19所述的装置，其特征在于，所述处理单元，具体用于：
    根据第一对应关系，确定所述APP对应的所述会话类型；
    其中，所述第一对应关系为APP与PDU会话的会话类型的对应关系。
  21. 根据权利要求20所述的装置，其特征在于，
    所述第一对应关系为预先配置在所述终端；或者，
    所述第一对应关系由所述终端从所述AMF实体获得。
  22. 根据权利要求19所述的装置，其特征在于，所述处理单元，具体用于：
    根据第二对应关系，确定所述APP对应的DN标识；
    确定所述DN标识对应的DN类型；
    根据第三对应关系，确定所述DN类型对应的所述会话类型；
    其中，所述第二对应关系为APP与DN标识的对应关系，所述第三对应关系为DN类型与PDU会话的会话类型的对应关系。
  23. 根据权利要求22所述的装置，其特征在于，所述通信单元，还用于：
    向所述AMF实体发送请求消息；
    接收所述AMF实体根据所述请求消息发送的所述DN标识和所述DN类型；或者，接收无线接入网络RAN设备广播的所述DN标识和所述DN类型。
  24. 根据权利要求19至23任一所述的装置，其特征在于，所述通信单元，还用于：
    向所述AMF实体发送第一DN信息，所述第一DN信息包括DN标识或者，包括DN标识和DN类型，所述第一DN信息用于所述AMF实体根据所述DN标识确定SMF实体，所述SMF实体用于建立所述会话类型的PDU会话。
  25. 一种装置，其特征在于，包括：处理单元和通信单元；
    所述通信单元，用于接收来自接入与移动性管理功能AMF实体的第二消息，所述第二消息包括终端请求的分组数据单元PDU会话的会话类型，所述第二消息用于请求建立PDU会话；
    所述处理单元，用于根据所述PDU会话的会话类型，建立PDU会话。
  26. 根据权利要求25所述的装置，其特征在于，
    所述通信单元，还用于接收来自所述AMF实体的DN标识；
    所述处理单元，还用于根据所述DN标识和所述PDU会话的会话类型，确定用户面功能UPF实体，所述UPF实体用于建立所述会话类型的PDU会话。
  27. 一种装置，其特征在于，包括：处理单元和通信单元；
    所述通信单元，用于接收来自接入与移动性管理功能AMF实体的第二消息，所 述第二消息包括第二数据网络DN信息，所述第二消息用于请求建立PDU会话；
    所述处理单元，用于根据所述第二DN信息，确定PDU会话的会话类型。
  28. 根据权利要求27所述的装置，其特征在于，所述第二DN信息包括DN标识，所述处理单元，具体用于：根据所述DN标识，确定DN类型，以及根据所述DN类型，确定所述PDU会话的会话类型；或者，
    所述第二DN信息包括DN类型，所述处理单元，具体用于：根据所述DN类型，确定所述PDU会话的会话类型。
  29. 根据权利要求27或28所述的装置，其特征在于，
    如果所述第二消息中携带终端请求的PDU会话的会话类型，当所述处理单元根据所述第二DN信息确定的PDU会话的会话类型与终端请求的PDU会话的会话类型不一致时，所述通信单元，用于向终端发送会话拒绝消息，所述会话拒绝消息包括所述处理单元根据所述第二DN信息确定的PDU会话的会话类型。
  30. 根据权利要求27或28所述的装置，其特征在于，所述处理单元，还用于：
    根据所述PDU会话的会话类型，建立PDU会话。
  31. 根据权利要求27或28所述的装置，其特征在于，所述处理单元，还用于：
    根据所述第二DN信息，确定用户面功能UPF实体，以及，
    与所述UPF实体建立所述会话类型的PDU会话。
  32. 一种装置，其特征在于，包括：处理单元和通信单元；
    所述通信单元，用于接收来自终端的第一消息和第一数据网络DN信息，所述第一消息用于请求建立PDU会话，
    所述处理单元，用于根据所述第一DN信息确定会话管理功能SMF实体；以及，根据所述第一消息，向所述SMF实体发送第二消息，所述第二消息用于请求所述SMF实体建立PDU会话，其中，所述PDU会话的会话类型与所述第一DN信息对应。
  33. 根据权利要求32所述的装置，其特征在于，
    所述第一消息和所述第二消息包括终端请求的PDU会话的会话类型；或者，
    所述第一DN信息包括DN标识，所述第二消息包含所述DN标识，所述DN标识用于所述SMF实体根据所述DN标识确定所述PDU会话的会话类型。
  34. 根据权利要求32所述的装置，其特征在于，所述第一DN信息包括DN标识；
    所述通信单元，还用于接收来自所述终端的数据网络DN标识；
    所述处理单元，具体用于根据所述DN标识，确定DN类型；
    所述通信单元，还用于向NRF实体发送所述DN标识和所述DN类型；以及，接收来自所述NRF实体的所述SMF实体，所述SMF实体由所述NRF实体根据所述DN标识和所述DN类型确定。
  35. 根据权利要求32至34任一所述的装置，其特征在于，所述通信单元，还用于：
    接收来自终端的请求注册的消息；
    根据所述请求注册的消息，向数据库获取所述终端签约的DN信息，所述签约的DN信息包括DN标识和DN类型；
    向所述终端发送所述终端签约的DN信息。
  36. 根据权利要求35所述的装置，其特征在于，所述请求注册的消息包括所述终 端的能力指示信息，所述能力指示信息用于指示所述终端支持的数据网络；
    所述终端签约的DN信息与所述终端支持的数据网络对应。
  37. 一种会话处理装置，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求1到6任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求1到6任一项所述的方法中，在所述装置进行的消息处理或控制操作。
  38. 根据权利要求37所述的装置，其特征在于，所述装置为终端。
  39. 一种传输信息的装置，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求7到13任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求7到13任一项所述的方法中，在所述装置侧进行的消息处理或控制操作。
  40. 根据权利要求39所述的装置，其特征在于，所述装置为会话管理功能SMF实体。
  41. 一种传输信息的装置，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求14到18任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求14到18任一项所述的方法中，在所述装置侧进行的消息处理或控制操作。
  42. 根据权利要求41所述的装置，其特征在于，所述装置为接入与移动性管理功能AMF实体。
  43. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求1到6任一项所述的方法。
  44. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求7到13任一项所述的方法。
  45. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求14到18任一项所述的方法。
  46. 一种传输信息的装置，其特征在于，用于执行1到6项任一项所述方法。
  47. 一种传输信息的装置，其特征在于，用于执行7到13项任一项所述方法。
  48. 一种传输信息的装置，其特征在于，用于执行14到18项任一项所述方法。
  49. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述1到6任一项所述的方法。
  50. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述7到13项任一项所述的方法。
  51. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述14到18项任一项所述的方法。
  52. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1到6项任一项所述的方法。
  53. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求7到13项任一项所述的方法。
  54. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求14到18项任一项所述的方法。
  55. 一种通信系统，其特征在于，包括如权利要求25或26所述的装置，和，如权利要求32至36中任一项所述的装置。
  56. 一种通信系统，其特征在于，包括如权利要求27至31中任一项所述的装置，和，如权利要求32至36中任一项所述的装置。
PCT/CN2018/100641 2017-08-15 2018-08-15 一种会话处理方法及装置 WO2019034078A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AU2018317155A AU2018317155A1 (en) 2017-08-15 2018-08-15 Session handling method and apparatus
BR112020003140-2A BR112020003140A2 (pt) 2017-08-15 2018-08-15 método de manuseio de sessão, aparelho, sistema de chip, produto de programa de computador, meio de armazenamento legível por computador e sistema
RU2020110522A RU2776678C2 (ru) 2017-08-15 2018-08-15 Способ и устройство обработки сеанса
EP18845744.4A EP3668257B1 (en) 2017-08-15 2018-08-15 Session processing method and device
US16/791,775 US11540337B2 (en) 2017-08-15 2020-02-14 Session handling method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710698731.1A CN109548175B (zh) 2017-08-15 2017-08-15 一种会话处理方法及装置
CN201710698731.1 2017-08-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/791,775 Continuation US11540337B2 (en) 2017-08-15 2020-02-14 Session handling method and apparatus

Publications (1)

Publication Number Publication Date
WO2019034078A1 true WO2019034078A1 (zh) 2019-02-21

Family

ID=65362115

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/100641 WO2019034078A1 (zh) 2017-08-15 2018-08-15 一种会话处理方法及装置

Country Status (6)

Country Link
US (1) US11540337B2 (zh)
EP (1) EP3668257B1 (zh)
CN (1) CN109548175B (zh)
AU (1) AU2018317155A1 (zh)
BR (1) BR112020003140A2 (zh)
WO (1) WO2019034078A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111615217A (zh) * 2019-02-25 2020-09-01 华为技术有限公司 一种会话建立方法及装置
CN111698290A (zh) * 2020-05-19 2020-09-22 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102584730B1 (ko) * 2018-03-23 2023-10-05 삼성전자 주식회사 통신 네트워크에서 서비스 요청 절차를 처리하는 방법 및 시스템
WO2020199105A1 (zh) * 2019-04-01 2020-10-08 Oppo广东移动通信有限公司 数据绑定方法、信息更新方法及装置、终端
CN110121155B (zh) * 2019-06-17 2021-05-14 腾讯科技（深圳）有限公司 虚拟网络群组的广播方法、装置、设备及系统
CN113994762B (zh) * 2019-06-18 2023-10-20 Oppo广东移动通信有限公司 关联会话的方法和装置
CN113615246A (zh) * 2019-08-05 2021-11-05 Oppo广东移动通信有限公司 一种会话验证方法、电子设备及存储介质
WO2021087910A1 (zh) * 2019-11-07 2021-05-14 Oppo广东移动通信有限公司 用于连接网络的方法和设备
CN111405682B (zh) * 2020-03-19 2024-04-16 中国联合网络通信集团有限公司 一种数据转发方法及网关
CN111601353B (zh) * 2020-05-08 2022-02-22 北京紫光展锐通信技术有限公司 应用程序的路由选择方法及相关装置
CN113709749B (zh) * 2020-05-20 2024-09-13 中国移动通信集团陕西有限公司 业务处理的方法、装置、系统及计算设备
FR3111512A1 (fr) * 2020-06-18 2021-12-17 Orange Procédé de configuration d’un dispositif terminal
CN113839981B (zh) * 2020-06-24 2024-10-22 中兴通讯股份有限公司 会话管理方法、装置及存储介质
CN114080054B (zh) * 2020-08-13 2024-09-24 华为技术有限公司 一种pdu会话建立方法、终端设备和芯片系统
CN114827065B (zh) * 2022-04-28 2024-02-23 抖动科技(深圳)有限公司 基于统一通信信道的实时通信方法及相关设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101316194A (zh) * 2007-05-31 2008-12-03 华为技术有限公司 提高监听用户面数据上报可靠性的方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8995421B2 (en) 2008-08-08 2015-03-31 Qualcomm Incorporated Processing polling requests from radio link control peers
CN102355652B (zh) * 2011-08-01 2014-11-12 大唐移动通信设备有限公司 一种请求获得系统信息的方法及装置
WO2013072403A1 (en) 2011-11-15 2013-05-23 Nec Europe Ltd. Method for supporting pdn connectivity of a mobile terminal and mobile terminal
US10575220B2 (en) * 2017-03-21 2020-02-25 Electronics And Telecommunications Research Institute Session management method based on reallocation of PDU session anchor device, and device performing the session management method
CN111278031B (zh) 2017-08-11 2021-04-13 华为技术有限公司 Pdu类型的设置方法、ue策略的设置方法、实体及存储介质
US11950198B2 (en) 2017-08-11 2024-04-02 Interdigital Patent Holdings, Inc. Traffic steering and switching between multiple access networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101316194A (zh) * 2007-05-31 2008-12-03 华为技术有限公司 提高监听用户面数据上报可靠性的方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Procedures for the 5G System Stage 2", 3GPP TS 23. 502 V0. 5. 0, 14 July 2017 (2017-07-14), XP051336671 *
"System Architecture for the 5G System Stage 2", 3GPP TS 23. 501 V0. 2. 0, 6 February 2017 (2017-02-06), XP051230726 *
See also references of EP3668257A4

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111615217A (zh) * 2019-02-25 2020-09-01 华为技术有限公司 一种会话建立方法及装置
WO2020173430A1 (zh) * 2019-02-25 2020-09-03 华为技术有限公司 一种会话建立方法及装置
CN111615217B (zh) * 2019-02-25 2023-11-21 华为技术有限公司 一种会话建立方法及装置
US12041135B2 (en) 2019-02-25 2024-07-16 Huawei Technologies Co., Ltd. Session establishment method and apparatus
CN111698290A (zh) * 2020-05-19 2020-09-22 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质
CN111698290B (zh) * 2020-05-19 2021-06-15 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质

Also Published As

Publication number Publication date
EP3668257A4 (en) 2020-09-16
CN109548175A (zh) 2019-03-29
EP3668257A1 (en) 2020-06-17
RU2020110522A3 (zh) 2022-01-10
US20200187276A1 (en) 2020-06-11
BR112020003140A2 (pt) 2020-09-15
US11540337B2 (en) 2022-12-27
CN109548175B (zh) 2021-11-19
AU2018317155A1 (en) 2020-03-19
RU2020110522A (ru) 2021-09-16
EP3668257B1 (en) 2024-02-21

Similar Documents

Publication Publication Date Title
WO2019034078A1 (zh) 一种会话处理方法及装置
US20200296142A1 (en) User Group Establishment Method and Apparatus
WO2018141269A1 (en) Network registration and network slice selection system and method
US11457331B2 (en) Positioning method and related device
WO2019184651A1 (zh) 一种通信方法及装置
US11528677B2 (en) Storing and retrieving the network context of a device
US11533670B2 (en) Communication method and communications apparatus
TWI654859B (zh) 用於點對點應用之網路輔助裝置對裝置搜尋
US20210099912A1 (en) Rate control method, apparatus, and system
WO2019157963A1 (zh) 用于数据传输的方法、移动管理设备、数据业务处理设备和终端
US10194476B2 (en) Wi-Fi direct services mechanisms for wireless gigabit display extension
WO2018059133A1 (zh) 物联网中处理短消息的方法、移动管理网元和终端设备
WO2019218762A1 (zh) 一种策略控制方法、装置及系统
US20220272577A1 (en) Communication method and communication apparatus
EP4292310A1 (en) Method, apparatus, and computer program product to facilitate control of terminal timing information within a network
US20230137283A1 (en) Systems and methods to optimize registration and session establishment in a wireless network
US11792298B2 (en) Efficient resource representation exchange between service layers
WO2022126327A1 (zh) 无线通信方法、终端设备以及网元
RU2776678C2 (ru) Способ и устройство обработки сеанса
WO2024027578A1 (zh) 流量路由方法、装置及设备
WO2022165679A1 (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: 18845744

Country of ref document: EP

Kind code of ref document: A1

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

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018317155

Country of ref document: AU

Date of ref document: 20180815

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018845744

Country of ref document: EP

Effective date: 20200313

ENP Entry into the national phase

Ref document number: 112020003140

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200214