WO2023185929A1 - 资源控制方法、装置、终端及网络侧设备 - Google Patents

资源控制方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2023185929A1
WO2023185929A1 PCT/CN2023/084722 CN2023084722W WO2023185929A1 WO 2023185929 A1 WO2023185929 A1 WO 2023185929A1 CN 2023084722 W CN2023084722 W CN 2023084722W WO 2023185929 A1 WO2023185929 A1 WO 2023185929A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
reactivation
slice
timer
terminal
Prior art date
Application number
PCT/CN2023/084722
Other languages
English (en)
French (fr)
Inventor
于航
康艳超
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2023185929A1 publication Critical patent/WO2023185929A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • This application belongs to the field of wireless communication technology, and specifically relates to a resource control method, device, terminal and network side equipment.
  • Network slicing access control is a method for the network side to control the resources associated with the slice.
  • the resources include the number of terminals (User Equipment, UE) associated with the slice, the protocol data unit associated with the slice ( Protocol Data Unit, PDU) number of sessions and data rate associated with slices, etc.
  • this control is managed separately according to access type.
  • the session management function (Session Management Function, SMF) performs NSAC when the PDU session is established for the first time
  • the network slice admission control network element (NSACF) performs NSAC on different access Access type is used for access control, which means that the network side controls the number of PDU sessions of different 3rd Generation Partnership Project (3GPP) access and non-3GPP access types of the slice.
  • 3GPP 3rd Generation Partnership Project
  • the network side may require the terminal to change the access type of a certain PDU session from non-3GPP access to 3GPP access, and reconstruct the user plane resources on the 3GPP access.
  • the terminal receives After a request from the network side, if the Single Network Slice Selection Assistance Information (S-NSSAI) associated with the established PDU for non-3GPP access is the S-NSSAI allowed by 3GPP access, the UE can send Service request, in which the network side is notified: the terminal supports the reactivation of the PDU session, that is, the type of the PDU session is changed from non-3GPP access to 3GPP access.
  • the network side NSAC is performed before establishing the PDU for 3GPP access.
  • NSAC succeeds and the PDU is successfully established, a service acceptance message is sent to the terminal to notify the terminal. However, if NSAC fails, the network side does not notify the terminal that PDU reactivation failed due to NSAC, resulting in The terminal cannot obtain the corresponding information.
  • Embodiments of the present application provide a resource control method, device, terminal and network side equipment, which can solve the problem in the above scenario that the terminal cannot learn that the reactivation of the PDU session fails due to NSAC.
  • a first aspect provides a resource control method, including: a network side device determines that reactivation of a first PDU session initiated by a terminal fails due to NSAC of a first slice; the network side device sends the first PDU session to the terminal.
  • message wherein the first message carries at least one of the following: first indication information, used to indicate a failure reason, and the failure reason indicates that the reason for the reactivation failure of the first PDU session is the first slice
  • the NSAC fails; the second indication information is used to indicate the first timer bound to the first slice and to allow the terminal to initiate connection with the first slice again after the first timer expires. Reactivation of the associated first PDU session.
  • a resource control device including: a first determining module, configured to determine that the reactivation of the first PDU session initiated by the terminal fails due to NSAC of the first slice; a first sending module, configured to The terminal sends a first message, wherein the first message carries at least one of the following: first indication information, used to indicate that the reason for the reactivation failure of the first PDU session is the NSAC of the first slice. Failure; second indication information, used to indicate the first timer bound to the first slice and to allow the terminal to initiate another session associated with the first slice after the first timer expires. Reactivation of the first PDU session.
  • a PDU session reactivation method including: a terminal sending a first PDU session reactivation request to a network side device, wherein the first PDU session reactivation request carries an identifier of the first PDU session.
  • the first PDU session is associated with the first slice, the first request message requests reactivation of the first PDU session; the terminal receives the first message sent by the network side device, wherein, The first message carries at least one of the following: first indication information, used to indicate a failure reason, and the failure reason indicates that the reason for the reactivation failure of the first PDU session is that NSAC of the first slice fails; Two indication information, used to indicate the first timer bound to the first slice and to indicate that the terminal is allowed to initiate the first PDU associated with the first slice again after the first timer expires. Session reactivation.
  • a PDU session reactivation device including: a second sending module configured to send a first PDU session reactivation request to a network side device, wherein the first PDU session reactivation request carries Identity of the first PDU session between the first PDU session and the first Slice association, the first request message requests reactivation of the first PDU session; the second receiving module is used to receive the first message sent by the network side device, wherein the first message carries at least one of the following : The first indication information is used to indicate the cause of the failure.
  • the failure reason indicates that the reason for the reactivation failure of the first PDU session is the NSAC failure of the first slice; the second indication information is used to indicate the failure of the reactivation of the first PDU session.
  • the first timer and indication bound to the first slice allow the terminal to initiate reactivation of the first PDU session associated with the first slice again after the first timer expires.
  • a terminal in a fifth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in three aspects.
  • a sixth aspect provides a terminal, including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the third aspect, and the communication interface is used to communicate with an external device.
  • a network side device in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • a network side device including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the first aspect, and the communication interface is used to communicate with an external device.
  • a ninth aspect provides a resource control system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the method described in the third aspect.
  • the network side device can be used to perform the steps of the method described in the first aspect. steps of the method described.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented as described in the first aspect. The steps of the method described in the third aspect.
  • a chip in an eleventh aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. The steps of a method, or steps of implementing a method as described in the third aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect
  • the network side device when the network side device determines that the reactivation of the first PDU session initiated by the terminal fails due to NSAC of the first slice, the network side device sends the first indication information and/or the second indication information to the terminal,
  • the first indication information indicates that the failure reason is that the NSAC of the first slice failed.
  • Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable
  • Figure 2 shows a schematic flow chart of a resource control method in the related art
  • Figure 3 shows a schematic flow chart of the resource control method provided by the embodiment of the present application.
  • Figure 4 shows a schematic flow chart of the PDU session reactivation method provided by the embodiment of the present application
  • Figure 5 shows another schematic flow chart of the resource control method provided by the embodiment of the present application.
  • Figure 6 shows a schematic structural diagram of a resource control device provided by an embodiment of the present application.
  • Figure 7 shows a schematic structural diagram of a PDU session reactivation device provided by an embodiment of the present application.
  • Figure 8 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 9 shows a schematic diagram of the hardware structure of a terminal provided by an embodiment of the present application.
  • Figure 10 shows a schematic hardware structure diagram of a network-side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet Device
  • AR augmented reality
  • VR virtual reality
  • robots wearable devices
  • WUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side device 12 may include an access network device and/or a core network device, where the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), or a radio access network. function or radio access network unit.
  • the access network device 12 may include a base station, a Wireless Local Area Network (WLAN) access point or a Wireless Fidelity (WiFi) node, etc.
  • WLAN Wireless Local Area Network
  • WiFi Wireless Fidelity
  • the base station may be called a Node B, an Evolved Node B (eNB), Access point, Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B-node, home Evolved B-node, Transmitting Receiving Point (TRP) or some other suitable terminology in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in this article In the application embodiment, the base station in the NR system is only introduced as an example, and the specific type of the base station is not limited.
  • Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, and mobility management Entity (Mobility Management Entity, MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function ( 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 Open Function (Network Exposure Function (NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • EASDF Edge
  • Figure 2 shows a schematic process diagram in related technologies in which the network side requires the terminal to convert the access type of a certain PDU session from non-3GPP access (non-3GPP access) to 3GPP access (3GPP access).
  • Figure 2 Indicates that paging is initiated on the network side and the terminal side is required to change the access type of a certain PDU session from non-3GPP access to 3GPP access (i.e. inter-access handover).
  • the process mainly includes the following steps:
  • the UE determines whether to initiate a service request (Service Request) message. If the S-NSSAI associated with the established non-3GPP access PDU is the allowed NSSAI of 3GPP access, the UE can carry the permission in the service request message.
  • the PDU session status IE (Allowed PDU session status IE) tells the network side that the UE supports the PDU session for reactivation (that is, the type of PDU session ID is changed from non-3GPP access to 3GPP access).
  • AMF After receiving the Service Request, AMF sends it to SMF through the interface message of AMF and SMF, allowing SMF to establish a PDU session associated with S-NSSAI and 3GPP access.
  • SMF performs NSAC before establishing the PDU of 3GPP access, and sends information such as S-NSSAI and access type to NSACF.
  • SMF returns to AMF that the establishment is successful.
  • the AMF sends a Service Accept message to the UE. If the PDU is successfully established, the Service Accept message carries indication information indicating that the PDU is successfully established.
  • SMF can indicate AMF in the following ways:
  • the AMF will cause an error in the PDU session reactivation result in the Service Acceptance (SERVICE ACCEPT) message IE (PDU session reactivation result error cause IE) use 5GMM cause#43 "LADN not available (LADN not available)";
  • AMF uses 5GMM cause #28 "restricted service area (restricted service area)" in the PDU session reactivation result error cause IE in the SERVICE ACCEPT message;
  • AMF PDU session reactivation result error in the SERVICE ACCEPT message cause IE uses 5GMM cause #92 (Insufficient user-plane resources of the PDU session) "for the PDU session", how the subsequent UE re-initiates the Service Request process depends on the implementation.
  • the network side does not notify the terminal that PDU reactivation fails due to NSAC, resulting in the terminal being unable to obtain the corresponding information.
  • FIG. 3 shows a schematic flowchart of a resource control method in an embodiment of the present application.
  • the method 300 can be executed by a network side device.
  • the network side device can be a network element with a mobility management function (for example, a core network AMF network element).
  • the method may be executed by software or hardware installed on the network side device.
  • the method may include the following steps.
  • the network side device determines that reactivation of the first PDU session initiated by the terminal fails due to NSAC of the first slice.
  • the method may further include: the network side device receiving a first request message sent by the terminal, wherein the first request message carries the first PDU The identifier of the session, the first PDU session is associated with the first slice, and the first request message requests reactivation of the first PDU session. That is to say, before S310, the terminal may initiate reactivation of the first PDU session through the first request message.
  • the reactivation of the first PDU session includes switching of the access type of the first PDU session.
  • the network side can initiate paging (Paging), requiring the terminal side to change the access type of a certain PDU session from non-3GPP access to 3GPP access (ie, inter-access handover), and reconstruct the user plane resources on 3GPP access.
  • Paging paging
  • 3GPP access ie, inter-access handover
  • the terminal After receiving the paging from the network side, if the S-NSSAI associated with the first PDU of the established non-3GPP access is the allowed NSSAI of 3GPP access, the terminal can send the first request message,
  • the first request message may be a service request message, and the terminal may tell the network side that the UE supports the PDU session for reactivation (ie: PDU session status IE) carried in the first request message.
  • PDU session status IE PDU session status IE
  • the type of session ID is changed from non-3GPP access to 3GPP access).
  • the network side device sends the first message to the terminal.
  • the first message carries at least one of the following:
  • First indication information used to indicate that the reason for the failure of reactivation of the first PDU session is the failure of NSAC of the first slice; through the first indication information, the terminal can learn about the reactivation of the first PDU session The first handover fails due to NSAC failure, so that a corresponding processing solution can be adopted in subsequent procedures, for example, the terminal no longer initiates the establishment of the first PDU session associated with the first slice, etc.
  • Second indication information used to indicate the first timer bound to the first slice and to allow the terminal to initiate association with the first slice again after the first timer expires. Reactivation of the first PDU session.
  • the terminal can initiate reactivation of the first PDU session associated with the first slice again after the first timer times out, thereby avoiding the terminal from determining that the reactivation of the first PDU session has failed.
  • the signaling storm caused by the reactivation of the first PDU session is continuously initiated to achieve more efficient and reasonable slice resource management and control.
  • the second indication information may include a first timer identifier and a duration of the first timer, and the terminal may start the first timer corresponding to the second indication information according to the second indication information.
  • the first indication information includes a failure reason value
  • the failure reason value includes one of the following:
  • Congestion occurs in the network side device; for example, the first message may carry a failure cause value: 5GMM cause#22 "congestion".
  • the resources of the first slice are insufficient; for example, the first message can carry a failure cause value (cause value): 5GMM cause#69 "insufficient resources for specific slice (insufficient resources for specific slice)".
  • the user plane resources of the first PDU session are insufficient.
  • the first message may carry a failure reason value (cause value): 5GMM cause#92 "Insufficient user-plane resources for the PDU session".
  • the first message may also carry third indication information, and the third indication information is used to instruct the network side device to receive the first request message, that is, the network side device receives Service request initiated by the terminal.
  • the terminal after receiving the first message, the terminal starts the first timer. After the first timer times out, the terminal may initiate activation of the first PDU session again. Therefore, in this possible implementation, After the network side device sends the first message to the terminal, the method may further include: after the timing duration of the first timer, the network side device receives the third message sent by the terminal. Two request messages, wherein the second request message carries the identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.
  • the network side device when the network side device determines that the reactivation of the first PDU session initiated by the terminal fails due to the NSAC of the first slice, the network side device sends the first indication information and/or the second The indication information indicates that the failure reason is NSAC failure of the first slice through the first indication information, indicates the first timer bound to the first handover through the second indication information, and indicates that the terminal is allowed to operate at the first timing.
  • the server times out the reactivation of the first PDU session associated with the first slice is initiated again, so that the terminal can learn that the reactivation of the first PDU session is due to the NSAC failure of the first slice, thereby allowing the terminal to update Efficient slice resource control.
  • the network-side AMF network element After receiving an indication that the SMF return slice is temporarily unavailable due to NSAC reasons, the network-side AMF network element performs at least one of the following operations:
  • the first message carries the 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", informing the UE
  • the reason for the failure of reactivation of a specific PDU session ID is that the NSAC of the slice failed;
  • the first message carries the first timer, which is used to instruct the UE to wait for the timer to expire before initiating a reactivation request again.
  • FIG 4 shows a schematic flowchart of the PDU session reactivation method in this embodiment of the present application.
  • the method 400 can be executed by a terminal.
  • the method may be performed by software or hardware installed on the terminal.
  • the method may include the following steps.
  • the terminal sends a first request message to the network side device, where the first request message carries an identifier of the first PDU session, the first PDU session is associated with the first slice, and the first request message Requesting reactivation of the first PDU session.
  • the first request message may be a service request message.
  • the first request message is used to indicate switching of the access type of the first PDU session.
  • the terminal can, if the established non- The S-NSSAI associated with the first PDU of 3GPP access is If the 3GPP access allows NSSAI, the terminal can send a first request message, carrying the allowed PDU session status IE (Allowed PDU session status IE) in the first request message to tell the network side: the UE supports the PDU session for resumption.
  • Activation ie: the type of PDU session ID is changed from non-3GPP access to 3GPP access).
  • the terminal receives the first message sent by the network side device.
  • the network side device may use the method described in the above method 300 to send the first message to the terminal.
  • the first message is the same as the first message in the method 300.
  • the first message may carry at least one of the following:
  • First indication information used to indicate that the reason for the failure of reactivation of the first PDU session is the failure of NSAC of the first slice;
  • Second indication information used to indicate the first timer bound to the first slice and to allow the terminal to initiate association with the first slice again after the first timer expires. Reactivation of the first PDU session.
  • the first indication information may include a failure reason value
  • the failure reason value may include one of the following:
  • the first message may also carry third indication information, and the third indication information is used to instruct the network side device to receive the first request message.
  • the method may further include the following steps:
  • Step 1 If the first message carries the second indication information, the terminal starts the first timer;
  • Step 2 After the first timer times out, the terminal sends a second request message, the second request message carries the identifier of the first PDU session, and the second request message requests reactivation of the session. Describe the first PDU session.
  • the terminal when the first message carries the second indication information, the terminal can start the first timer indicated by the second indication information, and after the first timer times out, send the first PDU session again. Reactivation to avoid the problem of signaling storm caused by repeated requests for reactivation of the first PDU session and continuous network congestion, thus achieving more efficient and reasonable slice resource management and control.
  • the method may further include the following steps:
  • the terminal starts a second timer, where the second timer is bound to the first slice. timer;
  • the terminal After the second timer times out, the terminal sends a second request message, the second request message carries the identifier of the first PDU session, and the second request message requests reactivation of the Describe the first PDU session.
  • the terminal in the case where the network side device does not indicate the first timer, the terminal can start a locally set second timer bound to the first slice, and after the second timer times out, the terminal can start the second timer again.
  • the reactivation of the first PDU session is sent to avoid the problem of signaling storm caused by repeated requests for the reactivation of the first PDU session and continuous network congestion, thereby achieving more efficient and reasonable slice resource management and control.
  • the method may further include: the terminal determines that the target timer is not set or the set target timer times out, wherein , the target timer is a timer bound to a first slice, and the first slice is a slice associated with the first PDU session. That is to say, in this possible implementation, before sending the first request message, the terminal first determines whether a timer bound to the first slice (for example, the above-mentioned first timer or the second timer) is set. ) or whether the set timer bound to the first slice times out. If the first timer or the second timer is not set or the first timer or the second timer is set and times out, perform S410.
  • a timer bound to the first slice for example, the above-mentioned first timer or the second timer
  • the method may further include: the terminal sending a second request carrying the identification of the first PDU session. message until the number of times the reactivation request of the first PDU session is continuously sent reaches a preset value, the terminal terminates the reactivation request process of the first PDU session, wherein the second request message requests reactivation. Describe the first PDU session.
  • the terminal may directly initiate a reactivation request for the first PDU session again without the second indication being carried in the first message until the maximum number of times is reached. Try again.
  • the terminal can receive the first message sent by the network side device after initiating the reactivation of the PDU session, so that it can learn that the reactivation of the PDU session failed due to NSAC.
  • the terminal can also wait. Trying to reactivate the PDU session again after a period of time can prevent the UE from repeatedly requesting messages, triggering signaling storms and causing continued network congestion, and achieve more efficient and reasonable slice resource management and control.
  • the execution operation includes at least one of the following: item:
  • the UE needs to check whether there is currently a running timer bound to the slice associated with the PDU session ID. If the UE needs to reactivate the PDU session ID associated with the slice, it needs to wait until the timer expires before initiating a reactivation request;
  • the UE can immediately initiate a PDU session reactivation request, carrying the reactivated PDU session ID;
  • the UE after receiving the first message sent by the network side device, performs an operation including at least one of the following:
  • the first message received contains the cause value of PDU session ID reactivation failure, it 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", and the first message contains timer, the timer will be started in the UE. In one implementation, if the timer is 0, the UE immediately re-initiates the service request;
  • the UE performs the fourth operation, and the fourth operation may include at least one of the following:
  • the UE starts an implementation specific timer for the slice of PDU session ID associated with the above cause value.
  • the UE does not set the timer and immediately re-initiates the service request message.
  • the UE can continuously try the maximum number of times (such as 5 times), and then it will no longer try to initiate a reactivation request until the network side instructs the UE to initiate a PDU reactivation request.
  • Figure 5 shows another schematic flowchart of the resource control method according to the embodiment of the present application. As shown in Figure 5, the method 500 mainly includes the following steps:
  • the UE Before initiating the first request for PDU session reactivation, the UE determines whether a timer (timer) is set. If so, it checks whether there is currently a running timer associated with the PDU session ID slice. If so, and If the UE needs to reactivate the PDU session ID associated with the slice, then after waiting for the timer to expire, the UE executes S502; if no timer is set, or the set timer times out, or the UE needs to activate the slice associated with the PDU session If no timer is bound, the UE executes S502.
  • timer timer
  • the UE sends a service request to the network side to request PDU session reactivation.
  • the service request carries the identifier of the PDU session (PDU session ID) that needs to be activated.
  • AMF After receiving the above service request, AMF reports information including PDU session ID, S-NSSAI and other information to SMF, and uses the PDU session ID for reactivation.
  • SMF interacts with NSACF to perform NSAC.
  • SMF receives the failure feedback from NSACF, and SMF notifies AMF of the information that the current slice is unavailable due to NSAC.
  • the AMF sends a first message, where the first message carries at least one of the following:
  • Indication information used to indicate acceptance of the service request initiated by the UE
  • the reason for the activation failure is that the slice's NSAC failed.
  • the first timer is used to instruct the UE to wait for the timer to expire before initiating a reactivation request again.
  • the UE After receiving the first message, the UE performs a first operation, where the first operation includes at least one of the following:
  • A.S507-a If the first message received contains the cause value of PDU session ID reactivation failure, it 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", and the first message contains a timer, the UE starts the timer, and after the timer expires, the service request message is re-initiated. In one implementation, if the timer is 0, the UE immediately re-initiates the service request message;
  • B.S507-b If the first message received contains the cause value of PDU session ID reactivation failure, it 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 contain timer, the UE performs the second operation, and the second operation includes at least one of the following:
  • the UE starts an implementation-specific timer, and re-initiates the service request message after the timer expires for the slice of PDU session ID associated with the above cause value.
  • the UE does not set a timer for the slice and immediately re-initiates the service request message.
  • the UE can continuously try the maximum number of times (such as 5 times), and will no longer try to initiate a reactivation request until the network side instructs the UE to initiate a PDU reactivation request. .
  • the execution subject may be a resource control device.
  • the resource control device executing the resource control method is taken as an example to illustrate the resource control device provided by the embodiment of the present application.
  • Figure 6 shows a schematic structural diagram of a resource control device provided by an embodiment of the present application.
  • the device 600 mainly includes: a first determination module 601 and a first sending module 602.
  • the first determination module 601 is used to determine 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 to send the first PDU session to the terminal.
  • a message wherein the first message carries at least one of the following: first indication information, used to indicate that the reason for the reactivation failure of the first PDU session is the NSAC failure of the first slice; a second indication Information used to indicate the first timer bound to the first slice and to indicate that the terminal is allowed to initiate the first PDU session associated with the first slice again after the first timer expires. Reactivate.
  • the reactivation of the first PDU session includes switching of the access type of the first PDU session.
  • the first indication information includes a failure reason value
  • the failure reason value includes one of the following:
  • the network side device is congested
  • the first slice has insufficient resources
  • the user plane resources of the first PDU session are insufficient.
  • the device may further include: a first receiving module 603, configured to receive a first request message sent by the terminal, wherein the first request message carries There is 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.
  • a first receiving module 603 configured to receive a first request message sent by the terminal, wherein the first request message carries There is 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.
  • the first message also carries third indication information, and the third indication information is used to instruct the network side device to receive the first request message.
  • the first receiving module 603 is further configured to receive the second request message sent by the terminal after the timing duration of the first timer, wherein the second request message carries the identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.
  • Figure 7 shows a schematic structural diagram of a PDU session reactivation device provided by an embodiment of the present application.
  • the device 700 mainly includes: a second sending module 701 and a second receiving module 702.
  • the second sending module 701 is configured to send a first request message to the network side device, where the first request message carries an identifier of the first PDU session, and the first PDU session is related to The first slice association, the first request message requests reactivation of the first PDU session;
  • the second receiving module 702 is used to receive the first message sent by the network side device, wherein the first The message carries at least one of the following: first indication information, used to indicate that the first PDU will The reason for the failed reactivation of the call is that the NSAC of the first slice fails; the second indication information is used to indicate the first timer bound to the first slice and to indicate that the terminal is allowed to operate in the first slice. After a timer expires, reactivation of the first PDU session associated with the first slice is initiated again.
  • the first request message is used to indicate switching of the first PDU session access type.
  • the second sending module 701 is also configured to start the first timer when the first message carries the second indication information. After timeout, a second request message is sent, the second request message carries the identifier of the first PDU session, and the second request message requests reactivation of the first PDU session.
  • the second sending module 701 is also configured to start a second timer when the first message does not carry the second indication information, wherein the second timer The timer is a timer bound to the first slice; after the second timer times out, a second request message is sent, and the second request message carries the identifier of the first PDU session, The second request message requests reactivation of the first PDU session.
  • the device may further include: a second determination module 703, configured to determine that the target timer is not set or the set target timer times out, wherein the target timer is The timer is a timer bound to a first slice, and the first slice is a slice associated with the first PDU session.
  • a second determination module 703 configured to determine that the target timer is not set or the set target timer times out, wherein the target timer is The timer is a timer bound to a first slice, and the first slice is a slice associated with the first PDU session.
  • the second sending module 701 is further configured to send a second request message carrying the identifier of the first PDU session until the number of consecutive sending of reactivation requests of the first PDU session reaches a predetermined number. Assuming that the terminal terminates the reactivation request process of the first PDU session, wherein the second request message requests reactivation of the first PDU session.
  • the PDU session reactivation device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • the PDU session reactivation device provided by the embodiments of this application can implement each process implemented by the terminal in the method embodiments of Figures 3 to 5, and achieve the same technical effect. To avoid duplication, details will not be described here.
  • this embodiment of the present application also provides a communication device 800, which includes a processor 801 and a memory 802.
  • the memory 802 stores information that can run on the processor 801.
  • Programs or instructions for example, when the communication device 800 is a terminal, when the program or instructions are executed by the processor 801, each step of the above PDU session reactivation method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 800 is a network-side device, when the program or instruction is executed by the processor 801, each step of the above resource control method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, the details are not repeated here.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface.
  • the processor is used to implement each step of the above PDU session reactivation method embodiment, and the communication interface is used to communicate with external devices.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 9 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 900 includes 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, a processor 910, etc. At least some parts.
  • the terminal 900 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 910 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 9 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or may combine certain components, or arrange different components, which will not be described again here.
  • the input unit 904 may include a graphics processing unit (Graphics Processing Unit, GPU) 9041 and a microphone 9042.
  • the graphics processor 9041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072 .
  • Touch panel 9071 also known as touch screen.
  • the touch panel 9071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 9072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 901 after receiving downlink data from the network side device, can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network side device.
  • 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.
  • Memory 909 may be used to store software programs or instructions as well as various data.
  • the memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first The storage area can store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • memory 909 may include volatile memory or nonvolatile memory, or memory 909 may include both volatile and nonvolatile memory.
  • 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), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), 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, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 910 may include one or more processing units; optionally, the processor 910 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 910.
  • the radio frequency unit 901 is used for:
  • the network side device sends a first request message to the network side device, where the first request message carries an identifier of a first PDU session, the first PDU session is associated with the first slice, and the first request message requests Reactivate the first PDU session;
  • First indication information used to indicate that the reason for the failure of reactivation of the first PDU session is that the NSAC of the first slice fails;
  • the second indication information is used to indicate the first timer bound to the first slice and to allow the terminal to initiate the first timer associated with the first slice again after the first timer expires. Reactivation of PDU session.
  • Embodiments of the present application also provide a network-side device, including a processor and a communication interface.
  • the processor is used to implement each step of the above resource control method embodiment, and the communication interface is used to communicate with external devices.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 1000 includes: a processor 1001, a network interface 1002, and a memory 1003.
  • the network interface 1002 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1000 in this embodiment of the present invention also includes: instructions or programs stored in the memory 1003 and executable on the processor 1001.
  • the processor 1001 calls the instructions or programs in the memory 1003 to execute each of the steps shown in Figure 6.
  • the method of module execution and achieving the same technical effect will not be described in detail here to avoid duplication.
  • Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, each process of the above resource control method embodiment is implemented, or the above PDU is implemented. Each process of the session reactivation method embodiment can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above resource control method embodiment.
  • Each process, or each process of implementing the above PDU session reactivation method embodiment, can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above resource control method embodiment.
  • Each process, or each process of implementing the above PDU session reactivation method embodiment can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • Embodiments of the present application also provide a resource control system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the PDU session reactivation method as described above.
  • the network side device can be used to perform the steps of the PDU session reactivation method as described above. The steps of the resource control method.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种资源控制方法、装置、终端及网络侧设备，属于无线通信领域，本申请实施例的资源控制方法，包括：网络侧设备确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败；所述网络侧设备向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。

