WO2022267632A1 - 会话管理的方法及装置 - Google Patents

会话管理的方法及装置 Download PDF

Info

Publication number
WO2022267632A1
WO2022267632A1 PCT/CN2022/086276 CN2022086276W WO2022267632A1 WO 2022267632 A1 WO2022267632 A1 WO 2022267632A1 CN 2022086276 W CN2022086276 W CN 2022086276W WO 2022267632 A1 WO2022267632 A1 WO 2022267632A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos flow
qos
parameter
terminal device
network device
Prior art date
Application number
PCT/CN2022/086276
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 EP22827135.9A priority Critical patent/EP4351209A4/en
Publication of WO2022267632A1 publication Critical patent/WO2022267632A1/zh
Priority to US18/393,841 priority patent/US20240129786A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the embodiments of the present application relate to the communication field, and more specifically, to a method and device for session management.
  • XR extended reality
  • GBR guaranteed bit rate quality of service
  • QoS quality of service
  • GBR-type QoS flows need to guarantee network resources.
  • core network equipment it is difficult for core network equipment to sense the end of the service, so that they cannot effectively manage the QoS flows, resulting in waste of network resources and the adverse effects of difficulty in improving system capacity. . Therefore, a session management method and device are needed to alleviate the above problems.
  • the present application provides a session management method and device, so that network equipment can sense the end of a service, improve the utilization rate of network resources, and save network resources.
  • a method for session management wherein the terminal device determines a first parameter, and the first parameter is used by a first network device to determine a first inactivity duration of a first quality of service QoS flow of the terminal device, Or, the first network device is used to determine the first inactivity duration of the first session of the terminal device; the terminal device sends a first message to the first network device, where the first message includes the first parameter.
  • the first inactive duration of the first QoS flow is used for determining to release the first Qos flow, or the first inactive duration of the first session is used for determining to release the user plane connection of the first session.
  • the first parameter is the first periodic information of the service of the terminal device, or, the first parameter is the second inactivity duration of the first QoS flow determined according to the first periodic information of the service of the terminal device or For the second inactive duration of the first session, the first periodic information of the service of the terminal device includes the information of the first frame rate of the service, or the information of the frames with high importance and frames with low importance in the service At least one item in the first ratio information.
  • the terminal device determines the first inactivity period for the first network device to determine the first quality of service QoS flow of the terminal device through the first periodical information of the terminal device's service, or, for the first network device to determine The first inactive duration of the first session of the terminal device, so that the first network device releases the first QoS flow (the QoS flow that requires the network to guarantee the bit rate) in time according to the first inactive duration of the first QoS flow, or the first QoS flow
  • a network device deactivates the user plane connection of the first session in time according to the first inactive duration of the first session, saving network resources.
  • the terminal device receives a message of the first network device that includes first inactivity duration information of the first QoS flow; When the duration of data transmission reaches the first inactive duration of the first QoS flow, the terminal device releases the first QoS flow; or, the terminal device sends an inactive message indicating that the first QoS flow is inactive to the first network device , and/or, a message requesting to release the first QoS flow; the terminal device receives a message from the first network device for instructing to release the first QoS flow.
  • the terminal device monitors whether the duration of no data transmission of the first QoS flow reaches the first inactive duration of the first QoS flow, or according to the message sent by the first network device for instructing release of the first QoS flow, The first QoS flow is released, so that the first QoS flow is released in time, thereby saving network resources.
  • the terminal device sends a second message to the first network device, where the second message includes a second parameter, and the second parameter is used for the first network device determining the first QoS parameter of the first QoS flow, or, the second message includes a third parameter, and the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the second QoS The first QoS parameter for the flow.
  • the second parameter or the third parameter is second periodic information of services of the terminal device.
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device, or the second QoS parameter of the first QoS flow and the second QoS flow of the second QoS flow
  • the second QoS parameter, the second QoS parameter of the first QoS flow is the second parameter
  • the information of the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow are the third parameter.
  • the second periodical information of the service of the terminal device includes at least one of the information of the second frame rate of the service, or the second ratio information of frames with high importance and frames with low importance in the service item.
  • the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow are both determined according to the second periodic information of the service of the terminal device, thus Determine QoS parameters based on service requirements and layered transmission information to improve network resource utilization efficiency.
  • the terminal device receives a message from the first network device that includes the first inactivity duration information of the first session; no data transmission in the first session
  • the terminal device deactivates the user plane connection of the first session; or, the terminal device sends a message indicating that the first session is inactive to the first network device , and/or, a message requesting to deactivate the user plane connection of the first session; the terminal device receives a message from the second network device indicating to deactivate the user plane connection of the first session.
  • the terminal device deactivates the user plane connection of the first session according to the message sent by the second network device indicating to deactivate the user plane connection of the first session, so that the user plane connection of the first session is deactivated in time, Thereby saving network resources.
  • a session management method including: a first network device receives a first message from a terminal device, the first message includes a first parameter, and the first parameter is used by the first network device to determine that the terminal The first inactive duration of the first quality of service QoS flow of the device, or the first inactive duration for the first network device to determine the first session of the terminal device; the first network device according to the first parameter, Determine the first inactive duration of the first QoS flow, or determine the first inactive duration of the first session.
  • the first inactive duration of the first QoS flow is used to determine to release the first QoS flow, or
  • the first inactive duration of the first session is used to determine to release the user plane connection of the first session.
  • the first network device determines the first inactivity duration of the first QoS flow of the terminal device according to the first parameter determined by the first periodical information of the service of the terminal device, or the first session of the first session of the terminal device An inactive duration, so that the first network device releases the first QoS flow (the QoS flow that requires the network to guarantee the bit rate) in time according to the first inactive duration of the first QoS flow, or the first network device releases the first QoS flow according to the first session's
  • the first inactivity period enables the user plane connection of the first session to be deactivated in time, thereby improving the utilization efficiency of network resources.
  • the first network device sends to the terminal device and/or the second network device and/or the third network device a first non-identical message including the first QoS flow.
  • a message of activity duration information the first network device receives from the terminal device and/or the second network device and/or the third network device: indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow
  • a message of a QoS flow the first network device sends a message for instructing release of the first QoS flow to the terminal device, and/or the second network device and/or the third network device.
  • the first network device receives a second message from the terminal device, the second message includes a second parameter, and the second parameter is used for the first network
  • the device determines the first QoS parameter of the first QoS flow; or, the second message includes a third parameter, and the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the second The first QoS parameter of the QoS flow.
  • the first network device sends a message including the first inactivity duration information of the first session to the terminal device.
  • the first network device receives an indication from the terminal device that the first session is inactive, and/or requests to deactivate the user plane connection of the first session a message; the first network device sends a message indicating to deactivate the user plane connection of the first session to the second network device and/or the third network device.
  • the second network device receives the message from the first network device that includes the first inactivity duration information of the first QoS flow.
  • the second network device sends an indication to the first network device that the first QoS flow is inactive, and /or, a message requesting to release the first QoS flow; the second network device receives a message from the first network device for instructing to release the first QoS flow.
  • the third network device receives the message from the first network device that includes the first inactivity duration information of the first QoS flow.
  • the third network device sends an indication to the first network device that the first QoS flow is inactive, and /or, a message requesting to release the first QoS flow; the third network device receives a message from the first network device for instructing to release the first QoS flow.
  • a session management method including: a terminal device sends a second message to a first network device, the second message includes a second parameter, and the second parameter is used by the first network device to determine the first The first QoS parameter of the QoS flow; or, the second message includes a third parameter, and the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • QoS parameters including: a terminal device sends a second message to a first network device, the second message includes a second parameter, and the second parameter is used by the first network device to determine the first The first QoS parameter of the QoS flow; or, the second message includes a third parameter, and the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • a session management method including: a first network device receives a second message from a terminal device, the second message includes a second parameter, and the second parameter is used by the first network device to determine the second message.
  • a communication device is provided, and the communication device is configured to execute the communication method provided in the first aspect or the third aspect.
  • the communication device includes a module for executing the communication methods provided in the first aspect to the third aspect.
  • a communication device is provided, and the communication device is configured to execute the communication method provided in the first aspect or the third aspect.
  • the communication device includes a module for executing the communication method provided in the second aspect or the fourth aspect.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor
  • the processor implements the method in any possible implementation manner of the aforementioned first aspect or third aspect through a logic circuit or executing code instructions.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor
  • the processor implements the method in any possible implementation manner of the aforementioned second aspect or fourth aspect through a logic circuit or executing code instructions.
  • a computer-readable storage medium in which a computer program or instruction is stored, and when the computer program or instruction is executed, any possibility of the aforementioned first aspect or third aspect can be realized. method in the implementation of .
  • a computer-readable storage medium is provided, and a computer program or instruction is stored in the computer-readable storage medium.
  • the computer program or instruction is executed, any possibility of the aforementioned second or fourth aspect can be realized. method in the implementation of .
  • a computer program product including instructions is provided, and when the instructions are executed, the method in any possible implementation manner of the aforementioned first aspect or the third aspect is implemented.
  • a computer program product including instructions is provided, and when the instructions are executed, the method in any possible implementation manner of the aforementioned second aspect or fourth aspect is implemented.
  • a computer program in a thirteenth aspect, includes codes or instructions, and when the codes or instructions are executed, implement the method in any possible implementation manner of the aforementioned first aspect or third aspect.
  • a computer program in a fourteenth aspect, includes codes or instructions, and when the codes or instructions are executed, implement the method in any possible implementation manner of the aforementioned second aspect or fourth aspect.
  • a chip system in a fifteenth aspect, includes a processor, and further includes a memory, configured to implement the method in any possible implementation manner of the aforementioned first aspect or the third aspect.
  • the system-on-a-chip consists of chips and also includes chips and other discrete devices.
  • a chip system in a sixteenth aspect, includes a processor, and further includes a memory, configured to implement the method in any possible implementation manner of the foregoing second aspect or the fourth aspect.
  • the system-on-a-chip consists of chips and also includes chips and other discrete devices.
  • a communication system in a seventeenth aspect, includes the devices of the fifth aspect and the sixth aspect.
  • FIG. 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of P frames and I frames applicable to this embodiment.
  • FIG. 3 is a schematic diagram of QoS stream transmission applicable to the embodiment of the present application.
  • FIG. 4 is a schematic diagram of a session management method 400 proposed by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a session management method 500 proposed by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a session management method 600 provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a session management method 700 provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a method 800 for determining service termination of a terminal device.
  • FIG. 9 is a schematic diagram of a session management method 900 provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a session management method 1000 provided by an embodiment of the present application.
  • Fig. 11 is a schematic block diagram of a communication device 1100 provided by an embodiment of the present application.
  • Fig. 12 is a schematic block diagram of a communication device 1200 provided by an embodiment of the application.
  • Fig. 13 is a schematic structural diagram of a simplified terminal device 1300 provided by the embodiment of the application.
  • Fig. 14 is a schematic structural diagram of a simplified network device 1400 provided by the embodiment of the application.
  • the technical solution of the embodiment of the present application is applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunications system, UMTS).
  • extended reality includes augmented reality (augmented reality, AR), virtual reality (virtual reality, VR), and mixed reality (mixed reality, MR).
  • V2X vehicle to vehicle
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • FIG. 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application. Some subjects involved in the network architecture shown in FIG. 1 will be described below.
  • UE User equipment
  • terminals mobile stations (mobile station, MS), terminal (terminal) or soft terminal.
  • MS mobile station
  • terminal terminal
  • water meters electricity meters
  • sensors sensors.
  • the user equipment in the embodiment of the present application refers to an access terminal, a subscriber unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal device ( terminal equipment), wireless communication equipment, user agent or user device.
  • the user equipment is also a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, user equipment in 5G networks or user equipment in future evolved public land mobile networks (public land mobile network, PLMN) or The user equipment in the future Internet of Vehicles is not limited in this embodiment of the present application.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PDA personal digital assistant
  • wearable devices are also called wearable smart devices, which is a general term for wearable devices that are intelligently designed for daily wear and developed by applying wearable technology, such as glasses and gloves. , watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and only focus on a certain type of application functions, which need to be used in conjunction with other devices such as smartphones , such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the user equipment can also be the user equipment in the Internet of Things (Internet of Things, IoT) system.
  • IoT Internet of Things
  • IoT is an important part of the development of information technology in the future, and its main technical feature is that items can be Connect with the network to realize the intelligent network of man-machine interconnection and object interconnection.
  • the IOT technology achieves massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.
  • the user equipment also includes smart printers, train detectors, and gas station sensors, and its main functions include collecting data (part of user equipment), receiving control information and downlink data of access network equipment, and sending electromagnetic waves , to transmit uplink data to the access network device.
  • It is used to provide network access functions for authorized user equipment in a specific area, and use transmission tunnels of different qualities according to the level of user equipment and business requirements.
  • (R)AN manages wireless resources, provides access services for user equipment, and completes the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN is also understood as a base station in a traditional network.
  • the access network device in the embodiment of the present application is any communication device with a wireless transceiver function for communicating with the user equipment.
  • the access network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI)
  • the access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or sending and receiving point (transmission and reception point, TRP) in the system can also be 5G, such as , NR, a gNB in the system, or, a transmission point (TRP or TP), one or a group (including multiple
  • a gNB includes a centralized unit (CU) and a DU.
  • the gNB also includes an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and realizing the functions of radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer.
  • the DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical (physical, PHY) layer.
  • the AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, is also considered to be sent by the DU , or, sent by DU+AAU.
  • the access network device is a device including one or more of a CU node, a DU node, and an AAU node.
  • dividing the CU into access network devices in the access network can also divide the CU into access network devices in the core network (core network, CN), which is not done in this application limited.
  • the user plane network element is used for packet routing and forwarding and quality of service (quality of service, QoS) processing of user plane data.
  • quality of service quality of service
  • the user plane network element is a user plane function (UPF) network element, which is responsible for the management of user plane paths and data distribution, including management of UE IP addresses, management of CN tunnel information, traffic Detection, user plane forwarding, and billing.
  • UPF user plane function
  • the user plane network element is still a UPF network element, or there are other names, which are not limited in this application.
  • Data network elements are used to provide a network for data transmission.
  • the data network element is a data network element (data network, DN), such as operator services, Internet access or third-party services.
  • the data network element is still a DN network element, or there are other names, which are not limited in this application.
  • Access management network element :
  • the access management network element is mainly used for mobility management and access management, and is used to implement other functions in the mobility management (mobility management entity, MME) entity functions except session management, such as lawful interception and access authorization/ Authentication function.
  • MME mobility management entity
  • the access management network element is an access and mobility management function (AMF) network element, which provides mobility management, lawful interception, or access authorization and authentication functions.
  • AMF access and mobility management function
  • the access management network element is still an AMF network element, or there are other names, which are not limited in this application.
  • Session management network element
  • the session management network element is mainly used for session management, Internet protocol (internet protocol, IP) address allocation and management of terminal equipment, selection of endpoints that can manage user plane functions, policy control and charging function interfaces, and downlink data notification.
  • Internet protocol Internet protocol, IP
  • the session management network element is a session management function (session management function, SMF) network element, which is used to implement session and bearer management and address allocation.
  • SMF session management function
  • the user plane functional network element is used for routing and forwarding of user plane data, threshold control, traffic monitoring, and verification functions.
  • the session management network element is still an SMF network element, or has other names, which are not limited in this application.
  • the policy control network element is used to guide the unified policy framework of network behavior, and provides policy rule information for control plane functional network elements (such as AMF and SMF network elements).
  • the policy control network element is a policy and charging rules function (PCRF) network element.
  • PCF policy control function
  • the policy control network element is a policy control function (policy control function, PCF) network element.
  • PCF policy control function
  • the policy control network element is still a PCF network element, or there are other names, which are not limited in this application.
  • the authentication server function network element is used for authentication services, generates keys to realize two-way authentication of terminal devices, and supports a unified authentication framework.
  • the authentication server is an authentication server function (authentication server function, AUSF).
  • the authentication server function network element is still an AUSF network element, or has other names, which are not limited in this application.
  • the data management network element is used to handle terminal equipment identification, access authentication, registration and mobility management.
  • the data management network element is a unified data management (unified data management, UDM) network element.
  • UDM unified data management
  • the unified data management is still a UDM network element, or there are other names, which are not limited in this application.
  • the application network element is used to route the data affected by the application, connect to the network open function network element, and interact with the policy framework for policy control.
  • the application network element is an application function (Application Function, AF) network element, which is a server end that provides a certain type of service for users, so it can also be called an application server or a service server.
  • AF Application Function
  • the AF is the AF deployed by the operator's network itself, and it is also a third-party AF.
  • the application network element is still the AF network element, or there are other names, which are not limited in this application.
  • Network storage network element :
  • Network storage network elements are used to maintain real-time information of all network function services in the network.
  • the network storage network element is a network registry function (network repository function, NRF) network element.
  • NRF network repository function
  • the network storage network element is still an NRF network element, or has other names, which are not limited in this application.
  • network element or function is not only a network element in a hardware device, but also a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the session management network element is referred to as the SMF network element
  • the access management network element is referred to as the AMF network element.
  • the SMF network element is referred to as SMF for short
  • the AMF network element is referred to as AMF for short. That is, the SMF described later in this application can be replaced by a session management network element, and the AMF can be replaced by an access management network element.
  • this application takes the device as an example of an SMF entity and an AMF entity to illustrate the method for transmitting data.
  • the implementation method of the device as a chip in an SMF entity or a chip in an AMF entity refer to the device respectively. It is a specific description of the SMF entity and the AMF entity, and will not be repeated.
  • the terminal equipment is connected to the AMF through the N1 interface
  • the (R)AN is connected to the AMF through the N2 interface
  • the RAN is connected to the UPF through the N3 interface
  • the UPF is connected to the DN through the N6 interface
  • the N4 interface is connected to the SMF connection.
  • the network architecture applied in the embodiment of the present application shown in Figure 1 above is only an example, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture that realizes the functions of the above-mentioned network elements is applicable to this application. Application example.
  • AMF network elements and SMF network elements are called network function network elements (network function, NF) network elements; or, in other network architectures, AMF network elements, SMF network elements A collection of network elements is called a control plane functional network element.
  • network function network function
  • XR services are usually transmitted between network devices and terminal devices in the form of "frames", and each frame represents a still image.
  • the data capacity is reduced through an algorithm.
  • an I frame represents a key frame, and only the data of the frame is needed to complete the decoding, so that the frame picture is completely preserved (because the data of the key frame contains a complete picture);
  • the P frame represents a key frame with the previous key frame (such as I frame), when decoding, it is necessary to superimpose the difference of the current frame with the previously cached picture to generate the final picture.
  • each frame and the size of the picture are related to the quality (for example, 1080P, 720P), usually each frame needs to be transmitted through multiple IP packets, for example, an I frame needs to pass through 100 IP packets For transmission, P frames are transmitted through 40 IP packets.
  • I frames the importance of I frames is higher than that of P frames, because when the transmission of some P frames fails, usually only the display of the P frames is affected, and the user feels a short-term freeze; however, if the I frame If the transmission fails, subsequent P frames will not be able to be parsed, and the user will experience a long-term freeze.
  • FIG. 2 is a schematic diagram of P frames and I frames applicable to this embodiment.
  • P0 is a P frame that has a large modification to the I frame
  • P1 frame is a frame that is slightly modified on the basis of an I frame or a P0 frame
  • a P2 frame is a modification of the previous frame (I frame, P0 frame). frame or P1 frame) with minor modifications.
  • frame or P1 frame with minor modifications.
  • the P1 frame or P2 frame is lost, it will only affect the display of the P1 frame or P2 frame, and the impact is small; if the I frame or P0 frame is lost, it will affect the display of the frame after the I frame or P0 frame, causing greater impact.
  • the XR service has the characteristics of data burst, for example, when the XR service is 60 frames/s, a frame of data will arrive at the base station every 16.67ms, that is, a group of IP packets arrive at the base station, requesting the base station to send it to the terminal device . If the base station cannot send these data, for example, due to network congestion, the base station will randomly discard one or more IP data packets in a set of received IP data packets, so as to alleviate the congestion situation.
  • IP data packets belong to high-priority frames, such as I frames and P0 frames, it will have a great impact on users; if the discarded data packets belong to low-priority frames, such as P1 frames and P2 frames, Then packet loss has little impact on users.
  • FIG. 3 is a schematic diagram of QoS stream transmission applicable to the embodiment of the present application.
  • the UPF entity receives the data sent to the UE from the XR server, it sends the data flow to the UE through two quality of service flows (QoS flows) according to the importance of the data flow.
  • QoS flows quality of service flows
  • the first QoS flow Frames with high importance such as I frame and P0 frame
  • frames with low importance such as P1 frame and P2 frame
  • QoS flow is the finest granularity of QoS forwarding processing defined in the 5G communication system. Data mapped to the same QoS flow will be subject to the same forwarding processing, such as scheduling strategy, queuing management strategy, and rate shaping strategy, providing different QoS Forwarding processing requires a different QoS flow.
  • I frame, P0 frame, and P1 frame, P2 frame as an example of the division of importance is just an example method.
  • the focus of this application is to divide business data into high and low importance.
  • the two types of data are not limited to the use of this division method, and any division factor about the importance of the data is used to determine the importance of the data. Classification of importance.
  • the base station When the base station cannot guarantee data transmission, such as network congestion, the base station will give priority to sending high-priority data (data received from the first QoS flow), and discard low-priority data (data received from the second QoS flow) , to ensure the user's service experience.
  • the two QoS flows are associated with each other, and the UPF entity determines whether to use the first QoS flow for transmission or the second QoS flow for transmission according to the importance of the data flow.
  • the first QoS flow needs to be created as a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow, that is, a QoS flow that requires the network to guarantee the bit rate, while the second QoS flow is created
  • GBR guaranteed bit rate
  • UE or application servers For services with specific QoS requirements, UE or application servers usually need to request specific QoS from 3GPP core network equipment based on service requirements, and then the core network equipment configures corresponding QoS flows.
  • the 3GPP core network equipment cannot sense when the service ends, so it cannot release the GBR QoS flow in time. Therefore, it may cause waste of network resources, contrary to the original intention of layered transmission to improve system capacity.
  • configuring QoS parameters based on business requirements without considering the layered transmission mechanism may cause the problem that the QoS configuration mechanism does not correspond to the layered transmission mechanism, resulting in low resource utilization and greatly reduced benefits of layered transmission.
  • this application proposes a method for session management, which releases the GBR QoS flow in time by determining the inactivity period of the QoS flow.
  • QoS parameters are configured based on business requirements and combined with layered information to improve the benefits of layered transmission.
  • the first QoS flow is a GBR QoS flow, that is, a guaranteed bit rate QoS flow
  • the second QoS flow is a non-GBR QoS flow, that is, no network is required QoS flow with guaranteed bit rate.
  • FIG. 4 is a schematic diagram of a session management method 400 proposed by an embodiment of the present application.
  • the first network device is an SMF entity
  • the second network device is a base station
  • the third network device is a UPF entity.
  • the method 400 includes the following steps:
  • the terminal device determines a first parameter.
  • the terminal device determines a first parameter, and the first parameter is used by the first network device to determine the first inactivity duration of the first quality of service QoS flow of the terminal device, or used by the first network device to determine the first inactivity period of the terminal device.
  • the first duration of inactivity for a session is used by the first network device to determine the first inactivity duration of the first quality of service QoS flow of the terminal device, or used by the first network device to determine the first inactivity period of the terminal device.
  • the first inactive duration of the first QoS flow represents the first duration of continuous no data transmission of the first QoS flow
  • the first inactive duration of the first session represents the first duration of continuous no data transmission of the first session
  • the first QoS flow or the first session is data used to transmit services of the terminal equipment.
  • the first inactive duration of the first QoS flow is used for determining to release the first Qos flow
  • the first inactive duration of the first session is used for determining to release the user plane connection of the first session.
  • the first parameter is first periodic information of services of the terminal device.
  • the first periodical information of the service of the terminal device includes at least one of the first frame rate information of the service, or the first proportion information of frames with high importance and frames with low importance in the service.
  • the information about the first frame rate is information about the number of frames per second, that is, information about a frame rate (frames per second, FPS).
  • the first ratio of frames with high importance to frames with low importance in the business is 1:7, which means that one frame with high importance is followed by 7 frames with low importance, that is, , understood as one I frame or P0 frame followed by seven P1 frames or P2 frames.
  • the terminal device determines the second inactivity duration of the first QoS flow or the second inactivity duration of the first session according to the first periodic information of the terminal device, and the second inactivity duration of the first QoS flow
  • the second inactivity period or the second inactivity period of the first session is the first parameter.
  • the second inactivity duration of the first QoS flow indicates the second duration of continuous no data transmission of the first QoS flow
  • the second inactivity duration of the first session indicates the second duration of continuous no data transmission of the first session.
  • the FPS when the FPS is 60, when layering is not used (that is, data is transmitted using one QoS flow or session, for example, data is transmitted through the first QoS flow or the first session), set the first QoS flow
  • layering that is, at least two QoS flows or sessions are used to transmit data, such as , transmit data through the first QoS flow and the second QoS flow, or the first session and the second session, the first QoS flow or the first session transmits data with high importance in the service, and the second QoS flow or the second session transmits Data with low importance in the business
  • the first ratio of frames with high importance to frames with low importance in the business is 1:7, then according to this ratio, 1 important frame will appear in every 8 frames
  • a frame with a high degree of importance that is, a frame with a high degree of importance occurs once every
  • the terminal device updates the second inactivity duration of the first QoS flow or the first period of the first session according to the updated periodical information of the service. 2. Length of inactivity.
  • the XR server also determines the first parameter, and for the description of determining the first parameter by the XR server, refer to the description of determining the first parameter by the terminal device above.
  • the terminal device sends a first message to the first network device.
  • the first network device receives the first message from the terminal device.
  • the terminal device sends a first message to the first network device, where the first message includes a first parameter.
  • the terminal device sends the first message including the first parameter to the first network device. Further, the first message also carries the QoS requirement of the service and quintuple (packet filter) information related to the service of the terminal device.
  • the present invention does not limit the specific name of the first message, which is a protocol data unit (protocol data unit, PDU) session establishment/modification request message.
  • the terminal device sending the first message to the first network device includes that the terminal device directly sends the first message to the first network device, and also includes that the terminal sends the first message to the first network device through an access network device or an intermediate network element of other core network devices.
  • the first message is sent to the first network device.
  • the terminal first sends the first message to the base station of the access network device, the base station then sends the first message to the core network device AMF, and finally the AMF sends the first message to the first network device.
  • the terminal device updates the second inactive duration of the first QoS flow or the second inactive duration of the first session according to the periodic information of the updated service, the terminal device sends a timely message to the first network device The second inactive duration of the first QoS flow after the update, or the second inactive duration of the first session.
  • the XR server determines the first parameter in S401, then in this step, the XR server sends the first parameter to the first network device.
  • the first network device receives the first parameter from the XR server.
  • the XR server sending the first parameter to the first network device includes directly sending the first parameter to the first network device, and also includes sending the first parameter to the first network device through other intermediate network elements.
  • the XR server sends a message including the first parameter to the PCF entity, and then the PCF entity initiates the SM policy-related modification process.
  • the XR server sends the message including the first parameter to the PCF entity, not only the XR The server sends directly to the PCF entity, and can also send to the PCF entity through the NEF entity.
  • the message sent by the XR server to the PCF entity carries the information of the first parameter, the QoS requirement, and the service-related quintuple (packet filter) of the terminal device, and the PCF entity calls the service to the first network device (SMF entity) ) to send the first parameter, QoS requirements, and quintuple (packet filter) parameters related to the service of the terminal device, wherein the service invoked by the PCF entity is Npcf_SMPolicyControl_UpdateNotify.
  • the first network device determines the first inactivity duration of the first QoS flow according to the first parameter, or determines the first inactivity duration of the first session.
  • the first network device determines the first inactive duration of the first QoS flow according to the first parameter, or determines the first inactive duration of the first session.
  • the first network device determines the first QoS flow according to the second inactivity duration of the first QoS flow, in combination with network policy factors (for example, network quality (jitter), network load factors).
  • network policy factors for example, network quality (jitter), network load factors.
  • the first duration of inactivity Further, the value of the first inactive duration of the first QoS flow should be greater than or equal to the value of the second inactive duration of the first QoS flow.
  • the first network device determines the second session of the first session according to the second inactivity duration of the first session, in combination with network policy factors (for example, network quality (jitter), network load factors). A period of inactivity. Further, the value of the first inactive duration of the first session should be greater than or equal to the value of the second inactive duration of the first session.
  • network policy factors for example, network quality (jitter), network load factors.
  • the first network device determines the first inactive duration of the first QoS flow or the first inactive duration of the first session according to the first periodical information of the service of the terminal device.
  • the first network device determines the first inactive duration of the first QoS flow or the first inactive duration of the first session according to the first periodic information of the service of the terminal device, in combination with network policy factors, Also refer to the description in S401 above that the terminal device determines the second inactivity duration of the first QoS flow or the second inactivity duration of the first session according to the first periodic information of the terminal device. For the sake of brevity, the present application does not repeat.
  • the first network device sends a message including the first inactivity duration information of the first QoS flow to the terminal device.
  • the terminal device receives a message from the first network device that includes the first inactivity duration information of the first QoS flow.
  • the first network device sends a message including information about the first inactivity duration of the first QoS flow to the terminal device, so that the terminal device monitors whether the duration of the first QoS flow without data transmission reaches the first QoS flow. A period of inactivity.
  • the first network device sends a message including the first inactivity duration information of the first QoS flow to the second network device.
  • the second network device receives a message from the first network device that includes the first inactivity duration information of the first QoS flow.
  • the first network device sends a message including first inactivity duration information of the first QoS flow to the second network device, so that the second network device monitors whether the duration of the first QoS flow without data transmission reaches The first inactive duration of the first QoS flow.
  • the terminal device releases the first QoS flow when the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow.
  • the terminal device monitors the duration of the first QoS flow without data transmission according to the first inactivity duration of the first QoS flow, and when the duration of no data transmission of the first QoS flow reaches the first QoS flow In the case of the first inactivity period, the first QoS flow is released.
  • the first QoS flow has a second QoS flow associated with it, and the terminal device deletes the association relationship between the first QoS flow and the second QoS flow, or releases the first QoS flow associated with the first QoS flow.
  • Two QoS flows are used to transmit service data of the terminal device, the first QoS flow transmits data with high importance in the service, and the second QoS flow transmits data with low importance in the service data.
  • the terminal device and/or the second network device and/or the third network device sends to the first network device: a message indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow.
  • the first network device receives a message from the terminal device and/or the second network device and/or the third network device: indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow.
  • the terminal device and/or the second network device and/or the third network device monitor the duration of the first QoS flow without data transmission according to the first inactivity duration of the first QoS flow, and in the first When the duration of no data transmission of the QoS flow reaches the first inactivity duration of the first QoS flow, a message indicating that the first QoS flow is inactive and/or requesting to release the first QoS flow is sent to the first network device.
  • the message is a report message that the duration of no data transmission of the first QoS flow reaches the first inactive duration of the first QoS flow, and can also include the QoS flow identifier (QFI) information of the first QoS flow, in other words, for Indicates that the first QoS flow satisfies the reporting condition.
  • QFI QoS flow identifier
  • the third network device sends a message indicating that the first QoS flow is inactive and/or requesting to release the first QoS flow to the first network device in the form of an N4 report (N4report) message.
  • N4 report N4report
  • the first network device sends a message for instructing release of the first QoS flow to the terminal device and/or the second network device and/or the third network device.
  • the terminal device and/or the second network device and/or the third network device receive a message from the first network device for instructing to release the first QoS flow.
  • the first network device after receiving the message indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow, the first network device sends the user to the terminal device and/or the second network device and/or the third network device The message indicating the release of the first QoS flow.
  • the first network device determines whether there is an associated QoS flow for the first QoS flow to be released according to the message indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow, and sends a message to the terminal device and/or Or the second network device and/or the third network device sends a message for instructing to release the first QoS flow.
  • the first network device sends a message for instructing release of the first QoS flow by sending a protocol data unit (protocol data unit, PDU) session modification message (PDU Session modification) to the terminal device, and/or, The first network device sends a message for instructing to release the first QoS flow by sending an N4 session modification message (N4 session modification) to the third network device.
  • PDU protocol data unit
  • N4 session modification N4 session modification
  • the terminal device releases the first QoS flow.
  • the terminal device releases the first QoS flow after receiving the message sent by the first network device for instructing to release the first QoS flow.
  • the terminal device releases the first QoS flow after receiving the message sent by the first network device for instructing to release the first QoS flow.
  • how to release the first QoS flow when there is a QoS flow associated with the first QoS flow (that is, the second QoS flow) and the first QoS flow does not have a QoS flow associated with it.
  • the flow refer to the relevant description of the above S405, and for the sake of brevity, the present application will not repeat it here.
  • the second network device releases the first QoS flow.
  • the second network device releases the first QoS flow after receiving the message sent by the first network device for instructing to release the first QoS flow.
  • how to release the first QoS flow when there is a QoS flow associated with the first QoS flow (that is, the second QoS flow) and the first QoS flow does not have a QoS flow associated with it.
  • the flow refer to the relevant description of the above S405, and for the sake of brevity, the present application will not repeat it here.
  • the third network device releases the first QoS flow.
  • the third network device releases the first QoS flow after receiving the message sent by the first network device for instructing to release the first QoS flow.
  • how to release the first QoS flow when there is a QoS flow associated with the first QoS flow (that is, the second QoS flow) and the first QoS flow does not have a QoS flow associated with it.
  • the flow refer to the relevant description of the above S405, and for the sake of brevity, the present application will not repeat it here.
  • releasing the first QoS flow includes the QoS flow context information (mainly including QoS profile (QFI and corresponding QoS parameters)) of the second network device side.
  • QoS flow context information mainly including QoS profile (QFI and corresponding QoS parameters)
  • the terminal device sends the second message to the first network device.
  • the first network device receives the second message from the terminal device.
  • the terminal device sends the second message to the first network, and the second message includes the second parameter or the third parameter.
  • the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow
  • the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow Parameters
  • the first QoS parameter of the first QoS flow includes the first guaranteed flow bit rate (Guaranteed flow bit rate, GFBR) of the first QoS flow, the first maximum flow bit rate (maximum flow bit rate, MFBR), or the first At least one of the maximum data burst volume (maximum data burst volume, MDBV)
  • the first QoS parameter of the second QoS flow includes the first GFBR, the first MFBR of the second QoS flow, or at least one of the first MDBV item.
  • the second parameter and the third parameter are second periodic information of services of the terminal device.
  • the second parameter is the second QoS parameter of the first QoS flow determined by the terminal device according to the second periodical information of the service of the terminal device and the information of the layered transmission of the service
  • the third The parameters are the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow determined by the terminal device according to the second periodic information of the service of the terminal device and the information of layered transmission.
  • the second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow
  • the second QoS parameter of the second QoS flow includes the second QoS flow of the second QoS flow.
  • At least one of the second GFBR, the second MFBR, or the second MDBV At least one of the second GFBR, the second MFBR, or the second MDBV.
  • GFBR refers to the guaranteed rate provided by the first network device for the QoS flow
  • MFBR refers to the limitation of the highest bit rate provided by the first network device for the QoS flow.
  • the second periodical information of the service of the terminal device includes at least one of the information of the second frame rate of the service, and the second proportion information of frames with high importance and frames with low importance in the service .
  • the second frame rate (FPS) information determines the second GFBR of the first QoS flow.
  • the number of frames with high importance ratio r1 that is, the number of frames with high importance/(importance degree The number of high frames + the number of low importance frames)
  • the frame size ratio r2 determines the second GFBR of the first QoS flow.
  • the size of the frame with high importance r2*the GFBR requirement of the service/(r2*FPS*r1+ FPS(1-r1)).
  • PDB is the packet delay budget (packet delay budget).
  • the second MDBV of the first QoS flow is determined according to the length of the PDB and the size of the frame with high importance.
  • the second MDBV of the first QoS flow size of high importance frame*PDB/(1000/Fps).
  • the second MDBV of the first QoS flow n*high importance frame size.
  • the second MDBV of the first QoS flow n*the size of the frame with high importance+importance The size of the high-degree frame*(PDB-n*frame ratio period)/(1000/Fps).
  • the frame ratio period is determined according to the ratio of frames with high importance to frames with low importance, and n is an integer greater than or equal to 1.
  • the second GFBR of the second QoS flow the GFBR requirement of the service-the second GFBR of the first QoS flow.
  • the first network device determines the first QoS parameter of the first QoS flow according to the second message, or determines the first QoS parameter of the first QoS flow and the second QoS flow The first QoS parameter of .
  • the second message includes a second parameter
  • the first network device determines the first QoS parameter of the first QoS flow according to the second parameter.
  • the first network device determines according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service The first QoS parameter of the first QoS flow.
  • the description of determining the first QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service refer to the above-mentioned second periodical information about the service of the terminal device according to the service of the terminal device.
  • the periodical information and the information of the layered transmission of the service determine the description of the second QoS parameter of the first QoS flow.
  • this application will not repeat them here.
  • the first network device determines the first QoS parameter of the first QoS flow according to the second QoS parameter of the first QoS flow.
  • the second message includes the third parameter
  • the first network device determines the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow according to the second message.
  • the first network device determines according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service The first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • the terminal device determines the second QoS parameter of the first QoS flow and the description of the second QoS parameter of the second QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service.
  • this application I won't repeat them here.
  • the third parameter is the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the first network device according to the second QoS parameter and the second QoS parameter of the first QoS flow
  • the second QoS parameter of the second QoS flow determines the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • the first network device also determines the usage mechanism of the QoS flow according to the second message, that is, the second QoS flow only transmits the data of the (XR) service of the terminal device, or the second QoS flow not only transmits the (XR) service data of the terminal device business data, and also transmit data from other businesses.
  • the first network device sends a message including the first inactivity duration information of the first session to the terminal device.
  • the terminal device receives a message from the first network device including the first inactivity duration information of the first session.
  • the first network device sends a message including information about the first inactivity duration of the first session to the terminal device, so that the terminal device monitors whether the duration of the first session without data transmission reaches the first session of the first session. Duration of inactivity. S411. In a case where the duration of no data transmission of the first session reaches the first inactivity duration of the first session, the terminal device deactivates the user plane connection of the first session.
  • the terminal device monitors the duration of the first session without data transmission according to the first inactivity duration of the first session, and when the duration of no data transmission of the first session reaches the first inactivity of the first session In the case of the duration, the terminal device deactivates the user plane connection of the first session.
  • deactivating the user plane connection of the first session refers to releasing the radio bearer between the terminal device corresponding to the first session and the second network device (base station), and the connection between the second network device (base station) and the third network device ( UPF entities), the terminal device deactivates the user plane connection of the first session by releasing the radio bearer corresponding to the first session.
  • the second network device (base station) and the third network device (UPF entity) perform the following operations to deactivate the user plane connection of the first session:
  • the second network device (base station): release the tunnel info of the UPF entity end corresponding to the first session, including the IP address and the tunnel port number of the UPF entity, and release the radio bearer corresponding to the first session.
  • the third network device release the tunnel info corresponding to the AN end of the first session, including the IP address of the base station and the tunnel port number.
  • releasing the user plane connection of the first session is to release all the user plane connections corresponding to the QoS flow included in the first session, because the above-mentioned tunnel info and radio bearer configuration PDU sessions are configured with QoS flow granularity.
  • the terminal device When the duration of no data transmission of the first session reaches the first inactivity duration of the first session, the terminal device sends an indication to the first network device that the first session is inactive, and/or requests to deactivate the first session. Messages for the session's user plane connection.
  • the first network device receives a message from the terminal device indicating that the first session is inactive, and/or requesting to deactivate the user plane connection of the first session.
  • the terminal device monitors the duration of the first session without data transmission according to the first inactivity duration of the first session, and when the duration of no data transmission of the first session reaches the first inactivity of the first session In the case of the duration, a message indicating that the first session is inactive, and/or requesting to deactivate the user plane connection of the first session is sent to the first network device.
  • the message is a report message that the duration of no data transmission of the first session reaches the first inactive duration of the first session, in other words, it is also used to indicate that the first session meets the reporting condition.
  • deactivating the user plane connection of the first session refers to releasing the radio bearer between the terminal equipment corresponding to the first session and the base station, and the user plane connection between the base station and the UPF entity.
  • the first network device sends a message indicating to deactivate the user plane connection of the first session to the second network device and/or the third network device.
  • the second network device and/or the third network device receives a message from the first network device indicating to deactivate the user plane connection of the first session.
  • the first network device after receiving the message indicating that the first session is inactive and/or requesting to deactivate the user plane connection of the first session, the first network device sends a message to the second network device and/or the third network device A message indicating to deactivate the user plane connection of the first session.
  • the first network device after receiving the message indicating that the first session is inactive, and/or requesting to deactivate the user plane connection of the first session, the first network device sends an instruction to deactivate to the second network device and/or the third network device A message about the user plane connection of the first session.
  • the first network device sends a message indicating to deactivate the user plane connection of the first session by sending an N2 message to the second network device.
  • the first network device sends a message indicating to deactivate the user plane connection of the first session by sending an N4 session modification message to the third network device.
  • the second network device sends a message indicating to deactivate the user plane connection of the first session to the terminal device.
  • the terminal device receives a message from the second network device indicating to deactivate the user plane connection of the first session.
  • the second network device after receiving the message from the first network device indicating to deactivate the user plane connection of the first session, the second network device sends to the terminal device a message indicating to deactivate the user plane connection of the first session.
  • the terminal device deactivates the user plane connection of the first session after receiving the message from the second network device indicating to deactivate the user plane connection of the first session.
  • S405 to S409 and S410 to S414 are two independent solutions, if S405 to S409 is executed, then S410 to S414 will not be executed; if S410 to S414 is executed, then S405 to S409 will not be executed.
  • the first inactive duration of the first QoS flow or the first inactive duration of the first session determined directly or indirectly through the first periodic information of the service of the terminal device, enables the first QoS flow to be released in time , or the user plane connection of the first session is deactivated in time, thereby saving network resources.
  • the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow determined directly or indirectly through the second periodic information of the service of the terminal device, thereby
  • the first QoS flow, or the QoS parameters of the first QoS flow and the second QoS flow are determined based on the service requirement information and the layered transmission information, so as to improve the utilization efficiency of network resources.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, the display of the frame may be affected, such as a longer period of frame freezing.
  • data burst characteristics such as XR services
  • the transmission performance of services can be improved, the impact of frame loss caused by the transmission process can be reduced, the time of picture freezing can be improved, and user experience can be improved.
  • FIG. 5 is a schematic diagram of a session management method 500 proposed by an embodiment of the present application. As shown in Figure 5, the method 500 includes the following steps:
  • the terminal device generates a second message.
  • the terminal device generates a second message including the second parameter or the third parameter.
  • the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow
  • the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow
  • the first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow
  • the first QoS parameter of the second QoS flow includes the first QoS parameter of the second QoS flow. At least one of GFBR, first MFBR, or first MDBV.
  • both the first QoS flow and the second QoS flow are used to transmit service data of the terminal equipment.
  • the second message includes the second parameter or the third parameter, and the second parameter and the third parameter
  • the second parameter and the third parameter refer to the above S409 about the second message including the second parameter or the third parameter, and the second parameter and the first parameter.
  • the description of the three parameters will not be repeated in this application.
  • the terminal device sends a second message to the first network device.
  • the first network device receives the second message from the terminal device.
  • the terminal device sends a second message to the first network device
  • the first network device determines the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow according to the second message.
  • the first network device determines the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow according to the second message.
  • the first network device determines the first QoS parameter of the first QoS flow according to the second message, or determines the first QoS parameter of the first QoS flow and the second QoS flow.
  • the first QoS parameter of the first QoS flow determined directly or indirectly through the second periodic information of the service of the terminal device, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow , so as to determine the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow based on the information of business requirements and the information of layered transmission, so as to improve the utilization of network resources efficiency.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, the display of the frame may be affected, such as a longer period of frame freezing.
  • data burst characteristics such as XR services
  • the transmission performance of services can be improved, the impact of frame loss caused by the transmission process can be reduced, the time of picture freezing can be improved, and user experience can be improved.
  • FIG. 6 is a schematic diagram of a session management method 600 provided by an embodiment of the present application. As shown in FIG. 6, the method 600 includes the following steps:
  • the terminal device establishes an interface (socket) connection with the XR server.
  • the terminal device starts the XR application, and establishes an interface (socket) connection with the XR server.
  • the terminal device establishes an interface (socket) connection with the XR server, and performs application-layer media negotiation, for example, negotiates the periodical information of the XR media stream service of the terminal device through a hypertext transfer protocol (hypertext transfer protocol, HTTP) .
  • HTTP hypertext transfer protocol
  • the terminal device sends a message including the first parameter to the AMF entity.
  • the AMF entity receives the message including the first parameter from the terminal device.
  • the terminal device determines that the first Qos flow is a GBR QoS flow, and sends a message including the first parameter to the AMF entity.
  • the first parameter is used by the first network device to determine the first inactive duration of the first QoS flow of the terminal device, or is used by the first network device to determine the first inactive duration of the first session of the terminal device.
  • the first inactive duration of the first QoS flow represents the first duration of continuous no data transmission of the first QoS flow
  • the first inactive duration of the first session represents the first duration of continuous no data transmission of the first session
  • the first QoS flow or the first session is data used to transmit services of the terminal equipment.
  • the first inactive duration of the first QoS flow is used for determining to release the first Qos flow
  • the first inactive duration of the first session is used for determining to release the user plane connection of the first session.
  • the terminal device sends a session modification request message to the AMF entity, and the session request message carries the first parameter, the QoS requirement, and the information of the five-tuple (packet filter) related to the service of the terminal device.
  • the session request message carries the first parameter, the QoS requirement, and the information of the five-tuple (packet filter) related to the service of the terminal device.
  • the AMF entity invokes the service and sends the first parameter to the SMF entity.
  • the SMF entity receives the first parameter from the AMF entity calling the service.
  • the AMF entity invokes a service to send the first parameter to the SMF entity.
  • the XR server triggers the PCF entity to initiate a modification process related to the SM policy.
  • the XR server sends a message including the first parameter to the PCF entity, and then the PCF entity initiates an SM policy-related modification process. It should be noted that the XR server sends the PCF The entity sends a message including the first parameter, which is sent directly to the PCF entity by the XR server, or sent to the PCF entity through the NEF entity.
  • the XR server carries the first parameter, QoS requirement, and quintuple (packet filter) parameters related to the service of the terminal device in the message sent to the PCF entity, and the PCF entity invokes the service to send the first parameter, QoS requirement to the SMF , and the five-tuple (packet filter) parameters related to the service of the terminal device, wherein the service invoked by the PCF is Npcf_SMPolicyControl_UpdateNotify.
  • the SMF entity determines the first inactive duration of the first QoS flow, or determines the first inactive duration of the first session.
  • the SMF entity determines the first inactive duration of the first QoS flow according to the first parameter, or determines the first inactive duration of the first session.
  • the SMF entity determines to determine the first inactive duration of the first QoS flow according to the first parameter, or determines the first inactive duration of the first session, refer to the above S403 about the first network device according to the first parameter, The description of determining the first inactive duration of the first QoS flow, or determining the first inactive duration of the first session is omitted in this application for brevity.
  • the SMF entity sends a message including the first inactivity duration of the first QoS flow, or a message including the first inactivity duration of the first session, to the terminal device, and/or the base station, and/or the UPF entity.
  • the terminal device, and/or the base station, and/or the UPF entity receives the message including the first inactivity duration of the first QoS flow, or the message including the first inactivity duration of the first session from the SMF entity.
  • the SMF entity determines the first inactive duration of the first QoS flow, or the first inactive duration of the first session, it sends a message containing the first QoS flow to the terminal device, and/or the base station, and/or the UPF entity.
  • the terminal device monitors the inactivity duration of the first QoS flow, or the inactivity duration of the first session.
  • the terminal device monitors the inactivity of the first QoS flow according to the above message.
  • the active duration, or the inactive duration of the first session is the active duration, or the inactive duration of the first session.
  • the terminal device monitors whether the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow according to the message of the first inactivity duration of the first QoS flow, or according to the first session of the first session A message of an inactive duration, monitoring whether the duration of no data transmission of the first session reaches the first inactive duration of the first session.
  • the base station monitors the inactive duration of the first QoS flow, or the inactive duration of the first session.
  • the base station monitors the inactivity of the first QoS flow according to the above message duration, or the duration of inactivity for the first session.
  • the base station monitors whether the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow according to the message of the first inactivity duration of the first QoS flow, or according to the first
  • the message of the inactive duration monitors whether the duration of no data transmission of the first session reaches the first inactive duration of the first session.
  • the UPF entity monitors the inactive duration of the first QoS flow, or the inactive duration of the first session.
  • the UPF entity receives the message from the SMF that includes the first inactive duration of the first QoS flow, or the message that includes the first inactive duration of the first session, it monitors the inactivity of the first QoS flow according to the above message.
  • the active duration, or the inactive duration of the first session is the active duration, or the inactive duration of the first session.
  • the UPF entity monitors whether the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow according to the message of the first inactivity duration of the first QoS flow, or according to the first session of the first session A message of an inactive duration, monitoring whether the duration of no data transmission of the first session reaches the first inactive duration of the first session.
  • S607a, S607b, and S607c are three independent steps.
  • the terminal device, and/or the base station, and/or the UPF entity sends a message indicating that the first QoS flow is inactive, and/or, requesting release of the first QoS flow, or indicating that the first session is inactive, to the SMF entity, and/or Or, a message requesting to deactivate the user plane connection of the first session.
  • the SMF entity receives a message from the terminal device, and/or the base station, and/or the UPF entity indicating that the first QoS flow is inactive, and/or requests to release the first QoS flow, or indicates that the first session is inactive, And/or, a message requesting to deactivate the user plane connection of the first session.
  • the terminal device and/or the base station, and/or the UPF entity sends an indication to the SMF entity when the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow.
  • a QoS flow is inactive, and/or, a message requesting to release the first QoS flow; or when the duration of no data transmission of the first session reaches the first inactive duration of the first session, send an indication to the SMF entity
  • a session is inactive, and/or, a message requesting to deactivate the user plane connection of the first session.
  • the UPF entity sends the message to the SMF entity in the form of an N4 report (N4report) message.
  • the message is represented as a report message that the duration of no data transmission of the first QoS flow reaches the first inactive duration of the first QoS flow, and also includes the QoS flow identifier (QFI) information of the first QoS flow, in other words, also used It is used to indicate that the first QoS flow satisfies the reporting condition; or, the message is represented as a report message that the duration of no data transmission of the first session reaches the first inactive duration of the first session, indicating that the first session meets the reporting condition.
  • QFI QoS flow identifier
  • the terminal device sends a report message that the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow to the SMF entity, thereby indicating that the first QoS flow is inactive, And/or, request to release the first QoS flow; or send a report message to the SMF entity that the duration of no data transmission of the first session reaches the first inactive duration of the first session, thereby indicating that the first session is inactive, and/or , requesting to deactivate the user plane connection of the first session.
  • the base station sends a report message that the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow to the SMF entity, thereby indicating that the first QoS flow is inactive, and /or, request to release the first QoS flow; or send a report message to the SMF entity that the duration of no data transmission of the first session reaches the first inactive duration of the first session, thereby indicating that the first session is inactive, and/or, Request to deactivate the user plane connection for the first session.
  • the SMF entity determines to release the first QoS flow, or deactivates the user plane connection of the first session.
  • the SMF entity determines whether there is an associated QoS flow for the first QoS flow to be released according to the message indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow, and determines to release the first QoS flow. QoS flow; or, the SMF entity determines to deactivate the user plane connection of the first session according to the message indicating that the first session is inactive, and/or requesting to deactivate the user plane connection of the first session.
  • the SMF entity sends a message for instructing release of the first QoS flow to the terminal device, and/or the base station, and/or the UPF entity.
  • the SMF entity when it is determined to release the first QoS flow, the SMF entity sends a message for instructing release of the first QoS flow to the terminal device, and/or the base station, and/or the UPF entity.
  • the SMF entity sends a message for instructing release of the first QoS flow by sending a PDU session modification message to the terminal device.
  • the SMF entity sends a message for instructing release of the first QoS flow by sending an N2 message to the base station.
  • the SMF entity sends a message for instructing release of the first QoS flow by sending an N4 session modification message to the UPF entity.
  • the terminal device performs a first operation.
  • the terminal device performs a first operation, and the first operation includes releasing a first QoS flow, or deactivating a user plane connection of a second QoS flow associated with the first QoS flow.
  • the terminal device monitors the inactivity duration of the first QoS flow, and when the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the terminal device Release the first QoS flow, or deactivate the user plane connection of the second QoS flow associated with the first QoS flow.
  • the first QoS flow has a second QoS flow associated therewith, and the terminal device deletes the association relationship between the first QoS flow and the second QoS flow, or releases the second QoS flow associated with the first QoS flow .
  • both the first QoS flow and the second QoS flow are used to transmit service data of the terminal device, the first QoS flow transmits data with high importance in the service, and the second QoS flow transmits data with low importance in the service data.
  • the terminal device directly releases the first QoS flow.
  • the terminal device performs the first operation by receiving a message sent by the SMF entity for instructing to release the first QoS flow.
  • the base station performs a first operation.
  • the base station performs a first operation, and the first operation includes releasing the first QoS flow, or deactivating a user plane connection of the second QoS flow associated with the first QoS flow.
  • the UPF entity performs a first operation, and the first operation includes releasing the first QoS flow, or deactivating the user plane connection of the second QoS flow associated with the first QoS flow.
  • the SMF entity sends a message indicating to deactivate the user plane connection of the first session to the base station and/or the UPF entity.
  • the base station and/or the UPF entity receives a message from the SMF entity indicating to deactivate the user plane connection of the first session.
  • the SMF entity sends a message to the base station and/UPF entity indicating to deactivate the user plane connection of the first session.
  • the SMF entity sends a message indicating to deactivate the user plane connection of the first session by sending an N4 session modification message to the UPF entity.
  • the base station sends a message, such as an RRC reconfiguration message, indicating to deactivate the user plane connection of the first session to the terminal device.
  • the terminal device receives a message from the base station indicating to deactivate the user plane connection of the first session.
  • the base station after receiving the message from the SMF entity indicating to deactivate the user plane connection of the first session, the base station sends the message indicating to deactivate the user plane connection of the first session to the terminal device.
  • the terminal device performs a second operation.
  • the terminal device performs a second operation, and the second operation includes deactivating the user plane connection of the first session, or deleting the association relationship between the first session and the second session, where both the first session and the second session are used for To transmit service data of the terminal device, the first session transmits data of high importance in the service, and the second session transmits data of low importance in the service.
  • the terminal device monitors the inactivity duration of the first session, and when the duration of no data transmission in the first session reaches the first inactivity duration of the first session, the terminal device deactivates the first session. User plane connection of a session, or delete the association relationship between the first session and the second session.
  • the terminal device deactivates the user plane connection of the first session, or deletes the connection between the first session and the second Session association.
  • the terminal device deactivates the user plane connection of the first session by releasing the radio bearer corresponding to the first session.
  • the base station performs a second operation.
  • the base station After receiving the message sent by the SMF entity indicating to deactivate the user plane connection of the first session, the base station performs a second operation.
  • the second operation refer to the description about the second operation in S614a above.
  • the base station deactivates the user plane connection of the first session by releasing the tunnel info (including the IP address and the tunnel port number of the UPF entity) of the UPF entity corresponding to the first session, and releasing the radio bearer corresponding to the first session.
  • the tunnel info including the IP address and the tunnel port number of the UPF entity
  • the UPF entity After receiving the message sent by the SMF entity indicating to deactivate the user plane connection of the first session, the UPF entity performs the second operation.
  • the second operation refer to the description about the second operation in S614a above.
  • the UPF entity releases the tunnel info (including the IP address of the base station and the tunnel port number) corresponding to the AN end of the first session, thereby deactivating the user plane connection of the first session.
  • releasing the user plane connection of the first session is to release all the user plane connections corresponding to the QoS flow included in the first session, because the above-mentioned tunnel info and radio bearer configuration PDU sessions are configured with QoS flow granularity.
  • the terminal device or the XR server determines to use the first QoS flow (GBR QoS flow), determine the second inactive duration of the first QoS flow or the first session of the first session according to the first periodic information of the service of the terminal device
  • the second inactive duration is sent to the SMF entity, and the SMF entity determines the first inactive duration of the first QoS flow or the first session of the first session based on the request of the terminal device or the XR server in combination with network policies (network quality Jitter, network load).
  • network policies network quality Jitter, network load
  • the SMF entity sends the message containing the first inactive duration information of the first QoS flow or the message containing the first inactive duration information of the first session to the terminal device, and/or the UPF entity, and/or the base station, to request the terminal
  • the device, and/or UPF entity, and/or the base station monitors the duration of no data transmission of the first QoS flow, or the duration of no data transmission of the first session, if the duration of no data transmission of the first QoS flow reaches the first QoS
  • the first inactive duration of flow execute the first operation, or report the event to the SMF entity, and the SMF entity determines to release the first QoS flow (GBR QoS flow) and renews the QoS flow associated therewith (the second QoS flow); Or if the duration of no data transmission of the first session reaches the first inactivity duration of the first session, the event is reported to the SMF entity, and the SMF entity determines to deactivate the user plane connection of the first session.
  • the SMF entity sends a message indicating to release the first QoS flow to the terminal device, and/or the UPF entity, and/or the base station, so that the terminal device, and/or the UPF entity, and/or the base station perform the first operation in time, or send an instruction
  • a message to deactivate the user plane connection of the first session is sent to the second network device, so that the second network device sends a message indicating to deactivate the user plane connection of the first session to the terminal device, so that the terminal device performs the second operation in time, saving the network resource.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, the display of the frame may be affected, such as a longer period of frame freezing.
  • data burst characteristics such as XR services
  • the display of the frame may be affected, such as a longer period of frame freezing.
  • FIG. 7 is a schematic diagram of a session management method 700 provided by an embodiment of the present application. As shown in FIG. 7, the method 700 includes the following steps:
  • the terminal device determines the termination of the service of the terminal device.
  • the terminal device determines the termination of the service of the terminal device.
  • the terminal device determines the termination of the service of the terminal device through its internal application to the modem, that is, through the method 800 for determining the termination of the service of the terminal device.
  • FIG. 8 is a schematic diagram of a method 800 for determining service termination of a terminal device. Wherein, as shown in FIG. 8, the method 800 includes the following steps:
  • the modem determines to establish a GBR QoS flow.
  • the modem determines to establish a GBR QoS flow (first QoS flow).
  • the modem sends to the application the information of stopping the application program bound with the subscription or the information of turning to the background.
  • the application receives from the modem the information of stopping the application program bound with the subscription or going to the background.
  • the modem determines to establish the GBR QoS flow (the first QoS flow), it sends to the application the stop information of the application program bound by subscription or the information of turning to the background, and the information indicates that the subscribed event is a stop of service detection (stop of service detection), the connection identifier is an IP address, or a session ID (session ID), or the five-tuple (packet filter) information associated with a session (session), or other identifiers used internally by the terminal device for connection.
  • stop of service detection the connection identifier is an IP address, or a session ID (session ID), or the five-tuple (packet filter) information associated with a session (session), or other identifiers used internally by the terminal device for connection.
  • the application determines that the application program is terminated or transferred to the background.
  • the application terminates or enters the background.
  • the application sends notification information to the modem.
  • the modem receives notification information from the application.
  • the application determines that the application program is terminated or transferred to the background, it sends notification information to the modem, notifying the modem that the application has terminated or transferred the application program to the background.
  • the notification information includes the information of the stop service detection, the information of the connection identification, or the quintuple (packet filter) information associated with the session (session).
  • the modem initiates a session modification process, and releases the corresponding GBR QoS flow.
  • the modem after receiving the notification information, the modem initiates a session modification procedure.
  • the terminal device does not need the interaction between the internal application and the modem, and determines the second period of the GBR QoS flow (first QoS flow) according to the first periodic information of the (XR) service of the terminal device. After the inactivity period, monitor the inactivity of the GBR QoS flow (the first QoS flow), and the duration of the continuous no data transmission of the GBR QoS flow (the first QoS flow) reaches the second of the GBR QoS flow (the first QoS flow). In the case of inactivity, initiate the session modification process.
  • the first periodic information of the (XR) service of the terminal device refer to the description of the first periodic information of the service of the terminal device in S401 above. For the sake of brevity, the present application will not repeat it here.
  • the XR server determines the termination of the service of the terminal device.
  • the XR server determines the termination of service of the terminal device.
  • the SMF entity receives a message indicating that the first QoS flow is inactive, and/or requests to release the first QoS flow.
  • the SMF entity receives a message from the terminal device or the XR server indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow.
  • the terminal device sends an indication to the SMF entity that the first QoS flow is inactive when the duration of the first QoS flow without data transmission reaches the second inactivity duration of the first QoS flow, And/or, a message requesting to release the first QoS flow.
  • the SMF entity receives a message from the terminal device indicating that the first QoS flow is inactive, and/or requesting to release the first QoS flow.
  • the terminal device sends to the SMF entity a report message indicating that the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, thereby indicating that the first QoS flow is inactive, and/or, requesting to release the first QoS flow.
  • a QoS flow indicating that the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, thereby indicating that the first QoS flow is inactive, and/or, requesting to release the first QoS flow.
  • the XR server determines that the service of the terminal device is terminated, it sends an AF notification message to the policy control function (policy control function, PCF) entity to the SMF entity, so that the PCF entity sends an AF notification message to the SMF entity.
  • policy control function policy control function
  • PCF policy control function
  • the SM policy association modification message triggers the SMF entity to release the first QoS flow. It is understood that the SMF entity receives a message indicating that the first QoS flow is inactive, and/or requests to release the first QoS flow.
  • the SMF entity determines to release the first QoS flow.
  • the SMF entity determines whether there is an associated QoS flow for the first QoS flow to be released according to the message indicating that the first QoS flow is inactive, and/or requests to release the first QoS flow, and determines to release the first QoS flow.
  • the SMF entity sends a message for instructing release of the first QoS flow to the terminal device, and/or the base station, and/or the UPF entity.
  • the SMF entity determines to release the first QoS flow, it sends a message for instructing release of the first QoS flow to the terminal device, and/or the base station, and/or the UPF entity.
  • the SMF entity sends a message for instructing release of the first QoS flow by sending a PDU session modification message to the terminal device.
  • the SMF entity sends a message for instructing release of the first QoS flow by sending an N4 session modification message to the UPF entity.
  • the terminal device performs a first operation.
  • the terminal device performs a first operation, and the first operation includes releasing a first QoS flow, or deactivating a user plane connection of a second QoS flow associated with the first QoS flow.
  • the base station performs a first operation.
  • the base station performs a first operation, and the first operation includes releasing the first QoS flow, or deactivating a user plane connection of the second QoS flow associated with the first QoS flow.
  • the UPF entity performs the first operation.
  • the UPF entity performs a first operation, and the first operation includes releasing the first QoS flow, or deactivating the user plane connection of the second QoS flow associated with the first QoS flow.
  • the terminal device releases the first QoS flow (GBR QoS flow) after determining that the service using the first QoS flow (GBR QoS flow) is terminated.
  • the modem of the terminal device in the process that the terminal device determines that the service using the first QoS flow (GBR QoS flow) is terminated, the modem of the terminal device establishes a PDU session with the first QoS flow (GBR QoS flow), subscribes and binds to the application of the terminal device
  • the application program of the terminal device terminates or transfers to the background information, and the application of the terminal device triggers the modification of the PDU session after receiving the notification.
  • network resources are saved.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, the display of the frame may be affected, such as a longer period of frame freezing.
  • data burst characteristics such as XR services
  • the display of the frame may be affected, such as a longer period of frame freezing.
  • FIG. 9 is a schematic diagram of a session management method 900 provided by an embodiment of the present application. As shown in Figure 9, the method 900 includes the following steps:
  • the terminal device establishes an interface (socket) connection with the XR server.
  • the terminal device starts the XR application, and establishes an interface (socket) connection with the XR server.
  • the terminal device establishes an interface (socket) connection with the XR server, and performs application-layer media negotiation, for example, negotiates the periodical information of the XR media stream service of the terminal device through a hypertext transfer protocol (hypertext transfer protocol, HTTP) .
  • HTTP hypertext transfer protocol
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodical information of the service of the terminal device and the information of the layered transmission of the service, or the second QoS parameter of the first QoS flow and the second QoS flow The second QoS parameter of .
  • the terminal device determines the second QoS parameter of the first QoS flow, or the second QoS parameter of the first QoS flow and the second QoS The second QoS parameter of the flow.
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodical information of the service of the terminal device and the information of the layered transmission of the service, or the second QoS parameter of the first QoS flow is combined with the second
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the first
  • the description of the second QoS parameter of the QoS flow and the second QoS parameter of the second QoS flow is omitted in this application for the sake of brevity.
  • the XR server determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the second QoS parameter of the first QoS flow and the second QoS flow The second QoS parameter of .
  • the XR server determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the second QoS parameter of the first QoS flow and the second QoS The second QoS parameter of the flow.
  • the XR server determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the second QoS parameter of the first QoS flow and the second
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the first
  • the description of the second QoS parameter of the QoS flow and the second QoS parameter of the second QoS flow is omitted in this application for the sake of brevity.
  • the terminal device sends a message including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, to the AMF entity.
  • the AMF entity receives a message from the terminal device including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow.
  • the terminal device After determining the second QoS parameter of the first QoS flow, the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, the terminal device sends the second QoS parameter containing the first QoS flow to the AMF entity.
  • a message of the QoS parameter or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow.
  • the terminal device sends a PDU session modification request message to the AMF entity, including the above parameter information.
  • the AMF entity sends a message including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, to the SMF entity.
  • the SMF entity receives a message from the AMF entity including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow.
  • the AMF entity sends a message including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, to the SMF entity.
  • the AMF entity sends a PDU session SM context update message to the SMF entity, including the above parameter information.
  • the XR server sends a message including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, to the SMF entity.
  • the SMF entity receives a message from the XR server including the second QoS parameter of the first QoS flow, or a message including the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow.
  • the XR server determines the second QoS parameter of the first QoS flow, or the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the XR server sends the second QoS parameter containing the first QoS flow to the SMF entity.
  • the XR server initiates the SM policy association modification process to the SMF entity, and carries the information of the above parameters in the request message.
  • the SMF entity determines the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • the SMF entity determines the second QoS parameter of the first QoS flow according to the second QoS parameter of the first QoS flow, or the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, and network policy information, and determines the second QoS parameter of the first QoS flow.
  • a QoS parameter, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow are examples of the SMF entity.
  • the SMF entity also determines the use mechanism of the QoS flow according to the first QoS parameter information of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter information of the second QoS flow, that is, the second QoS flow
  • the flow only transmits the data of the (XR) service of the terminal device, or the second QoS flow not only transmits the data of the (XR) service of the terminal device, but also transmits the data of other services.
  • the SMF entity invokes the service and sends the fourth parameter to the AMF entity.
  • the AMF entity receives the fourth parameter from the SMF entity calling the service.
  • the SMF entity calls the service and sends the fourth parameter to the AMF entity, where the fourth parameter includes the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow , and indicates that the first QoS flow is associated with the second QoS flow.
  • the service provided by the AMF entity is Namf_Communication_N1N2MessageTransfer, where N1 SM container is what the SMF entity will send to the terminal device through the AMF entity, N2 SM information is what the SMF entity will send to the base station through the AMF entity, and the fourth parameter is included in N2 SM information middle.
  • the N1 SM container also sends the parameters of the first QoS flow and the second QoS flow, as well as the association relationship, to the terminal device.
  • the fourth parameter also includes first indication information, where the first indication information is used to indicate whether the data transmitted by the second QoS flow is only data associated with the first QoS flow, that is, the second QoS flow only To transmit the data of the XR service of the terminal device, or to transmit the data of the XR service of the terminal device and the data of other services, if the second QoS flow simultaneously transmits the data of the XR service of the terminal device and the data of other services, the wireless access network (RAN) equipment needs to analyze the packet header of the subsequent data packet received from the second QoS flow (for example, the transmission protocol between the UPF entity and the RAN usually uses the GTP protocol, which is whether the GTP user plane data packet header (GTP-U header) carries the first Two indication information, wherein the second indication information is used to indicate whether the data packet is associated with the data packet transmitted by the first QoS flow. If the second QoS flow only transmits the data of the XR service of the terminal device, the RAN device does
  • the AMF entity sends an N2 message to the base station.
  • the base station receives the N2 message from the AMF entity.
  • the AMF entity after receiving the fourth message sent from the SMF entity, the AMF entity sends an N2 message to the base station, where the N2 message includes the first indication information.
  • the base station sends the AN message to the terminal device.
  • the terminal device receives the AN message from the base station.
  • the base station after receiving the N2 message from the AMF entity, the base station sends an AN message to the terminal device, and the AN message includes the information of the N1 SM container, that is, the information including the session modification instruction.
  • the AMF entity sends an N1 message to the terminal device.
  • the terminal device receives the N1 message from the AMF entity.
  • the AMF entity after receiving the fourth message sent from the SMF entity, the AMF entity sends an N1 message to the terminal device, where the N1 message includes the first indication information.
  • the AMF entity sends the above N1 message to the terminal device through the base station.
  • the SMF entity sends an N4 session modification request message to the UPF entity.
  • the UPF entity receives the N4 session modification request message from the SMF entity.
  • the SMF entity sends the N4 session modification request message to the UPF entity, and the message includes the first QoS parameter information of the first QoS flow and the first QoS parameter information of the second QoS flow, and the information of the first QoS flow and the second QoS flow Information about the relationship.
  • the UPF entity sends the service data of the second QoS flow transmission including the second indication information to the base station.
  • the base station receives the service data of the second QoS stream transmission including the second indication information from the UPF entity.
  • the UPF after receiving the N4 session modification request message from the SMF entity, the UPF sends to the base station the data of the service of the second QoS flow transmission including the second indication information, thereby indicating whether the above data is consistent with the data of the first QoS flow transmission connection relation.
  • the terminal device or XR server determines the QoS parameters corresponding to each layer after layering according to the ratio of high-importance frames to low-importance frames, frame size ratio, service GFBR requirements, and frame rate, and sends to the SMF entity Make a request.
  • the SMF entity determines the use mechanism of the QoS flow based on the QoS parameters requested by the terminal device or the XR server, and determines the first QoS flow, or the QoS parameters corresponding to the first QoS flow and the second QoS flow, to improve network resource utilization efficiency.
  • the SMF entity sends the first indication information to the base station (RAN), which is used to indicate whether the data transmitted by the second QoS flow is only data associated with the first QoS flow, that is, the data transmitted by the second QoS flow is only Whether to transmit the data of the (XR) service of the terminal equipment, or to transmit the data of the (XR) service and other services; Carry the second indication information, if not, the RAN does not need to parse the header of the subsequent data packet received through the second QoS flow.
  • the second indication information is used to indicate whether the data packet is a data packet associated with the data packet transmitted by the first QoS flow.
  • the UPF entity adds the second indication information to the header of the data packet when sending the data mapped to the second QoS flow to the RAN. For example, when the second indication information is 1, it indicates that the data packet is a data packet associated with the data packet transmitted by the first QoS stream; when the second indication information is 0, it indicates that the data packet is associated with the first QoS stream Packets that are streamed are unrelated packets.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, the display of the frame may be affected, such as a longer period of frame freezing.
  • data burst characteristics such as XR services
  • the transmission performance of services can be improved, the impact of frame loss caused by the transmission process can be reduced, the time of picture freezing can be improved, and user experience can be improved.
  • FIG. 10 is a schematic diagram of a session management method 1000 provided by an embodiment of the present application. As shown in Figure 10, the method 1000 includes the following steps:
  • the terminal device establishes an interface (socket) connection with the XR server.
  • the terminal device starts the XR application, and establishes an interface (socket) connection with the XR server.
  • the terminal device establishes an interface (socket) connection with the XR server, and performs application layer media negotiation, for example, performs negotiation of periodic information of the XR media stream service of the terminal device through the hypertext transfer protocol.
  • application layer media negotiation for example, performs negotiation of periodic information of the XR media stream service of the terminal device through the hypertext transfer protocol.
  • the terminal device determines the first QoS parameter of the requested first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow according to the service requirement of the terminal device.
  • the terminal device After the terminal device establishes an interface connection with the XR server, according to the negotiation result, it determines to request the first QoS parameter of the first QoS flow from the SMF entity, or the first QoS parameter of the first QoS flow and the second QoS flow First QoS parameter.
  • the XR server determines the first QoS parameter of the requested first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow according to the service requirements of the terminal device.
  • the XR server After the XR server establishes an interface connection with the terminal device, according to the negotiation result, it determines to request the first QoS parameter of the first QoS flow from the SMF entity, or the first QoS parameter of the first QoS flow and the second QoS flow First QoS parameter.
  • the terminal device sends to the AMF entity the second periodic information including the service of the terminal device, the ratio information of the size of the frame with high importance to the size of the frame with low importance in the service, and the information of the GFBR requirement of the service news.
  • the AMF entity receives from the terminal device the second periodic information including the service of the terminal device, the ratio information of the size of the frame with high importance to the size of the frame with low importance in the service, and the GFBR requirement of the service message of information.
  • the terminal device After the terminal device determines the requested QoS parameters, it sends to the AMF entity the second periodical information including the service of the terminal device, the ratio of the size of the frame with high importance to the size of the frame with low importance in the service information, as well as informational messages on the business's GFBR needs.
  • the terminal device sends a PDU session modification request message to the AMF entity, including the above information.
  • the AMF entity sends to the SMF entity the second periodic information including the service of the terminal device, the ratio information of the size of the frame with high importance in the service and the size of the frame with low importance in the service, and the information of the GFBR requirement of the service news.
  • the SMF entity receives from the AMF entity the second periodical information including the service of the terminal device, the ratio information of the size of the frame with high importance in the service to the size of the frame with low importance, and the GFBR requirement of the service message of information.
  • the AMF entity receives the second periodical information of the service including the terminal device from the terminal device, the ratio information of the size of the frame with high importance in the service to the size of the frame with low importance in the service, and the GFBR of the service After the message of the required information, a message containing the above information is sent to the SMF entity.
  • the AMF entity sends a PDU session SM context update message to the SMF entity, including the above information.
  • the XR server sends to the SMF entity the second periodic information including the service of the terminal device, the ratio information of the size of the frame with high importance in the service to the size of the frame with low importance in the service, and the information of the GFBR requirement of the service news.
  • the SMF entity receives from the XR server the second periodic information including the service of the terminal device, the ratio information of the size of the frame with high importance in the service to the size of the frame with low importance, and the GFBR requirement of the service message of information.
  • the XR server determines the requested QoS parameters, it sends to the SMF entity the second periodic information including the service of the terminal device, the ratio of the size of the frame with high importance to the size of the frame with low importance in the service information, as well as informational messages on the business's GFBR needs.
  • the XR server initiates the SM policy association modification process to the SMF entity, and carries the information of the above parameters in the request message.
  • the SMF entity determines the message of the first QoS parameter of the first QoS flow according to the second periodic information of the service and the information of the layered transmission of the service, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow - QoS parameters.
  • the SMF entity determines the message of the first QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service, or the first QoS parameter of the first QoS flow and the second The first QoS parameter of the QoS flow.
  • the SMF determines the first QoS parameter of the first QoS flow, or the description of the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow
  • the first network device Determine the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS of the second QoS flow according to the second periodic information of the service of the terminal device and the information of the layered transmission of the service
  • the description of the parameters will not be repeated in this application.
  • the SMF entity determines the usage mechanism of the QoS flow.
  • the SMF entity determines the usage mechanism of the QoS flow, that is, the second QoS flow only transmits the data of the (XR) service of the terminal equipment, or the second QoS flow not only transmits the data of the (XR) service of the terminal equipment, but also transmits other business data.
  • the SMF entity invokes the service and sends the fourth parameter to the AMF entity.
  • the AMF entity receives the fourth parameter from the SMF entity calling the service.
  • the SMF entity calls the service and sends the fourth parameter to the AMF entity, where the fourth parameter includes the first QoS parameter of the first QoS flow, or the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow , and indicates that the first QoS flow is associated with the second QoS flow.
  • the fourth parameter also includes first indication information, where the first indication information is used to indicate whether the data transmitted by the second QoS flow is only data associated with the first QoS flow.
  • the service provided by the AMF entity is Namf_Communication_N1N2MessageTransfer, where N1 SM container is what the SMF entity will send to the terminal device through the AMF entity, N2 SM information is what the SMF entity will send to the base station through the AMF entity, and the fourth parameter is included in N2 SM information middle.
  • the N1 SM container also sends the parameters of the first QoS flow and the second QoS flow, as well as the association relationship, to the terminal device.
  • the AMF entity sends an N2 message to the base station.
  • the base station receives the N2 message from the AMF entity.
  • the AMF entity after receiving the fourth message sent from the SMF entity, the AMF entity sends an N2 message to the base station, where the N2 message includes the first indication information.
  • the base station sends an AN message to the terminal device.
  • the terminal device receives the AN message from the base station.
  • the base station after receiving the N2 message from the AMF entity, the base station sends an AN message to the terminal device, and the AN message includes the information of the N1 SM container, that is, the information including the session modification instruction.
  • the AMF entity sends an N1 message to the terminal device.
  • the terminal device receives the N1 message from the AMF entity.
  • the AMF entity after receiving the fourth message sent from the SMF entity, the AMF entity sends an N1 message to the terminal device, where the N1 message includes the first indication information.
  • the AMF entity sends the above N1 message to the terminal device through the base station.
  • the SMF entity sends an N4 session modification request message to the UPF entity.
  • the UPF entity receives the N4 session modification request message from the SMF entity.
  • the SMF entity sends the N4 session modification request message to the UPF entity, and the message includes the first QoS parameter information of the first QoS flow and the first QoS parameter information of the second QoS flow, and the information of the first QoS flow and the second QoS flow Information about the relationship.
  • the UPF entity sends the data of the service of the second QoS flow transmission including the second indication information to the base station.
  • the base station receives the service data of the second QoS stream transmission including the second indication information from the UPF entity.
  • the UPF after receiving the N4 session modification request message from the SMF entity, the UPF sends to the base station the data of the service of the second QoS flow transmission including the second indication information, thereby indicating whether the above data is consistent with the data of the first QoS flow transmission connection relation.
  • the description of the second indication information refer to the description of the second indication information in S907 above, and for the sake of brevity, the present application does not repeat it here.
  • the terminal device sends the second periodic information of the service to the SMF entity (such as the frame rate FPS, the ratio of frames with high importance to frames with low importance), information on frame size ratio, and information on service GFBR requirements, Make the SMF entity determine the QoS parameters corresponding to each layer based on business requirements and layer parameters, business GFBR requirements, and frame rate, and improve network resource utilization efficiency.
  • the SMF entity such as the frame rate FPS, the ratio of frames with high importance to frames with low importance
  • the SMF entity such as the frame rate FPS, the ratio of frames with high importance to frames with low importance
  • information on frame size ratio such as information on frame size ratio
  • service GFBR requirements such as the SMF entity.
  • the SMF entity sends the first indication information to the base station (RAN), which is used to indicate whether the data transmitted by the second QoS flow is only data associated with the first QoS flow, that is, the data transmitted by the second QoS flow is only Whether to transmit the data of the (XR) service of the terminal equipment, or to transmit the data of the (XR) service and other services; Carry the second indication information, if not, the RAN does not need to parse the header of the subsequent data packet received through the second QoS flow.
  • the second indication information is used to indicate whether the data packet is a data packet associated with the data packet transmitted by the first QoS flow.
  • the UPF entity adds the second indication information to the header of the data packet when sending the data mapped to the second QoS flow to the RAN. For example, when the second indication information is 1, it indicates that the data packet is a data packet associated with the data packet transmitted by the first QoS stream; when the second indication information is 0, it indicates that the data packet is associated with the first QoS stream Packets that are streamed are unrelated packets.
  • the terminal device when the terminal device is performing services with data burst characteristics, such as XR services, if a more important frame is lost, it may affect the display of the frame, such as a longer period of freezing of the picture.
  • data burst characteristics such as XR services
  • the transmission performance of services can be improved, the impact of frame loss caused by the transmission process can be reduced, the time of picture freezing can be improved, and user experience can be improved.
  • the methods and operations implemented by the terminal equipment are also implemented by components (such as chips or circuits) that can be used in the terminal equipment, and the methods and operations implemented by the network equipment are also implemented by the components that can be used in the network A component (such as a chip or a circuit) of a device implements it.
  • each network element such as a transmitting-end device or a receiving-end device, includes a corresponding hardware structure and/or software module for performing each function.
  • each network element such as a transmitting-end device or a receiving-end device
  • each network element includes a corresponding hardware structure and/or software module for performing each function.
  • the present application is implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementation should not be considered beyond the scope of the present application.
  • the embodiment of the present application divides the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, divides each functional module corresponding to each function, and also integrates two or more functions into one processing module.
  • the above-mentioned integrated modules are implemented not only in the form of hardware, but also in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there are other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • Fig. 11 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1100 includes a transceiver unit 1110 and a processing unit 1120 .
  • the transceiver unit 1110 implements corresponding communication functions, and the processing unit 1110 is used for data processing.
  • the transceiver unit 1110 is also referred to as a communication interface or a communication unit.
  • the communication device 1100 further includes a storage unit for storing instructions and/or data, and the processing unit 1120 reads the instructions and/or data in the storage unit, so that the communication device implements the aforementioned methods example.
  • the communication device 1100 is used to perform the actions performed by the terminal device in the above method embodiments.
  • the communication device 1100 is a terminal device or a component that can be configured in the terminal device, and the transceiver unit 1110 is used to perform the above method embodiments.
  • the processing unit 1120 is configured to perform operations related to processing on the terminal device side in the method embodiments above.
  • the communication device 1100 is used to perform the actions performed by the network device in the method embodiment above.
  • the communication device 1100 is a network device or a component that can be configured in the network device, and the transceiver unit 1110 is used to perform the above method
  • the processing unit 1120 is configured to perform operations related to processing on the network device side in the method embodiments above.
  • the communication device 1100 is used to execute the actions performed by the terminal device in the embodiment shown in FIG. 4 above, and the transceiver unit 1110 is used to: S402, S404, S406, S407, S409, S410, S412, S414;
  • the processing unit 1120 is used for: S401, S405, S408a, S411.
  • the communication device 1100 is used to execute the actions performed by the terminal device in the embodiment shown in Fig. 5 above, the transceiver unit 1110 is used for: S502; the processing unit 1120 is used for: S501.
  • the communication device 1100 is used to execute the actions performed by the terminal device in the embodiment shown in FIG. 6 above, and the transceiver unit 1110 is used for: In: S607a, S611a, S614a.
  • the communication device 1100 is configured to execute the actions performed by the terminal device in the embodiment shown in FIG. 7 above, the transceiver unit 1110 is configured to: S701a, S702, and S704; the processing unit 1120 is configured to: S705a.
  • the communication apparatus 1100 is used to execute the actions performed by the terminal device in the embodiment shown in FIG. 9 above, the transceiver unit 1110 is used for: S901, S903, S909, S910; the processing unit 1120 is used for: S902a.
  • the communication device 1100 is used to execute the actions performed by the terminal device in the embodiment shown in FIG. 10 above, the transceiver unit 1110 is used for: S1001, S1003, S1010, S1011; the processing unit 1120 is used for: S1002a.
  • the communication device 1100 can implement the steps or processes corresponding to the terminal equipment in the method 400 and the method 500 according to the embodiment of the present application, and the communication device 1100 includes a method for executing the method 400 in FIG. The unit of the method performed by the terminal device. Moreover, each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement the corresponding processes of the method 400 in FIG. 4 to the method 1000 in FIG. 10 .
  • the communication device 1100 is used to execute the actions performed by the first network device in the embodiment shown in FIG. S413:
  • the processing unit 1120 is configured to: S403.
  • the communication apparatus 1100 is configured to execute the actions executed by the first network device in the embodiment shown in FIG. 5 above, the transceiver unit 1110 is configured to: S502; the processing unit 1120 is configured to: S503.
  • the communication device 1100 can implement the steps or processes corresponding to the first network device in the method 400 and the method 500 according to the embodiment of the present application, and the communication device 1100 includes a method for executing the method 400 in FIG. 4 and the method in FIG. Elements of the method performed by the first network device in 500 . Moreover, each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement corresponding processes of the method 400 in FIG. 4 and the method 500 in FIG. 5 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the communication device 1100 is used to execute the actions performed by the second network device in the embodiment shown in FIG. In: S408b.
  • the communication apparatus 1100 can implement the steps or processes corresponding to the execution of the second network device in the method 400 according to the embodiment of the present application, and the communication apparatus 1100 includes a method for executing the method 400 in FIG. 4 executed by the second network device.
  • the unit of the method Moreover, each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement a corresponding flow of the method in FIG. 4 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the communication device 1100 is used to execute the actions performed by the third network device in the above embodiment shown in FIG. S408c.
  • the communication apparatus 1100 can implement the steps or processes corresponding to the steps or processes executed by the third network device in the method 400 according to the embodiment of the present application, and the communication apparatus 1100 includes a method for executing the third network device in the method 400 in FIG. 4 The unit of the method. Moreover, each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement a corresponding flow of the method in FIG. 4 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the communication device 1100 is used to execute the actions performed by the SMF entity in the embodiment shown in FIG. 1120 is used for: S605, S609.
  • the communication device 1100 is configured to execute the actions performed by the SMF entity in the embodiment shown in FIG. 7 above, the transceiver unit 1110 is configured to: S702, S704; the processing unit 1120 is configured to: S703.
  • the communication device 1100 is used to execute the actions performed by the SMF entity in the embodiment shown in FIG. 9 above, the transceiver unit 1110 is used for: S901, S904, S905, S907, S911; the processing unit 1120 is used for: S906 .
  • the communication device 1100 is used to execute the actions performed by the SMF entity in the embodiment shown in FIG. , S1007.
  • the communication device 1100 can implement the steps or processes corresponding to the SMF entity in the method 600, method 700, method 900, and method 1000 according to the embodiment of the present application, and the communication device 1100 includes a method for executing the method 600, Elements of the methods performed by the SMF entity in the method 700 in FIG. 7 , the method 900 in FIG. 9 , and the method 1000 in FIG. 10 .
  • each unit in the communication device 1100 and the other operations and/or functions mentioned above are respectively in order to realize the corresponding processes of the method 600 in FIG. 6 , the method 700 in FIG. 7 , the method 900 in FIG. 9 and the method 1000 in FIG. 10 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the communication device 1100 is used to execute the actions performed by the UPF entity in the embodiment shown in FIG. 6 above, the transceiver unit 1110 is used for: S606, S608, S610, S612; S611c, S614c.
  • the communication device 1100 is configured to execute the actions performed by the UPF entity in the embodiment shown in FIG. 7 above, the transceiver unit 1110 is configured to: S702, S704; the processing unit 1120 is configured to: S705c.
  • the communication device 1100 is configured to execute the actions performed by the UPF entity in the embodiment shown in FIG. 9 above, and the transceiver unit 1110 is configured to: S911, S912.
  • the communication device 1100 is configured to execute the actions performed by the UPF entity in the embodiment shown in FIG. 10 above, and the transceiver unit 1110 is configured to: S1012, S1013.
  • the communication device 1100 can implement the steps or processes corresponding to the UPF entity in the method 600, method 700, method 900, and method 1000 according to the embodiment of the present application, and the communication device 1100 includes a method for executing the method 600, Elements of the methods performed by the UPF entity in the method 700 in FIG. 7 , the method 900 in FIG. 9 , and the method 1000 in FIG. 10 .
  • each unit in the communication device 1100 and other operations and/or functions described above are respectively intended to implement the corresponding processes of the method 600 in FIG. 6 , the method 700 in FIG. 7 , the method 900 in FIG. 9 , and the method 1000 in FIG. 10 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the communication device 1100 can implement the steps or processes corresponding to the base station in the method 600, method 700, method 900, and method 1000 according to the embodiment of the present application, and the communication device 1100 includes a method for executing the method 600 and the method in FIG. Units of the methods performed by the base station in the method 700 in 7, the method 900 in FIG. 9 and the method 1000 in FIG. 10 .
  • each unit in the communication device 1100 and the other operations and/or functions mentioned above are respectively in order to realize the corresponding processes of the method 600 in FIG. 6 , the method 700 in FIG. 7 , the method 900 in FIG. 9 and the method 1000 in FIG. 10 .
  • the processing unit 1120 in the above embodiments is implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 is implemented by a transceiver or a transceiver-related circuit.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit is realized by at least one memory.
  • the embodiment of the present application further provides a communication device 1200 .
  • the communication device 1200 includes a processor 1210, the processor 1210 is coupled with a memory 1220, the memory 1220 is used for storing computer programs or instructions and/or data, and the processor 1210 is used for executing the computer programs or instructions and/or data stored in the memory 1220, The methods in the above method embodiments are executed.
  • the communication device 1200 includes one or more processors 1210 .
  • the communication device 1200 further includes a memory 1220 .
  • the communication device 1200 includes one or more memories 1220 .
  • the memory 1220 is integrated with the processor 1210, or is set separately.
  • the communication device 1200 further includes a transceiver 1230 for receiving and/or sending signals.
  • the processor 1210 is configured to control the transceiver 1230 to receive and/or send signals.
  • the communication apparatus 1200 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the terminal device in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the terminal device in the above method embodiments.
  • the communications apparatus 1200 is configured to implement the operations performed by the first network device in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the first network device in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the network device in the above method embodiments.
  • the communications apparatus 1200 is configured to implement the operations performed by the second network device in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the second network device in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the network device in the above method embodiments.
  • the communication device 1200 is configured to implement the operations performed by the SMF entity in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the SMF entity in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the network device in the above method embodiments.
  • the communication device 1200 is configured to implement the operations performed by the UPF entity in the above method embodiments.
  • the processor 1210 is configured to implement the processing-related operations performed by the UPF entity in the above method embodiments
  • the transceiver 1230 is configured to implement the transceiving-related operations performed by the network device in the above method embodiments.
  • the communication device 1200 is configured to implement the operations performed by the base station in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the base station in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the network device in the above method embodiments.
  • the embodiment of the present application also provides a communication device 1300, where the communication device 1300 is a terminal device and also a chip.
  • the communication apparatus 1300 is configured to perform the operations performed by the terminal device in the foregoing method embodiments.
  • FIG. 13 shows a schematic structural diagram of a simplified terminal device.
  • the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device.
  • the processor is mainly used to process communication protocols and communication data, control terminal equipment, execute software programs, and process data of software programs.
  • Memory is primarily used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal.
  • Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal equipment do not have input and output devices.
  • the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
  • Memory is also referred to as a storage medium or a storage device. The memory is configured independently of the processor, and is also integrated with the processor, which is not limited in this embodiment of the present application.
  • the antenna and the radio frequency circuit with the transceiver function are regarded as the transceiver unit of the terminal device, and the processor with the processing function is regarded as the processing unit of the terminal device.
  • the terminal device includes a transceiver unit 1310 and a processing unit 1320 .
  • the transceiver unit 1310 is also referred to as a transceiver, a transceiver, or a transceiver.
  • the processing unit 1320 is also called a processor, a processing board, a processing module, or a processing device.
  • the device used to realize the receiving function in the transceiver unit 1310 is regarded as a receiving unit
  • the device used to realize the sending function in the transceiver unit 1310 is regarded as a sending unit
  • the transceiver unit 1310 includes a receiving unit and a sending unit
  • Transceiver units are sometimes also referred to as transceivers, transceivers, or transceiver circuits.
  • a receiving unit is also sometimes referred to as a receiver, receiver, or receiving circuit.
  • a sending unit is also sometimes called a transmitter, transmitter or transmitting circuit.
  • the processing unit 1320 is configured to execute the processing actions on the terminal device side in FIG. 4 to FIG. 10 .
  • the processing unit 1320 is configured to execute the processing steps in FIG. 4 to FIG. 10 ;
  • the transceiving unit 1310 is configured to execute the transceiving operations in FIG. 4 to FIG. 10 .
  • FIG. 13 is only an example rather than a limitation, and the foregoing terminal device including a transceiver unit and a processing unit does not depend on the structure shown in FIG. 13 .
  • the chip When the communication device 1300 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit is an input-output circuit or a communication interface
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application also provides a communication device 1400, where the communication device 1400 is a network device and also a chip.
  • the communication apparatus 1400 is configured to execute the operations performed by the first network device, or the second network device, or the third network device, or the SMF entity, or the UPF entity, or the base station in the foregoing method embodiments.
  • FIG. 14 shows a schematic structural diagram of a simplified network device 1400 .
  • Part 1410 is mainly used for transmitting and receiving radio frequency signals and conversion between radio frequency signals and baseband signals; part 1420 is mainly used for processing and control.
  • Part 1410 is commonly referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver.
  • the part 1420 is usually the control center of the network device, usually referred to as a processing unit, and is used to control the network device to perform the processing operations on the network device side in the foregoing method embodiments.
  • the transceiver unit of part 1410 also referred to as transceiver or transceiver, includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing.
  • the device used to realize the receiving function in part 1410 is regarded as a receiving unit
  • the device used to realize the sending function is regarded as a sending unit, that is, part 1410 includes a receiving unit and a sending unit.
  • the receiving unit is also called receiver, receiver, or receiving circuit
  • the sending unit is called transmitter, transmitter or transmitting circuit.
  • Section 1420 includes one or more single boards, each of which includes one or more processors and one or more memories.
  • the processor is used to read and execute programs in the memory to realize baseband processing functions and control the base station. If there are multiple single boards, each single board is interconnected to enhance processing capability. As an implementation manner, multiple boards share one or more processors, or multiple boards share one or more memories, or multiple boards share one or more processors at the same time.
  • the transceiving unit in part 1410 is used to execute the steps related to sending and receiving performed by the first network device in the embodiments shown in FIG. 4 and FIG. 5; Steps related to processing executed by the first network device in the illustrated embodiment.
  • the transceiver unit in part 1410 is used to execute the steps related to sending and receiving performed by the second network device in the embodiment shown in FIG. 4; Process-related steps performed by the second network device.
  • the transceiver unit in part 1410 is used to execute the steps related to sending and receiving performed by the third network device in the embodiment shown in FIG. 4; Steps related to processing performed by the third network device.
  • the transceiver unit in part 1410 is used to execute the steps related to sending and receiving performed by the SMF entity in the embodiment shown in Figure 6, Figure 7, Figure 9, and Figure 10; 6. Steps related to processing performed by the SMF entity in the embodiments shown in FIG. 7 , FIG. 9 , and FIG. 10 .
  • the transceiver unit in part 1410 is used to execute the steps related to sending and receiving performed by the UPF entity in the embodiment shown in Fig. 6, Fig. 7, Fig. 9 and Fig. 10; 6. Steps related to processing performed by the UPF entity in the embodiments shown in FIG. 7 , FIG. 9 , and FIG. 10 .
  • the transceiver unit in part 1410 is used to execute the steps related to transceiver performed by the base station in the embodiment shown in FIG. 6 , FIG. 7 , FIG. 9 , and FIG. 10 ; , steps related to processing performed by the base station in the embodiments shown in FIG. 7 , FIG. 9 , and FIG. 10 .
  • FIG. 14 is only an example rather than a limitation, and the foregoing network device including a transceiver unit and a processing unit does not depend on the structure shown in FIG. 14 .
  • the chip When the communication device 1400 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit is an input-output circuit and a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the terminal device or the method executed by the network device in the above method embodiments are stored.
  • the computer program when executed by a computer, the computer implements the method executed by the terminal device or the method executed by the network device in the foregoing method embodiments.
  • the embodiments of the present application also provide a computer program product including instructions, which, when executed by a computer, enable the computer to implement the method executed by the terminal device or the method executed by the network device in the above method embodiments.
  • An embodiment of the present application further provides a communication system, where the communication system includes the network device and the terminal device in the foregoing embodiments.
  • a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU) and memory (also called main memory).
  • the operating system at the operating system layer is any one or more computer operating systems that realize business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system or windows operating system.
  • the application layer includes browser, address book, word processing software, and instant messaging software.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as the program that records the code of the method provided in the embodiment of the present application is executed according to the method provided in the embodiment of the present application Just communicate.
  • the execution subject of the method provided by the embodiment of the present application is a terminal device or a network device, or a functional module in a terminal device or a network device that invokes a program and executes the program.
  • the computer-readable storage medium is any available medium accessed by a computer or an integrated server or data center data storage device including one or more available media.
  • Usable media include, but are not limited to, magnetic media or magnetic storage devices (for example, floppy disks, hard disks (such as removable hard disks), magnetic tapes), optical media (for example, optical disks, compact discs, CDs), digital versatile discs (DVDs), smart cards, and flash memory devices (for example, erasable programmable read-only memory (EPROM), card, stick, or key drives), or Semiconductor media (such as solid state disk (solid state disk, SSD), U disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), and various media for storing program codes.
  • Various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” includes, but is not limited to, wireless channels and various other media that store, contain and/or carry instructions and/or data.
  • processors mentioned in the embodiment of the present application is a central processing unit (central processing unit, CPU), or other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor is a microprocessor or any conventional processor.
  • non-volatile memory is read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable In addition to programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory is random access memory (random access memory, RAM). For example, RAM is used as an external cache.
  • RAM includes the following multiple forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods are implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the above units is only a logical function division, and there are other division methods in actual implementation, such as combining or integrating multiple units or components into another A system, or some feature, is ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed is through some interfaces, and the indirect coupling or communication connection of devices or units is in electrical, mechanical or other forms.
  • the units described above as separate components are or are not physically separated, and the components shown as units are or are not physical units, that is, they are located in one place, or are also distributed to multiple network units. Select some or all of the units according to actual needs to implement the solution provided by this application.
  • each functional unit in each embodiment of the present application is integrated into one unit, each unit also physically exists separately, or two or more units are integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • the computer is a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer is a personal computer, a server, or a network device.
  • Computer instructions are stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave) to another website site, computer, server, or data center.
  • DSL digital subscriber line
  • wireless eg, infrared, wireless, microwave
  • Embodiment 1 A method for session management, comprising:
  • the terminal device determines a first parameter, where the first parameter is used by the first network device to determine a first inactivity duration of a first quality of service QoS flow of the terminal device, or used by the first network device to determine the a first duration of inactivity of the first session of the terminal device;
  • the terminal device sends a first message to the first network device, where the first message includes the first parameter.
  • Embodiment 2 according to the method described in embodiment 1, it is characterized in that,
  • the first inactivity duration of the first QoS flow is used to determine to release the first QoS flow, or
  • the first inactivity duration of the first session is used to determine to release the user plane connection of the first session.
  • Embodiment 3 according to the method described in embodiment 1 or 2, is characterized in that,
  • the first parameter is the first periodic information of the service of the terminal device, or
  • the first parameter is the second inactive duration of the first QoS flow or the second inactive duration of the first session determined according to the first periodical information of the service of the terminal device.
  • Embodiment 4 The method according to Embodiment 3, wherein the first periodic information of the service of the terminal device includes the information of the first frame rate of the service, or the service has a high degree of importance At least one item of the first proportion information of the frame and the frame with low importance.
  • Embodiment 5 according to the method described in any one in embodiment 1 to 4, it is characterized in that, described method also comprises:
  • the terminal device receives the message of the first network device that includes the first inactivity duration information of the first QoS flow.
  • Embodiment 6 according to the method described in embodiment 5, it is characterized in that, described method also comprises:
  • the terminal device releases the first QoS flow.
  • Embodiment 7 according to the method described in embodiment 5, it is characterized in that, described method also comprises:
  • the terminal device When the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the terminal device sends an indication to the first network device that the first QoS flow is not An activity, and/or, a message requesting to release the first QoS flow;
  • the terminal device receives a message from the first network device indicating to release the first QoS flow.
  • Embodiment 8 The method according to Embodiment 6 or 7, wherein releasing the first QoS flow by the terminal device includes:
  • the terminal device deletes the association relationship between the first QoS flow and the second QoS flow, wherein the first QoS flow transmits data of high importance in the service, and the second QoS flow transmits the service For data of low importance, the first QoS flow is associated with the second QoS flow; or,
  • the terminal device releases a second QoS flow associated with the first QoS flow, wherein the first QoS flow transmits data with a high degree of importance in the service, and the second QoS flow transmits data in the service data of low importance.
  • Embodiment 9 according to the method described in any one in embodiment 1 to 8, it is characterized in that, described method also comprises:
  • the terminal device sends a second message to the first network device
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the first QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 10 The method according to Embodiment 9, wherein the second parameter or the third parameter is the second periodical information of the service of the terminal device.
  • Embodiment 11 according to the method described in embodiment 9, is characterized in that, described method also comprises:
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device, the second QoS parameter of the first QoS flow is the second parameter, and the The second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the terminal device determines the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow
  • the information of the second QoS parameter and the second QoS parameter of the second QoS flow are the third parameters, and the second QoS parameter of the first QoS flow includes the second GFBR and the second MFBR of the first QoS flow , or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes the second GFBR, the second MFBR of the second QoS flow, or at least one of the second MDBV.
  • Embodiment 12 The method according to embodiment 10 or 11, wherein the second periodical information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 13 according to the method described in any one in embodiment 1 to 4, it is characterized in that, described method also comprises:
  • the terminal device receives the message of the first network device that includes the first inactivity duration information of the first session.
  • Embodiment 14 according to the method described in embodiment 13, is characterized in that, described method also comprises:
  • the terminal device deactivates the user plane connection of the first session.
  • Embodiment 15 according to the method described in embodiment 13, is characterized in that, described method also comprises:
  • the terminal device When the duration of no data transmission of the first session reaches the first inactivity duration of the first session, the terminal device sends an indication to the first network device that the first session is inactive, and /or, a message requesting to deactivate the user plane connection of the first session;
  • the terminal device receives a message from the second network device indicating to deactivate the user plane connection of the first session.
  • Embodiment 16 A method for session management, comprising:
  • the first network device receives a first message from the terminal device, where the first message includes a first parameter, and the first parameter is used by the first network device to determine a first difference of a first quality of service (QoS) flow of the terminal device.
  • QoS quality of service
  • the first network device determines the first inactive duration of the first QoS flow according to the first parameter, or determines the first inactive duration of the first session.
  • Embodiment 17 The method according to embodiment 16, characterized in that,
  • the first inactivity duration of the first QoS flow is used to determine to release the first QoS flow, or
  • the first inactivity duration of the first session is used to determine to release the user plane connection of the first session.
  • Embodiment 18 The method according to embodiment 16 or 17, characterized in that,
  • the first parameter is the first periodic information of the service of the terminal device, or
  • the first parameter is the second inactive duration of the first QoS flow or the second inactive duration of the first session determined according to the first periodical information of the service of the terminal device.
  • Embodiment 19 The method according to Embodiment 18, wherein the first periodic information of the service of the terminal device includes the information of the first frame rate of the service, or the service has a high degree of importance At least one item of the first proportion information of the frame and the frame with low importance.
  • Embodiment 20 The method according to any one of embodiments 16 to 19, further comprising:
  • the first network device sends a message including the first inactivity duration information of the first QoS flow to the terminal device and/or the second network device and/or the third network device.
  • Embodiment 21 The method according to embodiment 20, further comprising:
  • the first network device receives from the terminal device and/or the second network device and/or the third network device: indicating that the first QoS flow is inactive, and/or requesting to release the the message of the first QoS flow;
  • the first network device sends a message for instructing to release the first QoS flow to the terminal device and/or the second network device and/or the third network device.
  • Embodiment 22 The method according to any one of embodiments 16 to 21, further comprising:
  • the first network device receives a second message from the terminal device
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the first QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 23 The method according to Embodiment 22, wherein the second parameter or the third parameter is the second periodic information of the service of the terminal device.
  • Embodiment 24 The method according to embodiment 22, wherein,
  • the second parameter is a second QoS parameter of the first QoS flow
  • the second QoS parameter of the first QoS flow is determined by the terminal device according to the second periodic information of the service of the terminal device,
  • the second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the third parameter is the information of the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, and the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the second QoS parameter of the terminal device is determined by the terminal device according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow includes the second GFBR, the second GFBR of the first QoS flow, Two MFBR, or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the second QoS flow.
  • Embodiment 25 The method according to Embodiment 23 or 24, wherein the second periodical information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 26 The method according to any one of embodiments 16 to 19, further comprising:
  • the first network device sends a message including the first inactivity duration information of the first session to the terminal device.
  • Embodiment 27 The method according to embodiment 26, further comprising:
  • the first network device receives a message from the terminal device indicating that the first session is inactive, and/or requesting to deactivate the user plane connection of the first session;
  • the first network device sends a message indicating to deactivate the user plane connection of the first session to the second network device and/or the third network device.
  • Embodiment 28 The method according to any one of embodiments 16 to 27, further comprising:
  • the second network device receives a message from the first network device including the first inactivity duration information of the first QoS flow.
  • Embodiment 29 The method according to embodiment 28, further comprising:
  • the second network device When the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the second network device sends an indication of the first QoS to the first network device The flow is inactive, and/or, a message requesting to release the first QoS flow;
  • the second network device receives a message from the first network device indicating to release the first QoS flow.
  • Embodiment 30 The method according to Embodiment 29, wherein releasing the first QoS flow by the second network device includes:
  • the second network device deletes the association relationship between the first QoS flow and the second QoS flow, wherein the first QoS flow transmits data with a high degree of importance in the service, and the second QoS flow transmits all data of low importance in the service, the first QoS flow is associated with the second QoS flow; or,
  • the second network device releases a second QoS flow associated with the first QoS flow, where the first QoS flow transmits data of high importance in the service, and the second QoS flow transmits the Data with low importance in business.
  • Embodiment 31 The method according to embodiments 16 to 30, further comprising:
  • the second network device receives a message from the first network device indicating to deactivate the user plane connection of the first session;
  • the second network device sends a message indicating to deactivate the user plane connection of the first session to the terminal device.
  • Embodiment 32 The method according to any one of embodiments 16 to 31, further comprising:
  • the third network device receives a message from the first network device including the first inactivity duration information of the first QoS flow.
  • Embodiment 33 The method according to embodiment 32, further comprising:
  • the third network device When the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the third network device sends an indication of the first QoS to the first network device The flow is inactive, and/or, a message requesting to release the first QoS flow;
  • the third network device receives a message from the first network device indicating to release the first QoS flow.
  • Embodiment 34 The method according to Embodiment 33, wherein releasing the first QoS flow by the third network device includes:
  • the third network device deletes the association relationship between the first QoS flow and the second QoS flow, where the first QoS flow transmits data with a high degree of importance in the service, and the second QoS flow transmits all data of low importance in the service, the first QoS flow is associated with the second QoS flow; or,
  • the third network device releases a second QoS flow associated with the first QoS flow, where the first QoS flow transmits data with high importance in the service, and the second QoS flow transmits the Data with low importance in business.
  • Embodiment 35 The method according to embodiments 16 to 34, further comprising:
  • the third network device receives a message from the first network device indicating to deactivate the user plane connection of the first session.
  • Embodiment 36 A method for session management, comprising:
  • the terminal device sends the second message to the first network device,
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the first At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 37 The method according to embodiment 36, wherein the second parameter or the third parameter is the second periodic information of the service of the terminal device.
  • Embodiment 38 The method according to embodiment 36, further comprising:
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device, the second QoS parameter of the first QoS flow is the second parameter, and the The second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the terminal device determines the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow
  • the information of the second QoS parameter and the second QoS parameter of the second QoS flow are the third parameters, and the second QoS parameter of the first QoS flow includes the second GFBR and the second MFBR of the first QoS flow , or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes the second GFBR, the second MFBR of the second QoS flow, or at least one of the second MDBV.
  • Embodiment 39 The method according to Embodiment 37 or 38, wherein the second periodical information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 40 A method for session management, comprising:
  • the first network device receives the second message from the terminal device,
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the first At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 41 The method according to Embodiment 40, wherein the second parameter or the third parameter is the second periodic information of the service of the terminal device.
  • Embodiment 42 The method according to embodiment 40, further comprising:
  • the second parameter is a second QoS parameter of the first QoS flow
  • the second QoS parameter of the first QoS flow is determined by the terminal device according to the second periodic information of the service of the terminal device,
  • the second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the third parameter is the information of the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, and the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the second QoS parameter of the terminal device is determined by the terminal device according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow includes the second GFBR, the second GFBR of the first QoS flow, Two MFBR, or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the second QoS flow.
  • Embodiment 43 The method according to embodiment 41 or 42, wherein the second periodical information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 44 A method for session management, characterized in that the method comprises:
  • the third network device receives a message from the first network device including the first inactivity duration information of the first QoS flow.
  • Embodiment 45 The method according to embodiment 44, further comprising:
  • the third network device When the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the third network device sends an indication of the first QoS to the first network device The flow is inactive, and/or, a message requesting to release the first QoS flow;
  • the third network device receives a message from the first network device indicating to release the first QoS flow.
  • Embodiment 46 The method according to Embodiment 45, wherein releasing the first QoS flow by the third network device includes:
  • the third network device deletes the association relationship between the first QoS flow and the second QoS flow, where the first QoS flow transmits data with a high degree of importance in the service, and the second QoS flow transmits all data of low importance in the service, the first QoS flow is associated with the second QoS flow; or,
  • the third network device releases a second QoS flow associated with the first QoS flow, where the first QoS flow transmits data with high importance in the service, and the second QoS flow transmits the Data with low importance in business.
  • Embodiment 47 The method according to any one of embodiments 44 to 46, further comprising:
  • the third network device receives a message from the first network device indicating to deactivate the user plane connection of the first session.
  • Embodiment 48 A device for session management, comprising:
  • a processing unit configured to determine a first parameter, where the first parameter is used by the first network device to determine a first inactivity duration of the first quality of service QoS flow of the terminal device, or used by the first network device determining a first duration of inactivity of the first session of the terminal device;
  • a transceiver unit configured to send a first message to the first network device, where the first message includes the first parameter.
  • Embodiment 49 The device of embodiment 48, wherein,
  • the first inactivity duration of the first QoS flow is used to determine to release the first QoS flow, or
  • the first inactivity duration of the first session is used to determine to release the user plane connection of the first session.
  • Embodiment 50 The device of embodiment 48 or 49, wherein,
  • the first parameter is the first periodic information of the service of the terminal device, or
  • the first parameter is the second inactive duration of the first QoS flow or the second inactive duration of the first session determined according to the first periodical information of the service of the terminal device.
  • Embodiment 51 The device according to Embodiment 50, wherein the first periodic information of the service of the terminal device includes the information of the first frame rate of the service, or the service has a high degree of importance At least one item of the first proportion information of the frame and the frame with low importance.
  • Embodiment 52 The device according to any one of Embodiments 48 to 51, wherein the transceiver unit is further used for:
  • Embodiment 53 The device according to embodiment 52, wherein the processing unit is further used for:
  • the terminal device releases the first QoS flow.
  • Embodiment 54 The device according to Embodiment 52, wherein the transceiver unit is further used for:
  • the terminal device When the duration of no data transmission of the first QoS flow reaches the first inactivity duration of the first QoS flow, the terminal device sends an indication to the first network device that the first QoS flow is not An activity, and/or, a message requesting to release the first QoS flow;
  • the terminal device receives a message from the first network device indicating to release the first QoS flow.
  • Embodiment 55 The device according to Embodiment 53 or 54, wherein the processing unit is further configured to:
  • the first QoS flow is associated with the second QoS flow;
  • Embodiment 56 The device according to any one of Embodiments 48 to 55, wherein the transceiver unit is further used for:
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the first QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 57 The device according to Embodiment 56, wherein the second parameter or the third parameter is the second periodic information of the service of the terminal device.
  • Embodiment 58 The device according to embodiment 56, wherein the processing unit is further configured to:
  • the second QoS parameter includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the second QoS parameter of the information and the second QoS flow is the third parameter
  • the second QoS parameter of the first QoS flow includes the second GFBR, the second MFBR, or the second QoS flow of the first QoS flow.
  • At least one of the MDBVs, the second QoS parameter of the second QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the second QoS flow.
  • Embodiment 59 The device according to Embodiment 57 or 58, wherein the second periodic information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 60 The device according to any one of Embodiments 48 to 51, wherein the transceiver unit is further used for:
  • Embodiment 61 The device according to embodiment 60, wherein the processing unit is further configured to:
  • Embodiment 62 The device according to Embodiment 60, wherein the transceiver unit is further used for:
  • a message indicating to deactivate the user plane connection of the first session is received from the second network device.
  • a device for session management comprising:
  • the transceiver unit of the first network device is configured to receive a first message from the terminal device, the first message includes a first parameter, and the first parameter is used by the first network device to determine a first quality of service of the terminal device
  • the processing unit of the first network device is configured to determine a first inactive duration of the first QoS flow, or determine a first inactive duration of the first session according to the first parameter.
  • Embodiment 64 The device of embodiment 63, wherein,
  • the first inactivity duration of the first QoS flow is used to determine to release the first QoS flow, or
  • the first inactivity duration of the first session is used to determine to release the user plane connection of the first session.
  • Embodiment 65 The device of embodiment 63 or 64, wherein,
  • the first parameter is the first periodic information of the service of the terminal device, or
  • the first parameter is the second inactive duration of the first QoS flow or the second inactive duration of the first session determined according to the first periodical information of the service of the terminal device.
  • Embodiment 66 The device according to Embodiment 65, wherein the first periodic information of the service of the terminal device includes the information of the first frame rate of the service, or the service has a high degree of importance At least one item of the first proportion information of the frame and the frame with low importance.
  • Embodiment 67 The device according to any one of Embodiments 63 to 66, wherein the transceiver unit of the first network device is further configured to:
  • Embodiment 68 The device according to Embodiment 67, wherein the transceiver unit of the first network device is further configured to:
  • Embodiment 69 The device according to any one of Embodiments 63 to 67, wherein the transceiver unit of the first network device is further configured to:
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the first QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow.
  • Embodiment 70 The device according to Embodiment 69, wherein the second parameter or the third parameter is the second periodical information of the service of the terminal device.
  • Embodiment 71 The device of embodiment 69, wherein,
  • the second parameter is a second QoS parameter of the first QoS flow
  • the second QoS parameter of the first QoS flow is determined by the terminal device according to the second periodic information of the service of the terminal device,
  • the second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the third parameter is the information of the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, and the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the second QoS parameter of the terminal device is determined by the terminal device according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow includes the second GFBR, the second GFBR of the first QoS flow, Two MFBR, or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the second QoS flow.
  • Embodiment 72 The device according to Embodiment 70 or 71, wherein the second periodic information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 73 The device according to any one of Embodiments 63 to 66, wherein the transceiver unit of the first network device is further configured to:
  • Embodiment 74 The device according to Embodiment 73, wherein the transceiver unit of the first network device is further configured to:
  • Embodiment 75 The device according to any one of Embodiments 63-74, further comprising:
  • the transceiver unit of the second network device is configured to receive a message from the first network device including the first inactivity duration information of the first QoS flow.
  • Embodiment 76 The device according to Embodiment 75, wherein the transceiver unit of the second network device is further configured to:
  • Embodiment 77 The device of embodiment 76, further comprising:
  • the processing unit of the second network device is configured to delete the association relationship between the first QoS flow and the second QoS flow, wherein the first QoS flow transmits data with a high degree of importance in the service, and the The second QoS flow transmits data of low importance in the service, and the first QoS flow is associated with the second QoS flow; or,
  • Embodiment 78 The device according to Embodiments 63 to 77, wherein the transceiver unit of the second network device is further configured to:
  • Embodiment 79 The device of any one of Embodiments 63-77, further comprising:
  • the transceiver unit of the third network device is configured to receive a message from the first network device including the first inactivity duration information of the first QoS flow.
  • Embodiment 80 The device according to Embodiment 79, wherein the transceiver unit of the third network device is further configured to:
  • Embodiment 81 The device of embodiment 80, further comprising:
  • the processing unit of the third network device is configured to delete the association relationship between the first QoS flow and the second QoS flow, wherein the first QoS flow transmits data with a high degree of importance in the service, and the The second QoS flow transmits data of low importance in the service, and the first QoS flow is associated with the second QoS flow; or,
  • Embodiment 82 The apparatus according to Embodiments 63 to 81, wherein the transceiver unit of the third network device is further configured to:
  • a message indicating to deactivate the user plane connection of the first session is received from the first network device.
  • Embodiment 83 A device for session management, comprising:
  • a processing unit configured to generate a second message, the second message includes a second parameter, the second parameter is used by the first network device to determine a first QoS parameter of a first QoS flow, and the first QoS flow
  • the first QoS parameter includes at least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the first QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow;
  • a transceiver unit configured to send the second message to the first network device.
  • Embodiment 84 The apparatus according to Embodiment 83, wherein the second parameter or the third parameter is the second periodic information of the service of the terminal device.
  • Embodiment 85 The device of Embodiment 83, further comprising:
  • the terminal device determines the second QoS parameter of the first QoS flow according to the second periodic information of the service of the terminal device, the second QoS parameter of the first QoS flow is the second parameter, and the The second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the terminal device determines the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow
  • the information of the second QoS parameter and the second QoS parameter of the second QoS flow are the third parameters, and the second QoS parameter of the first QoS flow includes the second GFBR and the second MFBR of the first QoS flow , or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes the second GFBR, the second MFBR of the second QoS flow, or at least one of the second MDBV.
  • Embodiment 86 The device according to Embodiment 84 or 85, wherein the second periodic information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • Embodiment 87 An apparatus for session management, comprising:
  • a transceiver unit configured to receive a second message from the terminal device
  • the second message includes a second parameter, the second parameter is used by the first network device to determine the first QoS parameter of the first QoS flow, and the first QoS parameter of the first QoS flow includes the first At least one of the first guaranteed flow bit rate GFBR, the first maximum flow bit rate MFBR, or the first maximum data burst volume MDBV of the QoS flow; or
  • the second message includes a third parameter, the third parameter is used by the first network device to determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow, the The first QoS parameter of the first QoS flow includes at least one of the first GFBR, the first MFBR, or the first MDBV of the first QoS flow, and the first QoS parameter of the second QoS flow includes the first QoS parameter of the first QoS flow. At least one of the first GFBR, the first MFBR, or the first MDBV of the second QoS flow;
  • a processing unit configured to determine the first QoS parameter of the first QoS flow according to the second message, or determine the first QoS parameter of the first QoS flow and the first QoS parameter of the second QoS flow.
  • Embodiment 88 The apparatus according to embodiment 87, wherein the second parameter or the third parameter is the second periodical information of the service of the terminal device.
  • Embodiment 89 The device of embodiment 87, further comprising:
  • the second parameter is a second QoS parameter of the first QoS flow
  • the second QoS parameter of the first QoS flow is determined by the terminal device according to the second periodic information of the service of the terminal device,
  • the second QoS parameter of the first QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the first QoS flow; or
  • the third parameter is the information of the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow, and the second QoS parameter of the first QoS flow and the second QoS parameter of the second QoS flow
  • the second QoS parameter of the terminal device is determined by the terminal device according to the second periodic information of the service of the terminal device, and the second QoS parameter of the first QoS flow includes the second GFBR, the second GFBR of the first QoS flow, Two MFBR, or at least one of the second MDBV, the second QoS parameter of the second QoS flow includes at least one of the second GFBR, the second MFBR, or the second MDBV of the second QoS flow.
  • Embodiment 90 The device according to embodiment 88 or 89, wherein the second periodical information of the service of the terminal device includes the information of the second frame rate of the service, or the importance of the service At least one item of the second proportion information of frames with high degrees and frames with low importance.
  • a device for session management comprising:
  • a transceiver unit configured to receive a message from the first network device including the first inactivity duration information of the first QoS flow
  • a processing unit configured to determine a first inactivity duration of the first QoS flow.
  • Embodiment 92 The method according to Embodiment 91, wherein the transceiver unit is further used for:
  • Embodiment 93 The method of embodiment 92, wherein the device further comprises:
  • a processing unit configured to delete the association relationship between the first QoS flow and the second QoS flow, wherein the first QoS flow transmits data of high importance in the service, and the second QoS flow transmits the For data of low importance in the business, the first QoS flow is associated with the second QoS flow; or,
  • Embodiment 94 The method according to any one of embodiments 91 to 93, wherein the transceiver unit is further used for:
  • a message indicating to deactivate the user plane connection of the first session is received from the first network device.
  • Embodiment 95 A communication device, comprising:
  • a storage unit for storing computer instructions
  • a processing unit configured to execute the computer instructions stored in the storage unit, so that the communication device executes the communication device as in Embodiments 1 to 15 or as in Embodiments 16 to 35 or as in Embodiments 36 to 39 or as in Embodiments 40 to 43 or The method as described in any one of Examples 44-47.
  • Embodiment 96 A communication device, comprising:
  • a processor configured to execute the computer instructions stored in the memory, so that the communication device executes as in Embodiments 1 to 15 or as in Embodiments 16 to 35 or as in Embodiments 36 to 39 or as in Embodiments 40 to 43 or as in Embodiments The method of any one of Examples 44-47.
  • Embodiment 97 A computer-readable storage medium, which is characterized in that a computer program is stored thereon.
  • the communication device executes the method described in Embodiments 1 to 15 or Embodiment 16. to 35 or as in any one of embodiments 36 to 39 or as in embodiments 40 to 43 or as in embodiments 44 to 47.
  • Embodiment 98 A computer program product, characterized in that, the computer program product includes a computer program product for executing embodiments as in embodiments 1 to 15 or as in embodiments 16 to 35 or as in embodiments 36 to 39 or as in embodiments 40 to 43 Or the method as described in any one of embodiments 44-47.
  • Embodiment 99 A chip, characterized in that the chip includes a processor and a data interface, and the processor reads the instructions stored on the memory through the data interface, so as to execute the instructions described in Embodiments 1 to 15 or as implemented. Examples 16 to 35 or the method as described in any one of Examples 36 to 39 or Examples 40 to 43 or Examples 44 to 47.
  • Embodiment 100 A communication system, characterized by comprising the device described in any one of Embodiments 48 to 62 and Embodiments 63 to 82, or any one of Embodiments 83 to 86 and Embodiments 87 to 90.

