IP Library › Granted Patent US 12,598,487
Granted Patent B2
US 12,598,487 · App. 18/045,978 · Granted Apr 7, 2026

Slicing method and apparatus, storage medium, and processor

Inventors: Zhe Fu (Guangdong, CN); Haorui Yang (Guangdong, CN)
Assignee: InterDigital Patent Holdings, Inc.
H04W24/04H04W36/0079H04W48/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,598,487
App. No.
18/045,978
Granted
Apr 7, 2026
Kind
B2
Abstract

Disclosed are a slice processing method and apparatus, a storage medium, and a processor. The method includes: obtaining, by a first network side device, a first handover request sent from a source base station, and determining a handover behavior based on slice information.

Claims (47)

1 . A slice processing method, comprising:

obtaining, by a network side device, a handover request sent from a source base station associated with a packet-data-unit (PDU) session to be handed over to a target base station, wherein the PDU session is associated with a second slice and the target base station is associated with at least a first slice, and wherein the handover request carries slice information and a Quality of Service (QoS) attribute set for at least one QoS flow of the PDU session;

identifying, by the network side device, that the first slice is different from the second slice by determining that a first slice identifier of the first slice is different from a second slice identifier of the second slice;

selecting, by the network device and based on the slice information and the QoS attribute set, a handover behavior, wherein the selecting the handover behavior comprises selecting one of:

remapping the second slice onto a different slice that is in a same slice-group as the first slice supported by the target base station,

falling-back to a default slice supported by the target base station, and

determining that the requested handover is not supported; and

performing the selected handover behavior.

2 . The method according to claim 1 , further comprising:

feeding-back a handover request acknowledgment (ACK) message to the source base station; or

feeding-back a handover command message to the source base station.

3 . The method according to claim 2 , wherein the handover request ACK message or the handover command message is further used to indicate whether the remapping the second slice or the falling-back to the default slice is supported or not supported.

4 . The method according to claim 1 , wherein the selecting the handover behavior is based on the slice information and based on one or more handover behavior rules configured by an operation-administration-maintenance (OAM) entity and stored at the network side device.

5 . The method according to claim 1 , wherein the handover request is determined to not be supported based on a maximum number of slices supported by the target base station.

6 . The method according to claim 1 , further comprising:

determining whether the PDU session is marked for service continuity or priority; and

prioritizing the PDU session for the selecting the handover behavior based on the determining.

7 . The method according to claim 1 , wherein the falling-back to the default slice is selected on a condition that the second slice cannot be remapped onto a different slice that is in the same slice-group as the first slice.

8 . The method according to claim 1 , further comprising transmitting a handover response message that indicates the selected handover behavior.

9 . The method according to claim 8 , wherein the selecting the handover behavior is further based on whether a user equipment reaches a configured maximum slice number.

10 . The method according to claim 1 , wherein the selecting is before the target base station finalizes admission of handover.

11 . A network side device comprising:

one or more processors, and memory storing operational instructions that, when executed by at least one of the one or more processors, cause the network side device to:

obtain a handover request sent from a source base station associated with a packet-data-unit (PDU) session to be handed over to a target base station, wherein the PDU session is associated with a second slice and the target base station is associated with at least a first slice, and wherein the handover request carries slice information and a Quality of Service (QoS) attribute set for at least one QoS flow of the PDU session;

identify that the first slice is different from the second slice by determining that a first slice identifier of the first slice is different from a second slice identifier of the second slice;

select, based on the slice information and the QoS attribute set, a handover behavior, wherein the selection of the handover behavior comprises selection of one of:

remapping the second slice onto a different slice that is in a same slice-group as the first slice supported by the target base station,

falling-back to a default slice supported by the target base station, and

determining that the requested handover is not supported; and

perform the selected handover behavior.

12 . The network side device according to claim 11 , wherein the operational instructions, when executed by at least one of the one or more processors, further causes the network side device to:

feed-back a handover request acknowledgment (ACK) message to the source base station; or

feed-back a handover command message to the source base station.

13 . The network side device according to claim 12 , wherein the handover request ACK message or the handover command message is further used to indicate whether the remapping the second slice or the falling-back to the default slice is supported or not supported.

14 . The network side device according to claim 11 , wherein the handover behavior is selected based on the slice information and based on one or more handover behavior rules configured by an operation-administration-maintenance (OAM) entity and stored at the network side device.

