Resource control method, device, terminal and network side device

Abstract

The present application discloses a resource control method, an apparatus, a terminal and a network side device, which belong to the field of wireless communication. The resource control method according to an embodiment of the present application includes a step of a network side device determining that a reactivation of a first PDU session initiated by a terminal fails due to an NSAC of a first slice, and a step of the network side device sending a first message to the terminal, the first message including at least one of first indication information for indicating that the reactivation failure of the first PDU session is caused by the NSAC failure of the first slice, and second indication information for indicating a first timer bound to the first slice and for indicating that the terminal is allowed to re-initiate the reactivation of the first PDU session associated with the first slice after the first timer times out.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This invention claims priority to a patent application filed with the China Patent Office on March 29, 2022, bearing application number 202210320869.9 and entitled "Resource control method, apparatus, terminal and network side equipment", the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the technical field of wireless communication, and in particular to a resource control method, apparatus, terminal and network side equipment. [Background technology]

[0003] Network slicing access control (NSAC) is a method for controlling resources related to a slice on the network side, and the resources include the number of terminals (User Equipment, UE) related to the slice, the number of protocol data unit (PDU) sessions related to the slice, and the data rate related to the slice, etc. In addition, such control is managed individually according to the access type.

[0004] In the related art, when an associated slice needs to perform NSAC, a Session Management Function (SMF) performs NSAC when first establishing a PDU session, and a network slice access control network element (NSACF) performs access control for each access type, i.e., the network side controls the number of different types of PDU sessions, such as 3rd Generation Partnership Project (3GPP) access and non-3GPP access, for a slice. When the number of PDU sessions of a certain access type associated with a certain slice reaches a maximum value, the SMF rejects the establishment of a PDU session in this access type by the slice.

[0005] In the related art, the network side may request the terminal to switch the access type of a PDU session from non-3GPP access to 3GPP access and re-establish user plane resources on the 3GPP access. After the terminal receives the request from the network side, if the single network slice selection assistance information (S-NSSAI) related to the PDU of the established non-3GPP access is an S-NSSAI allowed for 3GPP access, the UE may send a service request to notify the network side that the terminal supports reactivation of the PDU session, i.e., switching of the type of the PDU session from non-3GPP access to 3GPP access. When the network side receives the request from the terminal, it performs NSAC before establishing the PDU of the 3GPP access. If the NSAC is successful and the PDU is successfully established, it sends a service acceptance message to the terminal to notify the terminal, but if the NSAC fails, the network side does not notify the terminal that the reactivation of the PDU has failed due to NSAC, so that the terminal cannot obtain the corresponding information. Summary of the Invention

[0006] The embodiments of the present application provide a resource control method, device, terminal and network side equipment that can solve the problem that a terminal cannot know that reactivation of a PDU session has failed due to NSAC, as described above.

[0007] In a first aspect, a resource control method is provided, comprising: a step of a network side equipment determining that reactivation of a first PDU session initiated by a terminal has failed due to NSAC of a first slice; and a step of the network side equipment sending a first message to the terminal, wherein the first message includes at least one of first instruction information for indicating a failure cause indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice, and second instruction information for indicating a first timer bound to the first slice and for indicating that the terminal is allowed to re-initiate reactivation of the first PDU session related to the first slice after the first timer times out.

[0008] In a second aspect, a resource control device is provided, comprising: a first determination module used to determine that reactivation of a first PDU session initiated by a terminal has failed due to NSAC of a first slice; and a first transmission module used to send a first message to the terminal, wherein the first message includes at least one of first instruction information for indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice, and second instruction information for indicating a first timer bound to the first slice and for indicating that the terminal is permitted to re-initiate reactivation of the first PDU session associated with the first slice after the first timer times out.

[0009] In a third aspect, a PDU session reactivation method is provided, comprising: a step in which a terminal sends a first request message to a network side device, wherein the first request message includes an identifier of a first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session; and a step in which the terminal receives a first message sent from the network side device, wherein the first message includes at least one of first instruction information for indicating a failure cause indicating that a failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice, and second instruction information for indicating a first timer bound to the first slice and allowing the terminal to re-initiate reactivation of the first PDU session associated with the first slice after the first timer times out.

[0010] In a fourth aspect, a PDU session reactivation device is provided, comprising: a second transmitting module used for sending a first request message to a network side equipment, wherein the first request message includes an identifier of a first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session; and a second receiving module used for receiving a first message sent from the network side equipment, wherein the first message includes at least one of: first instruction information for indicating a failure cause indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice; and second instruction information for indicating a first timer bound to the first slice and allowing the terminal to re-initiate reactivation of the first PDU session associated with the first slice after the first timer times out.

[0011] In a fifth aspect, there is provided a terminal comprising a processor and a memory, wherein the memory stores programs or commands executable on the processor, the programs or commands implementing the steps of the method according to the third aspect when executed by the processor.

[0012] In a sixth aspect, there is provided a terminal comprising a processor and a communication interface, the processor being adapted to implement steps of the method according to the third aspect, and the communication interface being adapted to communicate with an external device.

[0013] In a seventh aspect, there is provided a network side device comprising a processor and a memory, wherein a program or command executable on the processor is stored in the memory, and the network side device realizes the steps of the method described in the first aspect when the program or command is executed by the processor.

[0014] In an eighth aspect, there is provided a network side device comprising a processor and a communication interface, the processor being used to realize the steps of the method described in the first aspect, and the communication interface being used to communicate with an external device.

