CN109246173B

CN109246173B - Session operation control method and device

Info

Publication number: CN109246173B
Application number: CN201710662303.3A
Authority: CN
Inventors: 柯小婉; 王弘; 许丽香
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2017-06-16
Filing date: 2017-08-04
Publication date: 2023-02-17
Anticipated expiration: 2037-08-04
Also published as: CN109246173A

Abstract

The invention provides a method and a device for controlling conversation operation, wherein the method for controlling the conversation operation comprises the following steps: the first node learns first session operation information about UE; wherein the first session operation information on the UE comprises at least one of: first session operation request information and first session operation result information; and determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information on the UE. The method provided by the invention can ensure that the core network, the wireless access network and the UE are consistent in the operation of establishing, modifying and releasing the session/QoS flow related to the UE by controlling the session/QoS flow operation of the UE, thereby not only reducing the signaling overhead and greatly improving the data transmission efficiency, but also greatly reducing the time delay of the UE accessing the network and ensuring the operation time delay of the session/QoS flow.

Description

Session operation control method and device

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for controlling a session operation.

Background

Modern mobile communication is increasingly tending to provide users with high-rate transmission multimedia services, and a system architecture diagram of System Architecture Evolution (SAE) is shown in fig. 1, wherein a User Equipment (UE) 101 is a terminal equipment supporting a network protocol; the evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network including base stations (eNodeB/NodeB) that provide an access radio network interface for UEs; mobility Management Entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE; serving Gateway (SGW) 104 mainly provides the function of user plane, MME 103 and SGW 104 may be in the same physical entity; a packet data network gateway (PGW) 105 is responsible for functions such as charging, lawful interception, etc., and may also be in the same physical entity as the SGW 104; a Policy and Charging Rules Function (PCRF) 106 provides quality of service (QoS) policy and charging criteria; the general packet radio service support node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides routing for the transmission of data; the Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, packet data context of the user equipment, etc., and UTRAN in fig. 1 represents an evolved universal terrestrial radio access network.

The initial system architecture diagram of the Next generation network (5G) is shown in fig. 2, which includes a Next generation user equipment UE 210, a Next generation access network or Next generation radio access network (Next Gen (R) AN) 220, a Next generation Core network (Next Gen Core) 230 and a data network 240; the control plane interface between the next generation access network or the next generation radio access network and the next generation core network is NG2 and the user plane interface is NG3. The names of these interfaces are only temporary names, and finally, based on the names of 3GPP (3 rd Generation Partnership Project), the next Generation core network further includes a user plane functional entity and a control plane functional entity.

In the foreseeable future, more and more electrical equipment is intelligentized, and articles around the life are interconnected and have the function of accessing to the network. On the one hand, some UEs in the future tend to have the following features: static or low mobility, low cost, transceived data also tends to be small data volume, non-continuous; for these UEs, the signaling overhead caused by establishing and releasing connections is much larger than the amount of data to be transceived. On the other hand, to support more and more real-time applications such as virtual reality, the access delay of future mobile communication networks is greatly reduced. In order to save signaling overhead, improve data transmission efficiency, and reduce the delay of UE accessing to the network, many problems of the existing network still need to be solved.

Disclosure of Invention

The method and the device aim to solve the problem that in the prior art, when user equipment accesses a network, signaling overhead is too large and operation time delay is large, so that data transmission efficiency is extremely low.

The embodiment of the invention provides a control method of session operation, which comprises the following steps:

the first node acquires first session operation information about UE; wherein the first session operation information on the UE comprises at least one of: first session operation request information and first session operation result information; and

and determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE.

The embodiment of the invention also provides a control method of session operation, which comprises the following steps:

the second node judges whether a preset condition is met or not;

when the preset condition is determined to be met, the second node determines second session operation information about the User Equipment (UE); wherein the second session operation information on the UE comprises at least one of: second session operation request information and second session operation result information; and

and transmitting the determined second session operation information about the UE.

An embodiment of the present invention further provides a device for controlling session operations, including:

an obtaining module, configured to obtain, by a first node, session operation information about a first UE; wherein the first UE-related session operation information includes at least one of: first session operation request information and first session operation result information; and

and the operation module is used for determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE.

the judging module is used for judging whether the second node meets the preset conditions or not;

a determining module, configured to, when it is determined that a preset condition is satisfied, determine, by the second node, second session operation information about the user equipment UE; wherein the second UE session operation information comprises at least one of: second session operation request information and second session operation result information; and

a sending module, configured to send the determined second session operation information about the UE.

When the core network performs a session operation for the UE, the core network needs to operate the UE and also needs the radio access network to allocate radio resources. The session operation request and the result between the UE and the core network are transparently passed through the radio access network. For some session operations, the radio access network is not aware of the results of the operation of the UE, nor is the UE aware of the results of the operation of the radio access network. If the UE accepts the session operation failed by the radio access network or the radio access network accepts the session operation failed by the UE, a problem of inconsistent session operation may occur. In addition, the access stratum operation and the non-access stratum operation of the UE are independent respectively. When the operation request of the access stratum fails, it is worthless to accept the operation request of the non-access stratum. The first embodiment of the present invention can solve the above problem, and the UE can determine whether to accept the session operation request from the core network according to the session operation request from the core network and the operation result of the session operation request from the radio access network to the core network; or the radio access network can determine the session operation request which needs to be sent to the UE finally according to the session operation request of the core network and the session operation result of the radio access network; or the wireless access network node determines the session operation result which needs to be finally returned to the core network according to the session operation result of the UE and the session operation result of the wireless access network node; or the core network may generate the session operation request sent to the UE according to the session operation result returned by the radio access network, and so on. Through the control on the conversation/QoS flow operation of the UE, the core network, the wireless access network and the UE can be ensured to be consistent in the establishment, modification and release operations of the conversation/QoS flow related to the UE, the core network is prevented from generating signaling repeatedly to maintain the consistency, the signaling overhead is reduced, the data transmission efficiency is greatly improved, the time delay of the UE accessing the network is greatly reduced, and the operation time delay of the conversation/QoS flow is ensured.

Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Drawings

The foregoing and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

FIG. 1 is a diagram illustrating a System Architecture Evolution (SAE) in the prior art;

FIG. 2 is a diagram illustrating an initial system architecture of a next generation network (5G) in the prior art;

fig. 3 is a flowchart of a method for controlling a session operation according to a first embodiment of the present invention;

fig. 4 is a flowchart of a method for controlling a session operation according to a second embodiment of the present invention;

fig. 5 is a schematic diagram of an operation process of a control method of session operation in a first application scenario according to the present invention;

fig. 6 is a schematic diagram of an operation process of a control method of session operation in a second application scenario according to the present invention;

fig. 7 is a schematic diagram of an operation process of a control method of session operation in a third application scenario according to the present invention;

fig. 8 is a schematic diagram of an operation process of a control method of session operation in a fourth application scenario according to the present invention;

fig. 9 is a schematic diagram of an operation process of a control method of session operation in a seventh application scenario according to the present invention;

fig. 10 is a schematic diagram of an operation process of a control method of session operation in an eighth application scenario according to the present invention;

fig. 11 is a schematic structural diagram of a control device for session operation according to a third embodiment of the present invention;

fig. 12 is a schematic structural diagram of a control device for session operation according to a fourth embodiment of the present invention;

fig. 13 is an operation process diagram of a control method of session operation in an eleventh application scenario of the present invention;

fig. 14 is an operation process diagram of a control method for session operation in a twelfth application scenario of the present invention.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention and are not to be construed as limiting the present invention.

In order to make the objects, technical means and advantages of the present application more apparent, the present application is further described in detail with reference to fig. 2.

An NG1 interface is arranged between the core network and the UE, and NAS (Non-Access Stratum) data packets are transmitted between the core network and the UE through signaling; the NAS data packet sent to the UE by the core network is sent to the UE through the wireless access network, and the NAS data packet sent to the core network by the UE is sent to the core network through the wireless access network; the contents of the NAS packets are generally transparent to the radio access network, which transmits the NAS packets without knowing the contents of the NAS packets.

The core network may operate multiple UE sessions simultaneously. Multiple QoS flow operations may be involved in one UE session operation.

A QoS profile (QoS profile) for a QoS flow is a QoS parameter for the QoS flow and associated operational requirements (e.g., notification requirements after the QoS flow is not satisfied, mapping QoS attributes, etc.).

In general, the core network decides the QoS rules and QoS profile of the QoS flows. In general, the core network may send QoS rules for QoS flow authorization to the UE. The UE applies the authorized QoS rules to decide the mapping of traffic data flows and QoS flows. The core network may send the QoS profile of the QoS flow to the radio access network. The radio access network will decide whether to accept the QoS flow based on its QoS profile. If so, the Radio access network may establish mapped Radio resources (such as a Data Radio Bearer (DRB)) for the QoS flow.

When a new service data flow arrives, the core network needs to decide to map the QoS flow for the service data flow. The method can be implemented by adopting one of the following modes: and modifying the existing QoS rule to include a new service data stream by adopting a default QoS rule, and establishing a new QoS rule.

The core network can establish or modify a plurality of UE sessions simultaneously, and one UE session can contain the operation (establishment, modification and deletion) of a plurality of QoS flows. The core network may also establish and/or modify and/or delete multiple QoS flows in one UE session at the same time, such as: establishing a QoS flow, deleting a QoS flow, modifying QoS parameters of a QoS flow, modifying QoS profiles (QoS profiles such as QoS Profile), modifying mapping rules of QoS flows and traffic data flows (QoS rule). The establishment or modification of a UE session or QoS flow by the core network may require synchronization to the radio access network and the UE. The Radio access network may perform configuration according to the established content, for example, determine configuration of a DRB (Data Radio Bearer) mapped by the QoS flow according to QoS parameters or QoS profile of the QoS flow, and establish the configured DRB with the UE. The Radio access network may change the configuration according to the modified content, for example, determine DRB (Data Radio Bearer) mapped by the QoS flow according to the updated QoS parameter or the updated QoS profile of the QoS flow. Of course, for the modified content, the radio access network may establish a DRB to map the updated QoS flow; or the DRB of the QoS flow mapping can be changed; the radio access network may not change the configuration, for example, if the DRB mapped to the QoS flow before modification can still meet the QoS requirement of the QoS flow after modification, the mapping between the QoS flow and the DRB is maintained, etc.; wherein the modification of the QoS flow also belongs to the modification of the UE session.

The following series of problems also exist with respect to the modification of UE sessions/QoS flows. The following analyses were performed one by one:

problem 1: generally, when a core network requests a radio access network to establish or modify a session of a UE, session establishment information or modification information to be synchronized to the UE is included in an NAS data packet and sent to the radio access network, and after the radio access network completes establishment or modification of the session of the UE, the radio access network sends the received NAS data packet to the UE. However, due to resource limitations and the like, the radio access network may not be able to satisfy the establishment or modification of the UE session, for example, when the QoS flow is changed from a non-guaranteed bit rate (non GBR) to a Guaranteed Bit Rate (GBR), the radio access network may fail to modify the rate that the GBR may not guarantee currently; for modifying the failed QoS flow, the radio access network may maintain the original configuration of the QoS flow and inform the core network of the failure result.

After receiving the NAS packet, the UE performs its own configuration.

-if one NAS packet contains setup information for multiple UE sessions or setup information for multiple QoS flows in one session. Since the operation of the access stratum and the non-access stratum of the UE are independent. Sessions and QoS flows may be accepted by the UE for UE sessions and QoS flows that are not accepted for establishment by the radio access network. That is, the access stratum is failed to be established, and the non-access stratum is successfully established. This results in inconsistent configuration of the UE access and non-access layers, resulting in inconsistent configuration between the UE and the radio access network. And the UE maps the service data stream according to the received mapping rule of the QoS stream. However, the QoS flow is not configured with the radio resource DRB, and cannot complete the transmission. The operation of mapping the traffic data streams according to the QoS rules is redundant, consuming valuable computational resources and power of the UE. For traffic, if the QoS flow is not mapped according to the dedicated QoS rules, it can also be mapped according to the default QoS rules of the PDU session and there is an opportunity to be transmitted. If the QoS flow without DRB is still mapped, a false connection may occur, which looks like data is being transmitted, but actually data is not being transmitted. If the configuration of the UE is corrected after the core network is found, additional signaling overhead is consumed.

-if modification information for multiple UE sessions is contained in one NAS data packet. Likewise, session modifications may be accepted by the UE for UEs that are not accepted by the radio access network. Thus, the configuration of the UE access layer and the non-access layer is inconsistent, and the configuration between the UE and the radio access network is inconsistent; if a NAS packet contains modification information of the QoS flow of a UE session, the modification of the QoS flow that is not accepted by the radio access network is also accepted by the UE. This results in inconsistent configurations of the UE access and non-access layers, and results in inconsistent configurations between the UE and the radio access network.

Problem 2: the UE may also fail to modify its own configuration by receiving the NAS packet, and the UE returns a modification result through the NAS packet, and the NAS packet is sent to the radio access network first and then to the core network. However, if one NAS packet contains modification information of multiple UE sessions, the radio access network may accept UE session modifications that are not accepted by the UE, and thus, configuration between the UE and the radio access network will be inconsistent; if a NAS packet contains modification information of a UE session, the radio access network may also accept QoS flow modifications that are not accepted by the UE, thus resulting in inconsistent configuration between the UE and the radio access network.

Problem 3: for the session or QoS flow that fails to be modified, the configuration before modification may be maintained to continue serving the UE, or may need to be released because the traffic demand of the UE cannot be met. In the latter case, after the core network fails to confirm the modification, a release process needs to be triggered to release the relevant session/QoS flow, resulting in redundant signaling overhead.

Problem 4: the QoS parameters for establishing QoS flows that may be unacceptable to the radio access network due to radio resource limitations; for QoS flows that cannot accept QoS parameters, an error may occur if the UE or core network applies its corresponding QoS rules. At this time, it may be considered to reduce the QoS parameter requirements of the QoS flow, or to apply default QoS rules, or to release the relevant traffic data. The establishment of UE sessions/QoS flows also faces problems 1, 2, and 4 in the modification of UE sessions/QoS flows; the release of the UE session/QoS flow may face problems 1, 2, and 4 in the modification of the UE session/QoS flow.

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.

It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

For convenience of understanding, before the technical solutions of the present invention are described in detail, some technical terms in the embodiments of the present invention are described as follows:

in some embodiments, the radio access network node may be at least one of: a base station, an evolved node B (eNodeB), a node B (NodeB), a 5G radio access technology base station, gbb, a radio access network central control unit (CU, e.g., gbb-CU), a radio access network node distribution unit (DU, e.g., gbb-DU), a source radio access network node during UE movement, a target radio access network node during UE movement, a new radio access network node to which the UE accesses in a light connection mode or in an inactive state, an old radio access network node to which the UE saves a UE context in the light connection mode or in the inactive state, a radio access network node on which the UE is suspended, and a radio access network node to which the UE requests connection restoration; in next generation networks, the concept of a node may be virtualized as a function or unit, and a radio access network central control unit may connect a plurality of radio access network node distribution units.

The UE may further distinguish at least one of the following: the UE AS a whole, a non-access stratum (e.g., NA layer) of the UE, an access stratum (e.g., AS layer) of the UE, and an application layer (e.g., APP layer) of the UE.

In some embodiments, the core network node may be at least one of: MME (Mobility Management Entity), SGSN (Serving GPRS Support Node), SGW (service gateway), AMF (Access Mobility Management Function), SMF (Session Management Function), UPF (User Port Function), core network control Node, core network User plane Node, core network control plane Function, core network User plane Function, core network control plane unit, core network User plane unit, and the like; in next generation networks, the concept of a node may be virtualized as a function or unit.

In some embodiments, the core network control node may be an MME, SGSN, AMF, SMF, core network control plane function, core network control plane element, or the like;

in some embodiments, the core network user plane node may be an SGW, an SGSN, a UPF, a core network user plane function, a core network user plane element, a network segment, or the like.

Unless specifically indicated, the operations herein may be at least one of: establishing, modifying and releasing; the object of the operation may be at least one of: session (e.g., PDU (Protocol Data Unit) session), PDU connection), qoS flow.

In some embodiments, establishing a QoS flow or session is allocating corresponding resources for the QoS or session, releasing a QoS flow or session is releasing the allocation of corresponding resources for the QoS or session, and modifying configuration information for a QoS flow or session may or may not cause the corresponding resources to change because the current resources may still be able to satisfy the new configuration.

