WO2021007734A1

WO2021007734A1 - Session setting method, network device, and user equipment

Info

Publication number: WO2021007734A1
Application number: PCT/CN2019/095897
Authority: WO
Inventors: 许阳; 杨皓睿
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-07-12
Filing date: 2019-07-12
Publication date: 2021-01-21
Also published as: CN113412665B; CN113412665A

Abstract

Disclosed in the present invention are a session setting method, a UE, a network device, a chip, a computer-readable storage medium, a computer program product, and a computer program. The method comprises: sending at least one piece of information related to an Always-On feature to the UE, wherein the at least one piece of related information is used by the UE to determine whether to bind a service to a session having the Always-On feature or to determine whether to enable a PDU session to have the Always-On feature, or comprises a second indication for indicating the number of Always-On sessions.

Description

A session setting method, network equipment and user equipment

Technical field

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

Background technique

An Always-on (Protocol Data Unit) session refers to a user plane resource that must be activated every time the UE transitions from the CM-idle state to the CM-connected state. When the PDU session is set 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, there is no solution for how to set the "Always-on" feature.

Summary of the invention

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

In the first aspect, a session setting method is provided, which is applied to a first network device, including:

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

Wherein, the at least one piece of related information is used by the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to set the PDU session to be permanently enabled with the Always-On feature, or to indicate the Always-On feature. On the second indication of the number of sessions.

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

At least one piece of information related to the Always-On feature is received; wherein the at least one piece of related information is used for the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to set the PDU session to be permanently open The Always-On feature, or a second indication used to indicate the number of Always-On sessions.

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

Based on the UE's PDU session related information, determine whether the PDU session of the UE is set to the Always-On feature;

When it is determined that the PDU session of the UE is set to the Always-On feature, an indication is sent to the UE; wherein the indication is used to notify the UE to set the PDU session to Always-On.

In a fourth aspect, a first network device is provided, including:

The first communication unit sends at least one piece of related information to the UE;

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

The second communication unit receives at least one piece of related information;

The second processing unit judges whether to bind the service to the session with the Always-On feature based on the at least one related information, or is used to judge whether to set the PDU session to permanently open the Always-On feature, or contains an indicator for always -On the second indication of the number of sessions.

In a sixth aspect, a second network device is provided, including:

The third processing unit, based on the PDU session related information of the UE, determines whether the PDU session of the UE is set to the Always-On feature;

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

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

Send a third indication to the network side, where the third indication is used to indicate the number of Always-On sessions.

In an eighth aspect, a UE is provided, including:

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

In a ninth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect, the third aspect, or each implementation manner thereof.

In a tenth aspect, a UE is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.

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

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes any one of the above-mentioned first aspect to the third aspect or each of its implementation modes method.

In a twelfth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the above-mentioned first to fourth aspects or the method in each implementation manner thereof.

In a thirteenth aspect, a computer program product is provided, including computer program instructions that cause a computer to execute any one of the first to fourth aspects above or the method in each implementation manner thereof.

In a fourteenth aspect, a computer program is provided, which, when run on a computer, causes the computer to execute any one of the above-mentioned first to fourth aspects or the method in each implementation manner thereof.

By adopting the above solution, the UE can determine whether to bind the service to the session with the Always-On feature, or whether to set the PDU session to the session with the Always-On feature based on at least one parameter. In this way, it is ensured that the services are bound to the Always-On session in time, thereby improving the time accuracy of these services and ensuring the reliability of the services.

Description of the drawings

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

Figure 2-1 is a schematic flow chart 1 of a session setting method provided by an embodiment of the present invention;

Figure 2-2 is a schematic diagram of the second flow of a session setting method provided by an embodiment of the present invention;

Figure 3-1 is a third schematic flow chart of a session setting method provided by an embodiment of the present invention;

Figure 3-2 is a fourth schematic flowchart of a session setting method provided by an embodiment of the present invention;

Figure 4-1 shows the UE policy acquisition process is one;

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

FIG. 5 is a third schematic flowchart of a session setting method provided by an embodiment of the present invention;

Figure 6 is a schematic diagram of a business request processing flow;

Figure 7 is a schematic diagram of a session establishment process;

FIG. 8 is a fourth schematic flowchart of a session setting method provided by an embodiment of the present invention;

9-11 are schematic diagrams of processing of sending correspondences in different processes according to an embodiment of the present invention;

FIG. 12 is a fifth schematic flowchart of a session setting method provided by an embodiment of the present invention;

FIG. 13 is a sixth flowchart of a session setting method provided by an embodiment of the present invention;

14-15 are schematic diagrams of two processes for sending instructions according to an embodiment of the present invention;

16 is a schematic diagram of the composition structure of a first network device provided by an embodiment of the present invention;

FIG. 17 is a schematic diagram of a UE composition structure provided by an embodiment of the present invention;

18 is a schematic diagram of the composition structure of a second network device provided by an embodiment of the present invention;

FIG. 19 is a seventh schematic flowchart of a session setting method provided by an embodiment of the present invention;

20 is a schematic diagram of another UE composition structure provided by an embodiment of the present invention;

FIG. 21 is a schematic diagram of the composition structure 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 second schematic diagram of a communication system architecture provided by an embodiment of the present application.

Detailed ways