Landscapes

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

Abstract

本申请提供了一种会话管理的方法和装置，该会话管理的方法包括：终端设备确定第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；终端设备向第一网络设备发送第一消息，所述第一消息包括所述第一参数。从而，终端设备确定用于第一网络设备确定终端设备的第一QoS流的第一不活动时长，或，用于第一网络设备确定终端设备的第一会话的第一不活动时长，第一网络设备根据第一QoS流的第一不活动时长，使得第一QoS流及时释放，或根据第一会话的第一不活动时长，使得第一会话的用户面连接及时去激活，节省网络资源。

Description

会话管理的方法及装置
本申请要求于2021年6月23日提交中国专利局、申请号为202110697476.5、申请名称为“一种Qos流管理的方法”的中国专利申请的优先权，以及于2021年7月30日提交中国专利局、申请号为202110874038.1、申请名称为“会话管理的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，更具体地，涉及会话管理的方法及装置。
背景技术
目前，在通信系统中，存在诸多类型的业务，例如扩展现实(extended reality,XR)业务，通常需要核心网设备为终端配置保障速率类型(guaranteed bit rate，GBR)的服务质量(quality of Service,QoS)流来传输业务的数据，从而保障业务体验。
在通信的过程中，GBR类型的QoS流需要保障网络资源，然而，核心网设备难以感知业务的结束，从而无法对QoS流进行有效管理，造成网络资源的浪费，造成系统容量难以提升的不良影响。所以，需要一种会话管理的方法及装置，缓解上述问题。
发明内容
本申请提供一种会话管理的方法及装置，使得网络设备感知业务的结束，提高网络资源的利用率，节省网络资源。
第一方面，提供了一种会话管理的方法，其中，终端设备确定第一参数，该第一参数用于第一网络设备确定该终端设备的第一服务质量QoS流的第一不活动时长，或，用于该第一网络设备确定该终端设备的第一会话的第一不活动时长；终端设备向第一网络设备发送第一消息，该第一消息包括该第一参数。
其中，该第一QoS流的第一不活动时长用于确定释放该第一Qos流，或，该第一会话的第一不活动时长用于确定释放该第一会话的用户面连接。
该第一参数为该终端设备的业务的第一周期性信息，或，该第一参数为根据该终端设备的业务的第一周期性信息确定的该第一QoS流的第二不活动时长或该第一会话的第二不活动时长，终端设备的业务的第一周期性信息包括该业务的第一帧率的信息，或该业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
基于上述方案，终端设备通过终端设备的业务的第一周期性信息确定用于第一网络设备确定终端设备的第一服务质量QoS流的第一不活动时长，或，用于第一网络设备确定终端设备的第一会话的第一不活动时长，从而第一网络设备根据第一QoS流的第一不活动时长，使得第一QoS流(需要网络保证比特速率的QoS流)及时释放，或第一网络设备根据第一会话的第一不活动时长，使得第一会话的用户面连接及时去激活，节省网络资 源。
结合第一方面，在第一方面的某些实现方式中，该终端设备接收该第一网络设备的包括该第一QoS流的第一不活动时长信息的消息；在该第一QoS流的无数据传输的时长达到该第一QoS流的第一不活动时长的情况下，该终端设备释放该第一QoS流；或，该终端设备向该第一网络设备发送指示该第一QoS流不活动，和/或，请求释放该第一QoS流的消息；该终端设备接收来自该第一网络设备的用于指示释放该第一QoS流的消息。
基于上述方案，终端设备通过监控第一QoS流无数据传输的时长是否达到第一QoS流的第一不活动时长，或根据第一网络设备发送的用于指示释放该第一QoS流的消息，释放第一QoS流，使得第一QoS流及时释放，从而节省网络资源。
结合第一方面，在第一方面的某些实现方式中，该终端设备向该第一网络设备发送第二消息，该第二消息包含第二参数，该第二参数用于该第一网络设备确定该第一QoS流的第一QoS参数，或，该第二消息包含第三参数，该第三参数用于该第一网络设备确定该第一QoS流的第一QoS参数和该第二QoS流的第一QoS参数。
在一些实施例中，第二参数或该第三参数为该终端设备的业务的第二周期性信息。
在一些实施例中，终端设备根据该终端设备的业务的第二周期性信息确定该第一QoS流的第二QoS参数，或该第一QoS流的第二QoS参数与该第二QoS流的第二QoS参数，该第一QoS流的第二QoS参数为该第二参数，该第一QoS流的第二QoS参数的信息与该第二QoS流的第二QoS参数为该第三参数。
其中，该终端设备的业务的第二周期性信息包括该业务的第二帧率的信息，或该业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
基于上述方案，第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数均根据终端设备的业务的第二周期性信息确定的，从而基于业务的需求及分层传输的信息确定QoS参数，提升网络资源利用效率。
结合第一方面，在第一方面的某些实现方式中，该终端设备接收该第一网络设备的包括该第一会话的第一不活动时长信息的消息；在该第一会话的无数据传输的时长达到该第一会话的第一不活动时长的情况下，该终端设备去激活该第一会话的用户面连接；或，该终端设备向该第一网络设备发送指示该第一会话不活动，和/或，请求去激活该第一会话的用户面连接的消息；该终端设备接收来自第二网络设备的指示去激活该第一会话的用户面连接的消息。
基于上述方案，终端设备根据第二网络设备发送的指示去激活该第一会话的用户面连接的消息，去激活该第一会话的用户面连接，使得第一会话的用户面连接及时去激活，从而节省网络资源。
第二方面，提供了一种会话管理的方法，包括：第一网络设备接收来自终端设备的第一消息，该第一消息包含第一参数，该第一参数用于第一网络设备确定该终端设备的第一服务质量QoS流的第一不活动时长，或，用于该第一网络设备确定该终端设备的第一会话的第一不活动时长；该第一网络设备根据该第一参数，确定该第一QoS流的第一不活动时长，或，确定该第一会话的第一不活动时长。
其中，该第一QoS流的第一不活动时长用于确定释放该第一Qos流，或
该第一会话的第一不活动时长用于确定释放该第一会话的用户面连接。
其中，关于第一参数的内容的描述，请参考第一方面中关于第一参数的内容的相关描述，为了简洁，本申请在此不再赘述。
基于上述方案，第一网络设备根据终端设备的业务的第一周期性信息确定的第一参数，确定终端设备的第一QoS流的第一不活动时长，或，终端设备的第一会话的第一不活动时长，从而第一网络设备根据第一QoS流的第一不活动时长，使得第一QoS流(需要网络保证比特速率的QoS流)及时释放，或第一网络设备根据第一会话的第一不活动时长，使得第一会话的用户面连接及时去激活，提升网络资源的利用效率。
结合第二方面，在第二方面的某些实现方式中，该第一网络设备向该终端设备和/或第二网络设备和/或第三网络设备发送包括该第一QoS流的第一不活动时长信息的消息；该第一网络设备接收来自该终端设备和/或该第二网络设备和/或第三网络设备的：指示该第一QoS流不活动，和/或，请求释放该第一QoS流的消息；该第一网络设备向该终端设备，和/或第二网络设备和/或第三网络设备发送用于指示释放该第一QoS流的消息。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
结合第二方面，在第二方面的某些实现方式中，该第一网络设备接收来自该终端设备的第二消息，该第二消息包含第二参数，该第二参数用于该第一网络设备确定该第一QoS流的第一QoS参数；或，该第二消息包含第三参数，该第三参数用于该第一网络设备确定该第一QoS流的第一QoS参数和该第二QoS流的第一QoS参数。
其中，关于第二参数的内容与第三参数的内容的描述，请参考第一方面中关于第二参数的内容与第三参数的内容的相关描述，为了简洁，本申请在此不再赘述。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
结合第二方面，在第二方面的某些实现方式中，该第一网络设备向该终端设备发送包括该第一会话的第一不活动时长信息的消息。
结合第二方面，在第二方面的某些实现方式中，该第一网络设备接收来自该终端设备的指示该第一会话不活动，和/或，请求去激活该第一会话的用户面连接的消息；该第一网络设备向该第二网络设备和/或第三网络设备发送指示去激活该第一会话的用户面连接的消息。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
结合第二方面，在第二方面的某些实现方式中，第二网络设备接收来自该第一网络设备的包括该第一QoS流的第一不活动时长信息的消息。在该第一QoS流的无数据传输的时长达到该第一QoS流的第一不活动时长的情况下，该第二网络设备向该第一网络设备发送指示该第一QoS流不活动，和/或，请求释放该第一QoS流的消息；该第二网络设备接收来自该第一网络设备的用于指示释放该第一QoS流的消息。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
结合第二方面，在第二方面的某些实现方式中，第三网络设备接收来自该第一网络设备的包括该第一QoS流的第一不活动时长信息的消息。在该第一QoS流的无数据传输的 时长达到该第一QoS流的第一不活动时长的情况下，该第三网络设备向该第一网络设备发送指示该第一QoS流不活动，和/或，请求释放该第一QoS流的消息；该第三网络设备接收来自该第一网络设备的用于指示释放该第一QoS流的消息。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
第三方面，提供了一种会话管理的方法，包括：终端设备向第一网络设备发送第二消息，该第二消息包含第二参数，该第二参数用于该第一网络设备确定第一QoS流的第一QoS参数；或，该第二消息包含第三参数，该第三参数用于该第一网络设备确定该第一QoS流的第一QoS参数和该第二QoS流的第一QoS参数。
其中，关于第二参数的内容与第三参数的内容的描述，请参考第一方面中关于第二参数的内容与第三参数的内容的相关描述，为了简洁，本申请在此不再赘述。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
第四方面，提供了一种会话管理的方法，包括：第一网络设备接收来自终端设备的第二消息，该第二消息包含第二参数，该第二参数用于该第一网络设备确定第一QoS流的第一QoS参数；或，该第二消息包含第三参数，该第三参数用于该第一网络设备确定该第一QoS流的第一QoS参数和该第二QoS流的第一QoS参数。
其中，关于第二参数的内容与第三参数的内容的描述，请参考第一方面中关于第二参数的内容与第三参数的内容的相关描述，为了简洁，本申请在此不再赘述。
上述方案的有益效果请参考第一方面相关的有益效果，为了简洁，本申请在此不再赘述。
第五方面，提供一种通信装置，通信装置用于执行上述第一方面或第三方面提供的通信方法。具体地，通信装置包括用于执行第一方面至第三方面提供的通信方法的模块。
第六方面，提供一种通信装置，通信装置用于执行上述第一方面或第三方面提供的通信方法。具体地，通信装置包括用于执行第二方面或第四方面提供的通信方法的模块。
第七方面，提供了一种通信装置，包括处理器和接口电路，接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第一方面或第三方面的任意可能的实现方式中的方法。
第八方面，提供了一种通信装置，包括处理器和接口电路，接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第二方面或第四方面的任意可能的实现方式中的方法。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第一方面或第三方面的任意可能的实现方式中的方法。
第十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第二方面或第四方面的任意可能的实现方式中的方法。
第十一方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第一方面或第三方面的任意可能的实现方式中的方法。
第十二方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第二方面或第四方面的任意可能的实现方式中的方法。
第十三方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第一方面或第三方面的任意可能的实现方式中的方法。
第十四方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第二方面或第四方面的任意可能的实现方式中的方法。
第十五方面，提供一种芯片系统，该芯片系统包括处理器，还包括存储器，用于实现前述第一方面或第三方面的任意可能的实现方式中的方法。该芯片系统由芯片构成，也包含芯片和其他分立器件。
第十六方面，提供一种芯片系统，该芯片系统包括处理器，还包括存储器，用于实现前述第二方面或第四方面的任意可能的实现方式中的方法。该芯片系统由芯片构成，也包含芯片和其他分立器件。
第十七方面，提供一种通信系统，该通信系统包括第五方面与第六方面的装置。
附图说明
图1是适用于本申请实施例的网络架构的一示意图。
图2是适用于本实施例的P帧与I帧的一示意图。
图3是适用于本申请实施例的QoS流传输的一示意图。
图4是本申请实施例提出的会话管理的方法400的一示意图。
图5是本申请实施例提出的一种会话管理的方法500的一示意图。
图6是本申请实施例提供的一种会话管理方法600的一示意图。
图7是本申请实施例提供的一种会话管理方法700的一示意图。
图8是确定终端设备的业务终止的方法800的一示意图。
图9是本申请实施例提供的一种会话管理方法900的一示意图。
图10是本申请实施例提供的一种会话管理方法1000的一示意图。
图11是本申请实施例提供的通信装置1100的示意性框图。
图12是申请实施例提供的通信装置1200的示意性框图。
图13是申请实施例提供的一种简化的终端设备1300的结构示意图。
图14是申请实施例提供的一种简化的网络设备1400的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案应用于各种通信系统，例如：第五代(5th generation，5G)系统或新无线(new radio，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)。以及云端视频源编解码，渲染，网络传输包括LTE、NR以及第六代系统(6th generation，6G)空口的 核心网和接入网，扩展现实设备，其中，扩展现实包括增强现实(augmented reality,AR)、虚拟现实(virtual reality,VR)，以及混合现实(mixed reality,MR)。
本申请实施例的技术方案还应用于设备到设备(device to device，D2D)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及车联网系统中的通信。其中，车联网系统中的通信方式统称为V2X(X代表任何事物)，例如，该V2X通信包括：车辆与车辆(vehicle to vehicle，V2V)通信，车辆与路边基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信。
图1是适用于本申请实施例的网络架构的一示意图。下面对该图1所示的网络架构中涉及的部分主体进行说明。
1、用户设备(user equipment，UE)：
包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端、移动台(mobile station，MS)、终端(terminal)或软终端。例如，水表、电表、传感器。
示例性地，本申请实施例中的用户设备指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、终端设备(terminal equipment)、无线通信设备、用户代理或用户装置。用户设备还是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的用户设备或者未来车联网中的用户设备，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，可穿戴设备也称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰。
此外，在本申请实施例中，用户设备还能是物联网(internet of Things，IoT)系统中的用户设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IOT技术通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。此外，在本申请实施例中，用户设备还包括智能打印机、火车探测器、加油站传感器，主要功能包括收集数据(部分用户设备)、接收接入网设备的控制信息与下行数据，并发送电磁波，向接入网设备传输上行数据。
2、(无线)接入网设备(radio access network，(R)AN)：
用于为特定区域的授权用户设备提供入网功能，并根据用户设备的级别，业务的需求使用不同质量的传输隧道。
(R)AN管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)，还能为5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)。
在一些部署中，gNB包括集中式单元(centralized unit，CU)和DU。gNB还包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也认为是由DU发送的，或者，由DU+AAU发送的。应理解，接入网设备为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，将CU划分为接入网(radio access network，RAN)中的接入网设备，也能将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、用户面网元：
用户面网元用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理。
在5G通信系统中，该用户面网元是用户面功能(user plane function，UPF)网元，负责用户面路径的管理及数据的分发，包括UE IP地址的管理、CN隧道信息的管理、traffic检测、用户面转发、计费。
在未来通信系统中，用户面网元仍是UPF网元，或者，还有其它的名称，本申请不做限定。
4、数据网络网元：
数据网络网元用于提供传输数据的网络。在5G通信系统中，该数据网络网元是数据网络网元(data network，DN)，例如运营商服务，Internet接入或者第三方业务。
在未来通信系统中，数据网络网元仍是DN网元，或者，还有其它的名称，本申请不做限定。
5、接入管理网元：
接入管理网元主要用于移动性管理和接入管理，用于实现移动性管理(mobility  management entity，MME)实体功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权功能。
在5G通信系统中，该接入管理网元是接入管理功能(access and mobility management function，AMF)网元，提供移动性管理、合法监听、或者接入授权以及鉴权功能。
在未来通信系统中，接入管理网元仍是AMF网元，或者，还有其它的名称，本申请不做限定。
6、会话管理网元：
会话管理网元主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知。
在5G通信系统中，该会话管理网元是会话管理功能(session management function，SMF)网元，用于实现会话和承载管理、地址分配。用户面功能网元用于用户面数据的路由转发，门限控制，流量监测、验证功能。
在未来通信系统中，会话管理网元仍是SMF网元，或者，还有其它的名称，本申请不做限定。
7、策略控制网元：
策略控制网元用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元)提供策略规则信息。
在4G通信系统中，该策略控制网元是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元是策略控制功能(policy control function，PCF)网元。在未来通信系统中，策略控制网元仍是PCF网元，或者，还有其它的名称，本申请不做限定。
8、认证服务器：
认证服务器功能网元用于鉴权服务、产生密钥实现对终端设备的双向鉴权，支持统一的鉴权框架。
在5G通信系统中，该认证服务器是认证服务器功能网元(authentication server function，AUSF)。在未来通信系统中，认证服务器功能网元仍是AUSF网元，或者，还有其它的名称，本申请不做限定。
9、数据管理网元：
数据管理网元用于处理终端设备标识，接入鉴权，注册以及移动性管理。
在5G通信系统中，该数据管理网元是统一数据管理(unified data management，UDM)网元。在未来通信系统中，统一数据管理仍是UDM网元，或者，还有其它的名称，本申请不做限定。
10、应用网元：
应用网元用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制。
在5G通信系统中，该应用网元是应用功能(application function，AF)网元，是为用户提供某种类型业务的服务器端，因此也可称为应用服务器或业务服务器。AF可是运营商网络自身部署的AF，也是第三方AF。
在未来通信系统中，应用网元仍是AF网元，或者，还有其它的名称，本申请不做限定。
11、网络存储网元：
网络存储网元用于维护网络中所有网络功能服务的实时信息。
在5G通信系统中，该网络存储网元是网络注册功能(network repository function，NRF)网元。在未来通信系统中，网络存储网元仍是NRF网元，或者，还有其它的名称，本申请不做限定。
理解的是，上述网元或者功能既是硬件设备中的网络元件，也是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
为方便说明，本申请后续，以会话管理网元为SMF网元，接入管理网元为AMF网元。
进一步地，将SMF网元简称为SMF，AMF网元简称为AMF。即本申请后续所描述的SMF均可替换为会话管理网元，AMF均可替换为接入管理网元。
为方便说明，本申请，以装置为SMF实体、AMF实体为例，对用于传输数据的方法进行说明，对于装置为SMF实体内的芯片、AMF实体内的芯片的实现方法，可参考装置分别为SMF实体、AMF实体的具体说明，不再重复介绍。
在图1所示的网络架构中，终端设备通过N1接口与AMF连接，(R)AN通过N2接口与AMF连接，RAN通过N3接口与UPF连接，UPF通过N6接口与DN连接，通过N4接口与SMF连接。
需要说明的是，图1中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只应用于目前已知的通信系统。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口或信令的具体名称并不限定，仅表示网元、接口或者信令的功能，对应的扩展到其它系统，比如2G、3G、4G或未来通信系统中。
上述图1所示的本申请实施例应用的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF网元、SMF网元网元都称为网络功能网元(network function，NF)网元；或者，在另一些网络架构中，AMF网元，SMF网元网元的集合都称为控制面功能网元。
当前，XR业务通常是通过“帧”的形式在网络设备和终端设备之间进行传输的，每个帧代表一幅静止的图像。而在实际压缩时，通过算法减少数据的容量。例如，I帧表示关键帧，只需要该帧的数据就完成解码，使得这一帧画面完整保留(因为该关键帧的数据包含完整的画面)；P帧表示与之前的一个关键帧(例如I帧)的差别帧，解码时需要用之前缓存的画面叠加上本帧画面的差别，生成最终画面。在实际传输的过程中，每个帧的大小和画面的大小与质量(例如，1080P，720P)有关，通常每个帧需要通过多个IP包进行传输，例如，I帧需要通过100个IP包传输，P帧通过40个IP包传输。
相对而言，I帧的重要性比P帧的重要性高，因为当部分P帧传输失败时，通常仅影响该P帧的显示，用户感受到的是短暂的卡顿；然而，如果I帧传输失败，会使得后续的P帧都无法解析，用户的感受到是较长时间的卡顿。
图2为适用于本实施例的P帧与I帧的一示意图。如图1所示，P0是对I帧有较大修改的P帧，P1帧是在I帧或P0帧的基础上进行较小修改的帧，P2帧是对前一帧(I帧，P0帧或P1帧)有较小修改的帧。其中，若P1帧或P2帧丢失，则仅影响P1帧或P2帧的显示，造成的影响较小；若I帧或P0帧丢失，则会影响I帧或P0帧之后的帧的显示，造成的影响较大。
此外，由于XR业务具有数据突发的特点，例如，当XR业务为60帧/s时，每16.67ms会有一帧的数据到达基站，即，一组IP包到达基站，请求基站发送至终端设备。若基站无法发送这些数据，例如由于网络拥塞原因，基站会对接收到的一组IP数据包中的一个或多个IP数据包进行随机丢包处理，从而缓解拥塞的情况。若随机丢弃的IP数据包属于高优先级帧的数据，例如I帧、P0帧，会对用户产生较大影响；若丢弃的数据包属于低优先级帧的数据，例如P1帧、P2帧，则丢包对用户的影响较小。
目前，为了解决基站随机丢包对用户观看XR业务的影响，通过分层传输的思想进行改善。例如，图3为适用于本申请实施例的QoS流传输的一示意图。如图3所示，UPF实体从XR服务器收到发给UE的数据之后，根据数据流的重要程度，将该数据流通过2个服务质量流(QoS flow)发送给UE，其中，第一QoS流传输重要性程度高的帧，例如I帧和P0帧；第二QoS流传输重要性程度低的帧，例如P1帧和P2帧。
其中，QoS流是5G通信系统中定义的QoS转发处理的最精细粒度，映射到相同QoS流的数据会受到相同的转发处理，如调度策略、排队管理策略、速率整型策略，提供不同的QoS转发处理需要不同的QoS流。
此外，使用I帧、P0帧，以及P1帧、P2帧作为重要性程度的划分只是示例的一种方法，本申请重点关注的是将业务的数据划分为重要性程度高和重要性程度低的两类数据，并不局限于使用此种划分方法，使用任何关于数据重要性程度的划分因素以确定数据的重要性程度，例如，通过观看视频中的视野区数据和非视野区数据进行数据的重要性程度划分。
当基站无法保证数据传输时，例如网络拥塞，基站优先保证发送高优先级的数据(从第一QoS流收到的数据)，丢弃低优先级的数据(从第二QoS流收到的数据)，保证用户的业务体验。
采用以上方式，2个QoS流相互之间具有关联关系，UPF实体根据数据流的重要程度，确定采用第一QoS流传输或是第二QoS流传输。通常情况下，为保证高优先级数据的传输，第一QoS流需创建为保障比特速率(guaranteed bit rate,GBR)QoS流，即，需要网络保证比特速率的QoS流，而第二QoS流创建为non-GBR QoS流，即，不需要网络保证比特速率的QoS流。
对于有特定QoS需求的业务，通常需要由UE或者应用服务器基于业务需求向3GPP核心网设备请求特定的QoS，再由核心网设备配置相应的QoS流。
然而，对于XR业务，3GPP核心网设备无法感知业务何时结束，从而无法及时释放GBR QoS流，因此，可能造成网络资源的浪费，有悖于分层传输提升系统容量的初衷。
此外，基于业务需求并配置QoS参数，并未考虑分层传输机制，可能造成QoS配置机制与分层传输机制不对应的问题，从而导致资源利用率低，分层传输的收益可能大打折扣。
鉴于此，本申请提出了一种会话管理的方法，通过确定QoS流的不活动时长，及时释放GBR QoS流。此外，也基于业务需求并结合分层信息配置QoS参数，提升分层传输的收益。
应理解，在下述各实施例中，第一QoS流为GBR QoS流，即，保障比特速率QoS流，如果存在第二QoS流，第二QoS流为non-GBR QoS流，即，不需要网络保证比特速率的QoS流。
图4为本申请实施例提出的会话管理的方法400的一示意图。在本实施例中，第一网络设备为SMF实体，第二网络设备为基站，第三网络设备为UPF实体。如图4所示，该方法400包括以下步骤：
S401，终端设备确定第一参数。
示例地，终端设备确定第一参数，该第一参数用于第一网络设备确定终端设备的第一服务质量QoS流的第一不活动时长，或，用于第一网络设备确定终端设备的第一会话的第一不活动时长。
具体地，第一QoS流的第一不活动时长表示第一QoS流的持续无数据传输的第一时长，第一会话的第一不活动时长表示第一会话的持续无数据传输的第一时长。其中，第一QoS流或第一会话为用于传输终端设备的业务的数据。进一步地，第一QoS流的第一不活动时长用于确定释放第一Qos流，第一会话的第一不活动时长用于确定释放第一会话的用户面连接。
在可能实现的一种方式中，第一参数为终端设备的业务的第一周期性信息。其中，终端设备的业务的第一周期性信息包括业务的第一帧率的信息，或业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
举例而言，第一帧率的信息为每秒的帧数量信息，即，帧速率(frames per second,FPS)的信息。
举例而言，业务中重要性程度高的帧与重要性程度低的帧的第一比例为1:7，则表明1个重要性程度高的帧后续有7个重要性程度低的帧，即，理解为1个I帧或P0帧之后，跟随7个P1帧或P2帧。
在可能实现的另一种方式中，终端设备根据终端设备的第一周期性信息，确定第一QoS流的第二不活动时长或第一会话的第二不活动时长，第一QoS流的第二不活动时长或第一会话的第二不活动时长为第一参数。其中，第一QoS流的第二不活动时长表示第一QoS流的持续无数据传输的第二时长，第一会话的第二不活动时长表示第一会话的持续无数据传输的第二时长。
举例而言，在FPS为60的情况下，不采用分层时(即，使用一个QoS流或会话传输数据，例如，通过第一QoS流或第一会话传输数据)，设置第一QoS流的第二不活动时长或或第一会话的第二不活动时长应大于或等于16.67ms(1s/60＝16.67ms)，采用分层时(即，使用至少两个QoS流或会话传输数据，例如，通过第一QoS流和第二QoS流，或第一会话和第二会话传输数据，第一QoS流或第一会话传输业务中重要性程度高的数据，第二QoS流或第二会话传输业务中重要性程度低的数据)，如果业务中重要性程度高的帧与重要性程度低的帧的第一比例为1:7，则根据该比例，每8个帧会出现1个重要性程度高的帧，即，重要性程度高的帧为每133.36ms(16.67*8ms＝133.36ms)出现一次，因此， 第一QoS流的第二不活动时长或第一会话的第二不活动时长应大于或等于133.36ms。
应理解，在终端设备的业务的第一周期性信息发生变化的情况下，终端设备根据更新之后的业务的周期性信息，更新第一QoS流的第二不活动时长，或第一会话的第二不活动时长。
此外，XR服务器也确定第一参数，以及，XR服务器确定第一参数的描述参考上述终端设备确定第一参数的描述。
S402，终端设备向第一网络设备发送第一消息。对应地，第一网络设备接收来自终端设备的第一消息。
示例地，终端设备向第一网络设备发送第一消息，该第一消息包括第一参数。
具体地，终端设备在确定第一参数之后，向第一网络设备发送包括第一参数的第一消息。进一步地，第一消息还携带业务的QoS需求以及终端设备的业务相关的五元组(packet filter)信息。其中，本发明不限定第一消息的具体名称，为协议数据单元(protocol data unit,PDU)会话建立/修改请求消息。
需要说明的是，终端设备向第一网络设备发送第一消息，包括终端设备直接将第一消息发送给第一网络设备，也包括终端通过接入网设备、其他核心网设备的中间网元将第一消息发送给第一网络设备。例如终终端先将第一消息发送给接入网设备基站，基站再将第一消息发送给核心网设备AMF，最后由AMF将第一消息发给第一网络设备。
应理解，如果终端设备根据更新之后的业务的周期性信息，更新了第一QoS流的第二不活动时长，或第一会话的第二不活动时长，则终端设备及时向第一网络设备发送更新之后的第一QoS流的第二不活动时长，或第一会话的第二不活动时长。
此外，如果在S401中是XR服务器确定第一参数，则本步骤为XR服务器向第一网络设备发送第一参数。对应地，第一网络设备接收来自XR服务器的第一参数。
需要说明的是，XR服务器向第一网络设备发送第一参数，包括直接将第一参数发送给第一网络设备，也包括通过其他中间网元将第一参数发送给第一网络设备。举例而言，XR服务器向PCF实体发送包括第一参数的消息，进而由PCF实体发起SM策略相关的修改流程，需要说明的是，XR服务器向PCF实体发送包括第一参数的消息，不仅由XR服务器直接向PCF实体发送，也能通过NEF实体向PCF实体发送。
具体地，XR服务器在向PCF实体发送的消息中携带第一参数、QoS需求，以及终端设备的业务相关的五元组(packet filter)的信息，PCF实体调用服务向第一网络设备(SMF实体)发送第一参数、QoS需求，以及终端设备的业务相关的五元组(packet filter)参数，其中，PCF实体调用的服务为Npcf_SMPolicyControl_UpdateNotify。
S403，第一网络设备根据第一参数，确定第一QoS流的第一不活动时长，或，确定第一会话的第一不活动时长。
示例地，第一网络设备根据第一参数，确定第一QoS流的第一不活动时长，或，确定第一会话的第一不活动时长。
在可能实现的一种方式中，第一网络设备根据第一QoS流的第二不活动时长，结合网络策略的因素(例如，网络质量(jitter)、网络负荷因素)，确定第一QoS流的第一不活动时长。进一步地，第一QoS流的第一不活动时长的值应当大于或等于第一QoS流的第二不活动时长的值。
在可能实现的另一种方式中，第一网络设备根据第一会话的第二不活动时长，结合网络策略的因素(例如，网络质量(jitter)、网络负荷因素)，确定第一会话的第一不活动时长。进一步地，第一会话的第一不活动时长的值应当大于或等于第一会话的第二不活动时长的值。
在可能实现的另一种方式中，第一网络设备根据终端设备的业务的第一周期性信息，确定第一QoS流的第一不活动时长或第一会话的第一不活动时长。
具体地，关于第一网络设备根据终端设备的业务的第一周期性信息，确定第一QoS流的第一不活动时长或第一会话的第一不活动时长的描述，结合网络策略的因素，并参考上述S401中终端设备根据终端设备的第一周期性信息，确定第一QoS流的第二不活动时长或第一会话的第二不活动时长的描述，为了简洁，本申请在此不再赘述。
S404a，第一网络设备向终端设备发送包括第一QoS流的第一不活动时长信息的消息。对应地，终端设备接收来自第一网络设备的包括第一QoS流的第一不活动时长信息的消息。
一些实施例，第一网络设备向终端设备发送包括第一QoS流的第一不活动时长信息的消息，从而使得终端设备监控第一QoS流持续无数据传输的时长是否达到第一QoS流的第一不活动时长。
S404b，第一网络设备向第二网络设备发送包括第一QoS流的第一不活动时长信息的消息。对应地，第二网络设备接收来自第一网络设备的包括第一QoS流的第一不活动时长信息的消息。
在一些实施例中，第一网络设备向第二网络设备发送包括第一QoS流的第一不活动时长信息的消息，从而使得第二网络设备监控第一QoS流持续无数据传输的时长是否达到第一QoS流的第一不活动时长。
应理解，S404a与S404b的执行顺序无具体限制，二者执行其一，也能均被执行，本申请在此不做限定。
S405，终端设备在第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的情况下，释放第一QoS流。
在一些实施例中，终端设备根据第一QoS流的第一不活动时长对第一QoS流持续无数据传输的时长进行监控，在第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的情况下，释放第一QoS流。
在可能实现的一种方式中，第一QoS流存在与之关联的第二QoS流，终端设备删除第一QoS流与第二QoS流的关联关系，或，释放与第一QoS流关联的第二QoS流。其中，第一QoS流与第二QoS流均用于传输终端设备的业务的数据，第一QoS流传输业务中重要性程度高的数据，第二QoS流传输所述业务中重要性程度低的数据。
在可能实现的另一种方式中，第一QoS流不存在与之关联的QoS流，终端设备直接释放第一QoS流。
S406，终端设备和/或第二网络设备和/或第三网络设备向第一网络设备发送：指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。对应地，第一网络设备接收来自终端设备和/或第二网络设备和/或第三网络设备的：指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
在一些实施例中，终端设备和/或第二网络设备和/或第三网络设备根据第一QoS流的第一不活动时长对第一QoS流持续无数据传输的时长进行监控，在第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的情况下，向第一网络设备发送指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。其中，该消息为第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的报告消息，还能包括第一QoS流的QoS流标识(QFI)信息，换言之，用于指示第一QoS流满足上报的条件。
举例而言，第三网络设备通过N4报告(N4report)消息的形式向第一网络设备发送指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
S407，第一网络设备向终端设备和/或第二网络设备和/或第三网络设备发送用于指示释放第一QoS流的消息。对应地，终端设备和/或第二网络设备和/或第三网络设备接收来自第一网络设备的用于指示释放第一QoS流的消息。
示例地，第一网络设备在接收指示第一QoS流不活动，和/或，请求释放第一QoS流的消息之后，向终端设备和/或第二网络设备和/或第三网络设备发送用于指示释放第一QoS流的消息。
具体地，第一网络设备根据指示第一QoS流不活动，和/或，请求释放第一QoS流的消息，确定待释放的第一QoS流是否存在关联的QoS流，并向终端设备和/或第二网络设备和/或第三网络设备发送用于指示释放第一QoS流的消息。
举例而言，第一网络设备通过向终端设备发送协议数据单元(protocol data unit,PDU)会话修改消息(PDU Session modification)的形式，发送用于指示释放第一QoS流的消息，和/或，第一网络设备通过向第三网络设备发送N4会话修改消息(N4session modification)的形式，发送用于指示释放第一QoS流的消息。
其中，关于在第一QoS流存在与之关联的QoS流(即，第二QoS流)，以及第一QoS流不存在与之关联的QoS流的两种情况下，分别如何释放第一QoS流的描述，参考上述S405的描述，为了简洁，本申请在此不再赘述。
S408a，终端设备释放第一QoS流。
在一些实施例中，终端设备在接收第一网络设备发送的用于指示释放第一QoS流的消息之后，释放第一QoS流。具体地，关于在第一QoS流存在与之关联的QoS流(即，第二QoS流)，以及第一QoS流不存在与之关联的QoS流的两种情况下，分别如何释放第一QoS流的描述，参考上述S405的相关描述，为了简洁，本申请在此不再赘述。
S408b，第二网络设备释放第一QoS流。
在一些实施例中，第二网络设备在接收第一网络设备发送的用于指示释放第一QoS流的消息之后，释放第一QoS流。具体地，关于在第一QoS流存在与之关联的QoS流(即，第二QoS流)，以及第一QoS流不存在与之关联的QoS流的两种情况下，分别如何释放第一QoS流的描述，参考上述S405的相关描述，为了简洁，本申请在此不再赘述。
S408c，第三网络设备释放第一QoS流。
在一些实施例中，第三网络设备在接收第一网络设备发送的用于指示释放第一QoS流的消息之后，释放第一QoS流。具体地，关于在第一QoS流存在与之关联的QoS流(即，第二QoS流)，以及第一QoS流不存在与之关联的QoS流的两种情况下，分别如何释放第一QoS流的描述，参考上述S405的相关描述，为了简洁，本申请在此不再赘述。
其中，释放第一QoS流包括第二网络设备侧的QoS flow上下文信息(主要包括QoS profile(QFI及对应的QoS参数))。
应理解，在上述方案中，如果S405被执行，则S406、S407中关于第一网络设备与终端设备之间消息交互的步骤，以及S408a不被执行；如果S405不被执行，则执行S406、S407中关于第一网络设备与终端设备之间消息交互的步骤，以及S408a。
S409，终端设备向第一网络设备发送第二消息。对应地，第一网络设备接收来自终端设备的第二消息。
在一些实施例中，终端设备向第一网络发送第二消息，第二消息包含第二参数或第三参数。其中，第二参数用于第一网络设备确定第一QoS流的第一QoS参数，第三参数用于第一网络设备确定第一QoS流的第一QoS参数和第二QoS流的第一QoS参数，第一QoS流的第一QoS参数包括第一QoS流的第一保障流比特速率(Guaranteed flow bit rate,GFBR)、第一最大流比特速率(maximum flow bit rate,MFBR)，或者第一最大数据突发量(maximum data burst volume,MDBV)中的至少一项，第二QoS流的第一QoS参数包括第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
在可能实现的一种方式中，第二参数与第三参数为终端设备的业务的第二周期性信息。
在可能实现的另一种方式中，第二参数为终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定的第一QoS流的第二QoS参数，第三参数为终端设备根据终端设备的业务的第二周期性信息与分层传输的信息确定的第一QoS流的第二QoS参数与第二QoS流的第二QoS参数。其中，第一QoS流的第二QoS参数包括第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，第二QoS流的第二QoS参数包括第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。GFBR指第一网络设备对该QoS流提供的保障速率，MFBR指第一网络设备对该QoS流提供的最高比特速率的限制。
其中，该终端设备的业务的第二周期性信息包括业务的第二帧率的信息、所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
举例而言，终端设备根据业务的GFBR需求信息、第二帧率(FPS)的信息、重要性程度高的帧的数量占比r1(即，重要性程度高的帧的数量/(重要性程度高的帧的数量+重要性程度低的帧的数量))，以及帧大小比r2确定第一QoS流的第二GFBR。
具体地，第一QoS流的第二GFBR＝第二FPS*r1*重要性程度高的帧的大小，重要性程度高的帧的大小＝r2*业务的GFBR需求/(r2*FPS*r1+FPS(1-r1))。
举例而言，第一QoS流的第二MDBV＝第一QoS流的峰均比*第一QoS流的第二GFBR*PDB＝(1/r1)*第一QoS流的第二GFBR*PDB。其中，PDB为包延迟预算(packet delay budget)。
举例而言，第一QoS流的第二MDBV根据PDB的长度与重要性程度高的帧的大小确定。
在一些实施例中，如果PDB<1000/Fps，则第一QoS流的第二MDBV＝重要性程度高的帧的大小*PDB/(1000/Fps)。
在一些实施例中，如果1000/Fps≤PDB≤n*帧配比周期，则第一QoS流的第二MDBV＝n*重要程度高帧大小。
在一些实施例中，如果n*帧配比周期≤PDB≤n*帧配比周期*1000/Fps，则第一QoS流的第二MDBV＝n*重要性程度高的帧的大小+重要性程度高的帧的大小*(PDB-n*帧配比周期)/(1000/Fps)。
其中，帧配比周期是根据重要性程度高的帧与重要性程度低的帧的配比确定的，n为大于或者等于1的整数。
举例而言，第二QoS流的第二GFBR＝业务的GFBR需求-第一QoS流的第二GFBR。
此外，第一网络设备在接收来自第一终端设备的第二消息之后，根据第二消息确定第一QoS流的第一QoS参数，或者确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
在可能实现的一种方式中，第二消息包括第二参数，第一网络设备根据第二参数确定第一QoS流的第一QoS参数。
在一些实施例中，在第二参数为终端设备的业务的第二周期性信息的情况下，第一网络设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第一QoS参数。
具体地，关于根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第一QoS参数的描述，参考上述关于终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数的描述，为了简洁，本申请在此不再赘述。
在一些实施例中，在第二参数为第一QoS流的第二QoS参数的情况下，第一网络设备根据第一QoS流的第二QoS参数确定第一QoS流的第一QoS参数。
在可能实现的另一种方式中，第二消息包括第三参数，第一网络设备根据第二消息确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
在一些实施例中，在第三参数为终端设备的业务的第二周期性信息的情况下，第一网络设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
具体地，关于根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数的描述，参考上述关于终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的描述，为了简洁，本申请在此不再赘述。
在一些实施例中，在第三参数为第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的情况下，第一网络设备根据第一QoS流的第二QoS参数与第二QoS流的第二QoS参数确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
应理解，第一网络设备还根据第二消息确定QoS流的使用机制，即，第二QoS流只传输终端设备的(XR)业务的数据，或第二QoS流不仅传输终端设备的(XR)业务的数据，还传输其他业务的数据。
S410，第一网络设备向终端设备发送包括第一会话的第一不活动时长信息的消息。对应地，终端设备接收来自第一网络设备的包括第一会话的第一不活动时长信息的消息。
在一些实施例中，第一网络设备向终端设备发送包括第一会话的第一不活动时长信息 的消息，从而使得终端设备监控第一会话持续无数据传输的时长是否达到第一会话的第一不活动时长。S411，在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，终端设备去激活第一会话的用户面连接。
在一些实施例中，终端设备根据第一会话的第一不活动时长对第一会话持续无数据传输的时长进行监控，在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，终端设备去激活第一会话的用户面连接。
具体地，去激活第一会话的用户面连接是指释放第一会话对应的终端设备和第二网络设备(基站)之间的无线承载，以及第二网络设备(基站)和第三网络设备(UPF实体)之间的用户面连接，终端设备通过释放第一会话对应的无线承载的方式去激活第一会话的用户面连接。
此外，第二网络设备(基站)和第三网络设备(UPF实体)执行下述操作去激活第一会话的用户面连接：
第二网络设备(基站)：释放第一会话对应的UPF实体端的tunnel info，包括UPF实体的IP地址及tunnel端口号，以及释放第一会话对应的无线承载。
第三网络设备(UPF实体)：释放第一会话对应的AN端的tunnel info，包括基站的IP地址及tunnel端口号。
应理解，释放第一会话的用户面连接是释放第一会话包括的所有的QoS flow对应的用户面连接，因为上述的tunnel info和无线承载的配置的PDU会话均是以QoS flow粒度配置的。
S412，在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，终端设备向第一网络设备发送指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。对应地，第一网络设备接收来自终端设备的指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。
在一些实施例中，终端设备根据第一会话的第一不活动时长对第一会话持续无数据传输的时长进行监控，在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，向第一网络设备发送指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。其中，该消息为第一会话的无数据传输的时长达到第一会话的第一不活动时长的报告消息，换言之，也用于指示第一会话满足上报的条件。
其中，去激活第一会话的用户面连接是指释放第一会话对应的终端设备和基站之间的无线承载，以及基站和UPF实体之间的用户面连接。
S413，第一网络设备向第二网络设备和/或第三网络设备发送指示去激活第一会话的用户面连接的消息。对应地，第二网络设备和/或第三网络设备接收来自第一网络设备的指示去激活第一会话的用户面连接的消息。
在一些实施例中，第一网络设备在接收指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息之后，向第二网络设备和/或第三网络设备发送指示去激活第一会话的用户面连接的消息。
具体地，第一网络设备在接收指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息之后，向第二网络设备和/或第三网络设备发送指示去激活第一会话的用户面连接的消息。
举例而言，第一网络设备通过向第二网络设备发送N2消息的形式，发送指示去激活第一会话的用户面连接的消息。
举例而言，第一网络设备通过向第三网络设备发送N4会话修改消息的形式，发送指示去激活第一会话的用户面连接的消息。
S414，第二网络设备向终端设备发送指示去激活第一会话的用户面连接的消息。对应地，终端设备接收来自第二网络设备的指示去激活第一会话的用户面连接的消息。
在一些实施例中，第二网络设备在接收第一网络设备发送的指示去激活第一会话的用户面连接的消息之后，向终端设备发送指示去激活第一会话的用户面连接的消息。
此外，终端设备在接收来自第二网络设备的指示去激活第一会话的用户面连接的消息之后，去激活第一会话的用户面连接。
具体地，关于去激活第一会话的用户面连接的描述，参考上述S411中关于去激活第一会话的用户面连接的描述，为了简洁，本申请在此不做赘述。
应理解，在上述方案中，S405至S409与S410至S414是独立的两种方案，如果S405至S409被执行，则不执行S410至S414；如果S410至S414被执行，则不执行S405至S409。
基于上述方案，通过终端设备的业务的第一周期性信息直接或间接确定的第一QoS流的第一不活动时长，或第一会话的第一不活动时长，使得第一QoS流及时被释放，或第一会话的用户面连接及时被去激活，从而节省网络资源。此外，通过终端设备的业务的第二周期性信息直接或间接确定的第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数，从而基于业务需求的信息与分层传输的信息确定第一QoS流，或第一QoS流与第二QoS流的QoS参数，提升网络资源的利用效率。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过节省网络资源以及提升网络资源的利用效率的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
图5为本申请实施例提出的一种会话管理的方法500的一示意图。如图5所示，该方法500包括以下步骤：
S501，终端设备生成第二消息。
在一些实施例中，终端设备生成第二消息，该第二消息包括第二参数或第三参数。第二参数用于第一网络设备确定第一QoS流的第一QoS参数，第三参数用于第一网络设备确定第一QoS流的第一QoS参数和第二QoS流的第一QoS参数，第一QoS流的第一QoS参数包括第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，第二QoS流的第一QoS参数包括第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。其中，第一QoS流与第二QoS流均用于传输终端设备的业务的数据。
具体地，关于第二消息包括第二参数或第三参数，以及第二参数与第三参数的描述，参考上述S409中关于第二消息包括第二参数或第三参数，以及第二参数与第三参数的描述，为了简洁，本申请在此不再赘述。
S502，终端设备向第一网络设备发送第二消息。对应地，第一网络设备接收来自终端设备的第二消息。
示例地，终端设备向第一网络设备发送第二消息，
S503，第一网络设备根据第二消息，确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
在一些实施例中，第一网络设备根据第二消息，确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
具体地，关于第一网络设备根据第二消息，确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数的描述，参考上述S409中关于第一网络设备在接收来自第一终端设备的第二消息之后，根据第二消息确定第一QoS流的第一QoS参数，或者确定第一QoS流的第一QoS参数与第二QoS流的第一QoS参数的描述，为了简洁，本申请在此不再赘述。
基于上述方案，通过终端设备的业务的第二周期性信息直接或间接确定的第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数，从而基于业务需求的信息与分层传输的信息确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数，提升网络资源的利用效率。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过提升网络资源的利用效率的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
图6为本申请实施例提供的一种会话管理方法600的一示意图。如图6所示，该方法600包括以下步骤：
S601，终端设备与XR服务器建立接口(socket)连接。
示例地，终端设备启动XR应用，并与XR服务器建立接口(socket)连接。
具体地，终端设备与XR服务器建立接口(socket)连接，并进行应用层媒体协商，例如，通过超文本传送协议(hypertext transfer protocol,HTTP)进行终端设备的XR媒体流业务的周期性信息的协商。其中，关于终端设备的XR媒体流业务的周期性信息的描述，参考上述S401中终端设备的业务的第一周期性信息的描述，为了简洁，本申请在此不再赘述。
S602，终端设备向AMF实体发送包括第一参数的消息。对应地，AMF实体接收来自终端设备的包括第一参数的消息。
示例地，终端设备与XR服务器建立连接之后，根据协商结果，终端设备确定第一Qos流为GBR QoS流，并向AMF实体发送包括第一参数的消息。其中，第一参数用于第一网络设备确定终端设备的第一服务质量QoS流的第一不活动时长，或，用于第一网络设备确定终端设备的第一会话的第一不活动时长。
具体地，第一QoS流的第一不活动时长表示第一QoS流的持续无数据传输的第一时长，第一会话的第一不活动时长表示第一会话的持续无数据传输的第一时长。其中，第一QoS流或第一会话为用于传输终端设备的业务的数据。进一步地，第一QoS流的第一不活动时长用于确定释放第一Qos流，第一会话的第一不活动时长用于确定释放第一会话的用户面连接。
举例而言，终端设备向AMF实体发送会话修改请求消息，该会话请求消息携带第一 参数、QoS需求，以及终端设备的业务相关的五元组(packet filter)的信息。
其中，关于第一参数的描述，参考S401中关于第一参数的描述，为了简洁，本申请在此不再赘述。
S603，AMF实体调用服务向SMF实体发送第一参数。对应地，SMF实体接收来自AMF实体调用服务的第一参数。
示例地，AMF实体在接收终端设备发送的第一参数之后，调用服务向SMF实体发送第一参数。
举例而言，AMF实体调用的服务为Nsmf_PDUSession_CreateSMContext，或者Nsmf_PDUSession_UpdateSMContext。
S604，XR服务器触发PCF实体发起SM策略相关的修改流程。
示例地，XR服务器与终端设备建立连接之后，根据协商结果，XR服务器向PCF实体发送包括第一参数的消息，进而由PCF实体发起SM策略相关的修改流程，需要说明的是，XR服务器向PCF实体发送包括第一参数的消息，由XR服务器直接向PCF实体发送，也通过NEF实体向PCF实体发送。
具体地，XR服务器在向PCF实体发送的消息中携带第一参数、QoS需求，以及终端设备的业务相关的五元组(packet filter)参数，PCF实体调用服务向SMF发送第一参数、QoS需求，以及终端设备的业务相关的五元组(packet filter)参数，其中，PCF调用的服务为Npcf_SMPolicyControl_UpdateNotify。
S605，SMF实体确定第一QoS流的第一不活动时长，或确定第一会话的第一不活动时长。
示例地，SMF实体在接收包含第一参数的消息之后，根据第一参数确定第一QoS流的第一不活动时长，或确定第一会话的第一不活动时长。
具体地，SMF实体确定根据第一参数确定第一QoS流的第一不活动时长，或确定第一会话的第一不活动时长的描述，参考上述S403中关于第一网络设备根据第一参数，确定第一QoS流的第一不活动时长，或，确定第一会话的第一不活动时长的描述，为了简洁，本申请在此不再赘述。
S606，SMF实体向终端设备，和/或基站，和/或UPF实体发送包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息。对应地，终端设备，和/或基站，和/或UPF实体接收来自SMF实体的包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息。
示例地，SMF实体在确定第一QoS流的第一不活动时长，或第一会话的第一不活动时长之后，向终端设备，和/或基站，和/或UPF实体发送包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息，从而使得终端设备，和/或基站，和/或UPF实体监控第一QoS流的持续无数据传输的时长是否达到第一QoS流的第一不活动时长，或第一会话的持续无数据传输的时长是否达到第一会话的第一不活动时长。
S607a，终端设备监控第一QoS流的不活动时长，或第一会话的不活动时长。
示例地，终端设备在接收来自SMF的包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息之后，根据上述消息，监控第一QoS流的不活动时长，或第一会话的不活动时长。
具体地，终端设备根据第一QoS流的第一不活动时长的消息，监控第一QoS流的无数据传输的时长是否达到第一QoS流的第一不活动时长，或根据第一会话的第一不活动时长的消息，监控第一会话的无数据传输的时长是否达到第一会话的第一不活动时长。
S607b，基站监控第一QoS流的不活动时长，或第一会话的不活动时长。
示例地，基站在接收来自SMF的包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息之后，根据上述消息，监控第一QoS流的不活动时长，或第一会话的不活动时长。
具体地，基站根据第一QoS流的第一不活动时长的消息，监控第一QoS流的无数据传输的时长是否达到第一QoS流的第一不活动时长，或根据第一会话的第一不活动时长的消息，监控第一会话的无数据传输的时长是否达到第一会话的第一不活动时长。
S607c，UPF实体监控第一QoS流的不活动时长，或第一会话的不活动时长。
示例地，UPF实体在接收来自SMF的包含第一QoS流的第一不活动时长的消息，或包含第一会话的第一不活动时长的消息之后，根据上述消息，监控第一QoS流的不活动时长，或第一会话的不活动时长。
具体地，UPF实体根据第一QoS流的第一不活动时长的消息，监控第一QoS流的无数据传输的时长是否达到第一QoS流的第一不活动时长，或根据第一会话的第一不活动时长的消息，监控第一会话的无数据传输的时长是否达到第一会话的第一不活动时长。
应理解，S607a、S607b、S607c为独立的三个步骤。
S608，终端设备，和/或基站，和/或UPF实体向SMF实体发送指示第一QoS流不活动，和/或，请求释放第一QoS流的消息，或指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。对应地，SMF实体接收来自终端设备，和/或基站，和/或UPF实体的指示第一QoS流不活动，和/或，请求释放第一QoS流的消息，或指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。
在一些实施例中，终端设备和/或基站，和/或UPF实体在第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的情况下，向SMF实体发送指示第一QoS流不活动，和/或，请求释放第一QoS流的消息；或在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，向SMF实体发送指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息。
在可能实现的一种方式中，UPF实体通过N4报告(N4report)消息的形式向SMF实体发送。其中，该消息表示为第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的报告消息，还包括第一QoS流的QoS流标识(QFI)信息，换言之，也用于指示第一QoS流满足上报的条件；或者，该消息表示为第一会话的无数据传输的时长达到第一会话的第一不活动时长的报告消息，指示第一会话满足上报的条件。
在可能实现的另一种方式中，终端设备向SMF实体发送第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的报告消息，从而指示第一QoS流不活动，和/或，请求释放第一QoS流；或向SMF实体发送第一会话的无数据传输的时长达到第一会话的第一不活动时长的报告消息，从而指示第一会话不活动，和/或，请求去激活第一会话的用户面连接。
在可能实现的另一种方式中，基站向SMF实体发送第一QoS流的无数据传输的时长 达到第一QoS流的第一不活动时长的报告消息，从而指示第一QoS流不活动，和/或，请求释放第一QoS流；或向SMF实体发送第一会话的无数据传输的时长达到第一会话的第一不活动时长的报告消息，从而指示第一会话不活动，和/或，请求去激活第一会话的用户面连接。
S609，SMF实体确定释放第一QoS流，或去激活第一会话的用户面连接。
在一些实施例中，SMF实体根据指示第一QoS流不活动，和/或，请求释放第一QoS流的消息，确定待释放的第一QoS流是否存在关联的QoS流，以及确定释放第一QoS流；或者，SMF实体根据指示第一会话不活动，和/或，请求去激活第一会话的用户面连接的消息，确定去激活第一会话的用户面连接。
S610，SMF实体向终端设备，和/或基站，和/或UPF实体发送用于指示释放第一QoS流的消息。
在一些实施例中，SMF实体在确定释放第一QoS流的情况下，向终端设备，和/或基站，和/或UPF实体发送用于指示释放第一QoS流的消息。
在可能实现的一种方式中，SMF实体通过向终端设备发送PDU会话修改消息的形式，发送用于指示释放第一QoS流的消息。
在可能实现的另一种方式中，SMF实体通过向基站发送N2消息的形式，发送用于指示释放第一QoS流的消息。
在可能实现的另一种方式中，SMF实体通过向UPF实体发送N4会话修改消息的形式，发送用于指示释放第一QoS流的消息。
S611a，终端设备执行第一操作。
示例地，终端设备执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
在可能实现的一种方式中，终端设备通过监控第一QoS流的不活动时长，在第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的情况下，终端设备释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
在一些实施例中，第一QoS流存在与之关联的第二QoS流，终端设备删除第一QoS流与第二QoS流的关联关系，或，释放与第一QoS流关联的第二QoS流。其中，第一QoS流与第二QoS流均用于传输终端设备的业务的数据，第一QoS流传输业务中重要性程度高的数据，第二QoS流传输所述业务中重要性程度低的数据。
在一些实施例中，第一QoS流不存在与之关联的QoS流，终端设备直接释放第一QoS流。
在可能实现的另一种方式中，终端设备通过接收SMF实体发送的用于指示释放第一QoS流的消息，执行第一操作。
S611b，基站执行第一操作。
示例地，基站执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
具体地，关于基站执行第一操作的描述，参考上述S611a中关于终端设备执行第一操作的描述，为了简洁，本申请在此不再赘述。
S611c，UPF实体执行第一操作。
示例地，UPF实体执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
具体地，关于UPF实体执行第一操作的描述，参考上述S611a中关于终端设备执行第一操作的描述，为了简洁，本申请在此不再赘述。
S612，SMF实体向基站和/或UPF实体发送指示去激活第一会话的用户面连接的消息。对应地，基站和/或UPF实体接收来自SMF实体的指示去激活第一会话的用户面连接的消息。
在一些实施例中，SMF实体向基站和/UPF实体发送指示去激活第一会话的用户面连接的消息。
举例而言，SMF实体通过向UPF实体发送N4会话修改消息，发送指示去激活第一会话的用户面连接的消息。
S613，基站向终端设备发送指示去激活第一会话的用户面连接的消息，例如RRC reconfiguration消息。对应地，终端设备接收来自基站的指示去激活第一会话的用户面连接的消息。
在一些实施例中，基站在接收来自SMF实体的指示去激活第一会话的用户面连接的消息之后，向终端设备发送指示去激活第一会话的用户面连接的消息。
S614a，终端设备执行第二操作。
示例地，终端设备执行第二操作，该第二操作包括去激活第一会话的用户面连接，或删除第一会话与第二会话的关联关系，其中，第一会话与第二会话均用于传输终端设备的业务的数据，第一会话传输业务中重要性程度高的数据，第二会话传输所述业务中重要性程度低的数据。
在可能实现的一种方式中，终端设备通过监控第一会话的不活动时长，在第一会话的无数据传输的时长达到第一会话的第一不活动时长的情况下，终端设备去激活第一会话的用户面连接，或删除第一会话与第二会话的关联关系。
在可能实现的另一种方式中，终端设备通过接收基站发送的用于指示去激活第一会话的用户面连接的消息，去激活第一会话的用户面连接，或删除第一会话与第二会话的关联关系。
具体地，终端设备通过释放第一会话对应的无线承载，从而去激活第一会话的用户面连接。
S614b，基站执行第二操作。
示例地，基站在接收SMF实体发送的指示去激活第一会话的用户面连接的消息之后，执行第二操作，该第二操作参考上述S614a中关于第二操作的描述。
具体地，基站通过释放第一会话对应的UPF实体端的tunnel info(包括UPF实体的IP地址及tunnel端口号)，以及释放第一会话对应的无线承载，从而去激活第一会话的用户面连接。
S614c，UPF实体执行第二操作。
示例地，UPF实体在接收SMF实体发送的指示去激活第一会话的用户面连接的消息之后，执行第二操作，该第二操作参考上述S614a中关于第二操作的描述。具体地，UPF实体通过释放第一会话对应的AN端的tunnel info(包括基站的IP地址及tunnel端口号)， 从而去激活第一会话的用户面连接。
应理解，释放第一会话的用户面连接是释放第一会话包括的所有的QoS flow对应的用户面连接，因为上述的tunnel info和无线承载的配置的PDU会话均是以QoS flow粒度配置的。
基于上述方案，在终端设备或XR服务器确定使用第一QoS流(GBR QoS流)时，根据终端设备的业务的第一周期性信息确定第一QoS流的第二不活动时长或第一会话的第二不活动时长并发送至SMF实体，SMF实体基于终端设备或XR服务器的请求，结合网络策略(网络质量Jitter、网络负荷)，确定第一QoS流的第一不活动时长或第一会话的第一不活动时长。SMF实体将包含第一QoS流的第一不活动时长信息的消息或包含第一会话的第一不活动时长信息的消息发送至终端设备，和/或UPF实体，和/或基站，以请求终端设备，和/或UPF实体，和/或基站监控第一QoS流的无数据传输的时长，或第一会话的无数据传输的时长，如果第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长，执行第一操作，或将该事件上报至SMF实体，SMF实体确定释放第一QoS流(GBR QoS流)并更新与之关联的QoS流(第二QoS流)；或如果第一会话的无数据传输的时长达到第一会话的第一不活动时长，将该事件上报至SMF实体，SMF实体确定去激活第一会话的用户面连接。SMF实体将指示释放第一QoS流的消息发送至终端设备，和/或UPF实体，和/或基站，使得终端设备，和/或UPF实体，和/或基站及时执行第一操作，或发送指示去激活第一会话的用户面连接的消息至第二网络设备，使得第二网络设备发送指示去激活第一会话的用户面连接的消息至终端设备，以便终端设备及时执行第二操作，节省网络资源。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过节省网络资源的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
图7为本申请实施例提供的一种会话管理方法700的一示意图。如图7所示，该方法700包括以下步骤：
S701a，终端设备确定终端设备的业务的终止。
示例地，终端设备确定终端设备的业务的终止。
在可能实现的一种方式中，终端设备通过其内部的应用于调制解调器，即，通过确定终端设备的业务终止的方法800，确定终端设备的业务的终止。图8为确定终端设备的业务终止的方法800的一示意图。其中，如图8所示，该方法800包括如下步骤：
S801，调制解调器确定建立GBR QoS流。
示例地，在传输终端设备的业务的数据的情况下，调制解调器确定建立GBR QoS流(第一QoS流)。
S802，调制解调器向应用发送订阅绑定的应用程序的停止信息或转入后台的信息。对应地，应用接收来自调制解调器的订阅绑定的应用程序的停止信息或转入后台的信息。
示例地，调制解调器在确定建立GBR QoS流(第一QoS流)之后，向应用发送订阅绑定的应用程序的停止信息或转入后台的信息，该信息指示订阅的事件为停止服务检测(stop of service detection)、连接标识为IP地址，或会话标识(session ID)，或会话(session) 关联的五元组(packet filter)信息，或其他终端设备内部用于连接的标识。
S803，应用确定应用程序终止或转入后台。
示例地，应用在接收订阅绑定的应用程序的停止信息或转入后台的信息之后，将应用程序终止或转入后台。
S804，应用向调制解调器发送通知信息。对应地，调制解调器接收来自应用的通知信息。
示例地，应用在确定应用程序终止或转入后台之后，向调制解调器发送通知信息，通知调制解调器应用已将应用程序终止或转入后台。其中，该通知信息包括停止服务检测的信息、连接标识的信息，或者会话(session)关联的五元组(packet filter)信息。
S805，调制解调器发起会话修改流程，释放对应的GBR QoS流。
示例地，调制解调器在接收通知信息之后，发起会话修改流程。
在可能实现的另一种方式中，终端设备不需要内部的应用与调制解调器的交互，根据终端设备的(XR)业务的第一周期性信息，确定GBR QoS流(第一QoS流)的第二不活动时长后，监控GBR QoS流(第一QoS流)的不活动情况，在GBR QoS流(第一QoS流)持续的无数据传输的时长达到GBR QoS流(第一QoS流)的第二不活动时长的情况下，发起会话修改流程。其中，关于终端设备的(XR)业务的第一周期性信息的描述，参考上述S401中关于终端设备的业务的第一周期性信息的描述，为了简洁，本申请在此不再赘述。
S701b，XR服务器确定终端设备的业务的终止。
示例地，XR服务器确定终端设备的业务的终止。
S702，SMF实体接收指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
示例地，SMF实体接收来自终端设备或XR服务器的指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
在可能实现的一种方式中，终端设备在第一QoS流持续的无数据传输的时长达到第一QoS流的第二不活动时长的情况下，向SMF实体发送指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。对应地，SMF实体接收来自终端设备的指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
具体地，终端设备向SMF实体发送第一QoS流的无数据传输的时长达到第一QoS流的第一不活动时长的报告消息，从而指示第一QoS流不活动，和/或，请求释放第一QoS流。
在可能实现的另一种方式中，XR服务器在确定终端设备的业务的终止之后，通过向策略控制功能(policy control function,PCF)实体向SMF实体发送AF通知消息，使得PCF实体向SMF实体发送SM策略关联修改消息，触发SMF实体释放第一QoS流。理解为，SMF实体收到了指示第一QoS流不活动，和/或，请求释放第一QoS流的消息。
S703，SMF实体确定释放第一QoS流。
示例地，SMF实体根据指示第一QoS流不活动，和/或，请求释放第一QoS流的消息，确定待释放的第一QoS流是否存在关联的QoS流，以及确定释放第一QoS流。
S704，SMF实体向终端设备，和/或基站，和/或UPF实体发送用于指示释放第一QoS流的消息。
示例地，SMF实体在确定释放第一QoS流的情况下，向终端设备，和/或基站，和/或UPF实体发送用于指示释放第一QoS流的消息。
在可能实现的一种方式中，SMF实体通过向终端设备发送PDU会话修改消息的形式，发送用于指示释放第一QoS流的消息。
在可能实现的另一种方式中，SMF实体通过向UPF实体发送N4会话修改消息的形式，发送用于指示释放第一QoS流的消息。
S705a，终端设备执行第一操作。
示例地，终端设备执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
具体地，关于终端设备执行第一操作的描述，参考上述S612a中关于终端设备执行第一操作的描述，为了简洁，本申请在此不再赘述。
S705b，基站执行第一操作。
示例地，基站执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
具体地，关于基站执行第一操作的描述，参考上述S612b中关于基站执行第一操作的描述，为了简洁，本申请在此不再赘述。
S705c，UPF实体执行第一操作。
示例地，UPF实体执行第一操作，该第一操作包括释放第一QoS流，或去激活与第一QoS流关联的第二QoS流的用户面连接。
具体地，关于UPF实体执行第一操作的描述，参考上述S612c中关于UPF实体执行第一操作的描述，为了简洁，本申请在此不再赘述。
基于上述方案，终端设备确定使用第一QoS流(GBR QoS流)的业务终止之后，释放第一QoS流(GBR QoS流)。其中，在终端设备确定使用第一QoS流(GBR QoS流)的业务终止的过程中，终端设备的调制解调器建立有第一QoS流(GBR QoS流)的PDU会话，向终端设备的应用订阅绑定的应用程序终止或者转入后台的信息，终端设备的应用接收到通知后触发PDU会话修改。从而，节省网络资源。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过节省网络资源的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
图9为本申请实施例提供的一种会话管理方法900的一示意图。如图9所示，该方法900包括以下步骤：
S901，终端设备与XR服务器建立接口(socket)连接。
示例地，终端设备启动XR应用，并与XR服务器建立接口(socket)连接。
具体地，终端设备与XR服务器建立接口(socket)连接，并进行应用层媒体协商，例如，通过超文本传送协议(hypertext transfer protocol,HTTP)进行终端设备的XR媒体流业务的周期性信息的协商。其中，关于终端设备的XR媒体流业务的周期性信息的描述，参考上述S401中终端设备的业务的第一周期性信息的描述，为了简洁，本申请在此不再赘述。
S902a，终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数。
示例地，终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数。
具体地，关于终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的描述，参考上述S409中终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的描述，为了简洁，本申请在此不再赘述。
S902b，XR服务器根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数。
示例地，XR服务器根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数。
具体地，关于XR服务器根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的描述，参考上述S409中终端设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的描述，为了简洁，本申请在此不再赘述。
S903，终端设备向AMF实体发送包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。对应地，AMF实体接收来自终端设备的包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
示例地，终端设备在确定第一QoS流的第二QoS参数，第一QoS流的第二QoS参数与第二QoS流的第二QoS参数之后，向AMF实体发送包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
举例而言，终端设备向AMF实体发送PDU会话修改请求消息，包含上述参数的信息。
S904，AMF实体向SMF实体发送包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。对应地，SMF实体接收来自AMF实体的包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
示例地，AMF实体向SMF实体发送包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
举例而言，AMF实体向SMF实体发送PDU会话SM上下文更新消息，包含上述参数的信息。
S905，XR服务器向SMF实体发送包含第一QoS流的第二QoS参数的消息，或包含 第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。对应地，SMF实体接收来自XR服务器的包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
示例地，XR服务器在确定第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数之后，向SMF实体发送包含第一QoS流的第二QoS参数的消息，或包含第一QoS流的第二QoS参数与第二QoS流的第二QoS参数的消息。
举例而言，XR服务器向SMF实体发起SM策略关联的修改流程，在请求消息中携带上述参数的信息。
S906，SMF实体确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
示例地，SMF实体根据第一QoS流的第二QoS参数，或第一QoS流的第二QoS参数与第二QoS流的第二QoS参数，以及网络策略的信息，确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
此外，SMF实体还根据第一QoS流的第一QoS参数信息，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数信息确定QoS流的使用机制，即，第二QoS流只传输终端设备的(XR)业务的数据，或第二QoS流不仅传输终端设备的(XR)业务的数据，还传输其他业务的数据。
S907，SMF实体调用服务向AMF实体发送第四参数。对应地，AMF实体接收来自SMF实体调用服务的第四参数。
示例地，SMF实体调用服务向AMF实体发送第四参数，该第四参数包括第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数，以及指示第一QoS流与第二QoS流存在关联关系。
其中，AMF实体提供的服务为Namf_Communication_N1N2MessageTransfer，其中N1 SM container是SMF实体通过AMF实体要发送给终端设备的，N2 SM information是SMF实体通过AMF实体要发送给基站的，第四参数包含于N2 SM information中。另外，N1 SM container也向终端设备发送第一QoS流和第二QoS流的参数，以及关联关系。
此外，该第四参数还包括第一指示信息，其中，第一指示信息用于指示第二QoS流传输的数据是否仅为与第一QoS流具有关联关系的数据，即，第二QoS流仅传输终端设备的XR业务的数据，或传输终端设备的XR业务的数据与其他业务的数据，如果第二QoS流同时传输终端设备的XR业务的数据与其他业务的数据，则无线接入网(RAN)设备需要解析后续从第二QoS流接收的数据包的包头(例如UPF实体与RAN之间的传输协议通常使用GTP协议，为GTP用户面数据包头(GTP-U头))中是否携带第二指示信息，其中，第二指示信息用于指示该数据包是否是与第一QoS流传输的数据包有关联关系的数据包。如果第二QoS流只传输终端设备的XR业务的数据，则RAN设备无需解析后续从第二QoS流接收的数据包的包头。
S908，AMF实体向基站发送N2消息。对应地，基站接收来自AMF实体的N2消息。
示例地，AMF实体在接收来自SMF实体发送的第四消息之后，向基站发送N2消息，该N2消息包括第一指示信息。
S909，基站向终端设备发送AN消息。对应地，终端设备接收来自基站的AN消息。
示例地，基站在收到来自AMF实体的N2消息之后，向终端设备发送AN消息，该AN消息包括N1 SM容器的信息，即，包含会话修改指令的信息。
S910，AMF实体向终端设备发送N1消息。对应地，终端设备接收来自AMF实体的N1消息。
示例地，AMF实体在接收来自SMF实体发送的第四消息之后，向终端设备发送N1消息，该N1消息包括第一指示信息。
具体地，AMF实体通过基站向终端设备发送上述N1消息。
应理解，在上述方案中，S908、S909，与S910为独立的方案。
S911，SMF实体向UPF实体发送N4会话修改请求消息。对应地，UPF实体接收来自SMF实体的N4会话修改请求消息。
示例地，SMF实体向UPF实体发送N4会话修改请求消息，该消息包括第一QoS流的第一QoS参数与第二QoS流的第一QoS参数信息，以及第一QoS流与第二QoS流的关联关系的信息。
S912，UPF实体向基站发送包括第二指示信息的第二QoS流传输的业务的数据。对应地，基站接收来自UPF实体的包括第二指示信息的第二QoS流传输的业务的数据。
示例地，UPF在接收来自SMF实体的N4会话修改请求消息之后，向基站发送包括第二指示信息的第二QoS流传输的业务的数据，从而指示上述数据与第一QoS流传输的数据是否具有关联关系。
基于上述方案，终端设备或XR服务器根据重要程度高的帧与重要程度低的帧配比、帧大小比、业务GFBR需求、帧率确定分层后的每层对应的QoS参数，并向SMF实体发出请求。SMF实体基于终端设备或XR服务器请求的QoS参数，确定QoS流的使用机制，并确定第一QoS流，或第一QoS流与第二QoS流对应的QoS参数，提升网络资源利用效率。
之后，SMF实体向基站(RAN)发送第一指示信息，用于指示第二QoS流传输的数据是否仅为与第一QoS流具有关联关系的数据，即，第二QoS流传输的数据为仅传输终端设备的(XR)业务的数据，还是传输该(XR)业务与其他业务的数据，若是，则RAN解析后续通过第二QoS流接收的数据包的包头(例如GTP-U头)中是否携带第二指示信息，若否，RAN则无需解析后续通过第二QoS流接收的数据包的包头。其中，第二指示信息用于指示该数据包是否为与第一QoS流传输的数据包有关联关系的数据包。
此外，UPF实体将映射到第二QoS流上的数据，在向RAN发送时，在数据包的包头中增加第二指示信息。例如，当第二指示信息为1时，指示该数据包为与第一QoS流传输的数据包有关联关系的数据包，当第二指示信息为0时，指示该数据包为与第一QoS流传输的数据包无关联关系的数据包。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过提升网络资源的利用效率的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
图10为本申请实施例提供的一种会话管理方法1000的一示意图。如图10所示，该方法1000包括以下步骤：
S1001，终端设备与XR服务器建立接口(socket)连接。
示例地，终端设备启动XR应用，并与XR服务器建立接口(socket)连接。
具体地，终端设备与XR服务器建立接口(socket)连接，并进行应用层媒体协商，例如，通过超文本传送协议进行终端设备的XR媒体流业务的周期性信息的协商。其中，关于终端设备的XR媒体流业务的周期性信息的描述，参考上述S401中终端设备的业务的第一周期性信息的描述，为了简洁，本申请在此不再赘述。
S1002a，终端设备根据终端设备的业务需求，确定请求的第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
示例地，终端设备在与XR服务器建立接口连接之后，根据协商的结果，确定向SMF实体请求第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
S1002b，XR服务器根据终端设备的业务需求，确定请求的第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
示例地，XR服务器在与终端设备建立接口连接之后，根据协商的结果，确定向SMF实体请求第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
S1003，终端设备向AMF实体发送包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。对应地，AMF实体接收来自终端设备的包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。
示例地，终端设备在确定请求的QoS参数之后，向AMF实体发送包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。
举例而言，终端设备向AMF实体发送PDU会话修改请求消息，包含上述信息。
其中，关于终端设备的业务的第二周期性信息的描述，参考上述S409中关于终端设备的业务的第二周期性信息的描述，为了简洁，本申请在此不再赘述。
S1004，AMF实体向SMF实体发送包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。对应地，SMF实体接收来自AMF实体的包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。
示例地，AMF实体在接收来自终端设备的含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息之后，向SMF实体发送包含上述信息的消息。
举例而言，AMF实体向SMF实体发送PDU会话SM上下文更新消息，包含上述信息。
S1005，XR服务器向SMF实体发送包含终端设备的业务的第二周期性信息、业务中 重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。对应地，SMF实体接收来自XR服务器的包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。
示例地，XR服务器在确定请求的QoS参数之后，向SMF实体发送包含终端设备的业务的第二周期性信息、业务中重要性程度高的帧的大小与重要性程度低的帧的大小的比例信息，以及业务的GFBR需求的信息的消息。
举例而言，XR服务器向SMF实体发起SM策略关联的修改流程，在请求消息中携带上述参数的信息。
其中，关于终端设备的业务的第二周期性信息的描述，参考上述S409中关于终端设备的业务的第二周期性信息的描述，为了简洁，本申请在此不再赘述。
S1006，SMF实体根据业务的第二周期性信息与业务的分层传输的信息确定第一QoS流的第一QoS参数的消息，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
示例地，SMF实体根据终端设备的业务的第二周期性信息与业务的分层传输的信息确定第一QoS流的第一QoS参数的消息，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数。
具体地，关于SMF确定第一QoS流的第一QoS参数的消息，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数的描述，参考上述S409中关于第一网络设备根据终端设备的业务的第二周期性信息，以及业务的分层传输的信息确定第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数的描述，为了简洁，本申请在此不再赘述。
S1007，SMF实体确定QoS流的使用机制。
示例地，SMF实体确定QoS流的使用机制，即，第二QoS流只传输终端设备的(XR)业务的数据，或第二QoS流不仅传输终端设备的(XR)业务的数据，还传输其他业务的数据。
S1008，SMF实体调用服务向AMF实体发送第四参数。对应地，AMF实体接收来自SMF实体调用服务的第四参数。
示例地，SMF实体调用服务向AMF实体发送第四参数，该第四参数包括第一QoS流的第一QoS参数，或第一QoS流的第一QoS参数与第二QoS流的第一QoS参数，以及指示第一QoS流与第二QoS流存在关联关系。进一步地，该第四参数还包括第一指示信息，该第一指示信息用于指示第二QoS流传输的数据是否仅为与第一QoS流具有关联关系的数据。
其中，AMF实体提供的服务为Namf_Communication_N1N2MessageTransfer，其中N1 SM container是SMF实体通过AMF实体要发送给终端设备的，N2 SM information是SMF实体通过AMF实体要发送给基站的，第四参数包含于N2 SM information中。另外，N1 SM container也向终端设备发送第一QoS流和第二QoS流的参数，以及关联关系。
具体地，关于第四参数与第一指示信息的描述，参考上述S907中关于第四参数与第一指示信息的描述，为了简洁，本申请在此不再赘述。
S1009，AMF实体向基站发送N2消息。对应地，基站接收来自AMF实体的N2消息。
示例地，AMF实体在接收来自SMF实体发送的第四消息之后，向基站发送N2消息，该N2消息包括第一指示信息。
S1010，基站向终端设备发送AN消息。对应地，终端设备接收来自基站的AN消息。
示例地，基站在收到来自AMF实体的N2消息之后，向终端设备发送AN消息，该AN消息包括N1 SM容器的信息，即，包含会话修改指令的信息。
S1011，AMF实体向终端设备发送N1消息。对应地，终端设备接收来自AMF实体的N1消息。
示例地，AMF实体在接收来自SMF实体发送的第四消息之后，向终端设备发送N1消息，该N1消息包括第一指示信息。
具体地，AMF实体通过基站向终端设备发送上述N1消息。
应理解，在上述方案中，S1009、S1010，与S1011为独立的方案。
S1012，SMF实体向UPF实体发送N4会话修改请求消息。对应地，UPF实体接收来自SMF实体的N4会话修改请求消息。
示例地，SMF实体向UPF实体发送N4会话修改请求消息，该消息包括第一QoS流的第一QoS参数与第二QoS流的第一QoS参数信息，以及第一QoS流与第二QoS流的关联关系的信息。
S1013，UPF实体向基站发送包括第二指示信息的第二QoS流传输的业务的数据。对应地，基站接收来自UPF实体的包括第二指示信息的第二QoS流传输的业务的数据。
示例地，UPF在接收来自SMF实体的N4会话修改请求消息之后，向基站发送包括第二指示信息的第二QoS流传输的业务的数据，从而指示上述数据与第一QoS流传输的数据是否具有关联关系。
具体地，关于第二指示信息的描述，参考上述S907中关于第二指示信息的描述，为了简洁，本申请在此不再赘述。
基于上述方案，终端设备向SMF实体发送业务的第二周期性信息(如帧率FPS、重要程度高的帧与重要程度低的帧配比)、帧大小比的信息、业务GFBR需求的信息，使得SMF实体基于业务需求及分层参数、业务GFBR需求、帧率确定各层对应的QoS参数，提升网络资源利用效率。
之后，SMF实体向基站(RAN)发送第一指示信息，用于指示第二QoS流传输的数据是否仅为与第一QoS流具有关联关系的数据，即，第二QoS流传输的数据为仅传输终端设备的(XR)业务的数据，还是传输该(XR)业务与其他业务的数据，若是，则RAN解析后续通过第二QoS流接收的数据包的包头(例如GTP-U头)中是否携带第二指示信息，若否，RAN则无需解析后续通过第二QoS流接收的数据包的包头。其中，第二指示信息用于指示该数据包是否为与第一QoS流传输的数据包有关联关系的数据包。
此外，UPF实体将映射到第二QoS流上的数据，在向RAN发送时，在数据包的包头中增加第二指示信息。例如，当第二指示信息为1时，指示该数据包为与第一QoS流传输的数据包有关联关系的数据包，当第二指示信息为0时，指示该数据包为与第一QoS流传输的数据包无关联关系的数据包。
因此，当终端设备在进行具有数据突发特点的业务时，例如，XR业务，如果较为重 要的帧丢失，可能会影响该帧的显示，比如画面的较长时间的卡顿。通过上述方案，通过提升网络资源的利用效率的方法，使得业务的传输性能得以提升，降低因传输过程导致的帧的丢失的影响，改善画面卡顿的时间，提升用户体验。
理解的是，上述各个方法实施例中，由终端设备实现的方法和操作，也由可用于终端设备的部件(例如芯片或者电路)实现，由网络设备实现的方法和操作，也由可用于网络设备的部件(例如芯片或者电路)实现。
以上，结合图4至图10详细说明了本申请实施例提供的方法。以下，结合图11至图14详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容参见上文方法实施例，为了简洁，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。应理解，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，对应各个功能划分各个功能模块，也将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既采用硬件的形式实现，也采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图11是本申请实施例提供的通信装置的示意性框图。该通信装置1100包括收发单元1110和处理单元1120。收发单元1110实现相应的通信功能，处理单元1110用于进行数据处理。收发单元1110还称为通信接口或通信单元。
在一些实施例中，该通信装置1100还包括存储单元，该存储单元用于存储指令和/或数据，处理单元1120读取存储单元中的指令和/或数据，以使得通信装置实现前述方法实施例。
该通信装置1100用于执行上文方法实施例中终端设备所执行的动作，这时，该通信装置1100为终端设备或者可配置于终端设备的部件，收发单元1110用于执行上文方法实施例中终端设备侧的收发相关的操作，处理单元1120用于执行上文方法实施例中终端设备侧的处理相关的操作。
或者，该通信装置1100用于执行上文方法实施例中网络设备所执行的动作，这时，该通信装置1100为网络设备或者可配置于网络设备的部件，收发单元1110用于执行上文方法实施例中网络设备侧的收发相关的操作，处理单元1120用于执行上文方法实施例中网络设备侧的处理相关的操作。
作为一种设计，该通信装置1100用于执行上文图4所示实施例中终端设备所执行的动作，收发单元1110用于：S402、S404、S406、S407、S409、S410、S412、S414；处理单元1120用于：S401、S405、S408a、S411。
作为一示例，该通信装置1100用于执行上文图5所示实施例中终端设备所执行的动 作，收发单元1110用于：S502；处理单元1120用于：S501。
作为又一示例，该通信装置1100用于执行上文图6所示实施例中终端设备所执行的动作，收发单元1110用于：S601、S602、S606、S608、S610、S613；处理单元1120用于：S607a、S611a、S614a。
作为又一示例，该通信装置1100用于执行上文图7所示实施例中终端设备所执行的动作，收发单元1110用于：S701a、S702、S704；处理单元1120用于：S705a。
作为又一示例，该通信装置1100用于执行上文图9所示实施例中终端设备所执行的动作，收发单元1110用于：S901、S903、S909、S910；处理单元1120用于：S902a。
作为又一示例，该通信装置1100用于执行上文图10所示实施例中终端设备所执行的动作，收发单元1110用于：S1001、S1003、S1010、S1011；处理单元1120用于：S1002a。
该通信装置1100可实现对应于根据本申请实施例的方法400和方法500中的终端设备执行的步骤或者流程，该通信装置1100包括用于执行图4中的方法400至图10中方法1000中的终端设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法400至图10中方法1000的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，通信装置1100用于执行上文图4所示实施例中第一网络设备所执行的动作，收发单元1110用于：S402、S404、S406、S407、S409、S410、S412、S413；处理单元1120用于：S403。
作为一示例，通信装置1100用于执行上文图5所示实施例中第一网络设备所执行的动作，收发单元1110用于：S502；处理单元1120用于：S503。
该通信装置1100可实现对应于根据本申请实施例的方法400和方法500中的第一网络设备执行的步骤或者流程，该通信装置1100包括用于执行图4中的方法400和图5中方法500中的第一网络设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法400和图5中方法500的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，通信装置1100用于执行上文图4所示实施例中第二网络设备所执行的动作，收发单元1110用于：S404、S406、S407、S413、S414；处理单元1120用于：S408b。
该通信装置1100可实现对应于根据本申请实施例的方法400中的第二网络设备执行的步骤或者流程，该通信装置1100包括用于执行图4中的方法400中的第二网络设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存 储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，通信装置1100用于执行上文图4所示实施例中第三网络设备所执行的动作，收发单元1110用于：S404、S406、S407、S413；处理单元1120用于：S408c。
该通信装置1100可实现对应于根据本申请实施例的方法400中的第三网络设备执行的步骤或者流程，该通信装置1100包括用于执行图4中的方法400中的第三网络设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，通信装置1100用于执行上文图6所示实施例中SMF实体所执行的动作，收发单元1110用于：S601、S603、S604、S606、S608、S610、S612；处理单元1120用于：S605、S609。
作为一示例，通信装置1100用于执行上文图7所示实施例中SMF实体所执行的动作，收发单元1110用于：S702、S704；处理单元1120用于：S703。
作为又一示例，通信装置1100用于执行上文图9所示实施例中SMF实体所执行的动作，收发单元1110用于：S901、S904、S905、S907、S911；处理单元1120用于：S906。
作为又一示例，通信装置1100用于执行上文图10所示实施例中SMF实体所执行的动作，收发单元1110用于：S1001、S1004、S1005、S1008、S1012；处理单元1120用于：S1006、S1007。
该通信装置1100可实现对应于根据本申请实施例的方法600、方法700、方法900、方法1000中的SMF实体执行的步骤或者流程，该通信装置1100包括用于执行图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000中的SMF实体执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，通信装置1100用于执行上文图6所示实施例中UPF实体所执行的动作，收发单元1110用于：S606、S608、S610、S612；处理单元1120用于：S607c、S611c、S614c。
作为一示例，通信装置1100用于执行上文图7所示实施例中UPF实体所执行的动作， 收发单元1110用于：S702、S704；处理单元1120用于：S705c。
作为又一示例，通信装置1100用于执行上文图9所示实施例中UPF实体所执行的动作，收发单元1110用于：S911、S912。
作为又一示例，通信装置1100用于执行上文图10所示实施例中UPF实体所执行的动作，收发单元1110用于：S1012、S1013。
该通信装置1100可实现对应于根据本申请实施例的方法600、方法700、方法900、方法1000中的UPF实体执行的步骤或者流程，该通信装置1100包括用于执行图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000中的UPF实体执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
该通信装置1100可实现对应于根据本申请实施例的方法600、方法700、方法900、方法1000中的基站执行的步骤或者流程，该通信装置1100包括用于执行图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000中的基站执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图6中的方法600、图7中的方法700、图9中的方法900和图10中方法1000的相应流程。
上文实施例中的处理单元1120由至少一个处理器或处理器相关电路实现。收发单元1110由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元通过至少一个存储器实现。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
如图12所示，本申请实施例还提供一种通信装置1200。该通信装置1200包括处理器1210，处理器1210与存储器1220耦合，存储器1220用于存储计算机程序或指令和/或数据，处理器1210用于执行存储器1220存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。
在一些实施例中，该通信装置1200包括的处理器1210为一个或多个。
在一些实施例中，如图12所示，该通信装置1200还包括存储器1220。
在一些实施例中，该通信装置1200包括的存储器1220为一个或多个。
在一些实施例中，该存储器1220与该处理器1210集成在一起，或者分离设置。
在一些实施例中，如图12所示，该通信装置1200还包括收发器1230，收发器1230用于信号的接收和/或发送。例如，处理器1210用于控制收发器1230进行信号的接收和/或发送。
作为一种方案，该通信装置1200用于实现上文方法实施例中由终端设备执行的操作。
例如，处理器1210用于实现上文方法实施例中由终端设备执行的处理相关的操作， 收发器1230用于实现上文方法实施例中由终端设备执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由第一网络设备执行的操作。
例如，处理器1210用于实现上文方法实施例中由第一网络设备执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由第二网络设备执行的操作。
例如，处理器1210用于实现上文方法实施例中由第二网络设备执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由SMF实体执行的操作。
例如，处理器1210用于实现上文方法实施例中由SMF实体执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由UPF实体执行的操作。
例如，处理器1210用于实现上文方法实施例中由UPF实体执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由基站执行的操作。
例如，处理器1210用于实现上文方法实施例中由基站执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
本申请实施例还提供一种通信装置1300，该通信装置1300是终端设备也是芯片。该通信装置1300用于执行上述方法实施例中由终端设备所执行的操作。
当该通信装置1300为终端设备时，图13示出了一种简化的终端设备的结构示意图。如图13所示，终端设备包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对终端设备进行控制，执行软件程序，处理软件程序的数据。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘主要用于接收用户输入的数据以及对用户输出数据。需要说明的是，有些种类的终端设备不具有输入输出装置。
当需要发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图13中仅示出了一个存储器和处理器，在实际的终端设备产品中，存在一个或多个处理器和一个或多个存储器。存储器也称为存储介质或者存储设备。存储器是独立于处理器设置，也是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，将具有收发功能的天线和射频电路视为终端设备的收发单元，将具有处理功能的处理器视为终端设备的处理单元。
如图13所示，终端设备包括收发单元1310和处理单元1320。收发单元1310也称为 收发器、收发机、收发装置。处理单元1320也称为处理器，处理单板，处理模块、处理装置。
在一些实施例中，将收发单元1310中用于实现接收功能的器件视为接收单元，将收发单元1310中用于实现发送功能的器件视为发送单元，即收发单元1310包括接收单元和发送单元。收发单元有时也称为收发机、收发器、或收发电路。接收单元有时也称为接收机、接收器、或接收电路。发送单元有时也称为发射机、发射器或者发射电路。
例如，处理单元1320用于执行图4至图10中终端设备侧的处理动作。例如，处理单元1320用于执行图4至图10中的处理步骤；收发单元1310用于执行图4至图10中的收发操作。
应理解，图13仅为示例而非限定，上述包括收发单元和处理单元的终端设备不依赖于图13所示的结构。
当该通信装置1300为芯片时，该芯片包括收发单元和处理单元。其中，收发单元是输入输出电路或通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种通信装置1400，该通信装置1400是网络设备也是芯片。该通信装置1400用于执行上述方法实施例中由第一网络设备，或第二网络设备，或第三网络设备，或SMF实体，或UPF实体，或基站所执行的操作。
当该通信装置1400为网络设备时，图14示出了一种简化的网络设备1400的结构示意图。包括1410部分以及1420部分。1410部分主要用于射频信号的收发以及射频信号与基带信号的转换；1420部分主要用于处理、控制。1410部分通常称为收发单元、收发机、收发电路、或者收发器。1420部分通常是网络设备的控制中心，通常称为处理单元，用于控制网络设备执行上述方法实施例中网络设备侧的处理操作。
1410部分的收发单元，也称为收发机或收发器，其包括天线和射频电路，其中射频电路主要用于进行射频处理。在一些实施例中，将1410部分中用于实现接收功能的器件视为接收单元，将用于实现发送功能的器件视为发送单元，即1410部分包括接收单元和发送单元。接收单元也称为接收机、接收器、或接收电路，发送单元称为发射机、发射器或者发射电路。
1420部分包括一个或多个单板，每个单板包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对基站的控制。若存在多个单板，各个单板之间互联以增强处理能力。作为一种实施方式，也是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
例如，在一种实现方式中，1410部分的收发单元用于执行图4、图5所示实施例中由第一网络设备执行的收发相关的步骤；1420部分用于执行图4、图5所示实施例中由第一网络设备执行的处理相关的步骤。
例如，在又一种实现方式中，1410部分的收发单元用于执行图4所示实施例中由第二网络设备执行的收发相关的步骤；1420部分用于执行图4所示实施例中由第二网络设备执行的处理相关的步骤。
例如，在又一种实现方式中，1410部分的收发单元用于执行图4所示实施例中由第三网络设备执行的收发相关的步骤；1420部分用于执行图4所示实施例中由第三网络设 备执行的处理相关的步骤。
例如，在又一种实现方式中，1410部分的收发单元用于执行图6、图7、图9、图10所示实施例中由SMF实体执行的收发相关的步骤；1420部分用于执行图6、图7、图9、图10所示实施例中由SMF实体执行的处理相关的步骤。
例如，在又一种实现方式中，1410部分的收发单元用于执行图6、图7、图9、图10所示实施例中由UPF实体执行的收发相关的步骤；1420部分用于执行图6、图7、图9、图10所示实施例中由UPF实体执行的处理相关的步骤。
例如，在又一种实现方式中，1410部分的收发单元用于执行图6、图7、图9、图10所示实施例中由基站执行的收发相关的步骤；1420部分用于执行图6、图7、图9、图10所示实施例中由基站执行的处理相关的步骤。
应理解，图14仅为示例而非限定，上述包括收发单元和处理单元的网络设备不依赖于图14所示的结构。
当该通信装置1400为芯片时，该芯片包括收发单元和处理单元。其中，收发单元是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由终端设备执行的方法，或由网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机实现上述方法实施例中由终端设备执行的方法，或由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由终端设备执行的方法，或由网络设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备与终端设备。
所属领域的技术人员清楚地了解到，为描述方便和简洁，上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请实施例中，终端设备或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。其中，硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)。操作系统层的操作系统是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统。应用层包含浏览器、通讯录、文字处理软件、即时通信软件。
本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构进行特别限定，只要通过运行记录有本申请实施例提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体是终端设备或网络设备，或者，是终端设备或网络设备中调用程序并执行程序的功能模块。
本申请的各个方面或特征实现成方法、装置或使用标准编程和/或工程技术的制品。本文中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。
其中，计算机可读存储介质是计算机存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心数据存储设备。可用介质(或者说计算机可读介质)例如包括但不限于：磁性介质或磁存储器件(例如，软盘、硬盘(如移动硬盘)、磁带)、光介质(例 如，光盘、压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD))、智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器)、或者半导体介质(例如固态硬盘(solid state disk，SSD)、U盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)，以及各种存储程序代码的介质。
本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”包括但不限于：无线信道和存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的处理器是中央处理单元(central processing unit，CPU)，还是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。通用处理器是微处理器或者该处理器也是任何常规的处理器。
还应理解，本申请实施例中提及的存储器是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器是随机存取存储器(random access memory，RAM)。例如，RAM用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，上述单元的划分，仅仅为一种逻辑功能划分，实际实现时有另外的划分方式，例如多个单元或组件结合或者集成到另一个系统，或一些特征忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接是通过一些接口，装置或单元的间接耦合或通信连接，是电性，机械或其它的形式。
上述作为分离部件说明的单元是或者也不是物理上分开的，作为单元显示的部件是或者也不是物理单元，即位于一个地方，或者也分布到多个网络单元上。根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元集成在一个单元中，也是各个单元单独物理存在，也两个或两个以上单元集成在一个单元中。
在上述实施例中，全部或部分地通过软件、硬件、固件或者其任意组合来实现。
当使用软件实现时，全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，计算机是个人计算机，服务器，或者网络设备。计算机指令存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波)方式向另一个网站站点、计算机、服务器或数据中心进行传输。关于计算机可读存储介质，参考上文描述。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求和说明书的保护范围为准。
实施例1.一种会话管理的方法，其特征在于，包括：
终端设备确定第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
终端设备向第一网络设备发送第一消息，所述第一消息包括所述第一参数。
实施例2.根据实施例1所述的方法，其特征在于，
所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
实施例3.根据实施例1或2所述的方法，其特征在于，
所述第一参数为所述终端设备的业务的第一周期性信息，或
所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
实施例4.根据实施例3所述的方法，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
实施例5.根据实施例1至4中任一项所述的方法，其特征在于，所述方法还包括：
所述终端设备接收所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例6.根据实施例5所述的方法，其特征在于，所述方法还包括：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备释放所述第一QoS流。
实施例7.根据实施例5所述的方法，其特征在于，所述方法还包括：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
所述终端设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例8.根据实施例6或7所述的方法，其特征在于，所述终端设备释放所述第一QoS流，包括：
所述终端设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
所述终端设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例9.根据实施例1至8中任一项所述的方法，其特征在于，所述方法还包括：
所述终端设备向所述第一网络设备发送第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例10.根据实施例9所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例11.根据实施例9所述的方法，其特征在于，所述方法还包括：
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例12.根据实施例10或11所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例13.根据实施例1至4中任一项所述的方法，其特征在于，所述方法还包括：
所述终端设备接收所述第一网络设备的包括所述第一会话的第一不活动时长信息的消息。
实施例14.根据实施例13所述的方法，其特征在于，所述方法还包括：
在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，所述终端设备去激活所述第一会话的用户面连接。
实施例15.根据实施例13所述的方法，其特征在于，所述方法还包括：
在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，所述终端设备向所述第一网络设备发送指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
所述终端设备接收来自第二网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例16.一种会话管理的方法，其特征在于，包括：
第一网络设备接收来自终端设备的第一消息，所述第一消息包含第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
所述第一网络设备根据所述第一参数，确定所述第一QoS流的第一不活动时长，或，确定所述第一会话的第一不活动时长。
实施例17.根据实施例16所述的方法，其特征在于，
所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
实施例18.根据实施例16或17所述的方法，其特征在于，
所述第一参数为所述终端设备的业务的第一周期性信息，或
所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
实施例19.根据实施例18所述的方法，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
实施例20.根据实施例16至19中任一项所述的方法，其特征在于，所述方法还包括：
所述第一网络设备向所述终端设备和/或第二网络设备和/或第三网络设备发送包括所述第一QoS流的第一不活动时长信息的消息。
实施例21.根据实施例20所述的方法，其特征在于，所述方法还包括：
所述第一网络设备接收来自所述终端设备和/或所述第二网络设备和/或所述第三网络设备的：指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
所述第一网络设备向所述终端设备和/或所述第二网络设备和/或所述第三网络设备发送用于指示释放所述第一QoS流的消息。
实施例22.根据实施例16至21中任一项所述的方法，其特征在于，所述方法还包括：
所述第一网络设备接收来自所述终端设备的第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流 比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例23.根据实施例22所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例24.根据实施例22所述的方法，其特征在于，
所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例25.根据实施例23或24所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例26.根据实施例16至19中任一项所述的方法，其特征在于，所述方法还包括：
所述第一网络设备向所述终端设备发送包括所述第一会话的第一不活动时长信息的消息。
实施例27.根据实施例26所述的方法，其特征在于，所述方法还包括：
所述第一网络设备接收来自所述终端设备的指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
所述第一网络设备向所述第二网络设备和/或所述第三网络设备发送指示去激活第一会话的用户面连接的消息。
实施例28.根据实施例16至27中任一项所述的方法，其特征在于，所述方法还包括：
第二网络设备接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例29.根据实施例28所述的方法，其特征在于，所述方法还包括：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述第二网络设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或， 请求释放所述第一QoS流的消息；
所述第二网络设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例30.根据实施例29所述的方法，其特征在于，所述第二网络设备释放所述第一QoS流，包括：
所述第二网络设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
所述第二网络设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例31.根据实施例16至30所述的方法，其特征在于，所述方法还包括：
所述第二网络设备接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息；
所述第二网络设备向所述终端设备发送指示去激活所述第一会话的用户面连接的消息。
实施例32.根据实施例16至31中任一项所述的方法，其特征在于，所述方法还包括：
第三网络设备接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例33.根据实施例32所述的方法，其特征在于，所述方法还包括：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述第三网络设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
所述第三网络设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例34.根据实施例33所述的方法，其特征在于，所述第三网络设备释放所述第一QoS流，包括：
所述第三网络设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
所述第三网络设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例35.根据实施例16至34所述的方法，其特征在于，所述方法还包括：
所述第三网络设备接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例36.一种会话管理的方法，其特征在于，包括：
终端设备向第一网络设备发送第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例37.根据实施例36所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例38.根据实施例36所述的方法，其特征在于，所述方法还包括：
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例39.根据实施例37或38所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例40.一种会话管理的方法，其特征在于，包括：
第一网络设备接收来自终端设备的第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例41.根据实施例40所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例42.根据实施例40所述的方法，其特征在于，所述方法还包括：
所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例43.根据实施例41或42所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例44.一种会话管理的方法，其特征在于，所述方法包括：
第三网络设备接收来自第一网络设备的包括第一QoS流的第一不活动时长信息的消息。
实施例45.根据实施例44所述的方法，其特征在于，所述方法还包括：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述第三网络设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
所述第三网络设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例46.根据实施例45所述的方法，其特征在于，所述第三网络设备释放所述第一QoS流，包括：
所述第三网络设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
所述第三网络设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例47.根据实施例44至46中任一项所述的方法，其特征在于，所述方法还包括：
所述第三网络设备接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例48.一种会话管理的装置，其特征在于，包括：
处理单元，用于确定第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
收发单元，用于向第一网络设备发送第一消息，所述第一消息包括所述第一参数。
实施例49.根据实施例48所述的装置，其特征在于，
所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
实施例50.根据实施例48或49所述的装置，其特征在于，
所述第一参数为所述终端设备的业务的第一周期性信息，或
所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
实施例51.根据实施例50所述的装置，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
实施例52.根据实施例48至51中任一项所述的装置，其特征在于，所述收发单元还用于：
接收所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例53.根据实施例52所述的装置，其特征在于，所述处理单元还用于：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备释放所述第一QoS流。
实施例54.根据实施例52所述的装置，其特征在于，所述收发单元还用于：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
所述终端设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例55.根据实施例53或54所述的装置，其特征在于，所述处理单元还用于：
删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例56.根据实施例48至55中任一项所述的装置，其特征在于，所述收发单元还用于：
向所述第一网络设备发送第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例57.根据实施例56所述的装置，其特征在于，所述第二参数或所述第三参数 为所述终端设备的业务的第二周期性信息。
实施例58.根据实施例56所述的装置，其特征在于，所述处理单元还用于：
根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例59.根据实施例57或58所述的装置，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例60.根据实施例48至51中任一项所述的装置，其特征在于，所述收发单元还用于：
接收所述第一网络设备的包括所述第一会话的第一不活动时长信息的消息。
实施例61.根据实施例60所述的装置，其特征在于，所述处理单元还用于：
在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，去激活所述第一会话的用户面连接。
实施例62.根据实施例60所述的装置，其特征在于，所述收发单元还用于：
在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，向所述第一网络设备发送指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
接收来自第二网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例63.一种会话管理的装置，其特征在于，包括：
第一网络设备的收发单元，用于接收来自终端设备的第一消息，所述第一消息包含第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
所述第一网络设备的处理单元，用于根据所述第一参数，确定所述第一QoS流的第一不活动时长，或，确定所述第一会话的第一不活动时长。
实施例64.根据实施例63所述的装置，其特征在于，
所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
实施例65.根据实施例63或64所述的装置，其特征在于，
所述第一参数为所述终端设备的业务的第一周期性信息，或
所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
实施例66.根据实施例65所述的装置，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
实施例67.根据实施例63至66中任一项所述的装置，其特征在于，所述第一网络设备的收发单元还用于：
向所述终端设备和/或第二网络设备和/或第三网络设备发送包括所述第一QoS流的第一不活动时长信息的消息。
实施例68.根据实施例67所述的装置，其特征在于，所述第一网络设备的收发单元还用于：
接收来自所述终端设备和/或所述第二网络设备和/或所述第三网络设备的：指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
向所述终端设备和/或所述第二网络设备和/或所述第三网络设备发送用于指示释放所述第一QoS流的消息。
实施例69.根据实施例63至67中任一项所述的装置，其特征在于，所述第一网络设备的收发单元还用于：
接收来自所述终端设备的第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
实施例70.根据实施例69所述的装置，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例71.根据实施例69所述的装置，其特征在于，
所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例72.根据实施例70或71所述的装置，其特征在于，所述终端设备的业务的 第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例73.根据实施例63至66中任一项所述的装置，其特征在于，所述第一网络设备的收发单元还用于：
向所述终端设备发送包括所述第一会话的第一不活动时长信息的消息。
实施例74.根据实施例73所述的装置，其特征在于，所述第一网络设备的收发单元还用于：
接收来自所述终端设备的指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
向所述第二网络设备和/或所述第三网络设备发送指示去激活所述第一会话的用户面连接的消息。
实施例75.根据实施例63至74中任一项所述的装置，其特征在于，所述装置还包括：
第二网络设备的收发单元，用于接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例76.根据实施例75所述的装置，其特征在于，所述第二网络设备的收发单元，还用于：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例77.根据实施例76所述的装置，其特征在于，所述装置还包括：
所述第二网络设备的处理单元，用于删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例78.根据实施例63至77所述的装置，其特征在于，所述第二网络设备的收发单元，还用于：
接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息；
向所述终端设备发送指示去激活所述第一会话的用户面连接的消息。
实施例79.根据实施例63至77中任一项所述的装置，其特征在于，所述装置还包括：
第三网络设备的收发单元，用于接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
实施例80.根据实施例79所述的装置，其特征在于，所述第三网络设备的收发单元，还用于：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一 QoS流的消息；
接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例81.根据实施例80所述的装置，其特征在于，所述装置还包括：
所述第三网络设备的处理单元，用于删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例82.根据实施例63至81所述的装置，其特征在于，所述第三网络设备的收发单元，还用于：
接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例83.一种会话管理的装置，其特征在于，包括：
处理单元，用于生成第二消息，所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项；
收发单元，用于向第一网络设备发送所述第二消息。
实施例84.根据实施例83所述的装置，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例85.根据实施例83所述的装置，其特征在于，所述装置还包括：
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例86.根据实施例84或85所述的装置，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例87.一种会话管理的装置，其特征在于，包括：
收发单元，用于接收来自终端设备的第二消息，
所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项；
处理单元，用于根据所述第二消息，确定第一QoS流的第一QoS参数，或确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数。
实施例88.根据实施例87所述的装置，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
实施例89.根据实施例87所述的装置，其特征在于，所述装置还包括：
所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
实施例90.根据实施例88或89所述的装置，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
实施例91.一种会话管理的装置，其特征在于，包括：
收发单元，用于接收来自第一网络设备的包括第一QoS流的第一不活动时长信息的消息；
处理单元，用于确定所述第一QoS流的第一不活动时长。
实施例92.根据实施例91所述的方法，其特征在于，所述收发单元还用于：
在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
实施例93.根据实施例92所述的方法，其特征在于，所述装置还包括：
处理单元，用于删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS 流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
实施例94.根据实施例91至93中任一项所述的方法，其特征在于，所述收发单元还用于：
接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接的消息。
实施例95.一种通信装置，其特征在于，包括：
存储单元，用于存储计算机指令；
处理单元，用于执行所述存储单元中存储的计算机指令，使得所述通信装置执行如实施例1至15或如实施例16至35或如实施例36至39或如实施例40至43或如实施例44至47中任一项所述的方法。
实施例96.一种通信装置，其特征在于，包括：
存储器，用于存储计算机指令；
处理器，用于执行所述存储器中存储的计算机指令，使得所述通信装置执行如实施例1至15或如实施例16至35或如实施例36至39或如实施例40至43或如实施例44至47中任一项所述的方法。
实施例97.一种计算机可读存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被通信装置执行时，使得所述通信装置执行如实施例1至15或如实施例16至35或如实施例36至39或如实施例40至43或如实施例44至47中任一项所述的方法。
实施例98.一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如实施例1至15或如实施例16至35或如实施例36至39或如实施例40至43或如实施例44至47中任一项所述的方法。
实施例99.一种芯片，其特征在于，所述芯片包括处理器与数据接口，所述处理器通过所述数据接口读取存储器上存储的指令，以执行如实施例1至15或如实施例16至35或如实施例36至39或如实施例40至43或如实施例44至47中任一项所述的方法。
实施例100.一种通信系统，其特征在于，包括如实施例48至62与实施例63至82，或如实施例83至86与如实施例87至90中任一项所述的装置。