In some embodiments, a reference to "operation" herein refers to establishing, modifying, and/or releasing, if not specified otherwise. The object of "session operation" refers to a QoS flow and/or a UE session, if not specified. The "session/QoS flow" as referred to herein, if not specified, refers to a QoS flow and/or a UE session.

In some embodiments, reference herein to "NAS message" or "NAS signaling" refers to the contents of a NAS packet, if not specified.

Reference herein to "assigning/mapping radio bearers" means assigning and/or mapping radio bearers, if not specified otherwise.

References herein to "QoS profile/QoS parameters" refer to QoS profiles and/or QoS parameters unless specified otherwise. A method for controlling a session operation, comprising: the first node learns first session operation information about UE; wherein the first session operation information on the UE comprises at least one of: first session operation request information and first session operation result information; and determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information on the UE.

Preferably, after determining whether to accept the operation request of the session/QoS flow in the first session operation request information, the method further comprises: generating second session operation request information; and/or generating second session operation result information.

Preferably, the second session operation result information is generated, including at least one of:

the session/QoS flow in the first session operation request information which is not executed or refused to be executed is used as the session/QoS flow which is failed to operate in the second session operation result information; the session/QoS flow in the first session operation request information which can accept operation or successfully operate is used as the session/QoS successfully operated in the second session operation result information; taking the session/QoS flow with failed operation in the obtained first session operation result information as the session/QoS flow with failed operation in the second session operation result information; and taking the session/QoS flow which is successfully operated in the acquired first session operation result information as the session/QoS flow which is failed to operate in the second session operation result information.

Preferably, the generating the second session operation request information specifically includes: the session/QoS flow in the first session operation request information which does not execute or refuses to execute modification is used as the session/QoS flow of the release request in the second session operation result information; the session/QoS flow in the first session operation request information capable of accepting an operation or a successful operation is taken as the session/QoS of the requested operation in the second session operation request information.

Preferably, the first node is at least one of: the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node for storing a context of the UE in the light connection mode or the inactive state, a radio access network node for suspending the UE, and a radio access network node for requesting connection recovery of the UE.

Preferably, the first session operation request information and the second session operation request information at least include one of the following items: operation request information; session information for operating the associated session; operating QoS flow information of a related quality of service QoS flow; requesting session information of the established session; requesting session information for the modified session; requesting session information of the released session; requesting the QoS flow information of the established QoS flow; requesting QoS flow information for the modified QoS flow; requesting QoS flow information of the released QoS flow; and/or

The first session operation result information and the second session operation result information at least comprise one of the following items: operation result information; operation information; session information for operating the associated session; operating QoS flow information of the relevant QoS flow; establishing session information of a successful session and/or establishing session information of a failed session; modifying the session information of the successful session and/or modifying the session information of the failed session; releasing the session information of the successful session and/or releasing the session information of the failed session; qoS flow information of a successful QoS flow is established and/or QoS flow information of a failed QoS flow is established; modifying QoS flow information of a successful QoS flow and/or modifying QoS flow information of a failed QoS flow; releasing QoS flow information for successful QoS flows and/or releasing QoS flow information for failed QoS flows.

Preferably, the operation request information includes at least one of: request establishment; requesting modification; requesting release; modifying the subsequent operation requirement which fails; and/or

The operation result information includes at least one of: the operation is successful; the operation fails; the establishment is successful; the establishment fails; the modification is successful; the modification failed; the release is successful; the release failed; the operation can be successful; the establishment can be successful; the modification can be successful; (ii) can release failure; and/or

The QoS flow information includes at least one of: an identification of the session to which it belongs; identification of QoS flows; qoS profile of QoS flows; qoS flow related QoS rules; information that the QoS flow is successfully established; information of QoS flow establishment failure; information that the QoS flow modification is successful; information of QoS flow modification failure; a QoS parameter; configured bearer information of the DRB; the reason for the operation failure; modifying the subsequent operation requirement which fails; and/or

The session information includes at least one of: an identification of the session; carrying information of the configured DRB; configured NG interface channel information; qoS flow information of the included QoS flow; the reason for the operation failure; and modifying the subsequent operation requirement which fails.

Preferably, the subsequent operation requirement for failed modification includes at least one of: maintaining the configuration before modification; releasing the QoS flow failed to modify; releasing the session that failed to modify.

Preferably, the information that the QoS flow establishment is successful includes at least one of: establishing a successful QoS flow identifier, establishing a successful QoS flow mapped wireless bearer identifier, receiving the QoS flow by the UE, receiving the QoS rule of the QoS flow by the UE, receiving the QoS flow at a non-access layer, receiving the QoS flow by a wireless access network node, distributing/mapping the QoS flow of the wireless bearer for the QoS flow by the wireless access network, receiving the QoS flow at an access layer, receiving the QoS introduction of the QoS flow by the wireless access network node, receiving the QoS parameter of the QoS flow by the wireless access network node, and establishing the QoS flow of necessary wireless resources;

preferably, the information of the QoS flow establishment failure includes at least one of: an identification of a failed QoS flow to be established, the QoS flow being rejected by the UE, qoS flow QoS rules being rejected by the UE, the QoS flow being rejected at a non-access stratum, the QoS flow being rejected by a radio access network node, the QoS flow having no configured radio bearer, the QoS flow having no mapped radio bearer, the QoS flow being rejected at an access stratum, a QoS profile of the QoS flow being rejected by a radio access network node, qoS parameters of the QoS flow being rejected by a radio access network node, no QoS flow having necessary radio resources (such as radio bearers) being established and/or mapped;

preferably, the information that the QoS flow modification is successful includes at least one of: modifying successful QoS flow identification, modifying the identity of the radio bearer to which the successful QoS flow is mapped, qoS rule updates for QoS flows being accepted by the UE and/or core network nodes (e.g., SMF, UPF), qoS profile updates for QoS flows being accepted by radio access network nodes, qoS parameter updates for QoS flows being accepted by radio access network nodes, radio access network allocating/mapping radio bearers according to QoS profiles or QoS parameters updated for QoS flows, qoS flows having necessary radio resources established and/or mapped according to the updates;

preferably, the information of QoS flow modification failure includes at least one of: modifying the identity of the failed QoS flow, modifying the identity of the radio bearer mapped before the failed QoS flow, qoS rule updates for the QoS flow rejected by the UE and/or core network node (e.g., SMF, UPF), qoS profile updates for the QoS flow rejected by the radio access network node, qoS parameter updates for the QoS flow rejected by the radio access network node, the radio access network node being unable to assign/map radio bearers based on the QoS profile updated for the QoS flow, the radio access network being unable to assign/map radio bearers based on the updated QoS parameters, no QoS flows that establish and/or map the necessary radio resources (e.g., radio bearers) based on the updates.

Preferably, the session operation information of the user equipment UE is acquired by any one of: a core network; a radio access network; a base station of 5G radio access technology, gbb; a centralized control unit gNB-CU of a base station of a 5G radio access technology; a distribution unit gNodeB-DU of a base station of a 5G radio access technology; a UE; a radio access network node; a core network node; a data termination point; a non-access stratum of the UE; a non-access stratum of the UE; an application layer of the UE; a control unit CU; a distribution unit DU; a core network user plane node; a core network control plane node; a source wireless access network node in the UE moving process; a target wireless access network node in the UE moving process; a new radio access network node accessed by the UE in a light connection mode or an inactive state; the UE saves the old radio access network node of the UE context in the light connection mode or in an inactive state; suspending a radio access network node of the UE; and the UE requests the wireless access network node with the connection recovered.

Preferably, the determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE includes at least one of the following situations:

for the session/QoS flow which fails to operate in the first session operation result information, the operation request of the session/QoS flow which fails to establish in the first session operation request information is not executed or refused to be executed;

modifying the failed conversation/QoS flow in the first conversation operation result information, and releasing the modified failed conversation/QoS flow;

for the session/QoS flow successfully operated in the first session operation result information, accepting or executing the operation request of the successfully operated session/QoS flow in the first session operation request information;

a QoS flow satisfying at least one of the following conditions in the first session operation result information: the QoS flow is successfully established, and the QoS flow is successfully modified; accepting or executing the operation request of the QoS flow successfully established and/or modified in the first session operation request information, wherein the operation request at least comprises one of the following items: accepting or applying QoS rules associated with the QoS flow, accepting or applying a QoS profile for the QoS flow, accepting or applying QoS parameters for the QoS flow, accepting or applying QoS rule updates for the QoS flow, accepting or applying QoS profile updates for the QoS flow, accepting or applying QoS parameter updates for the QoS flow;

a QoS flow satisfying at least one of the following conditions in the first session operation result information: the QoS flow is failed to establish, the QoS flow is failed to establish and cannot apply the default QoS rule, and the related service data in the failed QoS flow cannot apply the default QoS rule; the method does not execute or refuses to execute the operation request of the QoS flow in the first session operation request information, and at least comprises the following steps: the QoS rules associated with the QoS flow are rejected or not applied, the QoS rules associated with the QoS flow are requested to be rejected or not applied by other nodes, the QoS rules associated with the QoS profile of the QoS flow are rejected or not applied, the QoS rules associated with the QoS flow are requested to be released and/or not applied by other nodes, the QoS profile of the QoS flow is rejected or not applied, the QoS parameters of the QoS flow are rejected or not applied, the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow are discarded by other nodes, the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow are requested to be discarded by other nodes, the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow are temporarily buffered by other nodes, the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow are requested to be temporarily buffered by other nodes, the default QoS rules are applied for the data of the traffic data flow associated with the QoS flow, the default rules are applied for the data of the traffic data associated with the QoS flow of the QoS flow, the QoS flow is requested to be temporarily buffered, the QoS flow requirements are lowered, the default QoS flow data associated with the QoS flow data is configured, and the QoS flow data associated with the QoS flow is transmitted.

A QoS flow satisfying at least one of the following conditions in the first session operation result information: the QoS flow modification fails, and the relevant new service data flow in the QoS flow with the modification failure can not apply the default QoS rule; the operation request of the QoS flow in the first session operation request information is not executed or refused to be executed, and at least one of the following items is included: rejecting and/or releasing QoS rules updates for the QoS flow, requesting other nodes to reject and/or release QoS rules updates for the QoS flow, rejecting and/or releasing QoS rules associated with the QoS flow, requesting other nodes to reject and/or release QoS rules for the QoS flow, maintaining pre-modification QoS rules for the QoS flow, requesting other nodes to maintain pre-modification QoS rules for the QoS flow, rejecting or not applying QoS rules updates associated with updated QoS profile updates or QoS parameter updates, rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow, maintaining pre-update QoS profiles or QoS parameters for the QoS flow, maintaining a pre-update mapped radio bearer for the QoS flow, dropping data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to drop data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, temporarily caching data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to temporarily cache data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, and applying QoS profile updates for the newly added traffic data for the QoS flow, the default traffic flow, and the default QoS data for the newly added traffic flow is not configured for the QoS flow.

The technical solution of the present invention is described in detail below in the form of specific embodiments:

step 310: the first node learns first session operation information about UE; wherein the first UE-related session operation information includes at least one of: first session operation request information and first session operation result information; step 320: and determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE.

Specifically, step 310 is: the first node learns first session operation information about the UE.

Optionally, the first session operation information about the UE may include at least one of: first conversation operation request information and first conversation operation result information.

Optionally, the session operation request information or the first session operation request information may include at least one of:

information of operation requests (operation requests such as request establishment, authorization, request modification of configuration, or request release, etc.),

session information of operation related sessions (operation related sessions such as sessions in which the object of operation is a UE),

QoS flow information of operation related QoS flows (operation related QoS such that the object of the operation is a QoS flow of the UE),

-session information of the session requested to be established,

-requesting session information for the modified session,

-session information of the session requested to be released,

QoS flow information of the requested established QoS flow (which may also be embodied as QoS flow information of an authorized QoS flow, such as authorized QoS rules),

-requesting QoS flow information for the modified QoS flow,

-QoS flow information of the requested QoS flow.

In some embodiments, the first node is a UE, and learns that the first session operation request information is from a message of a NAS layer of a core network, such as a PDU session setup accept message and a PDU session modification command message. In the PDU session establishment accept message, the QoS flow in the authorized QoS rule may embody the QoS flow requested to be established. In the PDU session modification command message, the QoS flow in the authorized QoS rule may represent the QoS flow requested to be established, and the QoS flow in the requested modified QoS rule may represent the QoS flow requested to be modified. The first session operation result information known by the UE is the operation result of the radio access network node on the QoS flow requested to be established, for example, a radio bearer with a QoS flow mapping may indicate that the QoS flow is successfully established, and a radio bearer without the QoS flow mapping indicates that the QoS flow is unsuccessfully established.

In some embodiments, the first node is a radio access network node, and the first session operation request information is learned from a PDU session resource setup request message of a NG interface of the core network. In the PDU session resource establishment request message of the NG interface, the QoS flow requested to be added may represent the QoS flow requested to be established. Its QoS flow information may contain QoS profiles/QoS parameters for QoS flows. The radio access network node may allocate/map radio bearers (such as DRBs) for QoS flows based on the QoS profile/QoS parameters. The radio bearer may be used to transport QoS flow data.

Optionally, the information of the operation request may include at least one of: request establishment, request modification, request release, and subsequent operation requirements of failed modification.

Wherein the subsequent operation requirement for failed modification may include at least one of: and after the modification fails, maintaining the configuration before the modification, releasing the QoS flow which fails to modify, and releasing the session which fails to modify. It is understood that the modification failed subsequent operation requirement is an action that needs to be executed after the modification of the session or the QoS flow requested to be modified fails or the modification is not accepted, and by modifying the failed subsequent operation requirement, the operation process of the session can be accelerated and the signaling operation can be reduced, thereby avoiding excessive signaling overhead caused by the process of initiating the release again after the modification fails.

Optionally, the session operation result information or the first session operation result information may include at least one of:

information of the operation results (e.g. success, failure, success of establishment, failure of establishment, success of modification, failure of modification, success of release, failure of release, etc.),

information of the operation (e.g. setup, modification, release, etc.),

-session information for operating the associated session,

-QoS flow information of operation related QoS flows,

-session information for establishing a successful session, session information for establishing a failed session,

-modifying session information of successful sessions, modifying session information of failed sessions (which may also be embodied as leave-unchanged or reject-modified sessions),

-releasing session information of a successful session, releasing session information of a failed session,

QoS flow information for a successful QoS flow to be established, qoS flow information for a failed QoS flow to be established,

-modifying QoS flow information for successful QoS flows, modifying QoS flow information for failed QoS flows (which may also be embodied as stay-the-same or reject modified QoS flows),

-releasing QoS flow information for successful QoS flows, releasing QoS flow information for failed QoS flows.

In some embodiments, the QoS flow establishment success may be manifested by at least one of: the UE accepts the QoS flow, the UE accepts the QoS rule of the QoS flow, the QoS flow is accepted at a non-access layer, the wireless access network node accepts the QoS flow, the wireless access network allocates/maps the QoS flow of a wireless bearer (such as DRB) for the QoS flow, the QoS flow has the mapped wireless bearer, the QoS flow is accepted at an access layer, the QoS profile of the QoS flow is accepted by the wireless access network node, the QoS parameter of the QoS flow is accepted by the wireless access network node, and the QoS flow of necessary wireless resources is established.

In some embodiments, the QoS flow setup failure may be at least one of: qoS flows are rejected by the UE, qoS flow QoS rules are rejected by the UE, qoS flows are rejected at non-access stratum, qoS flows are rejected by the radio access network node, qoS flows have no configured radio bearer (e.g., DRB), qoS flows have no mapped radio bearer (e.g., DRB), qoS flows are rejected at access stratum, qoS profiles of QoS flows are rejected by the radio access network node, qoS parameters of QoS flows are rejected by the radio access network node, qoS flows have no radio resources established and/or mapped.

In some embodiments, the QoS flow modification success may be at least one of: qoS rule updates for QoS flows are accepted by the UE and/or core network nodes (e.g., SMF, UPF), qoS profile updates for QoS flows are accepted by radio access network nodes, qoS parameter updates for QoS flows are accepted by radio access network nodes, and radio access network assigns/maps radio bearers based on the QoS profile or QoS parameters updated by QoS flows. In some embodiments, the radio bearer mapped before updating satisfies the updated QoS profile/QoS parameter requirements, and the radio access network may establish and/or map the QoS flows of the necessary radio resources according to the updating without changing the radio bearer mapped by the QoS flows.

