WO2019047935A1 - 一种会话建立方法及装置 - Google Patents

一种会话建立方法及装置 Download PDF

Info

Publication number
WO2019047935A1
WO2019047935A1 PCT/CN2018/104680 CN2018104680W WO2019047935A1 WO 2019047935 A1 WO2019047935 A1 WO 2019047935A1 CN 2018104680 W CN2018104680 W CN 2018104680W WO 2019047935 A1 WO2019047935 A1 WO 2019047935A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
information
network device
deactivated state
air interface
Prior art date
Application number
PCT/CN2018/104680
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 EP18854810.1A priority Critical patent/EP3664570B1/en
Priority to AU2018329060A priority patent/AU2018329060B2/en
Publication of WO2019047935A1 publication Critical patent/WO2019047935A1/zh
Priority to US16/810,660 priority patent/US11202338B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a session establishment method and apparatus.
  • a Packet Data Unit (PDU) session is a session between a terminal and a Data Network (DN) to provide PDU connectivity services.
  • the PDU connectivity service refers to a service that provides PDU exchange between a terminal and a DN determined by a Data Network Name (DNN).
  • DNN Data Network Name
  • a PDU session includes at least one flow, and one of the flows is a default flow.
  • the default flow refers to the flow that is processed by the default QoS rules.
  • the default QoS rule is the only QoS rule in the PDU session that may not contain a packet filter.
  • the base station When the PDU session is established, the base station establishes corresponding air interface resources for each flow included in the PDU session, and the air interface resources of each flow are independently established.
  • the process of establishing an air interface resource for QoS Flow may or may not succeed.
  • the air interface resource of the default flow of the PDU session is successfully established, indicating that the PDU session has been successfully established; correspondingly, if the air interface resource of the default flow of the PDU session fails to be established, the PDU session is marked. Not successfully established.
  • the present application provides a session establishment method and apparatus for providing a method for establishing a PDU session.
  • an embodiment of the present application provides a session establishment method, where the method includes:
  • the first network device establishes the PDU session in a deactivated state according to the first information or triggers release of the PDU session; the first information is used to indicate Whether the PDU session in the deactivated state is allowed to be established when the establishment of the air interface resource of the default flow of the PDU session fails.
  • the PDU session in the deactivated state may be established or the PDU session is triggered to be released, thereby providing a default in the PDU session. If the establishment of the air interface resource fails, the PDU session is further processed to solve the problem of how to determine the PDU session in the deactivated state.
  • the embodiment of the present application provides a session establishment method, where the method includes:
  • the first network device maintains the PDU session as a deactivated state or triggers release of the PDU session according to the first information; the first information is used to indicate Whether to maintain the PDU session as a deactivated state when the air interface resource establishment of the default flow of the PDU session fails.
  • the first network device may maintain the PDU session in the deactivated state or trigger the release of the deactivated state of the PDU session, thereby
  • the PDU session in the deactivated state is further processed, and the problem of how to determine whether to maintain the PDU session in the deactivated state is solved.
  • the first network device determines whether the air interface resource of the default flow of the PDU session is successfully established, including:
  • the first network device acquires a flow list, where the flow list is generated by the second network device according to the air interface resource establishment result of the PDU session, where the flow list includes a flow in which the PDU session air interface resource establishment failure occurs;
  • the first network device determines, according to the flow list, whether the air interface resource of the default flow of the PDU session is successfully established.
  • the first network device can quickly and accurately determine the establishment result of the air interface resource of the default flow of the PDU session by using the flow list of the flow that fails to establish the PDU session air interface resource, thereby improving the default of determining the PDU session. Whether the flow of air interface resources establishes the accuracy of success.
  • the first information is a slice/service type in the subscription data of the terminal corresponding to the PDU session
  • the first information is a policy and a charging control rule of the terminal corresponding to the PDU session
  • the first information is indication information that is sent by the terminal to the first network device.
  • the method further includes:
  • the first network device acquires second information, where the second information is used to indicate a time point of activating the PDU session in a deactivated state;
  • the method further includes:
  • the first network device activates the PDU session in a deactivated state at a time indicated by the second information
  • the first network device sends the second indication information to the terminal, where the second indication information is used to indicate that the terminal activates the PDU session in a deactivated state at the time point.
  • the first network device activates the PDU session in the deactivated state at the time indicated by the second information, which can save time and network resources for establishing a PDU session, and can improve the PDU session with respect to re-establishing the PDU session.
  • the efficiency of the establishment enables the user plane resources of the PDU session to be established more quickly.
  • the method further includes:
  • the first network device acquires third information, where the third information is used to indicate a maximum number of times that the PDU session in the deactivated state is activated;
  • the method further includes:
  • the first network device determines that the activated number of times of the PDU session in the deactivated state is equal to the maximum number of times, triggering a process of releasing the PDU session.
  • the method further includes:
  • the first network device determines that the PDU session in the deactivated state is not allowed to be established according to the first information, when it is determined that at least one flow of the air interface resource is successfully established in the flow included in the PDU session, the first network device triggers Establishing a user plane resource for the PDU session;
  • the first network device sends the QoS session of the default flow to the second network device, if the first network device determines that the PDU session in the deactivated state is not allowed to be established according to the first information, And instructing the second network device to establish an air interface resource for the default flow according to the QoS parameter of the default flow.
  • the first network device may continue to establish user plane resources for the PDU session when the air interface resource establishment of the default flow of the PDU session fails, so that the user plane resources of the PDU session can be quickly established.
  • the method further includes:
  • the first network device releases the air interface resource of the stream in which the PDU session air interface resource is successfully established.
  • the first network device releases the air interface resource of the stream in which the PDU session air interface resource is successfully established, and the released resource may be reused, thereby improving resource utilization.
  • an embodiment of the present application provides a session establishing apparatus, where the communications apparatus includes a memory, a transceiver, and a processor, wherein: the memory is configured to store an instruction; the processor is configured to control the transceiver according to the instruction to execute the memory storage. Signal reception and signal transmission are performed, and when the processor executes the instruction stored in the memory, the terminal is configured to perform the method in any of the above aspects of the first aspect or the second aspect.
  • the embodiment of the present application provides a session establishing apparatus, which is used to implement any one of the foregoing first aspect or the second aspect, including a corresponding functional module, for example, including a processing unit, a receiving unit, a sending unit, and the like. , respectively, used to implement the steps in the above method.
  • an embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the first Aspect or method of any of the possible aspects of the second aspect.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform the method in any one of the foregoing first aspect or the second aspect.
  • an embodiment of the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory to implement any one of the foregoing first aspect or the second aspect. The method in the design.
  • the embodiment of the present application provides a session establishment method, including:
  • the terminal generates the first information, where the first information is used to indicate whether the PDU session in the deactivated state is allowed to be established when the air interface resource establishment failure of the default flow of the PDU session fails.
  • the terminal sends the first information to the first network device by using the second network device.
  • the terminal sends a first information to the first network device, indicating whether the PDU session in the deactivated state is allowed to be established, so that the first network device can establish the air interface resource establishment failure of the default flow of the PDU session.
  • the deactivated PDU session provides a further processing mechanism for the PDU session in the event that the air interface resource establishment failure of the default flow of the PDU session fails.
  • the PDU session is established as a deactivated state
  • the method further includes:
  • Second indication information that is sent by the first network device by using the second network device; the second information is used to indicate a time point of activating the PDU session in a deactivated state;
  • the terminal sends an activation request message to the second network device at a time indicated by the second indication information, where the activation request message is used to request activation of the PDU session in a deactivated state.
  • the embodiment of the present application provides a session establishing apparatus, where the communications apparatus includes a memory, a transceiver, and a processor, wherein: the memory is used to store an instruction; the processor is configured to control the transceiver according to the instruction to execute the memory storage. Signal reception and signal transmission are performed, and when the processor executes an instruction stored in the memory, the terminal is configured to perform the method in any of the possible aspects of the above eighth aspect.
  • the embodiment of the present application provides a session establishing apparatus, which is used to implement any one of the foregoing eight aspects, including a corresponding function module, for example, including a processing unit, a receiving unit, a sending unit, etc., respectively Implement the steps in the above method.
  • the embodiment of the present application provides a computer readable storage medium, where the computer storage medium stores computer readable instructions, and when the computer reads and executes the computer readable instructions, causes the computer to execute the foregoing Any of the eight possible approaches in the design.
  • the embodiment of the present application provides a computer program product, when the computer reads and executes the computer program product, causing the computer to perform the method in any of the foregoing eight aspects.
  • the embodiment of the present application provides a chip, where the chip is connected to a memory, for reading and executing a software program stored in the memory, to implement any possible design in the foregoing eighth aspect. Methods.
  • FIG. 1 is a schematic diagram of a system architecture applicable to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a session establishment method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of establishing a user plane of a PDU session according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of establishing a user plane of a PDU session according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a PDU session release process according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a session establishment method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a session establishment apparatus according to an embodiment of the present application.
  • FIG. 1 exemplarily shows a system architecture diagram suitable for the embodiment of the present application.
  • the terminal 101 can communicate with the core network via the access network entity 102. It can be referred to as User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • UE User Equipment
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • FIG. 1 Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks, and the like.
  • FIG. 1 for convenience of description, only one terminal is illustrated. In an actual network, multiple terminals may coexist, and details are not described herein again.
  • An access network (AN) entity 102 which may also be referred to as a radio access network (Radio Access Network, (R) AN) entity, hereinafter collectively referred to as an access network entity or (R)
  • the AN entity is mainly responsible for providing a wireless connection to the terminal 101, ensuring reliable transmission of uplink and downlink data of the terminal 101, and the like.
  • the access network entity 102 can be a gNB (generation Node B) in a 5G system, and can be a Global System of Mobile communication (GSM) system or a base station in Code Division Multiple Access (CDMA).
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • NodeB NodeB
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • a Session Management Function (SMF) entity 103 which may be used to perform part of the functions of the Mobility Management Entity (MME) in the LTE system, and is mainly responsible for establishing a session, managing a session, and the like for the terminal 101.
  • MME Mobility Management Entity
  • UPF User Plane Function
  • the user plane function entity 104 is a function network element of the user plane of the terminal 101.
  • the main functions include packet routing and forwarding, and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • Access and Mobility Management Function (AMF) entity 105 the main functions include the endpoint of the radio access network control plane, the endpoint of non-access signaling, mobility management, lawful interception, access authorization Or authentication and so on.
  • AMF Access and Mobility Management Function
  • the Policy Control Funnel (PCF) entity 106 is mainly responsible for the establishment, release, and modification of the user plane transmission path.
  • AUSF Authentication Server Function
  • a User Data Management (UDM) entity 108 is mainly responsible for managing subscription data of users and the like.
  • the Data Network (DN) 109 may refer to a network that provides services for the terminal 101.
  • some DNs may provide the Internet access function for the terminal 101, and some DNs may provide the MMS function for the terminal 101.
  • a PDU session is a connection between a terminal and a DN, providing a PDU connectivity service.
  • the terminal can establish multiple PDU sessions to connect to the same DN or different DNs.
  • the terminal can also establish PDU sessions served by different UPFs to connect to the same DN.
  • the state of the PDU session includes at least an active state and an inactive state (Inactive or de-activted).
  • the active state refers to a state in which the user plane resource of the PDU session has been established, and an end-to-end connection is established between the terminal and the DN, and data can be transmitted through the PDU session.
  • Inactive state means that the PDU session only retains part of the user plane resources, but the user plane air interface resources between the terminal and the (R) AN entity, and the connection between the (R) AN entity and the UPF entity are not established, the terminal and Data cannot be transferred between DNs, but some information of the PDU session is still retained in the SMF entity and the UPF entity.
  • the PDU session establishment process is generally divided into three parts: the first part, the preparation process of the user plane resources of the PDU session, the second part, the establishment of the air interface resource of the PDU session, and the third part, the subsequent process of the PDU session, for example, after the PDU session.
  • the (R) AN entity sends a process such as the port number of the (R) AN entity to the UPF entity, thereby completing the confirmation of the established PDU session.
  • the embodiment of the present application mainly relates to the second part, that is, the air interface resource for establishing a PDU session, which is described in detail below.
  • FIG. 1 Also shown in FIG. 1 are possible implementations of interfaces in various entities, such as the N2 interface between the access network entity 102 and the AMF entity 109, the N9 interface between the access network entity 102 and the UPF entity 104, and the like, I will not repeat them here.
  • FIG. 2 it is a schematic flowchart of a session establishment method provided by an embodiment of the present application.
  • the first network device in the method shown in FIG. 2 may refer to an SMF entity, and the second network device may refer to a (R) AN entity.
  • the method includes:
  • Step 201 The first network device determines whether the air interface resource of the default flow of the PDU session is successfully established.
  • the PDU session may be a newly initiated PDU session or a session in a deactivated state.
  • the terminal needs to activate the PDU session in the deactivated state by using a Service Request message.
  • Step 202 If the air interface resource of the default flow of the PDU session fails to be established, the first network device establishes the PDU session in the deactivated state according to the first information or triggers release of the PDU session; the first information And indicating whether to establish the PDU session in the deactivated state when the air interface resource establishment failure of the default flow of the PDU session fails.
  • the PDU session in the deactivated state is established according to the first information, which may be that the newly initiated PDU session is established as a deactivated state;
  • the PDU session in the deactivated state is established according to the first information, which may be that the PDU session in the deactivated state is kept in a deactivated state.
  • the first network device may acquire the first information from the UDM entity or the PCF entity.
  • the first information is used to indicate whether to establish the PDU session in the deactivated state when the air interface resource establishment failure of the default flow of the PDU session fails.
  • the first information may be in multiple forms.
  • the first information may be a slice/service type (SST) in the subscription data of the terminal corresponding to the PDU session.
  • SST slice/service type
  • the first information When the first information is a slice/service type in the subscription data of the terminal corresponding to the PDU session, the first information may be determined to be a deactivated state by indicating whether the PDU session requested by the terminal can be established. For example, when the SST of the slice to which the PDU session belongs is a Massive Internet of Things (MIoT), the first information indicates that the PDU session is allowed to be established as a deactivated state; and the SST of the slice to which the PDU session belongs is an IP multimedia sub- In the case of the System (Multimedia Subsystem, IMS) type, the first information indicates that the PDU session is not allowed to be established as a deactivated state.
  • MIoT Massive Internet of Things
  • IMS IP multimedia sub- In the case of the System (Multimedia Subsystem, IMS) type
  • the first information may be a Policy and Charging Control (PCC) rule of the terminal corresponding to the PDU session.
  • the PCC rule may be a high reliability low delay (Slice/Service Types, SST) of the slice to which the PDU session belongs (ultra-reliable)
  • SST Policy/Service Types
  • URLLC low latency communications
  • MIoT Massive Internet of Things
  • the PDU session is allowed to be allowed.
  • IMS IP Multimedia Subsystem
  • the first information may also be indication information that is sent by the terminal to the first network device.
  • the terminal Before the PDU session is established, the terminal generates the first information, and sends the first information to the first network device by using the second network device, where the terminal may indicate, by using the first information, whether the PDU session can be established as a deactivated state.
  • the terminal When the first information is sent by the terminal to the first network device, the terminal first sends the first information to the second network device, and the second network device forwards the information to the first network device.
  • the first information may be located in a PDU session establishment request or a PDU session user plane resource establishment request sent by the terminal to the second network device, and may also be located in a service request (Service Request) or a handover request sent to the second network device.
  • Service Request Service Request
  • the embodiment of the present application is not limited thereto, and the terminal may determine the message carrying the first information according to actual conditions.
  • the first information may also be a local policy configured by the first network device.
  • the local policy may indicate that the PDU session is not allowed to be established. Deactivated state; when the SST of the slice to which the PDU session belongs is MioT, it may indicate that the PDU session is allowed to be set to the deactivated state; when the SST of the slice to which the PDU session belongs is of the IMS type, it may indicate that the PDU session is not allowed to be deactivated. state.
  • the terminal may trigger the establishment process of the PDU session, or the network side actively establishes a PDU session for the terminal.
  • the user plane resource preparation process of the PDU session needs to be triggered, and the specific content of the process is
  • the application embodiment is not limited thereto, and details are not described herein again.
  • the air interface resource of the PDU session needs to be established.
  • the user plane resource of the PDU session may be divided into two parts, an air interface resource between the terminal and the (R) AN entity, and (R) a network side resource between the AN entity and the DN.
  • the second network device establishes air interface resources for each stream in the PDU session according to parameters such as a QoS profile required for each stream in the PDU session. At least one stream is included in one PDU session, and one of the streams is a default stream.
  • the default stream is the stream that is processed by the default QoS rules.
  • the default QoS rule is the only QoS rule in the PDU session that may not contain a packet filter. If the air interface resource of the default stream of the PDU session fails to be established, it indicates that the PDU session establishment fails. If the air interface resource of the default flow of the PDU session is successfully established, even if the air interface resource of other flows included in the PDU session fails to be established, the PDU session can be considered as successful.
  • the (R) AN entity establishes a corresponding air interface resource for each flow of the PDU session, thereby establishing a user plane resource for the PDU session.
  • the process of establishing an air interface resource for each flow may or may not fail. If the process of establishing an air interface resource for a flow fails, the flow cannot pass data.
  • the second network device feeds back the result of the success or failure of the air interface resource establishment for each flow to the network side, that is, sends the flow list to the first network device.
  • the flow included in the flow list is a flow in which the air interface resource fails to be established when the second network device establishes an air interface resource for the flow in the PDU session.
  • the list of flows may also be referred to as List of rejected QoS Flows, or a list of rejected QoS Flows for the PDU Sessions activated. .
  • the first network device may first obtain a flow list, and determine, according to the flow list, whether the air interface resource of the default flow of the PDU session is successfully established.
  • the flow list is generated by the second network device according to the air interface resource establishment result of the PDU session, where the flow list includes a flow in which the PDU session air interface resource establishment fails.
  • the flow list obtained by the first network device is sent by the second network device to the first network device by using an entity such as an AMF entity.
  • the second network device sends an N2 message including N2 session management (SM) information to the AMF entity, where the N2 session management information includes the PDU session identifier, the AN tunnel information, and the activated PDU. Information such as List of accepted QoS Flows for the PDU Sessions activated, the flow list, and the like.
  • the N2 message may further include one or more of the following: a PDU session identifier, a reason for establishing a failure, and N2 session management (SM) information (information).
  • the AMF entity sends an N11 message including the N2 session management information to the first network device. After receiving the N11 message, the first network device may obtain the flow list.
  • the terminal roams from a Home-Public Land Mobile Network (H-PLMN) to a visited public land mobile network (Visited-PLMN, V).
  • H-PLMN Home-Public Land Mobile Network
  • V visited public land mobile network
  • the terminal is served by the first network device instead of the third network device, and the third network device and the first network device are both SMF entities.
  • the second network device sends an N2 message including a flow list to the AMF entity
  • the AMF entity sends an N11 message including the flow list to the third network device, where the third network device sends the flow list including the flow list to the first network device.
  • the N16 message after the first network device receives the N16 message, may obtain the flow list.
  • the first network device may determine whether the air interface resource of each flow in the PDU session is successfully established.
  • step 202 if the first network device determines that the default flow of the PDU session is not in the flow list, the first network device may determine that the PDU session is successfully established, and then perform a subsequent process.
  • the first network device determines that the default flow of the PDU session is in the flow list, the air interface resource of the default flow of the PDU session may be considered to be failed. At this time, the first network device may establish the PDU session in the deactivated state or trigger the release of the PDU session.
  • the first network device may determine, according to the first information, whether to allow the establishment of the PDU session in a deactivated state or trigger release of the PDU session. If the first network device determines, according to the first information, that the PDU session is allowed to be established in a deactivated state, the PDU session in a deactivated state may be established; correspondingly, the first network device is configured according to the The first information determines that the PDU session is not allowed to establish the PDU session in a deactivated state, and triggers release of the PDU session.
  • the air interface resource of the flow in which the PDU session air interface resource is successfully established may be released, thereby preventing the PDU session in the deactivated state from occupying too many resources.
  • the first network device may establish the PDU session in a deactivated state by using the following steps:
  • Step 1 The first network device sends an Internet Protocol-Connectivity Access Network (IP-CAN) session modification (Session Modification) message to the PCF entity, where the message is used to indicate that the PDU session is established as a deactivated state.
  • IP-CAN Internet Protocol-Connectivity Access Network
  • Session Modification Session Modification
  • Step 2 The first network device sends an N4 Session Update Request message to the UPF entity, where the request message is used to indicate that the PDU session is established as a deactivated state.
  • the first network device receives the N4 session update response message sent by the UPF entity.
  • Step 3 The first network device sends an N11 message response (Message Response) to the AMF entity; the N11 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes a non-access stratum (NAS). Message.
  • Message Response N11 message response
  • NAS non-access stratum
  • Step 4 The AMF entity sends an N2 message response to the second network device, where the N2 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes an SM non-access stratum (NAS) message.
  • NAS non-access stratum
  • Step 5 The second network device transparently transmits the SM NAS message in the N2 message response to the terminal, and the SM NAS message is used to indicate that the PDU session is established as a deactivated state, and the terminal synchronizes the PDU session state according to the message.
  • the second network device may further send, to the first network device, second information, where the second information is used to indicate a point in time at which the PDU session of the deactivated state is activated.
  • the second information may be sent to the first network device in the same message as the flow list.
  • the PDU session in the deactivated state is activated at a point in time indicated by the second information.
  • the second information may indicate the timing duration of the timer.
  • the first network device sets a timer according to the timing duration indicated by the second information, and activates the deactivated state when the timer expires. PDU session.
  • the first network device may further send the second indication information to the terminal by using the second network device.
  • the terminal may then send an activation request message to the second network device at the time indicated by the second indication information, where the activation request message is used to request activation of the PDU session in the deactivated state.
  • the activation request message may be a service request (Service Request) or the like, which is not limited by the embodiment of the present application.
  • the third information may also be included in the subscription data or the PCC rule.
  • the third information may also be acquired, where the third information is used to indicate the maximum number of times the PDU session in the deactivated state is activated.
  • the first network device may reactivate the PDU session in the deactivated state after determining that the default flow of the PDU session is in the flow list and establishing the PDU session in the deactivated state. After the first network device obtains the third information, if it is determined that the activated number of the PDU session in the deactivated state is equal to the maximum number of times, the step does not activate the PDU session in the deactivated state, but triggers release. The PDU session.
  • any one of the following processes may be performed:
  • the first network device triggers establishment of a user plane resource for the PDU session when it is determined that at least one flow of the air interface resource establishment is successful in the flow included in the PDU session. At this time, although the default flow of the PDU session is not established successfully, but the flow of the air interface resource is successfully established in the PDU session, the data can be successfully transmitted through the air interface resource.
  • the process 2 the first network device sends a QoS parameter of the default flow to the second network device, and instructs the second network device to establish an air interface resource for the default flow according to the QoS parameter of the default flow.
  • the quality of service parameter of the default stream sent by the first network device is obtained by the PCF entity. Specifically, after the air interface resource of the default flow fails to be established, the first network device notifies the PCF entity that the air interface resource of the default flow fails to be established. At this time, the PCF entity re-adjusts the service quality parameter of the default flow, and adjusts the service of the default flow.
  • the quality parameter is sent to the first network device, and the first network device forwards the obtained quality of service parameter of the default flow to the AMF entity, and the AMF entity forwards the service quality parameter of the default flow to the second network device, and the second network device
  • the QoS parameter of the default stream re-establishes an air interface resource for the default stream.
  • the reason why the air interface resource of the default flow is not successfully established may be because the quality of service corresponding to the quality of service parameter used by the second network device to establish the default flow is high, and the second network device cannot allocate the air interface resource that meets the requirement.
  • the second network device may be unable to allocate air interface resources because the second network device is faulty, that is, the Error Case.
  • the quality of service corresponding to the quality of service parameter sent by the first network device is lower than the quality of service corresponding to the quality of service parameter used by the second network device to establish the default flow, and therefore the second network device is configured according to the first network device.
  • the QoS parameter of the default flow has a relatively high probability of establishing an air interface resource for the default flow, thereby establishing a PDU session.
  • Flow 3 The first network device triggers a process of releasing the PDU session.
  • the first network device may also release the air interface resource of the stream in which the PDU session air interface resource is successfully established, thereby improving the utilization of the air interface resource.
  • the second network device may also notify the first network device to perform one of the foregoing processes 1 to 3, and may determine the process to be performed in other manners.
  • FIG. 3 is a schematic flowchart of establishing a user plane of a PDU session according to an embodiment of the present application.
  • the first network device is an SMF entity
  • the second network device is a (R) AN entity.
  • Step 301a The SMF entity sends a request message to the UDM, where the request message is used to request subscription data of the terminal.
  • the first information is included in the contract data.
  • the subscription information further includes a third information.
  • Step 302a The UDM entity sends a request response message to the SMF entity, where the request response message includes subscription data or PCC rules.
  • step 301a and step 302a may also be replaced by step 301b and step 302b:
  • Step 301b The SMF entity sends a request message to the PCF entity, where the request message is used to request a PCC rule.
  • the first information is included in the PCC rules.
  • the third information is also included in the PCC rule.
  • Step 302b The PCF entity sends a request response message to the SMF entity, where the request response message includes a PCC rule.
  • Step 303 Establish a preparation process of the PDU user plane resource.
  • Step 304 The (R) AN entity establishes an air interface resource for each flow included in the PDU session.
  • Step 305 The (R) AN entity generates a flow list according to the establishment result of the air interface resource of each flow in the PDU session, and sends an N2 message including the N2 session management information to the AMF entity.
  • the N2 session management information includes a flow list, where the flow list includes a flow in which the PDU session air interface resource establishment fails.
  • the second information is also included in the N2 message.
  • the N2 message may also include one or more of the following: a PDU session identifier, and a reason for the failure to be established.
  • Step 306 The AMF entity sends an N11 message including the N2 session management information to the SMF entity.
  • Step 307 If the SMF entity determines that the default flow of the PDU session is located in the flow list, and determines that the PDU session is allowed to be established as a deactivated state according to the first information, triggering to establish the PDU of the deactivated state. Conversation.
  • Step 308 The SMF entity sends an IP-CAN session modification message to the PCF entity, where the message is used to indicate that the PDU session is established as a deactivated state. If there is a policy associated with the deactivated PDU session in the PCF entity, the PCF entity will send the associated policy to the SMF entity.
  • Step 309 The SMF entity sends an N4 Session Establishment/Modification Request message to the UPF entity. If the request message is an N4Session establishment request message, the SMF entity instructs the UPF entity to buffer the downlink data and send the downlink data notification (Downlink Data). Notification, DDN) message, and will not send the port number of the (R) AN entity to the UPF entity. If the request message is an N4 Session modification request message, the SMF entity may update the parameters on the UPF entity as needed.
  • N4Session establishment request message the SMF entity instructs the UPF entity to buffer the downlink data and send the downlink data notification (Downlink Data). Notification, DDN) message, and will not send the port number of the (R) AN entity to the UPF entity.
  • DDN Downlink Data notification
  • the SMF entity may update the parameters on the UPF entity as needed.
  • Step 310 The SMF entity receives an N4 session update response message sent by the UPF entity.
  • Step 311 The SMF entity sends an N11 message response to the AMF entity.
  • the N11 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes an SM non-access stratum message.
  • the first information may also be included in the N11 message. If the status of the PDU session is maintained in the AMF entity, the AMF entity may mark the PDU session as a deactivated state according to the first information.
  • Step 312 The AMF entity sends an N2 message response to the (R) AN entity, where the N2 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes a SM Non-access stratum (NAS) message.
  • NAS Non-access stratum
  • Step 313 After receiving the N2 message response, the (R) AN entity deletes resources related to the PDU session. At the same time, the (R) AN entity transparently transmits the SM NAS message in the N2 message response to the terminal, and the SM NAS message is used to indicate that the PDU session is established as a deactivated state, and the terminal synchronizes the PDU session state according to the message.
  • step 314 the SMF entity activates the PDU session in the deactivated state at the time indicated by the second information.
  • the SMF entity may also send the second information to the terminal, and the terminal sets a timer according to the second information, so that the terminal activates the PDU session in the deactivated state at the time indicated by the second information.
  • the deactivated state is no longer activated.
  • the PDU session but triggers the release of the PDU session.
  • the SMF entity specifically activates the PDU session in the deactivated state, which is not limited in this embodiment of the present application, and details are not described herein again.
  • the PDU session in the deactivated state may be established, and the PDU session may be in the appropriate time.
  • the PDU session re-establishes the air interface resource. Compared with re-establishing the PDU session, activating the deactivated PDU session can save time and signaling, so that the PDU session user plane resources can be quickly established, thereby improving system efficiency.
  • FIG. 4 is a schematic flowchart of establishing a user plane of a PDU session according to an embodiment of the present application.
  • the flow of Figure 4 is the scenario of home routed.
  • the terminal roams from the first network device in the H-PLMN to the third network device in the V-PLMN.
  • the third network device and the first network device are both SMF entities.
  • the first network device is called H- The SMF entity
  • the third network device is called a V-SMF entity
  • the second network device is called a (R) AN entity.
  • Step 401a The H-SMF entity sends a request message to the UDM entity, where the request message is used to request subscription data of the terminal.
  • the first information is included in the contract data.
  • Step 402a The UDM entity or the PCF entity sends a request response message to the SMF entity, where the request response message includes subscription data or PCC rules.
  • step 401a and step 402a may also be replaced by step 401b and step 402b:
  • Step 401b The H-SMF entity sends a request message to the PCF entity, where the request message is used to request a PCC rule.
  • the first information is included in the PCC rules.
  • Step 402b The PCF entity sends a request response message to the H-SMF entity, where the request response message includes a PCC rule.
  • Step 403 Establish a preparation process of the PDU user plane resource.
  • Step 404 The (R) AN entity establishes an air interface resource for each flow included in the PDU session.
  • Step 405 The (R) AN entity generates a flow list according to the establishment result of the air interface resource of each flow in the PDU session, and sends an N2 message including the N2 session management information to the AMF entity.
  • the N2 session management information includes a flow list, where the flow list includes a flow in which the PDU session air interface resource establishment fails.
  • the second information is also included in the N2 message.
  • the N2 message may also include one or more of the following: a PDU session identifier, and a reason for the failure to be established.
  • Step 406 The AMF entity sends an N11 message including the N2 session management information to the V-SMF entity.
  • Step 407 The V-SMF entity sends an N16 message including the N2 session management information to the H-SMF entity.
  • Step 408 If the H-SMF entity determines that the default flow of the PDU session is in the flow list, and determines that the PDU session is allowed to be established as a deactivated state according to the first information, triggering establishment of a deactivated state Said PDU session.
  • Step 409 The H-SMF entity sends an IP-CAN session modification message to the PCF entity, where the message is used to indicate that the PDU session is established as a deactivated state. If there is a policy in the PCF entity associated with the deactivated PDU session, the PCF entity will send the relevant measurement to the H-SMF entity.
  • Step 410 The H-SMF entity sends an N16 message response to the V-SMF entity, to indicate that the PDU session is established as a deactivated state.
  • Step 411 The V-SMF entity sends an N4 session establishment or modification request message to the UPF entity, where the request message is used to indicate that the PDU session is established as a deactivated state. If the request message is an N4 Session establishment request message, the SMF entity instructs the UPF entity to buffer the downlink data and send the downlink data notification message, and does not send the port number of the (R) AN entity to the UPF entity. If the request message is an N4 Session modification request message, the SMF entity may update the parameters on the UPF entity as needed.
  • Step 412 The V-SMF entity receives the N4 session update response message sent by the UPF entity.
  • Step 413 The V-SMF entity sends an N11 message response to the AMF entity.
  • the N11 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes an SM non-access stratum message.
  • Step 414 The AMF entity sends an N2 message response to the (R) AN entity, where the N2 message response is used to indicate that the PDU session is established as a deactivated state, and the message includes an SM Non-access stratum (NAS) message.
  • NAS Non-access stratum
  • Step 415 After receiving the N2 message response, the (R) AN entity deletes resources related to the PDU session. At the same time, the (R) AN entity transparently transmits the SM NAS message in the N2 message response to the terminal, and the SM NAS message is used to indicate that the PDU session is established as a deactivated state, and the terminal synchronizes the PDU session state according to the message.
  • step 416 the H-SMF entity activates the PDU session in the deactivated state at the time indicated by the second information.
  • the H-SMF entity determines that the number of times the PDU session is activated in the deactivated state is equal to the maximum number of times indicated by the third information, the deactivation is no longer activated.
  • the PDU session of the state but triggers the release of the PDU session.
  • the SMF entity specifically activates the PDU session in the deactivated state, which is not limited in this embodiment of the present application, and details are not described herein again.
  • the PDU session in the deactivated state may be established, and the PDU session may be at an appropriate time.
  • the activation of the deactivated PDU session can save time and signaling compared to re-establishing the PDU session, so that the PDU session user plane resources can be quickly established, thereby improving system efficiency.
  • FIG. 5 is a schematic diagram of a PDU session release process provided by an embodiment of the present application.
  • the first network device is an SMF entity
  • the second network device is a (R) AN entity.
  • Step 501 The SMF entity sends a request message to the PCF entity, where the request message is used to request a PCC rule.
  • the first information is included in the PCC rules.
  • Step 502 The PCF entity sends a request response message to the SMF entity, where the request response message includes a PCC rule.
  • the SMF entity can also request the subscription data of the terminal from the UDM entity to obtain the first information.
  • the SMF entity can also request the subscription data of the terminal from the UDM entity to obtain the first information.
  • Step 503 Establish a preparation process of the PDU user plane resource.
  • Step 504 The (R) AN entity establishes an air interface resource for each flow included in the PDU session.
  • Step 505 The (R) AN entity generates a flow list according to the establishment result of the air interface resource of each flow in the PDU session, and sends an N2 message including the N2 session management information to the AMF entity.
  • the N2 session management information includes a flow list, where the flow list includes a flow in which the PDU session air interface resource establishment fails.
  • Step 506 The AMF entity sends an N11 message including the N2 session management information to the SMF entity.
  • Step 507 If the SMF entity determines that the default flow of the PDU session is in the flow list, and determines that the PDU session in the deactivated state is not allowed to be established according to the first information, triggering release of the PDU session.
  • the SMF entity may also send timing indication information to the terminal, where the timing indication information is used to indicate that the terminal initiates re-establishment of the PDU session after a preset timing duration.
  • the timing indication information may be located in the subscription data or the PCC rule of the terminal, or may be sent by the (R) AN entity to the SMF entity.
  • the SMF entity may also release the air interface resource of the stream in which the PDU session air interface resource is successfully established, thereby improving the utilization of the air interface resource.
  • Step 508 The SMF entity sends an IP-CAN session termination message to the PCF entity, where the message is used to indicate that the PDU session is released.
  • Step 509 The SMF entity sends an N4 session release request message to the UPF entity, where the N4 session release request message is used to delete the IP address/prefix allocated to the PDU session, and release the user plane resource of the PDU session.
  • Step 510 The SMF entity receives an N4 session release response message sent by the UPF entity.
  • Step 511 The SMF entity sends an N11 request message to the AMF entity.
  • the N11 request message includes N1 session management information, where the N1 session management information includes a PDU Session Release Command and timing indication information.
  • Step 512 The AMF entity sends an N2 resource release request message to the (R) AN entity, where the N2 resource release request message includes N1 session management information.
  • Step 513 The (R) AN entity transparently transmits the N1 session management information to the terminal, and releases the user plane resource of the PDU session.
  • Step 514 The (R) AN entity sends an N2 resource release confirmation message to the AMF entity, indicating that the user plane resource of the PDU session has been released.
  • Step 515 The AMF entity sends an N11 response message to the SMF entity, where the N11 response message includes an N2 resource release confirmation message.
  • Step 516 The SMF entity sends an N11 message to the AMF entity, to notify the AMF entity that the PDU session has been released.
  • step 507 if the SMF entity determines that the default flow of the PDU session is in the flow list, and determines that the PDU session in the deactivated state is not allowed to be established according to the first information, the SMF The entity triggers establishment of a user plane resource for the PDU session when it is determined that at least one flow of the air interface resource establishment is successful in the flow included in the PDU session. At this time, although the default flow of the PDU session is not established successfully, but the flow of the air interface resource is successfully established in the PDU session, the data can be successfully transmitted through the air interface resource.
  • the SMF entity determines that the default flow of the PDU session is in the flow list, and determines that the PDU session in the deactivated state is not allowed to be established according to the first information, the SMF entity notifies the PCF entity of the default flow of the flow.
  • the resource establishment fails, and receives the quality of service parameter of the default stream sent by the PCF entity.
  • the SMF entity forwards the obtained QoS parameter of the default stream to the AMF entity, and the AMF entity forwards the QoS parameter of the default stream to the (R) AN entity, and the (R) AN entity re-based the QoS parameter of the default stream.
  • the default stream establishes an air interface resource.
  • the state of the PDU session in the deactivated state is maintained, or will go The resource release of the active PDU session.
  • FIG. 6 it is a schematic flowchart of a session establishment method provided by an embodiment of the present application.
  • the first network device in the method shown in FIG. 6 may refer to an SMF entity, and the second network device may refer to a (R) AN entity.
  • the method includes:
  • Step 601 The first network device determines whether the air interface resource of the default flow of the PDU session is successfully established, and the PDU session is in a deactivated state.
  • Step 602 If the air interface resource of the default flow of the PDU session fails to be established, the first network device maintains the PDU session as a deactivated state or triggers release of the PDU session according to the first information. And indicating whether to maintain the PDU session as a deactivated state when the air interface resource establishment failure of the default flow of the PDU session fails.
  • the other content in the step 601 to the step 602, for example, the first information and the like, is the same as the definition or description in the step 201 to the step 202, and details are not described herein again.
  • the first network device may further obtain the second information or the third information.
  • the specific description of the second information and the third information may refer to the definition or description in step 201 to step 202. Let me repeat.
  • the embodiment of the present application provides a schematic diagram of a structure of a session establishing apparatus, where the session establishing apparatus can perform the actions of the first network device in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 700 includes a processing unit 701 and a transceiver unit 702.
  • the processing unit 701 is configured to determine whether the air interface resource of the default flow of the packet data unit PDU session is successfully established.
  • the transceiver unit 702 is configured to: when the air interface resource establishment failure of the default flow of the PDU session fails, establish the PDU session in a deactivated state according to the first information or trigger release of the PDU session; the first information is used to indicate Whether the PDU session in the deactivated state is allowed to be established when the establishment of the air interface resource of the default flow of the PDU session fails.
  • the transceiver unit 702 is specifically configured to:
  • the processing unit 701 is specifically configured to determine, according to the flow list, whether the air interface resource of the default flow of the PDU session is successfully established.
  • the first information is a slice/service type SST in the subscription data of the terminal corresponding to the PDU session;
  • the first information is a policy and a charging control rule of the terminal corresponding to the PDU session
  • the first information is indication information that is sent by the terminal to the device.
  • the transceiver unit 702 is further configured to:
  • the processing unit 701 is further configured to:
  • the transceiver unit is further configured to send the second indication information to the terminal, where the second indication information is used to indicate that the terminal activates the PDU session in a deactivated state at the time point.
  • the transceiver unit 702 is further configured to:
  • the processing unit 701 is further configured to:
  • the processing unit 701 is further configured to:
  • the processing unit 701 is further configured to:
  • the air interface resource of the stream in which the PDU session air interface resource is successfully established is released.
  • FIG. 8 a schematic diagram of a structure of a session establishing apparatus is provided in the embodiment of the present application.
  • the session establishing apparatus may perform the operations of the first network device in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 800 includes a processing unit 801 and a transceiver unit 802.
  • the processing unit 801 is configured to determine whether the air interface resource of the default flow of the packet data unit PDU session is successfully established, and the PDU session is in a deactivated state;
  • the transceiver unit 802 when the air interface resource for the default flow of the PDU session fails to be established, maintaining the PDU session as a deactivated state or triggering release of the PDU session according to the first information; the first information is used to indicate that Whether to maintain the PDU session as a deactivated state when the air interface resource of the default flow of the PDU session fails to be established.
  • FIG. 9 a schematic diagram of a structure of a session establishing apparatus is provided in the embodiment of the present application.
  • the session establishing apparatus may perform the actions of the terminal in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 900 includes a processing unit 901 and a transceiver unit 902.
  • the processing unit 901 is configured to generate first information, where the first information is used to indicate whether to establish the PDU session in the deactivated state when the air interface resource establishment failure of the default flow of the packet data unit PDU session fails;
  • the transceiver unit 902 is configured to send the first information to the first network device by using the second network device.
  • the PDU session is established as a deactivated state
  • the transceiver unit 902 is further configured to:
  • the embodiment of the present application provides a schematic diagram of a structure of a session establishing apparatus, where the session establishing apparatus can perform the actions of the first network device in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 1000 includes a processor 1001, a transceiver 1002, a memory 1003, and a communication interface 1004.
  • the processor 1001, the transceiver 1002, the memory 1003, and the communication interface 1004 are connected to each other through a bus 1005.
  • the processor 1001 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 1001 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 1003 may include a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory.
  • RAM random-access memory
  • non-volatile memory such as a flash memory.
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 1003 may also include a combination of the above types of memories.
  • the communication interface 1004 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the bus 1005 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 1003 can be used to store program instructions, and the processor 1001 invokes program instructions stored in the memory 1003 to perform one or more of the steps shown in the above scheme.
  • the processor 1001 is configured to determine whether the air interface resource of the default flow of the packet data unit PDU session is successfully established.
  • the transceiver 1002 is configured to: when the air interface resource establishment failure of the default flow of the PDU session fails, establish the PDU session in a deactivated state according to the first information or trigger release of the PDU session; the first information is used to indicate Whether the PDU session in the deactivated state is allowed to be established when the establishment of the air interface resource of the default flow of the PDU session fails.
  • the transceiver 1002 is specifically configured to:
  • the processor 1001 is specifically configured to determine, according to the flow list, whether an air interface resource of a default flow of the PDU session is successfully established.
  • the first information is a slice/service type SST in the subscription data of the terminal corresponding to the PDU session;
  • the first information is a policy and a charging control rule of the terminal corresponding to the PDU session
  • the first information is indication information that is sent by the terminal to the device.
  • the transceiver 1002 is further configured to:
  • the processor 1001 is further configured to:
  • the transceiver is further configured to send the second indication information to the terminal, where the second indication information is used to indicate that the terminal activates the PDU session in a deactivated state at the time point.
  • the transceiver 1002 is further configured to:
  • the processor 1001 is further configured to:
  • the processor 1001 is further configured to:
  • the processor 1001 is further configured to:
  • the air interface resource of the stream in which the PDU session air interface resource is successfully established is released.
  • FIG. 11 a schematic diagram of a structure of a session establishing apparatus is provided in the embodiment of the present application.
  • the session establishing apparatus may perform the operations of the first network device in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 1100 includes a processor 1101, a transceiver 1102, a memory 1103, and a communication interface 1104.
  • the processor 1101, the transceiver 1102, the memory 1103, and the communication interface 1104 are connected to each other through a bus 1105.
  • the specific content of the foregoing module may be Referring to the description of related modules in FIG. 10, details are not described herein again.
  • the processor 1101 is configured to determine whether the air interface resource of the default flow of the packet data unit PDU session is successfully established, and the PDU session is in a deactivated state;
  • the transceiver 1102 when the air interface resource for the default flow of the PDU session fails to be established, maintaining the PDU session as a deactivated state or triggering release of the PDU session according to the first information; the first information is used to indicate that Whether to maintain the PDU session as a deactivated state when the air interface resource of the default flow of the PDU session fails to be established.
  • a schematic diagram of a structure of a session establishing apparatus is provided in the embodiment of the present application.
  • the session establishing apparatus may perform the actions of the terminal in the foregoing method embodiments.
  • the session establishing device may be referred to as an SMF entity
  • the second network device may be referred to as an (R) AN entity.
  • the session establishing apparatus 1200 includes: a processor 1201, a transceiver 1202, a memory 1203, and a communication interface 1204.
  • the processor 1201, the transceiver 1202, the memory 1203, and the communication interface 1204 are connected to each other through a bus 1205.
  • the specific content of the foregoing module may be Referring to the description of related modules in FIG. 10, details are not described herein again.
  • the processor 1201 is configured to generate first information, where the first information is used to indicate whether to establish the PDU session in a deactivated state when the air interface resource establishment failure of the default flow of the packet data unit PDU session fails;
  • the transceiver 1202 is configured to send the first information to the first network device by using the second network device.
  • the PDU session is established as a deactivated state
  • the transceiver 1202 is further configured to:
  • the embodiment of the present application further provides a computer readable storage medium for storing computer software instructions required to execute the foregoing processor, which includes a program for executing the above-mentioned processor.
  • the embodiment of the present application provides a computer program product that, when the computer reads and executes the computer program product, causes the computer to perform the method in any of the above possible designs.
  • the embodiment of the present application provides a chip connected to a memory for reading and executing a software program stored in the memory to implement the method in any of the above possible designs.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种会话建立方法及装置，其中方法包括：第一网络设备判断PDU会话的默认流的空口资源是否建立成功；若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。