Description

资源控制方法、装置、终端及网络侧设备
交叉引用
本发明要求在2022年03月29日提交中国专利局、申请号为202210320869.9、发明名称为“资源控制方法、装置、终端及网络侧设备”的中国专利申请的优先权，该申请的全部内容通过引用结合在本发明中。
技术领域
本申请属于无线通信技术领域，具体涉及一种资源控制方法、装置、终端及网络侧设备。
背景技术
网络切片准入控制(network slicing access control，NSAC)是一种网络侧对切片相关联的资源进行控制的方法，资源包括切片关联的终端(User Equipment，UE)数量、切片关联的协议数据单元(Protocol Data Unit，PDU)会话(session)数量以及切片关联的数据速率等。另外，这种控制是按照接入类型(access type)分开管控的。
在相关技术中，如果关联的切需要做NSAC，则会话管理功能(Session Management Function，SMF)在第一次建立PDU会话时执行NSAC，并且网络切片准入控制网元(NSACF)对不同接入类型(access type)进行准入控制，也就是说网络侧对切片的不同第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)接入和非3GPP接入类型的PDU会话(session)进行数量控制，如果某一切片关联的某一access type的PDU session数量达到了最大值，则SMF就会拒绝使用该切片在这一access type上建立PDU会话。
在相关技术中，在某些情况下，网络侧可能要求终端将某一个PDU会话的接入类型由非3GPP接入转为3GPP接入，在3GPP接入上重建用户面资源，终端在接收到网络侧的请求后，如果已经建立的非3GPP接入的PDU关联的单一网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)是3GPP接入允许的S-NSSAI，则UE可以发送服务请求，在该请求中通知网络侧：终端支持该PDU会话进行重激活，即该PDU会话的类型由非3GPP接入转为3GPP接入，网络侧在接收终端的请求后， 在建立3GPP接入的PDU之前进行NSAC，如果NSAC成功并PDU建立成功，则向终端发送服务接受消息通知终端，但如果NSAC失败，网络侧并不会通知终端PDU重激活因NSAC而失败，导致终端不能获知相应的信息。
发明内容
本申请实施例提供一种资源控制方法、装置、终端及网络侧设备，能够解决上述场景中终端不能获知PDU会话的重激活因NSAC而失败的问题。
第一方面，提供了一种资源控制方法，包括：网络侧设备确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败；所述网络侧设备向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示失败原因，所述失败原因指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
第二方面，提供了一种资源控制装置，包括：第一确定模块，用于确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败；第一发送模块，用于向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
第三方面，提供了一种PDU会话重激活方法，包括：终端向网络侧设备发送第一PDU会话重激活请求，其中，所述第一PDU会话重激活请求中携带有第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话；所述终端接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示失败原因，所述失败原因指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
第四方面，提供了一种PDU会话重激活装置，包括：第二发送模块，用于向网络侧设备发送第一PDU会话重激活请求，其中，所述第一PDU会话重激活请求中携带有第一PDU会话的标识，所述第一PDU会话与所述第一 切片关联，所述第一请求消息请求重激活所述第一PDU会话；第二接收模块，用于接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示失败原因，所述失败原因指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于实现如第三方面所述的方法的步骤，所述通信接口用于与外部设备进行通信。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于实现如第一方面所述的方法的步骤，所述通信接口用于与外部设备进行通信。
第九方面，提供了一种资源控制***，包括：终端及网络侧设备，所述终端可用于执行如第三方面所述的方法的步骤，所述网络侧设备可用于执行如第一方面所述的方法的步骤。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法的步骤，或实现如第三方面所述的方法的步骤。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或实现如第三方面所述的方法的步骤。
在本申请实施例中，网络侧设备在确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败的情况下，向终端发送第一指示信息和/或第二指示信息，通过第一指示信息指示失败原因为是第一切片的NSAC失败，通 过第二指示信息指示与第一切换绑定的第一定时器，指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活，从而使得终端可以获知第一PDU会话的重激活是因为第一切片的NSAC失败，进而使得终端可以进行更高效的切片资源控制。
附图说明
图1示出本申请实施例可应用的一种无线通信***的框图；
图2示出相关技术中一种资源控制方法的流程示意图；
图3示出本申请实施例提供的资源控制方法的一种流程示意图；
图4示出本申请实施例提供的PDU会话重激活方法的一种流程示意图；
图5示出本申请实施例提供的资源控制方法的另一种流程示意图
图6示出本申请实施例提供的资源控制装置的一种结构示意图
图7示出本申请实施例提供的PDU会话重激活装置的一种结构示意图；
图8示出本申请实施例提供的一种通信设备的结构示意图；
图9示出本申请实施例提供的一种终端的硬件结构示意图；
图10示出本申请实施例提供的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)***，还可用于其他无线通信***，诸如码分多址(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)和其他***。本申请实施例中的术语“***”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的***和无线电技术，也可用于其他***和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)***，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR***应用以外的应用，如第6代(6th Generation，6G)通信***。
图1示出本申请实施例可应用的一种无线通信***的框图。无线通信***包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备和/或核心网设备，其中，接入网设备12也可以称为无线接入网设备、无线接入网(Radio Access Network，RAN)、无线接入网功能或无线接入网单元。接入网设备12可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或无线保真(Wireless Fidelity，WiFi)节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR***中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理 实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR***中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
图2示出相关技术中网络侧要求终端将某一个PDU会话的接入类型由非3GPP接入(non-3GPP access)转为3GPP接入(3GPP access)的一种流程示意图，如图2所示，在网络侧发起寻呼(Paging)，要求终端侧将某一PDU session的接入类型由non-3GPP access转为3GPP access(即inter-access handover)，在3GPP access上重建用户面资源后，该流程主要包括以下步骤：
S201、UE判断是否发起服务请求(Service Request)消息，如果已经建立的non-3GPP access的PDU关联的S-NSSAI是3GPP access的允许(allowed)NSSAI，则UE就可以在服务请求消息中携带允许的PDU会话状态IE(Allowed PDU session status IE)中告诉网络侧：UE支持该PDU session进行重激活(即：PDU session ID的类型由non-3GPP access转为3GPP access)。
S202、AMF收到Service Request之后，通过AMF和SMF的接口消息发给SMF，让SMF建立一个与S-NSSAI和3GPP access关联的PDU session。
S203、SMF在建立3GPP access的PDU之前进行NSAC，将S-NSSAI和access type等信息发送给NSACF。
S204-1、如果NSAC成功并且PDU建立成功，则SMF返回给AMF建立成功。
S204-2、如果因为某些原因导致的PDU建立失败，则根据不同的情况，SMF指示不同的信息给AMF。
S205、AMF向UE发送服务接受(Service Accept)消息，如果PDU建立成功，服务接受消息中携带有PDU建立成功的指示信息。
其中，在S204-2中，SMF可以采用以下方式指示AMF：
(1)如果SMF指示AMF，UE不在本地区域数据网(Local Area Data Network，LADN)的服务区，则AMF在服务接受(SERVICE ACCEPT)消息中的PDU会话重新激活结果错误原因IE(PDU session reactivation result error cause IE)使用5GMM cause#43"LADN不可用(LADN not available)"；
(2)如果SMF指示AMF，只允许建立高优先级的服务，则AMF在SERVICE ACCEPT消息中的PDU session reactivation result error cause IE使用5GMM cause#28"限制服务区(restricted service area)"；
(3)如果SMF指示AMF，用户面的资源不可用，则AMF在SERVICE ACCEPT消息中的PDU session reactivation result error cause IE使用5GMM cause#92"(PDU会话的用户面资源不足)insufficient user-plane resources for the PDU session"，后续UE如何重新发起Service Request流程取决于实现。
由此可见，在相关技术中，网络侧并不会通知终端PDU重激活因NSAC而失败，导致终端不能获知相应的信息。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的资源控制方法进行详细地说明。
图3示出本申请实施例中的资源控制方法的一种流程示意图，该方法300可以由网络侧设备执行，可选地，网络侧设备可以是具有移动管理功能的网元(例如，核心网的AMF网元)。换言之，所述方法可以由安装在网络侧设备上的软件或硬件来执行。如图3所示，该方法可以包括以下步骤。
S310、网络侧设备确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败。
在一个可能的实现方式中，在S310之前，该方法还可以包括：所述网络侧设备接收所述终端发送的第一请求消息，其中，所述第一请求消息中携带有所述第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话。也就是说，在S310之前，终端可以通过第一请求消息发起第一PDU会话的重激活。
在一个可能的实现方式中，所述第一PDU会话的重激活包括所述第一PDU会话接入类型的切换。例如，网络侧可以发起寻呼(Paging)，要求终端侧将某一PDU session的接入类型由non-3GPP access转为3GPP access(即inter-access handover)，在3GPP access上重建用户面资源，终端在接收到网络侧的寻呼后，如果已经建立的non-3GPP access的第一PDU关联的S-NSSAI是3GPP access的允许(allowed)NSSAI，则终端可以发送第一请求消息， 该第一请求消息可以为服务请求消息，终端可以在第一请求消息中携带允许的PDU会话状态IE(Allowed PDU session status IE)中告诉网络侧：UE支持该PDU session进行重激活(即：PDU session ID的类型由non-3GPP access转为3GPP access)。
S312、所述网络侧设备向所述终端发送第一消息。
在本申请实施例中，所述第一消息携带以下至少之一：
(1)第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；通过第一指示信息，终端可以获知第一PDU会话的重激活因第一切换的NSAC失败而失败，从而可以在后续程序中采用相应的处理方案，例如，终端不再发起第一切片关联的第一PDU会话的建立等。
(2)第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。通过第二指示信息，使得终端可以在第一定时器超时后，再次发起与第一切片关联的第一PDU会话的重激活，从而可以避免终端在确定第一PDU会话的重激活失败后，不停地重复发起第一PDU会话的重激活而导致的信令风暴，实现较为高效合理的切片资源管控。
在本申请实施例中，第二指示信息可以包括第一定时器标识和第一定时器的时长，终端根据第二指示信息，可以启动与第二指示信息对应的第一定时器。
在一个可能的实现方式中，所述第一指示信息包括失败原因值，所述失败原因值包括以下之一：
(1)所述网络侧设备发生拥塞；例如，第一消息中可以携带失败原因值(cause value)：5GMM cause#22"拥塞(congestion)"。
(2)所述第一切片的资源不足；例如，第一消息中可以携带失败原因值(cause value)：5GMM cause#69"特定切片的资源不足(insufficient resources for specific slice)"。
(3)所述第一PDU会话的用户面资源不足。例如，第一消息中可以携带失败原因值(cause value)：5GMM cause#92"该PDU会话的用户面资源不足(insufficient user-plane resources for the PDU session)"。
在一个可能的实现方式中，所述第一消息中还可以携带有第三指示信息，所述第三指示信息用于指示所述网络侧设备接收所述第一请求消息，即网络侧设备接收终端发起的服务请求。
在一个可能的实现方式中，终端在接收到第一消息后，启动第一定时器，在第一定时器超时后，可能会再次发起第一PDU会话的激活，因此，在该可能的实现方式，在所述网络侧设备向所述终端发送第一消息之后，所述方法还可以包括：在所述第一定时器的定时时长之后，所述网络侧设备接收所述终端发送的所述第二请求消息，其中，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
通过本申请实施例提供的技术方案，网络侧设备在确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败的情况下，向终端发送第一指示信息和/或第二指示信息，通过第一指示信息指示失败原因为是第一切片的NSAC失败，通过第二指示信息指示与第一切换绑定的第一定时器，指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活，从而使得终端可以获知第一PDU会话的重激活是因为第一切片的NSAC失败，进而使得终端可以进行更高效的切片资源控制。
例如，网络侧AMF网元在收到SMF返回切片由于NSAC原因暂时不可用的指示之后，执行操作包括以下至少一项：
A.发送第一消息，用于接受UE发起的服务请求；
B.第一消息中携带第一cause value：5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，告知UE特定PDU session ID重激活失败的原因是切片的NSAC失败；
C.第一消息中携带第一timer，用于指示UE等待timer到期之后再次发起重激活请求。
图4示出本申请实施例中的PDU会话重激活方法的一种流程示意图，该方法400可以由终端执行。换言之，所述方法可以由安装在终端上的软件或硬件来执行。如图4所示，该方法可以包括以下步骤。
S410、终端向网络侧设备发送第一请求消息，其中，所述第一请求消息中携带有第一PDU会话的标识，所述第一PDU会话与第一切片关联，所述第一请求消息请求重激活所述第一PDU会话。
在本申请实施例中，第一请求消息可以为服务请求消息。
可选地，所述第一请求消息用于指示所述第一PDU会话的接入类型的切换。例如，终端可以在接收到网络侧发起的要求终端侧将某一PDU session的接入类型由non-3GPP access转为3GPP access(即inter-access handover)的寻呼后，如果已经建立的non-3GPP access的第一PDU关联的S-NSSAI是 3GPP access的允许(allowed)NSSAI，则终端可以发送第一请求消息，在第一请求消息中携带允许的PDU会话状态IE(Allowed PDU session status IE)中告诉网络侧：UE支持该PDU session进行重激活(即：PDU session ID的类型由non-3GPP access转为3GPP access)。
S412、所述终端接收所述网络侧设备发送的第一消息。
其中，网络侧设备可以采用上述方法300所描述的方法向终端发送第一消息，所述第一消息与方法300中的第一消息相同，具体可以参见方法300中的描述，在此不再赘述。
在本申请实施例中，所述第一消息可以携带以下至少之一：
(1)第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
(2)第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
在一个可能的实现方式中，所述第一指示信息可以包括失败原因值，所述失败原因值包括以下之一：
(1)所述网络侧设备发生拥塞；
(2)所述第一切片的资源不足；
(3)所述第一PDU会话的用户面资源不足。
在一个可能的实现方式中，所述第一消息中还可以携带有第三指示信息，所述第三指示信息用于指示所述网络侧设备接收所述第一请求消息。
在一个可能的实现方式中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还可以包括以下步骤：
步骤1，在所述第一消息中携带所述第二指示信息的情况下，所述终端启动所述第一定时器；
步骤2，在所述第一定时器超时后，所述终端发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
在上述可能的实现方式中，在第一消息中携带第二指示信息的情况下，终端可以启动第二指示信息指示的第一定时器，在第一定时器超时后，再次发送第一PDU会话的重激活，以避免不停地重复请求第一PDU会话的重激活而引发信令风暴使得网络持续拥塞的问题，从而可以实现较为高效合理的切片资源管控。
在另一个可能的实现方式中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还可以包括以下步骤：
(1)在所述第一消息中未携带所述第二指示信息的情况下，所述终端启动第二定时器，其中，所述第二定时器为与所述第一切片绑定的定时器；
(2)在所述第二定时器超时后，所述终端发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
在上述可能的实现方式中，在网络侧设备没有指示第一定时器的情况下，终端可以启动本地设置的与第一切片绑定的第二定时器，在第二定时器超时后，再次发送第一PDU会话的重激活，以避免不停地重复请求第一PDU会话的重激活而引发信令风暴使得网络持续拥塞的问题，从而可以实现较为高效合理的切片资源管控。
在一个可能的实现方式中，在所述终端向网络侧设备发送第一请求消息之前，所述方法还可以包括：所述终端确定未设置目标定时器或者设置的所述目标定时器超时，其中，所述目标定时器为第一切片绑定的定时器，所述第一切片为所述第一PDU会话关联的切片。也就是说，在该可能的实现方式中，终端在发送第一请求消息之前，首先判断是否设置有与第一切片绑定的定时器(例如，上述的第一定时器或第二定时器)或者设置的与第一切片绑定的定时器是否超时，在未设置第一定时器或第二定时器或设置有第一定时器或第二定时器超时的情况下，执行S410。
在又一个可能的实现方式中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还可以包括：所述终端发送携带所述第一PDU会话的标识的第二请求消息，直至所述第一PDU会话的重激活请求连续发送的次数到达预设值，所述终端终止所述第一PDU会话的重激活请求流程，其中，所述第二请求消息请求重激活所述第一PDU会话。在该可能的实现方式中，终端可以在接收到第一消息后，在第一消息中未携带第二指示的情况下，直接再次发起第一PDU会话的重激活请求，直至达到最大次数之后不再尝试。
在本申请实施例中，终端可以在发起PDU会话的重激活后，接收网络侧设备发送的第一消息，从而可以获知PDU会话的重激活因NSAC而失败，可选地，终端还可以在等待一段时间之后再次尝试该PDU会话的重激活，可以防止UE不停地重复请求消息引发信令风暴让网络持续拥塞，实现较为高效合理的切片资源管控。
例如，UE在发起PDU session重激活流程时，执行操作包括以下至少一 项：
A.如果有设置定时器(timer)，UE需要检查当前是否有正在运行的与PDU session ID关联切片绑定的timer。如果UE需要重激活该切片关联的PDU session ID，则需要等timer到期之后才能发起重激活请求；
B.如果没有设置timer，UE可以立即发起PDU session重激活请求，携带重激活的PDU session ID；
另外，UE在收到网络侧设备发送的第一消息之后，执行操作包括以下至少一项：
A.如果收到第一消息中包含PDU session ID重激活失败的cause value是5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，并且第一消息中包含timer，则在UE启动timer计时。在一种实施方式中，如果timer是0，UE立即重新发起服务请求；
B.如果收到第一消息中包含PDU session ID重激活失败的cause value是5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，但是第一消息中不包含timer，则UE执行第四操作，第四操作可以包括以下至少一项：
1)UE启动一个具体实施(implementation specific)的timer，针对上述cause value关联的PDU session ID的切片。
2)UE不设置timer并且立即重新发起服务请求消息，UE可以连续尝试最大次数(如5次)，之后将不再尝试发起重激活请求，直到网络侧再起指示UE发起PDU重激活请求。
图5示出本申请实施例的资源控制方法的另一种流程示意图，如图5所示，该方法500主要包括以下步骤：
S501、在发起PDU会话重激活的第一请求之前，UE判断是否有设置定时器(timer)，如果设置有，则检查当前是否有正在运行的与PDU session ID关联切片的timer，如果有，且UE需要重激活该切片关联的PDU session ID，则在等timer到期之后，UE执行S502；如果未设置有定时器，或者设置的定时器超时，或者，UE需要激活的PDU会话所关联的切片未绑定有定时器，则UE执行S502。
S502、UE向网络侧发送服务请求，请求PDU会话重激活，该服务请求中携带有需要激活的PDU会话的标识(PDU session ID)。
S503、AMF接收到上述服务请求后，将包括PDU session ID、S-NSSAI等信息报给SMF，使用该PDU session ID进行重激活。
S504、SMF与NSACF交互进行NSAC。
S505、SMF接收到NSACF的失败反馈，SMF将当前切片由于NSAC不可用的信息告诉AMF。
S506、AMF发送第一消息，所述第一消息携带以下至少一项：
A.指示信息，用于指示接受UE发起的服务请求；
B.第一cause value：5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，告知UE特定PDU session ID重激活失败的原因是切片的NSAC失败。
C.第一timer，用于指示UE等待timer到期之后再次发起重激活请求。
S507、UE在收到第一消息之后，执行第一操作，所述第一操作包括以下至少一项：
A.S507-a：如果收到第一消息中包含PDU session ID重激活失败的cause value是5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，并且第一消息中包含timer，则在UE启动timer计时，在该timer到期后，重新发起服务请求消息。在一种实施方式中，如果timer是0，UE立即重新发起服务请求消息；
B.S507-b：如果收到第一消息中包含PDU session ID重激活失败的cause value是5GMM cause#22"congestion"或者5GMM cause#69"insufficient resources for specific slice"或者5GMM cause#92"insufficient user-plane resources for the PDU session"，但是第一消息中不包含timer，则UE执行第二操作，第二操作包括以下至少一项：
1)UE启动一个implementation specific的timer，针对上述cause value关联的PDU session ID的切片，在timer到期后，重新发起服务请求消息。
2)UE不为该切片设置timer并且立即重新发起服务请求消息，UE可以连续尝试最大次数(如5次)，之后将不再尝试发起重激活请求，直到网络侧再起指示UE发起PDU重激活请求。
本申请实施例提供的资源控制方法，执行主体可以为资源控制装置。本申请实施例中以资源控制装置执行资源控制方法为例，说明本申请实施例提供的资源控制装置。
图6示出本申请实施例提供的资源控制装置的一种结构示意图，如图6所示，该装置600主要包括：第一确定模块601和第一发送模块602。
在本申请实施例中，第一确定模块601，用于确定终端发起的第一PDU会话的重激活因第一切片的NSAC而失败；第一发送模块602，用于向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
在一个可能的实现方式中，所述第一PDU会话的重激活包括所述第一PDU会话接入类型的切换。
在一个可能的实现方式中，所述第一指示信息包括失败原因值，所述失败原因值包括以下之一：
所述网络侧设备发生拥塞；
所述第一切片的资源不足；
所述第一PDU会话的用户面资源不足。
在一个可能的实现方式中，如图6所示，所述装置还可以包括：第一接收模块603，用于接收所述终端发送的第一请求消息，其中，所述第一请求消息中携带有所述第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话。
在一个可能的实现方式中，所述第一消息中还携带有第三指示信息，所述第三指示信息用于指示所述网络侧设备接收所述第一请求消息。
在一个可能的实现方式中，第一接收模块603，还用于在所述第一定时器的定时时长之后，接收所述终端发送的所述第二请求消息，其中，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
图7示出本申请实施例提供的PDU会话重激活装置的一种结构示意图，如图7所示，该装置700主要包括：第二发送模块701和第二接收模块702。
在本申请实施例中，第二发送模块701，用于向网络侧设备发送第一请求消息，其中，所述第一请求消息中携带有第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话；第二接收模块702，用于接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：第一指示信息，用于指示所述第一PDU会 话的重激活失败的原因是所述第一切片的NSAC失败；第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
在一个可能的实现方式中，所述第一请求消息用于指示所述第一PDU会话接入类型的切换。
在一个可能的实现方式中，第二发送模块701，还用于在所述第一消息中携带所述第二指示信息的情况下，启动所述第一定时器，在所述第一定时器超时后，发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
在一个可能的实现方式中，所述第二发送模块701，还用于在所述第一消息中未携带所述第二指示信息的情况下，启动第二定时器，其中，所述第二定时器为与所述第一切片绑定的定时器；在所述第二定时器超时后，发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
在一个可能的实现方式中，如图7所示，所述装置还可以包括：第二确定模块703，用于确定未设置目标定时器或者设置的所述目标定时器超时，其中，所述目标定时器为第一切片绑定的定时器，所述第一切片为所述第一PDU会话关联的切片。
在一个可能的实现方式中，第二发送模块701，还用于发送携带所述第一PDU会话的标识的第二请求消息，直至所述第一PDU会话的重激活请求连续发送的次数到达预设值，所述终端终止所述第一PDU会话的重激活请求流程，其中，所述第二请求消息请求重激活所述第一PDU会话。
本申请实施例中的PDU会话重激活装置可以是电子设备，例如具有操作***的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的PDU会话重激活装置能够实现图3至图5的方法实施例中终端实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图8所示，本申请实施例还提供一种通信设备800，包括处理器801和存储器802，存储器802上存储有可在所述处理器801上运行的 程序或指令，例如，该通信设备800为终端时，该程序或指令被处理器801执行时实现上述PDU会话重激活方法实施例的各个步骤，且能达到相同的技术效果。该通信设备800为网络侧设备时，该程序或指令被处理器801执行时实现上述资源控制方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，处理器用于实现上述PDU会话重激活方法实施例的各个步骤，通信接口用于与外部设备进行通信。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图9为实现本申请实施例的一种终端的硬件结构示意图。
该终端900包括但不限于：射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909以及处理器910等中的至少部分部件。
本领域技术人员可以理解，终端900还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理***与处理器910逻辑相连，从而通过电源管理***实现管理充电、放电、以及功耗管理等功能。图9中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元904可以包括图形处理单元(Graphics Processing Unit，GPU)9041和麦克风9042，图形处理器9041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元906可包括显示面板9061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板9061。用户输入单元907包括触控面板9071以及其他输入设备9072中的至少一种。触控面板9071，也称为触摸屏。触控面板9071可包括触摸检测装置和触摸控制器两个部分。其他输入设备9072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元901接收来自网络侧设备的下行数据后，可以传输给处理器910进行处理；另外，射频单元901可以向网络侧设备发送上行数据。通常，射频单元901包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器909可用于存储软件程序或指令以及各种数据。存储器909可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一 存储区可存储操作***、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器909可以包括易失性存储器或非易失性存储器，或者，存储器909可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器909包括但不限于这些和任意其它适合类型的存储器。
处理器910可包括一个或多个处理单元；可选的，处理器910集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作***、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器910中。
其中，射频单元901，用于：
向网络侧设备发送第一请求消息，其中，所述第一请求消息中携带有第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话；
接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：
第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，处理器用于实现上述资源控制方法实施例的各个步骤，通信接口用于与外部设备进行通信。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能 达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图10所示，该网络侧设备1000包括：处理器1001、网络接口1002和存储器1003。其中，网络接口1002例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备1000还包括：存储在存储器1003上并可在处理器1001上运行的指令或程序，处理器1001调用存储器1003中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述资源控制方法实施例的各个过程，或者实现上述PDU会话重激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述资源控制方法实施例的各个过程，或者实现上述PDU会话重激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为***级芯片，***芯片，芯片***或片上***芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述资源控制方法实施例的各个过程，或者实现上述PDU会话重激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种资源控制***，包括：终端及网络侧设备，所述终端可用于执行如上所述的PDU会话重激活方法的步骤，所述网络侧设备可用于执行如上所述的资源控制方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情 况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (27)

  1. 一种资源控制方法，包括：
    网络侧设备确定终端发起的第一协议数据单元PDU会话的重激活因第一切片的网络切片准入控制NSAC而失败；
    所述网络侧设备向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：
    第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
    第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
  2. 根据权利要求1所述的方法，其中，所述第一PDU会话的重激活包括所述第一PDU会话接入类型的切换。
  3. 根据权利要求1所述的方法，其中，所述第一指示信息包括失败原因值，所述失败原因值包括以下之一：
    所述网络侧设备发生拥塞；
    所述第一切片的资源不足；
    所述第一PDU会话的用户面资源不足。
  4. 根据权利要求1至3任一项所述的方法，其中，在网络侧设备确定终端发起的第一PDU会话的重激活因第一切片的网络切片准入控制NSAC而失败之前，所述方法还包括：
    所述网络侧设备接收所述终端发送的第一请求消息，其中，所述第一请求消息中携带有所述第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话。
  5. 根据权利要求4所述的方法，其中，所述第一消息中还携带有第三指示信息，所述第三指示信息用于指示所述网络侧设备接收所述第一请求消息。
  6. 根据权利要求4所述的方法，其中，在所述网络侧设备向所述终端发送第一消息之后，所述方法还包括：
    在所述第一定时器的定时时长之后，所述网络侧设备接收所述终端发送的所述第二请求消息，其中，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  7. 一种PDU会话重激活方法，包括：
    终端向网络侧设备发送第一请求消息，其中，所述第一请求消息中携带有第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话；
    所述终端接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：
    第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
    第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
  8. 根据权利要求7所述的方法，其中，所述第一请求消息用于指示所述第一PDU会话的接入类型的切换。
  9. 根据权利要求7所述的方法，其中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还包括：
    在所述第一消息中携带所述第二指示信息的情况下，所述终端启动所述第一定时器；
    在所述第一定时器超时后，所述终端发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  10. 根据权利要求7所述的方法，其中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还包括：
    在所述第一消息中未携带所述第二指示信息的情况下，所述终端启动第二定时器，其中，所述第二定时器为与所述第一切片绑定的定时器；
    在所述第二定时器超时后，所述终端发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  11. 根据权利要求7至10任一项所述的方法，其中，在所述终端向网络侧设备发送第一请求消息之前，所述方法还包括：
    所述终端确定未设置目标定时器或者设置的所述目标定时器超时，其中，所述目标定时器为第一切片绑定的定时器，所述第一切片为所述第一PDU会话关联的切片。
  12. 根据权利要求7所述的方法，其中，在所述终端接收所述网络侧设备发送的第一消息之后，所述方法还包括：
    所述终端发送携带所述第一PDU会话的标识的第二请求消息，直至所述第一PDU会话的重激活请求连续发送的次数到达预设值，所述终端终止所述第一PDU会话的重激活请求流程，其中，所述第二请求消息请求重激活所述第一PDU会话。
  13. 一种资源控制装置，包括：
    第一确定模块，用于确定终端发起的第一协议数据单元PDU会话的重激活因第一切片的NSAC而失败；
    第一发送模块，用于向所述终端发送第一消息，其中，所述第一消息携带以下至少之一：
    第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
    第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
  14. 根据权利要求13所述的装置，其中，所述第一PDU会话的重激活包括所述第一PDU会话接入类型的切换。
  15. 根据权利要求13所述的装置，其中，所述第一指示信息包括失败原因值，所述失败原因值包括以下之一：
    所述网络侧设备发生拥塞；
    所述第一切片的资源不足；
    所述第一PDU会话的用户面资源不足。
  16. 根据权利要求13至15任一项所述的装置，其中，所述装置还包括：第一接收模块，用于接收所述终端发送的第一请求消息，其中，所述第一请求消息中携带有所述第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话。
  17. 根据权利要求16所述的装置，其中，所述第一消息中还携带有第三指示信息，所述第三指示信息用于指示所述网络侧设备接收所述第一请求消息。
  18. 根据权利要求16所述的装置，其中，所述第一接收模块，还用于在所述第一定时器的定时时长之后，接收所述终端发送的所述第二请求消息，其中，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  19. 一种PDU会话重激活装置，包括：
    第二发送模块，用于向网络侧设备发送第一请求消息，其中，所述第一请求消息中携带有第一PDU会话的标识，所述第一PDU会话与所述第一切片关联，所述第一请求消息请求重激活所述第一PDU会话；
    第二接收模块，用于接收所述网络侧设备发送的第一消息，其中，所述第一消息携带以下至少之一：
    第一指示信息，用于指示所述第一PDU会话的重激活失败的原因是所述第一切片的NSAC失败；
    第二指示信息，用于指示与所述第一切片绑定的第一定时器以及指示允许所述终端在所述第一定时器超时后再次发起与所述第一切片关联的第一PDU会话的重激活。
  20. 根据权利要求19所述的装置，其中，所述第一请求消息用于指示所述第一PDU会话接入类型的切换。
  21. 根据权利要求19所述的装置，其中，所述第二发送模块，还用于在所述第一消息中携带所述第二指示信息的情况下，启动所述第一定时器，在所述第一定时器超时后，发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  22. 根据权利要求19所述的装置，其中，所述第二发送模块，还用于在所述第一消息中未携带所述第二指示信息的情况下，启动第二定时器，其中，所述第二定时器为与所述第一切片绑定的定时器；在所述第二定时器超时后，发送第二请求消息，所述第二请求消息中携带有所述第一PDU会话的标识，所述第二请求消息请求重激活所述第一PDU会话。
  23. 根据权利要求19至22任一项所述的装置，其中，所述装置还包括：第二确定模块，用于确定未设置目标定时器或者设置的所述目标定时器超时，其中，所述目标定时器为第一切片绑定的定时器，所述第一切片为所述第一PDU会话关联的切片。
  24. 根据权利要求19所述的装置，其中，所述第二发送模块，还用于发送携带所述第一PDU会话的标识的第二请求消息，直至所述第一PDU会话的重激活请求连续发送的次数到达预设值，所述终端终止所述第一PDU会话的重激活请求流程，其中，所述第二请求消息请求重激活所述第一PDU会话。
  25. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求7至12任一项所述的PDU会话重激活方法的步骤。
  26. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述 处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至6任一项所述的资源控制方法的步骤。
  27. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至6任一项所述的资源控制方法的步骤，或者实现如权利要求7至12任一项所述的PDU会话重激活方法的步骤。