In some embodiments, the QoS flow modification failure may be at least one of: qoS rule updates for QoS flows are rejected by UEs and/or core network nodes (e.g., SMF, UPF), qoS profile updates for QoS flows are rejected by radio access network nodes, qoS parameter updates for QoS flows are rejected by radio access network nodes, radio access network nodes cannot allocate/map radio bearers based on QoS profile updates for QoS flows, radio access network nodes cannot allocate/map radio bearers based on updated QoS parameters, and QoS flows that do not establish and/or map necessary radio resources based on updates.

In some embodiments, the radio access network cannot allocate/map radio bearers according to the updated QoS parameters, and may maintain the mapped radio bearers before updating for the QoS flows.

Optionally, the information of the operation result may include at least one of: the operation is successful, the operation is failed, the establishment is successful, the establishment is failed, the modification is successful, the modification is failed, the release is successful, the release is failed, the operation is successful, the establishment is successful, the modification is successful, and the release is failed. In some embodiments, the first session operation result information is a result of an operation that has been completed or a result of an operation that can be completed, wherein the result of the operation that can be completed may represent an ability to complete but not yet actually complete. In some embodiments, the learned first session operation result information may be an operation result performed by the first node according to the first session request information or received session operation result information (e.g., operation result information performed by other nodes according to the first session request information).

Optionally, the QoS flow information may include at least one of: the QoS profile of the QoS flow, qoS rules related to the QoS flow, information that the QoS flow is successfully established, information that the QoS flow is failed to be established, information that the QoS flow is successfully modified, information that the QoS flow is failed to be modified, an identifier of a session to which the QoS flow belongs, an identifier of the QoS flow, qoS parameters, bearer information (such as an identifier of a DRB, a logical channel identifier mapped by the DRB, qoS parameters of the DRB, a PDCP (Packet Data Convergence Protocol) configuration of the DRB, an RLC (Radio Link Control) configuration and/or a logical channel configuration, and the like) of an associated DRB, a reason for an operation failure (which may be one of the QoS flow information of the QoS flow that the operation fails), and a subsequent operation requirement for the establishment failure (which may indicate at least one of mapping a service Data flow related to the QoS flow that the QoS flow is failed by using a default QoS rule, and releasing a service Data flow related to the QoS flow that the establishment is failed) (which the QoS flow is related to the QoS flow may be known by the QoS rule of the QoS flow). Modifying the failed subsequent operational requirement (which may indicate at least one of maintaining the pre-modification configuration after the modification failure, releasing the failed QoS flow, and modifying the newly added traffic data flow of the failed QoS flow using a default QoS rule mapping (e.g., the newly added traffic data flow of the QoS flow may be known by the updated QoS rule of the QoS flow)). It will be understood that when the operation on the QoS flow is a modification of the configuration and the modification fails, the first node may release the relevant resources of the QoS flow or maintain the configuration of the QoS flow before the modification fails, according to the subsequent operation requirements of the modification failure.

Optionally, the default QoS rule is a PDU session default QoS rule, and for the service data without mapped QoS rule, mapping may be performed according to the default QoS rule.

Optionally, the information that the QoS flow establishment is successful may indicate one of the following: the method comprises the steps of establishing an identification of a successful QoS flow, establishing an identification of a radio bearer mapped by the successful QoS flow, receiving the QoS flow by UE, receiving a QoS rule of the QoS flow by UE, receiving the QoS flow at a non-access layer, receiving the QoS flow by a radio access network node, distributing/mapping the QoS flow of a radio bearer (such as DRB) for the QoS flow by the radio access network, receiving the QoS flow at an access layer by the QoS flow with mapping, receiving the QoS flow at the access layer, receiving a QoS profile of the QoS flow by the radio access network node, receiving a QoS parameter of the QoS flow by the radio access network node, and establishing the QoS flow of necessary radio resources.

Optionally, the information of QoS flow establishment failure may indicate one of the following: identification of a QoS flow that failed to be established, the QoS flow being rejected by the UE, qoS flow QoS rules being rejected by the UE, the QoS flow being rejected at a non-access stratum, the QoS flow being rejected by a radio access network node, the QoS flow being without a configured radio bearer (e.g., DRB), the QoS flow being without a mapped radio bearer (e.g., DRB), the QoS flow being rejected at an access stratum, the QoS profile of the QoS flow being rejected by a radio access network node, qoS parameters of the QoS flow being rejected by a radio access network node, qoS flows without establishing and/or mapping necessary radio resources.

Optionally, the information that the QoS flow modification is successful may be at least one of: modifying successful QoS flow identification, modifying identity of radio bearers to which successful QoS flow mappings are mapped, qoS rule updates for QoS flows being accepted by UE and/or core network nodes (e.g., SMF, UPF), qoS profile updates for QoS flows being accepted by radio access network nodes, qoS parameter updates for QoS flows being accepted by radio access network nodes, radio access network allocating/mapping radio bearers based on QoS profile or QoS parameters updated for QoS flows, qoS flows having necessary radio resources established and/or mapped based on the updates.

In some embodiments, the radio access network may not change the radio bearers to which the QoS flows are mapped when the radio bearers to which the mapping is performed before the update meet the updated QoS profile/QoS parameter requirements. At this time, the radio access network node may still send the updated QoS flow mapped radio bearer identification to the UE. In this way, the UE can know that the QoS parameters or QoS profile update of the QoS flow is successful and the associated DRB is unchanged.

Optionally, the QoS flow modification failure information may be at least one of: modifying the failed QoS flow identification, modifying the identity of the radio bearer mapped before the failed QoS flow, qoS rule updates for the QoS flow being rejected by the UE and/or core network node (e.g., SMF, UPF), qoS profile updates for the QoS flow being rejected by the radio access network node, qoS parameter updates for the QoS flow being rejected by the radio access network node, the radio access network node being unable to assign/map radio bearers based on the QoS profile updated for the QoS flow, the radio access network being unable to assign/map radio bearers based on the updated QoS parameters, no QoS flows having the necessary radio resources being established and/or mapped based on the update.

In some embodiments, when the radio access network node fails to meet the updated QoS profile/QoS parameter requirements, the radio access network may not change the radio bearers mapped before the QoS flow. At this point, the radio access network node may send the QoS flow identification for which the modification failed to the UE. In this way, the UE may know that the QoS parameters or QoS profile update of the QoS flow failed.

Optionally, the QoS profile (QoS profile) and/or QoS parameters of the QoS flow may include, but are not limited to, at least one of: qoS Flow identification, 5G QoS Indicator (5 QI)), allocation and Retention Priority (ARP)), uplink Guaranteed Flow Bit Rate (GFBR) -UL), downlink Guaranteed Flow Bit Rate (GFBR) -DL), uplink Maximum Flow Bit Rate (MFBR) -UL), downlink Maximum Flow Bit Rate (MFBR) -DL), guaranteed Bit Rate type, non-Guaranteed Bit Rate type, notification control Indicator (Notification control), i.e. when the QoS Flow requirement (such as QoS parameter requirement) cannot be met, notification to the core network is required, and QoS Attribute (RQA)) is reflected.

Optionally, a QoS rule (QoS rule) associated with a QoS flow is a mapping rule of a service data flow to a QoS flow. A QoS rule may include, but is not limited to, at least one of the following: the QoS rule identifies, a mapped QoS flow identifier, a packet filtering rule (packet filters), a priority (a precedence value), and a QoS parameter of the QoS flow (such as a QoS parameter of the QoS flow related to the UE). A QoS flow may have multiple QoS rules.

Optionally, the information of the session may include at least one of: the identification of the session, the configured bearer information of the DRB (such as the identification of the DRB, the QoS parameters of the DRB, the PDCP/RLC/configuration of the DRB, etc.), the configured NG interface channel information, the QoS flow information of the included QoS flow, the reason of the operation failure (which may be one of the session information of the session with the operation failure), and the subsequent operation requirement of the modification failure (which may indicate at least one of maintaining the configuration before modification after the modification failure, and releasing the session with the modification failure). It will be appreciated that when the operation on the session is a modification of the configuration and the modification fails, the first node may release the session or maintain the previous configuration of the session, depending on the requirements of the subsequent operation on which the modification failed.

Optionally, the session operation information about the UE may be known by one of the following: the core network, the radio access network, the gNodeB-CU, the gNodeB-DU, the UE, the radio access network node, the core network node, the data terminal node, the non-access layer (such AS the NA layer) of the UE, the non-access layer (such AS the AS layer) of the UE, the application layer (such AS the APP layer) of the UE, the CU, the DU, the core network user plane node, the core network control plane node, the source radio access network node during the movement of the UE, the target radio access network node during the movement of the UE, the new radio access network node accessed by the UE in a light connection mode or an inactive state, the old radio access network node storing the context of the UE in the light connection mode or the inactive state, the radio access network node suspending the UE, and the radio access network node requesting connection recovery of the UE.

In some embodiments, the first session operation request information and the first session operation result information may come from different nodes or node units, such as the session operation request information from a core network and the session operation result information from a radio access network node, the first node being a UE. For another example, the session operation request information is from a core network, the session operation result information is from the UE, and the first node is a radio access network node.

The session operation information about the UE known by the core network may be contained in NAS packets and/or in information elements other than NAS packets in the NG interface message.

The session operation information about the UE, which is learned through the Radio access network, may be included in a cell other than a NAS data packet in a Radio Resource Control (RRC) message.

The session operation information about the UE known by the UE may be included in the NAS packet and/or in an information element other than the NAS packet in the RRC message.

Optionally, the first node may be at least one of: the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer (such AS an NA layer) of the UE, a non-access layer (such AS an AS layer) of the UE, an application layer (such AS an APP layer) of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node storing a context of the UE in the light connection mode or the inactive state, a radio access network node suspending the UE, and a radio access network node requesting connection recovery of the UE.

Specifically, step 320 is: the first node determines whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information on the UE.

In some embodiments, the learned first session operation result information may be an operation result performed by the first node according to the first session request information or received session operation result information (e.g., operation result information performed by other nodes according to the first session request information).

Specifically, after determining whether to accept the operation request of the session/QoS flow in the first session operation request information, at least one of the following may be further included: and generating second session operation request information and second session operation result information.

The learned first session operation result information may be the result of an operation performed by the first node according to the first session request information or the result of an operation performed by the received other node according to the first session request information.

Specifically, the first node determining whether the operation request of the session/QoS flow in the first session operation request information can be accepted according to the learned session operation information about the UE may include at least one of:

-1) for the session/QoS flow whose operation failed in the first session operation result information, not executing or rejecting the operation request in the first session operation request information for the session/QoS flow whose operation failed; such as

For the session/QoS flow failed to be established in the first session operation result information, the establishment request of the session/QoS flow failed to be established in the first session operation request information is not executed or refused to be executed;

for the failed session/QoS flow modified in the first session operation result information, the modification request of the failed session/QoS flow modified in the first session operation request information is not executed or refused;

and for the session/QoS flow which fails to be released in the first session operation result information, the release request of the session/QoS flow which fails to be released in the first session operation request information is not executed or refused.

-2) releasing said session/QoS flow failed to modify for the session/QoS flow failed to operate in the first session operation result information; such as

the first node releasing the session/QoS flow for which the modification failed may be based on the modification of the session/QoS flow

The subsequent operation requirement of the failure is executed by 'release';

-3) for the session/QoS flow successfully operated in the first session operation result information, the operation request of the session/QoS flow successfully operated in the first session operation request information can be accepted or executed.

In some embodiments: the first node is a UE; the first node may learn the session operation request information from the NAS packet of the core network node, and may also learn session operation result information from the radio access network node (the session operation result information may be an operation result of the radio access network node for the session operation request about the UE). For the related session or the related QoS flow where the radio access network node explicitly indicates the operation failure, the first node does not execute or refuse to execute the operation request for the related session or the related QoS flow from the core network, and specifically may include one of the following:

-establishing a failed session/QoS flow for the radio access network, the first node may not perform or reject the establishment request of the relevant session;

-for the radio access network to modify the failed session, the first node may perform at least one of: and the modification request of the related session is not executed or refused to be executed, and the session which fails to be modified by the radio access network is released. The first node releasing the session that failed to modify may be performed in accordance with a requirement that a subsequent operation that failed to modify the session be "release";

-releasing the failed session to the radio access network, the first node may not perform or refuse to perform a release request of the related session;

-for a failed QoS flow established in the radio access network, the first node may not perform or reject the request for establishment of the relevant QoS flow;

-for the radio access network modifying the failed QoS flow, the first node may perform at least one of: and the modification request of the related QoS flow is not executed or refused to be executed, and the QoS flow failed to be modified by the wireless access network is released. The first node releasing the QoS flow for which modification failed may be performed in accordance with a subsequent operation requirement that the modification of the QoS flow failed being "released";

-the first node may not perform or refuse to perform a release request for the failed QoS flow for the radio access network.

It will be readily appreciated that the following,

when the session operation request sent by the core network is a request to operate multiple QoS flows (e.g. QoS parameter modification) in one UE session, the radio access network node may fail to operate on some of the QoS flows. When the radio access network node sends a session operation request about the UE to the UE (the operation request about the UE session can be contained in a NAS data packet), the session operation result about the UE (such as QoS flow information of a QoS flow which is successfully modified or QoS flow information of a QoS flow which is failed to be modified) on the radio access network side is indicated to the UE, and according to the session operation result about the UE sent by the radio access network, the first node only accepts the operation request about the QoS flow which is successfully operated and indicated by the session operation result about the UE or rejects the operation request about the QoS flow which is failed to be operated and indicated by the session operation result about the UE.

When the session operation request sent by the core network is a request to operate multiple UE sessions (e.g. modification of QoS parameters), the radio access network node fails to operate some of the UE sessions. When the radio access network node sends a session operation request about the UE to the UE (the operation request about the UE session may be contained in a NAS data packet), the radio access network side indicates to the UE a session operation result about the UE (such as session information about a successful UE session or session information about a failed UE session), and the first node accepts only a modification request that the session operation result about the UE is a successful UE session or rejects to accept a modification request that the session operation result about the UE is a failed UE session according to the session operation result about the UE sent by the radio access network.

In some embodiments: the first node is a radio access network node (e.g., a gNB-CU); the first node may learn the session operation request information from NG/N2 (interface between the 5G core network and the radio access network) interface signaling sent by the core network node, and may also learn the session operation result information (which may be an operation result of the UE on the session operation request about the UE) from the UE. For the relevant session or the relevant QoS flow for which the UE explicitly indicates an operation failure, the first node may not perform an operation request for the relevant session or the relevant QoS flow from the core network.

-for a QoS flow for which the first node operation failed (setup/modify/release failure), no NAS packets related to this QoS flow are sent to the UE. It is understood that the core network needs to generate a new NAS packet to be sent to the UE. The new NAS packet does not contain the QoS flow for which the first node operation failed.

-establishing a failed session for the UE, the first node may perform at least one of: and the establishment request of the relevant session is not executed or refused, and the session establishment failure is returned to the core network.

-for the UE modifying the failed session, the first node may perform at least one of: and the modification request of the related session is not executed or refused to be executed, and the session which fails to be modified by the radio access network is released. The first node releasing the session that failed the modification may be performed in accordance with a subsequent operation requirement that the modification of the session failed being "released".

-releasing the failed session for the UE, the first node may not perform or refuse to perform the release request of the related session.

-establishing a failed QoS flow for the UE, the first node being operable to perform at least one of: and the establishment request of the relevant QoS flow is not executed or refused, and the failure of the QoS flow establishment is returned to the core network.

-for the UE to modify the failed QoS flow, the first node may perform at least one of: and the modification request of the related QoS flow is not executed or refused to be executed, the QoS flow failed to be modified by the UE is released, and the QoS flow modification failure is returned to the core network. The first node releasing the QoS flow whose modification failed may be performed in accordance with a subsequent operation requirement that the QoS flow's modification failed is "release".

-for the UE releasing the failed QoS flow, the first node may not perform or refuse to perform the release request of the relevant QoS flow.

It will be readily appreciated that the following,