Description

一种会话建立方法及装置
本申请要求在2017年9月8日提交国家专利局、申请号为201710806432.5、发明名称为“一种会话建立方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种会话建立方法及装置。
背景技术
分组数据单元(Packet Data Unit，PDU)会话是终端和数据网络(Data Network，DN)之间的会话，用以提供PDU连接性服务。PDU连接性服务，是指提供终端和由数据网络名称(Data Network Name，DNN)确定的DN之间PDU交换的服务。
无线通信系统中，数据的传输是基于无线承载(Resource Bearer，RB)的，无线通信系统按照各种应用的服务质量(Quality of Service，QoS)需求，将数据划分成一个或多个RB。一个RB可以划分为多个QoS流(flow)，以下均简称为流或flow。一个PDU会话中包括至少一个flow，其中一个flow为默认(default)flow。默认flow是指通过默认QoS规则来进行处理的flow。默认QoS规则是PDU会话中仅有的可能不包含分组过滤器(packet filter)的QoS规则。
PDU会话在建立时，基站会为PDU会话所包括的每个flow建立相应的空口资源，每个flow的空口资源分别独立建立。为QoS Flow建立空口资源的过程可能成功也可能失败。在PDU会话用户面资源建立过程中，PDU会话的默认flow的空口资源建立成功，标志着该PDU会话已经建立成功；相应的，如果PDU会话的默认flow的空口资源建立失败，标志着该PDU会话未建立成功。
在未来的5G通信系统中，当PDU会话的默认flow的空口资源建立失败时，如何对PDU会话进行处理，还没有一个明确的解决方案。
发明内容
本申请提供一种会话建立方法及装置，用以提供一种建立PDU会话的处理方法。
第一方面，本申请实施例提供了一种会话建立方法，该方法包括：
第一网络设备判断PDU会话的默认流的空口资源是否建立成功；
若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
根据上述方法，第一网络设备在确定所述PDU会话的默认流的空口资源建立失败时，可以建立去激活态的所述PDU会话或触发释放所述PDU会话，从而提供了在PDU会话的默认流的空口资源建立失败的情况下，对PDU会话进行进一步的处理机制，解决了如 何确定建立去激活态的PDU会话的问题。
第二方面，本申请实施例提供了一种会话建立方法，该方法包括：
第一网络设备判断PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
根据上述方法，第一网络设备在确定处于去激活态的PDU会话的默认流的空口资源建立失败时，可以维持去激活态的所述PDU会话或触发释放去激活态的所述PDU会话，从而提供了在去激活态的PDU会话的默认流的空口资源建立失败的情况下，对去激活态的PDU会话进行进一步的处理机制，解决了如何确定是否维持去激活态的PDU会话的问题。
可选的，所述第一网络设备判断PDU会话的默认流的空口资源是否建立成功，包括：
所述第一网络设备获取流列表，所述流列表为第二网络设备根据PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流；
所述第一网络设备根据所述流列表判断PDU会话的默认流的空口资源是否建立成功。
根据上述方法，第一网络设备通过包括所述PDU会话中空口资源建立失败的流的流列表，可以快速、准确的确定PDU会话的默认流的空口资源的建立结果，从而提高判断PDU会话的默认流的空口资源是否建立成功的准确性。
可选的，所述第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型；
或者，所述第一信息为所述PDU会话对应的终端的策略与计费控制规则；
或者，所述第一信息为所述终端发送给所述第一网络设备的指示信息。
可选的，所述方法还包括：
所述第一网络设备获取第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
所述根据第一信息建立去激活态的所述PDU会话之后，所述方法还包括：
所述第一网络设备在所述第二信息指示的时间点激活去激活态的所述PDU会话；
或者，所述第一网络设备将所述第二指示信息发送给所述终端，所述第二指示信息用于指示所述终端在所述时间点激活去激活态的所述PDU会话。
通过上述方法，第一网络设备在第二信息指示的时间点激活去激活态的所述PDU会话，可以节省建立PDU会话的时间和网络资源，相对于重新建立PDU会话而言，可以提高PDU会话建立的效率，使得PDU会话的用户面资源能够更快的建立起来。
可选的，所述方法还包括：
所述第一网络设备获取第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数；
所述第一网络设备在所述第二信息指示的时间点激活去激活态的所述PDU会话之后，还包括：
所述第一网络设备若确定所述去激活态的所述PDU会话的被激活次数等于所述最大次数，则触发释放所述PDU会话的流程。
可选的，所述第一网络设备确定所述PDU会话的默认流的空口资源建立失败之后， 所述方法还包括：
所述第一网络设备若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源；
或者，所述第一网络设备若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则所述第一网络设备向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
通过上述方法，第一网络设备可以在PDU会话的默认流的空口资源建立失败时，继续为所述PDU会话建立用户面资源，从而使得PDU会话的用户面资源能够更快的建立起来。
可选的，所述根据第一信息建立去激活态的所述PDU会话之后，所述方法还包括：
所述第一网络设备将所述PDU会话中空口资源建立成功的流的空口资源释放。
通过上述方法，第一网络设备将所述PDU会话中空口资源建立成功的流的空口资源释放，可以将释放的资源重新利用，从而提高资源利用率。
第三方面，本申请实施例提供一种会话建立装置，所述通信装置包括存储器、收发机和处理器，其中：存储器用于存储指令；处理器用于根据执行存储器存储的指令，并控制收发机进行信号接收和信号发送，当处理器执行存储器存储的指令时，终端用于执行上述第一方面或第二方面中任一种可能的设计中的方法。
第四方面，本申请实施例提供一种会话建立装置，用于实现上述第一方面或第二方面中的任意一种方法，包括相应的功能模块，例如包括处理单元、接收单元、发送单元等，分别用于实现以上方法中的步骤。
第五方面，本申请实施例提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第一方面或第二方面中任一种可能的设计中的方法。
第六方面，本申请实施例提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面或第二方面中任一种可能的设计中的方法。
第七方面，本申请实施例提供一种芯片，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面或第二方面中任一种可能的设计中的方法。
第八方面，本申请实施例提供了一种会话建立方法，包括：
终端生成第一信息，所述第一信息用于指示在PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话；
所述终端通过第二网络设备向第一网络设备发送第一信息。
通过上述方法，终端通过向第一网络设备发送第一信息，指示出是否允许建立去激活态的PDU会话，从而使得第一网络设备在确定PDU会话的默认流的空口资源建立失败时，可以建立去激活态的PDU会话，从而提供了在PDU会话的默认流的空口资源建立失败的情况下，对PDU会话进行进一步的处理机制。
可选的，所述PDU会话被建立为去激活态；
所述方法还包括：
所述终端接收所述第一网络设备通过所述第二网络设备发送的第二指示信息；所述第 二信息用于指示激活去激活态的所述PDU会话的时间点；
所述终端在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。
第九方面，本申请实施例提供一种会话建立装置，所述通信装置包括存储器、收发机和处理器，其中：存储器用于存储指令；处理器用于根据执行存储器存储的指令，并控制收发机进行信号接收和信号发送，当处理器执行存储器存储的指令时，终端用于执行上述第八方面中任一种可能的设计中的方法。
第十方面，本申请实施例提供一种会话建立装置，用于实现上述第八方面中的任意一种方法，包括相应的功能模块，例如包括处理单元、接收单元、发送单元等，分别用于实现以上方法中的步骤。
第十一方面，本申请实施例提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第八方面中任一种可能的设计中的方法。
第十二方面，本申请实施例提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第八方面中任一种可能的设计中的方法。
第十三方面，本申请实施例提供一种芯片，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述第八方面中任一种可能的设计中的方法。
附图说明
图1为适用于本申请实施例的一种系统架构示意图；
图2为本申请实施例提供的一种会话建立方法流程示意图；
图3为本申请实施例提供的一种建立PDU会话用户面的流程示意图；
图4为本申请实施例提供的一种建立PDU会话用户面的流程示意图；
图5为本申请实施例提供的一种PDU会话释放流程示意图；
图6为本申请实施例提供的一种会话建立方法流程示意图；
图7为本申请实施例提供的一种会话建立装置示意图；
图8为本申请实施例提供的一种会话建立装置示意图；
图9为本申请实施例提供的一种会话建立装置示意图；
图10为本申请实施例提供的一种会话建立装置示意图；
图11为本申请实施例提供的一种会话建立装置示意图；
图12为本申请实施例提供的一种会话建立装置示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
图1示例性示出了适用于本申请实施例的一种系统架构示意图，如图1所示，在未来的5G系统架构中，终端101可以经接入网实体102与核心网进行通信，终端可以指用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线 本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端等。图1中为方便描述，只示例出1个终端，实际网络中，可能存在多个终端共存，在此不再赘述。
接入网(Access Network，AN)实体102，接入网实体也可以称之为无线接入网((Radio)Access Network，(R)AN)实体，以下统称为接入网实体或(R)AN实体，主要负责为终端101提供无线连接，保证终端101的上下行数据的可靠传输等。接入网实体102可为5G系统中的gNB(generation Node B)，可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)等。
会话管理功能(Session Management Function，SMF)实体103，该实体可以用于执行LTE系统中移动性管理实体(Mobility Management Entity，MME)的部分功能，主要负责为终端101建立会话、管理会话等。可以根据终端101的位置信息为终端101选择合适的用户面功能(User Plane Function，UPF)实体。
用户面功能实体104，是终端101用户面的功能网元，主要功能包括分组路由和转发，用户面数据的服务质量(Quality of Service，QoS)处理等。
接入和移动性管理(Access and Mobility Management Function,AMF)实体105，主要功能包括无线接入网络控制平面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等等。
策略控制功能(Policy Control Funtion，PCF)实体106，主要负责用户面传输路径的建立、释放和更改等功能。
鉴权服务器功能(Authentication Server Function，AUSF)实体107，其主要功能包括用户鉴权等。
用户数据管理(User Data Management，UDM)实体108，主要负责管理用户的签约数据等。
数据网络(Data Network，DN)109可以是指为终端101提供服务的网络，比如有些DN可以为终端101提供上网功能，有些DN可以为终端101提供彩信功能。
PDU会话是终端和DN之间的连接，提供PDU连接性服务。终端可以建立多个PDU会话，来连接到相同的DN或者不同的DN。终端也可以建立由不同的UPF提供服务的PDU会话，来连接到相同的DN。
PDU会话的状态至少包括激活态(active)和非激活态(Inactive或de-activted)。
其中，激活态是指PDU会话的用户面资源已经建立起来的状态，终端和DN之间建立了端到端的连接，可以通过PDU会话传递数据。非激活态是指PDU会话仅保留部分用户面资源，但是终端和(R)AN实体之间的用户面空口资源，以及(R)AN实体和UPF实体之间的连接都没有建立起来，终端和DN之间不能传递数据，但SMF实体和UPF实体中仍保留PDU会话的部分信息。
PDU会话建立流程一般分为三个部分：第一部分，PDU会话的用户面资源的准备流程；第二部分，建立PDU会话的空口资源；第三部分，PDU会话的后续流程，例如在PDU 会后建立完成后，(R)AN实体向UPF实体发送(R)AN实体的端口号等流程，从而完成对建立完成的PDU会话的确认。
本申请实施例主要涉及第二部分，即建立PDU会话的空口资源，下面详细描述。
图1中还示出了各个实体中的接口的可能实现方式，比如接入网实体102和AMF实体109之间的N2接口，接入网实体102与UPF实体104之间的N9接口等等，在此不再一一赘述。
结合前面的描述，如图2所示，为本申请实施例提供的一种会话建立方法流程示意图。图2所示的方法中的第一网络设备可以是指SMF实体，第二网络设备可以是指(R)AN实体。
参见图2，该方法包括：
步骤201：第一网络设备判断PDU会话的默认流的空口资源是否建立成功。
需要说明的是，所述PDU会话可以为新发起建立的PDU会话，也可以为处于去激活态的会话。所述PDU会话为处于去激活态的PDU会话时，终端需要通过服务请求(Service Request)信息激活去激活态的所述PDU会话。
步骤202：若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
本申请实施例中，所述PDU会话为新发起建立的PDU会话时，根据第一信息建立去激活态的所述PDU会话，可以是指将新发起建立的PDU会话建立为去激活态；所述PDU会话为处于去激活态的会话时，根据第一信息建立去激活态的所述PDU会话，可以是指将去激活态的所述PDU会话保持为去激活态。
步骤202之前，第一网络设备可以从UDM实体或PCF实体获取第一信息。
本申请实施例中，第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
第一信息可以有多种形式，一种可能的实现方式中，所述第一信息可以为所述PDU会话对应的终端的签约数据中的切片/业务类型(Slice/Service Types,SST)。
第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型时，第一信息可以通过指示终端请求的PDU会话是否可以建立为去激活态。例如，PDU会话所属切片的SST为海量物联网(massive IoT(Internet of Things)，MIoT)时，第一信息指示允许将该PDU会话建立为去激活态；PDU会话所属切片的SST为IP多媒体子系统(Multimedia Subsystem，IMS)类型时，第一信息指示不允许将该PDU会话建立为去激活态。
一种可能的实现方式中，所述第一信息可以为所述PDU会话对应的终端的策略与计费控制(Policy and Charging Control，PCC)规则。相应的，第一信息为从PCF实体获取的PCC规则时，所述PCC规则可以在PDU会话所属切片的切片/业务类型(Slice/Service Types,SST)为高可靠性低时延(ultra-reliable low latency communications，URLLC)时，指示不允许将该PDU会话建立为去激活态；PDU会话所属切片的SST为海量物联网(massive IoT(Internet of Things)，MIoT)时，指示允许将该PDU会话建立为去激活态；PDU会话所属切片的SST为IP多媒体子系统(Multimedia Subsystem，IMS)类型时，指示不允许将该PDU会话建立为去激活态。
一种可能的实现方式中，所述第一信息也可以是终端发送给所述第一网络设备的指示信息。终端在建立PDU会话之前，生成第一信息，并通过第二网络设备向第一网络设备发送所述第一信息，终端从而可以通过第一信息指示PDU会话是否可以建立为去激活态。
第一信息是由终端发送给第一网络设备时，终端先将第一信息发送给第二网络设备，第二网络设备再转发给第一网络设备。此时，第一信息可以位于终端向第二网络设备发送的PDU会话建立请求或PDU会话用户面资源建立请求中，还可以位于向第二网络设备发送的服务请求(Service Request)或切换请求(Handover Request)中，本申请实施例对此并不限定，终端可以根据实际情况确定携带第一信息的消息。
本申请实施例中，第一信息也可以是由第一网络设备配置的本地策略，例如，所述本地策略可以为PDU会话所属切片的SST为URLLC时，可以指示不允许将该PDU会话建立为去激活态；PDU会话所属切片的SST为MIoT时，可以指示允许将该PDU会话建立为去激活态；PDU会话所属切片的SST为IMS类型时，可以指示不允许将该PDU会话建立为去激活态。
需要说明的是，第一信息也可以是其他形式，在此不再赘述。
第一网络设备获取第一信息之后，终端可以触发PDU会话的建立流程，或者网络侧主动为终端建立PDU会话，此时需要触发PDU会话的用户面资源的准备流程，该流程的具体内容，本申请实施例对此并不限定，在此不再赘述。
PDU会话的用户面资源的准备流程之后，需要建立PDU会话的空口资源。PDU会话的用户面资源，可以分为两部分，终端和(R)AN实体之间的空口资源，以及(R)AN实体到DN之间的网络侧资源。
第二网络设备，根据PDU会话中的每个流所需的QoS档案(profile)等参数，分别为PDU会话中的每个流建立空口资源。一个PDU会话中包括至少一个流，其中一个流为默认流。默认流是指通过默认QoS规则来进行处理的流。默认QoS规则是PDU会话中仅有的、可能不包含分组过滤器的QoS规则。PDU会话的默认流的空口资源若建立失败，则标志着PDU会话建立失败。PDU会话的默认流的空口资源若建立成功，即使PDU会话所包括的其他流的空口资源建立失败，PDU会话也可以认为建立成功。
(R)AN实体会为PDU会话的每个流建立相应的空口资源，从而实现为PDU会话建立用户面资源。为每个流建立空口资源的过程可能成功也可能失败。如果为某个流建立空口资源的过程失败，那么该流无法传递数据。
在PDU会话用户面资源建立过程中，第二网络设备会将为每个流建立空口资源成功或失败的结果反馈给网络侧，即将流列表发送给第一网络设备。所述流列表包括的流，就是第二网络设备为所述PDU会话中的流建立空口资源时，空口资源建立失败的流。所述流列表也可以称为被拒绝的QoS流列表(List of rejected QoS Flows)，或称为被激活的PDU会话中被拒绝的QoS流的列表(List of rejected QoS Flows for the PDU Sessions activated)。
步骤201中，第一网络设备可以先获取流列表，并根据所述流列表判断PDU会话的默认流的空口资源是否建立成功。其中，所述流列表为第二网络设备根据PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流。
第一网络设备获取到的流列表，是第二网络设备通过AMF实体等实体发送给第一网络设备的。
举例来说，第二网络设备向AMF实体发送包括N2会话管理(Session management， SM)信息(information)的N2消息，其中，N2会话管理信息中包括PDU会话标识、AN隧道信息、被激活的PDU会话中被接受的QoS流的列表(List of accepted QoS Flows for the PDU Sessions activated)、所述流列表等信息。其中，N2消息中还可以包括以下一项或多项：PDU会话标识，建立失败原因，N2会话管理(Session management，SM)信息(information)等。
AMF实体再向第一网络设备发送包括N2会话管理信息的N11消息，第一网络设备接收到所述N11消息之后，可以获取所述流列表。
再举例来说，在归属地漫游(home routed)场景下，终端从归属地公共陆地移动网络(Home-Public Land Mobile Network，H-PLMN)漫游到拜访地公共陆地移动网络(Visited-PLMN,V-PLMN)，终端从由第一网络设备服务，改为由第三网络设备服务，第三网络设备和第一网络设备均为SMF实体。此场景下，第二网络设备向AMF实体发送包括流列表的N2消息，AMF实体再向第三网络设备发送包括流列表的N11消息，第三网络设备再向第一网络设备发送包括流列表的N16消息，第一网络设备接收到所述N16消息之后，可以获取所述流列表。
第一网络设备获取到流列表之后，可以确定PDU会话中每个流的空口资源是否建立成功。
步骤202中，第一网络设备若确定所述PDU会话的默认流不位于所述流列表中，则可以认为PDU会话建立成功，则执行后续的流程。
相应的，第一网络设备若确定所述PDU会话的默认流位于所述流列表中，则可以认为所述PDU会话的默认流的空口资源建立失败。此时，第一网络设备可以建立去激活态的所述PDU会话或触发释放所述PDU会话。
具体的，第一网络设备可以根据第一信息确定是否允许建立去激活态的所述PDU会话或触发释放所述PDU会话。其中，所述第一网络设备若根据所述第一信息确定允许建立去激活态的所述PDU会话，则可以建立去激活态的所述PDU会话；相应的，所述第一网络设备若根据所述第一信息确定所述PDU会话不允许建立去激活态的所述PDU会话，则触发释放所述PDU会话。
可选的，第一网络设备建立去激活态的所述PDU会话的同时，可以将所述PDU会话中空口资源建立成功的流的空口资源释放，从而避免去激活态的PDU会话占用过多资源。
所述第一网络设备具体可以通过以下步骤建立去激活态的所述PDU会话：
步骤一：第一网络设备向PCF实体发送互联网协议连接接入网(Internet Protocol-Connectivity Access Network，IP-CAN)会话修正(Session Modification)消息，该消息用于指示PDU会话建立为去激活态。
步骤二：第一网络设备向UPF实体发送N4会话更新请求(Session update request)消息，该请求消息用于指示PDU会话建立为去激活态。
相应的，第一网络设备会接收到UPF实体发送的N4会话更新响应(Session update response)消息。
步骤三：第一网络设备向AMF实体发送N11消息响应(Message Response)；N11消息响应用于指示PDU会话建立为去激活态，该消息中包括SM非接入层(Non-access stratum，NAS)消息。
步骤四：AMF实体向第二网络设备发送N2消息响应,N2消息响应用于指示PDU会 话建立为去激活态，该消息中包括SM非接入层(Non-access stratum，NAS)消息。
步骤五：第二网络设备将N2消息响应中的SM NAS消息透传给终端,SM NAS消息用于指示PDU会话建立为去激活态，终端根据此消息同步PDU会话状态。
可选的，第二网络设备还可以向第一网络设备发送第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点。所述第二信息可以与流列表在同一个消息中发送给第一网络设备。
相应的，所述第一网络设备获取所述第二信息之后，在所述第二信息指示的时间点激活去激活态的所述PDU会话。第二信息可以指示的是定时器的定时时长，第一网络设备接收到第二信息之后，根据第二信息指示的定时时长设置定时器，并在定时器超时时，激活去激活态的所述PDU会话。
可选的，第一网络设备还可以通过第二网络设备向终端发送第二指示信息。终端从而可以在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。所述激活请求消息可以为服务请求(Service Request)等，本申请实施例对此并不限定。
进一步的，签约数据或PCC规则中还可以包括第三信息。当第一网络设备获取第一信息的同时，还可以获取到第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数。
所述第一网络设备在确定所述PDU会话的默认流位于所述流列表中，并建立去激活态的所述PDU会话之后，可能会重新激活去激活态的所述PDU会话。所述第一网络设备获取第三信息之后，若确定去激活态的所述PDU会话的被激活次数等于所述最大次数，步则不再激活去激活态的所述PDU会话，而是触发释放所述PDU会话。
本申请实施例中，所述第一网络设备若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则可以执行以下任意一个流程：
流程1：第一网络设备在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源。此时，虽然PDU会话的默认流未建立成功，但是PDU会话中存在空口资源建立成功的流，因此可以通过空口资源建立成功的流传递数据。
流程2：所述第一网络设备向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
第一网络设备发送的默认流的服务质量参数是PCF实体获取到的。具体的，默认流的空口资源建立失败之后，第一网络设备通知PCF实体默认流的空口资源建立失败，此时，PCF实体重新调整默认流的服务质量参数，并将调整后的默认流的服务质量参数发送给第一网络设备，第一网络设备将获得的默认流的服务质量参数转发给AMF实体，AMF实体再将默认流的服务质量参数转发给第二网络设备，第二网络设备从而根据该默认流的服务质量参数重新为默认流建立空口资源。
默认流的空口资源未建立成功的原因，可能是因为第二网络设备建立所述默认流时所使用的服务质量参数对应的服务质量较高，第二网络设备无法分配满足要求的空口资源，还可能是因为第二网络设备运行故障，即Error Case，导致第二网络设备无法分配空口资源。当然，默认流的空口资源未建立成功的原因还有其他可能，在此不再逐一举例说明。第一网络设备发送的服务质量参数对应的服务质量比第二网络设备建立所述默认流时所 使用的服务质量参数对应的服务质量差，因此第二网络设备根据第一网络设备发送的所述默认流的服务质量参数，为所述默认流建立空口资源成功的概率比较大，从而实现建立PDU会话。
流程3：所述第一网络设备触发释放所述PDU会话的流程。
进一步的，在该流程中，所述第一网络设备还可以将所述PDU会话中空口资源建立成功的流的空口资源释放，从而提高空口资源的利用率。
需要说明的是，第二网络设备也可以通知第一网络设备具体执行上述流程1至流程3中的一个流程，也可以通过其他方式确定需要执行的流程，本申请实施例对此并不限定。
下面结合具体的实施例描述前面的过程。
如图3所示，为本申请实施例提供的一种建立PDU会话用户面的流程示意图。
图3所示的流程中，第一网络设备为SMF实体，第二网络设备为(R)AN实体。
步骤301a：SMF实体向UDM发送请求消息，所述请求消息用于请求终端的签约数据。
签约数据中包括第一信息。
可选的，签约数据中还包括第三信息。
步骤302a：UDM实体向SMF实体发送请求响应消息，所述请求响应消息中包括签约数据或PCC规则。
可选的，步骤301a以及步骤302a还可以替换为步骤301b以及步骤302b：
步骤301b：SMF实体向PCF实体发送请求消息，所述请求消息用于请求PCC规则。
PCC规则中包括第一信息。
可选的，PCC规则中还包括第三信息。
步骤302b：PCF实体向SMF实体发送请求响应消息，所述请求响应消息中包括PCC规则。
步骤303：建立PDU用户面资源的准备流程。
该步骤的具体过程，本申请实施例对此并不限定，在此不再赘述。
步骤304：(R)AN实体为PDU会话中所包括的每个流建立空口资源。
具体如何建立空口资源，本申请实施例对此并不限定，在此不再赘述。
步骤305：(R)AN实体根据PDU会话中每个流的空口资源的建立结果生成流列表，并向AMF实体发送包括N2会话管理信息的N2消息。N2会话管理信息中包括流列表，所述流列表包括所述PDU会话中空口资源建立失败的流。
可选的，N2消息中还包括第二信息。
N2消息中还可以包括以下一项或多项：PDU会话标识，建立失败原因。
步骤306：AMF实体向SMF实体发送包括所述N2会话管理信息的N11消息。
步骤307：SMF实体若确定所述PDU会话的默认流位于所述流列表中，且根据所述第一信息确定所述PDU会话允许建立为去激活态，则触发建立去激活态的所述PDU会话。
步骤308：SMF实体向PCF实体发送IP-CAN会话修正消息，该消息用于指示PDU会话建立为去激活态。如果PCF实体中有与去激活态的PDU会话相关的策略，PCF实体则会将所述相关的策略发给SMF实体。
步骤309：SMF实体向UPF实体发送N4会话建立或修改请求(N4Session establishment/modificationrequest)消息，该请求消息如果是N4Session establishment请求消息，则SMF实体指示UPF实体缓存下行数据并发送下行数据通知(Downlink Data  Notification，DDN)消息，而且不会将(R)AN实体的端口号发送给UPF实体。该请求消息如果是N4 Session modification请求消息，SMF实体可能根据需要对UPF实体上的参数进行更新。
用于指示PDU会话建立为去激活态。
步骤310：SMF实体接收UPF实体发送的N4会话更新响应消息。
步骤311：SMF实体向AMF实体发送N11消息响应；N11消息响应用于指示PDU会话建立为去激活态，该消息中包括SM非接入层消息。在该N11消息响中也可以包括第一信息，如果AMF实体中维护PDU会话的状态，AMF实体可以根据所述第一信息将此PDU会话标记为去激活态。
步骤312：AMF实体向(R)AN实体发送N2消息响应,N2消息响应用于指示PDU会话建立为去激活态，该消息中包括SM非接入层(Non-access stratum，NAS)消息。
步骤313：(R)AN实体接收到N2消息响应之后，会删除与该PDU会话相关的资源。同时(R)AN实体将N2消息响应中的SM NAS消息透传给终端,SM NAS消息用于指示PDU会话建立为去激活态，终端根据此消息同步PDU会话状态。
可选的，N2消息中包括第二信息时，步骤314：SMF实体在所述第二信息指示的时间点激活去激活态的所述PDU会话。SMF实体也可以将第二信息发送给终端，由终端根据第二信息设置定时器，从而由终端在第二信息指示的时间点激活去激活态的所述PDU会话。
可选的，签约数据或PCC规则中包括第三信息时，SMF实体若确定激活去激活态的所述PDU会话的次数等于所述第三信息指示的最大次数，则不再激活去激活态的所述PDU会话，而是触发释放所述PDU会话。
SMF实体具体如何激活去激活态的所述PDU会话，本申请实施例对此并不限定，在此不再赘述。
上述流程中，SMF实体在获取到流列表之后，若确定所述PDU会话的默认流位于所述流列表中，则可以建立去激活态的所述PDU会话，则可以在合适的时间为所述PDU会话再建立空口资源，相比于重新建立PDU会话，激活去激活态的PDU会话能够节省时间和信令，使PDU会话用户面资源能够较快的建立起来，从而提高系统效率。
如图4所示，为本申请实施例提供的一种建立PDU会话用户面的流程示意图。
图4的流程为home routed的场景。终端从H-PLMN中的第一网络设备漫游到V-PLMN中的第三网络设备，第三网络设备和第一网络设备均为SMF实体，为了描述方便，将第一网络设备称为H-SMF实体，第三网络设备称为V-SMF实体，第二网络设备称为(R)AN实体。
步骤401a：H-SMF实体向UDM实体发送请求消息，所述请求消息用于请求终端的签约数据。
签约数据中包括第一信息。
步骤402a：UDM实体或PCF实体向SMF实体发送请求响应消息，所述请求响应消息中包括签约数据或PCC规则。
可选的，步骤401a以及步骤402a还可以替换为步骤401b以及步骤402b：
步骤401b：H-SMF实体向PCF实体发送请求消息，所述请求消息用于请求PCC规则。
PCC规则中包括第一信息。
步骤402b：PCF实体向H-SMF实体发送请求响应消息，所述请求响应消息中包括PCC规则。
步骤403：建立PDU用户面资源的准备流程。
该步骤的具体过程，本申请实施例对此并不限定，在此不再赘述。
步骤404：(R)AN实体为PDU会话中所包括的每个流建立空口资源。
步骤405：(R)AN实体根据PDU会话中每个流的空口资源的建立结果生成流列表，并向AMF实体发送包括N2会话管理信息的N2消息。N2会话管理信息中包括流列表，所述流列表包括所述PDU会话中空口资源建立失败的流。
可选的，N2消息中还包括第二信息。
N2消息中还可以包括以下一项或多项：PDU会话标识，建立失败原因。
步骤406：AMF实体向V-SMF实体发送包括所述N2会话管理信息的N11消息。
步骤407：V-SMF实体向H-SMF实体发送包括所述N2会话管理信息的N16消息。
步骤408：H-SMF实体若确定所述PDU会话的默认流位于所述流列表中，且根据所述第一信息确定所述PDU会话允许建立为去激活态，则触发建立去激活态的所述PDU会话。
步骤409：H-SMF实体向PCF实体发送IP-CAN会话修正消息，该消息用于指示PDU会话建立为去激活态。如果PCF实体中有与去激活态的PDU会话相关的策略，PCF实体则会将所述相关的测量发给H-SMF实体。
步骤410：H-SMF实体向V-SMF实体发送N16消息响应，用于指示PDU会话建立为去激活态。
步骤411：V-SMF实体向UPF实体发送N4会话建立或修改请求消息，该请求消息用于指示PDU会话建立为去激活态。该请求消息如果是N4 Session establishment请求消息，则SMF实体指示UPF实体缓存下行数据并发送下行数据通知消息，而且不会将(R)AN实体的端口号发送给UPF实体。该请求消息如果是N4 Session modification请求消息，SMF实体可能根据需要对UPF实体上的参数进行更新。
步骤412：V-SMF实体接收UPF实体发送的N4会话更新响应消息。
步骤413：V-SMF实体向AMF实体发送N11消息响应；N11消息响应用于指示PDU会话建立为去激活态，该消息中包括SM非接入层消息。
步骤414：AMF实体向(R)AN实体发送N2消息响应,N2消息响应用于指示PDU会话建立为去激活态，该消息中包括SM非接入层(Non-access stratum，NAS)消息。
步骤415：(R)AN实体接收到N2消息响应之后，会删除与该PDU会话相关的资源。同时(R)AN实体将N2消息响应中的SM NAS消息透传给终端,SM NAS消息用于指示PDU会话建立为去激活态，终端根据此消息同步PDU会话状态。
可选的，N2消息中包括第二信息时，步骤416：H-SMF实体在所述第二信息指示的时间点激活去激活态的所述PDU会话。
可选的，签约数据或PCC规则中包括第三信息时，H-SMF实体若确定激活去激活态的所述PDU会话的次数等于所述第三信息指示的最大次数，则不再激活去激活态的所述PDU会话，而是触发释放所述PDU会话。
SMF实体具体如何激活去激活态的所述PDU会话，本申请实施例对此并不限定，在此不再赘述。
上述流程中，在获取到流列表之后，若确定所述PDU会话的默认流位于所述流列表中，则可以建立去激活态的所述PDU会话，则可以在合适的时间为所述PDU会话再建立空口资源，相比于重新建立PDU会话，激活去激活态的PDU会话能够节省时间和信令，使PDU会话用户面资源能够较快的建立起来，从而提高系统效率。
如图5所示，为本申请实施例提供的一种PDU会话释放流程示意图。
图5所示的流程中，第一网络设备为SMF实体，第二网络设备为(R)AN实体。
步骤501：SMF实体向PCF实体发送请求消息，所述请求消息用于请求PCC规则。
PCC规则中包括第一信息。
步骤502：PCF实体向SMF实体发送请求响应消息，所述请求响应消息中包括PCC规则。
当然SMF实体还可以向UDM实体请求终端的签约数据，从而获得第一信息，具体可以参考前面的描述，在此不再赘述。
步骤503：建立PDU用户面资源的准备流程。
该步骤的具体过程，本申请实施例对此并不限定，在此不再赘述。
步骤504：(R)AN实体为PDU会话中所包括的每个流建立空口资源。
具体如何建立空口资源，本申请实施例对此并不限定，在此不再赘述。
步骤505：(R)AN实体根据PDU会话中每个流的空口资源的建立结果生成流列表，并向AMF实体发送包括N2会话管理信息的N2消息。N2会话管理信息中包括流列表，所述流列表包括所述PDU会话中空口资源建立失败的流。
步骤506：AMF实体向SMF实体发送包括所述N2会话管理信息的N11消息。
步骤507：SMF实体若确定所述PDU会话的默认流位于所述流列表中，且根据所述第一信息确定不允许建立去激活态的所述PDU会话，则触发释放所述PDU会话。
SMF实体还可以向终端发送定时指示信息，定时指示信息用于指示终端在预设定时时长之后发起重新建立所述PDU会话。
所述定时指示信息可以是位于所述终端的签约数据或PCC规则中的，也可以是由(R)AN实体发送给所述SMF实体的。
进一步的，SMF实体还可以将所述PDU会话中空口资源建立成功的流的空口资源释放，从而提高空口资源的利用率。
步骤508：SMF实体向PCF实体发送IP-CAN会话终结消息，该消息用于指示释放所述PDU会话。
步骤509：SMF实体向UPF实体发送N4会话释放请求消息，该N4会话释放请求消息用于指示删除分配给所述PDU会话的IP地址/前缀，并释放所述PDU会话的用户面资源。
步骤510：SMF实体接收UPF实体发送的N4会话释放响应消息。
步骤511：SMF实体向AMF实体发送N11请求消息；N11请求消息中包括N1会话管理信息，N1会话管理信息中包括PDU会话释放命令(PDU Session Release Command)以及定时指示信息等。
步骤512：AMF实体向(R)AN实体发送N2资源释放请求消息,N2资源释放请求消息中包括N1会话管理信息。
步骤513：(R)AN实体将N1会话管理信息透传给终端,并释放所述PDU会话的用 户面资源。
步骤514：(R)AN实体向AMF实体发送N2资源释放确认消息，用于指示已经释放所述PDU会话的用户面资源。
步骤515：AMF实体向SMF实体发送N11响应消息，N11响应消息中包括N2资源释放确认消息。
步骤516：SMF实体向AMF实体发送N11消息，用于通知AMF实体PDU会话已释放。
需要说明的是，在步骤507中，SMF实体若确定所述PDU会话的默认流位于所述流列表中，且根据所述第一信息确定不允许建立去激活态的所述PDU会话时，SMF实体在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源。此时，虽然PDU会话的默认流未建立成功，但是PDU会话中存在空口资源建立成功的流，因此可以通过空口资源建立成功的流传递数据。
或者，SMF实体若确定所述PDU会话的默认流位于所述流列表中，且根据所述第一信息确定不允许建立去激活态的所述PDU会话时，SMF实体通知PCF实体默认流的空口资源建立失败，并接收PCF实体发送的所述默认流的服务质量参数。SMF实体将获得的默认流的服务质量参数转发给AMF实体，AMF实体再将默认流的服务质量参数转发给(R)AN实体，(R)AN实体从而根据该默认流的服务质量参数重新为默认流建立空口资源。
本申请实施例中，还可以在重新激活去激活态的PDU会话的过程中，在确定不能激活所述去激活态的PDU会话时，维持去激活态的PDU会话的状态不变，或者将去激活态的PDU会话的资源释放。
结合前面的描述，如图6所示，为本申请实施例提供的一种会话建立方法流程示意图。图6所示的方法中的第一网络设备可以是指SMF实体，第二网络设备可以是指(R)AN实体。
参见图6，该方法包括：
步骤601：第一网络设备判断PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
步骤602：若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
关于步骤601至步骤602中的其他内容，例如第一信息等，与步骤201至步骤202中的定义或描述相同，在此不再赘述。
步骤601至步骤602中，所述第一网络设备还可以获取第二信息或第三信息，第二信息、第三信息的具体描述可以参考步骤201至步骤202中的定义或描述，在此不再赘述。
如图7所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的第一网络设备的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置700包括：处理单元701和收发单元702。
处理单元701，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功；
收发单元702，用于在所述PDU会话的默认流的空口资源建立失败时，根据第一信息 建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
一种可选地实施方案中，所述收发单元702具体用于：
获取流列表，所述流列表为第二网络设备根据所述PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流；
所述处理单元701具体用于，根据所述流列表判断所述PDU会话的默认流的空口资源是否建立成功。
一种可选地实施方案中，所述第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型SST；
或者，所述第一信息为所述PDU会话对应的终端的策略与计费控制规则；
或者，所述第一信息为所述终端发送给所述装置的指示信息。
一种可选地实施方案中，所述收发单元702还用于：
获取第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
所述根据第一信息建立去激活态的所述PDU会话之后，所述处理单元701还用于：
在所述第二信息指示的所述时间点激活去激活态的所述PDU会话；
或者，所述收发单元还用于将所述第二指示信息发送给所述终端，所述第二指示信息用于指示所述终端在所述时间点激活去激活态的所述PDU会话。
一种可选地实施方案中，所述收发单元702还用于：
获取第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数；
所述在所述第二信息指示的时间点激活去激活态的所述PDU会话之后，所述处理单元701还用于：
若确定所述去激活态的所述PDU会话的被激活次数等于所述最大次数，则触发释放所述PDU会话的流程。
一种可选地实施方案中，所述确定所述PDU会话的默认流的空口资源建立失败之后，所述处理单元701还用于：
若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源；
或者，若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
一种可选地实施方案中，所述根据第一信息建立去激活态的所述PDU会话之后，所述处理单元701还用于：
将所述PDU会话中空口资源建立成功的流的空口资源释放。
如图8所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的第一网络设备的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置800包括：处理单元801和收发单元802。
处理单元801，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
收发单元802，用于所述PDU会话的默认流的空口资源建立失败时，根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
如图9所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的终端的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置900包括：处理单元901和收发单元902。
处理单元901，用于生成第一信息，所述第一信息用于指示在分组数据单元PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话；
收发单元902，用于通过第二网络设备向第一网络设备发送第一信息。
一种可选地实施方案中，所述PDU会话被建立为去激活态；
所述收发单元902还用于：
接收所述第一网络设备通过所述第二网络设备发送的第二指示信息；所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。
如图10所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的第一网络设备的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置1000包括：处理器1001、收发机1002、存储器1003和通信接口1004；其中，处理器1001、收发机1002、存储器1003和通信接口1004通过总线1005相互连接。
处理器1001可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器1001还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
存储器1003可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器1003还可以包括上述种类的存储器的组合。
通信接口1004可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。
总线1005可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
存储器1003可以用于存储程序指令，处理器1001调用该存储器1003中存储的程序指令，可以执行上述方案中所示实施例中的一个或多个步骤。
处理器1001，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功；
收发机1002，用于在所述PDU会话的默认流的空口资源建立失败时，根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
一种可选地实施方案中，所述收发机1002具体用于：
获取流列表，所述流列表为第二网络设备根据所述PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流；
所述处理器1001具体用于，根据所述流列表判断所述PDU会话的默认流的空口资源是否建立成功。
一种可选地实施方案中，所述第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型SST；
或者，所述第一信息为所述PDU会话对应的终端的策略与计费控制规则；
或者，所述第一信息为所述终端发送给所述装置的指示信息。
一种可选地实施方案中，所述收发机1002还用于：
获取第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
所述根据第一信息建立去激活态的所述PDU会话之后，所述处理器1001还用于：
在所述第二信息指示的所述时间点激活去激活态的所述PDU会话；
或者，所述收发机还用于将所述第二指示信息发送给所述终端，所述第二指示信息用于指示所述终端在所述时间点激活去激活态的所述PDU会话。
一种可选地实施方案中，所述收发机1002还用于：
获取第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数；
所述在所述第二信息指示的时间点激活去激活态的所述PDU会话之后，所述处理器1001还用于：
若确定所述去激活态的所述PDU会话的被激活次数等于所述最大次数，则触发释放所述PDU会话的流程。
一种可选地实施方案中，所述确定所述PDU会话的默认流的空口资源建立失败之后，所述处理器1001还用于：
若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源；
或者，若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
一种可选地实施方案中，所述根据第一信息建立去激活态的所述PDU会话之后，所述处理器1001还用于：
将所述PDU会话中空口资源建立成功的流的空口资源释放。
如图11所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的第一网络设备的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置1100包括：处理器1101、收发机1102、存储器1103和通信接口1104； 其中，处理器1101、收发机1102、存储器1103和通信接口1104通过总线1105相互连接，上述模块的具体内容可以参考图10中相关模块的描述，在此不再赘述。
处理器1101，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
收发机1102，用于所述PDU会话的默认流的空口资源建立失败时，根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
如图12所示，为本申请实施例提供一种会话建立装置结构示意图，该会话建立装置可执行上述各方法实施例中的终端的动作。可选的，该会话建立装置可以为可以是指SMF实体，第二网络设备可以是指(R)AN实体。
该会话建立装置1200包括：处理器1201、收发机1202、存储器1203和通信接口1204；其中，处理器1201、收发机1202、存储器1203和通信接口1204通过总线1205相互连接，上述模块的具体内容可以参考图10中相关模块的描述，在此不再赘述。
处理器1201，用于生成第一信息，所述第一信息用于指示在分组数据单元PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话；
收发机1202，用于通过第二网络设备向第一网络设备发送第一信息。
一种可选地实施方案中，所述PDU会话被建立为去激活态；
所述收发机1202还用于：
接收所述第一网络设备通过所述第二网络设备发送的第二指示信息；所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。
本申请实施例还提供了一种计算机可读存储介质，用于存储为执行上述处理器所需执行的计算机软件指令，其包含用于执行上述处理器所需执行的程序。
本申请实施例提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述任一种可能的设计中的方法。
本申请实施例提供一种芯片，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现上述任一种可能的设计中的方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (23)

  1. 一种会话建立方法，其特征在于，所述方法包括：
    第一网络设备判断分组数据单元PDU会话的默认流的空口资源是否建立成功；
    若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
  2. 一种会话建立方法，其特征在于，所述方法包括：
    第一网络设备判断分组数据单元PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
    若所述PDU会话的默认流的空口资源建立失败，则所述第一网络设备根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一网络设备判断PDU会话的默认流的空口资源是否建立成功，包括：
    所述第一网络设备获取流列表，所述流列表为第二网络设备根据所述PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流；
    所述第一网络设备根据所述流列表判断所述PDU会话的默认流的空口资源是否建立成功。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型SST；
    或者，所述第一信息为所述PDU会话对应的终端的策略与计费控制规则；
    或者，所述第一信息为所述终端发送给所述第一网络设备的指示信息。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备获取第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
    所述根据第一信息建立去激活态的所述PDU会话之后，所述方法还包括：
    所述第一网络设备在所述第二信息指示的所述时间点激活去激活态的所述PDU会话；
    或者，所述第一网络设备将所述第二指示信息发送给所述终端，所述第二指示信息用于指示所述终端在所述时间点激活去激活态的所述PDU会话。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备获取第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数；
    所述第一网络设备在所述第二信息指示的时间点激活去激活态的所述PDU会话之后，还包括：
    所述第一网络设备若确定所述去激活态的所述PDU会话的被激活次数等于所述最大次数，则触发释放所述PDU会话的流程。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述第一网络设备确定所述PDU会话的默认流的空口资源建立失败之后，所述方法还包括：
    所述第一网络设备若根据所述第一信息确定不允许建立去激活态的所述PDU会话， 则在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源；
    或者，所述第一网络设备若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则所述第一网络设备向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述根据第一信息建立去激活态的所述PDU会话之后，所述方法还包括：
    所述第一网络设备将所述PDU会话中空口资源建立成功的流的空口资源释放。
  9. 一种会话建立方法，其特征在于，所述方法包括：
    终端生成第一信息，所述第一信息用于指示在分组数据单元PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话；
    所述终端通过第二网络设备向第一网络设备发送第一信息。
  10. 根据权利要求9所述的方法，其特征在于，所述PDU会话被建立为去激活态；
    所述方法还包括：
    所述终端接收所述第一网络设备通过所述第二网络设备发送的第二指示信息；所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
    所述终端在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。
  11. 一种会话建立装置，其特征在于，所述装置包括：
    处理单元，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功；
    收发单元，用于在所述PDU会话的默认流的空口资源建立失败时，根据第一信息建立去激活态的所述PDU会话或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话。
  12. 一种会话建立装置，其特征在于，所述装置包括：
    处理单元，用于判断分组数据单元PDU会话的默认流的空口资源是否建立成功,所述PDU会话处于去激活态；
    收发单元，用于所述PDU会话的默认流的空口资源建立失败时，根据第一信息维持所述PDU会话为去激活态或触发释放所述PDU会话；所述第一信息用于指示在所述PDU会话的默认流的空口资源建立失败时，是否允许维持所述PDU会话为去激活态。
  13. 根据权利要求11或12所述的装置，其特征在于，所述收发单元具体用于：
    获取流列表，所述流列表为第二网络设备根据所述PDU会话的空口资源建立结果生成的，所述流列表包括所述PDU会话中空口资源建立失败的流；
    所述处理单元具体用于，根据所述流列表判断所述PDU会话的默认流的空口资源是否建立成功。
  14. 根据权利要求11至13任一所述的装置，其特征在于，所述第一信息为所述PDU会话对应的终端的签约数据中的切片/业务类型SST；
    或者，所述第一信息为所述PDU会话对应的终端的策略与计费控制规则；
    或者，所述第一信息为所述终端发送给所述装置的指示信息。
  15. 根据权利要求11至14任一所述的装置，其特征在于，所述收发单元还用于：
    获取第二信息，所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
    所述根据第一信息建立去激活态的所述PDU会话之后，所述处理单元还用于：
    在所述第二信息指示的所述时间点激活去激活态的所述PDU会话；
    或者，所述收发单元还用于将所述第二指示信息发送给所述终端，所述第二指示信息用于指示所述终端在所述时间点激活去激活态的所述PDU会话。
  16. 根据权利要求15所述的装置，其特征在于，所述收发单元还用于：
    获取第三信息，所述第三信息用于指示去激活态的所述PDU会话被激活的最大次数；
    所述在所述第二信息指示的时间点激活去激活态的所述PDU会话之后，所述处理单元还用于：
    若确定所述去激活态的所述PDU会话的被激活次数等于所述最大次数，则触发释放所述PDU会话的流程。
  17. 根据权利要求11至16任一所述的装置，其特征在于，所述确定所述PDU会话的默认流的空口资源建立失败之后，所述处理单元还用于：
    若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则在确定所述PDU会话所包括的流中存在至少一个空口资源建立成功的流时，触发为所述PDU会话建立用户面资源；
    或者，若根据所述第一信息确定不允许建立去激活态的所述PDU会话，则向所述第二网络设备发送默认流的服务质量参数，并指示所述第二网络设备根据所述默认流的服务质量参数为所述默认流建立空口资源。
  18. 根据权利要求11至17任一所述的装置，其特征在于，所述根据第一信息建立去激活态的所述PDU会话之后，所述处理单元还用于：
    将所述PDU会话中空口资源建立成功的流的空口资源释放。
  19. 一种会话建立装置，其特征在于，所述装置包括：
    处理单元，用于生成第一信息，所述第一信息用于指示在分组数据单元PDU会话的默认流的空口资源建立失败时，是否允许建立去激活态的所述PDU会话；
    收发单元，用于通过第二网络设备向第一网络设备发送第一信息。
  20. 根据权利要求19所述的装置，其特征在于，所述PDU会话被建立为去激活态；
    所述收发单元还用于：
    接收所述第一网络设备通过所述第二网络设备发送的第二指示信息；所述第二信息用于指示激活去激活态的所述PDU会话的时间点；
    在所述第二指示信息指示的时间点，向所述第二网络设备发送激活请求消息，所述激活请求消息用于请求激活去激活态的所述PDU会话。
  21. 一种计算机可读存储介质，其特征在于，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如权利要求1-10任意一项所述的方法。
  22. 一种计算机程序产品，其特征在于，当计算机读取并执行所述计算机程序产品时，使得计算机执行如权利要求1-10任意一项所述的方法。
  23. 一种芯片，其特征在于，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现如权利要求1-10任意一项所述的方法。