Claims (48)

  1. 一种会话管理的方法，其特征在于，包括：
    终端设备确定第一参数，所述第一参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
    终端设备向第一网络设备发送第一消息，所述第一消息包括所述第一参数。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
    所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述第一参数为所述终端设备的业务的第一周期性信息，或
    所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备释放所述第一QoS流。
  7. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述终端设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
    所述终端设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述终端设备释放所述第一QoS流，包括：
    所述终端设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
    所述终端设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述第一网络设备发送第二消息，
    所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
    所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
  10. 根据权利要求9所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
    所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
  12. 根据权利要求10或11所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
  13. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述第一网络设备的包括所述第一会话的第一不活动时长信息的消息。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，所述终端设备去激活所述第一会话的用户面连接。
  15. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    在所述第一会话的无数据传输的时长达到所述第一会话的第一不活动时长的情况下，所述终端设备向所述第一网络设备发送指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
    所述终端设备接收来自第二网络设备的指示去激活所述第一会话的用户面连接的消息。
  16. 一种会话管理的方法，其特征在于，包括：
    第一网络设备接收来自终端设备的第一消息，所述第一消息包含第一参数，所述第一 参数用于第一网络设备确定所述终端设备的第一服务质量QoS流的第一不活动时长，或，用于所述第一网络设备确定所述终端设备的第一会话的第一不活动时长；
    所述第一网络设备根据所述第一参数，确定所述第一QoS流的第一不活动时长，或，确定所述第一会话的第一不活动时长。
  17. 根据权利要求16所述的方法，其特征在于，
    所述第一QoS流的第一不活动时长用于确定释放所述第一Qos流，或
    所述第一会话的第一不活动时长用于确定释放所述第一会话的用户面连接。
  18. 根据权利要求16或17所述的方法，其特征在于，
    所述第一参数为所述终端设备的业务的第一周期性信息，或
    所述第一参数为根据所述终端设备的业务的第一周期性信息确定的所述第一QoS流的第二不活动时长或所述第一会话的第二不活动时长。
  19. 根据权利要求18所述的方法，其特征在于，所述终端设备的业务的第一周期性信息包括所述业务的第一帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第一比例信息中的至少一项。
  20. 根据权利要求16至19中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述终端设备和/或第二网络设备和/或第三网络设备发送包括所述第一QoS流的第一不活动时长信息的消息。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述终端设备和/或所述第二网络设备和/或所述第三网络设备的：指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
    所述第一网络设备向所述终端设备和/或所述第二网络设备和/或所述第三网络设备发送用于指示释放所述第一QoS流的消息。
  22. 根据权利要求16至21中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述终端设备的第二消息，
    所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
    所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
  23. 根据权利要求22所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
  24. 根据权利要求22所述的方法，其特征在于，
    所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至 少一项；或
    所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
  25. 根据权利要求23或24所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
  26. 根据权利要求16至19中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述终端设备发送包括所述第一会话的第一不活动时长信息的消息。
  27. 根据权利要求26所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述终端设备的指示所述第一会话不活动，和/或，请求去激活所述第一会话的用户面连接的消息；
    所述第一网络设备向所述第二网络设备和/或所述第三网络设备发送指示去激活所述第一会话的用户面连接的消息。
  28. 根据权利要求16至27中任一项所述的方法，其特征在于，所述方法还包括：
    第二网络设备接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述第二网络设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
    所述第二网络设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
  30. 根据权利要求29所述的方法，其特征在于，所述第二网络设备释放所述第一QoS流，包括：
    所述第二网络设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
    所述第二网络设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
  31. 根据权利要求16至30中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接；
    所述第二网络设备向所述终端设备发送指示去激活所述第一会话的用户面连接的消 息。
  32. 根据权利要求16至31中任一项所述的方法，其特征在于，所述方法还包括：
    第三网络设备接收来自所述第一网络设备的包括所述第一QoS流的第一不活动时长信息的消息。
  33. 根据权利要求32所述的方法，其特征在于，所述方法还包括：
    在所述第一QoS流的无数据传输的时长达到所述第一QoS流的第一不活动时长的情况下，所述第三网络设备向所述第一网络设备发送指示所述第一QoS流不活动，和/或，请求释放所述第一QoS流的消息；
    所述第三网络设备接收来自所述第一网络设备的用于指示释放所述第一QoS流的消息。
  34. 根据权利要求33所述的方法，其特征在于，所述第三网络设备释放所述第一QoS流，包括：
    所述第三网络设备删除所述第一QoS流与第二QoS流的关联关系，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据，所述第一QoS流与所述第二QoS流存在关联关系；或，
    所述第三网络设备释放与所述第一QoS流关联的第二QoS流，其中，所述第一QoS流传输所述业务中重要性程度高的数据，所述第二QoS流传输所述业务中重要性程度低的数据。
  35. 根据权利要求16至34中任一项所述的方法，其特征在于，所述方法还包括：
    所述第三网络设备接收来自所述第一网络设备的指示去激活所述第一会话的用户面连接。
  36. 一种会话管理的方法，其特征在于，包括：
    终端设备向第一网络设备发送第二消息，
    所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
    所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
  37. 根据权利要求36所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
  38. 根据权利要求36所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述第二参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
    所述终端设备根据所述终端设备的业务的第二周期性信息确定所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数为所述第三参数，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
  39. 根据权利要求37或38所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
  40. 一种会话管理的方法，其特征在于，包括：
    第一网络设备接收来自终端设备的第二消息，
    所述第二消息包含第二参数，所述第二参数用于所述第一网络设备确定第一QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一保障流比特速率GFBR、第一最大流比特速率MFBR，或者第一最大数据突发量MDBV中的至少一项；或
    所述第二消息包含第三参数，所述第三参数用于所述第一网络设备确定所述第一QoS流的第一QoS参数和所述第二QoS流的第一QoS参数，所述第一QoS流的第一QoS参数包括所述第一QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项，所述第二QoS流的第一QoS参数包括所述第二QoS流的第一GFBR、第一MFBR，或者第一MDBV中的至少一项。
  41. 根据权利要求40所述的方法，其特征在于，所述第二参数或所述第三参数为所述终端设备的业务的第二周期性信息。
  42. 根据权利要求40所述的方法，其特征在于，所述方法还包括：
    所述第二参数为所述第一QoS流的第二QoS参数，所述第一QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项；或
    所述第三参数为所述第一QoS流的第二QoS参数的信息与所述第二QoS流的第二QoS参数，所述第一QoS流的第二QoS参数与所述第二QoS流的第二QoS参数为所述终端设备根据所述终端设备的业务的第二周期性信息确定的，所述第一QoS流的第二QoS参数包括所述第一QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项，所述第二QoS流的第二QoS参数包括所述第二QoS流的第二GFBR、第二MFBR，或者第二MDBV中的至少一项。
  43. 根据权利要求41或42所述的方法，其特征在于，所述终端设备的业务的第二周期性信息包括所述业务的第二帧率的信息，或所述业务中重要性程度高的帧与重要性程度低的帧的第二比例信息中的至少一项。
  44. 一种通信装置，其特征在于，包括：
    存储单元，用于存储计算机指令；
    处理单元，用于执行所述存储单元中存储的计算机指令，使得所述通信装置执行如权 利要求1至15或如权利要求16至35或如权利要求36至39或如权利要求40至43中任一项所述的方法。
  45. 一种通信装置，其特征在于，包括：
    存储器，用于存储计算机指令；
    处理器，用于执行所述存储器中存储的计算机指令，使得所述通信装置执行如权利要求1至15或如权利要求16至35或如权利要求36至39或如权利要求40至43中任一项所述的方法。
  46. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被通信装置执行时，使得所述通信装置执行如权利要求1至15或如权利要求16至35或如权利要求36至39或如权利要求40至43中任一项所述的方法。
  47. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至15或如权利要求16至35或如权利要求36至39或如权利要求40至43中任一项所述的方法。
  48. 一种芯片，其特征在于，所述芯片包括处理器与数据接口，所述处理器通过所述数据接口读取存储器上存储的指令，以执行如权利要求1至15或如权利要求16至35或如权利要求36至39或如权利要求40至43中任一项所述的方法。