when the session operation request sent by the core network is a request for modifying multiple QoS flows (e.g., modification of QoS parameters) in one UE session, the UE may fail to modify some QoS flows. The UE returns session operation result information (such as QoS flow information of a QoS flow that is successfully modified and QoS flow information of a QoS flow that is failed to be modified) to the core network node through the NAS data packet, and returns session operation result information to the radio access network node through the RRC cell. The first node only accepts the modification request of the QoS flow of which the session operation result indicates the successful modification or rejects the modification request of the QoS flow of which the session operation result is the failed modification according to the session operation result of the UE sent by the UE. The QoS flow successfully modified in the session operation result of the UE returned by the first node to the core network node is the QoS flow successfully modified by both the UE and the first node.

When the session operation request sent by the core network is a request for modification of multiple sessions (e.g., modification of QoS parameters), the UE may fail to modify some of the sessions. The UE returns session operation result information (for example, session information of a successful session and session information of a failed session) to the core network node through the NAS data packet, and simultaneously returns session operation result information to the first node through the RRC cell. The first node only accepts the modification request of the session of which the session operation result indicates the successful modification or rejects the modification request of the session of which the session operation result is the failed modification according to the session operation result of the UE sent by the UE. The session successfully modified in the session operation result of the UE returned by the first node to the core network node is the session successfully modified by both the UE and the first node.

In some embodiments: the first node is a core network node. The first node may learn session operation result information (which may be an operation result of the radio access network node for a session operation request with respect to the UE) from the radio access network node. For the relevant session or the relevant QoS flow for which the radio access network node explicitly indicates an operation failure, the first node does not generate an operation request for the relevant session or the relevant QoS flow. For example, the first node first sends the session operation request information to the radio access network node, and generates the session operation request information about the UE, which is finally sent to the UE, according to the session operation result information returned by the radio access network node. The session operation request information sent by the first node to the UE may be included in the NG interface signaling. The session operation request information transmitted by the first node to the UE may be included in a NAS data packet.

-establishing a failed session to the radio access network, the first node may not send a request for establishment of a related session to the UE.

-for the radio access network to modify the failed session, the first node may perform at least one of: the first node may not send a modification request of the relevant session to the UE, and release the session with which the radio access network has failed to modify.

For a release of a failed session by the radio access network, the first node may not send a release request of the relevant session to the UE.

-for a QoS flow failed to be established by the radio access network, the first node does not send a request for establishment of the relevant QoS flow to the UE.

-for the radio access network to modify the failed QoS flow, the first node may perform at least one of: and not sending a modification request of the related QoS flow to the UE, and releasing the QoS flow failed to be modified by the wireless access network.

-for a radio access network releasing a failed QoS flow, the first node does not send a release request for the relevant QoS flow to the UE.

It is understood that the first node firstly confirms the session operation request information which can be accepted by the radio access network from the radio access network, and then finally generates the session operation request information which is sent to the UE. Therefore, the consistency of the UE, the radio access network and the core network on the conversation operation of the UE can be ensured.

In some embodiments, when the first session operation result information satisfies at least one of the following conditions: the QoS flow is successfully established, and the QoS flow is successfully modified; the first node may perform, but is not limited to, at least one of:

-accepting or applying QoS rules associated with the QoS flow (such as QoS rules for a QoS flow that a UE may accept when a QoS profile or QoS parameters for the QoS flow are accepted by a radio access network node);

-accepting or applying the QoS profile of the QoS flow;

-accepting or applying QoS parameters of the QoS flow;

accepting or applying a QoS rule update for the QoS flow (e.g., when a QoS profile update or QoS parameter update for a QoS flow is accepted by a radio access network node, the UE may accept the corresponding updated QoS rule for the QoS flow);

-accepting or applying a QoS profile update for the QoS flow;

-accepting or applying QoS parameter updates for the QoS flow.

It will be appreciated that a QoS flow can only be delivered if the wireless access network accepts the QoS flow and radio resources (e.g., DRBs) are allocated or mapped based on QoS profile requirements or QoS parameter requirements for the QoS flow. The data of the service data flow can be transmitted after being mapped into QoS flow data through the QoS rule.

In some embodiments, the first session operation result information is when at least one of the following conditions is satisfied: the QoS flow is failed to establish, the QoS flow is failed to establish and cannot apply the default QoS rule, and the relevant service data in the failed QoS flow cannot apply the default QoS rule; the first node may perform, but is not limited to, at least one of:

-rejecting or not applying the QoS rule of the QoS flow association (the QoS rule of the QoS flow association may be a received QoS rule or a preconfigured QoS rule);

requesting the other nodes to reject or not apply the QoS rules associated with the QoS flow (in some embodiments, when the SMF is the first node, the SMF may request to reject or not apply the QoS rules associated with the QoS flow.

-rejecting or not applying QoS rules associated with the QoS profile of the QoS flow;

-requesting the other nodes to reject, release and/or not apply the QoS rules associated with the QoS flow (in some embodiments, when the SMF is the first node, the SMF may request the UPF to reject, release and/or not apply the QoS rules associated with the QoS flow.

-rejecting or not applying the QoS profile of the QoS flow;

-rejecting or not applying QoS parameters of the QoS flow;

-dropping data of the QoS flow and/or data of a traffic data flow associated with the QoS flow (in some embodiments, the first node is a UE and/or a core network node (e.g. SMF, UPF), qoS rules associated with the QoS flow are not applied, while dropping data of a traffic data flow associated with the QoS flow when default QoS rules are not applicable as well);

requesting the other nodes to drop data for the QoS flow and/or data for a traffic data flow associated with the QoS flow (in some embodiments, when the SMF is the first node, the SMF may request the UPF to reject, release, and/or not apply the QoS rules associated with the QoS flow;

the radio access network node may receive the reduced QoS profile request, assign and/or map radio bearers (e.g., DRBs) for the QoS flow, and when the radio bearer DRBs are mapped, the data for the buffered QoS flow or traffic data flow may be transmitted;

-requesting other nodes (e.g. UPF) to temporarily buffer data of the QoS flow and/or data of a traffic data flow associated with the QoS flow;

-applying default QoS rules for data of the traffic data flow to which the QoS flow relates;

-applying a default QoS rule for data of a traffic data flow to which a QoS rule of the QoS flow relates;

-reducing the QoS parameter requirements of the QoS flow (in some embodiments, when the first node is an SMF, the SMF may reduce the QoS parameter requirements of the QoS flow for retransmission to the UE, the UPF and/or the radio access network node may receive the reduced QoS parameter requirements, allocate radio resources for the QoS flow or specify a DRB for mapping.

Release of relevant configuration of the QoS flow (such as QoS profiles and/or QoS rules, etc. in some embodiments, profiles and/or QoS rules for the QoS flow may be released when the first node is a UE and/or a core network node (e.g., SMF, UPF);

-transmitting the QoS flow data using a default radio bearer.

It will be understood that the radio access network may refuse to accept QoS flows, i.e., cannot meet QoS profile requirements for QoS flows, cannot meet QoS parameter requirements for QoS flows, and refuse to assign/map radio bearers for QoS flows, possibly due to limited radio resources, etc. At this time, the data of the service data flow is mapped into the QoS flow data by the QoS rule, which has no value and can be discarded. And the QoS rule of the QoS flow is not mapped, the data of the service data flow can also meet the default QoS rule, and after the data is mapped into the QoS flow corresponding to the default QoS rule, the data can also be transmitted through the wireless resource mapped by the QoS flow associated with the default QoS rule. And for the traffic data flow which can not map the default QoS rule at the same time, the traffic data flow can be discarded or temporarily buffered. Temporary buffering means that the core network node finds that the QoS profile requirements or QoS parameter requirements of the QoS flow are too high to be fulfilled by the radio access network node, which may reduce the QoS profile requirements or QoS parameter requirements of the QoS flow. Radio resources may be allocated or mapped if the radio access network node is capable of accepting QoS profile requirements or QoS parameter requirements for a reduced QoS flow. At this time, the buffered service data stream can be mapped to the QoS rule of the QoS stream to be QoS stream data, and can be transmitted through the mapped wireless resource.

In some embodiments, the first session operation result information is when at least one of the following conditions is satisfied: the QoS flow modification fails, and the relevant new service data flow in the QoS flow with the modification failure can not apply the default QoS rule; the first node may perform, but is not limited to, at least one of:

reject, not apply and/or release the QoS rules update for the QoS flow (in some embodiments, the QoS rules update is associated with a QoS profile/QoS parameters update when the QoS profile/QoS parameters update for the QoS flow is rejected by the radio access network, the UE or the core network may correspondingly reject the QoS rules update);

-requesting the other nodes to reject and/or release the QoS rules update for the QoS flow (in some embodiments, when the SMF is at the first node, the SMF requests the UPF to reject, not apply and/or release the QoS rules update for the QoS flow);

reject, not apply, and/or release QoS rules associated with the QoS flow (in some embodiments, except for updated QoS rules, it may be that none of the existing QoS rules associated with the QoS flow are applicable);

-requesting the other node to reject, not apply and/or release the QoS rules for the QoS flow (in some embodiments, when the SMF is at the first node, the SMF requests the UPF to reject, not apply and/or release the QoS rules for the QoS flow.

-maintaining the pre-modification QoS rules for the QoS flow;

-requesting the other nodes to maintain the pre-modification QoS rules for the QoS flow (in some embodiments, when the SMF is the first node, the SMF requests the UPF to maintain the pre-modification QoS rules for the QoS flow.

The UE and core network may reject or not apply the corresponding QoS rule update when the QoS parameter update is not received by the radio access network;

-rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow;

-maintaining a pre-update QoS profile or QoS parameters for the QoS flow;

-maintaining the pre-update mapped radio bearers (e.g. DRBs) of the QoS flow;

-discarding data of the added traffic data flow related to the QoS rule update of the QoS flow;

-requesting other nodes (e.g. UPF) to discard data of the new traffic data flow associated with the QoS rule update of the QoS flow;

-temporarily buffering data of the added traffic data flow in relation to the QoS rules update of the QoS flow;

-requesting other nodes (e.g. UPF) to temporarily cache data of the added traffic data flow in relation to the QoS rules update of the QoS flow;

-applying default QoS rules for the newly added traffic data flow in relation to the QoS rule update of the QoS flow;

-applying default QoS rules for the new traffic data flow without dedicated QoS rules;

-reducing updated QoS profile requirements or QoS parameter requirements for the QoS flow;

-release of relevant configuration of the QoS flow (such as QoS profile and/or QoS rules, etc.);

-transmitting the QoS flow data using a default radio bearer.

Optionally, after performing session operation on the UE according to the obtained session operation information on the UE, the first node generates and sends second session operation result information (the content of the second session operation result information is as described in the session operation result information in step 301, and is not described herein again). In some embodiments, the second session operation result information may be used in response to the first session operation result information. Specifically, the first node may generate the second session operation result information according to the learned session operation information about the UE, where the second session operation result information includes at least one of:

-1) operating the session/QoS flow in the first session operation request information, which is not executed or is rejected, as the session/QoS flow, which has failed to be operated in the second session operation result information; such as:

the session/QoS flow which does not execute or refuses to execute the establishment is used as the session/QoS flow which fails to be established in the second session operation result information;

the session/QoS flow which does not execute or refuses to execute modification is used as the session/QoS flow which fails to be modified in the second session operation result information;

the session/QoS flow not executing or refusing to execute the release is used as the second session operation result information

Releasing the failed session/QoS flow;

-2) operating the session/QoS flow in the first session operation request information capable of accepting the operation or successful operation as the session/QoS successfully operated in the second session operation result information; such as:

the session/QoS flow which can be accepted to be established or successfully established is used as the successful session/QoS flow established in the second session operation result information;

the session which can accept modification or successful modification is taken as the session/QoS flow which is successfully modified in the second session operation result information;

taking the session which can be released or successfully released as the session/QoS flow successfully released in the second session operation result information;

-3) the session/QoS flow with failed operation in the known first session operation result information is used as the session/QoS flow with failed operation in the second session operation result information.

And 4) taking the session/QoS flow which is successfully operated in the known first session operation result information as the session/QoS flow which is failed to be operated in the second session operation result information.

In some embodiments, a session/QoS flow for which the first node may return an operation failure may have 1) the session or QoS flow for which the first node performed the operation but for which the operation failed and 2) the session or QoS flow for which the first node rejected performing the operation due to other node operation failures. In order to distinguish the above two cases, the session information/QoS flow information of the session/QoS flow with failed operation may carry an indication, such as a reason of failure, where the failure reason distinguishes whether the first node side causes operation failure or other node side causes operation failure, such as operation failure caused by the reason of the UE side or operation failure caused by the reason of the radio access network side (such as insufficient radio resources).

Optionally, the first node performs a session operation on the UE according to the obtained session operation information on the UE, and then generates and sends second session operation request information, where in some embodiments, the first node requests to release a session/QoS flow that fails to be modified.

Specifically, the first node may generate the second session operation request information according to the learned session operation information about the UE, where the second session operation request information includes at least one of:

-1) the session/QoS flow in the first session operation request information that will not be executed or will be rejected from being executed is not operated as the session/QoS flow that is requested by the operation in the second session operation request information; such as:

the session/QoS flow in the first session operation request information which does not execute or refuses to execute the establishment is not taken as the session/QoS flow requested to be established in the second session operation request information;

the session/QoS flow in the first session operation request information which does not execute or refuse to execute modification is not taken as the session/QoS flow which requests modification in the second session operation request information;

the session/QoS flow in the first session operation request information which does not execute or refuse to execute release is not taken as the session/QoS flow requested to release in the second session operation request information;

-2) the session/QoS flow operation in the first session operation request information that will not be executed or will be rejected as being not the session/QoS flow requested by the release in the second session operation request information; such as:

will not execute or refuse to execute the session/QoS flow action in the modified first session operation request information

The session requested to be released in the second session operation request information is obtained;

-3) the session/QoS flow in the first session operation request information capable of accepting the operation or successfully operating is taken as the session/QoS of the requested operation in the second session operation request information; such as:

taking the session/QoS in the first session operation request information capable of accepting establishment or successfully establishing as the session/QoS requested to be established in the second session operation request information;

taking the session/QoS in the first session operation request information capable of accepting modification or successfully modifying as the session/QoS requested to be modified in the second session operation request information;

taking the session/QoS in the first session operation request information capable of accepting release or successfully releasing as the session/QoS requested to be released in the second session operation request information;

optionally, the second session operation result information or the second session operation request information generated by the first node may be sent to at least one of the following: the method comprises the steps of a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer (such AS an NA layer) of the UE, a non-access layer (such AS an AS layer) of the UE, an application layer (such AS an APP layer) of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node storing a context of the UE in the light connection mode or the inactive state, a radio access network node suspending the UE, and a radio access network node requesting connection recovery of the UE.

Compared with the prior art, the first embodiment of the invention can ensure that the establishment, modification and release operations of the session/QoS flow of the UE are consistent by the wireless access network and the UE through controlling the session/QoS flow operation of the UE, avoids the core network from repeatedly generating signaling to maintain the consistency, reduces the signaling overhead, greatly improves the data transmission efficiency, greatly reduces the time delay of the UE accessing the network, and ensures the operation time delay of the session/QoS flow.

A method for controlling a session operation, comprising: the second node judges whether a preset condition is met; when the preset condition is determined to be met, the second node determines second session operation information about the User Equipment (UE); wherein the second UE session operation information includes at least one of: second session operation request information and second session operation result information; and transmitting the determined second session operation information on the UE.

Preferably, the preset condition includes at least one of: learning a session operation synchronization indication with respect to the UE; acquiring first session operation request information; acquiring first session operation result information; wherein the first session operation result information includes: operating according to the acquired first session operation request information to obtain an operation result; and/or the received session operation result information.

Preferably, the session operation synchronization indication of the UE includes: generating an indication of session operation request information for the UE; and/or generating an indication of session operation result information of the UE; the session operation synchronization indication with respect to the UE is for indicating that the session operation of the second node is the same as the operation of the session/QoS flow of the UE.

Preferably, the determining, by the second node, second session operation request information and/or second session operation result information about the user equipment UE includes: determining second session operation request information according to the operation executed on the first session operation request information; and/or determining second session operation result information according to the acquired first session operation result information and/or the operation result of the second node on the first session operation request information.

