CN113412665A

CN113412665A - Session setting method, network equipment and user equipment

Info

Publication number: CN113412665A
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: 2021-09-17
Anticipated expiration: 2039-07-12
Also published as: WO2021007734A1; CN113412665B

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 information related to Always-On feature to the UE; the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain 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

An Always-on (Always-on) Protocol Data Unit (PDU) session refers to a user plane resource that must be activated each time the UE transitions from a CM-IDLE state to a CM-CONNECTED state. After setting the PDU session to Always _ on, the UE must Request to activate the PDU session every time it initiates a Service Request (Service Request), even if there is no data to send.

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

Disclosure of Invention

To solve the foregoing technical problem, 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, which is applied to a first network device, and includes:

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

the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.

In a second aspect, a session setting method is provided, which is applied to a UE, and includes:

receiving at least one piece of information related to Always-On characteristics; the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.

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

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

sending an indication to the UE when it is determined that the PDU session of the UE is set to Always-On feature; wherein the indication is to inform the UE to set the PDU session to Always-On.

In a fourth aspect, a first network device is provided, which includes:

a first communication unit which transmits at least one piece of relevant information to the UE;

In a fifth aspect, a UE is provided, including:

a second communication unit receiving at least one related information;

and the second processing unit is used for judging whether to bind the service to the session of the Always-On characteristic or not based On the at least one piece of relevant information, or is used for judging whether to set the PDU session to be permanently started with the Always-On characteristic or contains a second indication for indicating the number of Always-On sessions.

In a sixth aspect, a second network device is provided, which includes:

the third processing unit is used for determining whether the PDU session of the UE is set to Always-On characteristics or not based On the PDU session related information of the UE;

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

A seventh aspect provides a session setting method, 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, a UE is provided, including:

and the fourth communication unit is used for sending a third instruction to the network side, wherein the third instruction is used for indicating the Always-On conversation quantity.

In a ninth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect, the third aspect, or each implementation manner thereof.

In a tenth aspect, a UE is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.

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

Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method according to any one of the first to third aspects or the implementation manners thereof.

In a twelfth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method of any one of the 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 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 first to fourth aspects or implementations thereof.

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

Drawings

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

fig. 2-1 is a first flowchart of a session setting method according to an embodiment of the present invention;

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

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

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

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

FIG. 4-2 is a diagram illustrating a UE policy container reason value indication location;

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

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

FIG. 7 is a schematic view of a session establishment procedure;

fig. 8 is a fourth schematic flowchart of a session setting method according to an embodiment of the present invention;

FIGS. 9-11 are schematic diagrams of processing for sending correspondences in different processes according to embodiments of the present invention;

fig. 12 is a schematic flowchart of a session setting method according to an embodiment of the present invention;

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

FIGS. 14-15 are two flow diagrams illustrating the sending of an indication according to embodiments of the present invention;

fig. 16 is a schematic structural diagram of a first network device according to an embodiment of the present invention;

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

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

fig. 19 is a seventh flowchart of a session setting method according to an embodiment of the present invention;

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

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

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

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

Detailed Description

So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