In order to have a more detailed understanding of the features and technical content of the embodiments of the present invention, the implementation of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The attached drawings are for reference and description purposes only and are not used to limit the embodiments of the present invention.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the 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 UE 120 (or called a communication terminal or a terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with UEs located in the coverage area. Optionally, the network equipment 110 may be a network equipment (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network equipment (NodeB, NB) in a WCDMA system, or an evolution in an LTE system Type network equipment (Evolutional Node B, eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment may be a mobile switching center, a relay station, an access point, In-vehicle devices, wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one UE 120 located within the coverage area of the network device 110. "UE" as used herein includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another UE's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A UE set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal".

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between UEs 120.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

In order to understand the features and technical content of the embodiments of the present invention in more detail, the implementation of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and description purposes only, and are not used to limit the embodiments of the present invention.

The embodiment of the present invention provides a session setting method, which is applied to a first network device, as shown in Figure 2-1, including:

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

The embodiment of the present invention provides a session setting method, which is applied to a UE, as shown in Figure 2-2, including:

Step 121: Receive at least one piece of information related to the Always-On feature;

In the solution provided in this embodiment, the information related to the Always-On feature may be the route selector (RSD, Route Selection Descriptors) of the first UE path selection policy (URSP, UE Route Selection Policy) contained in the policy container. The parameter, or, can be a corresponding relationship.

The following describes the solution provided in this embodiment in multiple scenarios:

scene 1,

The embodiment of the present invention provides a session setting method, which is applied to a first network device, as shown in Figure 3-1, including:

Step 201: Send a policy container to the UE; wherein the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used by the UE to determine whether to bind the service to On conversations with Always-On characteristics.

This embodiment also provides a session setting method, which is applied to the UE, as shown in Figure 3-2, including:

Step 301: Receive a policy container; wherein the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used to determine whether to bind the service to Always-On Characteristics of the conversation.

Step 302: The UE determines whether to bind the service to the session with the Always-On feature based on the first indication.

Further, it may also include: feeding back the policy configuration result to the first network device.

It needs to be pointed out that the first indication is carried in the 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 feature session refers to the user plane resource that must be activated every time the UE transitions from the CM-IDLE state to the CM-CONNECTED state. Based on an instruction from the upper layer of the UE, the UE may set the session as an Always-on PDU session during the process of requesting the establishment of a PDU session (that is, the PDU session establishment request message carries an Always-on PDU Session Requested). SMF will determine whether the session requested by the UE is established as an Always-on. In roaming scenarios, V-SMF will also participate in determining whether the session can be set to Always-on. After the UE moves from EPS to 5GS, the UE can send the PDU session modification process to the network-side SMF and include the Always-on PDU Session Requested parameter, requesting that the PDU session be set as an Always-on session, and the SMF can determine whether it can be set to Always- on the right to the session.

When a certain PDU session is set 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.

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

The UE strategy may include ANDSP (ANDSP strategy further includes WLANSP and/or N3IWF/ePDG network element selection strategy) and URSP strategy. This embodiment mainly adopts the URSP strategy.

Among them, the configuration method of the UE policy can be shown in Figure 4-1. The UE policy is through the user equipment configuration update (UCU, UE Configuration Update) process defined by 3GPP. The PCF puts the UE policy (Policy) to be updated in a container (Container). ), sent to AMF, AMF uses NAS message to directly forward to UE.

For the UE policy configuration, the reason value of "UE policy container" has been introduced in both downlink NAS and uplink NAS messages, as shown in Figure 4-2. Further, the bit arrangement is 4321, and examples of the reason value are as follows: 0000, which identifies N1 SM information; 0010 is SMS; 0011 is LTE Positioning Protocol (LLP, LTE Positioning Protocol) information container; 0100 is SOR transparent transmission container; 0101 It is the UE policy container; 0110 is the UE parameter update transparent transmission container; 1111 is the multiple load; the remaining reason value is reserved.

Based on Figure 4-1 and Figure 5, taking the first network device as PCF and the third network device as AMF as an example, the solution provided in this embodiment will be described in detail:

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

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

In this embodiment, the first URSP policy is used to provide the UE with an indication of whether to bind the Always-On feature, that is, it is enhanced on the basis of the existing URSP policy, that is, whether to add is added to the RSD list of the existing URSP policy Always-On instructions.

Combine Table 1 and Table 2 to describe the first URSP strategy and the RSD list therein. Among them, Table 1 shows the contents of multiple rules included in the first URSP policy, and the contents of the RSD list in Table 1 refer to Table 2; Table 2 shows the specific contents of the RSD list in the first URSP policy , It needs to be pointed out that the Always-On indication has been added to the RSD list:

Table 1

Table 2

The "Always-On indication" in Table 2 is a newly added parameter in this embodiment, and this parameter can be used to indicate whether the UE binds the application data corresponding to the service descriptor of the URSP rule to the Always-On session. For example, when it is 1, it can indicate that the service is bound to the session with the Always-On feature, and when it is 0, it can indicate that the service is not bound to the session with the Always-On feature. In addition, it should be noted that if there is a session with the Always-On feature, you can directly bind the service to the session; if there is no session with the Always-On feature, you can create a new Always-On session Characteristic session, and then bind the business to the newly created session.

Specifically, the Traffic Descriptor in the URSP rules is used to describe a specific service. For example, the microblog service can be described in the range of IP 1-9, and the IMS service can be described by IMS DNN. Then, there can be one or more RSDs (route selectors) under a service descriptor, and each RSD corresponds to the attribute of a PDU session, that is to say, the service data corresponding to the service descriptor can run on the PDU session corresponding to the RSD in.

Step 2. After the AMF receives the message of step 1, if the UE is currently in the CM-IDLE state, the service request process is triggered to allow the UE to return to the CM-CONNECTED state to transfer the policy container; that is, when the UE is in the idle state , Based on the service request process triggered by the third network device (AMF), switch from the idle state to the connected state.

Among them, the service request process can be used for the UE in the CM-IDLE state to send uplink signaling messages, user data or reply to network paging requests. After completing the service request process and activating the user plane connection, the UE enters the CM-CONNECTED state. In addition, the service request process is also used for the CM-CONNECTED UE to initiate activation of inactive user plane links (such as PDU sessions) and reply to NAS notification messages from AMF. When the user plane connection is activated, the AS layer of the UE will notify the NAS layer.

Refer to Figure 6 to explain the service request process: the parameters that need to be carried in the first message (Service Request) message can include: AN parameters, Service Request (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, 5G-S-TMSI, [NAS message container], Exempt Indication. Among them, AN Parameter is the parameter that the UE sends to the base station at the AS layer, such as GUTI information, network slice information, etc., and the following Service Request is a NAS message. It is transparently transmitted by the base station to the AMF. The parameter that is strongly related to this patent is the List Of PDU Sessions To Be Activated parameter, which is the PDU session that the UE actively requests to reactivate. In addition, List Of Allowed PDU Sessions is when the UE (passive) receives the request. After the call message or NAS notification message, reply to the network side which allowed PDU sessions.

For 1, 2 and 4 in Figure 6, the Service Request message will be transparently transmitted to the SMF. After the internal interaction of the network side, especially the interaction between the SMF and the RAN, the SMF determines which UE requests List Of PDU Sessions To Be Activated, And put it in the Service Accept message and return it to the UE through 11, 12 and 13.

Step 3: When the UE is in the CM-CONNECTED state, it sends the message of Step 3, carrying the PoicyContainer in Step 1. The Container does not need to be read in the AMF, and the AMF directly encapsulates the Container in a NAS message and sends it to the UE.

Step 4-5: The first network device (ie, PCF) receives the policy configuration result carried by the UE through the policy container. Correspondingly, the UE returns the result of the policy configuration to the PCF through this message. Similarly, the result of the configuration is transparently transmitted to the PCF in the Policy Container.

Here, the UE processing also needs to bind the service to the session with the Always-On feature based on the first URSP strategy.

The specific processing method for the UE to bind the service to the corresponding PDU session for transmission based on the URSP strategy can be described as follows:

When data appears at the application layer, the UE uses the URSP rule in the URSP policy to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rule, and the order of viewing is in accordance with the Precedence ( Priority) is determined, that is, the UE checks the matching situation in sequence based on the order of priority. When a URSP rule is matched, the RSD list under the URSP rule is used to bind the PDU session.

When a URSP rule is matched, the UE searches for a suitable PDU session according to the Precedence order in the RSD. The RSD with higher priority is preferentially used here. If a parameter in the RSD has one or more values, the UE selects One of them is combined with other parameters to find whether the PDU session exists:

If it exists, bind the application data to the session for transmission;

If it does not exist, 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 will bind the application data to the session for transmission; if the session is not established successfully, the UE will search again based on other parameter combinations in the RSD or using the parameter combination in the second priority RSD Whether the PDU session exists.

If a suitable PDU session cannot be found for binding according to the matched URSP rule, the UE searches for the Traffic Descriptor in the second-priority URSP rule according to the Precedence order to see if it can match the application data stream characteristics. When it matches, repeat The previous process.

The above process of finding a suitable PDU session for the application can be called "evaluation". After finding a suitable PDU session binding, the UE will re-execute the evaluation in at least one of the following situations to view the original application data and the PDU session Does the binding relationship need to be changed:

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

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

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

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

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

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

In addition, this embodiment may also include: receiving indication information for setting the Always-On feature sent by the UE.

Specifically, it is: receiving the indication information for setting the Always-On attribute sent by the UE during the initial session establishment process or the session modification process.

That is, the UE can carry an "Always-on" indication during the initial PDU session establishment or session modification process. The network side can accept or reject whether the PDU session can be Always-on. It can be considered that Always-on is a type of PDU session. Feature, and then use the aforementioned processing procedure to bind the service to the session with the Always-On feature, and then send an instruction to the UE. In this way, after the established PDU session is Always-on, every subsequent UE transitions from CM-IDLE to CM-CONNECTED state, the PDU session with Always-on must be activated. That is, when the UE transitions from CM-IDLE to CM-CONNECTED, the sent Service Request message carries the identifier of the "Always-on" PDU session, so that the network side can activate the PDU session.

For example, the aforementioned services are bound to sessions with the Always-On feature, and the targeted services may at least include: PDU sessions for low-latency and high-reliability services (URLLC), and time synchronization services (Time Sync) The PDU session and some PDU sessions that deliver time sensitive services (TSN) need to be set to Always-on.

Regarding the PDU session establishment process, as shown in Figure 7, the most important thing for the UE side is the PDU session establishment request message and the received reply message.

Step 1: The PDU session establishment request message is sent by the UE to the AMF and SMF through the NAS message. The NAS message can 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 the AMF that further sends the container to SMF, which mainly contains information related to session characteristics. In this step, the UE can add the "Always-on is requested" flag to instruct SMF to establish an Always-on PDU session .

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

Step 3-10, SMF decides whether to establish the PDU session based on the NAS message from the UE, subscription information, dynamic or local static policy (because it is an internal behavior on the network side, the specific process will not be described in detail)

Step 11-13: The SMF sends a message to the RAN, which mainly includes N1 SM Container(PDU Session Establishment Accept([QoS Rule(s) and QoS Flow level QoS parameters if required for the QoS Flow(s) associated with the QoS rule( s), N2 SM information(PDU Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, Session-AMBR, PDU Session Type, User Plane Security Enforcement Information, UE Integration Protection Maximum Data Rate, RSN), [Always-on PDU Session Granted], selected SSC mode, S-NSSAI(s), DNN, allocated IPv4 address, interface identifier, Session-AMBR, selected PDU Session Type, [Reflective QoS Timer ](if available),[P-CSCF address(es)],[Control Plane Only indicator], [Header Compression Configuration] and other parameters. According to this, the RAN will send the N1 SM Container to the UE, and the N2 SM Information for itself For air interface bearer establishment and use, other parameters such as [Always-on PDU Session Granted] are also sent to the UE.

In addition, if the UE does not request Always-on in the PDU Session Establishment Request, SMF can decide to set it to Always-on by itself, so that [Always-on PDU Session] is added to the Session Establishment Accept message in the PDU. Granted] (Always-On PDU session authorization).

Finally, it needs to be pointed out in this embodiment that this embodiment is aimed at the binding of the Always-On feature of the session, but in actual processing, there may also be binding of more other features or binding of more attributes. The processing method adopted can be the same as the foregoing solution, but it is not exhaustive in this embodiment. In addition, this embodiment illustrates several services that are bound to the session with the Always-On feature, but in fact, it can also be applied to the determination of any other session that can enable the Always-On service. This embodiment also Do not exhaustively.

In addition, the solution provided in this embodiment may further include: the first network device sends a second indication for indicating the number of Always-On sessions to the UE. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side, and accordingly, the UE determines the number of Always-on feature PDU sessions that can be requested according to the second indication.

In addition, the UE may also send a third indication for indicating the number of Always-On sessions to the first network device; that is to say, the indication may also be sent by the UE to the network side, and the network side may decide to be able to The number of received PDU sessions corresponding to the Always-on feature of the same UE.

Scenario 2: Configure the corresponding relationship for the UE.

The details can be shown in Figure 8:

Step 401: The UE receives at least one parameter related to the PDU session;

Step 402: Based on the at least one parameter related to the PDU session and the corresponding relationship, determine to set the PDU session to permanently enable the Always-On feature.

The UE receives the URSP rule; in turn, the UE can determine whether to set the PDU session as the Always-On feature according to the network slicing parameter (NSSAI) and/or the DNN parameter of the RSD list in the URSP rule configured on the network side.

The corresponding relationship is: a first corresponding relationship;

Wherein, the first correspondence is the correspondence between at least one parameter in the PDU session attribute and the Always-On feature;

Alternatively, the first correspondence is a correspondence between at least one parameter in the PDU session attribute and a first type of service; wherein, the first type of service is a service capable of setting an Always-On feature session.

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

That is to say, the UE can match the multiple parameters included in the RSD list in the URSP rule with the first correspondence relationship with at least one parameter specified in the URSP rule, and when it matches with at least one parameter specified in the first correspondence relationship When these parameters are matched, it can be determined that the first correspondence relationship is satisfied, and then it is determined that the PDU session can be set to the Always-On feature according to the first correspondence relationship.

Alternatively, the UE may match the first correspondence with at least one parameter specified in the URSP rule according to multiple parameters included in the RSD list in the URSP rule, when it matches with at least one specified in the first correspondence When the parameters are matched, it can be determined that the first correspondence is satisfied, and then the PDU session is determined as the PDU session of the first type of service according to the first correspondence, and the PDU session of the first type of service can be set to the Always-On feature.

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

For example, the UE receives the URSP rule and uses the parameters in the URSP rule as the parameters of the PDU session attribute. When the RSD in the URSP rule-1 contains specific S-NSSAI-1 and/or DNN-1, the UE will One correspondence (for example, the correspondence between S-NSSAI-1 and/or DNN-1 and Always-On features, or the correspondence between S-NSSAI-2 and/or DNN-2 and the first type of service), judge The session is to perform a specific service (such as URLLC service), and whether the PDU session that needs to be bound is an Always-on feature, or it is directly determined whether it needs to be bound to an Always-on PDU session.

Further, the binding of services to the PDU session in this example can be understood as transmitting specific data 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 correspondence" (ie the correspondence between S-NSSAI and/or DNN and the "Always-on" attribute; or the correspondence between S-NSSAI and/or DNN and the service) can be dynamically sent to the terminal through the network side , It can also be statically configured in the terminal.

Among them, for the dynamic transmission to the terminal, the following manners may be selected: receiving the first correspondence sent through the UCU message, or receiving the first correspondence sent through the registration reply message. Specifically:

Manner 1: Send according to the UCU message. The UCU message may be a UCU message triggered by AMF or a UCU message triggered by PCF.

For example, as shown in Figure 9, when the AMF (that is, the third network device) sends the configuration update instruction to the UE, it carries the first corresponding relationship; then the UE sends the UE configuration update complete to the AMF, and AMD sends the relevant Information and update RAN.

For another example, as shown in Figure 10, the information sent to the AMF through the PCF carries the first corresponding relationship, and then the AMF triggers the service request process so that the UE enters the connected state, transmits the UE policy container to the UE, and carries the first correspondence in the policy container. Correspondence: The UE performs subsequent processing based on the first correspondence.

Method 2: Send to the terminal in the registration reply message. As shown in Figure 11, the registration process has been described above and will not be repeated here. In the process shown in FIG. 11, the AMF feeds back the registration received information to the UE and carries the first correspondence.

Another processing method is that the UE receives QoS parameters.

After establishing the PDU session, the UE decides to set it to Always-on according to the configured QoS information.

This example is different from the foregoing example in that this example sends a PDU session establishment request message, and receives the QoS parameters carried in the PDU session establishment request reply message on the network side. That is, the UE receives the QoS information sent by the network side after the session establishment request, and then determines whether to set the PDU session as an Always-On feature session according to the QoS parameters and the second correspondence. That is, the UE sends a PDU session establishment request message; and then receives QoS parameters related to the PDU session.

In this example, the corresponding relationship is: the second corresponding relationship;

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service;

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

The UE matches the received QoS parameter with the second correspondence relationship. When the QoS parameter matches the second correspondence relationship, it may be determined to set the PDU session as the Always-On feature based on the second correspondence relationship; or, the second correspondence relationship is When at least one of the QoS parameters corresponds to the first type of service, it can be matched according to the content contained in the received QoS parameter and the parameter contained in the second correspondence. When it matches, it can be determined that the PDU session is the first For a session of a type of service, it is determined that the PDU session needs to be set to the Always-On feature.

In addition, when determining to set the PDU session to the Always-On feature, the UE may send a first request to set the PDU session to the Always-On feature through a session modification request message; and then receive feedback information for the first request, based on The feedback information determines whether to set the PDU session as an Always-On feature.

As shown in Figure 12, according to the PDU session establishment request message sent by the UE and the received QoS information, it is determined whether the session needs to be set to Always-on. If necessary, the UE sets the session to Always-on.

The second correspondence management can be understood as a QoS rule, and the SMF will send out the QoS rule that needs to be sent to the UE through the NAS message through steps 11, 12, and 13 in the PDU session establishment process shown in FIG. 7. That is, in step 11, the SMF sends the N1 SM container to the AMF, and the container contains PDU Session Establishment Accept([QoS Rule(s) and QoS Flow level QoS parameters if required for the QoS Flow(s) associated with the QoS rule(s)]. Here QoS parameter (i.e. QoS parameter) is used to describe the QoS Flow characteristics in the PDU session, including 5QI, ARP, RQA, Aggregate Bit Rates, Notification control, flow bit rate, Maximum Packet Loss Rate, etc. , Or the UE derives its own static QoS parameters according to the message returned by the SMF. In any case, the UE determines whether it needs to be set to Always-on according to the QoS parameters of the data flow of the PDU session. Typical QoS parameters and specific services are as follows 3 shown.

In addition, in addition to the PDU session establishment process, 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 process, and the UE can also decide whether to set up the PDU session based on this It is Always-on.

For example, for an eMBB application corresponding to 5QI=80, the UE can determine that the session needs to be set to Always-on according to a specific 5QI value (for example, 5QI=80). For another example, the QoS flow with 5QI=82-85 requires Delay Critical GBR, and the UE can consider that the PDU session where the Delay Critical GBR data flow is located needs to be set to Always-on.

table 3

The above example is based on 5QI processing. In fact, other parameters in the QoS parameters can also be used. For example, the stream bit rate, the maximum packet loss rate (Maximum Packet Loss Rate), etc. can be used. For example, it can be set to There is a second correspondence between the bit rate-1 and the Always-On feature, or alternatively, a second correspondence between the packet loss rate and the Always-On feature (or the first type of service) within a certain range can be set.

In combination with the PDU session establishment process shown in Figure 7, when the UE decides to set the PDU session to Always-on according to the received QoS parameters, the UE initiates the PDU session modification procedure. According to the existing procedure, the UE requests the PDU session modification request Add the "Always-on is request" parameter to the message to request the network side to set it as an Always-on session, and the network side can decide whether to set it to Always-on eventually.

In addition, the solution provided in this embodiment may further include: the UE receives a second indication for indicating the number of Always-On sessions. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side, and accordingly, the UE determines the number of Always-on feature PDU sessions that can be requested according to the second indication. The network side may be the second network device, the first network device, or the third network device on the network side, that is, it may be PCF, AMF, or SMF, which is not limited in this embodiment.

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

It can be seen that by adopting the above solution, the UE can determine whether to set the PDU session as the Always-On feature according to the corresponding relationship. In this way, it is ensured that the service session is bound to the Always-On session in time, thereby improving the time accuracy of these services and ensuring the reliability of the service.

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

Step 501: Based on the UE's PDU session related information, determine whether the PDU session of the UE is set to the Always-On feature;

Step 502: When it is determined that the PDU session of the UE is set to the Always-On feature, send an indication to the UE; wherein the indication is used to notify the UE to set the PDU session to Always-On.

In this embodiment, the second network device may be an SMF.

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

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

Correspondingly, the SMF can decide whether to set the session to Always-on according to the session establishment parameters such as S-NSSAI and DNN reported by the UE, as well as the user's subscription information, PCC policy, and local configuration. That is to say, even if the UE does not indicate that it needs to be set to Always-on in the request message, SMF can still set it to Always-on for its decision, so that the network side has enough ability to judge, and does not need to be sent to the UE to judge .

Specifically, the manner in which the second network device (SMF) on the network side sends an indication for the UE may have the following multiple processing methods:

Manner 1. As shown in Figure 14, the UE initiates a session establishment request to the second network device, namely SMF, and after the SMF decides to set it to Always-on, it sends a session establishment reply message carrying the first indication to the UE; The first indication is used to instruct the UE to set the PDU session to the Always-On feature.

After sending the first indication, receive the Always-on PDU session request identifier carried in the PDU session modification request message by the UE. For example, as shown in the figure, the session establishment reply message carries the "first indication". After the UE receives the first indication, the UE initiates the PDU session modification process and carries the "Always-on is requested indication", and the SMF agrees according to the existing process The PDU session is set to Always-on.

It should be pointed out that the detailed PDU session establishment and modification process has been described in the foregoing embodiments, and will not be repeated here.

Manner 2: Send a notification message to the UE, the notification message carries a first parameter; wherein, the first parameter includes an identifier of whether an Always-On session needs to be established and/or an Always-On session needs to be established. In other words, the network-side SMF notifies the terminal through a separate message to require the UE to set the session to Always-on

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

As shown in Figure 15, the notification message sent by the network side contains the "first parameter", the notification message may be a dedicated 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 the identification of the Always-on session needs to be established.

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

The PDU session in this embodiment may be a URLLC, TSN service PDU session, of course, it may also be other services, as long as it is necessary to set the Always-On session feature, all services can be included in the protection scope of this embodiment. No more exhaustive list here.

In this way, for important TSN time synchronization services, if it cannot be set to Always-on in time, it will have an important impact on time accuracy. For example, when the UE changes from idle state to connected state, long-term non-time synchronization is required Perform Time Sync immediately so that the network side can adjust the offset time of the clock on the network element in time.

For URLLC services, industrial scenarios are used more, and must be set to Always-on to transfer data in time, otherwise high-reliability specific will not be realized because some sessions are not activated.

In addition, the solution provided in this embodiment may further include: the second network device sends a second indication for indicating the number of Always-On sessions to the UE. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side, and accordingly, the UE determines the number of Always-on feature PDU sessions that can be requested according to the second indication. The network side may be the second network device SMF on the network side.

In addition, the second network device may also receive the third indication sent by the UE to indicate 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 decide according to the indication The number of PDU sessions corresponding to the Always-on feature of the same UE that can be received. Similarly, the network side may specifically be SMF.

It can be seen that by adopting the above solution, the network side can determine whether the session can be set to the Always-On feature according to the UE's PDU session related information. In this way, it is ensured that the service session is bound to the Always-On session in time, thereby improving the time accuracy of these services and ensuring the reliability of the service.

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

The first communication unit 61 sends at least one piece of related information to the UE;

This embodiment also provides a UE, as shown in FIG. 17, including:

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

The second processing unit 72, based on the at least one piece of related information, determines whether to bind the service to the session with the Always-On feature, or is used to determine whether to set the PDU session to permanently open the Always-On feature, or contains instructions for The second indication of the number of Always-On sessions.

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

scene 1,

The first communication unit 61 of the first network device sends a policy container to the UE; wherein the policy container carries a first URSP policy; the first URSP policy carries a first indication, and the first indication is used for Assist the UE to determine whether to bind the service to the session with the Always-On feature.

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 policy carries a first indication, The first indication is used to assist the UE in determining whether to bind the service to the session with the Always-On feature.

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

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

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

If the UE is currently in the CM-IDLE state, the third network device triggers the service request process to allow the UE to return to the CM-CONNECTED state to deliver the policy container;

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

When the UE is in the CM-CONNECTED state, the AMF directly encapsulates the Container into a NAS message and sends it to the UE.

The first communication unit 61 of the first network device (ie, 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 this message. Similarly, the result of the configuration is placed in the Policy Container and transparently transmitted to the PCF.

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

This embodiment is aimed at the binding of the Always-On feature of the session, but in actual processing, there may be binding of more other features or binding of more attributes, and the processing method adopted can be the same as the foregoing solution, except This embodiment will not be exhaustive. In addition, this embodiment illustrates several services that are bound to the session with the Always-On feature, but in fact, it can also be applied to the determination of any other session that can enable the Always-On service. This embodiment also Do not exhaustively.

In addition, the function of each unit in this embodiment is the same as the processing flow in the foregoing method embodiment, and will not be repeated.

In addition, the solution provided in this embodiment may further include: the first communication unit of the first network device sends a second indication for indicating the number of Always-On sessions to the second communication unit of the UE. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side, and accordingly, the UE determines the number of Always-on feature PDU sessions that can be requested according to the second indication.

In addition, the second communication unit of the UE may also send a third indication for indicating the number of Always-On sessions to the first network device; that is, the indication may also be sent by the UE to the network side, and the network side may According to the instruction, the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received is determined.

Scene 2,

The second communication unit 71 receives at least one parameter related to the PDU session;

The second processing unit 72, based on the at least one parameter and the corresponding relationship related to the PDU session, determines to set the PDU session to permanently enable the Always-On feature.

The second communication unit 71 receives the URSP rule; furthermore, the UE can determine whether to set the PDU session as the Always-On feature according to the network slicing parameter (NSSAI) and/or the DNN parameter of the RSD list in the URSP rule configured on the network side.

The corresponding relationship is: a first corresponding relationship;

That is to say, the second processing unit 72 of the UE may perform a match based on the multiple parameters contained in the RSD list in the URSP rule, and the first correspondence may be at least one parameter specified in the URSP rule. When at least one parameter specified in the relationship matches, it may be determined that the first correspondence relationship is satisfied, and then it is determined according to the first correspondence relationship that the PDU session can be set as the Always-On feature.

Alternatively, the second processing unit 72 of the UE may perform a match based on the multiple parameters contained in the RSD list in the URSP rule, and the first correspondence may be at least one parameter specified in the URSP rule. When at least one of the specified parameters matches, the first correspondence can be determined to be satisfied, and then the PDU session is determined to be the PDU session of the first type of service according to the first correspondence, and the PDU session of the first type of service can be set to Always- On feature.

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

There is another way in which the UE decides to set it to Always-on according to the configured QoS information after establishing the PDU session.

This example is different from the previous example in that the second communication unit 71 of this example sends a PDU session establishment request message, and receives the QoS parameters carried in the PDU session establishment request reply message on the network side. That is, the UE receives the QoS information sent by the network side after the session establishment request, and then determines whether to set the PDU session as an Always-On feature session according to the QoS parameters and the second correspondence. That is, the UE sends a PDU session establishment request message; and then receives QoS parameters related to the PDU session.

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service; or, the second correspondence is a correspondence between at least one of the QoS parameters and an Always-On feature.

The second processing unit of the UE matches the received QoS parameter with the second correspondence. When the QoS parameter matches the second correspondence, it may be determined to set the PDU session as the Always-On feature based on the second correspondence; or, When the second correspondence is the correspondence between at least one of the QoS parameters and the first type of service, it can be matched according to the content contained in the received QoS parameter and the parameters contained in the second correspondence. When it matches, The PDU session is determined to be the session of the first type of service, and then it is determined that the PDU session needs to be set with the Always-On feature.

In addition, when the UE determines that the PDU session is set to the Always-On feature, the second communication unit 71 sends a first request for setting the PDU session to the Always-On feature through a session modification request message; and then receives the first request for setting the PDU session to the Always-On feature. The requested feedback information is determined based on the feedback information whether to set the PDU session as an Always-On feature.

In addition, the solution provided in this embodiment may further include: the second communication unit of the UE receives a second indication for indicating the number of Always-On sessions. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side. Correspondingly, the second processing unit of the UE can also determine the number of PDU sessions with the Always-on feature that can be requested according to the second indication. . The network side may be the second network device, the first network device, or the third network device on the network side, that is, it may be PCF, AMF, or SMF, which is not limited in this embodiment.

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

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

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

The third communication unit 81, when it is determined that the PDU session of the UE is set to the Always-On feature, sends an indication to the UE; wherein, the indication is used to notify the UE to set the PDU session to Always-On. -On.

In this embodiment, the second network device may be an SMF.

Correspondingly, the third processing unit 82 of the SMF may decide whether to set the session to Always-on according to the session establishment parameters such as S-NSSAI and DNN reported by the UE, as well as the user's subscription information, PCC policy, local configuration, etc. That is to say, even if the UE does not indicate that it needs to be set to Always-on in the request message, SMF can still set it to Always-on for its decision, so that the network side has enough ability to judge, and does not need to be sent to the UE to judge .

Manner 1: The third communication unit 81 receives the session establishment request initiated by the UE to the second network device, that is, the SMF. After the third processing unit of the SMF decides to set it to Always-on, the third communication unit 81 sends to the UE with The first indicated session establishment reply message; wherein, the first indication is used to instruct the UE to set the PDU session as the Always-On feature.

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

Manner 2: The third communication unit 81 sends a notification message to the UE, the notification message carries a first parameter; wherein, the first parameter includes whether an Always-On session needs to be established and/or an Always-On session needs to be established Logo. In other words, the network-side SMF notifies the terminal through a separate message to require the UE to set the session to Always-on

In addition, the solution provided in this embodiment may further include: the third communication unit of the second network device sends a second indication for indicating the number of Always-On sessions to the UE. Due to the capability processing limitations of the UE or the network side, for example, it is possible that the UE or the network side can only activate a certain number of PDU sessions in one Service Request message at the same time, so a second indication for indicating the number of Always-On sessions is introduced That is, "Always_on session quantity indication", the second indication can be sent to the UE by the network side, and accordingly, the UE determines the number of Always-on feature PDU sessions that can be requested according to the second indication. The network side may be the second network device SMF on the network side.

In addition, the third communication unit of the second network device may also receive the 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 The number of PDU sessions corresponding to the Always-on feature of the same UE that can be received can be determined according to the indication. Similarly, the network side may specifically be SMF.

It can be seen that by adopting the above solution, the network side can determine whether the session can be set to the Always-On feature according to the UE's PDU session related information. In this way, it is ensured that the business session is bound to the Always-On session in time, thereby improving the time accuracy of these services and ensuring the reliability of the business.

A session setting method provided by an embodiment of the present invention is applied to a UE, as shown in FIG. 19, and may include:

Step 1001: Send a third indication to the network side, where the third indication is used to indicate 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 the third instruction sent by the UE.

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

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

For example, the second network device, or the first network device, or the third network device receives the 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 For the network side, the network side can determine the number of PDU sessions corresponding to the Always-on feature of the same UE that can be received according to the indication. Similarly, the network side may specifically be 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. The communication device in this embodiment may be specifically the network device or UE in the foregoing embodiment. The communication device 1900 shown in FIG. 21 includes a processor 1910, and the processor 1910 can call and run a computer program from the 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. The processor 1910 can call and run a computer program from the memory 1920 to implement the method in the embodiment of the present invention.

The memory 1920 may be a separate device independent of the processor 1910, or may be integrated in 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. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 1900 may specifically be a network device or a UE in an embodiment of the present invention, and the communication device 1900 may implement the corresponding procedures implemented by the network device in each method of the embodiment of the present invention. For the sake of brevity, it is not here. Repeat it again.

Optionally, the communication device 1900 may specifically be a network device or a UE according to an embodiment of the present invention, and the communication device 1900 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present invention. For the sake of brevity, I will not repeat them here.

FIG. 22 is a schematic structural diagram of a chip according to an embodiment of the present invention. The chip 2000 shown in FIG. 22 includes a processor 2010, and the processor 2010 can call and run a computer program from the 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. The processor 2010 can call and run a computer program from the memory 2020 to implement the method in the embodiment of the present invention.

The memory 2020 may be a separate device independent of the processor 2010, or may be integrated in the processor 2010.

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

Optionally, the chip 2000 may further include an output interface 2040. The processor 2010 can control the output interface 2040 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device or the UE in the embodiment of the present invention, and the chip can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present invention. For brevity, details are not described herein again.

It should be understood that the chip mentioned in the embodiment of the present invention may also be called a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.

It should be understood that the processor in the embodiment of the present invention may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention can be implemented or executed.

It can be understood that the memory in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present invention may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. In other words, the memory in the embodiment of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

FIG. 23 is a schematic block diagram of a communication system 2100 according to an embodiment of the present application. As shown in FIG. 23, the communication system 2100 includes a UE 2110 and a network device 2120.

Wherein, the UE 2110 may be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 2120 may be used to implement the corresponding function implemented by the network device in the above method. For brevity, details are not described herein again.

The embodiment of the present invention also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the network device or UE in the embodiment of the present invention, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention. For brevity, I will not repeat them here.

The embodiment of the present invention also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device or UE in the embodiment of the present invention, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention. For brevity, This will not be repeated here.

The embodiment of the present invention also provides a computer program.

Optionally, the computer program can be applied to the network device or UE in the embodiment of the present invention. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present invention. For brevity, I won't repeat them here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided by the present invention, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. It should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

A session setting method, applied to a first network device, includes:

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

Wherein, the at least one piece of related information is used by the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to set the PDU session to be permanently enabled with the Always-On feature, or to indicate the Always-On feature. On the second indication of the number of sessions.
The method according to claim 1, wherein the sending at least one piece of information related to the Always-On feature to the UE comprises:

Send a policy container to the UE; wherein the policy container carries the first URSP policy; the first URSP policy carries a first indication, and the first indication is used by the UE to determine whether to bind the service to Always-On Characteristics of the conversation.
The method according to claim 2, wherein the first indication is carried in an RSD in the first URSP policy.
The method according to claim 2, wherein the sending the policy container to the UE further comprises:

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

Receive the policy configuration result carried by the UE through the policy container.
The method according to claim 2, wherein the method further comprises:

Receive the indication information for setting the Always-On feature sent by the UE.
The method according to claim 6, wherein the receiving the indication information for setting the Always-On feature sent by the UE comprises:

Receive the indication information for setting the Always-On feature sent by the UE during the initial session establishment process or the session modification process.
The method according to claim 1, wherein the method further comprises:

Configure the corresponding relationship for the UE.
The method according to claim 8, wherein the corresponding relationship is: a first corresponding relationship;

Wherein, the first correspondence is the correspondence between at least one parameter in the PDU session attribute and the Always-On feature;

Alternatively, the first correspondence is a correspondence between at least one parameter in the PDU session attribute and a first type of service; wherein, the first type of service is a service capable of setting an Always-On feature session.
The method according to claim 9, wherein the at least one parameter in the PDU session attribute includes at least one of the following: S-NSSAI, DNN.
The method according to claim 8, wherein the method further comprises:

Send QoS parameters.
The method according to claim 11, wherein the corresponding relationship is: a second corresponding relationship;

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service;

Or, the second correspondence is a correspondence between at least one parameter among the QoS parameters and the Always-On feature.
The method according to any one of claims 1-12, wherein the method further comprises:

Receive the third indication sent by the UE for indicating the number of Always-On sessions.
A session setting method, applied to UE, includes:

At least one piece of information related to the Always-On feature is received; wherein the at least one piece of related information is used for the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to set the PDU session to be permanently open The Always-On feature, or a second indication used to indicate the number of Always-On sessions.
The method according to claim 14, wherein said receiving at least one piece of information related to the Always-On feature comprises:

Receiving a policy container; wherein the policy container carries a first URSP policy; the first URSP policy carries a first indication;

The method also includes:

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

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

When in the idle state, based on the service request process triggered by the third network device, switch from the idle state to the connected state.
The method according to claim 15, wherein the method further comprises:

Send the instruction information for setting the Always-On feature to the first network device.
The method according to claim 19, wherein the sending instruction information for setting the Always-On feature to the first network device comprises:

In the initial session establishment process or the session modification process, the instruction information for setting the Always-On feature is sent to the first network device.
The method according to claim 14, wherein the method further comprises:

Based on the at least one parameter and the corresponding relationship related to the PDU session, it is determined to set the PDU session to permanently enable the Always-On feature.
The method according to claim 21, wherein the corresponding relationship is: a first corresponding relationship;

Wherein, the first correspondence is the correspondence between at least one parameter in the PDU session attribute and the Always-On feature;

Alternatively, the first correspondence is a correspondence between at least one parameter in the PDU session attribute and a first type of service; wherein, the first type of service is a service capable of setting an Always-On feature session.
The method according to claim 22, wherein the at least one parameter in the PDU session attribute includes at least one of the following: S-NSSAI, DNN.
The method according to claim 21, wherein the corresponding relationship is: sent by the network side to the UE, or pre-configured by the UE.
The method of claim 24, wherein the method further comprises:

Receive the first correspondence sent through the UCU message.
The method of claim 24, wherein the method further comprises:

Receive the first correspondence sent by the registration reply message.
The method of claim 21, wherein the method further comprises:

Receive QoS parameters.
The method according to claim 27, wherein the method further comprises:

Send a PDU session establishment request message, and receive the QoS parameter carried in the PDU session establishment request reply message on the network side.
The method according to claim 27, wherein the corresponding relationship is: a second corresponding relationship;

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service;

Or, the second correspondence relationship is a correspondence relationship between at least one of the QoS parameters and the Always-On feature.
The method of claim 29, wherein the method further comprises:

When it is determined that the PDU session needs to be set to the Always-On feature, the first request for setting the PDU session to the Always-On feature is sent 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 as an Always-On feature based on the feedback information.
A session setting method, applied to UE, includes:

Send a third indication to the network side, where the third indication is used to indicate the number of Always-On sessions.
A session setting method, applied to a second network device, includes:

Based on the UE's PDU session related information, determine whether the PDU session of the UE is set to the Always-On feature;

When it is determined that the PDU session of the UE is set to the Always-On feature, an indication is sent to the UE; wherein the indication is used to notify the UE to set the PDU session to Always-On.
The method according to claim 33, wherein the PDU session related information of the UE includes at least one of the following:

Session establishment parameters reported by the UE, user subscription information corresponding to the UE, PCC policies, and local configuration.
The method according to claim 34, wherein the method further comprises:

Receive a session establishment request sent by the UE;

Correspondingly, the sending an instruction to the UE includes:

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

After sending the first indication, receive the Always-on PDU session request identifier carried in the PDU session modification request message by the UE.
The method according to claim 35, wherein the sending an indication to the UE comprises:

Send a notification message to the UE, where the notification message carries a first parameter; wherein, the first parameter includes an identifier of whether an Always-On session needs to be established and/or an Always-On session needs to be established.
The method according to claim 35, wherein the notification message is: a dedicated NAS message or a paging message.
The method of claim 37, wherein the method further comprises:

A session modification request sent by the UE is received, and the session modification request carries an indication that the PDU session is an Always-On feature.
The method according to any one of claims 33-39, wherein the method further comprises:

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

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

The first communication unit sends at least one piece of information related to the Always-On feature to the UE;

Wherein, the at least one piece of related information is used by the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to set the PDU session to be permanently enabled with the Always-On feature, or to indicate the Always-On feature. On the second indication of the number of sessions.
The first network device according to claim 42, wherein the first communication unit sends a policy container to the UE; wherein, the policy container carries a first URSP policy; the first URSP policy carries a An indication, the first indication is used by the UE to determine whether to bind the service to the session with the Always-On feature.
The first network device according to claim 43, wherein the first indication is carried in an RSD in the first URSP policy.
The first network device according to claim 43, wherein the first communication unit transparently transmits the policy container to the UE through a third network device.
The first network device according to any one of claims 43-45, wherein the first communication unit receives the policy configuration result carried by the UE through the policy container.
The first network device according to claim 43, wherein the first communication unit receives instruction information for setting the Always-On feature sent by the UE.
The first network device according to claim 47, wherein the first communication unit receives indication information for setting the Always-On feature sent by the UE during the initial session establishment process or the session modification process.
The first network device according to claim 42, wherein the first communication unit configures the corresponding relationship for the UE.
The first network device according to claim 49, wherein the corresponding relationship is: a first corresponding relationship;

Wherein, the first correspondence is the correspondence between at least one parameter in the PDU session attribute and the Always-On feature;

Alternatively, the first correspondence is a correspondence between at least one parameter in the PDU session attribute and a first type of service; wherein, the first type of service is a service capable of setting an Always-On feature session.
The first network device according to claim 50, wherein the at least one parameter in the PDU session attribute includes at least one of the following: S-NSSAI, DNN.
The first network device according to claim 49, wherein the first communication unit transmits QoS parameters.
The first network device according to claim 52, wherein the corresponding relationship is: a second corresponding relationship;

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service;

Or, the second correspondence is a correspondence between at least one parameter among the QoS parameters and the Always-On feature.
The first network device according to any one of claims 42-53, wherein the first communication unit receives a third indication sent by the UE for indicating the number of Always-On sessions.
A type of UE, including:

The second communication unit receives at least one piece of information related to the Always-On feature; wherein the at least one piece of related information is used by the UE to determine whether to bind the service to the session with the Always-On feature, or to determine whether to bind the PDU The session is set to permanently enable the Always-On feature, or includes a second indication for indicating the number of Always-On sessions.
The UE according to claim 55, wherein said second communication unit receives a policy container; wherein said policy container carries a first URSP policy; said first URSP policy carries a first indication, said The first indication is used to determine whether to bind the service to the session with the Always-On feature.
The UE according to claim 56, wherein the first indication is carried in an RSD in the first URSP policy.
The UE according to claim 56, wherein the second communication unit receives the policy container sent by the first network device transparently transmitted by the third network device.
The UE according to claim 56, wherein the UE further comprises:

The second processing unit, when in the idle state, switches from the idle state to the connected state based on the service request process triggered by the third network device.
The UE according to claim 56, wherein the second communication unit sends instruction information for setting the Always-On feature to the first network device.
The UE according to claim 60, wherein the second communication unit sends instruction information for setting the Always-On feature to the first network device during the initial session establishment process or the session modification process.
The UE according to claim 55, wherein the UE further comprises:

The second processing unit, based on the at least one parameter and corresponding relationship related to the PDU session, determines to set the PDU session to permanently enable the Always-On feature.
The UE according to claim 62, wherein the corresponding relationship is: a first corresponding relationship;

Wherein, the first correspondence is the correspondence between at least one parameter in the PDU session attribute and the Always-On feature;

Alternatively, the first correspondence is a correspondence between at least one parameter in the PDU session attribute and a first type of service; wherein, the first type of service is a service capable of setting an Always-On feature session.
The UE according to claim 63, wherein the at least one parameter in the PDU session attribute includes at least one of the following: S-NSSAI, DNN.
The UE according to claim 62, wherein the corresponding relationship is: sent to the UE by the network side, or pre-configured by the UE.
The UE according to claim 65, wherein the second communication unit receives the first correspondence sent by a UCU message.
The UE according to claim 65, wherein the second communication unit receives the first correspondence sent by a registration reply message.
The UE according to claim 62, wherein the second communication unit receives QoS parameters.
The UE according to claim 68, wherein the second communication unit sends a PDU session establishment request message, and receives the QoS parameter carried in the PDU session establishment request reply message on the network side.
The UE according to claim 68, wherein the corresponding relationship is: a second corresponding relationship;

Wherein, the second correspondence is a correspondence between at least one of the QoS parameters and the first type of service;

Or, the second correspondence is a correspondence between at least one parameter among the QoS parameters and the Always-On feature.
The UE according to claim 70, wherein when it is determined that the PDU session needs to be set to the Always-On feature, the second communication unit sends a session modification request message to set the PDU session to the first feature of the Always-On feature. request.
The UE according to claim 71, wherein the second communication unit receives feedback information for the first request;

The second processing unit determines whether to set the PDU session as an Always-On feature based on the feedback information.
A type of UE, including:

The fourth communication unit sends a third indication for indicating the number of Always-On sessions.
A second network device, including:

The third processing unit, based on the PDU session related information of the UE, determines whether the PDU session of the UE is set to the Always-On feature;

The third communication unit sends an indication to the UE when it is determined that the PDU session of the UE is set to the Always-On feature; wherein the indication is used to notify the UE to set the PDU session to Always-On. On.
The second network device according to claim 74, wherein the PDU session related information of the UE includes at least one of the following:

Session establishment parameters reported by the UE, user subscription information corresponding to the UE, PCC policies, and local configuration.
The second network device according to claim 75, wherein the third communication unit receives a session establishment request sent by the UE;

Sending a session establishment reply message carrying a first indication to the UE; where the first indication is used to instruct the UE to set the PDU session to the Always-On feature.
The second network device according to claim 76, wherein the third communication unit, after sending the first instruction, receives the Always-on PDU session request identifier carried in the PDU session modification request message by the UE.
The second network device according to claim 74, wherein the third communication unit sends a notification message to the UE, and the notification message carries a first parameter; wherein, the first parameter includes whether to establish Always-On session and/or an identifier that needs to establish an Always-On session.
The second network device according to claim 78, wherein the notification message is: a dedicated NAS message or a paging message.
The second network device according to claim 78, wherein the third communication unit receives a session modification request sent by the UE, and the session modification request carries an indication that the PDU session is an Always-On feature.
The second network device according to any one of claims 74-80, wherein the third communication unit receives a third indication sent by the UE for indicating the number of Always-On sessions.
The second network device according to any one of claims 74-80, wherein the third communication unit sends a second indication for indicating the number of Always-On sessions to the UE.
A network device including: a processor and a memory for storing a computer program that can run on the processor,

Wherein, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the steps of the method according to any one of claims 1-13 and 33-41.
A UE includes a processor and a memory for storing computer programs that can run on the processor,

Wherein, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the steps of the method according to any one of claims 14-32.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-13 and 33-41.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 14-32.
A computer-readable storage medium used to store a computer program that enables a computer to execute the steps of the method according to any one of claims 1-41.
A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1-41.
A computer program that causes a computer to execute the method according to any one of claims 1-41.