CN113412665B

CN113412665B - Session setting method, network equipment and user equipment

Info

Publication number: CN113412665B
Application number: CN201980091578.3A
Authority: CN
Inventors: 许阳; 杨皓睿
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-07-12
Filing date: 2019-07-12
Publication date: 2023-09-22
Anticipated expiration: 2039-07-12
Also published as: CN113412665A; WO2021007734A1

Abstract

The invention discloses a session setting method, UE, network equipment, a chip, a computer readable storage medium, a computer program product and a computer program, wherein the method comprises the following steps: transmitting at least one piece of information related to the Always-On feature to the UE; wherein the at least one related information is used for the UE to determine whether to bind traffic to a session of the Always-On feature, or to determine whether to set a PDU session to permanently open the Always-On feature, or to include a second indication for indicating the number of Always-On sessions.

Description

Session setting method, network equipment and user equipment

Technical Field

The present invention relates to the field of information processing technologies, and in particular, to a session setting method, a network device, a User Equipment (UE), a chip, a computer readable storage medium, a computer program product, and a computer program.

Background

A permanently open (Always-on) protocol data unit (PDU, protocol Data Unit) session refers to the user plane resources that must be activated each time the UE transitions from CM-IDLE state to CM-CONNECTED state. When a PDU session is set to always_on, the UE must Request to activate the PDU session every time a Service Request (Service Request) is initiated, even if no data needs to be transmitted.

However, no solution is provided for how to set the "Always-on" feature.

Disclosure of Invention

To solve the above technical problems, embodiments of the present invention provide a session setting method, a network device, a UE, a chip, a computer readable storage medium, a computer program product, and a computer program.

In a first aspect, a session setting method is provided, applied to a first network device, and includes:

transmitting at least one piece of information related to the Always-On feature to the UE;

wherein the at least one related information is used for the UE to determine whether to bind traffic to a session of the Always-On feature, or to determine whether to set a PDU session to permanently open the Always-On feature, or to include a second indication for indicating the number of Always-On sessions.

In a second aspect, a session setting method is provided, applied to a UE, including:

receiving at least one piece of information related to an Always-On feature; wherein the at least one related information is used for the UE to determine whether to bind traffic to a session of the Always-On feature, or to determine whether to set a PDU session to permanently open the Always-On feature, or to include a second indication for indicating the number of Always-On sessions.

In a third aspect, a session setting method is provided, applied to a second network device, and includes:

determining whether the PDU session of the UE is set to an Always-On feature based On PDU session related information of the UE;

upon determining that the PDU session of the UE is set to an Always-On feature, sending an indication to the UE; wherein the indication is used to inform the UE to set the PDU session to Always-On.

In a fourth aspect, there is provided a first network device comprising:

a first communication unit that transmits at least one related information to the UE;

In a fifth aspect, there is provided a UE comprising:

a second communication unit receiving at least one related information;

and a second processing unit for judging whether to bind the service to the session of the Always-On feature or whether to set the PDU session to the permanently-On feature or to include a second indication for indicating the number of Always-On sessions based On the at least one related information.

In a sixth aspect, there is provided a second network device comprising:

a third processing unit for determining whether the PDU session of the UE is set as an Always-On feature based On PDU session related information of the UE;

a third communication unit that transmits an indication to the UE when it is determined that the PDU session of the UE is set to an Always-On feature; wherein the indication is used to inform the UE to set the PDU session to Always-On.

In a seventh aspect, a session setting method is provided, applied to a UE, including:

and sending a third indication to the network side, wherein the third indication is used for indicating the number of Always-On sessions.

In an eighth aspect, there is provided a UE comprising:

and the fourth communication unit is used for sending a third indication to the network side, wherein the third indication is used for indicating the number of Always-On sessions.

In a ninth aspect, a network device is provided that includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and execute the computer program stored in the memory, to perform the method according to the first aspect, the third aspect or each implementation thereof.

In a tenth aspect, a UE is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

In an eleventh aspect, a chip is provided for implementing the method in each implementation manner.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method as in any one of the first to third aspects or implementations thereof described above.

In a twelfth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to fourth aspects or implementations thereof.

In a thirteenth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the above first to fourth aspects or implementations thereof.

In a fourteenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-described first to fourth aspects or implementations thereof.

By adopting the scheme, the UE can judge whether to bind the service to the session with the Always-On characteristic or set the PDU session as the session with the Always-On characteristic based On at least one parameter. Therefore, the services are ensured to be bound into the Always-On session in time, so that the time accuracy of the services is improved, and the reliability of the services is ensured.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application;

fig. 2-1 is a schematic flow chart of a session setting method according to an embodiment of the present application;

fig. 2-2 is a schematic flow chart of a session setting method according to the second embodiment of the present application;

fig. 3-1 is a schematic flow chart III of a session setting method according to an embodiment of the present application;

fig. 3-2 is a schematic flow chart of a session setting method according to an embodiment of the present application;

FIG. 4-1 is a UE policy acquisition procedure;

fig. 4-2 is a schematic diagram of a cause value indication location of a UE policy container;

fig. 5 is a schematic flow chart III of a session setting method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a service request processing flow;

fig. 7 is a schematic diagram of a session establishment procedure;

fig. 8 is a schematic flow chart of a session setting method according to an embodiment of the present application;

FIGS. 9-11 are schematic diagrams illustrating a process of sending a correspondence relationship in different flows according to an embodiment of the present application;

fig. 12 is a schematic flow chart of a session setting method according to an embodiment of the present application;

fig. 13 is a flowchart of a session setting method according to an embodiment of the present application;

FIGS. 14-15 are two flow diagrams for sending an indication according to an embodiment of the present application;

Fig. 16 is a schematic diagram of a first network device according to an embodiment of the present application;

fig. 17 is a schematic diagram of a UE composition structure according to an embodiment of the present application;

fig. 18 is a schematic diagram of a second network device according to an embodiment of the present application;

fig. 19 is a schematic flow diagram seventh of a session setting method according to an embodiment of the present application;

fig. 20 is a schematic diagram of another UE composition structure according to an embodiment of the present application;

fig. 21 is a schematic diagram of a communication device according to an embodiment of the present application;

FIG. 22 is a schematic block diagram of a chip provided by an embodiment of the application;

fig. 23 is a schematic diagram of a communication system architecture according to an embodiment of the present application.

Detailed Description

For a more complete understanding of the nature and the technical content of the embodiments of the present application, reference should be made to the following detailed description of embodiments of the application, taken in conjunction with the accompanying drawings, which are meant to be illustrative only and not limiting of the embodiments of the application.

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, or 5G systems, and the like.

