Method of authorization for network slicing
US-2022116816-A1 · Apr 14, 2022 · US
US12363601B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12363601-B2 |
| Application number | US-202217704362-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 25, 2022 |
| Priority date | Sep 26, 2019 |
| Publication date | Jul 15, 2025 |
| Grant date | Jul 15, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The disclosure provides communication methods and apparatuses. One example method includes receiving, by a first network device, a first message from a second network device, where the first message includes network slice configuration information. The network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1. In response to the received first message, the first network device sends a second message to the second network device.
Opening claim text (preview).
What is claimed is: 1. A communication method comprises: receiving, by a first network device, a first message from a second network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises: first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and sending, by the first network device, a second message to the second network device, wherein the second message is in response to the first message. 2. The method according to claim 1 , wherein: the first message is a handover request message; the first message is a UE context setup request message or a UE context modification request message; the first message is a bearer context setup request message or a bearer context modification request message; the first message is a secondary node addition request message or a secondary node modification request message; or the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message. 3. The method according to claim 1 , wherein: the second message is a handover request acknowledge message; the second message is a UE context setup response message or a UE context modification response message; the second message is a bearer context setup response message or a bearer context modification response message; the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or the second message is a PDU session resource setup response message or an initial context setup response message. 4. The method according to claim 1 , wherein the second message indicates that the first network device rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n. 5. The method according to claim 4 , further comprising: sending, by the first network device, rejection information to the second network device, wherein the rejection information indicates that a reason why the first network device rejects the configuration requirements of maximum data rates provided by m network slices is that the first network device does not support the maximum data rates provided by the m network slices for the terminal device. 6. A communication method comprises: sending, by a second network device, a first message to a first network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises: first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and receiving a second message from the first network device, wherein the second message is in response to the first message. 7. The method according to claim 6 , wherein: the first message is a handover request message; the first message is a UE context setup request message or a UE context modification request message; the first message is a bearer context setup request message or a bearer context modification request message; the first message is a secondary node addition request message or a secondary node modification request message; or the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message. 8. The method according to claim 6 , wherein: the second message is a handover request acknowledge message; the second message is a UE context setup response message or a UE context modification response message; the second message is a bearer context setup response message or a bearer context modification response message; the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or the second message is a PDU session resource setup response message or an initial context setup response message. 9. The method according to claim 6 , wherein the second message indicates that the first network device rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n. 10. The method according to claim 9 , further comprising: receiving, by the second network device, rejection information from the first network device, wherein the rejection information indicates that a reason why the first network device rejects the configuration requirements of maximum data rates provided by m network slices is that the first network device does not support the maximum data rates provided by m network slices for the terminal device. 11. A communication apparatus, comprising at least one processor; and one or more memories are coupled to the at least one processor and storing programming instructions for execution by the at least one processor to perform operations comprising: receiving a first message from a network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises: first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and sending a second message to the network device, wherein the second message is in response to the first message. 12. The communication a
Reselecting a communication resource in the serving access point · CPC title
Cell handover without a predetermined boundary, e.g. virtual cells · CPC title
of control information between different access points · CPC title
Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists · CPC title
Selecting a network or a communication service · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.