PCT/CN2022/086276 2021-06-23 2022-04-12 会话管理的方法及装置 WO2022267632A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22827135.9A EP4351209A4 (en) 2021-06-23 2022-04-12 SESSION MANAGEMENT PROCEDURE AND DEVICE
US18/393,841 US20240129786A1 (en) 2021-06-23 2023-12-22 Session management method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110697476.5 2021-06-23
CN202110697476 2021-06-23
CN202110874038.1 2021-07-30
CN202110874038.1A CN115515192A (zh) 2021-06-23 2021-07-30 会话管理的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/393,841 Continuation US20240129786A1 (en) 2021-06-23 2023-12-22 Session management method and apparatus

Publications (1)

Publication Number Publication Date
WO2022267632A1 true WO2022267632A1 (zh) 2022-12-29

Family

ID=84499745

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/086276 WO2022267632A1 (zh) 2021-06-23 2022-04-12 会话管理的方法及装置

Country Status (4)

Country Link
US (1) US20240129786A1 (zh)
EP (1) EP4351209A4 (zh)
CN (1) CN115515192A (zh)
WO (1) WO2022267632A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246856A (zh) * 2017-05-16 2019-01-18 中国移动通信有限公司研究院 无线资源释放方法、定时器配置方法、设备及存储介质
CN109923937A (zh) * 2016-10-11 2019-06-21 日本电气株式会社 用于会话管理参数维护的方法、会话管理功能节点、用户平面功能节点和用户设备以及其中的计算机可读记录介质
CN112567714A (zh) * 2018-08-14 2021-03-26 华为技术有限公司 通信系统中的时间感知服务质量

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018172548A1 (en) * 2017-03-24 2018-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Qos flows inactivity counters
CN112437122B (zh) * 2020-11-08 2023-05-05 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109923937A (zh) * 2016-10-11 2019-06-21 日本电气株式会社 用于会话管理参数维护的方法、会话管理功能节点、用户平面功能节点和用户设备以及其中的计算机可读记录介质
CN109246856A (zh) * 2017-05-16 2019-01-18 中国移动通信有限公司研究院 无线资源释放方法、定时器配置方法、设备及存储介质
CN112567714A (zh) * 2018-08-14 2021-03-26 华为技术有限公司 通信系统中的时间感知服务质量

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4351209A4