15 . The network side device according to claim 11 , wherein

the handover request is determined to not be supported based on a maximum number of slices supported by the target base station.

16 . The network side device according to claim 11 , wherein the operational instructions, when executed by at least one of the one or more processors, further causes the network side device to:

determine whether the PDU session is marked for service continuity or priority; and

prioritize the PDU session for the selection of the handover behavior based on the determination.

17 . The network side device according to claim 11 , wherein the operational instructions, when executed by at least one of the one or more processors, further causes the network side device to:

select the falling-back to the default slice on a condition that the second slice cannot be remapped onto a different slice that is in the same slice-group as the first slice.

18 . The network side device according to claim 11 , wherein the operational instructions, when executed by at least one of the one or more processors, further causes the network side device to:

transmit a handover response message that indicates the selected handover behavior.

19 . The network side device according to claim 18 , wherein the selected handover behavior is further based on whether a user equipment reaches a configured maximum slice number.

20 . The network side device according to claim 11 , wherein

the handover behavior is selected before the target base station finalizes admission of handover.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 17, 2025
From: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.
To: INTERDIGITAL HOLDINGS, INC.
Reel/Frame 069911/0769 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 17, 2025
From: INTERDIGITAL HOLDINGS, INC.
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 069911/0994 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 13, 2022
From: FU, ZHE; YANG, HAORUI
To: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.
Reel/Frame 061410/0382 →
Continuity (2)
Continuation PCTCN2020084503 · Apr 13, 2020
Related Publication 20230056120A1 · Feb 23, 2023
References Cited (29)
US 10506489B2 · Vrzic · 2019 [cited by examiner]
US 10932253B2 · Centonza · 2021 [cited by examiner]
US 11463947B2 · Jin · 2022 [cited by examiner]
US 20180324663A1 · Park et al. · 2018 [cited by applicant]
US 20190158360A1 · Xu et al. · 2019 [cited by applicant]
US 20190306761A1 · Jin · 2019 [cited by examiner]
US 20190357103A1 · Jin · 2019 [cited by examiner]
US 20190394683A1 · Sillanpaa et al. · 2019 [cited by applicant]
US 20200022033A1 · Wei · 2020 [cited by examiner]
US 20200022061A1 · Jin · 2020 [cited by examiner]
US 20200169303A1 · Park · 2020 [cited by examiner]
US 20200305054A1 · Zee · 2020 [cited by examiner]
US 20200344679A1 · Jin · 2020 [cited by examiner]
US 20210274407A1 · Wu · 2021 [cited by examiner]
US 20230014464A1 · Fu · 2023 [cited by examiner]
US 20230054288A1 · Gao · 2023 [cited by examiner]
US 20230086410A1 · Sun · 2023 [cited by examiner]
CN 108632927 · 2018 [cited by applicant]
WO 2017118489 · 2017 [cited by applicant]
WO WO2018135992A1 · 2018 [cited by examiner]
WO 2018208371 · 2018 [cited by applicant]
Nokia et al., “Connected mode mobility with slicing, ” 3GPP TSG-RAN WG3#95bis, R3-171116, Apr. 2017. [cited by applicant]
CATT, “Discussion on Slice-aware mobility,” 3GPP TSG-RAN WG3 #95bis, R3-171012, Apr. 2017. [cited by applicant]
SA WG2, “Response LS on slice re-mapping during connected mode mobility,” 3GPP TSG-SA WG2 Meeting #121, S2-174019, May 2017. [cited by applicant]
CMCC, “Email discussion for R17 proposals on slicing,” 3GPP TSG RAN Meeting #85, RP-191778, Sep. 2019. [cited by applicant]
WIPO, International Search Report and Written Opinion for PCT/CN2020/084503, Dec. 30, 2020. [cited by applicant]
EPO, Extended European Search Report for EP Application No. 20930939.2, May 19, 2023. [cited by applicant]
ZTE, “NW Slice Availability Handling Approaches during Mobility,” 3GPP TSG RAN WG3 Meeting #95bis, R3-171029, Apr. 2017. [cited by applicant]
Huawei, “Further Discussion on Slice Re-mapping,” 3GPP TSG-RAN WG3 95bis, R3-171251, Apr. 2017. [cited by applicant]