[0015] In a ninth aspect, there is provided a resource control system comprising a terminal and a network side device, the terminal being usable for executing steps of the method described in the third aspect, and the network side device being usable for executing steps of the method described in the first aspect.

[0016] In a tenth aspect, there is provided a readable storage medium having stored thereon a program or command which, when executed by a processor, performs steps of the method according to the first aspect or performs steps of the method according to the third aspect.

[0017] In an eleventh aspect, there is provided a chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor executing a program or command to implement steps of the method according to the first aspect or used to implement steps of the method according to the third aspect.

[0018] In a twelfth aspect, there is provided a computer program / program product stored on a storage medium which, when executed by at least one processor, performs the steps of the method according to the first aspect or performs the steps of the method according to the third aspect.

[0019] In an embodiment of the present application, when the network side device determines that the reactivation of the first PDU session initiated by the terminal has failed due to the NSAC of the first slice, it sends first indication information and / or second indication information to the terminal, where the first indication information indicates that the cause of the failure is a failure of the NSAC of the first slice, and the second indication information indicates a first timer bound to the first slice, and allows the terminal to re-initiate reactivation of the first PDU session related to the first slice after the first timer times out, so that the terminal can know that the reactivation of the first PDU session has failed due to the NSAC of the first slice, and further enables more efficient slice resource control. [Brief description of the drawings]

[0020] [Figure 1] 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied. [Diagram 2] 1 shows a schematic flow diagram of a resource control method in the related art. [Diagram 3] 1 shows a flow diagram of a resource control method according to an embodiment of the present application; [Figure 4]A flow diagram of a PDU session reactivation method according to an embodiment of the present application is shown. [Diagram 5] 4 illustrates another flow diagram of a resource control method according to an embodiment of the present application; [Figure 6] 1 shows a structural schematic diagram of a resource control device according to an embodiment of the present application; [Figure 7] 1 illustrates a structural schematic diagram of a PDU session reactivation device according to an embodiment of the present application; [Figure 8] 1 shows a structural schematic diagram of a communication device according to an embodiment of the present application; [Figure 9] 1 is a schematic diagram of the hardware structure of a terminal according to an embodiment of the present application; [Figure 10] 1 is a schematic diagram of the hardware structure of a network side device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, the technical solutions in the embodiments of the present application will be explicitly described with reference to the drawings in the embodiments of the present application, and it is to be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. Based on the embodiments in the present application, other embodiments that a person skilled in the art can obtain shall all fall within the scope of protection of the present application.

[0022] The terms "first", "second", and the like in the specification and claims of the present application are not intended to describe a particular order or sequence, but are intended to distinguish between similar objects. It should be understood that the terms used in this manner may be interchangeable in some cases, such that the embodiments of the present application may be performed in an order other than that shown or described herein, and "first" and "second" are generally intended to distinguish between objects of the same type, and do not limit the number of objects, e.g., the first object may be one or more. Also, in the specification and claims, "and / or" refers to at least one of the objects connected, and the symbol " / " generally refers to the related objects before and after being in an "or" relationship.

[0023] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / Long Term Evolution Advanced (LTE-Advanced, LTE-A) systems, but may be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the techniques described may be used in the systems and radio technologies described above, or in other systems and radio technologies. In the following description, for purposes of illustration, New Radio (NR) systems are described, and NR terminology is used extensively in the following description, however, these technologies may be used in applications other than NR system applications, such as sixth generation (6G) systems. th The present invention may be applied to a 6G (6th Generation) communication system.