Preferably, the determining of the second session operation request information according to the operation performed on the first session operation request information specifically includes at least one of the following: determining second conversation operation request information according to the result of the operation on the first conversation operation request information and/or whether the operation requested in the first conversation operation request information can be accepted; determining second session operation request information according to the obtained session operation synchronization instruction of the UE and/or the obtained instruction for generating the session operation request information of the UE; and determining the session/QoS flow in the first session operation request information capable of accepting operation or successfully operating as the session/QoS flow requesting operation in the second session operation request information.

Preferably, the second session operation result information is determined according to the obtained first session operation result information and/or the operation result of the second node on the first session operation request information, and specifically includes at least one of the following: determining the obtained first session operation result information and the operation result of the first session operation request information on the second node to indicate the session/QoS flow with successful operation, and determining the session/QoS flow with successful operation in the second session operation result information; determining the session/QoS flow with operation failure indicated by the obtained first session operation result information as the session/QoS flow with operation failure in the second session operation result information; determining the session/QoS flow which is failed in operation and indicates the operation result of the first session operation request information on the second node as the session/QoS flow which is failed in operation in the second session operation result information; and determining second session operation result information according to operation results of the UE on the UE and the second node on the first session operation request information, and/or according to a session operation synchronization instruction of the UE, and/or an instruction for generating the session operation result information of the UE.

Preferably, the second node is at least one of: the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or in an inactive state, an old radio access network node for storing the context of the UE in the light connection mode or in the inactive state, a radio access network node for suspending the UE, and a radio access network node for requesting connection recovery of the UE; and/or

The second node sends session operation information about the UE to at least one of:

the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node for storing the context of the UE by the UE in the light connection mode or the inactive state, a radio access network node for suspending the UE, and a radio access network node for requesting connection recovery of the UE.

The technical solution of the present invention is described in detail in the form of specific embodiments below:

fig. 4 is a flowchart of a method for controlling a session operation according to a second embodiment of the present invention; step 410: the second node judges whether a preset condition is met, if so, step 420 is executed, otherwise, the operation is finished; step 420: when the preset condition is determined to be met, the second node determines second session operation information about the User Equipment (UE); wherein the second session operation information on the UE includes at least one of: second session operation request information and second session operation result information; step 430: and sending the determined session operation information about the UE.

Specifically, step 410 specifically includes: the second node determines whether a predetermined condition is satisfied.

Optionally, the predetermined condition may comprise at least one of: learning a session operation synchronization indication with respect to the UE; acquiring first session operation request information; the first session operation result information is known.

In some embodiments, the first session operation request information is learned while the operation synchronization indication is learned.

In some embodiments, the learned first session operation result information is at least one of: and the second node carries out the operation result of the operation according to the acquired first session operation request information, and the other nodes received by the second node carry out the operation result of the operation according to the first session operation request information.

Optionally, the session operation synchronization indication with respect to the UE means that the session operations of the radio access network node and the UE with respect to the UE are kept consistent. Such as a session/QoS flow for which the radio access network node fails to operate, the UE may not perform the operation of the relevant session/QoS flow; for a session/QoS flow for which the UE operation fails, the radio access network node may not perform the operation of the relevant session/QoS flow; a session/QoS flow that operates successfully is a session/QoS flow that both the radio access network and the UE operate successfully.

In some embodiments, the operation synchronization indication may further comprise one of:

-generating a session operation request information indication for the UE; the method can be used for indicating that second session operation request information is generated according to the acquired first session operation result information; in some embodiments, the learned first session operation result information may be an operation result performed by the first node according to the first session request information or received session operation result information (for example, operation result information performed by other nodes according to the first session request information). (ii) a

-generating a session operation result information indication in respect of the UE; the method can be used for indicating that second session operation request information is generated according to the acquired first session operation result information; in some embodiments, the learned first session operation result information may be an operation result performed by the first node according to the first session request information or received session operation result information (for example, operation result information performed by other nodes according to the first session request information).

For "generating the session operation request information indication about the UE", when the second node is a radio access network node, it is understood that, for a session/QoS flow for which the second node has operated successfully or can operate successfully, the second node may send an operation request of the relevant session/QoS flow to the UE; for a session/QoS flow for which the second node has failed or failed to operate successfully, the second node may not send an operation request for the relevant session/QoS flow to the UE.

For "generating the session operation result information indication about the UE", when the second node is the radio access network, it is understood that, for the session/QoS flow for which the UE and the second node have successfully operated or can successfully operate, the session/QoS flow for which the second node includes the relevant session/QoS flow and which is sent to the core network node by the second node is the session/QoS flow for which the operation is successful. And the session/QoS flow which fails to operate or cannot successfully operate on the UE or the second node is the session/QoS flow which fails to operate, and the second node sends the relevant session/QoS flow contained in the second session operation result information to the core network node.

Optionally, the second node may be at least one of: the core network, the radio access network, the gNodeB-CU, the gNodeB-DU, the UE, the radio access network node, the core network node, the data terminal node, the non-access layer (such AS the NA layer) of the UE, the non-access layer (such AS the AS layer) of the UE, the application layer (such AS the APP layer) of the UE, the CU, the DU, the core network user plane node, the core network control plane node, the source radio access network node during the movement of the UE, the target radio access network node during the movement of the UE, the new radio access network node accessed by the UE in a light connection mode or an inactive state, the old radio access network node storing the context of the UE in the light connection mode or the inactive state, the radio access network node suspending the UE, and the radio access network node requesting connection recovery of the UE.

Specifically, step 420 specifically includes: when the preset condition is determined to be met, the second node determines second session operation information about the User Equipment (UE); wherein the second session operation information on the UE comprises at least one of: second session operation request information and second session operation result information.

Specifically, the method comprises the following steps:

the second node may determine the second session operation request information from an operation performed on the first session operation request information; the operation that the second node can perform according to the first session operation request information may be an operation that the first node has completed or an operation that can be accepted.

The second node may determine the second session operation result information according to the received first session operation result information and/or an operation result on the second node for the first session operation request information.

Specifically, the second node may determine the second session operation request information according to an operation performed on the first session operation request information, and may include at least one of:

-1) the session/QoS flow in the first session operation request information that failed to be performed or refused to be performed is not operated as the session/QoS flow of the operation request in the second session operation request information; such as:

the session/QoS flow in the first session operation request information which fails to execute or refuses to execute the establishment is not taken as the session/QoS flow requested to be established in the second session operation request information;

the session/QoS flow in the first session operation request information which fails to execute or refuses to execute modification is not taken as the session/QoS flow which requests modification in the second session operation request information;

the session/QoS flow in the first session operation request information which fails to execute or refuses to execute release is not taken as the session/QoS flow requesting release in the second session operation request information;

-2) the session/QoS flow in the first session operation request information that failed to be performed or refused to be performed is not operated as the session/QoS flow requested by the release in the second session operation request information; such as:

taking the session/QoS flow in the first session operation request information which does not execute or refuse to execute modification as the session requested to be released in the second session operation request information;

-3) the session/QoS flow in the first session operation request information capable of accepting the operation or successful operation is taken as the session/QoS flow requesting the operation in the second session operation request information; such as:

taking the session/QoS in the first session operation request information capable of accepting establishment or being successfully established as the session/QoS requested to be established in the second session operation request information;

and taking the session/QoS in the first session operation request information capable of accepting release or successfully releasing as the session/QoS requested to release in the second session operation request information.

Specifically, the second node may determine the second session operation result information according to the received first session operation result information and/or the operation result of the second node on the first session operation request information, where the second session operation result information may include at least one of the following:

-1) the received first session operation result information and the operation result on the second node for the first session operation request information both indicate that the operation was successful session/QoS flow as the operation was successful session/QoS in the second session operation result information;

-2) the received first session operation result information indicates a session/QoS flow whose operation failed as a session/QoS flow whose operation failed in the second session operation result information;

-3) the operation result on the second node for the first session operation request information indicates the session/QoS flow whose operation failed as the session/QoS whose operation failed in the second session operation result information.

Optionally, the first session operation request information and the second session operation request information may have the same content as that included in the session operation request information in step 310, and are not described herein again.

Optionally, the content of the first session operation result information and the second session operation result information may be the same as the content that may be included in the session operation result information in step 310, and is not described herein again.

In some embodiments, the first/second session operation result information is a result of an operation that has been completed or a result of an operation that can be completed, wherein the result of the operation that can be completed may represent an ability to complete but not yet actually complete.

For "the second node may determine the second session operation request information based on the operation performed on the first session operation request information", in some embodiments, the second node is a radio access network node (e.g., a gNB, gNB-CU). The second node may learn the first session operation request information from NG interface signaling sent by the core network node. The second node first operates according to the session operation request of the UE or decides whether the requested operation can be accepted. And the second node generates final second session operation request information according to the session operation result of the UE on the second node. The second node may only send to the UE an operation request for a session/QoS flow for which the operation was successful or can be successful at the second node side, or may not send to the UE an operation request for a session/QoS flow for which the operation failed or cannot be accepted at the second node side. It will be understood that the operation request sent by the core network to the radio access network for the UE session does not contain NAS packets that are required to be sent to the UE. But the radio access network node is required to generate second session operation request information which is finally sent to the UE according to the operation result of the radio access network node. This ensures that the UE and the radio access network node are consistent with respect to the session operation request of the UE.

For "the second node may determine the second session operation result information according to the received first session operation result information and/or the operation result of the first session operation request information on the second node", in some embodiments, the second node is a radio access network node (e.g., a gbb-CU). The second node may learn the first session operation result information (which may be the operation result of the UE on the session operation request with respect to the UE) on the UE from an information element in an RRC message sent by the UE. And the second node generates final second session operation result information according to the session operation results of the UE side and the wireless access network side relative to the UE. Wherein, the session/QoS flow successfully operated included in the final session operation result about the UE is the session/QoS flow successfully operated at both the UE and the second node; the final session/QoS flow with operation failure included in the session operation result of the UE may be a session/QoS flow with operation failure on the UE side or operation failure on the second node side, and the UE side operation failure or the radio access network side operation failure may be distinguished by different operation failure reasons, and the second node may return the final second session operation result information to the core network. It is understood that, at this time, the session successfully operated by the second node to the core network or the QoS flow is the true successful QoS flow and session, and the UE does not need to return the NAS data packet, thereby avoiding the core network finding that the operation results of the UE and the second node are inconsistent, and avoiding the core network triggering a signaling to maintain synchronization.

Specifically, step 430 is: the second node transmits the decided session operation information on the UE.

Optionally, the second session operation information about the UE may include at least one of: second session operation request information and second session operation result information.

Optionally, the second node may send the decided session operation information about the UE to at least one of: a radio access network node, a core network node, a data terminal node, a UE, a non-access layer (e.g. NA layer) of the UE, an access layer (e.g. AS layer) of the UE, an application layer (e.g. APP layer) of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node during UE movement, a target radio access network node during UE movement, a new radio access network node to which the UE is accessed in a light connection mode or in an inactive state, an old radio access network node to which the UE saves a UE context in a light connection mode or in an inactive state, a radio access network node on which the UE is suspended, and a radio access network node to which the UE requests connection restoration.

In the following, through specific application scenarios under different situations, the above embodiments of the present invention are respectively shown and described in a more intuitive and specific manner, which is convenient for those skilled in the art to more thoroughly understand the technical solutions of the embodiments of the present invention.

The first specific application scenario of the present invention: as shown in fig. 5, fig. 5 is a schematic view of a first specific application scenario of a method for controlling a session operation of a user equipment according to the present invention.

Step 510: the UE sends a NAS packet to the AMF. In one implementation, the SMF receives the PDU session establishment request of the UE and sends the PDU session establishment request to the AMF.

Step 520: the AMF sends an NG interface PDU session resource establishment request message to the gNB (i.e., gnnodeb). Optionally, the message includes at least one of the following: session operation request information (including session information of the PDU session (PDU session 1, PDU session 2) requested to be established, NAS packets (corresponding to a plurality of PDU sessions (PDU session 1, PDU session 2)) establishment acceptance messages).

In one embodiment, the gNB can only accept the establishment of PDU session 1, but not PDU session 2.

Step 530: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS data packet, session operation result information (such as session information of a PDU session 1 that is successfully established or session information of a PDU session 2 that is failed to be established) at the gNB side, and DRB configuration related to the PDU session 1.

And the UE receives the PDU session establishment acceptance message configuration (PDU session 1, PDU session 2) indicated by the NAS data packet. The UE may only perform setup configuration on PDU session 1 according to the session operation result information on the gNB side, as described in step 320.

Step 540: and the gNB returns a PDU session establishment response message of the NG interface to the AMF. Optionally, the message may include at least one of the following: and the session operation result (such as session information of a PDU session 1 which is successfully established, session information of a PDU session 2 which is failed to be established, and a NAS data packet) of the UE returned by the gNB.

Step 550: optionally, the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: the session establishment completion message in the NAS data packet can comprise one of the following reasons, namely, the PDU session 1 is successfully established, the PDU session 2 is failed to be established, and the failure reason is the reason of the wireless access network side.

Step 560: optionally, the gNB returns an upstream NAS transport message of the NG interface to the AMF. Optionally, the message may include at least one of the following: NAS packets from the UE.

As can be seen from the above embodiments, the session operation results returned by the gNB and the UE with respect to the UE are consistent, and both are that PDU session 1 is successfully established, and PDU session 2 is unsuccessfully established.

The second specific application scenario of the present invention: as shown in fig. 6, fig. 6 is a schematic diagram of a second specific application scenario of the method for controlling session operation of the ue according to the present invention.

Step 610: the AMF sends an NG interface PDU session release request message to the gNB. Optionally, the message includes at least one of the following: session operation request information (including session information of the PDU session (PDU session 1, PDU session 2)) requesting release, NAS packets (corresponding to multiple PDU sessions (PDU session 1, PDU session 2) release requests).

In one embodiment, the gNB can only accept PDU session 1 release and not PDU session 2 release.

Step 620: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packets, session operation result information on the gbb side (for example, session information of PDU session 1 that released successfully, or session information of PDU session 2 that released failed).

And the PDU session release request indicated by the NAS data packet received by the UE indicates that the PDU session 1 and the PDU session 2 are released. The UE may perform a release operation only on PDU session 1 according to the information of the session operation result on the gbb side, as described in step 320.

Step 630: and the gNB returns a PDU session release response message of the NG interface to the AMF. Optionally, the message includes a session operation result (for example, session information of PDU session 1 that successfully releases, session information of PDU session 2 that fails to release, and an NAS packet) returned by the gNB about the UE.

Step 640: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: NAS packet, UE side session operation result information (e.g. the session information of PDU session 1 that is released successfully, and the session information of PDU session 2 that is rejected for release). The PDU conversation release response in the returned NAS data packet comprises that the UE accepts the release of the PDU conversation 1 and rejects the release of the PDU conversation 2. The gNB can know that only PDU session 1 is successfully released finally according to the session operation result information of the UE side, as described in step 320.

Step 650: optionally, the gNB returns an upstream NAS transport message of the NG interface to the AMF. Optionally, the message may include at least one of the following: NAS packets from the UE.

As can be seen from the process of the second application scenario, the session operation results returned by the gNB and the UE with respect to the UE are consistent, and both are that the release of PDU session 1 is successful, and the release of PDU session 2 is failed.

Fig. 7 shows a third specific application scenario of the present invention, and fig. 7 is a schematic diagram of the third specific application scenario of the method for controlling session operation of the ue according to the present invention.

Step 710: the AMF sends an NG interface PDU session resource modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information (such as session information for PDU sessions requested to be modified (such as PDU session 1, PDU session 2, PDU session 3)), NAS packets (corresponding to multiple PDU session (PDU session 1, PDU session 2, and PDU session 3) modification requests).

In one embodiment, the gNB can only accept PDU session 1 and PDU session 3 modifications, but not PDU session 2 modifications.

Step 720: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packets, session operation result information on the gbb side (such as session information for modifying successful PDU sessions (PDU session 1 and PDU session 3), or session information for modifying failed PDU session (PDU session 2)).

Step 730: the UE receives a PDU session modification request indicated by the NAS data packet, wherein the PDU session modification request indicates that PDU session 1, PDU session 2 and PDU session 3 are modified. The UE may perform modification operation only on PDU session 1 and PDU session 3 according to the session operation result information on the gbb side, which is specifically shown in step 320 in the first embodiment of the present invention. In one embodiment, the UE can only accept PDU session 1 modifications, but not PDU session 3 modifications.

