# US 10,455,641 B2 · Protocol data unit management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,641 B2 - Document ID: US10455641B2 - Status: Granted - Kind: B2 - Application number: 15/699,069 - Filed: 2017-09-08 - Published: 2018-07-05 - Granted: 2019-10-22 - Earliest claimed: 2017-01-05 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Aaron James Callard - Inventors: Aaron James Callard - Web page: https://patentgrep.com/patent/US10455641B2 ## CPC - H04W 88/182: {Network node acting on behalf of an other network entity, e.g. proxy} - H04L 49/9063: {Intermediate storage in different physical parts of a node or terminal} - H04W 76/20: Manipulation of established connections - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system and method is provided for configuring a plurality of PDU sessions. In an implementation, a core network function transmits a PDU bulk configuration request to at least one network node associated with the plurality of PDU sessions. The PDU bulk configuration request including a PDU session identifying component to enable the at least one network node to identify the plurality of PDU sessions, and includes a PDU session modifying component identifying required changes to one or more PDU session parameters to configure the plurality of PDU sessions. ## Claims ### Claim 1 A method for configuring a plurality of PDU sessions comprising a core network function: transmitting a PDU bulk configuration request to at least one network node associated with the plurality of PDU sessions, the at least one network node comprising at least one access node providing connectivity to the network; wherein the PDU bulk configuration request includes a PDU session identifying component to enable the at least one network node to identify the plurality of PDU sessions, and includes a PDU session modifying component identifying required changes to one or more PDU session parameters to configure the plurality of PDU sessions. ### Claim 2 (depends on 1) The method of claim 1, wherein the PDU session identifying component comprises use of at least one of: i) a filter; ii) a group label or identifier; and, iii) header logic. ### Claim 3 (depends on 1) The method of claim 1, wherein the PDU bulk configuration request is transmitted to a plurality of network nodes. ### Claim 4 (depends on 1) The method of claim 1, wherein the PDU session modifying component further defines a time window in which the PDU bulk configuration request should be applied. ### Claim 5 (depends on 1) The method of claim 1, wherein the PDU session modifying component further comprises a command component to be applied to the filtered PDU sessions. ### Claim 6 (depends on 5) The method of claim 5, wherein the command component is selected from the group consisting of: PDU Session Setup; PDU Session Modify; PDU Session Modification Indication; Initial Context Setup; and, UE Context Modification Indication. ### Claim 7 A network function operative to configure a plurality of PDU sessions comprising: a network interface for receiving data from and transmitting data to network functions connected to a network; a processor; and a non-transient memory for storing instructions that when executed by the processor cause the network function to be configured to: transmit a PDU bulk configuration request to at least one network node associated with the plurality of PDU sessions, the at least one network node comprising at least one access node providing connectivity to the network; wherein the PDU bulk configuration request includes a PDU session identifying component to enable the at least one network node to identify the plurality of PDU sessions, and includes a PDU session modifying component identifying required changes to one or more PDU session parameters to configure the plurality of PDU sessions. ### Claim 8 (depends on 7) The network function of claim 7, wherein the PDU session identifying component comprises use of at least one of: i) a filter; ii) a group label or identifier; and, iii) header logic. ### Claim 9 (depends on 7) The network function of claim 7, wherein the PDU bulk configuration request is transmitted to a plurality of network nodes. ### Claim 10 (depends on 7) The network function of claim 7, wherein the PDU session modifying component further defines a time window in which the PDU bulk configuration request should be applied. ### Claim 11 (depends on 7) The network function of claim 7, wherein the PDU session modifying component further comprises a command component to be applied to the filtered PDU sessions. ### Claim 12 (depends on 11) The network function of claim 11, wherein the command component is selected from the group consisting of: PDU Session Setup; PDU Session Modify; PDU Session Modification Indication; Initial Context Setup; and, UE Context Modification Indication. ### Claim 13 A method for configuring a plurality of PDU sessions comprising a network node: receiving, from a core network function, a PDU bulk configuration request, the PDU bulk configuration request including a PDU session identifying component, and including a PDU session modifying component; applying the PDU session identifying component to identify the plurality of PDU sessions to be configured; and, applying the PDU session modifying component to change one or more PDU session parameters of the identified plurality of PDU sessions to configure the plurality of PDU sessions; wherein the network node comprises an access node providing connectivity to the network. ### Claim 14 (depends on 13) The method of claim 13, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: applying a filter parameter to PDU sessions managed by the access node to identify the plurality of PDU sessions that match the filter parameter. ### Claim 15 (depends on 13) The method of claim 13, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: retrieving a group identifier from the PDU session identifying component and, identifying the plurality of PDU sessions that match the group identifier. ### Claim 16 (depends on 13) The method of claim 13, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: retrieving a header logic command from the PDU session identifying component; applying the header logic command to PDU sessions managed by the access node to identify the plurality of PDU sessions that conform with the header logic command. ### Claim 17 (depends on 13) The method of claim 13, wherein the PDU session modifying component further defines a time window in which the PDU bulk configuration request should be applied, and wherein the method further comprises the network node confirming to apply the PDU session modifying component during the defined time window. ### Claim 18 (depends on 11) The method of claim 11, further comprising: the network node receiving a new PDU bulk configuration request; and, replacing the PDU bulk configuration request with the new PDU bulk configuration request. ### Claim 19 (depends on 13) The method of claim 13, wherein the PDU session modifying component further comprises a command component to be applied to the filtered PDU sessions, and wherein the method further comprises the network node applying the command component to the filtered PDU sessions. ### Claim 20 (depends on 13) The method of claim 13, wherein the command component is selected from the group consisting of: PDU Session Setup; PDU Session Modify; PDU Session Modification Indication; Initial Context Setup; and, UE Context Modification Indication. ### Claim 21 A network node operative to configure a plurality of PDU sessions comprising: a network interface for receiving data from and transmitting data to network functions connected to a network; a processor; and a non-transient memory for storing instructions that when executed by the processor cause the network node to: receive, from a core network function, a PDU bulk configuration request, the PDU bulk configuration request including a PDU session identifying component, and including a PDU session modifying component; apply the PDU session identifying component to identify the plurality of PDU sessions to be configured; and, apply the PDU session modifying component to change one or more PDU session parameters of the identified plurality of PDU sessions to configure the plurality of PDU sessions; wherein the network node comprises an access node providing connectivity to the network. ### Claim 22 (depends on 21) The network node of claim 21, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: applying a filter parameter to PDU sessions managed by the access node to identify the plurality of PDU sessions that match the filter parameter. ### Claim 23 (depends on 21) The network node of claim 21, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: retrieving a group identifier from the PDU session identifying component and, identifying the plurality of PDU sessions that match the group identifier. ### Claim 24 (depends on 21) The network node of claim 21, wherein the applying the PDU session identifying component to identify the plurality of PDU sessions to be configured comprises: retrieving a header logic command from the PDU session identifying component; applying the header logic command to PDU sessions managed by the access node to identify the plurality of PDU sessions that conform with the header logic command. ### Claim 25 (depends on 21) The network node of claim 21, wherein the PDU session modifying component further defines a time window in which the PDU bulk configuration request should be applied, and wherein the method further comprises the network node confirming to apply the PDU session modifying component during the defined time window. ### Claim 26 (depends on 25) The network node of claim 25, further comprising: the network node receiving a new PDU bulk configuration request; and, replacing the PDU bulk configuration request with the new PDU bulk configuration request. ### Claim 27 (depends on 21) The network node of claim 21, wherein the PDU session modifying component further comprises a command component to be applied to the filtered PDU sessions, and wherein the method further comprises the network node applying the command component to the filtered PDU sessions. ### Claim 28 (depends on 21) The network node of claim 21, wherein the command component is selected from the group consisting of: PDU Session Setup; PDU Session Modify; PDU Session Modification Indication; Initial Context Setup; and, UE Context Modification Indication.