[0024] 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a personal digital assistant, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle user equipment (VUE), a pedestrian user equipment (PUE), a smart home (home equipment with wireless communication function, such as a refrigerator, a television, a washing machine, or furniture), a game machine, a personal computer, a mobile phone, a mobile terminal (Mobile Internet Device), a mobile user equipment (MID), a mobile terminal (Mobile User Equipment ... The network side equipment 12 may be a terminal side equipment such as a wireless computer (PC), an automated teller machine or a kiosk, and the wearable device includes a smart watch, a smart band, a smart earphone, a smart glasses, a smart accessory (smart bracelet, a smart chain bracelet, a smart ring, a smart necklace, a smart anklet, a smart chain anklet, etc.), a smart wristband, a smart clothing, etc. It should be noted that the embodiment of the present application does not specifically limit the type of the terminal 11. The network side equipment 12 may include an access network equipment and / or a core network equipment, where the access network equipment 12 may be referred to as a radio access network equipment, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network unit.The access network equipment 12 may include a base station, a Wireless Local Area Network (WLAN) access point, or a Wireless Fidelity (WiFi) node, etc., and the base station may be called a Node B, an evolved Node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B, a Home Evolved Node B, a Transmitting Receiving Point (TRP), or any other suitable term in the field, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and as should be explained, in the embodiments of this application, only a base station in an NR system is described as an example, but the type of the base station is not specifically limited.The core network devices are: Core Network Node, Core Network Function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (BSF), Application Function (Application Node B), Application Node C, Application Node D, Application Node E, Application Node F ... It should be noted that the embodiments of the present application only use the core network device in the NR system as an example, and do not specifically limit the type of the core network device.

[0025] Figure 2 shows a flow diagram of a network side in the related technology requesting a terminal to switch the access type of a PDU session from non-3GPP access to 3GPP access. As shown in Figure 2, after the network side initiates paging and requests the terminal side to switch the access type of a PDU session from non-3GPP access to 3GPP access (i.e., inter-access handover) and re-establish user plane resources on 3GPP access, the process mainly includes the following steps:

[0026] In S201, the UE determines whether to send a Service Request message, and if the S-NSSAI related to the PDU of the established non-3GPP access is an NSSAI allowed by 3GPP access, the UE may include an Allowed PDU session status IE in the Service Request message to inform the network side that the UE supports reactivation of the PDU session (i.e., switching the type of PDU session ID from non-3GPP access to 3GPP access).

[0027] In S202, after receiving the Service Request, the AMF sends it to the SMF via an AMF-SMF interface message, causing the SMF to establish a PDU session related to the S-NSSAI and 3GPP access.

[0028] In S203, the SMF performs NSAC before establishing a 3GPP access PDU, and transmits information such as S-NSSAI and access type to the NSACF.

[0029] In S204-1, if NSAC is successful and PDU establishment is successful, the SMF replies to the AMF that establishment is successful.

[0030] In S204-2, if the PDU establishment fails due to a specified cause, the SMF indicates different information to the AMF depending on the case.

[0031] In S205, the AMF sends a Service Accept message to the UE, and if the PDU is successfully established, the Service Accept message includes indication information that the PDU is successfully established.

[0032] Here, in S204-2, the SMF can instruct the AMF as follows:

[0033] (1) If the SMF indicates to the AMF that the UE is not located in the service area of ​​a Local Area Data Network (LADN), the AMF uses 5GMM cause #43 “LADN not available” in the PDU session reactivation result error cause IE in the SERVICE ACCEPT message.

[0034] (2) If the SMF instructs the AMF that only establishment of high priority services is allowed, the AMF uses 5GMM cause #28 “restricted service area” in the PDU session reactivation result error cause IE in the SERVICE ACCEPT message.

[0035] (3) If the SMF indicates to the AMF that user plane resources are not available, the AMF uses 5GMM cause #92 “insufficient user-plane resources for the PDU session” in the PDU session reactivation result error cause IE in the SERVICE ACCEPT message, and it is up to the implementation how the UE later restarts the Service Request process.

[0036] As can be seen from the above, in the related art, the network side does not notify the terminal that the reactivation of the PDU has failed due to the NSAC, so the terminal cannot obtain the relevant information.

[0037] Hereinafter, the resource control method according to the embodiments of the present application will be described in more detail with reference to some embodiments and their application scenarios with reference to the drawings.

[0038] Figure 3 shows a flow diagram of a resource control method in an embodiment of the present application, where the method 300 may be performed by a network side device, and optionally, the network side device may be a network element having mobility management function (e.g., an AMF network element of a core network). In other words, the method may be performed by software or hardware installed in the network side device. As shown in Figure 3, the method may include the following steps:

[0039] At S310, the network side equipment determines that reactivation of the first PDU session initiated by the terminal has failed due to the NSAC of the first slice.

[0040] In one possible implementation, before S310, the method may further include a step of the network side device receiving a first request message sent from the terminal, the first request message including an identifier of the first PDU session, the first PDU session being associated with the first slice, and the first request message requesting reactivation of the first PDU session. That is, before S310, the terminal may initiate reactivation of the first PDU session by the first request message.

[0041] In one possible implementation, the reactivation of the first PDU session includes switching the access type of the first PDU session. For example, the network side may initiate paging to request the terminal side to switch the access type of a PDU session from non-3GPP access to 3GPP access (i.e., inter-access handover) and re-establish user plane resources on the 3GPP access. After the terminal receives the paging from the network side, if the S-NSSAI associated with the first PDU of the established non-3GPP access is an NSSAI allowed by the 3GPP access, the terminal may send a first request message. The first request message may be a service request message. The terminal may include an allowed PDU session status IE in the first request message to inform the network side that the UE supports reactivation of the PDU session (i.e., switching the type of PDU session ID from non-3GPP access to 3GPP access).

[0042] At S312, the network side device transmits a first message to the terminal.

[0043] In an embodiment of the present application, the first message includes at least one of the following:

[0044] (1) First indication information for indicating that the failure of the reactivation of the first PDU session is due to the failure of the NSAC of the first slice. The first indication information allows the terminal to know that the reactivation of the first PDU session has failed due to the failure of the NSAC of the first slice, and in a later procedure, a corresponding processing recipe can be adopted, for example, so that the terminal does not start the establishment of the first PDU session related to the first slice.

[0045] (2) Second instruction information for indicating a first timer bound to the first slice and for permitting the terminal to re-initiate reactivation of a first PDU session associated with the first slice after the first timer times out. The second instruction information allows the terminal to re-initiate reactivation of a first PDU session associated with the first slice after the first timer times out, thereby preventing a signaling storm caused by the terminal frequently and repeatedly initiating reactivation of the first PDU session after determining failure of reactivation of the first PDU session, and realizing efficient and reasonable slice resource management.

[0046] In an embodiment of the present application, the second indication information may include a first timer identifier and a period of the first timer, and the terminal can start the first timer corresponding to the second indication information according to the second indication information.

[0047] In one possible implementation, the first indication information includes a failure cause value, and the failure cause value includes one of the following:

[0048] (1) Occurrence of congestion in the network side device For example, the first message may include a failure cause value: 5GMM cause#22 “congestion”.

[0049] (2) Insufficient resources for the first slice. For example, the first message may include a failure cause value: 5GMM cause#69 “insufficient resources for specific slice.”

[0050] (3) Insufficient user-plane resources for the first PDU session. For example, the first message may include a failure cause value: 5GMM cause #92 “insufficient user-plane resources for the PDU session.”

[0051] In one possible implementation form, the first message may further include third indication information for indicating that the network side equipment has received the first request message, i.e., that the network side equipment has received a service request initiated by the terminal.

[0052] In one possible implementation form, since the terminal may start a first timer after receiving the first message and re-initiate activation of the first PDU session after the first timer times out, in this possible implementation form, after the network side equipment sends the first message to the terminal, the method may further include a step of the network side equipment receiving a second request message sent from the terminal after the first timer times out, wherein the second request message includes an identifier of the first PDU session and the second request message requests re-activation of the first PDU session.

[0053] According to the technical solution of an embodiment of the present application, when the network side equipment determines that the reactivation of the first PDU session initiated by the terminal fails due to the NSAC of the first slice, it sends first indication information and / or second indication information to the terminal, where the first indication information indicates that the cause of the failure is a failure of the NSAC of the first slice, and the second indication information indicates a first timer bound to the first slice, and allows the terminal to re-initiate the reactivation of the first PDU session related to the first slice after the first timer times out, so that the terminal can know that the reactivation of the first PDU session has failed due to the NSAC of the first slice, and further can perform slice resource control more efficiently.

[0054] For example, after receiving an indication from the SMF that the slice is unavailable due to the NSAC, the network side AMF network element: A. sending a first message to accept a service request from a UE; B. the first message carries a first cause value: 5GMM cause#22 “congestion” or 5GMM cause#69 “insufficient resources for specific slice” or 5GMM cause#92 “insufficient user-plane resources for the PDU session” to inform the UE that the failure to reactivate the specific PDU session ID is due to a failure of NSAC for the slice; C. the first message includes a first timer for instructing the UE to reinitiate the reactivation request after the timer expires; Perform an operation that includes at least one of the following:

[0055] 4 shows a flow diagram of a PDU session reactivation method in an embodiment of the present application, where the method 400 may be performed by a terminal. In other words, the method may be performed by software or hardware installed in the terminal. As shown in FIG. 4, the method may include the following steps:

[0056] At S410, the terminal sends a first request message to a network side device, the first request message including an identifier of a first PDU session, the first PDU session being associated with a first slice, and the first request message requests reactivation of the first PDU session.

[0057] In an embodiment of the present application, the first request message may be a service request message.

[0058] Alternatively, the first request message is used to indicate a switch of the access type of the first PDU session. For example, after the UE receives a paging initiated by the network side requesting the UE to switch the access type of a PDU session from non-3GPP access to 3GPP access (i.e., inter-access handover), if the S-NSSAI associated with the first PDU of the established non-3GPP access is an NSSAI allowed by 3GPP access, the UE may send the first request message. The first request message includes an Allowed PDU session status IE for informing the network side that the UE supports reactivation of the PDU session (i.e., switching the type of PDU session ID from non-3GPP access to 3GPP access).

[0059] At S412, the terminal receives a first message sent from the network side device.

[0060] Here, the network side device may employ the method described in the above method 300 to send a first message to the terminal, and the first message is the same as the first message in the method 300. Therefore, specific reference may be made to the description in the method 300, and the description will be omitted here.

[0061] In an embodiment of the present application, the first message comprises: (1) first indication information for indicating that a failure in reactivating the first PDU session is due to a failure of an NSAC of the first slice; (2) second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session associated with the first slice after the first timer times out; and At least one of the following may be included.

[0062] In one possible implementation, the first indication information may include a failure cause value, and the failure cause value is: (1) The occurrence of congestion in the network side device; and (2) a shortage of resources in the first slice; and (3) a shortage of user plane resources for the first PDU session; and Contains one of the following:

[0063] In one possible implementation form, the first message may further include third indication information for indicating that the network side device has received the first request message.

[0064] In one possible implementation form, after the terminal receives a first message sent from the network side device, the method includes: a step 1 of the terminal starting the first timer when the first message includes the second indication information; a step 2 in which the terminal sends a second request message after the first timer times out, the second request message including an identifier of the first PDU session, the second request message requesting reactivation of the first PDU session; It may further include.

[0065] In the above-mentioned possible implementation form, when the first message includes the second instruction information, the terminal starts a first timer indicated in the second instruction information, and restarts reactivation of the first PDU session after the first timer times out, thereby preventing the problem of continuous network congestion due to a signaling storm caused by frequently and repeatedly requesting reactivation of the first PDU session, and realizing efficient and rational slice resource management.

[0066] In another possible implementation form, after the terminal receives a first message sent from the network side device, the method includes: (1) if the first message does not include the second indication information, the terminal starts a second timer bound to the first slice; (2) after the second timer times out, the terminal sends a second request message, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session; It may further include.

[0067] In the above-mentioned possible implementation form, if the network side equipment does not indicate the first timer, the terminal starts a second timer bound to the first slice installed locally, and restarts reactivation of the first PDU session after the second timer times out, thereby preventing the problem of continuous network congestion due to signaling storms caused by frequently and repeatedly requesting reactivation of the first PDU session, and realizing efficient and rational slice resource management.

[0068] In one possible implementation form, before the terminal transmits a first request message to a network side device, the method may further include a step in which the terminal determines that a target timer is not set or that the set target timer has timed out, the target timer being a timer bound to a first slice, and the first slice being a slice associated with the first PDU session. That is, in this possible implementation form, before transmitting the first request message, the terminal first determines whether a timer bound to the first slice (e.g., the first timer or the second timer) is set or whether a set timer bound to the first slice has timed out, and executes S410 if the first timer or the second timer is not set or the set first timer or the second timer has timed out.

[0069] In yet another possible implementation form, after the terminal receives the first message sent from the network side device, the method may further include a step of the terminal sending a second request message including an identifier of the first PDU session, the second request message requesting reactivation of the first PDU session, until the number of consecutive transmissions of the reactivation request of the first PDU session reaches a preset value and the terminal terminates the reactivation request process of the first PDU session. In this possible implementation form, after receiving the first message, if the first message does not include second indication information, the terminal may directly restart the reactivation request of the first PDU session and continue to try until the maximum number is reached.

[0070] In an embodiment of the present application, the terminal may receive a first message sent from a network side device after initiating reactivation of a PDU session, and may know that reactivation of the PDU session has failed due to NSAC. Optionally, the terminal may wait a certain period of time before attempting to reactivate the PDU session again, thereby preventing the network from being continuously congested due to a signaling storm caused by the UE frequently and repeatedly sending a request message, and realizing efficient and reasonable slice resource management.

[0071] For example, when the UE initiates a PDU session reactivation process, it performs operations including at least one of the following:

[0072] A. If a timer is installed, the UE must check whether there is a running timer associated with the slice associated with the PDU session ID. If the UE needs to reactivate the PDU session ID associated with the slice, the UE cannot initiate a reactivation request until the timer expires.

[0073] B. If no timer is set, the UE may immediately initiate a reactivation request for the PDU session that contains the PDU session ID to be reactivated.

[0074] In addition, after receiving the first message sent from the network side device, the UE performs operations including at least one of the following:

[0075] A. If the received first message includes a PDU session ID reactivation failure cause value of 5GMM cause #22 "congestion" or 5GMM cause #69 "insufficient resources for specific slice" or 5GMM cause #92 "insufficient user-plane resources for the PDU session" and the first message includes a timer, start the timer in the UE to count. In one embodiment, when the timer reaches zero, the UE immediately initiates a new service request.

[0076] B. If the received first message includes a PDU session ID reactivation failure cause value of 5GMM cause #22 "congestion" or 5GMM cause #69 "insufficient resources for specific slice" or 5GMM cause #92 "insufficient user-plane resources for the PDU session" but the first message does not include a timer, the UE performs a fourth operation. The fourth operation may include at least one of the following:

[0077] 1) The UE starts an implementation specific timer for a slice of the PDU session ID associated with the cause value.