PCT/CN2018/104680 2017-09-08 2018-09-07 一种会话建立方法及装置 WO2019047935A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18854810.1A EP3664570B1 (en) 2017-09-08 2018-09-07 Session establishment methods and apparatus
AU2018329060A AU2018329060B2 (en) 2017-09-08 2018-09-07 Session establishment method and apparatus
US16/810,660 US11202338B2 (en) 2017-09-08 2020-03-05 Session establishment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710806432.5 2017-09-08
CN201710806432.5A CN109474954B (zh) 2017-09-08 2017-09-08 一种会话建立方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/810,660 Continuation US11202338B2 (en) 2017-09-08 2020-03-05 Session establishment method and apparatus

Publications (1)

Publication Number Publication Date
WO2019047935A1 true WO2019047935A1 (zh) 2019-03-14

Family

ID=65633503

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104680 WO2019047935A1 (zh) 2017-09-08 2018-09-07 一种会话建立方法及装置

Country Status (5)

Country Link
US (1) US11202338B2 (zh)
EP (1) EP3664570B1 (zh)
CN (1) CN109474954B (zh)
AU (1) AU2018329060B2 (zh)
WO (1) WO2019047935A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018230778A1 (ko) * 2017-06-14 2018-12-20 엘지전자 주식회사 세션을 관리하는 방법 및 그 방법을 수행하는 smf 노드
US11134419B2 (en) * 2019-02-18 2021-09-28 Mediatek Inc. Interworking between fifth generation system (5GS) and evolved packet system (EPS) for session management
KR102686161B1 (ko) * 2019-05-03 2024-07-18 삼성전자 주식회사 이동통신 시스템에서 시간 또는 서비스 지역에 따른 단말의 세션 설정 관리 방법 및 장치
US20220322489A1 (en) * 2019-10-11 2022-10-06 Nec Corporation Controlling and restricting of user identities per ue
CN111277470B (zh) * 2020-02-19 2022-07-26 联想(北京)有限公司 一种用户面功能切换方法、装置、系统和存储介质
US12016075B2 (en) * 2022-01-03 2024-06-18 Verizon Patent And Licensing Inc. Systems and methods for transferring multiple packet data unit sessions with a same data network name configuration between networks

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
CN106851856A (zh) * 2016-12-23 2017-06-13 电信科学技术研究院 一种基于移动中继的无线通信建立方法及网络设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7685254B2 (en) * 2003-06-10 2010-03-23 Pandya Ashish A Runtime adaptable search processor
WO2015008989A1 (en) * 2013-07-14 2015-01-22 Lg Electronics Inc. Method and apparatus for managing data radio bearers for dual connectivity in wireless communication system
US9894614B2 (en) * 2015-03-31 2018-02-13 Apple Inc. Frame transmission scheme modification
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
JP7189126B2 (ja) * 2017-06-21 2022-12-13 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるサービス要求手順の実行方法とそのための装置
KR101979856B1 (ko) * 2017-08-08 2019-05-17 엘지전자 주식회사 접속 제어 방법 및 사용자기기

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
CN106851856A (zh) * 2016-12-23 2017-06-13 电信科学技术研究院 一种基于移动中继的无线通信建立方法及网络设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Supporting home routed PUD session in TS 23.502", 3GPP TSG SA WG2 MEETING #121 S 2-174283, 30 June 2017 (2017-06-30), pages 2 - 3, XP051309363 *
See also references of EP3664570A4