PCT/CN2023/084722 2022-03-29 2023-03-29 资源控制方法、装置、终端及网络侧设备 WO2023185929A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210320869.9 2022-03-29
CN202210320869.9A CN116939889A (zh) 2022-03-29 2022-03-29 资源控制方法、装置、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2023185929A1 true WO2023185929A1 (zh) 2023-10-05

Family

ID=88199314

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084722 WO2023185929A1 (zh) 2022-03-29 2023-03-29 资源控制方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN116939889A (zh)
WO (1) WO2023185929A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180367980A1 (en) * 2017-06-19 2018-12-20 Samsung Electronics Co., Ltd. Method and apparatus for network virtualization and session management
CN110495214A (zh) * 2017-04-19 2019-11-22 Lg电子株式会社 用于处理pdu会话建立过程的方法和amf节点
CN111107664A (zh) * 2018-10-26 2020-05-05 电信科学技术研究院有限公司 一种资源管理方法、会话管理功能实体及设备
US20200305118A1 (en) * 2019-03-19 2020-09-24 Comcast Cable Communications, Llc Wireless Communications for Communication Setup/Response
EP3941116A1 (en) * 2020-07-17 2022-01-19 Apple Inc. Pdu session handover

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110495214A (zh) * 2017-04-19 2019-11-22 Lg电子株式会社 用于处理pdu会话建立过程的方法和amf节点
US20180367980A1 (en) * 2017-06-19 2018-12-20 Samsung Electronics Co., Ltd. Method and apparatus for network virtualization and session management
CN111107664A (zh) * 2018-10-26 2020-05-05 电信科学技术研究院有限公司 一种资源管理方法、会话管理功能实体及设备
US20200305118A1 (en) * 2019-03-19 2020-09-24 Comcast Cable Communications, Llc Wireless Communications for Communication Setup/Response
EP3941116A1 (en) * 2020-07-17 2022-01-19 Apple Inc. Pdu session handover

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NEC: "TS23.501 Correction to the NSAC to maintain service continuity", 3GPP DRAFT; S2-2105666, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210816 - 20210827, 10 August 2021 (2021-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052055881 *

Also Published As

Publication number Publication date
CN116939889A (zh) 2023-10-24

Similar Documents

Publication Publication Date Title
WO2022017359A1 (zh) 直接通信启动控制方法及相关设备
US20230336968A1 (en) Method for controlling secondary cell group, terminal, and network-side device
CN115209492B (zh) 通信处理方法、装置及相关设备
WO2023185929A1 (zh) 资源控制方法、装置、终端及网络侧设备
WO2023185845A1 (zh) 通信方法、装置及相关设备
WO2023131286A1 (zh) 资源控制方法、装置、终端、网络侧设备及可读存储介质
WO2023185728A1 (zh) 业务处理方法、装置、终端、网络侧设备及可读存储介质
WO2023207947A1 (zh) 小区重配置方法、装置、终端及网络侧设备
WO2024022267A1 (zh) 算力任务迁移方法及通信设备
WO2023202560A1 (zh) 辅小区组信息发送方法、接收方法、终端、设备和介质
WO2023143436A1 (zh) 数据转发的方法、装置、终端设备和网络设备
WO2024022389A1 (zh) 小区连接方法、装置及相关设备
WO2024017023A1 (zh) 允许的nssai的获取方法、终端及网络侧设备
WO2022268012A1 (zh) 资源处理方法、装置、电子设备及存储介质
WO2024041470A1 (zh) ***信息消息接收方法、发送方法、终端及网络侧设备
WO2024037632A1 (zh) 通信方法、终端及网络侧设备
WO2023208048A1 (zh) 小区切换方法、装置、终端及网络侧设备
WO2024093712A1 (zh) 中继通信链路处理方法、中继通信链路配置方法、中继终端处理方法及相关设备
WO2024001954A1 (zh) 标识配置方法、装置、终端及存储介质
WO2023198071A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2024017244A1 (zh) 信息发送方法、信息接收方法、装置及相关设备
WO2023193676A1 (zh) 测量上报处理方法、装置、终端及网络侧设备
WO2024027638A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
WO2024022398A1 (zh) 托管网络的选网信息的获取方法、终端及网络侧设备
WO2023165481A1 (zh) 网络故障的处理方法、终端、接入网设备及核心网设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23778294

Country of ref document: EP

Kind code of ref document: A1