# US 11,903,073 B2 · Dynamic adjustment method and apparatus for PDU session > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,903,073 B2 - Document ID: US11903073B2 - Status: Granted - Kind: B2 - Application number: 17/289,085 - Filed: 2019-11-01 - Published: 2022-01-06 - Granted: 2024-02-13 - Earliest claimed: 2018-11-01 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Xiaojuan Li; Guowei Ouyang - Web page: https://patentgrep.com/patent/US11903073B2 ## CPC - H04W 76/22: Manipulation of transport tunnels - H04W 24/08: Testing, {supervising or monitoring} using real traffic - H04W 24/10: Scheduling measurement reports {; Arrangements for measurement reports} - H04W 48/16: Discovering, processing access restriction or access information - H04W 76/11: Allocation or use of connection identifiers - H04W 76/18: Management of setup rejection or failure - H04W 76/30: Connection release - H04W 76/32: Release of transport tunnels - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method for a protocol data unit (PDU) session includes a step of a first core network device obtaining a first message from a first server. The first core network device generates a first parameter based on the first message. A terminal device obtains a measurement result based on the first parameter and sends the measurement result to the first core network device. The first core network device obtains a second parameter based on the measurement result, and the second core network device configures the second parameter to dynamically adjust the PDU session based on location or time information with reference to the second parameter. ## Claims ### Claim 1 A method for adjusting a protocol data unit (PDU) session comprising: obtaining, by a second core network device, a first message from a first core network device, wherein the first message comprises a first parameter and a network resource status of a first application; sending the first message to a terminal device to instruct the terminal device to obtain a measurement result of the first parameter; obtaining the measurement result from the terminal device; sending the measurement result to the first core network device; obtaining a second message to instruct the second core network device to configure, based on the measurement result, a second parameter to adjust the PDU session; obtaining a fourth message from a third core network device, wherein the fourth message comprises at least one of a first application identifier or a second time period; and retaining the PDU session when the fourth message includes the first application identifier. ### Claim 2 (depends on 1) The method of claim 1, wherein when the first message indicates a network resource status of a first slice, the method further comprises: obtaining a third message that comprises at least one of first slice information or a first time period; and performing, in response to the third message, a first operation comprising: retaining the PDU session when the PDU session belongs to the first slice; and releasing the PDU when the PDU session does not belong to the first slice. ### Claim 3 (depends on 2) The method of claim 2, further comprising identifying that the PDU session exists, and wherein the first operation comprises retaining the PDU session when the PDU session belongs to the first slice. ### Claim 4 (depends on 2) The method of claim 2, further comprising: obtaining a PDU session establishment request from the terminal device; and sending, in response to the PDU session establishment request, a PDU session reception request message to the terminal device when the PDU session belongs to the first slice. ### Claim 5 (depends on 4) The method of claim 4, further comprising sending, when the PDU session does not belong to the first slice, in a PDU session rejection request message to the terminal device, wherein the PDU session rejection request message comprises a first cause value and first time information, wherein the first cause value indicates a cause for rejecting the PDU session, and wherein the first time information indicates a next time when the PDU session can be established. ### Claim 6 (depends on 2) The method of claim 2, further comprising identifying that the PDU session exists, and wherein the first operation comprises releasing the PDU session when the PDU session does not belong to the first slice. ### Claim 7 (depends on 1) The method of claim 1, wherein the second parameter comprises one or more of an air interface measurement or a quality of service (QoS)-related parameter. ### Claim 8 (depends on 1) The method of claim 1, further comprising releasing the PDU session when the fourth message does not carry the first application identifier. ### Claim 9 (depends on 1) The method of claim 1, wherein the first parameter comprises one or more of an air interface measurement or a quality of service (QoS)-related parameter. ### Claim 10 (depends on 1) The method of claim 1, wherein the second parameter comprises a 5G QoS indicator (5QI). ### Claim 11 A method for a protocol data unit (PDU) session comprising: obtaining, by a terminal device, from a core network device, a first message comprising a first parameter, wherein the first message instructs the terminal device to obtain a measurement result of the first parameter, wherein the measurement result comprises statistical information related to a PDU session, and wherein the first message further indicates a network resource status of a first application; obtaining, from the core network device, a second message comprising a second time period; and sending the measurement result to the core network device. ### Claim 12 (depends on 11) The method of claim 11, wherein the second message further comprises first application information comprising a first application identifier. ### Claim 13 (depends on 12) The method of claim 12, wherein the first application is configured to transmit data, wherein the method further comprises performing a first operation when the PDU session exists, and wherein the first operation comprises sending, to the core network device, a PDU session modification request message comprising the first application identifier when the PDU session matches the first application identifier. ### Claim 14 (depends on 12) The method of claim 12, wherein the first application is configured to transmit data, wherein the method further comprises performing a second operation when the PDU session does not exist, wherein the second operation comprises sending a PDU session establishment request message comprising a first application identifier to the core network device. ### Claim 15 (depends on 11) The method of claim 11, wherein the first parameter comprises one or more of an air interface measurement or a quality of service (QoS)-related parameter. ### Claim 16 A terminal device for a protocol data unit (PDU) session-comprising: a receiver configured to obtain, from a core network device, a first message comprising: a network resource status of a first application, wherein the first application is configured to transmit data; and a first parameter, wherein the first message instructs the terminal device to collect statistics on a measurement result of the first parameter, wherein the measurement result comprises statistical information related to the PDU session, wherein the receiver is further configured to obtain a second message from the core network device, and wherein the second message comprises first application information; a transmitter coupled to the receiver and configured to send the measurement result to the core network device; and a processor configured to perform a first operation when the PDU session does not exist, and wherein the first operation is configured to cause the transmitter to send, to the core network device, a PDU session establishment request message comprising a first application identifier. ### Claim 17 (depends on 16) The terminal device of claim 16, wherein the terminal device further comprises a processor coupled to the receiver and the transmitter and configured to perform a first operation comprising: retaining the PDU session when the PDU session belongs to a first slice; and releasing the PDU when the PDU session does not belong to a first slice. ### Claim 18 (depends on 16) The terminal device of claim 16, wherein the first application is configured to transmit data, wherein the processor is further configured to perform the first operation when the PDU session exists, and wherein the first operation is configured to cause the transmitter to send, to the core network device, a PDU session modification request message comprising the first application identifier when the PDU session matches the first application identifier. ### Claim 19 (depends on 16) The terminal device of claim 16, wherein the first message further indicates a network resource status of a first application, wherein the receiver is further configured to obtain a second message from the core network device, wherein the second message comprises a time period, and wherein the terminal device further comprises a processor coupled to the receiver and the transmitter and configured to perform a first operation comprising: retaining the PDU session when the PDU session belongs to a first slice; and releasing the PDU when the PDU session does not belong to a first slice. ### Claim 20 (depends on 16) The method of claim 16, wherein the first parameter comprises one or more of an air interface measurement or a quality of service (QoS)-related parameter.