[0078] 2) The UE does not set a timer, it immediately sends the service request message again, the UE can try a maximum number of times (e.g. 5) consecutively, after which the UE will not attempt to initiate a re-activation request until the network side again instructs the UE to initiate a re-activation request PDU.

[0079] FIG. 5 shows another flow diagram of a resource control method according to an embodiment of the present application. As shown in FIG. 5, the method 500 mainly includes the following steps:

[0080] In S501, before initiating a first request for reactivation of a PDU session, the UE determines whether a timer is set, and if a timer is set, checks whether there is a currently running timer associated with the slice associated with the PDU session ID, and if there is a timer and the UE needs to reactivate the PDU session ID associated with the slice, the UE executes S502 after the timer expires. If no timer is set, or the set timer times out, or there is no timer bound to the slice associated with the PDU session to be activated by the UE, the UE executes S502.

[0081] At S502, the UE sends a service request to the network side to request reactivation of a PDU session, where the service request includes an identifier (PDU session ID) of the PDU session to be activated.

[0082] In S503, after receiving the above service request, the AMF notifies the SMF of information including the PDU session ID, S-NSSAI, etc., and reactivates the PDU session ID.

[0083] In S504, the SMF interacts with the NSACF to perform NSAC.

[0084] At S505, the SMF receives failure feedback from the NSACF and informs the AMF that the slice is currently unavailable by the NSAC.