For example, a communication system 100 applied in the embodiment of the present application 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. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Network device (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or a Network device in 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 Public Land Mobile Network (PLMN) for future evolution, or the like.

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, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a 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 another UE's device configured to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A UE that is arranged to communicate over a radio interface may be referred to as a "radio communication terminal", "radio terminal" or "mobile terminal".

Optionally, a Device to Device (D2D) communication may be performed between UEs 120.

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

An embodiment of the present invention provides a session setting method, applied to a first network device, as shown in fig. 2-1, including:

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

An embodiment of the present invention provides a session setting method, applied to a UE, as shown in fig. 2-2, including:

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

In the solution provided in this embodiment, the information related to Always-On features may be parameters included in a Routing Selector (RSD) of a first UE routing Policy (URSP) included in a Policy container, or may be a corresponding relationship.

The scheme provided by the present embodiment is described in a variety of scenarios as follows:

scene 1,

An embodiment of the present invention provides a session setting method, applied to a first network device, as shown in fig. 3-1, including:

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

The present embodiment further provides a session setting method, applied to a UE, as shown in fig. 3-2, including:

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

Step 302: and the UE judges whether to bind the service to the session with Always-On characteristic based On the first indication.

Further, the method can also comprise the following steps: and feeding back a strategy configuration result to the first network equipment.

It is first noted that the first indication is carried in an RSD in the first URSP 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 Always-on characterized session refers to the user plane resources that the UE must activate each time it transitions from the CM-IDLE state to the CM-CONNECTED state. The UE may set the Session to Always-on PDU Session in the request to establish PDU Session (i.e., Always-on PDU Session request is carried in the PDU Session establishment request message) 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 the roaming scenario, the V-SMF will also participate in deciding whether the session can be set to Always-on. After the UE moves from EPS to 5GS, the UE may send a PDU Session modification procedure to the network SMF, and include an Always-on PDU Session request parameter, to request to set the PDU Session as an Always-on Session, and the SMF has a right to decide whether it can be set as an Always-on Session.

After 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 a Service Request when the session has no data to send

The UE policies may include ANDSP (the ANDSP policies further include wlan sp and/or N3IWF/ePDG network element selection policies) and URSP policies. The present embodiment mainly adopts the URSP policy.

As shown in fig. 4-1, the UE Policy Configuration method may include that the PCF places the UE Policy (Policy) to be updated in a Container (Container) through a UE Configuration Update (UCU) procedure defined by 3GPP, and sends the UE Policy (Policy) to the AMF, and the AMF directly forwards the UE Policy to the UE using an NAS message.

For UE policy configuration, the cause value of "UE policy container" has been introduced in both downlink NAS and uplink NAS messages, as shown in fig. 4-2. Further, the arrangement of bits is 4321, and examples of cause values are as follows: 0000, identification N1 SM information; 0010 is SMS; 0011 is an LTE Location Protocol (LLP) information container; 0100 is SOR transparent transmission container; 0101 is UE policy container; 0110 it is UE parameter update transparent transmission container; 1111 is a multi-load; the remaining cause values remain.

On the basis of fig. 4-1 and with reference to fig. 5, taking the first network device as a PCF and the third network device as an AMF as an example, the scheme provided by this embodiment is described in detail:

step 0-1: UE policy is triggered by the PCF, possibly based on UE initial registration, location/time changes, policy changes, etc., which may decide to trigger policy configuration, updates, or deletions.

That is to say, 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 URSP policy.

The embodiment provides the UE with an indication of whether to bind the Always-On feature through the first URSP policy, that is, the UE is enhanced On the basis of the existing URSP policy, that is, the RSD list of the existing URSP policy is added with indication information of whether to add Always-On.

The first URSP policy and the RSD list thereof are described with reference to table 1 and table 2. Wherein, the contents of the plurality of rules included in the first URSP policy are shown in table 1, and the contents of the RSD list in table 1 refer to table 2; table 2 shows the specific content included in the RSD list in the first URSP policy, and it should be noted that an indication of Always-On is added to the RSD list:

TABLE 1

TABLE 2

In table 2, "Always-On indication" is a newly added parameter in this embodiment, and the parameter may indicate whether the UE binds application data corresponding to the service descriptor of the URSP rule to the Always-On session. For example, when it is 1, it can be characterized that the service is bound to the session with Always-On feature, and when it is 0, it can be characterized that the service is not bound to the session with Always-On feature. In addition, it should be noted that, if there is a session with Always-On characteristics, the service can be directly bound to the session; if the session with Always-On characteristic does not exist, a new session with Always-On characteristic can be created, and then the service is bound to the newly-created session.

Specifically, a Traffic Descriptor in the URSP rule is used to describe a specific service, for example, a microblog service may be described by a range of IP 1 to 9, and for example, an IMS service may be described by an IMS DNN. Then, one or more RSDs (routing identifiers) may be under one service descriptor, each of which corresponds to an attribute of one PDU session, that is, service data corresponding to the service descriptor may run in the PDU session corresponding to the RSD.

Step 2, after receiving the message in step 1, if the UE is currently in a CM-IDLE state, the AMF triggers a service request flow so as to enable the UE to return to a CM-CONNECTED state to transfer a policy 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 equipment (AMF).

The service request process may be used for the UE in the CM-IDLE state to send an uplink signaling message, user data, or reply to a network paging request. After the service request process is completed and the user plane connection is activated, the UE enters a CM-CONNECTED state. In addition, the service request flow is also used for the CM-CONNECTED UE to initiate the activation of the inactive user plane link (e.g. PDU session) and reply to the NAS notification message from the AMF. When the user plane connection is activated, the AS layer of the UE notifies the NAS layer.

The service request flow is explained with reference to fig. 6: the parameters to be carried in the first message (Service Request) may include: AN parameters, Service requests (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status,5G-S-TMSI, [ NAS message container ], expression indication, wherein AN Parameter is a Parameter such AS GUTI information, network slice information, etc. that the UE sends To the base station at the AS layer, the following Service Request is AN NAS message, which is passed through by the base station To the AMF, and what is strongly related To this patent is the List Of PDU Sessions To Be Activated which the UE actively requests To reactivate, and further the List Of Allowed PDU Sessions are which PDUs Allowed at the network side are replied after the UE (passively) receives a paging message or AN NAS notification message.

For 1, 2 and 4 in fig. 6, the Service Request message is transparently transmitted To the SMF, and through the interaction inside the network side, especially the interaction between the SMF and the RAN, the SMF determines which List Of PDU Sessions To Be Activated requested by the UE To activate, and places the message in the Service Accept message To return To the UE through 11, 12 and 13.

And step 3: and when the UE is in the CM-CONNECTED state, the UE sends the message in the step 3, the message carries the PoicyContainer in the step 1, the Container does not need to be read in the AMF, and the AMF directly encapsulates the Container into the NAS message and sends the NAS message to the UE.

And 4-5: and the first network equipment (namely PCF) receives the strategy configuration result carried by the UE through the strategy container. Correspondingly, the UE returns the result of the Policy configuration to the PCF through the message, and similarly, the result of the configuration is placed in Policy Container and transmitted to the PCF.

Here, the UE also needs to bind the traffic into the session with Always-On feature based On the first URSP policy.

The specific processing manner for the UE to bind the traffic to the corresponding PDU session for transmission based on the URSP policy can be described as follows:

when data appears in an application layer, the UE checks whether the characteristics of the application data are matched with the Traffic Descriptor of one of the URSP rules by using the URSP rules in the URSP policy, the checking sequence is determined according to the Precedence (priority) in the 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 PDU session is bound by using the RSD list under the URSP rule.

When the URSP rule is matched, the UE searches a proper PDU session according to the Precedence order in the RSD, wherein the RSD with high priority is preferentially used, 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 the application data exists, the application data is bound 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 successfully established, the UE binds the application data to the session for transmission; if the session establishment is not successful, the UE again looks up whether the PDU session exists based on other parameter combinations in the RSD or using parameter combinations in the RSD of the secondary priority.

If a proper PDU session can not be found for binding according to the matched URSP rule, the UE searches whether the Traffic Descriptor in the next-priority URSP rule can be matched with the application data stream characteristics according to the Precedence sequence, and when the Traffic Descriptor is matched with the application data stream characteristics, the previous process is repeated.

The above process of finding a suitable PDU session for an application may be referred to as "evaluation", and when finding a suitable PDU session binding, the UE may perform evaluation again in at least one of the following situations to see whether the binding relationship between the original application data and the PDU session needs to be changed:

-updating by PCF (the URSP is updated by the PCF);

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

-Allowed NSSAI or Configured NSSAI update (change of Allowed NSSAI or Configured NSSAI);

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

-UE registration for 3GPP or non-3GPP access (UE registers over 3GPP or non-3GPP access);

-the UE establishing a WLAN access (UE associations 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 specifically comprises the following steps: and receiving indication information which is sent by the UE in an initial session establishing process or a session modifying process and used for setting Always-On attributes.

That is, the UE may carry an "Always-On" indication in the initial PDU session establishment or session modification process, the network side may accept or reject whether the PDU session may be Always-On, it may be considered that Always-On is a feature of the PDU session, then the foregoing processing procedure is adopted to bind the service to the session with Always-On feature, and then the indication is sent to the UE. Thus, each time a subsequent UE transitions from CM-IDLE to CM-CONNECTED after the established PDU session is Always-on, the PDU session with Always-on must be activated. That is, when the UE is converted from CM-IDLE to CM-CONNECTED, the Service Request message sent carries the identification of the PDU session of the "Always-on" feature, so as to let the network side activate the PDU session.

For example, the aforementioned binding of the service to the session of Always-On feature may be performed for at least one service including: the PDU session for low latency high reliability traffic (URLLC), the PDU session for Time synchronization traffic (Time Sync), and the PDU session for partial delivery Time sensitive Traffic (TSN) need to be set to Always-on.

Regarding the PDU session setup procedure, as shown in fig. 7, the most important to the UE side is the PDU session setup request message and the received reply message.

Step 1: the PDU Session Establishment Request message is sent by the UE to the AMF and the SMF through an NAS message, where the NAS message may include S-nssai (S), DNN, PDU Session ID, Request type, Old PDU Session ID, N1 SM Container (PDU Session Establishment Request), where SM Container is further sent by the AMF to the SMF by the SM Container and mainly includes information related to Session characteristics, and the UE may add an "Always-on requested" identifier to indicate that the SMF establishes an Always-on PDU Session.

Step 2: and 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 (the detailed process is not detailed because it is the behavior inside the network side)

Step 11-13: SMF sends message to RAN, which mainly contains N1 SM Container (PDU) associated with QoS Flow (S) associated with QoS Flow (S), N2 SM information (PDU _ SESSID, QFI (S), QoS Profile (S), CN _ Tunnel _ Info, S-NSSAI from the associated NSSAI, Session-AMBR, PDU _ Type, User Plane _ SecurityEnformation, UE _ IntegrationMaximumDataRate, RSN), [ Alway-PDU _ PDU ], selected SSC, S-NSSAI _ ControlsControlsN, UE _ ControlControlandSigneServiceType _ PDU, QoS _ SegmentsType, S-SAI _ ControlsTypesN, QoS _ ControlyServiceN ] and so on, UE _ SegmentsType _ PDU, QoS Flow _ SegmentsType, QoS _ SegmentsType _ Index _ ReservationsType _ IndustsTypesN, UE _ ControlySegmentsTypesN, QoS _ SegmentsTypesN, UE _ Infoe _ Segment _ PDU, QoS _ Infoe _ Selection _ PDU, QoS _ SelectionType [ IPv _ ReservationsType ] and so on _ Selection _ ReservationsType [ 35 ], the N2 SM Information is used for self-use for air interface bearer establishment, and other parameters such as the [ Always-on PDU Session Granted ] parameter are also sent to the UE.

In addition, if the UE does not Request Always-On in the PDU Session Establishment Request, the SMF may decide to set itself to Always-On, thus adding [ Always-On PDU Session Granted ] (Always-On PDU Session grant) in the PDU return Session Establishment Accept message.

Finally, it should be noted in this embodiment that this embodiment is directed to the binding of Always-On features of a session, but in actual processing, there may also be binding of other more features or binding of more attributes, and the processing mode adopted may be the same as that in the foregoing scheme, but is not exhaustive in this embodiment. In addition, several services bound to the session with Always-On characteristics are illustrated in this embodiment, but this embodiment is not exhaustive and may also be applied to any other determination that the session of the Always-On service can be opened.

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. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, which can be sent to the UE by the network side, and accordingly, the UE determines the number of PDU sessions of 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 by the UE; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication.

And 2, configuring a corresponding relation for the UE.

Specifically, as shown in fig. 8:

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

step 402: and determining to set the PDU session as a permanent open Always-On feature based On the at least one parameter related to the PDU session and the corresponding relation.

UE receives URSP rule; the UE may then determine whether to set the PDU session to Always-On feature according to the network slice parameter (NSSAI) and/or DNN parameter of the RSD list in the URSP rule configured On 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 the PDU conversation attribute and Always-On characteristic;

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

The at least one parameter of the PDU session attribute may be one or more parameters in an RSD in a URSP rule.

That is, the UE may match the first corresponding relationship with at least one parameter that may be specified in the URSP rule according to the plurality of parameters included in the received RSD list in the URSP rule, and when the first corresponding relationship is matched with the at least one parameter specified in the first corresponding relationship, it may be determined that the first corresponding relationship is satisfied, and then it is determined that the PDU session can be set to Always-On characteristics according to the first corresponding relationship.

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

At least one parameter in the PDU session attributes includes at least one of: S-NSSAI, DNN.

For example, the UE receives the URSP rule, uses the parameter in the URSP rule as the parameter of the PDU session attribute, and when the RSD in the URSP rule-1 includes a specific S-NSSAI-1 and/or DNN-1, the UE determines that the session is to execute a specific service (e.g., URLLC service) according to the first corresponding relationship (e.g., the corresponding relationship between S-NSSAI-1 and/or DNN-1 and Always-On characteristics, or the corresponding relationship between S-NSSAI-2 and/or DNN-2 and first class services), and whether the PDU session to be bound is an Always-On characteristic, or directly determines whether the PDU session to be bound to Always-On is needed.

Further, in this example, with respect to binding traffic to a PDU session, it can be understood that specific data is transmitted on a specific PDU session. For example, if application 1 is bound to PDU session 1, it means that the data of application 1 is transmitted 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, and can also be statically configured on the terminal.

For dynamic transmission to the terminal, the following modes can be selected: receiving the first correspondence sent through the UCU message, or receiving the first correspondence sent through the registration reply message. Specifically, the method comprises the following steps:

mode 1: the UCU message is sent according to UCU message, which may be UCU message triggered by AMF or UCU message triggered by PCF.

For example, as shown in fig. 9, when the AMF (i.e., the third network device) sends the configuration update instruction to the UE, the first corresponding relationship is carried in the configuration update instruction; and then the UE sends the UE configuration update completion to the AMF, the AMD sends the related information to the UMD, and the RAN is updated.

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

Mode 2: and sending the message to the terminal in a registration reply message. As shown in fig. 11, what has been described above with respect to the registration flow is not described here again. In the flow shown in fig. 11, the AMF feeds back the first correspondence to the information received by the UE.

Another processing method is as follows: the UE receives QoS parameters.

And the UE determines to be set to Always-on according to the configured QoS information after the PDU session is established.

The present example is different from the foregoing example in that the present example sends a PDU session establishment request message, and receives the QoS parameter carried in a PDU session establishment request reply message by the network side. That is, the UE receives the QoS information sent by the network side after performing the session establishment request, and further determines whether to set the PDU session to an Always-On session according to the QoS parameter and the second correspondence. Namely UE sends PDU conversation establishment request message; and receiving QoS parameters associated with the PDU session.

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

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

or the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the Always-On characteristic.

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 conversation can be set to be Always-On characteristic based On the second corresponding relation; or, when the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service, matching may be performed according to the content included in the received QoS parameter and the parameter included in the second correspondence, and when matching is performed, the PDU session may be determined to be a session of the first type of service, and then the determined PDU session needs to be set to the Always-On feature.

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

As shown in fig. 12, it is determined whether the session needs to be set as Always-on according to the PDU session setup request message transmitted by the UE and the received QoS information, and if so, the UE sets the session as Always-on when initiating the PDU session modification procedure.

The second corresponding management can 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 setup procedure as shown in fig. 7 through steps 11, 12 and 13. That is, in step 11, the SMF sends N1 SM Container to AMF, where the Container contains PDU Session Establishment Accept ([ QoS Rule(s) and QoS Flow level QoS parameters if new for the QoS Flow(s) ]. here, the QoS parameter is used to describe the QoS Flow characteristics in the PDU Session, including 5QI, ARP, RQA, Aggregate Bit Rates, Notification control, Flow Rate, Maximum Packet Rate, etc., or derives static QoS parameters on its own in the message that the UE replies to the SMF, however, the UE decides whether to set the traffic-on. typical QoS parameters and specific traffic as shown in table 3 below, depending on the QoS parameters of the data Flow of the PDU Session.

In addition, in addition to the PDU session establishment procedure, the UE may also obtain 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 also decide whether to set the PDU session as Always-on.

For example, an eMBB application, such as 5QI ═ 80, so the UE may determine that the session needs to be set to Always-on based on a particular 5QI value (e.g., 5QI ═ 80). For another example, a QoS flow of 5QI ═ 82-85 requires a Delay Critical GBR, and the UE may consider that a PDU session in which a data flow of the Delay Critical GBR occurs needs to be set to Always-on.

TABLE 3

The above example is processing based On 5QI, and other parameters in QoS parameters may be actually used, such as a streaming bit Rate, a Maximum Packet Loss Rate (Maximum Packet Loss Rate), and so On, for example, a second correspondence between a bit Rate of-1 and Always-On characteristics may be set, or a second correspondence between a range of Packet Loss rates and Always-On characteristics (or first type of traffic) may be set.

Describing with reference to the PDU session establishment procedure shown in fig. 7, after the UE determines to set the PDU session to Always-on according to the received QoS parameter, the UE initiates a PDU session modification procedure, according to the existing procedure, the UE adds an "Always-on is request" parameter to the PDU session modification request message, requests the network side to set it as an Always-on session, and the network side can determine whether to finally set it as Always-on.

In addition, the scheme provided by the embodiment may further include: the UE receives a second indication indicating the number of Always-On sessions. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, which can be sent to the UE by the network side, and accordingly, the UE determines the number of PDU sessions of 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 of the network side, that is, may be a PCF, an AMF, or an SMF, which is not limited in this embodiment.

In addition, a third indication for indicating the number of Always-On sessions can be sent for the UE; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication. Similarly, the network side may be specifically a PCF, an AMF, or an SMF.

Therefore, by adopting the scheme, the UE can determine whether to set the PDU session to Always-On characteristic according to the corresponding relation. Therefore, the service session is guaranteed to be bound to the Always-On session in time, the time accuracy of the services is improved, and the reliability of the services is guaranteed.

An embodiment of the present invention further provides a session setting method, applied to a second network device, as shown in fig. 13, including:

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

step 502: sending an indication to the UE when it is determined that the PDU session of the UE is set to Always-On feature; wherein the indication is 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:

the method comprises the steps of session establishment parameters reported by UE, user subscription information corresponding to the UE, PCC strategies and local configuration.

Correspondingly, the SMF may determine whether to set the session to Always-on according to session establishment parameters such as S-NSSAI and DNN reported by the UE, subscription information of the user, a PCC policy, local configuration, and the like. That is, even if the UE does not indicate the setting to Always-on in the request message, the SMF may decide to set to Always-on, so that the network side has sufficient capability to determine without sending to the UE to determine.

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

in a first manner, as shown in fig. 14, a UE initiates a session establishment request to a second network device, that is, an SMF, and after the SMF determines to set to Always-on, the SMF sends a session establishment reply message carrying a first indication to the UE; wherein the first indication is to instruct the UE to set a PDU session to Always-On feature.

And after the first indication is sent, receiving Always-on PDU session request identification carried in the PDU session modification request message by the UE. 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 "Always-on is requested indication", and the SMF agrees to set the PDU session as Always-on according to the existing procedure.

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

Sending a notification message to the UE, wherein the notification message carries the first parameter; the first parameter comprises the identification whether the Always-On session needs to be established or not and/or the Always-On session needs to be established. That is, the network side SMF informs the terminal through a separate message that the UE is required to set the session to Always-on

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

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

Then, the method can also comprise that the UE initiates a PDU session modification flow to carry an Always-on requested indication, and the SMF agrees to set the PDU session as Always-on according to the existing flow.

The PDU session in this embodiment may be a PDU session of URLLC and TSN services, and of course, may also be other services, as long as a service that needs to set the session characteristics of Always-On may be included in the protection scope of this embodiment. It is not exhaustive here.

Thus, for an important TSN Time synchronization service, if it cannot be set as Always-on in Time, it will have an important influence on the accuracy of Time, for example, after the UE changes from idle state to connected state, long-Time non-Time synchronization needs to be performed immediately with Time Sync, so that the network side can adjust the offset Time of the clock on the network element in Time.

For URLLC traffic, the industrial scenario is more used, and Always-on must be set to deliver data in time, otherwise highly reliable specialization will not be possible 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. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, which can be sent to the UE by the network side, and accordingly, the UE determines the number of PDU sessions of 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 used for indicating the number of Always-On sessions and sent by the UE can be received for the second network equipment; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication. Similarly, the network side may specifically be an SMF.

Therefore, by adopting the scheme, the network side can determine whether the session can be set to Always-On characteristics according to the PDU session related information of the UE. Therefore, the service session is guaranteed to be bound to the Always-On session in time, the time accuracy of the services is improved, and the reliability of the services is guaranteed.

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

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

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

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

and the second processing unit 72 is used for judging whether to bind the service to the session of the Always-On characteristic based On the at least one piece of relevant information, or is used for judging whether to set the PDU session as a permanent turn-On Always characteristic, or contains a second indication for 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 URSP policy included in the policy container, or may be at least one parameter related to a PDU session, or may be a QoS parameter.

scene 1,

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

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

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

UE policy is triggered by the PCF, possibly based on UE initial registration, location/time changes, policy changes, etc., which may decide to trigger policy configuration, updates, or deletions.

That is to say, 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 URSP policy.

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

the UE further comprises: when the second processing unit 72 is in the idle state, the idle state is switched to the connection state based on a service request flow triggered by a third network device (AMF).

When the UE is in the CM-CONNECTED state, the AMF directly encapsulates the Container into the 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 the Policy configuration to the PCF through the message, and similarly, the result of the configuration is placed in the Policy Container and is passed through to the PCF.

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

The embodiment is directed to the binding of Always-On characteristics of a session, but in actual processing, there may also be binding of other more characteristics or binding of more attributes, and the processing mode adopted may be the same as the foregoing scheme, but is not exhaustive in the embodiment. In addition, several services bound to the session with Always-On characteristics are illustrated in this embodiment, but this embodiment is not exhaustive and may also be applied to any other determination that the session of the Always-On service can be opened.

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

In addition, the scheme provided by the embodiment may further include: the first communication unit of the first network device sends a second indication indicating the number of Always-On sessions to the second communication unit of the UE. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, which can be sent to the UE by the network side, and accordingly, the UE determines the number of PDU sessions of 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 by the second communication unit of the UE; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication.

Scene 2,

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

and the second processing unit 72 determines to set the PDU session as a permanent open Always-On feature based On the at least one parameter related to the PDU session and the corresponding relation.

A second communication unit 71 that receives the URSP rule; the UE may then determine whether to set the PDU session to Always-On feature according to the network slice parameter (NSSAI) and/or DNN parameter of the RSD list in the URSP rule configured On 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 URSP rule for the first corresponding relationship according to the received multiple parameters included in the RSD list in the URSP rule, and when the multiple parameters match the at least one parameter specified in the first corresponding relationship, may determine that the first corresponding relationship is satisfied, and further determine that the PDU session can be set to the Always-On feature according to the first corresponding relationship.

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

For dynamic transmission to the terminal, the following modes can be selected: the second communication unit 71 receives the first correspondence transmitted by the UCU message, or the second communication unit 71 receives the first correspondence transmitted by the registration reply message.

There is another way that the UE decides to set to Always-on according to the configured QoS information after setting up the PDU session.

The difference between this example and the foregoing example is that the second communication unit 71 in this example sends a PDU session establishment request message, and receives the QoS parameter carried in the PDU session establishment request reply message by the network side. That is, the UE receives the QoS information sent by the network side after performing the session establishment request, and further determines whether to set the PDU session to an Always-On session according to the QoS parameter and the second correspondence. Namely UE sends PDU conversation establishment request message; and receiving QoS parameters associated with the PDU session.

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

the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the first class of service; or the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the Always-On characteristic.

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 set to be Always-On characteristic based On the second corresponding relation; or, when the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service, matching may be performed according to the content included in the received QoS parameter and the parameter included in the second correspondence, and when matching is performed, the PDU session may be determined to be a session of the first type of service, and then the determined PDU session needs to be set to the Always-On feature.

In addition, the UE may send a first request for setting the PDU session to Always-On feature through the session modification request message by the second communication unit 71, when it is determined to set the PDU session to Always-On feature; and receiving feedback information for the first request, and determining whether to set the PDU session to 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 the number of Always-On sessions. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, the second indication may be sent to the UE by the network side, and accordingly, the second processing unit of the UE may also determine the number of PDU sessions of Always-On feature that may 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 of the network side, that is, may be a PCF, an AMF, or an SMF, which is not limited in this embodiment.

In addition, a third indication for indicating the number of Always-On sessions can be sent for the second communication unit of the UE; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication. Similarly, the network side may be specifically a PCF, an AMF, or an SMF.

An embodiment of the present invention further provides a second network device, as shown in fig. 18, including:

the third processing unit 82, which determines whether the PDU session of the UE is set to Always-On characteristics based On the PDU session related information of the UE;

a third communication unit 81, configured to send an indication to the UE when it is determined that the PDU session of the UE is set to Always-On feature; wherein the indication is 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 the session establishment parameters, such as S-NSSAI and DNN, reported by the UE, subscription information of the user, a PCC policy, a local configuration, and the like. That is, even if the UE does not indicate the setting to Always-on in the request message, the SMF may decide to set to Always-on, so that the network side has sufficient capability to determine without sending to the UE to determine.

in the first mode, after a third communication unit 81 receives a session establishment request initiated by a UE to a second network device, that is, SMF, and a third processing unit of SMF determines 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 to instruct the UE to set a PDU session to Always-On feature.

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

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

In addition, the scheme provided by the embodiment may further include: a third communication unit of the second network device sends a second indication to the UE indicating the number of Always-On sessions. Due to the capability handling limitation of the UE or the network side, for example, it may be that the UE or the 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, that is, "Always _ On session number indication" is introduced, which can be sent to the UE by the network side, and accordingly, the UE determines the number of PDU sessions of 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 used for indicating the number of Always-On sessions and sent by the UE can be received for a third communication unit of the second network equipment; that is, the indication may also be sent by the UE to the network side, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication. Similarly, the network side may specifically be an SMF.

The session setting method provided in the embodiment of the present invention is applied to a UE, and as shown in fig. 19, the session setting method 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, the second network device, or the third network device on the network side may receive a 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 instruction to the network side, where the third instruction is used to indicate the Always-On session number.

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, and the network side may determine the number of PDU sessions corresponding to Always-on characteristics of the same UE that can be received according to the indication. Similarly, the network side may be specifically one of AMF, PCF, and SMF.

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

Optionally, as shown in fig. 21, the communication device 1900 may further include a memory 1920. From memory 1920, processor 1910 may invoke and execute a computer program, among other things, to implement methods in embodiments of the present invention.

The memory 1920 may be a separate device from the processor 1910 or may be integrated into 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 specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 1930 may include a transmitter and a receiver, among other things. The transceiver 1930 may further include one or more antennas.

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

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

Fig. 22 is a schematic structural diagram of a chip of an embodiment of the present invention. The chip 2000 shown 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, the chip 2000 may further include a memory 2020. From the memory 2020, the processor 2010 may call and execute a computer program to implement the method in the embodiment of the present invention.

The memory 2020 may be a separate device from the processor 2010 or may be integrated into the processor 2010.

Optionally, the chip 2000 may further comprise an input interface 2030. The processor 2010 may control the input interface 2030 to communicate with other devices or chips, and specifically, may obtain information or data sent by the other devices or chips.

Optionally, the chip 2000 may further include an output interface 2040. The 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 the network device or the UE in the embodiment of the present invention, and the chip may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present invention, and for brevity, details are not described here again.

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

It should be understood that the processor of embodiments 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 performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed 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 either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus 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 memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present invention may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present invention 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 in 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 configured to implement corresponding functions implemented by the terminal device in the foregoing method, and the network device 2120 may be configured to implement corresponding functions implemented by the network device in the foregoing method, which is not described herein again for brevity.

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

Optionally, the computer-readable storage medium may be applied to the network device or the UE in the embodiment of the present invention, and the computer program enables the computer to execute corresponding processes implemented by the network device in the methods in the embodiments of the present invention, which are not described herein again for brevity.

Embodiments of the present invention also provide a computer program product, which includes computer program instructions.

Optionally, the computer program product may be applied to the network device or the UE in the embodiment of the present invention, and the computer program instruction causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present invention, which is not described herein again for brevity.

The embodiment of the invention also provides a computer program.

Optionally, the computer program may be applied to the network device or the UE in the embodiment of the present invention, and when the computer program runs on a computer, the computer is enabled to execute corresponding processes implemented by the network device in the methods in the embodiment of the present invention, which is not described herein again 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 implementation. 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 is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered 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

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

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

the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.
The method of claim 1, wherein the sending at least one piece of information related to Always-On feature to the UE comprises:

sending a policy container to the UE; wherein the policy container carries a first URSP policy; the first URSP strategy carries a first indication, and the first indication is used for UE to judge whether to bind the service to the session of Always-On characteristics.
The method of claim 2, wherein the first indication is carried in an RSD in the first URSP policy.
The method of claim 2, wherein the sending the policy container to the UE further comprises:

and transmitting the policy container to the UE through the third network equipment.
The method according to any one of claims 2-4, wherein the method further comprises:

and receiving a policy configuration result carried by the UE through the policy container.
The method of claim 2, wherein the method further comprises:

and receiving indication information for setting Always-On characteristics sent by the UE.
The method of claim 6, wherein the receiving the indication information for setting Always-On feature sent by the UE comprises:

and receiving indication information for setting Always-On characteristics, which is sent by the UE in an initial session establishment process or a session modification process.
The method of claim 1, wherein the method further comprises:

and configuring the corresponding relation for the UE.
The method of claim 8, wherein the correspondence is: a first correspondence;

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

or, the first corresponding relation is a corresponding relation between at least one parameter in the PDU session attribute and the first class service; the first type of service is a service capable of setting Always-On characteristic session.
The method of claim 9, wherein the at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.
The method of claim 8, wherein the method further comprises:

the QoS parameters are transmitted.
The method of claim 11, wherein the correspondence is: a second correspondence;

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

or the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the Always-On characteristic.
The method of any one of claims 1-12, wherein the method further comprises:

and receiving a third indication sent by the UE for indicating the number of Always-On sessions.
A session setting method is applied to UE and comprises the following steps:

receiving at least one piece of information related to Always-On characteristics; the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.
The method of claim 14, wherein said receiving at least one information related to Always-On features comprises:

receiving a policy container; wherein the policy container carries a first URSP policy; the first URSP strategy carries a first indication;

the method further comprises the following steps:

and the UE judges whether to bind the service to the session with Always-On characteristic based On the first indication.
The method of claim 15, wherein the first indication is carried in an RSD in the first URSP policy.
The method of claim 16, wherein the method further comprises:

and receiving the policy container transmitted by the first network device and transparently transmitted by the third network device.
The method of claim 17, wherein the method further comprises:

and when the network equipment is in the idle state, switching from the idle state to the connection state based on a service request process triggered by the third network equipment.
The method of claim 15, wherein the method further comprises:

and sending indication information for setting Always-On characteristics to the first network equipment.
The method of claim 19, wherein said sending an indication to the first network device to set Always-On characteristics comprises:

and in the initial session establishing process or the session modifying process, sending indication information for setting Always-On characteristics to the first network equipment.
The method of claim 14, wherein the method further comprises:

and determining to set the PDU session as a permanent open Always-On feature based On the at least one parameter related to the PDU session and the corresponding relation.
The method of claim 21, wherein the correspondence is: a first correspondence;

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

or, the first corresponding relation is a corresponding relation between at least one parameter in the PDU session attribute and the first class service; the first type of service is a service capable of setting Always-On characteristic session.
The method of claim 22, wherein at least one parameter in the PDU session attribute comprises at least one of: S-NSSAI, DNN.
The method of claim 21, wherein the correspondence is: and the network side sends the information to the UE, or the UE is configured in advance.
The method of claim 24, wherein the method further comprises:

receiving a first correspondence sent via a UCU message.
The method of claim 24, wherein the method further comprises:

a first correspondence sent via a registration reply message is received.
The method of claim 21, wherein the method further comprises:

QoS parameters are received.
The method of claim 27, wherein the method further comprises:

and sending a PDU session establishment request message, and receiving the QoS parameter carried in the PDU session establishment request reply message by the network side.
The method of claim 27, wherein the correspondence is: a second correspondence;

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

or the second corresponding relation is a corresponding relation between at least one of the QoS parameters and the Always-On characteristic.
The method of claim 29, wherein the method further comprises:

when it is determined that the PDU session needs to be set to Always-On feature, a first request for setting the PDU session to Always-On feature is transmitted through a session modification request message.
The method of claim 30, wherein the method further comprises:

receiving feedback information for the first request, and determining whether to set the PDU session to Always-On feature based On the feedback information.
A session setting method is applied to UE and comprises the following steps:

and sending a third indication to the network side, wherein the third indication is used for indicating the number of Always-On sessions.
A session setting method applied to a second network device comprises the following steps:

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

sending an indication to the UE when it is determined that the PDU session of the UE is set to Always-On feature; wherein the indication is to inform the UE to set the PDU session to Always-On.
The method of claim 33, wherein the PDU session-related information of the UE comprises at least one of:

the method comprises the steps of session establishment parameters reported by UE, user subscription information corresponding to the UE, PCC strategies and local configuration.
The method of claim 34, wherein the method further comprises:

receiving a session establishment request sent by UE;

correspondingly, the sending the indication to the UE includes:

sending a session establishment reply message carrying a first indication to the UE; wherein the first indication is to instruct the UE to set a PDU session to Always-On feature.
The method of claim 35, wherein the method further comprises:

and after the first indication is sent, receiving Always-on PDU session request identification carried in the PDU session modification request message by the UE.
The method of claim 35, wherein the sending an indication to the UE comprises:

sending a notification message to the UE, wherein the notification message carries a first parameter; the first parameter comprises the identification whether the Always-On session needs to be established or not and/or the Always-On session needs to be established.
The method of claim 35, wherein the notification message is: proprietary NAS messages, or paging messages.
The method of claim 37, wherein the method further comprises:

receiving a session modification request sent by UE, wherein the session modification request carries an indication that the PDU session is Always-On characteristic.
The method of any one of claims 33-39, wherein the method further comprises:

and receiving a third indication sent by the UE for indicating the number of Always-On sessions.
The method of any one of claims 33-39, wherein the method further comprises:

sending a second indication indicating the number of Always-On sessions to the UE.
A first network device, comprising:

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

the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.
The first network device of claim 42, wherein the first communication unit is to transmit a policy container to the UE; wherein the policy container carries a first URSP policy; the first URSP strategy carries a first indication, and the first indication is used for judging whether the UE binds the service to the session of Always-On characteristics.
The first network device of claim 43, wherein the first indication is carried in an RSD in the first URSP policy.
The first network device of claim 43, wherein the first communication unit is to transparently transmit the policy container to the UE through a third network device.
The first network device of any one of claims 43-45, wherein the first communication unit is configured to receive a policy configuration result carried by the UE via a policy container.
The first network device of claim 43, wherein the first communication unit receives indication information sent by the UE to set Always-On characteristics.
The first network device of claim 47, wherein the first communication unit receives indication information for setting Always-On feature sent by the UE in an initial session setup procedure or a session modification procedure.
The first network device of claim 42, wherein the first communication unit configures a correspondence for a UE.
The first network device of claim 49, wherein the correspondence is: a first correspondence;

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

or, the first corresponding relation is a corresponding relation between at least one parameter in the PDU session attribute and the first class service; the first type of service is a service capable of setting Always-On characteristic session.
The first network device of claim 50, wherein the at least one parameter in the PDU session attributes comprises at least one of: S-NSSAI, DNN.
The first network device of claim 49, wherein the first communication unit is to transmit QoS parameters.
The first network device of claim 52, wherein the correspondence is: a second correspondence;

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

or the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the Always-On characteristic.
The first network device of any one of claims 42-53, wherein the first communication unit is to receive a third indication indicating the number of Always-On sessions sent by the UE.
A UE, comprising:

a second communication unit receiving at least one information related to Always-On feature; the at least one piece of relevant information is used for the UE to judge whether to bind the service to the session of the Always-On feature, or to judge whether to set the PDU session as the Always-On feature, or to contain a second indication for indicating the number of Always-On sessions.
The UE of claim 55, wherein the second communication unit is to receive a policy container; wherein the policy container carries a first URSP policy; the first URSP strategy carries a first indication, and the first indication is used for judging whether to bind the service to the session of Always-On characteristics.
The UE of claim 56, wherein the first indication is carried in an RSD in the first URSP policy.
The UE of claim 56, wherein the second communication unit is to receive a policy container sent by the first network device that is transparently transmitted by the third network device.
The UE of claim 56, wherein the UE further comprises:

and the second processing unit is used for switching 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.
The UE of claim 56, wherein the second communication unit is to transmit an indication to set Always-On characteristics to the first network device.
The UE of claim 60, wherein the second communication unit is configured to send, to the first network device, indication information for setting Always-On feature in an initial session establishment procedure or a session modification procedure.
The UE of claim 55, wherein the UE further comprises:

and the second processing unit is used for determining to set the PDU session as a permanent Always-On characteristic based On the at least one parameter related to the PDU session and the corresponding relation.
The UE of claim 62, wherein the correspondence is: a first correspondence;

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

or, the first corresponding relation is a corresponding relation between at least one parameter in the PDU session attribute and the first class service; the first type of service is a service capable of setting Always-On characteristic session.
The UE of claim 63, wherein at least one parameter in the PDU session attributes comprises at least one of: S-NSSAI, DNN.
The UE of claim 62, wherein the correspondence is: and the network side sends the information to the UE, or the UE is configured in advance.
The UE of claim 65, wherein the second communication unit is to receive the first correspondence sent via a UCU message.
The UE of claim 65, wherein the second communication unit is to receive the first correspondence sent via a registration reply message.
The UE of claim 62, wherein the second communication unit receives a QoS parameter.
The UE of claim 68, wherein the second communication unit sends a PDU session setup request message, and receives the QoS parameter carried in a PDU session setup request reply message by the network side.
The UE of claim 68, wherein the correspondence is: a second correspondence;

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

or the second corresponding relation is the corresponding relation between at least one parameter in the QoS parameters and the Always-On characteristic.
The UE according to claim 70, wherein the second communication unit transmits a first request for setting the PDU session to Always-On feature through a session modification request message when it is determined that the PDU session needs to be set to Always-On feature.
The UE of claim 71, wherein the second communication unit is to receive feedback information for the first request;

the second processing unit determines whether to set the PDU session to Always-On feature based On the feedback information.
A UE, comprising:

and the fourth communication unit is used for sending a third indication for indicating the number of Always-On sessions.
A second network device, comprising:

the third processing unit is used for determining whether the PDU session of the UE is set to Always-On characteristics or not based On the PDU session related information of the UE;

a third communication unit which transmits an instruction to the UE when it is determined that the PDU session of the UE is set to Always-On characteristic; wherein the indication is to inform the UE to set the PDU session to Always-On.
The second network device of claim 74, wherein the PDU session related information for the UE includes at least one of:

the method comprises the steps of session establishment parameters reported by UE, user subscription information corresponding to the UE, PCC strategies and local configuration.
The second network device of claim 75, wherein the third communication unit receives a session establishment request from a UE;

sending a session establishment reply message carrying a first indication to the UE; wherein the first indication is to instruct the UE to set a PDU session to Always-On feature.
The second network device of claim 76, wherein the third communication unit, after sending the first indication, receives an Always-on PDU session request identifier carried by the UE in a PDU session modification request message.
The second network device of claim 74, wherein the third communication unit sends a notification message to the UE, and the notification message carries the first parameter; the first parameter comprises the identification whether the Always-On session needs to be established or not and/or the Always-On session needs to be established.
The second network device of claim 78, wherein the notification message is: proprietary NAS messages, or paging messages.
The second network device of claim 78, wherein the third communications unit receives a session modification request sent by the UE, and the session modification request carries an indication that the PDU session is Always-On.
The second network device of any of claims 74-80, wherein the third communication unit is configured to receive a third indication indicating the number of Always-On sessions sent by the UE.
The second network device of any of claims 74-80, wherein the third communication unit is to send a second indication to the UE indicating a number of Always-On sessions.
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 and the processor is adapted to call and run the computer program stored in the memory to perform the steps of the method according to any of claims 1-13, 33-41.
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 and the processor is adapted to call and run the computer program stored in the memory to perform the steps of the method according to any of claims 14-32.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1-13, 33-41.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 14-32.
A computer readable storage medium for storing a computer program for causing a computer to perform the steps of the method according to any one of claims 1 to 41.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 41.
A computer program for causing a computer to perform the method of any one of claims 1-41.