Step 740: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes session information returned by the gNB about the session operation result of the UE (e.g., session information of a PDU session (PDU session 1) that is successfully modified, session information of a PDU session (PDU session 2, PDU session 3) that is failed to be modified, and an NAS data packet (returned by the UE).

Step 750: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: NAS packets, UE side session operation result information (such as session information of a successful PDU session (PDU session 1), session information of a rejected PDU session (PDU session 2), and/or session information of a failed PDU session (PDU session 3 and/or PDU session 2)). The PDU session modification response in the returned NAS data packet comprises that the UE accepts the modification of the PDU session 1 and rejects the modification of the PDU session 2 and the PDU session 3. The gNB can know from the session operation result information of the UE side that only PDU session 1 is successfully modified, as described in step 320.

Step 760: optionally, the gNB returns an upstream NAS transport message of the NG interface to the AMF. Optionally, the message may include at least one of the following: NAS packets from the UE.

As can be seen from the process of the third application scenario, the session operation results returned by the gNB and the UE with respect to the UE are consistent, and both PDU session 1 modification is successful, and PDU session 2 modification and PDU session 3 modification are failed.

As shown in fig. 8, a fourth specific application scenario of the present invention is a schematic diagram of the fourth specific application scenario of the method for controlling session operation of the user equipment according to the present invention in fig. 8.

Step 810: the AMF sends an NG interface PDU session modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information (such as QoS flow information for QoS flows requesting modification (such as QoS flow 1, qoS flow 2, qoS flow 3)), NAS packets (modification requests for multiple QoS flows (QoS flow 1, qoS flow 2, and QoS flow 3) in the same PDU session).

In one embodiment, the gNB can only accept the modifications for QoS flows 1 and 3, but not QoS flow 2.

Step 820: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packets, gNB side session operation result information (such as modifying QoS flow information for successful QoS flows (QoS flow 1 and QoS flow 3) and/or modifying QoS flow information for failed QoS flow (QoS flow 2)).

Step 830: the UE receives the PDU session modification request indicated by the NAS packet indicating that QoS flows 1, 2 and 3 are modified. The UE may perform the modification operation only on QoS flow 1 and QoS flow 3 according to the session operation result information on the gbb side, as described in step 320. In one embodiment, the UE can only accept the modification of QoS flow 1 and not QoS flow 3.

Step 840: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes the session operation result (such as QoS flow information of a successful QoS flow (QoS flow 1) and information of a failed QoS flow (QoS flow 2 and QoS flow 3) returned by the gNB about the UE, and the NAS packet (returned by the UE).

Step 850: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: NAS packets, UE side session operation result information (such as modify QoS flow information for successful QoS flow (QoS flow 1), reject QoS flow information for modified QoS flow (QoS flow 2), and/or modify QoS flow information for failed QoS flow (QoS flow 3 and/or QoS flow 2)). The PDU session modification response in the returned NAS data packet comprises that the UE accepts the modification of the QoS flow 1 and rejects the modification of the QoS flow 2 and the QoS flow 3. The gNB can know that only QoS flow 1 is successfully modified finally according to the session operation result information of the UE side, as described in step 320.

Step 860: optionally, the gNB returns an upstream NAS transport message of the NG interface to the AMF. Optionally, the message may include at least one of the following: NAS packets from the UE.

As can be seen from the process of the fourth application scenario, the session operation results returned by the gNB and the UE about the UE are consistent, and both QoS flow 1 modification succeeds and QoS flow 2 and QoS flow 3 modification fails.

A fifth specific application scenario of the present invention is also shown in fig. 7, but a specific operation process is slightly different from the third application scenario, and specifically includes the following steps:

step 710: the AMF sends an NG interface PDU session modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information (such as session information for PDU sessions requested to be modified (such as PDU session 1, PDU session 2, PDU session 3)), NAS packets (corresponding to multiple PDU sessions (PDU session 1, PDU session 2, and PDU session 3) modification requests). Assuming that the modification failure follow-up operations of PDU Session 1, PDU Session 2, and PDU Session 3 are all set to Release, the modification failure follow-up operations may be included in the NAS packet or NG interface PDU Session modification request message.

In one embodiment, the gNB can only accept PDU session 1 and PDU session 3 modifications, but not PDU session 2 modifications. The gNB may release resources (e.g., NG interface resources or radio resources) for PDU session 2, as depicted in step 320.

Step 720: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packets, gNB side session operation result information (such as session information of a PDU session (PDU session 1 and PDU session 3) that is successfully modified or session information of a PDU session (PDU session 2) that is failed to be modified), and gNB side session operation request information (such as session information of a PDU session (PDU session 2) that is requested to be released and/or a DRB established by the PDU session 2 that is requested to be released).

Step 730: the UE receives a PDU session modification request indicated by the NAS data packet, wherein the PDU session modification request indicates that PDU session 1, PDU session 2 and PDU session 3 are modified. The UE may modify PDU session 1 and PDU session 3 and release PDU session 2 according to the gNB side session operation result information and/or gNB side session operation request information, as described in step 320. In one embodiment, the UE can only accept the PDU session 1 modification but not the PDU session 3 modification, and then the UE can release the resources and configuration (e.g., radio resource DRB) related to PDU session 2, as shown in step 320.

Step 740: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes session information returned by the gNB about the session operation result of the UE (such as session information of PDU session (PDU session 1) that is modified successfully, session information of PDU session (PDU session 2, PDU session 3) that is modified failed or released, and a NAS packet (UE-returned).

Step 750: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: NAS packets, UE side session operation result information (such as session information for modifying a successful PDU session (PDU session 1), session information for modifying a failed PDU session (PDU session 3), and/or session information for releasing a successful PDU session (PDU session 2)), and UE side session operation request information (such as session information for requesting to release a successful PDU session (PDU session 3)). The PDU session modification response in the NAS data packet returned by the UE comprises that the UE receives the modification of the PDU session 1, and the PDU session 2 and the PDU session 3 are released. The gNB may know, according to the UE side session operation result information and/or the UE side session operation request information, that only PDU session 1 is successfully modified and the radio resource of PDU session 3 needs to be released, as described in step 320. Then, the gNB may release resources (e.g., NG interface resources or radio resources) for PDU session 3, as described in step 320.

As can be seen from the process of the fifth application scenario, the session operation results returned by the gNB and the UE about the UE are consistent, that is, the PDU session 1 is successfully modified, and the PDU session 2 and the PDU session 3 are released after the modification fails.

A sixth specific application scenario of the present invention is also shown in fig. 8, but a specific operation process is slightly different from the fourth application scenario, and specifically as follows:

in step 810, amf sends NG interface PDU session modification request message to gNB. Optionally, the message includes at least one of the following: session operation request information (such as QoS flow information for QoS flows requesting modification (such as QoS flow 1, qoS flow 2, qoS flow 3)), NAS packets (corresponding to modification requests for multiple QoS flows (QoS flow 1, qoS flow 2, and QoS flow 3) in the same PDU session). Assume that the modify failure follow-up operations for QoS flow 1, qoS flow 2 and QoS flow 3 are all set to release; the modification failure follow-up operation may be contained in a NAS packet or in a NG interface PDU session modification request message. In one embodiment, the gNB can only accept the modifications for QoS flows 1 and 3, but not QoS flow 2. The gNB may release resources (e.g., its unbound DRBs) for QoS flow 2, as depicted at step 320.

Step 820: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packets, gNB side session operation result information (such as QoS flow information of QoS flows (QoS flow 1 and QoS flow 3) that are successfully modified, and/or QoS flow information of QoS flow (QoS flow 2) that is failed to be modified)), and gNB side session operation request information (such as QoS flow information of QoS flow (QoS flow 2) that is requested to be released, and/or DRB that is requested to unbind QoS flow).

Step 830: the UE receives the PDU session modification request indicated by the NAS packet indicating modification of QoS flow 1, qoS flow 2 and QoS flow 3. The UE may perform the modification operation only on QoS flow 1 and QoS flow 3 according to the gNB side session operation result information and/or the gNB side session operation request information, as described in step 320. In one embodiment, the UE can only accept the QoS flow 1 modification and not the QoS flow 3 modification. The UE may release the resources and configuration (e.g., binding with DRB) for QoS flow 3, as depicted in step 320.

Step 840: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes the session operation result (such as QoS flow information of a QoS flow (QoS flow 1) that is successfully modified, information of a QoS flow (QoS flow 2, qoS flow 3) that is failed to be modified or released) returned by the gNB, and the NAS packet (UE-returned).

Step 850: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: NAS packets, UE side session operation result information (such as QoS flow information for modifying a successful QoS flow (QoS flow 1), qoS flow information for rejecting a modified QoS flow (QoS flow 2), qoS flow information for modifying a failed QoS flow (QoS flow 3 and/or QoS flow 2), and/or QoS flow information for a released QoS flow (QoS flow 3 and/or QoS flow 2)), and UE side session operation request information (such as QoS flow information for requesting a released QoS flow (QoS flow 3)). The returned PDU session modification response in the NAS data packet comprises the modification of the QoS flow 1 accepted by the UE, and the QoS flow 2 and the QoS flow 3 are released. The gNB may know, according to the UE side session operation result information and/or the UE side session operation request information, that only QoS flow 1 is successfully modified and the radio resource of QoS flow 3 needs to be released, as described in step 320. The gNB may release resources for QoS flow 3 (e.g., unbind QoS flow 3 from the previous DRB, which bound QoS flow no longer contains QoS flow 3), as depicted in step 320.

As can be seen from the process of the sixth application scenario, the session operation results returned by the gNB and the UE with respect to the UE are consistent, and both QoS flow 1 modification is successful, and QoS flow 2 and QoS flow 3 modification is released after failure.

As shown in fig. 9, fig. 9 is a schematic diagram of a seventh specific application scenario of a method for controlling a session operation of a user equipment according to the present invention.

Step 910: the AMF sends an NG interface PDU session modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information requesting modified PDU sessions (such as PDU session 1, PDU session 2, and PDU session 3), session operation synchronization indication with respect to the UE. In one embodiment, the gNB can only accept PDU session 1 and PDU session 3 modifications, but not PDU session 2 modifications.

Step 920: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: the gNB side session operation request information (e.g., session information of PDU session (PDU session 1)) requesting modification.

The UE may perform a modification operation on PDU session 1 and PDU session 3 according to the gNB side session operation request information, as described in step 320. In one embodiment, the UE can only accept PDU session 1 modifications and not PDU session 3 modifications.

Step 930: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: UE side session operation result information (e.g. modify the session information of the successful PDU session (PDU session 1), modify the session information of the failed PDU session (PDU session 3)). The gNB can know from the session operation result information of the UE side that only PDU session 1 is successfully modified, as described in step 410.

Step 940: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Wherein, the message includes session information returned by the gNB about the session operation result of the UE (such as the session information of the PDU session (PDU session 1) that was successfully modified, and the session information of the PDU session (PDU session 2, PDU session 3) that failed to be modified.

As can be seen from the process of the seventh application scenario, the operation between the UE and the core network may not be controlled by the NAS packet, but the gNB directly controls to keep the session operation result between the UE and the gNB with respect to the UE consistent, where the PDU session 1 modification succeeds and the PDU session 2 and PDU session 3 modification fails.

As shown in fig. 10, fig. 10 is a schematic diagram of an eighth specific application scenario of a method for controlling a session operation of a user equipment according to the present invention.

Step 1010: the AMF sends an NG interface PDU session modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information for requesting modified QoS flows (such as QoS flow 1, qoS flow 2, qoS flow 3) regarding a session operation synchronization indication of the UE.

In one embodiment, the gNB can only accept the QoS flow 1 and QoS flow 3 modifications and cannot accept the QoS flow 2 modifications.

Step 1020: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packet, gNB side session operation request information (such as QoS flow information of QoS flow (QoS flow 1 and QoS flow 3) requesting modification).

The UE may modify QoS flows 1 and 3 according to the session operation request information on the gbb side, as shown in step 320 in the first embodiment of the present invention. In one embodiment, the UE can only accept the QoS flow 1 modification and not the QoS flow 3 modification.

Step 1030: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: UE side session operation result information (such as modifying QoS flow information for a successful QoS flow (QoS flow 1) and/or modifying QoS flow information for a failed QoS flow (QoS flow 3)). The gNB can know that only QoS flow 1 is successfully modified finally according to the session operation result information of the UE side, as described in step 410.

Step 1040: and the gNB returns a PDU session modification response message of the NG interface to the AMF. The message includes the session operation result (such as QoS flow information of a successful QoS flow (QoS flow 1) and information of a failed QoS flow (QoS flow 1, qoS flow 3) returned by the gNB about the UE.

As can be seen from the process of the eighth application scenario, the operation between the UE and the core network may not be controlled by the NAS packet, but the gNB directly controls to keep the session operation result between the UE and the gNB with respect to the UE consistent, where the QoS flow 1 modification succeeds and the QoS flow 2 and QoS flow 3 modification fail.

A ninth specific application scenario of the present invention is also shown in fig. 9, but a specific operation process is slightly different from the seventh application scenario, and specifically includes the following steps:

as shown in fig. 9, fig. 9 is a schematic diagram of a ninth specific application scenario of the method for controlling session operation of user equipment according to the present invention.

In step 910, amf sends NG interface PDU session modification request message to gNB. Optionally, the message includes at least one of the following: session operation request information for requesting modified PDU sessions (e.g., PDU session 1, PDU session 2, PDU session 3), session operation synchronization indication with respect to the UE. Assume that the modify failure follow-up operations for PDU session 1, PDU session 2, and PDU session 3 are all set to release. The modification failure follow-up operation may be contained in a NAS packet or in a NG interface PDU session modification request message.

In one embodiment, the gNB can only accept the PDU session 1 and PDU session 3 modifications, but not PDU session 2 modifications. The gNB may release resources (e.g., NG interface resources or radio resources) for PDU session 2, as shown in step 320 in the first embodiment of the present invention.

Step 920: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: the session operation request information on the gNB side (for example, session information requesting modification of PDU session (PDU session 1 and PDU session 3), session information requesting release of PDU session (PDU session 2), and/or DRB requesting release of PDU session 2 establishment).

The UE may modify PDU session 1 and PDU session 3 and release PDU session 2 according to the session operation request information on the gNB side, which is specifically shown as step 320 in the first embodiment of the present invention. In one embodiment, the UE can only accept the modification of PDU session 1 but not PDU session 3, and then the UE can release the resources and configuration (e.g., radio resource DRB) related to PDU session 2, as shown in step 320.

Step 930: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: UE side session operation result information (such as modifying session information of a successful PDU session (PDU session 1), modifying session information of a failed PDU session (PDU session 3), and/or releasing session information of a successful PDU session (PDU session 2)). The gNB can know from the session operation result information of the UE side that only PDU session 1 is successfully modified and the radio resource of PDU session 3 needs to be released, as described in step 320. The gNB may release resources (e.g., NG interface resources or radio resources) for PDU session 3, as depicted in step 320.

Step 940: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes session information (such as the session information of the PDU session 1 that is successfully modified, the session information of the PDU session 2 that is failed or released) about the session operation result of the UE returned by the gNB.

As can be seen from the process of the ninth application scenario, the operation between the UE and the core network may not be controlled by the NAS packet, but the gNB directly controls to keep the session operation result between the UE and the gNB consistent with the session operation result of the UE, where the PDU session 1 is successfully modified, and the PDU session 2 and the PDU session 3 are released after the modification fails.

A tenth specific application scenario of the present invention is also shown in fig. 10, but the specific operation process is slightly different from the eighth application scenario, and specifically as follows:

in step 1010, the amf sends an NG interface PDU session modification request message to the gNB. Optionally, the message includes at least one of the following: session operation request information for requesting modified QoS flows (e.g., qoS flow 1, qoS flow 2, qoS flow 3) regarding a session operation synchronization indication of the UE. Assume that the modify failure follow-up operations for QoS flow 1, qoS flow 2 and QoS flow 3 are all set to release; the modification failure follow-up operation may be included in the NAS packet or in the NG interface PDU session modification request message. In one embodiment, the gNB can only accept the QoS flow 1 and QoS flow 3 modifications and cannot accept the QoS flow 2 modifications, and the gNB can release resources (e.g., DRBs unbundling) for QoS flow 2, as described in step 320.

Step 1020: the gNB sends an RRC message to the UE. Optionally, the message includes at least one of the following: the gNB side session operation requests information (such as QoS flow information for QoS flows requesting modification (QoS flow 1 and QoS flow 3), qoS flow information for QoS flow requesting release (QoS flow 2), and/or DRB requesting unbinding of QoS flows).

The UE may perform the modification operation only on QoS flow 1 and QoS flow 3 according to the session operation request information on the gbb side, as shown in step 320 in the first embodiment of the present invention. Wherein in one embodiment, the UE can only accept the QoS flow 1 modification and cannot accept the QoS flow 3 modification, and then the UE can release the resources and configuration (e.g., binding with DRB) for QoS flow 3, as described in step 320.

Step 1030: the UE returns an RRC message to the gNB. Optionally, the message includes at least one of the following: UE side session operation result information (such as modifying QoS flow information for a successful QoS flow (QoS flow 1), modifying QoS flow information for a failed QoS flow (QoS flow 3), and/or releasing QoS flow information for a successful QoS flow (QoS flow 2)). The gNB can know from the session operation result information of the UE side that only QoS flow 1 is successfully modified and the radio resource of QoS flow 3 needs to be released, as described in step 320. The gNB may release resources for QoS flow 3 (e.g., unbind QoS flow 3 from the previous DRB, which bound QoS flow no longer contains QoS flow 3), as depicted in step 320.

Step 1040: and the gNB returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes the session operation result (such as QoS flow information of a successful QoS flow (QoS flow 1) and information of failed or released QoS flows (QoS flow 1, qoS flow 3) returned by the gNB, and the AMF sends the corresponding session information to the SMF, and the SMF can control resource release on the CN side with respect to QoS flow 2 and QoS flow 3.

As can be seen from the process of the tenth application scenario, the operation between the UE and the core network may not be controlled by the NAS packet, but the gNB directly controls to keep the session operation result between the UE and the gNB for the UE consistent, and the QoS flow 2 and the QoS flow 3 are released after the modification fails.

The eleventh specific application scenario of the present invention: for session establishment, as shown in fig. 13, fig. 13 is a schematic diagram of an eleventh specific application scenario of a method for session operation control of a ue according to the present invention.

Step 1301: the UE sends NAS packets to an access mobility management function (AMF). Wherein, the NAS data packet comprises a session establishment request message of the N1 PDU.

Step 1302: the AMF sends a PDU session context setup request message to a Session Management Function (SMF). The message contains the NAS packet received from the UE. The operation flow between the SMF and the core network such as UDF is omitted, and in one implementation, the SMF receives the PDU session establishment request from the UE and sends the PDU session establishment request to the AMF, in step 1303.

Step 1303: the SMF sends a session context setup response message to the AMF. The message may contain NAS packets, qoS profiles/QoS requirements of QoS flows for PDU sessions. The NAS packet contains an N1 PDU session setup accept message. The N1 PDU session setup accept message may contain an authorized QoS rule for the accepted PDU session.

Step 1304: the AMF sends an NG interface PDU session resource establishment request message to the radio access network node. Optionally, the message includes at least one of the following: PDU session operation request information (including session information of the PDU session requested to be established (QoS profile/QoS parameters requirements of QoS flow 1, qoS profile/QoS parameters requirements of QoS flow 2), NAS data packet (N1 PDU session establishment accept message (such as QoS rules granted by QoS flow 1, qoS rules granted by QoS flow 2, etc.).

In one embodiment, the radio access network node can only accept the establishment of QoS flow 1 and not QoS flow 2. For example, at least one of the radio access network node may accept the QoS profile or QoS parameter requirements for QoS flow 1, may assign/map radio bearers for QoS flow 1, the radio access network node may refuse to accept the QoS profile or QoS parameter requirements for QoS flow 2, and the radio access network node may be unable to assign/map radio bearers for QoS flow 2.

Step 1305: the radio access network node sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS data packet (N1 PDU conversation establishment acceptance message (such as QoS rule authorized by QoS flow 1, qoS rule authorized by QoS flow 2, etc.), wireless access network node side conversation operation result information, and DRB configuration mapped by QoS flow 1.

The UE may perform DRB configuration according to the DRB configuration mapped by QoS flow 1 and map QoS flow 1. For QoS flow 1 accepted by the radio access network node or QoS flow 1 with mapped DRB, the UE may accept or apply QoS rules related to QoS flow 1 (which may be UE pre-configured or QoS rules for QoS flow 1 in the N1 PDU session setup accept message).

For QoS flow 2 that fails to be established by the radio access network node (e.g., qoS flow 2 rejected or not accepted by the radio access network node or QoS flow 2 without mapped DRB), the UE may perform, but is not limited to, at least one of the following (the following is only an example, and is specifically described in step 320): rejecting or not applying the QoS rules associated with the QoS flow, requesting other nodes to reject or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS rules associated with the QoS profile of the QoS flow, requesting other nodes to release and/or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS profile of the QoS flow, rejecting or not applying the QoS parameters of the QoS flow, discarding the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to discard the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, temporarily buffering the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to temporarily buffer the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, applying the default QoS rules for the data of the traffic data of the QoS flow associated with the QoS flow, reducing the QoS requirements for the QoS flow, and configuring the data of the QoS flow associated with the QoS flow.

Step 1306: and the UE returns an RRC configuration completion message to the radio access network node.

Step 1307: and the radio access network node returns a PDU session establishment response message of the NG interface to the AMF. Optionally, the message may include at least one of the following: the radio access network node performs a session operation on the UE (e.g., qoS flow information of QoS flow 1 that is successfully established, qoS flow information of QoS flow 2 that is unsuccessfully established, etc.).

Step 1308: the AMF sends a session context modification request message to the SMF. Optionally, the message may include at least one of the following: the radio access network node performs a session operation on the UE (e.g., qoS flow information of QoS flow 1 that is successfully established, qoS flow information of QoS flow 2 that is unsuccessfully established, etc.).

For QoS flow 2 that fails to establish or QoS flow 2 for which the QoS profile or QoS parameter requirements are not accepted, the smf may reject or not apply the QoS rules associated with QoS flow 2.

For QoS flow 2, smf may be performed, but is not limited to, at least one of the following (detailed in step 320): rejecting or not applying the QoS rules associated with the QoS flow, requesting other nodes to reject or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS rules associated with the QoS profile of the QoS flow, requesting other nodes to release and/or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS profile of the QoS flow, rejecting or not applying the QoS parameters of the QoS flow, discarding the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to discard the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, temporarily buffering the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to temporarily buffer the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, applying the default QoS rules for the data of the traffic data of the QoS flow associated with the QoS flow, reducing the QoS requirements for the QoS flow, and configuring the data of the QoS flow associated with the QoS flow.

Step 1309: the SMF sends a session context modification request message to the UPF. Optionally, the message may include at least one of the following: the radio access network node performs a session operation on the UE (e.g., qoS flow information of QoS flow 1 that is successfully established, qoS flow information of QoS flow 2 that is unsuccessfully established, etc.).

For QoS flows 2 that fail to establish or QoS flows 2 for which the QoS profile or QoS parameter requirements are not accepted, the upf may reject or not apply the QoS rules associated with QoS flow 2.

For QoS flow 2, upf may be performed, but is not limited to, at least one of the following (as described in detail in step 320): rejecting or not applying the QoS rules associated with the QoS flow, requesting other nodes to reject or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS rules associated with the QoS profile of the QoS flow, requesting other nodes to release and/or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS profile of the QoS flow, rejecting or not applying the QoS parameters of the QoS flow, discarding the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to discard the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, temporarily buffering the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, requesting other nodes to temporarily buffer the data of the QoS flow and/or the data of the traffic data flow associated with the QoS flow, applying the default QoS rules for the data of the traffic data of the QoS flow associated with the QoS flow, reducing the QoS requirements for the QoS flow, and configuring the data of the QoS flow associated with the QoS flow.

Step 1310: the UPF sends a session context modification response message to the SMF.

Step 1311: the SMF sends a session context modification response message to the AMF.

As can be seen from the above embodiments, the UE or core network node decides whether to accept the QoS rules for the QoS flow based on whether the radio access network node accepts the QoS profile or QoS parameters for the QoS flow.

A twelfth specific application scenario of the present invention, as shown in fig. 14, fig. 14 is a schematic diagram of a fourth specific application scenario of a method for controlling a session operation of a user equipment according to the present invention.

Step 1401: the SMF sends a session transfer message to the AMF. Optionally, the message includes at least one of the following: session operation request information (such as QoS flow information (such as QoS profile update or QoS parameter update) of a requested modified QoS flow (such as QoS flow 1, qoS flow 2)), NAS packets (modification commands (such as QoS rule update of QoS flow) of multiple QoS flows (QoS flow 1, qoS flow 2) corresponding to the same PDU session).

Step 1402: the AMF sends an NG interface PDU session modification request message to the radio access network node. Optionally, the message includes at least one of the following: session operation request information (such as QoS flow information (such as QoS profile update or QoS parameter update) of QoS flows requested to be modified (such as QoS flow 1 and QoS flow 2)), NAS packets (PDU session modification command message (modification command (such as QoS rule update of QoS flow) corresponding to a plurality of QoS flows (QoS flow 1 and QoS flow 2) in the same PDU session).

In one embodiment, the radio access network node can only accept the modification for QoS flow 1 and not QoS flow 2. For example, the radio access network node accepts the QoS profile update or QoS parameter update for QoS flow 1, may assign/map radio bearers for QoS flow 1 based on the updated QoS profile or updated QoS parameter requirements, the radio access network node rejects accepting the QoS profile or QoS parameter requirements for QoS flow 2, fails to assign/map radio bearers for QoS flow 2, and/or fails to assign/map radio bearers for QoS flow 1 for QoS2 based on the updated QoS profile or updated QoS parameter requirements.

In one embodiment, the DRB previously associated with QoS flow 1 by the radio access network node can still meet the QoS profile or QoS parameter requirements of QoS flow 1 update, i.e. the DRB associated with QoS flow 1 does not need to be updated.

Step 1403: the radio access network node sends an RRC message to the UE. Optionally, the message includes at least one of the following: NAS packet, session operation result information on the gNB side (such as QoS flow information of QoS flow 1 that is successfully modified, and/or QoS flow information of QoS flow 2 that is failed modified)).

For a radio access network node that modifies failed QoS flow 2 (e.g., an update of QoS flow 2 rejected or not accepted by the radio access network node, the radio access network cannot allocate/or map according to the update of QoS flow 2), the UE may perform, but is not limited to, at least one of the following (the following is only an example, and is specifically described in step 320): rejecting and/or releasing QoS rules updates for the QoS flow, requesting other nodes to reject and/or release QoS rules updates for the QoS flow, rejecting and/or releasing QoS rules associated with the QoS flow, requesting other nodes to reject and/or release QoS rules for the QoS flow, maintaining pre-modification QoS rules for the QoS flow, requesting other nodes to maintain pre-modification QoS rules for the QoS flow, rejecting or not applying QoS rules updates associated with updated QoS profile updates or QoS parameter updates, rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow, maintaining pre-update QoS profiles or QoS parameters for the QoS flow, maintaining a pre-update mapped radio bearer for the QoS flow, dropping data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to drop data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, temporarily caching data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to temporarily cache data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, and applying QoS profile updates for the newly added traffic data for the QoS flow, the default traffic flow, and the default QoS data for the newly added traffic flow is not configured for the QoS flow.

Step 1404: the UE sends an RRC message to the radio access network node. Optionally, the message includes a NAS packet returned by the UE, such as an N1 PDU session modification acknowledgement.

Step 1405: and the wireless access network node returns a PDU session modification response message of the NG interface to the AMF. Optionally, the message includes a session operation result (such as QoS flow information of a QoS flow 1 that is successfully modified, information of a QoS flow 2 that is failed to be modified, and a NAS packet (returned by the UE)) returned by the gNB about the UE.

Step 1406: the AMF sends a session context modification request message to the SMF. Optionally, the message may include at least one of the following: the radio access network node modifies the session of the UE according to the operation result (such as modifying the QoS flow information of the successful QoS flow 1, modifying the QoS flow information of the failed QoS flow 2, etc.).

For QoS flow 2 that fails to modify or QoS profile updates or QoS parameter requirements updates are not accepted, the smf may reject or not apply the QoS rule update associated with QoS flow 2.

For QoS flow 2, smf may perform, but is not limited to, at least one of the following (the following is merely an example, and is specifically described in step 320): rejecting and/or releasing QoS rules updates for the QoS flow, requesting other nodes to reject and/or release QoS rules updates for the QoS flow, rejecting and/or releasing QoS rules associated with the QoS flow, requesting other nodes to reject and/or release QoS rules for the QoS flow, maintaining pre-modification QoS rules for the QoS flow, requesting other nodes to maintain pre-modification QoS rules for the QoS flow, rejecting or not applying QoS rules updates associated with updated QoS profile updates or QoS parameter updates, rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow, maintaining pre-update QoS profiles or QoS parameters for the QoS flow, maintaining a pre-update mapped radio bearer for the QoS flow, dropping data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to drop data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, temporarily caching data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to temporarily cache data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, and applying QoS profile updates for the newly added traffic data for the QoS flow, the default traffic flow, and the default QoS data for the newly added traffic flow is not configured for the QoS flow.

Step 1407: the SMF sends a session context modification request message to the UPF. Optionally, the message may include at least one of the following: the result of the session operation of the radio access network node to the UE (such as modifying the QoS flow information of the successful QoS flow 1, modifying the QoS flow information of the failed QoS flow 2, etc.).

For QoS flows 2 that fail to modify or QoS profile updates or QoS parameter requirements updates are not accepted, the upf may reject or not apply QoS rule updates associated with QoS flow 2.

For QoS flow 2, upf may be performed, but is not limited to, at least one of the following (the following is merely an example, and is specifically set forth in step 320):

for QoS flow 1 rejected or not accepted by the radio access network node or QoS flow 2 of the unmapped DRB, the upf may perform, but is not limited to, at least one of the following (detailed in step 320):

rejecting and/or releasing QoS rules updates for the QoS flow, requesting other nodes to reject and/or release QoS rules updates for the QoS flow, rejecting and/or releasing QoS rules associated with the QoS flow, requesting other nodes to reject and/or release QoS rules for the QoS flow, maintaining pre-modification QoS rules for the QoS flow, requesting other nodes to maintain pre-modification QoS rules for the QoS flow, rejecting or not applying QoS rules updates associated with updated QoS profile updates or QoS parameter updates, rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow, maintaining pre-update QoS profiles or QoS parameters for the QoS flow, maintaining a pre-update mapped radio bearer for the QoS flow, dropping data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to drop data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, temporarily caching data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, requesting other nodes to temporarily cache data for a newly added traffic data flow associated with QoS rules updates for the QoS flow, and applying QoS profile updates for the newly added traffic data for the QoS flow, the default traffic flow, and the default QoS data for the newly added traffic flow is not configured for the QoS flow.

Step 1408: the UPF sends a session context modification response message to the SMF.

Step 1409: the SMF sends a session context modification response message to the AMF.

As can be seen from the above embodiments, the UE or core network node decides whether to accept the QoS rules for the QoS flow based on the QoS profile or QoS parameters of whether the radio access network node accepts the QoS flow.

As can be seen from the process of the twelfth application scenario, it can be seen from the above embodiments that the UE or the core network node decides whether to accept the QoS rule update of the QoS flow according to whether the radio access network node accepts the QoS profile update or the QoS parameter update of the QoS flow.

In a third embodiment of the present invention, there is provided a control apparatus for a conversation operation, including: an obtaining module S10 and an operating module S11, as shown in fig. 11.

An obtaining module S10, configured to obtain, by a first node, session operation information of a first UE; wherein the first UE-related session operation information includes at least one of: first session operation request information and first session operation result information;

an operation module S11, configured to determine whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE.

In a fourth embodiment of the present invention, there is provided a control apparatus for a conversation operation, including: a judging module S20, a determining module S21 and a sending module S22, as shown in fig. 12.

A judging module S20, configured to judge, by the second node, whether a preset condition is met;

a determining module S21, configured to, when it is determined that the preset condition is met, the second node determines second session operation information about the user equipment UE; wherein the second UE session operation information comprises at least one of: second session operation request information and second session operation result information;

a sending module S22, configured to send the determined second session operation information about the UE.

The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by a person skilled in the art that the scope of the invention as referred to in the present application is not limited to the embodiments with a specific combination of the above-mentioned features, but also covers other embodiments with any combination of the above-mentioned features or their equivalents without departing from the inventive concept. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.

As will be appreciated by those skilled in the art, a "terminal" as used herein includes both devices having a wireless signal receiver, which are devices having only a wireless signal receiver without transmit capability, and devices having receive and transmit hardware, which have devices having receive and transmit hardware capable of two-way communication over a two-way communication link. Such a device may include: a cellular or other communications device having a single line display or a multi-line display or a cellular or other communications device without a multi-line display; PCS (Personal Communications Service), which may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (Personal Digital Assistant), which may include a radio frequency receiver, a pager, internet/intranet access, a web browser, a notepad, a calendar and/or a GPS (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal" or "terminal device" can be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. As used herein, a "terminal Device" may also be a communication terminal, a web terminal, a music/video playing terminal, such as a PDA, an MID (Mobile Internet Device) and/or a Mobile phone with music/video playing function, or a smart tv, a set-top box, etc.

Those skilled in the art will appreciate that the present invention includes apparatus directed to performing one or more of the operations described in the present application. These devices may be specially designed and manufactured for the required purposes, or they may comprise known devices in general-purpose computers. These devices have stored within them computer programs that are selectively activated or reconfigured. Such a computer program may be stored in a device (e.g., computer) readable medium, including, but not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magnetic-optical disks, ROMs (Read-Only memories), RAMs (Random Access memories), EPROMs (Erasable Programmable Read-Only memories), EEPROMs (Electrically Erasable Programmable Read-Only memories), flash memories, magnetic cards, or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus. That is, readable media includes any medium that stores or transmits information in a form readable by a device (e.g., a computer).

It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions may be implemented by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the aspects specified in the block diagrams and/or flowchart block or blocks of the present disclosure.

Those skilled in the art will appreciate that the various operations, methods, steps, measures, arrangements of steps in the flow, which have been discussed in the present application, may be alternated, modified, combined, or eliminated. Further, various operations, methods, steps in the flows, which have been discussed in the present disclosure, may also be alternated, modified, rearranged, split, combined, or deleted. Further, steps, measures, schemes in the various operations, methods, procedures disclosed in the prior art and the present invention can also be alternated, changed, rearranged, decomposed, combined, or deleted.

The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and embellishments can be made without departing from the principle of the present invention, and these should also be construed as the scope of the present invention.

Claims

1. A method for controlling a session operation, comprising:

the first node acquires first session operation information about UE; wherein the first session operation information on the UE comprises: first session operation request information and first session operation result information; and

determining whether to accept the operation request of the session/QoS flow in the first session operation request information according to the first session operation information about the UE;

when the first node is UE, the first session operation request information includes session operation request information from a core network, and the first session operation result information includes session operation result information of the session operation request information from a radio access network to the core network.

2. The method of claim 1, further comprising, after determining whether to accept the operation request of the session/QoS flow in the first session operation request information:

generating second session operation request information; and/or

And generating second session operation result information.

3. The method according to claim 2, wherein the generating second session operation result information includes at least one of:

the session/QoS flow in the first session operation request information which is not executed or refused to be executed is used as the session/QoS flow which is failed to operate in the second session operation result information;

the session/QoS flow in the first session operation request information which can accept operation or successfully operate is used as the session/QoS successfully operated in the second session operation result information;

the session/QoS flow with failed operation in the obtained first session operation result information is used as the session/QoS flow with failed operation in the second session operation result information;

and taking the session/QoS flow which is successfully operated in the acquired first session operation result information as the session/QoS flow which is failed to operate in the second session operation result information.

4. The method according to claim 2, wherein the generating the second session operation request information specifically includes:

the session/QoS flow in the first session operation request information which does not execute or refuses to execute modification is used as the session/QoS flow of the release request in the second session operation result information;

the session/QoS flow in the first session operation request information capable of accepting an operation or a successful operation is taken as the session/QoS of the requested operation in the second session operation request information.

5. The method according to any of claims 1 to 4, wherein the first node is at least one of: the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node during the moving process of the UE, a target radio access network node during the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node for storing a context of the UE by the UE in the light connection mode or the inactive state, a radio access network node for suspending the UE and a radio access network node for requesting connection recovery of the UE.

6. The method according to any of claims 2 to 4, wherein the first session operation request information and the second session operation request information at least comprise one of the following items:

operation request information; session information for operating the associated session; operating QoS flow information of a related QoS flow; requesting session information of the established session; requesting session information for the modified session; requesting session information of the released session; requesting the QoS flow information of the established QoS flow; requesting modified QoS flow information for the QoS flow; qoS flow information of the requested released QoS flow; and/or

The first session operation result information and the second session operation result information at least comprise one of the following items: operation result information; operation information; session information for operating the associated session; operating QoS flow information of the relevant QoS flow; establishing session information of a successful session and/or establishing session information of a failed session; modifying session information of a successful session and/or modifying session information of a failed session; releasing the session information of the successful session and/or releasing the session information of the failed session; qoS flow information of the successful QoS flow is established and/or QoS flow information of the failed QoS flow is established; modifying QoS flow information of a successful QoS flow and/or modifying QoS flow information of a failed QoS flow; releasing QoS flow information for successful QoS flows and/or releasing QoS flow information for failed QoS flows.

7. The method of claim 6, wherein the operation request information comprises at least one of: request establishment; requesting modification; requesting release; modifying the subsequent operation requirement which fails; and/or

The operation result information includes at least one of: the operation is successful; the operation failed; the establishment is successful; the establishment fails; the modification is successful; the modification failed; the release is successful; the release failed; the operation can be successful; the establishment can be successful; the modification can be successful; (ii) can release failure; and/or

The QoS flow information includes at least one of: an identification of the session to which it belongs; an identification of a QoS flow; qoS profile of QoS flows; qoS flow related QoS rules; information that the QoS flow is successfully established; information of QoS flow establishment failure; information that the QoS flow modification is successful; information of QoS flow modification failure; a QoS parameter; carrying information of the configured DRB; the reason for the operation failure; modifying the subsequent operation requirement which fails; and/or

8. The method of claim 7, wherein the subsequent operation requirement for the failed modification comprises at least one of: maintaining the configuration before modification, releasing the QoS flow failed in modification, and releasing the session failed in modification; and/or

The information that the QoS flow establishment is successful at least comprises one of the following items: establishing a successful QoS flow identifier, establishing a successful QoS flow mapped wireless bearer identifier, receiving the QoS flow by the UE, receiving the QoS rule of the QoS flow by the UE, receiving the QoS flow at a non-access layer, receiving the QoS flow by a wireless access network node, distributing/mapping the QoS flow of the wireless bearer for the QoS flow by the wireless access network, receiving the QoS flow at an access layer, receiving the QoS introduction of the QoS flow by the wireless access network node, receiving the QoS parameter of the QoS flow by the wireless access network node, and establishing the QoS flow of necessary wireless resources; and/or

The information of the QoS flow establishment failure at least comprises one of the following items: establishing an identification of a failed QoS flow, the QoS flow being rejected by the UE, the QoS rules of the QoS flow being rejected by the UE, the QoS flow being rejected at a non-access layer, the QoS flow being rejected by a radio access network node, the QoS flow having no configured radio bearer, the QoS flow having no mapped radio bearer, the QoS flow being rejected at an access layer, the QoS profile of the QoS flow being rejected by a radio access network node, the QoS parameters of the QoS flow being rejected by a radio access network node, the QoS flow having no necessary radio resources being established and/or mapped; and/or

The information that the QoS flow modification is successful comprises at least one of: modifying the successful QoS flow identification, modifying the identifier of the radio bearer mapped by the successful QoS flow, accepting the QoS rule update of the QoS flow by the UE and/or the core network node, accepting the QoS profile update of the QoS flow by the radio access network node, accepting the QoS parameter update of the QoS flow by the radio access network node, allocating/mapping the radio bearer by the radio access network according to the QoS profile or QoS parameter update of the QoS flow, and establishing and/or mapping the QoS flow of the necessary radio resource according to the update; and/or

The information of QoS flow modification failure at least comprises one of the following items: modifying the failed QoS flow identification, modifying the identity of the radio bearer mapped before the failed QoS flow, the QoS rule update of the QoS flow being rejected by the UE and/or core network node, the QoS profile update of the QoS flow being rejected by the radio access network node, the QoS parameter update of the QoS flow being rejected by the radio access network node, the radio access network node being unable to allocate/map radio bearers according to the QoS profile update of the QoS flow, the radio access network being unable to allocate/map radio bearers according to the updated QoS parameters, no QoS flows having the necessary radio resources being established and/or mapped according to the update.

9. The method according to any of claims 1-4 and 7-8, wherein the session operation information of the User Equipment (UE) is obtained by any of the following:

a core network; a radio access network; a base station of 5G radio access technology, gbb; a centralized control unit gNB-CU of a base station of a 5G radio access technology; a distribution unit gNodeB-DU of a base station of a 5G radio access technology; a UE; a radio access network node; a core network node; a data termination point; a non-access stratum of the UE; an application layer of the UE; a control unit CU; a distribution unit DU; a core network user plane node; a core network control plane node; a source wireless access network node in the UE moving process; a target wireless access network node in the UE moving process; a new radio access network node accessed by the UE in a light connection mode or an inactive state; an old radio access network node where the UE context is saved by the UE in a lightly connected mode or in an inactive state; suspending a radio access network node of the UE; and the UE requests the radio access network node with the connection recovered.

10. The method according to any of claims 1-4 and 7-8, wherein determining whether to accept the operation request of session/QoS flow in the first session operation request information according to the first session operation information about UE comprises at least one of the following situations:

for the session/QoS flow which is failed to operate in the first session operation result information, the operation request of establishing the failed session/QoS flow in the first session operation request information is not executed or refused to be executed;

for the session/QoS flow successfully operated in the first session operation result information, accepting or executing the operation request of the session/QoS flow successfully operated in the first session operation request information;

a QoS flow satisfying at least one of the following conditions in the first session operation result information: the QoS flow is failed to establish, the QoS flow is failed to establish and cannot apply the default QoS rule, and the related service data in the failed QoS flow cannot apply the default QoS rule; the operation request of the QoS flow in the first session operation request information is not executed or refused to be executed, and at least one of the following items is included: rejecting or not applying the QoS rules associated with the QoS flow, requesting other nodes to reject or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS rules associated with the QoS profile of the QoS flow, requesting other nodes to release and/or not apply the QoS rules associated with the QoS flow, rejecting or not applying the QoS profile of the QoS flow, rejecting or not applying the QoS parameters of the QoS flow, discarding data of the QoS flow and/or data of a traffic data flow associated with the QoS flow, requesting other nodes to discard data of the QoS flow and/or data of a traffic data flow associated with the QoS flow, temporarily caching data of the QoS flow and/or data of a traffic data flow associated with the QoS flow, requesting other nodes to temporarily cache data of the QoS flow and/or data of a traffic data flow associated with the QoS flow, applying default QoS rules for data of a traffic data flow associated with the QoS flow, reducing the QoS requirements for the QoS flow, configuring data of the QoS flow associated with the QoS flow, and transmitting data of the QoS flow;

a QoS flow satisfying at least one of the following in the first session operation result information: the QoS flow modification fails, and the relevant new service data flow in the QoS flow with the modification failure can not apply the default QoS rule; the operation request of the QoS flow in the first session operation request information is not executed or refused to be executed, and at least one of the following items is included: rejecting and/or releasing QoS rules updates for the QoS flow, requesting other nodes to reject and/or release QoS rules updates for the QoS flow, rejecting and/or releasing QoS rules associated with the QoS flow, requesting other nodes to reject and/or release QoS rules for the QoS flow, maintaining pre-modification QoS rules for the QoS flow, requesting other nodes to maintain pre-modification QoS rules for the QoS flow, rejecting or not applying updated QoS profile updates or QoS parameter updates related QoS rule updates, rejecting or not applying QoS profile updates or QoS parameter updates for the QoS flow, maintaining pre-update QoS profiles or QoS parameters for the QoS flow, maintaining a pre-update mapped radio bearer for the QoS flow, dropping data for a newly added traffic data flow related to QoS rules updates for the QoS flow, requesting other nodes to drop data for a newly added traffic data flow related QoS rules updates for the QoS flow, temporarily caching data for a newly added traffic data flow related QoS rules update for the QoS flow, requesting other nodes to temporarily cache data for a newly added traffic data flow related QoS rules for the QoS flow, and applying default QoS profile updates for the newly added traffic data flow, the newly added traffic data for the QoS flow, and the newly added traffic flow is configured with default QoS profile updates for the QoS data for the QoS flow.

11. A method for controlling a session operation, comprising:

the second node acquires at least one item of the first session operation request information and the first session operation result information;

according to at least one item of the acquired first session operation request information and the acquired first session operation result information, the second node determines second session operation information related to the UE; wherein the second UE session operation information comprises at least one of: second session operation request information and second session operation result information; and

transmitting the determined second session operation information on the UE;

and when the second node is a wireless access network, determining second session operation request information sent to the UE according to the first session operation request information from the core network and the first session operation result information of the second node, or determining second session operation result information sent to the core network according to the first session operation result information of the UE and the first session operation result information of the second node.

12. The method of claim 11, wherein the second node is further aware of a session operation synchronization indication for the UE;

wherein the first session operation result information includes: performing operation according to the acquired first session operation request information to obtain an operation result; and/or the received session operation result information.

13. The method of claim 12, wherein the indication of synchronization of session operation of the UE comprises: generating an indication of session operation request information for the UE; and/or the presence of a gas in the gas,

generating an indication of session operation result information for the UE;

the session operation synchronization indication with respect to the UE indicates that the session operation of the second node is the same as the operation of the session/QoS flow of the UE.

14. The method according to claim 11, wherein the second node determines second session operation request information and/or second session operation result information about the UE, and comprises:

determining second session operation request information according to the operation executed on the first session operation request information; and/or the presence of a gas in the atmosphere,

and determining second session operation result information according to the acquired first session operation result information and/or the operation result of the second node on the first session operation request information.

15. The method according to claim 14, wherein the determining the second session operation request information according to the operation performed on the first session operation request information specifically includes at least one of:

determining second conversation operation request information according to the result of operating the first conversation operation request information and/or whether the operation requested in the first conversation operation request information can be accepted;

determining second session operation request information according to the obtained session operation synchronization instruction of the UE and/or the obtained instruction for generating the session operation request information of the UE;

and determining the session/QoS flow in the first session operation request information capable of accepting operation or successfully operating as the session/QoS flow requesting operation in the second session operation request information.

16. The method according to claim 14, wherein the determining, according to the obtained first session operation result information and/or the operation result of the first session operation request information at the second node, the second session operation result information specifically includes at least one of:

determining the obtained first session operation result information and the operation result of the first session operation request information on the second node to indicate the session/QoS flow with successful operation, and determining the session/QoS flow with successful operation in the second session operation result information;

determining the session/QoS flow with failed operation indicated by the obtained first session operation result information as the session/QoS flow with failed operation in the second session operation result information;

determining the session/QoS flow which has failed in operation and is indicated by the operation result of the first session operation request information on the second node as the session/QoS flow which has failed in operation in the second session operation result information;

and determining second session operation result information according to operation results of the UE on the UE and the second node on the first session operation request information, and/or according to a session operation synchronization instruction of the UE, and/or an instruction for generating the session operation result information of the UE.

17. The method according to any of claims 11 to 16, wherein the second node is at least one of:

the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or an inactive state, an old radio access network node for storing the context of the UE by the UE in the light connection mode or the inactive state, a radio access network node for suspending the UE and a radio access network node for requesting connection recovery by the UE; and/or

the system comprises a core network, a radio access network, a gNB-CU, a gNB-DU, a UE, a radio access network node, a core network node, a data terminal node, a non-access layer of the UE, an application layer of the UE, a centralized control unit CU, a distribution unit DU, a core network user plane node, a core network control plane node, a source radio access network node in the moving process of the UE, a target radio access network node in the moving process of the UE, a new radio access network node accessed by the UE in a light connection mode or in an inactive state, an old radio access network node for storing the context of the UE in the light connection mode or in the inactive state, a radio access network node for suspending the UE, and a radio access network node for requesting connection recovery of the UE.

18. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-17 when executing the program.

19. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1-17.