[0085] In S506, the AMF sends a first message, and the first message includes: A. indication information for indicating acceptance of a service request initiated by a UE; B. A first cause value: 5GMM cause#22 “congestion” or 5GMM cause#69 “insufficient resources for specific slice” or 5GMM cause#92 “insufficient user-plane resources for the PDU session” to inform the UE that the reactivation failure of a specific PDU session ID is due to a NSAC failure of the slice; C. a first timer for instructing the UE to re-initiate a reactivation request after the timer expires; At least one of the following is included:

[0086] In S507, after receiving the first message, the UE performs a first operation, and the first operation includes at least one of the following:

[0087] A. S507-a: If the received first message includes a PDU session ID reactivation failure cause value of 5GMM cause#22 “congestion” or 5GMM cause#69 “insufficient resources for specific slice” or 5GMM cause#92 “insufficient user-plane resources for the PDU session” and the first message includes a timer, start the timer in the UE to count, and resend the service request message after the timer expires. In one embodiment, when the timer reaches 0, the UE immediately resends the service request message.

[0088] B. S507-b: If the received first message includes a cause value of the PDU session ID reactivation failure that is 5GMM cause #22 "congestion" or 5GMM cause #69 "insufficient resources for specific slice" or 5GMM cause #92 "insufficient user-plane resources for the PDU session" but the first message does not include a timer, the UE performs a second operation. The second operation includes at least one of the following:

[0089] 1) The UE starts an implementation specific timer for the slice of the PDU session ID associated with the above cause value, and sends the service request message again after the timer expires.

[0090] 2) The UE does not set a timer for that slice, and immediately resends the service request message, and the UE may attempt a maximum number of consecutive attempts (e.g., 5), after which the UE will no longer attempt to initiate a reactivation request until the network side again instructs the UE to initiate a reactivation request PDU.