Also Published As

Publication number Publication date
CN115515192A (zh) 2022-12-23
US20240129786A1 (en) 2024-04-18
EP4351209A1 (en) 2024-04-10
EP4351209A4 (en) 2024-09-04

Similar Documents

Publication Publication Date Title
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
WO2020224472A1 (zh) 分配、获取ip地址的方法及设备
WO2021212439A1 (zh) 一种通信方法及装置
WO2022110214A1 (zh) 通信方法及装置
WO2021203814A1 (zh) 处理时间同步报文的方法和装置
US20230035694A1 (en) Service guarantee method and apparatus
WO2019206322A1 (zh) 能力开放方法、相关装置及系统
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2021109143A1 (zh) 上行数据传输的控制方法和装置
WO2020211778A1 (zh) 小区切换方法以及装置
WO2022206850A1 (zh) 信息传递方法及装置
WO2022047803A1 (zh) 通信方法及装置
US20230079012A1 (en) Communication method and communication apparatus
WO2020142884A1 (zh) 切换传输路径的方法及装置
WO2022267632A1 (zh) 会话管理的方法及装置
WO2021203983A1 (zh) 处理时间同步报文的方法和装置
WO2023185598A1 (zh) 通信方法及装置
WO2023207958A1 (zh) 策略传输的方法、通信装置和系统
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
EP4344329A1 (en) Communication method and apparatus
JP7495275B2 (ja) セルラ通信システム、無線端末、及び基地局
WO2024027320A1 (zh) 无线通信的方法、装置和系统
WO2023169230A1 (zh) 业务速率调整方法及通信装置
WO2023011279A1 (zh) 一种周期业务的传输方法及通信装置
US20240214455A1 (en) Communication method and apparatus

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022827135

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022827135

Country of ref document: EP

Effective date: 20240104

NENP Non-entry into the national phase

Ref country code: DE