By way of example, a communication system 100 to which embodiments of the present application may be applied may be as shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a UE120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with UEs located within that coverage area. Alternatively, the network device 110 may be a network device (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network device (NodeB, NB) in a WCDMA system, an evolved network device (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud wireless access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 also includes at least one UE120 located within the coverage area of the network device 110. "UE" as used herein includes, but is not limited to, connection via wireline, such as via public-switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of another UE arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. UEs arranged to communicate via a radio interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals".

Optionally, a direct terminal (D2D) communication may be performed between UEs 120.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

For a more complete understanding of the nature and the technical content of the embodiments of the present invention, reference should be made to the following detailed description of embodiments of the invention, taken in conjunction with the accompanying drawings, which are meant to be illustrative only and not limiting of the embodiments of the invention.

The embodiment of the invention provides a session setting method, which is applied to first network equipment, as shown in fig. 2-1, and comprises the following steps:

step 111: transmitting at least one piece of information related to the Always-On feature to the UE;

The embodiment of the invention provides a session setting method, which is applied to UE, as shown in fig. 2-2, and comprises the following steps:

step 121: receiving at least one piece of information related to an Always-On feature;

In the solution provided in this embodiment, the information related to the Always-On feature may be a parameter included in a routing identifier (RSD, route Selection Descriptors) of the first UE path selection policy (urs, UE Route Selection Policy) included in the policy container, or may be a correspondence.

The following describes the schemes provided in this embodiment in various scenarios:

scene 1,

The embodiment of the invention provides a session setting method, which is applied to first network equipment, as shown in fig. 3-1, and comprises the following steps:

step 201: sending a policy container to the UE; the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used for the UE to judge whether to bind the service to the session of the Always-On feature.

The embodiment also provides a session setting method, which is applied to the UE, as shown in fig. 3-2, and includes:

step 301: receiving a policy container; the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used for judging whether to bind the service to the session of the Always-On feature.

Step 302: the UE determines whether to bind traffic to a session of an Always-On feature based On the first indication.

Further, the method may further include: and feeding back a policy configuration result to the first network equipment.

It is first noted that the first indication is carried in the RSD in the first urs policy.

In this embodiment, the first network device may be a PCF on the network side, and the third network device may be an AMF on the network side.

The session of the Always-on feature refers to user plane resources that must be activated each time the UE transitions from CM-IDLE state to CM-CONNECTED state. The UE may set the PDU session to an Always-on PDU session in the process of requesting establishment of the PDU session (i.e., the PDU session establishment request message carries Always-on PDU Session Requested) based on an indication from an upper layer of the UE. The SMF will decide whether the session requested by the UE is established as Always-on. In roaming scenarios, the V-SMF may also participate in deciding whether the session may be set to Always-on. After the UE moves from EPS to 5GS, the UE may send a PDU session modification procedure and include an Always-on PDU Session Requested parameter to the network side SMF, requesting that the PDU session be set to an Always-on session, and the SMF has the right to decide whether it can be set to an Always-on session.

When a certain PDU session is set to Always-on, the UE must Request to activate the PDU session every time a Service Request (Service Request) is initiated, even if there is no data to send.

If a PDU session is not accepted by the network side as an Always-on session, the UE may not activate it during the Service Request when the session has no data to send

The UE policies may include an ANDSP (the ANDSP policies further include WLANSP and/or N3IWF/ePDG network element selection policies) and a urs policy. The present embodiment mainly adopts the urs policy.

As shown in fig. 4-1, the configuration method of the UE Policy may be shown in fig. 4-1, where the UE Policy is set in a Container (Container) by the PCF through a procedure of user equipment configuration update (UCU, UE Configuration Update) defined by 3GPP, and the PCF sends the updated UE Policy to the AMF, and the AMF uses NAS information to directly forward to the UE.

For UE policy configuration, a cause value of "UE policy container" has been introduced in both the downlink NAS and uplink NAS messages, as shown in fig. 4-2. Further, the bit arrangement is 4321, and the cause value is exemplified as follows: 0000, identifying N1SM information; 0010 is SMS;0011 is an LTE location protocol (LLP, LTE Positioning Protocol) information container; 0100 is SOR transparent transmission container; 0101 is a UE policy container; 0110 is a UE parameter updating transparent transmission container; 1111 is multiple load; the remaining cause value remains.

The solution provided in this embodiment will be described in detail with reference to fig. 5 on the basis of fig. 4-1, taking the first network device as PCF and the third network device as AMF as an example:

Step 0-1: UE policy is triggered by PCF, which may decide to trigger policy configuration, update or deletion based on factors such as UE initial registration, location/time change, policy change, etc.

That is, the PCF of the first network device transparently transmits the policy container to the UE through the AMF of the third network device, where the policy container carries the UE policy, and the UE policy may include the first urs policy.

The first URSP policy is used for providing an indication of whether to bind the Always-On feature for the UE, namely, the enhancement is performed On the basis of the existing URSP policy, namely, the indication information of whether to add the Always-On is added in an RSD list of the existing URSP policy.

The first urs policy and RSD list therein are described in connection with tables 1 and 2. Wherein table 1 illustrates the contents of a plurality of rules contained in the first urs policy, and table 1 is referred to as RSD list contents; table 2 shows the specific content contained in the RSD list in the first urs policy, it being noted that the RSD list has an indication of increasing Always-On:

TABLE 1

TABLE 2

In table 2, "Always-On indication" is a newly added parameter in this embodiment, through which it can be indicated whether the UE binds the application data corresponding to the service descriptor of the urs rule to the Always-On session. For example, when it is 1, it may be characterized that traffic is bound to a session with the Always-On feature, and when it is 0, it may be characterized that traffic is not bound to a session with the Always-On feature. In addition, it should be noted that, when there is a session with the Always-On feature, the service may be directly bound to the session; when there is no conversation with the Always-On feature, a new conversation with the Always-On feature can be created, and then the business is bound to the newly built conversation.

In particular, traffic Descriptor (service descriptor) in the urs rule is used to describe a specific service, for example, a microblog service may be described by a range of IP 1-9, and for example, an IMS service may be described by IMS DNN. One or more RSDs (route selectors) may then follow a service descriptor, each RSD corresponding to an attribute of a PDU session, that is to say the service data corresponding to the service descriptor may run in the PDU session corresponding to the RSD.

Step 2. After AMF receives the message of step 1, if UE is in CM-IDLE state at present, trigger the business request flow, in order to let UE return to CM-CONNECTED state and transmit the tactics container; that is, when the UE is in the idle state, the UE is switched from the idle state to the connected state based on a service request procedure triggered by a third network device (AMF).

The service request flow may be used for the UE in CM-IDLE state to send uplink signaling message, user data, or reply to a network paging request. After completing the service request procedure to activate the user plane connection, the UE enters the CM-CONNECTED state. In addition, the service request procedure is also used for the UE of CM-CONNECTED to initiate activation of unactivated user plane links (such as PDU session) and reply to NAS notification message from AMF. After the user plane connection is activated, the AS layer of the UE notifies the NAS layer.

The flow of service request is described with reference to fig. 6: the parameters that need to be carried in the first message (Service Request) message may include: AN parameters, service Request (List Of PDU SessionsTo Be Activated, list Of Allowed PDU Sessions, security parameters, PDU Session status,5G-S-TMSI, [ NAS message container ], exempt indication, wherein AN Parameter is a Parameter sent by the UE to the base station at the AS layer, such AS GUTI information, network slice information, etc., the latter Service Request is a NAS message, which is transmitted by the base station to the AMF, and is related to this patent, the List Of PDU Sessions To Be Activated Parameter is that the UE actively requests which PDU sessions to re-activate, and List Of Allowed PDU Sessions is that which PDU sessions allowed by the network side are replied after the UE (passively) receives a paging message or NAS notification message.

For 1, 2 and 4 in fig. 6, the Service Request message is transmitted to the SMF, and the SMF decides which UEs to activate List Of PDU Sessions To Be Activated through the interaction inside the network, especially the interaction between the SMF and the RAN, and returns to the UE through 11, 12 and 13 in the Service Accept message.

Step 3: and when the UE is in the CM-CONNECTED state, the message of the step 3 is sent, the PoicyContainer in the step 1 is carried, the Container does not need to be read in an AMF, and the AMF directly encapsulates the Container into a NAS message and sends the NAS message to the UE.

Step 4-5: the first network device (i.e., PCF) receives a policy configuration result carried by the UE via the policy container. Correspondingly, the UE returns the result of Policy configuration to the PCF through the message, and the same is put in the Policy Container and transmitted to the PCF.

Here, the UE also needs to bind the traffic into an Always-On feature-enabled session based On the first urs policy in the process.

The specific handling of the UE binding the traffic to the corresponding PDU session for transmission based on the urs policy can be explained as follows:

when the application layer generates data, the UE uses the URSP rules in the URSP policy to check whether the characteristics of the application data are matched with Traffic Descriptor of one rule in the URSP rules, the checking sequence is determined according to the priority in Traffic Descriptor in the URSP rules, namely, the UE checks the matching condition in sequence based on the priority sequence, and when one URSP rule is matched, the binding of PDU session is carried out by using an RSD list under the URSP rule.

When the URSP rule is matched, the UE searches for a proper PDU session according to the priority sequence in the RSD, wherein the RSD with high priority is preferentially used, and if a certain parameter in the RSD is one or more values, the UE selects one of the parameters to be combined with other parameters to search whether the PDU session exists or not:

if yes, binding the application data to the session for transmission;

if not, the UE triggers the establishment of the PDU session, and the UE reports the attribute parameters of the PDU session in the establishment request message.

If the session is established successfully, the UE binds the application data to the session for transmission; if the session establishment is unsuccessful, the UE again looks for whether a PDU session exists based on other parameter combinations in the RSD or using parameter combinations in the RSD of the secondary priority.

If no suitable PDU session can be found for binding according to the matched urs rule, the UE searches for whether Traffic Descriptor in the next-priority urs rule can match the application data flow characteristics according to the preference order, and when matching, repeats the previous procedure.

The above procedure of searching for a suitable PDU session for an application may be referred to as "evaluation", and when searching for a suitable PDU session binding, the UE may re-perform the evaluation in at least one of the following cases to see if the binding relationship between the original application data and the PDU session needs to be changed:

Updating URSP (the URSP is updated by the PCF) by PCF;

-UE moves to EPC or 5GC (the UE moves from EPC to 5 GC);

-allowed nsai or configured nsai updates (change of Allowed NSSAI or Configured NSSAI);

-LADN DNN validity update (Change of LADN DNN availability);

-the UE registering a 3GPP or non-3GPP access (UE registers over 3GPP or non-3GPP access);

-the UE establishing WLAN access (UE establishes connection to a WLAN access).

In addition, the present embodiment may further include: and receiving indication information for setting Always-On characteristics sent by the UE.

The method comprises the following steps: and receiving the indication information for setting the Always-On attribute sent by the UE in the initial session establishment process or the session modification process.

That is, the UE may carry an "Always-On" indication during the initial PDU session establishment or session modification process, and the network side may accept or reject whether the PDU session may be Always-On, which may be considered as a feature of the PDU session, and then bind the service to the session with Always-On feature by using the foregoing process flow, and then send the indication to the UE. Thus, when the established PDU session is Always-on, the subsequent UE must activate the PDU session with Always-on each time it transitions from the CM-IDLE to the CM-CONNECTED state. That is, when the UE transitions from CM-IDLE to CM-CONNECTED, the Service Request message sent carries the identity of the PDU session with the "Always-on" feature, so that the network side activates the PDU session.

For example, the foregoing session for binding services to the Always-On feature may at least include: PDU sessions for low latency high reliability services (URLLC), for Time synchronization services (Time Sync), and for partial delivery of Time sensitive services (TSN) need to be set to Always-on.

Regarding the PDU session establishment procedure, as shown in fig. 7, the PDU session establishment request message and the received reply message are the most important for the UE side.

Step 1: the PDU Session establishment Request message is sent to AMF and SMF by UE through NAS message, which can contain S-NSSAI (S), DNN, PDU Session ID, request type, old PDU Session ID, N1 SM Container (PDU Session Establishment Request), wherein SM Container is that AMF sends the Container to SMF, mainly contains Session feature related information, and UE can add "Always-on is requested" mark to instruct SMF to establish Always-on PDU Session.

Step 2: the AMF selects the SMF based on the NAS message sent by the UE, and sends the N1 NAS Container of the NAS message in the step one to the SMF.

Step 3-10, SMF decides whether to establish the PDU session based on NAS message from UE, subscription information, dynamic or local static policy (detailed procedure is omitted because it is an internal behavior of network side)

Step 11-13: the SMF sends a message to the RAN, which mainly contains parameters of N1 SM Container (PDU Session Establishment Accept ([ QoS Rule (S) and QoS Flow level QoS parameters if needed for the QoS Flow (S) associated with the QoS Rule (S), N2 SM Information (PDU Session ID, QFI (S), qoS Profile (S)), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, session-AMBR, PDU Session Type, user Plane Security Enforcement Information, UE Integrity Protection Maximum Data Rate, RSN), [ Always-on PDU Session Granted ], selected SSC mode, S-NSSAI (S), DNN, assigned IPv4 address, interface identifier, session-AMBR, selected PDU Session Type, [ Reflective QoS Timer ] (if available), [ P-CSCF address (es) ], [ Control Plane Only indicator ], [ Header Compression Configuration ], etc. whereby the RAN sends N1 SM available to the UE, N2 SM Information is used by itself for establishment of an air interface bearer, and other parameters such as [ Always-on PDU Session Granted ] parameters are also sent to the UE.

Furthermore, if the UE does not request Always-On in PDU Session Establishment Request, the SMF may decide to set Always-On, so that [ Always-On PDU Session Granted ] (Always-On PDU session grant) is added in PDU back Session Establishment Accept (session establishment accept) message.

Finally, in this embodiment, it should be noted that, in this embodiment, binding of the Always-On feature of the session is aimed at, but in actual processing, there may be binding of other more features or binding of more attributes, and the adopted processing manner may be the same as that of the foregoing scheme, which is not exhaustive in this embodiment. In addition, several services bound to the session of the Always-On feature are exemplified in the present embodiment, but the present embodiment can be applied to any other determination that can open the session of the Always-On feature, which is not exhaustive in the present embodiment.

In addition, the scheme provided by the embodiment may further include: the first network device sends a second indication to the UE indicating the number of Always-On sessions. Because of capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication for indicating the number of Always-On sessions, i.e. "Always-On session number indication", is introduced, which can be sent by the network side to the UE, and accordingly the UE decides the number of PDU sessions of the Always-On feature that can be requested according to the second indication.

In addition, a third indication for indicating the number of Always-On sessions can be sent to the first network equipment for the UE; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received.

And 2, configuring a corresponding relation for the UE.

As shown in fig. 8, in particular:

step 401: the UE receiving at least one parameter related to a PDU session;

step 402: based On the at least one parameter associated with the PDU session and the correspondence, it is determined to set the PDU session to a permanently-On Always-On feature.

The UE receives URSP rules; the UE may then determine whether to set the PDU session to the Always-On feature based On network slice parameters (NSSAI) and/or DNN parameters of the RSD list in the urs rules configured at the network side.

The corresponding relation is as follows: a first correspondence;

wherein, the first corresponding relation is the corresponding relation between at least one parameter in PDU conversation attribute and Always-On characteristic;

or the first corresponding relation is the corresponding relation between at least one parameter in the PDU session attribute and the first type of service; the first type of service is a service capable of setting an Always-On feature session.

The at least one parameter of the PDU session attribute may be one or more parameters in RSD in the urs p rule.

That is, the UE may match at least one parameter specified in the urs rule with the first correspondence according to a plurality of parameters included in the RSD list received in the urs rule, and when the at least one parameter specified in the first correspondence matches, it may determine that the first correspondence is satisfied, and further determine that the PDU session may be set as an Always-On feature according to the first correspondence.

Or, the UE may match at least one parameter specified in the urs rule according to the received multiple parameters included in the RSD list in the urs rule, and when the multiple parameters match with at least one parameter specified in the first correspondence, the UE may determine that the first correspondence is satisfied, and further determine that the PDU session is a PDU session of a first type of service according to the first correspondence, and may set the PDU session of the first type of service as an Always-On feature.

The at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.

For example, when the UE receives the urs rule and takes the parameters in the urs rule as parameters of the PDU session attribute, and when the RSD in the urs rule-1 includes a specific S-NSSAI-1 and/or DNN-1, the UE determines that the session is to execute a specific service (such as urs service) according to a first correspondence (for example, a correspondence between S-NSSAI-1 and/or DNN-1 and an alwass-On feature, or a correspondence between S-NSSAI-2 and/or DNN-2 and a first type service), whether the PDU session to be bound is an alwass-On feature, or directly determines whether the PDU session to be bound to alwass-On is needed.

Further, in this example, with respect to binding traffic to a PDU session, it may be understood that specific data is transmitted on a specific PDU session. For example, application 1 binds to PDU session 1, then data for application 1 is indicated for transmission in PDU session 1.

The first corresponding relation (namely, the corresponding relation between the S-NSSAI and/or DNN and the Always-on attribute or the corresponding relation between the S-NSSAI and/or DNN and the service) can be dynamically sent to the terminal through the network side or can be statically configured at the terminal.

For dynamic sending to the terminal, the following manner may be selected: the first correspondence transmitted through the UCU message is received, or the first correspondence transmitted through the registration reply message is received. Specifically:

mode 1: the UCU message is sent according to UCU information, and the UCU information can be AMF triggered UCU information or PCF triggered UCU information.

For example, as shown in fig. 9, when the AMF (i.e., the third network device) sends a configuration update instruction to the UE, the AMF carries the first correspondence relationship; and the UE sends the UE configuration update completion to the AMF, and the AMD sends related information to the UMD and updates the RAN.

For another example, as shown in fig. 10, the information sent to the AMF by the PCF carries a first correspondence, and then the AMF triggers the service request flow, so that the UE enters a connection state, and transmits a UE policy container to the UE, where the policy container carries the first correspondence; and the UE performs subsequent processing based on the first corresponding relation.

Mode 2: and sending the registration reply message to the terminal. As shown in fig. 11, the registration procedure has been described previously and will not be repeated here. In the flow shown in fig. 11, the AMF carries the first correspondence relationship in the information received by the feedback registration of the AMF to the UE.

The other processing mode is as follows: the UE receives QoS parameters.

The UE decides to set to Always-on according to the configured QoS information after establishing the PDU session.

The present example differs from the previous example in that it sends a PDU session establishment request message, and the receiving network side carries the QoS parameter in the PDU session establishment request reply message. That is, after the UE makes the session establishment request, the UE receives the QoS information sent by the network side, and further determines whether to set the PDU session as the session with the Always-On feature according to the QoS parameter and the second correspondence. Namely, the UE transmits a PDU session establishment request message; and thus receives QoS parameters associated with the PDU session.

In this example, the correspondence relationship is: a second correspondence;

wherein the second corresponding relation is a corresponding relation between at least one parameter in QoS parameters and the first type of service;

or, the second correspondence is a correspondence between at least one parameter of the QoS parameters and the Always-On feature.

The UE is matched with the second corresponding relation according to the received QoS parameter, and when the QoS parameter is matched with the second corresponding relation, the PDU session can be determined to be set to be an Always-On feature based On the second corresponding relation; or when the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the first type of service, the matching can be performed according to the content contained in the received QoS parameters and the parameters contained in the second corresponding relation, and when the matching is performed, the PDU session can be determined to be the session of the first type of service, and then the PDU session is determined to be required to be set with the Always-On feature.

In addition, the UE may send a first request to set the PDU session to the Always-On feature through a session modification request message when it is determined to set the PDU session to the Always-On feature; and further receiving feedback information for the first request, determining whether to set the PDU session to an Always-On feature based On the feedback information.

As shown in fig. 12, it is determined whether the session needs to be set to Always-on according to the PDU session establishment request message transmitted by the UE and the received QoS information, and if necessary, the UE sets the session to Always-on in the process of initiating PDU session modification.

The second correspondence management may be understood as QoS rules, and the SMF will send out the QoS rules that need to be sent to the UE through NAS messages in the PDU session establishment procedure shown in fig. 7 through steps 11, 12 and 13. That is, in step 11, the SMF transmits the N1 SM Container to the AMF, where the Container contains PDU Session Establishment Accept ([ QoS Rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS Rule(s) ]. Here, the QoS parameter (i.e., qoS parameter) is used to describe the QoS Flow characteristics in the PDU session, including 5QI, ARP, RQA, aggregate Bit Rates, notification control, stream bit rate, maximum Packet Loss Rate, etc., or derive static QoS parameters at the UE itself according to the message replied by the SMF.

In addition to the PDU session establishment procedure, the UE may acquire new QoS parameters and QoS rules or update its existing QoS parameters and QoS rules in the PDU session modification procedure, and then the UE may decide whether to set the PDU session to Always-on according to the new QoS parameters and QoS rules.

For example, an eMBB application corresponding to 5 qi=80, so the UE may decide that the session needs to be set to Always-on according to a specific 5QI value (e.g. 5 qi=80). For another example, qoS flows of 5 qi=82-85 require Delay Critical GBR, and the UE may consider PDU session where a data flow of Delay Critical GBR occurs to be set to Always-on.

/>

TABLE 3 Table 3

The above example is a process based On 5QI, and other parameters of QoS parameters may be actually used, such as a stream bit rate, a maximum packet loss rate (Maximum Packet Loss Rate), and the like, for example, a second correspondence between bit rate-1 and Always-On characteristics may be set, or a second correspondence between packet loss rate and Always-On characteristics (or first class traffic) within a certain range may be set.

When the UE decides to set the PDU session to Always-on according to the received QoS parameters, the UE initiates a PDU session modification procedure, and according to the existing procedure, the UE adds an "Always-on is request" parameter in the PDU session modification request message, requests the network side to set it to Always-on session, and the network side can decide whether to set it to Always-on.

In addition, the scheme provided by the embodiment may further include: the UE receives a second indication indicating a number of Always-On sessions. Because of capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication for indicating the number of Always-On sessions, i.e. "Always-On session number indication", is introduced, which can be sent by the network side to the UE, and accordingly the UE decides the number of PDU sessions of the Always-On feature that can be requested according to the second indication. The network side may be a second network device, a first network device, or a third network device, that is, may be PCF, AMF, or SMF, which is not limited in this embodiment.

In addition, a third indication for indicating the number of Always-On sessions can be sent to the UE; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Likewise, the network side may specifically be PCF, AMF or SMF.

It can be seen that by adopting the above scheme, it can be determined by the UE whether to set the PDU session as the Always-On feature according to the correspondence. Therefore, the conversation of the business is timely bound to the Always-On conversation, so that the time accuracy of the business is improved, and the reliability of the business is ensured.

The embodiment of the invention also provides a session setting method, which is applied to the second network device, as shown in fig. 13, and includes:

step 501: determining whether the PDU session of the UE is set to an Always-On feature based On PDU session related information of the UE;

step 502: upon determining that the PDU session of the UE is set to an Always-On feature, sending an indication to the UE; wherein the indication is used to inform the UE to set the PDU session to Always-On.

The second network device in this embodiment may be an SMF.

The PDU session related information of the UE in this embodiment includes at least one of the following:

session establishment parameters reported by the UE, user subscription information corresponding to the UE, PCC strategy and local configuration.

Accordingly, the SMF may determine whether to set the session to Always-on according to session establishment parameters such as S-nsai and DNN reported by the UE, subscription information of the user, PCC policy, local configuration, and the like. That is, even if the UE does not indicate that the request message needs to be set to Always-on, the SMF may still set to Always-on for its decision, so that the network side has enough capability to determine, and does not need to send to the UE to determine.

Specifically, the manner in which the network side second network device (SMF) sends the indication to the UE may have the following multiple processing manners:

In a first mode, as shown in fig. 14, a UE initiates a session establishment request to a second network device, i.e. an SMF, and after the SMF decides to set to aware-on, sends a session establishment reply message carrying a first indication to the UE; wherein the first indication is for instructing the UE to set a PDU session to an Always-On feature.

And after the first indication is sent, receiving an Always-on PDU session request identifier carried by the UE in a PDU session modification request message. For example, as shown in the figure, the session establishment reply message carries a first indication, after the UE receives the first indication, the UE initiates a PDU session modification procedure to carry an alwass-on is requested indication, and the SMF agrees that the PDU session is set to alwass-on according to the existing procedure.

It should be noted that the foregoing embodiments have been described with respect to detailed PDU session establishment and modification procedures, and are not repeated here.

A second mode is that a notification message is sent to the UE, wherein the notification message carries a first parameter; wherein the first parameter includes an identification of whether an Always-On session needs to be established and/or whether an Always-On session needs to be established. That is, the network side SMF informs the terminal that the UE is required to set the session to Always-on through a separate message

Wherein, the notification message is: a proprietary NAS message, or a paging message.

As shown in fig. 15, the network side sends a notification message including a "first parameter", where the notification message may be a proprietary NAS message or a paging message, and the "first parameter" includes: whether an Always-on session needs to be established and/or an identity of an Always-on session needs to be established.

Then, it may also include that the UE initiates a PDU session modification procedure carrying an "Always-on is requested indication", and that the SMF agrees again that the PDU session is set to Always-on according to the existing procedure.

In this embodiment, the PDU session may be a PDU session of a URLLC or TSN service, and of course, other services may also be used, so long as the services that need to set the session characteristics of Always-On may be included in the protection scope of this embodiment. And are not exhaustive.

Thus, for an important TSN Time synchronization service, if the TSN Time synchronization service cannot be set to Always-on in Time, an important effect is caused on Time accuracy, for example, when the UE changes from an idle state to a connected state, long-Time non-Time synchronization needs to be performed immediately, so that the network side can adjust the offset Time of the clock on the network element in Time.

For URLLC traffic, industry scenarios are more used, and must be set to Always-on to deliver data in time, otherwise a highly reliable specification would not be achievable due to the inactivity of certain sessions.

In addition, the scheme provided by the embodiment may further include: the second network device sends a second indication to the UE indicating the number of Always-On sessions. Because of capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication for indicating the number of Always-On sessions, i.e. "Always-On session number indication", is introduced, which can be sent by the network side to the UE, and accordingly the UE decides the number of PDU sessions of the Always-On feature that can be requested according to the second indication. Wherein the network side may be a second network device SMF of the network side.

In addition, a third indication sent by the UE and used for indicating the number of Always-On sessions can be received for the second network equipment; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Likewise, the network side may specifically be SMF.

By adopting the scheme, the network side can determine whether the session can be set as an Always-On feature according to PDU session related information of the UE. Therefore, the conversation of the business is timely bound to the Always-On conversation, so that the time accuracy of the business is improved, and the reliability of the business is ensured.

An embodiment of the present invention provides a first network device, as shown in fig. 16, including:

a first communication unit 61 that transmits at least one piece of related information to the UE;

The present embodiment also provides a UE, as shown in fig. 17, including:

a second communication unit 71 that receives at least one piece of related information;

the second processing unit 72 determines, based On the at least one related information, whether to bind the service to the session of the Always-On feature, or to set the PDU session to permanently open the Always-On feature, or to include a second indication indicating the number of Always-On sessions.

In the solution provided in this embodiment, the at least one parameter may be a parameter included in the RSD of the first urs policy included in the policy container, or may be at least one parameter related to the PDU session, or may be a QoS parameter.

scene 1,

A first communication unit 61 of the first network device, which sends a policy container to the UE; the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used for assisting the UE to judge whether to bind the service to the session of the Always-On feature.

Correspondingly, the second communication unit 71 at the UE side receives the policy container sent by the first network device; the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used for assisting the UE to judge whether to bind the service to the session of the Always-On feature.

Taking the first network device as PCF and the third network device as AMF as an example, the scheme provided in this embodiment is described in detail:

UE policy is triggered by PCF, which may decide to trigger policy configuration, update or deletion based on factors such as UE initial registration, location/time change, policy change, etc.

That is, the first communication unit 61 of the first network device PCF transparently transmits the policy container to the UE through the third network device AMF, where the policy container carries the UE policy, and the UE policy may include the first urs policy.

If the UE is in the CM-IDLE state, the third network device triggers the service request flow so as to enable the UE to return to the CM-CONNECTED state to transfer the policy container;

the UE further includes: the second processing unit 72, when in the idle state, switches from the idle state to the connected state based on a service request flow triggered by the third network device (AMF).

In the CM-CONNECTED state, AMF directly encapsulates the Container into NAS message and sends the NAS message to the UE.

The first communication unit 61 of the first network device (i.e. PCF) receives the policy configuration result carried by the UE through the policy container. Correspondingly, the second communication unit 71 of the UE returns the result of Policy configuration to the PCF through the message, and the same applies the result of Policy Container to the PCF.

The first communication unit 61 of the first network device receives the indication information of setting the Always-On attribute transmitted by the UE in the initial session establishment procedure or the session modification procedure.

The embodiment aims at binding of the Always-On feature of the session, but in actual processing, there may be other binding of more features or binding of more attributes, and the adopted processing manner may be the same as that of the foregoing scheme, which is not exhaustive in the embodiment. In addition, several services bound to the session of the Always-On feature are exemplified in the present embodiment, but the present embodiment can be applied to any other determination that can open the session of the Always-On feature, which is not exhaustive in the present embodiment.

In addition, the functions of each unit in this embodiment are the same as the processing flow in the foregoing method embodiment, and will not be described in detail.

In addition, the scheme provided by the embodiment may further include: the first communication unit of the first network device sends a second indication to the second communication unit of the UE indicating the number of Always-On sessions. Because of capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication for indicating the number of Always-On sessions, i.e. "Always-On session number indication", is introduced, which can be sent by the network side to the UE, and accordingly the UE decides the number of PDU sessions of the Always-On feature that can be requested according to the second indication.

In addition, a third indication for indicating the number of Always-On sessions can be sent to the first network equipment for the second communication unit of the UE; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received.

Scene 2,

A second communication unit 71 receiving at least one parameter related to a PDU session;

the second processing unit 72 determines to set the PDU session to the permanently On Always-On feature based On the at least one parameter related to the PDU session and the correspondence.

A second communication unit 71 that receives the urs rules; the UE may then determine whether to set the PDU session to the Always-On feature based On network slice parameters (NSSAI) and/or DNN parameters of the RSD list in the urs rules configured at the network side.

The corresponding relation is as follows: a first correspondence;

That is, the second processing unit 72 of the UE may match at least one parameter specified in the urs rule according to the received multiple parameters included in the RSD list in the urs rule, and when matching with at least one parameter specified in the first correspondence, may determine that the first correspondence is satisfied, and further determine that the PDU session can be set as an Always-On feature according to the first correspondence.

Or, the second processing unit 72 of the UE may match at least one parameter specified in the urs rule according to the received multiple parameters included in the RSD list in the urs rule, and when the multiple parameters match with at least one parameter specified in the first correspondence, the second processing unit may determine that the first correspondence is satisfied, and further determine that the PDU session is a PDU session of the first type of service according to the first correspondence, and may set the PDU session of the first type of service as an Always-On feature.

For dynamic sending to the terminal, the following manner may be selected: the second communication unit 71 receives the first correspondence transmitted through the UCU message, or the second communication unit 71 receives the first correspondence transmitted through the registration reply message.

There is another way for the UE to decide to set to Always-on based on configured QoS information after establishing the PDU session.

The present example differs from the foregoing example in that the second communication unit 71 of the present example transmits a PDU session establishment request message, and receives the QoS parameter carried by the network side in the PDU session establishment request reply message. That is, after the UE makes the session establishment request, the UE receives the QoS information sent by the network side, and further determines whether to set the PDU session as the session with the Always-On feature according to the QoS parameter and the second correspondence. Namely, the UE transmits a PDU session establishment request message; and thus receives QoS parameters associated with the PDU session.

In this example, the correspondence relationship is: a second correspondence;

wherein the second corresponding relation is a corresponding relation between at least one parameter in QoS parameters and the first type of service; or, the second correspondence is a correspondence between at least one parameter of the QoS parameters and the Always-On feature.

The second processing unit of the UE matches the second corresponding relation according to the received QoS parameter, and when the QoS parameter matches the second corresponding relation, the PDU session can be determined to be set as an Always-On feature based On the second corresponding relation; or when the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the first type of service, the matching can be performed according to the content contained in the received QoS parameters and the parameters contained in the second corresponding relation, and when the matching is performed, the PDU session can be determined to be the session of the first type of service, and then the PDU session is determined to be required to be set with the Always-On feature.

In addition, the UE may transmit a first request to set the PDU session to the Always-On feature through a session modification request message by the second communication unit 71 upon determining to set the PDU session to the Always-On feature; and further receiving feedback information for the first request, determining whether to set the PDU session to an Always-On feature based On the feedback information.

In addition, the scheme provided by the embodiment may further include: the second communication unit of the UE receives a second indication indicating a number of Always-On sessions. Due to capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication, i.e. "always_on session number indication", for indicating the number of Always-On sessions is introduced, which can be sent by the network side to the UE, and correspondingly, the second processing unit of the UE can also decide the number of PDU sessions of Always-On characteristics that can be requested based On the second indication. The network side may be a second network device, a first network device, or a third network device, that is, may be PCF, AMF, or SMF, which is not limited in this embodiment.

In addition, a third indication for indicating the number of Always-On sessions can be sent to the second communication unit of the UE; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Likewise, the network side may specifically be PCF, AMF or SMF.

The embodiment of the invention also provides a second network device, as shown in fig. 18, including:

a third processing unit 82 that determines whether the PDU session of the UE is set to an Always-On feature based On PDU session related information of the UE;

a third communication unit 81 that transmits an indication to the UE when it is determined that the PDU session of the UE is set to an Always-On feature; wherein the indication is used to inform the UE to set the PDU session to Always-On.

The second network device in this embodiment may be an SMF.

Correspondingly, the third processing unit 82 of the SMF may determine whether to set the session to Always-on according to session establishment parameters such as S-nsai and DNN reported by the UE, subscription information of the user, PCC policy, local configuration, and the like. That is, even if the UE does not indicate that the request message needs to be set to Always-on, the SMF may still set to Always-on for its decision, so that the network side has enough capability to determine, and does not need to send to the UE to determine.

in the first mode, after the third communication unit 81 receives a session establishment request initiated by the UE to the second network device, i.e., the SMF, and the third processing unit of the SMF decides to set to Always-on, a session establishment reply message carrying a first indication is sent to the UE through the third communication unit 81; wherein the first indication is for instructing the UE to set a PDU session to an Always-On feature.

After sending the first indication, the third communication unit 81 receives an Always-on PDU session request identifier carried by the UE in the PDU session modification request message.

The second mode and the third communication unit 81 send a notification message to the UE, where the notification message carries a first parameter; wherein the first parameter includes an identification of whether an Always-On session needs to be established and/or whether an Always-On session needs to be established. That is, the network side SMF informs the terminal that the UE is required to set the session to Always-on through a separate message

In addition, the scheme provided by the embodiment may further include: the third communication unit of the second network device sends a second indication to the UE indicating the number of Always-On sessions. Because of capability handling limitations On the UE or network side, such as the possibility that the UE or network side can only activate a specific number of PDU sessions simultaneously in one Service Request (Service Request) message, a second indication for indicating the number of Always-On sessions, i.e. "Always-On session number indication", is introduced, which can be sent by the network side to the UE, and accordingly the UE decides the number of PDU sessions of the Always-On feature that can be requested according to the second indication. Wherein the network side may be a second network device SMF of the network side.

In addition, a third communication unit of the second network device may also receive a third indication sent by the UE and used for indicating the number of Always-On sessions; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Likewise, the network side may specifically be SMF.

The session setting method provided by the embodiment of the invention is applied to the UE, as shown in fig. 19, and may include:

step 1001: and sending a third indication to the network side, wherein the third indication is used for indicating the number of Always-On sessions.

In addition, the first network device or the second network device or the third network device on the network side may receive the third indication sent by the UE.

Correspondingly, as shown in fig. 20, a UE provided in an embodiment of the present invention includes:

The fourth communication unit 91 sends a third indication to the network side, where the third indication is used to indicate the number of Always-On sessions.

For example, the second network device, or the first network device, or the third network device receives a third indication sent by the UE for indicating the number of Always-On sessions; that is, the indication may also be sent by the UE to the network side, from which the network side may decide the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Likewise, the network side may specifically be one of AMF, PCF, SMF.

Fig. 21 is a schematic block diagram of a communication device 1900 according to an embodiment of the present invention, where the communication device in this embodiment may be specifically a network device or a UE in the foregoing embodiment. The communications device 1900 shown in fig. 21 includes a processor 1910, and the processor 1910 may call and run a computer program from memory to implement the methods in embodiments of the present invention.

Optionally, as shown in fig. 21, the communications device 1900 may also include a memory 1920. Wherein the processor 1910 may call and run computer programs from the memory 1920 to implement the methods in embodiments of the present invention.

Wherein the memory 1920 may be a separate device from the processor 1910 or may be integrated within the processor 1910.

Optionally, as shown in fig. 21, the communication device 1900 may further include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices, and in particular, may transmit information or data to other devices, or receive information or data transmitted by other devices.

Among other things, transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include antennas, the number of which may be one or more.

Optionally, the communication device 1900 may be specifically a network device or a UE according to an embodiment of the present invention, and the communication device 1900 may implement a corresponding flow implemented by the network device in each method according to the embodiment of the present invention, which is not described herein for brevity.

Optionally, the communication device 1900 may be specifically a network device or a UE according to an embodiment of the present invention, and the communication device 1900 may implement corresponding flows implemented by a mobile terminal/terminal device in each method according to an embodiment of the present invention, which are not described herein for brevity.

Fig. 22 is a schematic structural view of a chip of an embodiment of the present invention. The chip 2000 illustrated in fig. 22 includes a processor 2010, and the processor 2010 may call and execute a computer program from a memory to implement the method in the embodiment of the present invention.

Optionally, as shown in fig. 22, chip 2000 may also include memory 2020. Wherein the processor 2010 may invoke and run a computer program from the memory 2020 to implement the method in embodiments of the present invention.

Wherein the memory 2020 may be a separate device from the processor 2010 or may be integrated in the processor 2010.

Optionally, the chip 2000 may also include an input interface 2030. Processor 2010 may control input interface 2030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 2000 may also include an output interface 2040. Processor 2010 may control the output interface 2040 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to a network device or UE in the embodiment of the present invention, and the chip may implement a corresponding flow implemented by a terminal device in each method in the embodiment of the present invention, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present invention may also be referred to as system-on-chip chips, or the like.

It should be appreciated that the processor of an embodiment of the present invention may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present invention may be implemented or performed.

It will be appreciated that the memory in embodiments of the invention may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 23 is a schematic block diagram of a communication system 2100 provided by an embodiment of the present application. As shown in fig. 23, the communication system 2100 includes a UE2110 and a network device 2120.

The UE2110 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 2120 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

The embodiment of the invention also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device or UE in the embodiment of the present invention, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present invention, which is not described herein for brevity.

The embodiment of the invention also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device or UE in the embodiment of the present invention, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present invention, which are not described herein for brevity.

The embodiment of the invention also provides a computer program.

Optionally, the computer program may be applied to a network device or UE in the embodiment of the present invention, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present invention, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A session setting method is applied to a first network device and comprises the following steps:

wherein the at least one related information is used for the UE to determine whether to bind the service to the session of the Always-On feature or comprises a second indication for indicating the number of Always-On sessions;

the sending at least one piece of information related to the Always-On feature to the UE includes:

sending a policy container to the UE; the policy container carries a first URSP policy; a first indication of whether to add Always-On is added to the RSD list of the first urs policy, and the first indication is used for the UE to determine whether to bind the service to the session of the Always-On feature.

2. The method of claim 1, wherein the sending a policy container to a UE further comprises:

and transmitting the policy container to the UE through third network equipment.

3. The method according to claim 1 or 2, wherein the method further comprises:

and receiving a strategy configuration result carried by the UE through the strategy container.

4. The method of claim 1, wherein the method further comprises:

and receiving indication information for setting Always-On characteristics sent by the UE.

5. The method of claim 4, wherein the receiving the indication information sent by the UE to set the Always-On feature comprises:

and receiving the indication information for setting the Always-On characteristic sent by the UE in the initial session establishment process or the session modification process.

6. The method of claim 1, wherein the method further comprises:

and configuring a corresponding relation for the UE.

7. The method of claim 6, wherein the correspondence is: a first correspondence;

8. The method of claim 7, wherein the at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.

9. The method of claim 6, wherein the method further comprises:

and transmitting the QoS parameters.

10. The method of claim 9, wherein the correspondence is: a second correspondence;

11. The method according to claim 1 or 2, wherein the method further comprises:

and receiving a third indication sent by the UE and used for indicating the number of the Always-On sessions.

12. A session setting method, applied to a UE, comprising:

receiving at least one piece of information related to an Always-On feature; wherein the at least one related information is used for the UE to determine whether to bind the service to the session of the Always-On feature or comprises a second indication for indicating the number of Always-On sessions;

wherein said receiving at least one information related to an Always-On feature comprises:

Receiving a policy container; the policy container carries a first URSP policy; adding a first indication of whether to add Always-On in an RSD list of the first URSP policy;

the method further comprises the steps of:

the UE determines whether to bind traffic to a session of an Always-On feature based On the first indication.

13. The method of claim 12, wherein the method further comprises:

and receiving a policy container sent by the first network device transmitted by the third network device.

14. The method of claim 13, wherein the method further comprises:

and when the network device is in the idle state, switching from the idle state to the connection state based on a service request flow triggered by the third network device.

15. The method of claim 12, wherein the method further comprises:

and sending indication information for setting the Always-On feature to the first network equipment.

16. The method of claim 15, wherein the transmitting, to the first network device, the indication information to set the Always-On feature comprises:

in the initial session establishment procedure, or the session modification procedure, indication information for setting the Always-On feature is transmitted to the first network device.

17. The method of claim 12, wherein the method further comprises:

Based On at least one parameter associated with the PDU session and the correspondence, it is determined to set the PDU session to a permanently-On Always-On feature.

18. The method of claim 17, wherein the correspondence is: a first correspondence;

19. The method of claim 18, wherein the at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.

20. The method of claim 17, wherein the correspondence is: the network side sends the message to the UE or the UE is preconfigured.

21. The method of claim 20, wherein the method further comprises:

a first correspondence is received that is sent via the UCU message.

22. The method of claim 20, wherein the method further comprises:

a first correspondence is received that is sent via a registration reply message.

23. The method of claim 17, wherein the method further comprises:

QoS parameters are received.

24. The method of claim 23, wherein the method further comprises:

and sending the PDU session establishment request message, and receiving the QoS parameters carried in the PDU session establishment request reply message by the network side.

25. The method of claim 23, wherein the correspondence is: a second correspondence;

26. The method of claim 25, wherein the method further comprises:

when it is determined that the PDU session needs to be set to the Always-On feature, a first request to set the PDU session to the Always-On feature is sent via a session modification request message.

27. The method of claim 26, wherein the method further comprises:

feedback information for the first request is received, and it is determined whether to set the PDU session to an Always-On feature based On the feedback information.

28. A session setting method, applied to a UE, comprising:

29. A session setting method is applied to a second network device and comprises the following steps:

upon determining that the PDU session of the UE is set to an Always-On feature, sending an indication to the UE; wherein the indication is used to inform the UE to set the PDU session to Always-On;

the method further comprises the steps of:

and sending a second indication for indicating the number of Always-On sessions to the UE.

30. The method of claim 29, wherein the PDU session related information of the UE comprises at least one of:

31. The method of claim 30, wherein the method further comprises:

receiving a session establishment request sent by UE;

correspondingly, the sending the indication to the UE includes:

transmitting a session establishment reply message carrying a first indication to the UE; wherein the first indication is for instructing the UE to set a PDU session to an Always-On feature.

32. The method of claim 31, wherein the method further comprises:

and after the first indication is sent, receiving an Always-on PDU session request identifier carried by the UE in a PDU session modification request message.

33. The method of claim 31, wherein the sending the indication to the UE comprises:

sending a notification message to the UE, wherein the notification message carries a first parameter; wherein the first parameter includes an identification of whether an Always-On session needs to be established and/or whether an Always-On session needs to be established.

34. The method of claim 33, wherein the notification message is: a proprietary NAS message, or a paging message.

35. The method of claim 33, wherein the method further comprises:

and receiving a session modification request sent by the UE, wherein the session modification request carries an indication that the PDU session is of an Always-On characteristic.

36. The method of any one of claims 29-35, wherein the method further comprises:

37. A first network device, comprising:

a first communication unit transmitting at least one piece of information related to an Always-On feature to the UE;

the first communication unit sends a policy container to the UE; the policy container carries a first URSP policy; a first indication of whether to add Always-On is added to the RSD list of the first urs policy, and the first indication is used for the UE to determine whether to bind the service to the session of the Always-On feature.

38. The first network device of claim 37, wherein the first communication unit transparently passes the policy container to a UE through a third network device.

39. The first network device according to claim 37 or 38, wherein the first communication unit receives a policy configuration result carried by the UE through a policy container.

40. The first network device of claim 37, wherein the first communication unit receives indication information sent by the UE to set an Always-On feature.

41. The first network device of claim 40, wherein the first communication unit receives indication information of setting an Always-On feature transmitted by the UE during an initial session establishment procedure or a session modification procedure.

42. The first network device of claim 37, wherein the first communication unit configures a correspondence for a UE.

43. The first network device of claim 42, wherein the correspondence is: a first correspondence;

44. The first network device of claim 43, wherein at least one parameter of the PDU session attribute comprises at least one of: S-NSSAI, DNN.

45. The first network device of claim 42, wherein the first communication unit transmits QoS parameters.

46. The first network device of claim 45, wherein the correspondence is: a second correspondence;

47. The first network device of claim 37 or 38, wherein the first communication unit receives a third indication sent by the UE for indicating the number of Always-On sessions.

48. A UE, comprising:

a second communication unit receiving at least one information related to an Always-On feature; wherein the at least one related information is used for the UE to determine whether to bind the service to the session of the Always-On feature or comprises a second indication for indicating the number of Always-On sessions;

wherein the second communication unit receives a policy container; the policy container carries a first URSP policy; a first indication of whether to add Always-On is added to the RSD list of the first urs policy, and the first indication is used for judging whether to bind the service to the session of the Always-On feature.

49. The UE of claim 48, wherein the second communication unit receives a policy container sent by the first network device and transmitted by the third network device.

50. The UE of claim 48, wherein the UE further comprises:

and the second processing unit is switched from the idle state to the connection state based on a service request flow triggered by the third network equipment when the second processing unit is in the idle state.

51. The UE of claim 48, wherein the second communication unit transmits indication information to the first network device to set an Always-On feature.

52. The UE of claim 51, wherein the second communication unit transmits indication information for setting an Always-On feature to the first network device in an initial session establishment procedure or a session modification procedure.

53. The UE of claim 48, wherein the UE further comprises:

and a second processing unit determining to set the PDU session to a permanently-On Always-On Always-On feature based On at least one parameter associated with the PDU session and the correspondence.

54. The UE of claim 53, wherein the correspondence is: a first correspondence;

55. The UE of claim 54, wherein the at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.

56. The UE of claim 53, wherein the correspondence is: the network side sends the message to the UE or the UE is preconfigured.

57. The UE of claim 56 wherein the second communication unit receives the first correspondence sent via UCU messages.

58. The UE of claim 56, wherein the second communication unit receives the first correspondence sent via a registration reply message.

59. The UE of claim 53, wherein the second communication unit receives QoS parameters.

60. The UE of claim 59, wherein the second communication unit sends a PDU session establishment request message, and receives the QoS parameters carried by the network side in the PDU session establishment request reply message.

61. The UE of claim 59, wherein the correspondence is: a second correspondence;

62. The UE of claim 61, wherein the second communication unit transmits a first request to set the PDU session to the Always-On feature through a session modification request message when it is determined that the PDU session needs to be set to the Always-On feature.

63. The UE of claim 62, wherein the second communication unit receives feedback information for the first request;

the second processing unit determines whether to set the PDU session to an Always-On feature based On the feedback information.

64. A UE, comprising:

and a fourth communication unit for transmitting a third indication for indicating the number of Always-On sessions.

65. A second network device, comprising:

a third communication unit that transmits an indication to the UE when it is determined that the PDU session of the UE is set to an Always-On feature; wherein the indication is used to inform the UE to set the PDU session to Always-On;

wherein the third communication unit sends a second indication for indicating the number of Always-On sessions to the UE.

66. The second network device of claim 65, wherein the PDU session related information of the UE includes at least one of:

67. The second network device of claim 66, wherein the third communication unit receives a session establishment request from the UE;

68. The second network device of claim 67, wherein the third communication unit receives an Always-on PDU session request identity carried by the UE in a PDU session modification request message after sending the first indication.

69. The second network device of claim 65, wherein the third communication unit sends a notification message to the UE, the notification message carrying the first parameter; wherein the first parameter includes an identification of whether an Always-On session needs to be established and/or whether an Always-On session needs to be established.

70. The second network device of claim 69, wherein the notification message is: a proprietary NAS message, or a paging message.

71. The second network device of claim 69, wherein the third communication unit receives a session modification request sent by the UE, where the session modification request carries an indication that the PDU session is an Always-On feature.

72. The second network device of any of claims 65-71, wherein the third communication unit receives a third indication sent by the UE for indicating the number of Always-On sessions.

73. A network device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the memory is adapted to store a computer program, said processor being adapted to invoke and run the computer program stored in said memory, performing the steps of the method according to any of claims 1-11, 29-36.

74. A UE, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the memory is adapted to store a computer program, said processor being adapted to invoke and run the computer program stored in said memory, performing the steps of the method according to any of claims 12-28.

75. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 1-11, 29-36.

76. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 12-28.

77. A computer readable storage medium for storing a computer program which causes a computer to perform the steps of the method of any one of claims 1-36.