[0091] In the resource control method according to the embodiment of the present application, the execution body may be a resource control device. In the embodiment of the present application, the resource control device according to the embodiment of the present application will be described by taking the resource control method being executed by the resource control device as an example.

[0092] FIG. 6 shows a structural schematic diagram of a resource control device according to an embodiment of the present application. As shown in FIG. 6, the device 600 mainly includes: a first determining module 601 and a first sending module 602 .

[0093] In an embodiment of the present application, the first determining module 601 is used for determining that the reactivation of the first PDU session initiated by the terminal fails due to the NSAC of the first slice. The first sending module 602 is used for sending a first message to the terminal, the first message including at least one of first indication information for indicating that the failure of the reactivation of the first PDU session is caused by the failure of the NSAC of the first slice, and second indication information for indicating a first timer bound to the first slice and for indicating that the terminal is allowed to re-initiate the reactivation of the first PDU session associated with the first slice after the first timer times out.

[0094] In one possible implementation, reactivating the first PDU session includes switching the access type of the first PDU session.

[0095] In one possible implementation, the first indication information includes a failure cause value, and the failure cause value is: Occurrence of congestion in the network side device; and A lack of resources in the first slice; and A shortage of user plane resources for the first PDU session; and Contains one of the following:

[0096] In one possible implementation, as shown in FIG. 6, the device may further include a first receiving module 603 used to receive a first request message sent from the terminal, where the first request message includes an identifier of the first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session.

[0097] In one possible implementation mode, the first message further includes third indication information for indicating that the network side device has received the first request message.

[0098] In one possible implementation form, the first receiving module 603 is further used to receive a second request message sent from the terminal after the first timer times out, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

[0099] FIG. 7 shows a structural schematic diagram of a PDU session re-activation device according to an embodiment of the present application. As shown in FIG. 7, the device 700 mainly includes a second sending module 701 and a second receiving module 702.

[0100] In an embodiment of the present application, the second sending module 701 is used for sending a first request message to a network side device, the first request message includes an identifier of a first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session. The second receiving module 702 is used for receiving a first message sent from the network side device, the first message includes at least one of first indication information for indicating that a failure in reactivating the first PDU session is caused by a failure of NSAC of the first slice, and second indication information for indicating a first timer bound to the first slice and for allowing the terminal to re-initiate reactivation of the first PDU session associated with the first slice after the first timer times out.

[0101] In one possible implementation, the first request message is used to indicate a switch in access type of the first PDU session.

[0102] In one possible implementation form, the second transmitting module 701 is further used to start the first timer when the first message includes the second indication information, and to send a second request message after the first timer times out, wherein the second request message includes an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

[0103] In one possible implementation form, the second transmitting module 701 is further used for starting a second timer, which is a timer bound to the first slice, when the first message does not include the second indication information, and for sending a second request message after the second timer times out, wherein the second request message includes an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

[0104] In one possible implementation, as shown in FIG. 7, the device may further include a second determination module 703 used to determine that a target timer is not set or that the set target timer has timed out, where the target timer is a timer bound to a first slice, and the first slice is a slice associated with the first PDU session.

[0105] In one possible implementation form, the second transmission module 701 is further used to transmit a second request message including an identifier of the first PDU session, the second request message requesting reactivation of the first PDU session, until the number of consecutive transmissions of a reactivation request of the first PDU session reaches a preset value and the terminal terminates the reactivation request process of the first PDU session.

[0106] The PDU session reactivation device in the embodiment of the present application may be an electronic device, such as an electronic device having an operating system, or may be a component in an electronic device, such as an integrated circuit or chip. The electronic device may be a terminal, or other devices other than a terminal. Exemplarily, the terminal may include, but is not limited to, the types of terminal 11 listed above, and the other devices may be servers, network attached storage (NAS), etc., and are not specifically limited in the embodiment of the present application.

[0107] The PDU session reactivation device according to the embodiment of the present application realizes each process implemented by the terminal in the method embodiments of Figures 3 to 5 and can achieve similar technical effects, and detailed descriptions will be omitted here to avoid repetition.

[0108] Optionally, as shown in Fig. 8, the embodiment of the present application further provides a communication device 800 including a processor 801 and a memory 802, in which programs and commands executable on the processor 801 are stored, for example, when the communication device 800 is a terminal, the steps of the embodiment of the PDU session reactivation method can be realized when the programs and commands are executed by the processor 801, and similar technical effects can be achieved. When the communication device 800 is a network side device, the steps of the embodiment of the resource control method can be realized when the programs and commands are executed by the processor 801, and similar technical effects can be achieved, and detailed description thereof will be omitted here to avoid repetition.

[0109] The embodiment of the present application further provides a terminal including a processor and a communication interface, the processor is used to realize each step of the embodiment of the PDU session reactivation method, and the communication interface is used to communicate with an external device. The embodiment of the terminal corresponds to the embodiment of the method by the terminal side, and each implementation process and realization form of the embodiment of the method can be applied to the embodiment of the terminal, and the same technical effect can be achieved. Specifically, FIG. 9 is a hardware structure schematic diagram of a terminal for realizing the embodiment of the present application.

[0110] The terminal 900 includes at least some of the following components, but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processor 910.

[0111] Those skilled in the art can understand that the terminal 900 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 910 by a power management system, and the power management system may realize functions such as charge / discharge management and power consumption management. The structure of the terminal shown in FIG. 9 is not intended to limit the terminal, and the terminal may include more or fewer components than those shown, or a combination of some components, or a different component arrangement, and detailed descriptions thereof will be omitted here.