Also Published As

Publication number Publication date
EP3664570A1 (en) 2020-06-10
EP3664570A4 (en) 2020-07-29
AU2018329060B2 (en) 2020-11-19
US20200205226A1 (en) 2020-06-25
CN109474954A (zh) 2019-03-15
US11202338B2 (en) 2021-12-14
EP3664570B1 (en) 2021-05-26
CN109474954B (zh) 2020-12-25
AU2018329060A1 (en) 2020-03-12

Similar Documents

Publication Publication Date Title
CN112740824B (zh) 恢复请求随后释放和重定向
US9942748B2 (en) Service provisioning system and method, and mobile edge application server and support node
US11202338B2 (en) Session establishment method and apparatus
US10129802B2 (en) Layered connectivity in wireless systems
US20190313262A1 (en) Handling QoS Flow without a Mapping Data Radio Bearer
US10863569B2 (en) RRC connection re-establishment method for data transmission
WO2019196643A1 (zh) 通信的方法和通信装置
WO2020173137A1 (zh) 一种数据传输方法、相关设备、程序产品以及存储介质
JPWO2018230730A1 (ja) ユーザ装置、無線通信システム及び無線通信方法
WO2020001257A1 (zh) 一种数据传输方法及装置
US11722574B2 (en) Packet transmission method, communication apparatus, and communication system
WO2022068424A1 (zh) 通信方法及装置
WO2018014154A1 (zh) 一种rrc连接重建方法和装置
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
TWI749312B (zh) 一種擁塞控制方法、設備及裝置
WO2019238050A1 (zh) 一种通信方法及装置
US20160234687A1 (en) Splitting method, base station, and user equipment
WO2022082543A1 (zh) Iab节点的移植方法及装置
WO2020142884A1 (zh) 切换传输路径的方法及装置
WO2022160861A1 (zh) 通信方法及装置
WO2019085888A1 (zh) 专有承载流的处理方法、装置及系统
WO2018228309A1 (zh) 缓存控制方法、网元及控制器
US20240147524A1 (en) Managing data communication before and after a state transition
WO2022067730A1 (zh) 一种双终端设备进行数据传输的方法及装置
WO2021190513A1 (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: 18854810

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018329060

Country of ref document: AU

Date of ref document: 20180907

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018854810

Country of ref document: EP

Effective date: 20200306