[0112] It should be understood that in the embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes image data of still images or videos captured by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. The other input devices 9072 may include, but are not limited to, a physical keyboard, a function button (e.g., a volume control button, a switch button, etc.), a trackball, a mouse, and an operation lever, and detailed description thereof will be omitted here.

[0113] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 901 can transmit the downlink data to the processor 910 for processing, and the radio frequency unit 901 can transmit uplink data to the network side device. Typically, the radio frequency unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0114] The memory 909 can be used to store software programs, commands, and various data. The memory 909 may include a first storage area that mainly stores programs and commands, and a second storage area that stores data, where the first storage area can store an operating system, applications and commands required for at least one function (e.g., a sound playback function, an image playback function, etc.). The memory 909 may include a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. Here, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be Random Access Memory (RAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synch link Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). Memory 909 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

[0115] The processor 910 may include one or more processing units. Alternatively, the processor 910 may integrate an application processor that mainly processes operations related to an operating system, a user interface, and applications, and a modem processor that mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 910.

[0116] Here, the radio frequency unit 901 is Sending a first request message to a network side device, the first request message including an identifier of a first PDU session, the first PDU session being associated with the first slice, and the first request message requesting reactivation of the first PDU session; receiving a first message transmitted from the network side device; The first message is First indication information for indicating that the failure of reactivation of the first PDU session is due to a failure of an NSAC of the first slice; second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session associated with the first slice after the first timer times out; At least one of the following is included:

[0117] The embodiment of the present application further provides a network side device including a processor and a communication interface, the processor is used to realize each step of the embodiment of the resource control method, and the communication interface is used to communicate with an external device. The embodiment of the network side device corresponds to the embodiment of the method by the network side device, and each implementation process and realization form of the embodiment of the method can be applied to the embodiment of the network side device to achieve the same technical effects.

[0118] Specifically, an embodiment of the present application further provides a network side device. As shown in Fig. 10, the network side device 1000 includes a processor 1001, a network interface 1002 and a memory 1003. Here, the network interface 1002 is, for example, a common public radio interface (CPRI).

[0119] Specifically, the network side device 1000 according to an embodiment of the present invention further includes commands and programs stored in memory 1003 and executable on the processor 1001, and the processor 1001 calls the commands and programs in the memory 1003 to execute the method according to each module shown in FIG. 6, thereby achieving similar technical effects, and detailed descriptions thereof will be omitted here to avoid repetition.

[0120] An embodiment of the present application further provides a readable storage medium on which programs or commands are stored, which, when executed by a processor, realize each process of the embodiment of the above resource control method, or realize each process of the embodiment of the above PDU session reactivation method, thereby achieving similar technical effects, and detailed descriptions thereof will be omitted here to avoid repetition.

[0121] Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0122] An embodiment of the present application further provides a chip comprising a processor and a communication interface, the communication interface being coupled to the processor, and the processor being used to execute programs or commands to realize each process of the embodiment of the above resource control method, or to realize each process of the embodiment of the above PDU session reactivation method, so as to achieve similar technical effects, and detailed descriptions are omitted here to avoid repetition.

[0123] It should be understood that the chip described in the embodiments of the present application may be referred to as a system on a chip, a system chip, a chip system, or an SoC.

[0124] An embodiment of the present application further provides a computer program / program product stored in a storage medium, which, when executed by at least one processor, realizes each process of the embodiment of the above resource control method, or realizes each process of the embodiment of the above PDU session reactivation method, thereby achieving similar technical effects, and detailed descriptions thereof will be omitted here to avoid repetition.

[0125] An embodiment of the present application further provides a resource control system comprising a terminal and a network side equipment, wherein the terminal can be used to perform steps of the PDU session reactivation method as described above, and the network side equipment can be used to perform steps of the resource control method as described above.

[0126] It should be noted that in this specification, the terms "comprise", "comprises" or any other variations are intended to include a non-exclusive inclusion, whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly stated or inherent to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. It should also be noted that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed herein, but may include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the methods described above may be performed in a different order than described, and further, steps may be added, omitted, or combined. Also, features described with reference to some examples may be combined with other examples.

[0127] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be realized in the form of a combination of software and a necessary general-purpose hardware platform. Of course, it can also be realized by hardware, but in many cases, the former is a more preferred embodiment. Based on this view, the technical solution of the present application can be substantially embodied in the form of a computer software product, which is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes a number of commands for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.

[0128] Although the examples of the present application have been described above with reference to the drawings, the present application is not limited to the above-mentioned specific embodiments, which are merely illustrative and not limiting. Based on the suggestions of the present application, many forms that a person skilled in the art can make without departing from the spirit of the present application and the scope of protection of the claims are all within the scope of protection of the present application.

Claims

1. A network side device determines that a reactivation of a first protocol data unit (PDU) session initiated by the terminal fails due to a network slice access control (NSAC) of a first slice; the network side device transmitting a first message to the terminal; Including, The first message is First indication information for indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice; Second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session related to the first slice after the first timer times out; The resource control method includes at least one of the following:

2. 2. The method of claim 1, wherein reactivating the first PDU session includes switching an access type of the first PDU session.

3. The first indication information includes a failure cause value, and the failure cause value is Occurrence of congestion in the network side device; and A resource shortage in the first slice; and A shortage of user plane resources for the first PDU session; and The method of claim 1 , comprising one of:

4. Before the step of the network side equipment determining that the reactivation of the first PDU session initiated by the terminal has failed due to a network slice access control (NSAC) of the first slice, the method further comprises:

4. The method according to claim 1, further comprising the step of: the network side equipment receiving a first request message transmitted from the terminal, the first request message including an identifier of the first PDU session, the first PDU session being associated with the first slice, and the first request message requesting reactivation of the first PDU session.

5. The method according to claim 4 , wherein the first message further includes third indication information for indicating that the network side device has received the first request message.

6. After the step of the network side device transmitting a first message to the terminal, the method further comprises:

5. The method of claim 4, further comprising: after the first timer times out, the network side equipment receives a second request message sent from the terminal, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

7. A step of the terminal sending a first request message to a network side device, the first request message including an identifier of a first PDU session, the first PDU session being associated with the first slice, and the first request message requesting reactivation of the first PDU session; receiving a first message sent by the terminal from the network side device; Including, The first message is First indication information for indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice; Second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session related to the first slice after the first timer times out; A method for reactivating a PDU session, comprising at least one of the following steps:

8. 8. The method of claim 7, wherein the first request message is used to indicate switching of an access type of the first PDU session.

9. After the terminal receives a first message transmitted from the network side device, the method further comprises: If the first message includes the second indication information, the terminal starts the first timer; After the first timer times out, the terminal sends a second request message, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session; The method of claim 7 further comprising:

10. After the terminal receives a first message transmitted from the network side device, the method further comprises: If the first message does not include the second indication information, the terminal starts a second timer bound to the first slice; After the second timer times out, the terminal sends a second request message, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session; The method of claim 7 further comprising:

11. Before the terminal sends a first request message to a network side device, the method further comprises: The method according to any one of claims 7 to 10, further comprising the step of the terminal determining that a target timer is not set or that the set target timer has timed out, the target timer being a timer bound to a first slice, and the first slice being a slice associated with the first PDU session.

12. After the terminal receives a first message transmitted from the network side device, the method further comprises:

8. The method of claim 7, further comprising the step of: the terminal transmitting a second request message including an identifier of the first PDU session until a number of consecutive transmissions of the reactivation request for the first PDU session reaches a preset value and the terminal terminates the reactivation request process for the first PDU session, the second request message requesting reactivation of the first PDU session.

13. A first determination module used for determining that a reactivation of a first protocol data unit (PDU) session initiated by a terminal fails due to an NSAC of a first slice; a first sending module used for sending a first message to the terminal; Equipped with The first message is First indication information for indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice; Second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session related to the first slice after the first timer times out; A resource control device comprising at least one of:

14. The apparatus of claim 13, wherein reactivating the first PDU session includes switching an access type of the first PDU session.

15. The first indication information includes a failure cause value, and the failure cause value is Occurrence of congestion in the network side device; and A resource shortage in the first slice; and A shortage of user plane resources for the first PDU session; and The apparatus of claim 13 , comprising one of:

16. 16. The apparatus according to claim 13, further comprising: a first receiving module used for receiving a first request message transmitted from the terminal, wherein the first request message includes an identifier of the first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session.

17. The apparatus according to claim 16 , wherein the first message further includes third indication information for indicating that the network side device has received the first request message.

18. 17. The apparatus of claim 16, wherein the first receiving module is further used for receiving a second request message sent from the terminal after the first timer times out, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

19. A second transmission module used for transmitting a first request message to a network side device, wherein the first request message includes an identifier of a first PDU session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session; a second receiving module for receiving a first message sent from the network side device; Equipped with The first message is First indication information for indicating that the failure of reactivation of the first PDU session is due to a failure of NSAC of the first slice; Second instruction information for indicating a first timer bound to the first slice and for instructing the terminal to re-initiate reactivation of a first PDU session related to the first slice after the first timer times out; A PDU session reactivation device including at least one of the following:

20. 20. The apparatus of claim 19, wherein the first request message is used to indicate switching of an access type of the first PDU session.

21. 20. The apparatus of claim 19, wherein the second transmitting module is further used to start the first timer when the first message includes the second indication information, and to send a second request message after the first timer times out, the second request message including an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

22. The second transmission module is further used for starting a second timer bound to the first slice when the first message does not include the second indication information, and for sending a second request message after the second timer times out, wherein the second request message includes an identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.

23. 23. The apparatus of claim 19, further comprising a second determination module used to determine that a target timer is not set or that the set target timer has timed out, the target timer being a timer bound to a first slice, the first slice being a slice associated with the first PDU session.

24. 20. The apparatus of claim 19, wherein the second transmitting module is further used for transmitting a second request message including an identifier of the first PDU session, the second request message requesting reactivation of the first PDU session, until a number of consecutive transmissions of the reactivation request of the first PDU session reaches a preset value and the terminal terminates the reactivation request process of the first PDU session.

25. A terminal comprising a processor and a memory, the memory storing a program or command executable on the processor, the terminal implementing the steps of the PDU session reactivation method according to any one of claims 7 to 12 when the program or command is executed by the processor.

26. A network side device comprising a processor and a memory, wherein a program or command executable on the processor is stored in the memory, and the network side device realizes the steps of the resource control method described in any one of claims 1 to 6 when the program or command is executed by the processor.

27. A readable storage medium on which a program or command is stored, the program or command implementing the steps of the resource control method of any one of claims 1 to 6, or the steps of the PDU session reactivation method of any one of claims 7 to 12, when executed by a processor.

Images