CN112449389B - Switching method, source base station, target base station and terminal - Google Patents

Switching method, source base station, target base station and terminal Download PDF

Info

Publication number
CN112449389B
CN112449389B CN201910836413.6A CN201910836413A CN112449389B CN 112449389 B CN112449389 B CN 112449389B CN 201910836413 A CN201910836413 A CN 201910836413A CN 112449389 B CN112449389 B CN 112449389B
Authority
CN
China
Prior art keywords
slice
base station
terminal
information
reconfiguration message
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201910836413.6A
Other languages
Chinese (zh)
Other versions
CN112449389A (en
Inventor
陈宁宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
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 China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN201910836413.6A priority Critical patent/CN112449389B/en
Publication of CN112449389A publication Critical patent/CN112449389A/en
Application granted granted Critical
Publication of CN112449389B publication Critical patent/CN112449389B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/30Reselection being triggered by specific parameters by measured or perceived connection quality data

Abstract

The invention discloses a switching method, a source base station, a target base station and a terminal, which relate to the technical field of communication and are used for solving the problem that in the related art, the target base station directly refuses a slice when the slice is not supported by the current running of the terminal, so that the service of the terminal is interrupted. The method comprises the following steps: and sending a first reconfiguration message to the terminal, wherein the first reconfiguration message is acquired from the target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information. The embodiment of the invention can enable the terminal to be switched to the target base station by degrading or backing the slice, so that the terminal can continuously carry out related services without service interruption even if the target base station does not support the slice currently operated by the terminal or the load of the slice, and further the user service experience can be ensured.

Description

Switching method, source base station, target base station and terminal
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a handover method, a source base station, a target base station, and a terminal.
Background
In the process of communication between the terminal and the base station, the measured signal intensity of the current service cell is reported to the base station, and the base station can determine whether to switch to other base stations according to the information reported by the terminal. In the related art, when the source base station decides that the service currently operated by the terminal needs to be switched to the target base station, the source base station may send a switching request message to the target base station, and the target base station may determine whether to support the slice currently operated by the terminal, if so, a switching command including a reconfiguration message is returned to the source base station, but in the case of not supporting, the target base station directly refuses the slice, thereby easily causing interruption of the service of the terminal and affecting the user service experience.
Disclosure of Invention
The embodiment of the invention provides a switching method, a source base station, a target base station and a terminal, which are used for solving the problem that in the related art, the target base station directly refuses a slice to cause terminal service interruption under the condition that the slice is not supported by the current running of the terminal.
In a first aspect, an embodiment of the present invention provides a handover method, which is applicable to a source base station, including:
and sending a first reconfiguration message to the terminal, wherein the first reconfiguration message is acquired from the target base station and comprises slice degradation information or slice rollback information.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, before the first reconfiguration message is sent to the terminal, the method further includes:
transmitting a switching request message to the target base station, wherein the switching request message comprises slice information of the current operation of the terminal;
and receiving a first reconfiguration message sent by the target base station.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
Minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
the method further comprises the steps of:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the terminal, wherein the second reconfiguration message comprises slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
A partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, the number of the target base stations is at least two;
before the first reconfiguration message is sent to the terminal, the method further includes:
determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the sending the first reconfiguration message to the terminal includes:
and sending the first reconfiguration message sent by the target switching base station to a terminal.
In a second aspect, an embodiment of the present invention further provides another handover method, which is applicable to a target base station, including:
Receiving a switching request message sent by a source base station, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station;
generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
and sending the first reconfiguration message to the source base station.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
The generating a first reconfiguration message according to the handover request message includes:
judging whether the minimum QoS requirement of a slice currently operated by the terminal can be met or not according to the minimum QoS requirement information;
if yes, a first reconfiguration message including the degraded slice information or the fallback default slice information is generated.
Optionally, the generating a first reconfiguration message according to the handover request message includes:
if the target base station does not support the current running slice of the terminal or the load of the slice and can meet the requirement of the current running slice of the terminal or the load of the slice through degradation or rollback, generating a first reconfiguration message according to the switching request message;
after receiving the handover request message sent by the source base station, the method further includes:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the source base station, wherein the second reconfiguration message comprises slice rejection information.
In a third aspect, an embodiment of the present invention further provides another handover method, which is applicable to a terminal, including:
receiving a first reconfiguration message sent by a source base station, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information;
and switching to the target base station according to the first reconfiguration message.
In a fourth aspect, an embodiment of the present invention further provides a source base station, including:
and the first sending module is used for sending a first reconfiguration message to the terminal, wherein the first reconfiguration message is acquired from the target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the source base station further includes:
the second sending module is used for sending a switching request message to the target base station, wherein the switching request message comprises slice information of the current operation of the terminal;
and the first receiving module is used for receiving the first reconfiguration message sent by the target base station.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
the source base station further includes:
and the third sending module is used for sending a second reconfiguration message to the terminal if the target base station does not support the current running slice of the terminal or the loading of the slice and the requirements of the current running slice of the terminal or the loading of the slice cannot be met through degradation and rollback, wherein the second reconfiguration message comprises slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, the number of the target base stations is at least two;
the source base station further includes:
the determining module is used for determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the first sending module is used for sending a first reconfiguration message sent by the target switching base station to the terminal.
In a fifth aspect, an embodiment of the present invention further provides a target base station, including:
the switching module is used for receiving a switching request message sent by a source base station, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station;
the generation module is used for generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
and the first sending module is used for sending the first reconfiguration message to the source base station.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
the generation module comprises:
a first judging unit, configured to judge whether the minimum QoS requirement of the slice currently operated by the terminal can be met according to the minimum QoS requirement information;
and the first generation unit is used for generating a first reconfiguration message comprising the degraded slice information or the fallback default slice information if yes.
Optionally, the generating module is configured to generate a first reconfiguration message according to the handover request message if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, and the requirement of the slice currently operated by the terminal or the bearer of the slice can be met by degradation or rollback;
the source base station further includes:
and the second sending module is used for sending a second reconfiguration message to the source base station if the target base station does not support the current running slice of the terminal or the loading of the slice and the requirements of the current running slice of the terminal or the loading of the slice cannot be met through degradation and rollback, wherein the second reconfiguration message comprises slice rejection information.
In a sixth aspect, an embodiment of the present invention further provides a terminal, including:
the first receiving module is used for receiving a first reconfiguration message sent by a source base station, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information;
and the switching module is used for switching to the target base station according to the first reconfiguration message.
In a seventh aspect, an embodiment of the present invention further provides a source base station, including: a transceiver and a processor;
the transceiver is configured to send a first reconfiguration message to a terminal, where the first reconfiguration message is acquired by the source base station from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the transceiver is further configured to send a handover request message to the target base station; and receiving a first reconfiguration message sent by the target base station.
Optionally, the handover request message includes at least one of:
Minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
the transceiver is further configured to send a second reconfiguration message to the terminal if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, and neither degradation nor fallback can satisfy a requirement of the slice currently operated by the terminal or the bearer of the slice, where the second reconfiguration message includes slice rejection information.
Optionally, the slice rejection information includes at least one of:
A rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, the number of the target base stations is at least two;
the processor is used for determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the transceiver is further configured to send a first reconfiguration message sent by the target handover base station to a terminal.
In an eighth aspect, an embodiment of the present invention further provides a target base station, including: a transceiver and a processor;
The transceiver is configured to receive a handover request message sent by a source base station, where the handover request message includes slice information that a terminal connected to the source base station currently operates;
the processor is configured to generate a first reconfiguration message according to the handover request message, where the first reconfiguration message includes slice degradation information or slice fallback information;
the transceiver is further configured to send the first reconfiguration message to the source base station.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
the processor is further configured to determine, according to the minimum QoS requirement information, whether a minimum QoS requirement of a slice currently operated by the terminal can be met; if yes, a first reconfiguration message including the slice degradation information or the slice fallback information is generated.
Optionally, the processor is further configured to generate a first reconfiguration message according to the handover request message if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, and the requirement of the slice currently operated by the terminal can be met through degradation or rollback;
the transceiver is further configured to send a second reconfiguration message to the source base station if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, and neither degradation nor fallback can satisfy a requirement of the slice currently operated by the terminal or the bearer of the slice, where the second reconfiguration message includes slice rejection information.
In a ninth aspect, an embodiment of the present invention further provides a terminal, including: a transceiver and a processor;
the transceiver is configured to receive a first reconfiguration message sent by a source base station, where the first reconfiguration message is acquired by the source base station from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information;
and the processor is used for switching to the target base station according to the first reconfiguration message.
In a tenth aspect, an embodiment of the present invention further provides a source base station, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the handover method as described in the first aspect above when the computer program is executed.
In an eleventh aspect, an embodiment of the present invention further provides a target base station, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the handover method as described in the second aspect above when the computer program is executed.
In a twelfth aspect, an embodiment of the present invention further provides a terminal, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the handover method as described in the third aspect above when the computer program is executed.
In a thirteenth aspect, an embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the handover method according to the first aspect described above; or the computer program when executed by a processor performs the steps in a handover method as in the second aspect above; or which when executed by a processor implements the steps in a handover method as described in the third aspect above.
In the embodiment of the invention, a first reconfiguration message is sent to a terminal, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information. In this way, the terminal can be switched to the target base station by degrading or backing up the slice, so that the terminal can continuously perform related services even if the target base station does not support the slice currently operated by the terminal or the load of the slice, service interruption is not easy to occur, and user service experience can be further ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.
FIG. 1 is one of the flowcharts of a handover method according to an embodiment of the present invention;
FIG. 2 is a second flowchart of a handover method according to an embodiment of the present invention;
FIG. 3 is a third flowchart of a handover method according to an embodiment of the present invention;
fig. 4 is one of the block diagrams of the source base station provided in the embodiment of the present invention;
fig. 5 is a second block diagram of a source base station according to an embodiment of the present invention;
fig. 6 is a third block diagram of a source base station according to the embodiment of the present invention;
fig. 7 is a fourth block diagram of a source base station according to an embodiment of the present invention;
fig. 8 is one of the block diagrams of the target base station provided in the embodiment of the present invention;
fig. 9 is a block diagram of a generating module of a target base station according to an embodiment of the present invention;
FIG. 10 is a second block diagram of a target base station according to an embodiment of the present invention;
fig. 11 is one of the block diagrams of the terminal provided in the embodiment of the present invention;
FIG. 12 is a second block diagram of a terminal according to an embodiment of the present invention;
fig. 13 is a fifth block diagram of a source base station according to an embodiment of the present invention;
fig. 14 is a third block diagram of a target base station according to the embodiment of the present invention;
fig. 15 is a third block diagram of a terminal according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, fig. 1 is a flowchart of a handover method provided by an embodiment of the present invention, for a source base station, as shown in fig. 1, the method includes the following steps:
step 101, a first reconfiguration message is sent to a terminal, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information.
In the embodiment of the present invention, the source base station may be a base station to which the terminal is currently connected and establishes communication connection, and the target base station is a target handover base station. The terminal can measure the signal intensity of the current service cell in the process of communicating with the source base station and report the signal intensity to the source base station, and the source base station can determine whether to switch to other base stations according to the information reported by the terminal, for example, when determining that the signal quality of the current service cell of the terminal is poor, the terminal can send switching request information to other base stations so as to switch the terminal to the base station with better signal quality to obtain better service quality.
In practice, the source base station may send a handover request message to the target base station, where the handover request message may include slice information that the terminal currently operates, that is, before sending the first reconfiguration message to the terminal, the method may further include: transmitting a switching request message to a target base station; receiving a first reconfiguration message sent by the target base station; specifically, slice information currently operated by the terminal is related to a service currently operated by the terminal, and different services correspond to different slices, for example, the terminal allows different slices when performing video service and session service respectively.
Wherein the handover request message may include at least one of:
minimum quality of service (Quality of Service, qoS) requirement information for a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
In order for the target base station to obtain the QoS requirement information of the current running slice of the terminal, so as to determine whether the QoS requirement of the current running slice of the terminal can be met, the handover request message may carry QoS requirement information related to the current running slice of the terminal, for example, one or more of minimum QoS requirement information of the current running slice of the terminal, minimum QoS requirement information of QoS flow in the current running slice of the terminal, recommended QoS requirement information of QoS flow in the current running slice of the terminal, and the like.
The minimum QoS requirement information of the slice currently operated by the terminal is used to indicate the minimum QoS requirement of the slice currently operated by the terminal, such as time delay, packet error rate, priority, etc.
The minimum QoS requirement information of the QoS flow in the slice currently operated by the terminal is used to indicate the minimum QoS requirement of a certain QoS flow in the slice currently operated by the terminal, that is, the slice currently operated by the terminal may include a plurality of QoS flows, each QoS flow may have a different QoS requirement, and the terminal may carry the minimum QoS requirement of a certain QoS flow in the handover request message.
The target base station may determine whether the minimum QoS requirement of the slice can be met based on the minimum QoS requirement information of the slice or the minimum QoS requirement information of a certain QoS flow in the slice, if so, may perform degradation or rollback on the slice or a part of QoS flows in the slice to support a slice switching request of the terminal, that is, the target base station may generate a switching command including a first reconfiguration message, where the first reconfiguration message includes slice degradation information or slice rollback information, and is used to instruct the terminal to switch to the target base station according to the slice degradation information or the slice rollback information; if not, the handover request of the slice may be rejected, i.e. the target base station may generate a reconfiguration message including slice rejection information for indicating rejection of the handover request of the terminal.
The recommended QoS requirement information of the slice currently operated by the terminal may be to provide better QoS guarantee for the slice currently operated by the terminal, and compared with the source base station, the recommended QoS requirement of the slice is recommended to the target base station, that is, the source base station currently fails to meet the most suitable QoS requirement of the slice currently operated by the terminal, and degradation processing is performed for the slice, so when a handover request is sent to the target base station, the recommended QoS requirement information may be carried in the handover request message, so that the target base station determines whether the recommended QoS requirement of the slice can be met.
Similarly, since the slice in which the terminal is currently operating may include a plurality of QoS flows, and each QoS flow has a different QoS requirement, the terminal may carry the recommended QoS requirement information of a certain QoS flow in the handover request message, so that the target base station determines whether the recommended QoS requirement of the QoS flow in the slice can be met.
The target base station may determine whether the recommended QoS requirement of the slice can be met based on the recommended QoS requirement information of the slice or the recommended QoS requirement information of a certain QoS flow in the slice, if so, upgrade may be performed on the slice or a part of QoS flows in the slice to switch the slice of the terminal to the target base station, and provide higher service quality for the slice, that is, the target base station may generate a switch command including a third reconfiguration message, where the third reconfiguration message includes upgraded slice information, and is used to instruct the terminal to switch to the target base station according to the upgraded slice information; if not, a handoff of the slice may be accommodated and the slice may remain provided with the same level of quality of service.
In this way, by carrying QoS requirement information of each different slice currently operated by the terminal in the handover request message, the target base station can determine, according to the information, which mode to accept the handover request of the terminal, and ensure that a suitable quality of service is provided for the slice of the terminal.
Wherein the QoS requirement information may include at least one of latency, packet error rate, and priority. In this way, the requirements of the current running slice of the terminal on the service quality of the base station can be reflected through time delay, data packet error rate, priority and the like, so that the target base station can clearly judge whether the current running service of the terminal can be supported according to the QoS requirement information.
In the embodiment of the present invention, the first reconfiguration message may include slice degradation information or slice fallback information, and specifically, may be when the target base station determines, based on slice information currently operated by the terminal carried in the slice request message, that the slice currently operated by the terminal or the bearer of the slice cannot be supported, generate a first reconfiguration message including the slice degradation information or the slice fallback information, so as to inform the terminal to switch to the target base station by reducing the slice bearer level or the manner of fallback default slices, where the first reconfiguration message may be carried in a switching command and sent to the source base station.
Specifically, in one case, the target base station may not guarantee that a certain bearer of a slice currently operated by the terminal continues to operate on an original level due to resource congestion and other reasons in a handover process, and the level of the bearer needs to be degraded, so that a first reconfiguration message including slice degradation information may be generated. For example, a slice currently operated by the terminal includes two bearers, wherein a Qos identifier level (QoS Class Identifier, QCI) of one bearer is 5, and a Qos identifier level of the other bearer is 7, and if the target base station cannot guarantee that the bearer with the level 5 of the slice continues to operate due to resource congestion, the bearer needs to be degraded, for example, the Qos identifier level is adjusted to be 6, the target base station may carry slice degradation information in a handover command sent to the source base station, and instruct the terminal to degrade the Qos identifier level of the certain bearer of the slice.
Wherein the slice degradation information may include at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
To explicitly indicate that the terminal needs slice degradation information, one or more of a slice identification of degradation, a bearer identification of degradation, and degradation information may be included in the slice degradation information, where the slice identification of degradation is used to indicate which slice needs degradation, such as a slice ID, and the bearer identification of degradation is used to indicate which bearer of a slice needs degradation, such as a data radio bearer (Data Radio Bearer, DRB) ID, and the degradation information is used to indicate a level of degradation, such as to which level of QCI.
In another case, the target base station does not support a certain slice currently operated by the terminal, but when the service corresponding to the slice can continue to operate on a default slice, the target base station can rollback the slice to the default slice through network configuration, that is, the QCI level of the default slice can meet the basic requirement of the slice operation. Thus, the target base station may in this case generate a first reconfiguration message comprising slice fallback information and may configure the target base station with default slices through the core network.
Wherein the slice fallback information comprises at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
In order to clearly indicate the slice information that the terminal needs to fall back, the slice fall-back information may include a default slice bearer establishment message and/or a slice fall-back message, where the default slice bearer establishment message is used to indicate the terminal to establish a bearer of a default slice, and the default slice bearer establishment message may include configuration information of the bearer, such as a configured QCI class, and when the terminal accesses a target base station, the bearer is established according to the configuration information of the bearer.
The slice fallback message is used for indicating that the terminal fallback a slice currently operated to a default slice to continue to operate the original service, and may carry at least one of a slice identifier, a bearer identifier and a QCI level (e.g. qci=9) of a fallback bearer, where the slice identifier is used for indicating which slice operated by the terminal needs to be fallback to the default slice, and the bearer identifier is used for indicating which bearer in the slice needs to be fallback to the default bearer.
It should be noted that, if the target base station supports the slice currently operated by the terminal or the bearer of the slice, the target base station may generate a third reconfiguration message including admitted slice information or upgraded slice information, and send the third reconfiguration message to the source base station.
In this manner, when the target base station supports a slice currently operated by the terminal or a bearer of the slice, the target base station may generate a reconfiguration message including admitted slice information or updated slice information to indicate that the terminal can directly switch to the target base station, or may further update a certain slice therein to obtain better quality of service.
Specifically, in one case, if the source base station and the target base station both support a slice currently performed by the terminal, the target base station may carry information of the slice in a handover command as an admitted slice, that is, the third reconfiguration message may carry admitted slice information.
Wherein the received slice information may include at least one of:
a received slice identifier;
and the received bearing identification.
The received slice identifier is used for indicating which slice the terminal currently operates is received by the target base station, and the received bearer identifier is used for indicating which bearer in a certain slice the terminal currently operates is received by the target base station. In this way, the terminal can directly switch a slice or bearer currently performed to the target base station for operation according to the received slice information.
In another case, if the target base station receives the recommended QoS requirement information of the slice currently operated by the terminal or the recommended QoS requirement information of the QoS flow in the slice, which is included in the handover request message sent by the source base station, and the target base station can meet the recommended QoS requirement information, a third reconfiguration message including updated slice information may be generated, so as to update a slice currently operated by the terminal to the recommended QoS requirement, so that the terminal obtains better service experience.
Wherein the updated slice information may include at least one of:
an upgraded slice identifier;
an upgraded bearing identifier;
slice upgrade indication;
and the updated QoS parameters.
In order to explicitly indicate slice information that the terminal can be upgraded, the upgraded slice information may include one or more of an upgraded slice identifier, an upgraded bearer identifier, a slice upgrade instruction, and an upgraded QoS parameter, where the upgraded slice identifier is used to indicate a slice to be upgraded in a slice currently operated by the terminal, the upgraded bearer identifier is used to indicate a bearer to be upgraded, the slice upgrade instruction is used to indicate that a slice currently operated by the terminal is QoS upgraded at the target base station, and the upgraded QoS parameter is used to indicate QoS parameters such as delay, packet error rate, priority, and the like of the slice currently operated by the terminal after upgrade.
After receiving the first reconfiguration message, the source base station may forward the first reconfiguration message to the terminal, and when the first reconfiguration message is carried in a slicing command and sent to the source base station, the source base station may extract the first reconfiguration message from the handover command and then send the first reconfiguration message to the terminal. In this way, the terminal may switch to the target base station according to the first reconfiguration message, for example, switch to the target base station according to the slice degradation information, reduce the slice or the bearer to be degraded to the indicated level in the switching process, or switch to the target base station according to the slice fallback information, and fallback the slice to be fallback to the default slice or fallback the bearer of the slice to the default bearer in the switching process.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
the method further comprises the steps of:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the terminal, wherein the second reconfiguration message comprises slice rejection information.
In this manner, the method may include receiving a first reconfiguration message including slice degradation information or slice fallback information sent by the target base station, and sending the first reconfiguration message to the terminal, where the target base station does not support a slice currently operated by the terminal or a bearer of the slice, but can meet a requirement of the slice currently operated by the terminal or the bearer of the slice through degradation or fallback.
And when the target base station does not support the current running slice of the terminal and cannot meet the requirement of the current running slice of the terminal through degradation and rollback, the target base station can reject the switching request of the slice, or when part of the bearers in a certain current running slice of the terminal cannot be served by the target base station, the target base station can reject one or more bearers in the slice. That is, the target base station may in this case generate a second reconfiguration message including slice rejection information and send it to the source base station, which in turn forwards it to the terminal to indicate that the terminal does not currently support handover of certain slices by the target base station.
Wherein the slice rejection information may include at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
To explicitly indicate which slices of the terminal cannot be operated at the target base station, the slice rejection information may include at least one of a rejected slice identifier, a partially rejected slice identifier, and a rejected bearer identifier, where the rejected slice identifier is used to indicate rejection of all bearers of a slice currently operated by the terminal, the partially rejected slice identifier is used to indicate rejection of partial bearers of a slice currently operated by the terminal, and the rejected bearer identifier is used to indicate rejection of which bearers of the slice currently operated by the terminal. For example, if the rejected slice ID is 1, it indicates that all the bearers of slice 1 are rejected, the terminal releases all the bearers in slice 1 after receiving the slice rejection information, and if the partially rejected slice ID is 2 and the rejected bearer ID is 5, it indicates that the bearer 5 of slice 2 is rejected, and the terminal releases the bearer 5 in slice 2 but does not release other bearers after receiving the slice rejection information.
Optionally, the number of the target base stations is at least two;
prior to the step 101, the method further includes:
determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the step 101 includes:
and sending the first reconfiguration message sent by the target switching base station to a terminal.
In an alternative embodiment, the number of target base stations may be at least two, i.e. a plurality, i.e. the source base station may send a handover request message to a plurality of target base stations to determine which target base station is more suitable as the target handover base station for the terminal. In this way, the multiple target base stations may determine whether to support the handover of the slice currently operated by the terminal based on the handover request message, and decide what manner to perform the handover, and each target base station may generate a corresponding reconfiguration message according to the determination result and carry the reconfiguration message in a handover command and feed back the reconfiguration message to the source base station, so that the source base station may determine the target handover base station based on the handover command sent by each target base station and the signal strength of each target base station, and a specific determination manner may be multiple, where no specific limitation is made, and for example, a target base station with feedback-upgraded slice information and medium signal strength may be preferentially used as the target handover base station, or a target base station with feedback-admitted slice information and strong signal strength may be used as the target handover base station, or a target base station with feedback-slice degradation information and strongest signal strength may be used as the target handover base station, and so on.
After determining the target switching base station, a first reconfiguration message in a switching command sent by the target switching base station can be sent to the terminal, so that the terminal is switched to the target switching base station according to the first reconfiguration message.
In this way, by sending the handover request message to multiple target base stations at the same time, a target base station with a better suitability (such as better signal strength or better service quality) can be determined for the terminal to perform access handover, so as to ensure the service quality performed on the terminal and improve the service experience of the user.
According to the switching method, a first reconfiguration message is sent to a terminal, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information. In this way, the terminal can be switched to the target base station by degrading or backing up the slice, so that the terminal can continuously perform related services even if the target base station does not support the slice currently operated by the terminal or the load of the slice, service interruption is not easy to occur, and user service experience can be further ensured.
Referring to fig. 2, fig. 2 is a flowchart of another handover method provided in an embodiment of the present invention, for a target base station, as shown in fig. 2, where the method includes the following steps:
Step 201, receiving a handover request message sent by a source base station, where the handover request message includes slice information of a terminal connected to the source base station that is currently running.
Step 202, generating a first reconfiguration message according to the handover request message, where the first reconfiguration message includes slice degradation information or slice fallback information.
Step 203, sending the first reconfiguration message to the source base station.
It should be noted that, in this embodiment, as an implementation manner of the target base station corresponding to the embodiment shown in fig. 1, a specific implementation manner of the target base station may refer to a related description in the embodiment shown in fig. 1, and in order to avoid repetitive description, this embodiment is not repeated.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
the step 202 includes:
judging whether the minimum QoS requirement of a slice currently operated by the terminal can be met or not according to the minimum QoS requirement information;
if yes, a first reconfiguration message including the slice degradation information or the slice fallback information is generated.
Optionally, the handover request message includes recommended QoS requirement information of a slice in which the terminal is currently operating, or recommended QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
The method further comprises the steps of:
judging whether the recommended QoS requirement of the slice currently operated by the terminal can be met or not according to the recommended QoS requirement information;
if yes, generating a third reconfiguration message comprising the upgraded slice information.
Optionally, the step 202 includes:
if the target base station does not support the current running slice of the terminal or the load of the slice and can meet the requirement of the current running slice of the terminal or the load of the slice through degradation or rollback, generating a first reconfiguration message according to the switching request message;
after the step 201, the method further includes:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the source base station, wherein the second reconfiguration message comprises slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
And the refused bearing identifier is used for indicating the refused bearing.
The above optional implementation manner may refer to the related description in the embodiment shown in fig. 1, and in order to avoid repetitive description, this embodiment is not repeated.
According to the switching method, a switching request message sent by a source base station is received, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station; generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information; and sending the first reconfiguration message to the source base station. In this way, the terminal can be switched to the target base station by degrading or backing up the slice, so that the terminal can continuously perform related services even if the target base station does not support the slice currently operated by the terminal or the load of the slice, service interruption is not easy to occur, and user service experience can be further ensured.
Referring to fig. 3, fig. 3 is a flowchart of another handover method provided in an embodiment of the present invention, for a terminal, as shown in fig. 3, where the method includes the following steps:
step 301, receiving a first reconfiguration message sent by a source base station, where the first reconfiguration message is acquired by the source base station from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information.
Step 302, switching to the target base station according to the first reconfiguration message.
It should be noted that, in this embodiment, as an implementation manner of the terminal side corresponding to the embodiment shown in fig. 1, a specific implementation manner of the embodiment may refer to a related description in the embodiment shown in fig. 1, and in order to avoid repetitive description, this embodiment is not repeated.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
The method further comprises the steps of:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, receiving a second reconfiguration message sent by the source base station, wherein the second reconfiguration message comprises slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
The above optional implementation manner may refer to the related description in the embodiment shown in fig. 1, and in order to avoid repetitive description, this embodiment is not repeated.
In the switching method of the embodiment of the invention, a first reconfiguration message sent by a source base station is received, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information; and switching to the target base station according to the first reconfiguration message. In this way, the target base station can be switched to by degrading or backing up the slice, so that the terminal can continuously perform related services even if the target base station does not support the slice currently operated by the terminal or the load of the slice, service interruption is not easy to occur, and user service experience can be further ensured.
The embodiment of the invention also provides a source base station. Referring to fig. 4, fig. 4 is a block diagram of a source base station according to an embodiment of the present invention. Since the principle of the source base station for solving the problem is similar to that of the handover method in the embodiment of the present invention, the implementation of the source base station can refer to the implementation of the method, and the repetition is not repeated.
As shown in fig. 4, the source base station 400 includes:
a first sending module 401, configured to send a first reconfiguration message to a terminal, where the first reconfiguration message is acquired by the source base station from the target base station, and the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, as shown in fig. 5, the source base station 400 further includes:
a second sending module 402, configured to send a handover request message to the target base station, where the handover request message includes slice information that the terminal currently operates;
a first receiving module 403, configured to receive a first reconfiguration message sent by the target base station;
optionally, the handover request message includes at least one of:
Minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
as shown in fig. 6, the source base station 400 further includes:
and a third sending module 404, configured to send a second reconfiguration message to the terminal if the target base station does not support the current running slice of the terminal or the bearer of the slice, and neither degradation nor fallback can meet the requirement of the current running slice of the terminal or the bearer of the slice, where the second reconfiguration message includes slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, the number of the target base stations is at least two;
as shown in fig. 7, the source base station 400 further includes:
a determining module 405, configured to determine a target handover base station according to a first reconfiguration message sent by at least two target base stations and a signal strength of each of the at least two target base stations;
the first sending module 401 is configured to send a first reconfiguration message sent by the target handover base station to a terminal.
The source base station provided in the embodiment of the present invention may execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein.
The source base station 400 of the embodiment of the invention can enable the terminal to be switched to the target base station in a degrading or rollback mode by forwarding the degrading slice information or the rollback default switching information of the target base station, so that the terminal can continuously carry out related services without service interruption even if the target base station does not support the current running slice or the load of the slice, and further the user service experience can be ensured.
The embodiment of the invention also provides a target base station. Referring to fig. 8, fig. 8 is a block diagram of a target base station according to an embodiment of the present invention. Since the principle of solving the problem of the target base station is similar to that of the handover method in the embodiment of the present invention, the implementation of the target base station can refer to the implementation of the method, and the repetition is not repeated.
As shown in fig. 8, the target base station 800 includes:
a receiving module 801, configured to receive a handover request message sent by a source base station, where the handover request message includes slice information currently operated by a terminal connected to the source base station;
A generating module 802, configured to generate a first reconfiguration message according to the handover request message, where the first reconfiguration message includes slice degradation information or slice fallback information;
a first sending module 803, configured to send the first reconfiguration message to the source base station.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
As shown in fig. 9, the generating module 802 includes:
a first judging unit 8021, configured to judge whether the minimum QoS requirement of the slice currently operated by the terminal can be met according to the minimum QoS requirement information;
a first generating unit 8022, configured to generate, if yes, a first reconfiguration message including the slice degradation information or the slice fallback information.
Optionally, the handover request message includes recommended QoS requirement information of a slice in which the terminal is currently operating, or recommended QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
optionally, the generating module 802 is configured to generate, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, and the current slice operated by the terminal or a bearer of the slice can be met by degradation or rollback, a first reconfiguration message according to the handover request message;
as shown in fig. 10, the target base station 800 further includes:
a second sending module 804, configured to send a second reconfiguration message to the source base station if the target base station does not support the slice currently operated by the terminal or the bearer of the slice, and neither degradation nor fallback can meet the requirement of the slice currently operated by the terminal or the bearer of the slice, where the second reconfiguration message includes slice rejection information.
The target base station provided in the embodiment of the present invention may execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein.
The target base station 800 in the embodiment of the invention can feed back the degradation slice information or the rollback default switching information to the source base station, so that the terminal can be switched to the target base station in a degradation or rollback mode, and therefore, even if the target base station does not support the slice currently operated by the terminal or the load of the slice, the terminal can continuously carry out related services, service interruption is not easy to occur, and further user service experience can be ensured.
The embodiment of the invention also provides a terminal. Referring to fig. 11, fig. 11 is a block diagram of a terminal according to an embodiment of the present invention. Since the principle of solving the problem by the terminal is similar to that of the handover method in the embodiment of the present invention, the implementation of the terminal can refer to the implementation of the method, and the repetition is not repeated.
As shown in fig. 11, the terminal 1100 includes:
a first receiving module 1101, configured to receive a first reconfiguration message sent by a source base station, where the first reconfiguration message is acquired by the source base station from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information;
And a switching module 1102, configured to switch to the target base station according to the first reconfiguration message.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
as shown in fig. 12, the terminal 1100 further includes:
and a second receiving module 1103, configured to receive a second reconfiguration message sent by the source base station if the target base station does not support the current running slice of the terminal or the bearer of the slice, and neither degradation nor fallback can meet the requirement of the current running slice of the terminal or the bearer of the slice, where the second reconfiguration message includes slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
The terminal 1100 in the embodiment of the present invention can switch the slice to the target base station in a mode of degrading or backing off by receiving the degrading slice information or backing off default switching information fed back by the source base station, so that even if the target base station does not support the slice currently running or the load of the slice, the terminal can continuously perform related services, and service interruption is not easy to occur, thereby ensuring user service experience.
The embodiment of the invention also provides a source base station. Because the principle of the source base station for solving the problem is similar to that of the handover method in the embodiment of the present invention, the implementation of the source base station can refer to the implementation of the method, and the repetition is not repeated. As shown in fig. 13, a source base station according to an embodiment of the present invention includes:
processor 1300, for reading the program in memory 1320, performs the following procedure:
A first reconfiguration message is sent to the terminal by the transceiver 1310, the first reconfiguration message being obtained by the source base station from the target base station, the first reconfiguration message including slice degradation information or slice fallback information.
A transceiver 1310 for receiving and transmitting data under the control of the processor 1300.
Where in FIG. 13, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of the one or more processors, specifically represented by processor 1300, and the memory, represented by memory 1320, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1310 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium.
The processor 1300 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1300 in performing operations.
Further, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Further, the transceiver 1310 is further configured to send a handover request message to the target base station, where the handover request message includes slice information that the terminal currently operates; receiving a first reconfiguration message sent by the target base station;
further, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Further, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Further, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
processor 1300, for reading the program in memory 1320, performs the following procedure:
If the target base station does not support the current operation slice of the terminal or the bearer of the slice and cannot meet the requirements of the current operation slice of the terminal or the bearer of the slice through degradation and rollback, a second reconfiguration message is sent to the terminal through the transceiver 1310, wherein the second reconfiguration message comprises slice rejection information.
Further, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Further, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Further, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Further, the number of the target base stations is at least two;
processor 1300, for reading the program in memory 1320, performs the following procedure:
determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the first reconfiguration message sent by the target handover base station is sent to the terminal through the transceiver 1310.
The source base station provided in the embodiment of the present invention may execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein.
The embodiment of the invention also provides a target base station. Because the principle of solving the problem of the target base station is similar to that of the handover method in the embodiment of the present invention, the implementation of the target base station can refer to the implementation of the method, and the repetition is not repeated. As shown in fig. 14, the target base station in the embodiment of the present invention includes:
processor 1400, for reading the program in memory 1420, performs the following process:
receiving, by a transceiver 1410, a handover request message transmitted by a source base station, the handover request message including slice information of a current operation of a terminal connected to the source base station;
Generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
the first reconfiguration message is sent to the source base station through transceiver 1410.
A transceiver 1410 for receiving and transmitting data under the control of the processor 1400.
Wherein in fig. 14, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by the processor 1400 and various circuits of the memory represented by the memory 1420, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1410 may be a number of elements, i.e., include a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium.
The processor 1400 is responsible for managing the bus architecture and general processing, and the memory 1420 may store data used by the processor 1400 in performing operations.
Further, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Further, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Further, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Further, the handover request message includes minimum quality of service QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
processor 1400, for reading the program in memory 1420, performs the following process:
judging whether the minimum QoS requirement of a slice currently operated by the terminal can be met or not according to the minimum QoS requirement information; if yes, a first reconfiguration message including the slice degradation information or the slice fallback information is generated.
Further, the processor 1400 is configured to read the program in the memory 1420, and execute the following procedures:
if the target base station does not support the current running slice of the terminal or the load of the slice and can meet the requirement of the current running slice of the terminal or the load of the slice through degradation or rollback, generating a first reconfiguration message according to the switching request message;
If the target base station does not support the current operation slice of the terminal or the bearer of the slice and the current operation slice of the terminal or the bearer of the slice cannot be satisfied by degradation and rollback, a second reconfiguration message is sent to the source base station through the transceiver 1410, the second reconfiguration message including slice rejection information.
The target base station provided in the embodiment of the present invention may execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein.
The embodiment of the invention also provides a terminal. Since the principle of solving the problem by the terminal is similar to that of the handover method in the embodiment of the present invention, the implementation of the terminal can refer to the implementation of the method, and the repetition is not repeated. As shown in fig. 15, a terminal according to an embodiment of the present invention includes:
processor 1500, for reading the program in memory 1520, performs the following process:
receiving, by the transceiver 1510, a first reconfiguration message sent by a source base station, the first reconfiguration message being obtained by the source base station from a target base station, the first reconfiguration message including slice degradation information or slice backoff information;
and switching to the target base station according to the first reconfiguration message.
A transceiver 1510 for receiving and transmitting data under the control of the processor 1500.
Where in FIG. 15, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of the one or more processors, as represented by processor 1500, and the memory, as represented by memory 1520, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 1530 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 may store data used by the processor 1500 in performing operations.
Further, the slice degradation information includes at least one of:
Degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Further, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Further, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Further, if the target base station does not support the current running slice of the terminal or the bearer of the slice, and the current running slice of the terminal or the bearer of the slice can be met through degradation or rollback, the first reconfiguration message includes slice degradation information or slice rollback information;
processor 1500, for reading the program in memory 1520, performs the following process:
if the target base station does not support the current operation slice of the terminal or the bearer of the slice and cannot meet the requirements of the current operation slice of the terminal or the bearer of the slice through degradation and rollback, a second reconfiguration message sent by the source base station is received through the transceiver 1510, wherein the second reconfiguration message comprises slice rejection information.
Further, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
The terminal provided by the embodiment of the present invention may execute the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein.
Furthermore, a computer readable storage medium according to an embodiment of the present invention stores a computer program, which in one implementation is executable by a processor to implement the steps of:
and sending a first reconfiguration message to the terminal, wherein the first reconfiguration message is acquired from the target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the computer program may be executed by a processor to implement the steps of:
Transmitting a switching request message to the target base station, wherein the switching request message comprises slice information of the current operation of the terminal;
receiving a first reconfiguration message sent by the target base station;
optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the computer program may be further executable by a processor to implement the steps of:
if the target base station does not support the current running slice of the terminal or the bearer of the slice and can meet the requirements of the current running slice of the terminal or the bearer of the slice through degradation or rollback, the first reconfiguration message comprises slice degradation information or slice rollback information;
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the terminal, wherein the second reconfiguration message comprises slice rejection information.
Optionally, the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
Optionally, the slice degradation information includes at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
Optionally, the slice fallback information includes at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
and the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
Optionally, the number of the target base stations is at least two;
the computer program may also be executable by a processor to perform the steps of:
determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
and sending the first reconfiguration message sent by the target switching base station to a terminal.
In another embodiment, the computer program is executable by a processor to perform the steps of:
receiving a switching request message sent by a source base station, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station;
generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
and sending the first reconfiguration message to the source base station.
Optionally, if the target base station does not support a slice currently operated by the terminal or a bearer of the slice, the first reconfiguration message includes slice degradation information or slice fallback information.
Optionally, the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
Optionally, the QoS requirement information includes at least one of latency, packet error rate, and priority.
Optionally, the handover request message includes minimum QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow in the slice in which the terminal is currently operating;
the computer program may also be executable by a processor to perform the steps of:
judging whether the minimum QoS requirement of a slice currently operated by the terminal can be met or not according to the minimum QoS requirement information;
if yes, a first reconfiguration message including the slice degradation information or the slice fallback information is generated.
Optionally, the computer program may be further executable by a processor to implement the steps of:
if the target base station does not support the current running slice of the terminal or the load of the slice and can meet the requirement of the current running slice of the terminal or the load of the slice through degradation or rollback, generating a first reconfiguration message according to the switching request message;
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the source base station, wherein the second reconfiguration message comprises slice rejection information.
In yet another embodiment, the computer program is executable by a processor to perform the steps of:
receiving a first reconfiguration message sent by a source base station, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information;
and switching to the target base station according to the first reconfiguration message.
In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform part of the steps of the transceiving method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.

Claims (25)

1. The switching method is suitable for the source base station and comprises the following steps:
transmitting a first reconfiguration message to a terminal, wherein the first reconfiguration message is acquired from a target base station and comprises slice degradation information or slice rollback information;
And if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
2. The handover method according to claim 1, wherein before the sending the first reconfiguration message to the terminal, the method further comprises:
transmitting a switching request message to the target base station, wherein the switching request message comprises slice information of the current operation of the terminal;
and receiving a first reconfiguration message sent by the target base station.
3. The handover method of claim 2, wherein the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
4. The handover method of claim 3, wherein the QoS requirement information includes at least one of latency, packet error rate, and priority.
5. The handover method of claim 1, wherein the first reconfiguration message includes slice degradation information or slice fallback information if the target base station does not support a slice currently operated by the terminal or a bearer of the slice and can meet a requirement of the slice currently operated by the terminal or the bearer of the slice by degradation or fallback;
The method further comprises the steps of:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the terminal, wherein the second reconfiguration message comprises slice rejection information.
6. The handover method of claim 5, wherein the slice rejection information includes at least one of:
a rejected slice identifier indicating a rejected slice and indicating rejection of all bearers of the slice;
a partially rejected slice identity for indicating a rejected slice and for indicating a partial bearer rejecting the slice;
and the refused bearing identifier is used for indicating the refused bearing.
7. The handover method of claim 1, wherein the slice degradation information comprises at least one of:
degraded slice identification;
degraded bearer identification;
degradation information indicating a level of degradation.
8. The handover method of claim 1, wherein the slice backoff information comprises at least one of:
a default slice bearer establishment message, configured to instruct the terminal to establish a bearer of a default slice;
And the slice rollback message is used for indicating the terminal to rollback the currently running slice to the default slice.
9. The handover method according to claim 1, wherein the number of target base stations is at least two;
before the first reconfiguration message is sent to the terminal, the method further includes:
determining a target switching base station according to a first reconfiguration message sent by at least two target base stations and the signal intensity of each target base station in the at least two target base stations;
the sending the first reconfiguration message to the terminal includes:
and sending the first reconfiguration message sent by the target switching base station to a terminal.
10. The switching method is suitable for the target base station and comprises the following steps:
receiving a switching request message sent by a source base station, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station;
generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
sending the first reconfiguration message to the source base station;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
11. The handover method of claim 10, wherein the handover request message includes at least one of:
minimum quality of service (QoS) requirement information of a slice currently operated by the terminal;
minimum QoS requirement information of QoS flows in a slice currently operated by the terminal;
recommended QoS requirement information of a slice currently operated by the terminal;
recommended QoS requirement information for the QoS flow within the slice currently operated by the terminal.
12. The handover method of claim 11, wherein the QoS requirement information includes at least one of latency, packet error rate, and priority.
13. The handover method of claim 11, wherein the handover request message includes minimum quality of service QoS requirement information of a slice in which the terminal is currently operating, or minimum QoS requirement information of a QoS flow within the slice in which the terminal is currently operating;
the generating a first reconfiguration message according to the handover request message includes:
judging whether the minimum QoS requirement of a slice currently operated by the terminal can be met or not according to the minimum QoS requirement information;
if yes, a first reconfiguration message including degraded slice information or fallback default slice information is generated.
14. The handover method of claim 10, wherein the generating a first reconfiguration message according to the handover request message comprises:
if the target base station does not support the current running slice of the terminal or the load of the slice and can meet the requirement of the current running slice of the terminal or the load of the slice through degradation or rollback, generating a first reconfiguration message according to the switching request message;
after receiving the handover request message sent by the source base station, the method further includes:
and if the target base station does not support the current running slice of the terminal or the loading of the slice and cannot meet the requirements of the current running slice of the terminal or the loading of the slice through degradation and rollback, sending a second reconfiguration message to the source base station, wherein the second reconfiguration message comprises slice rejection information.
15. The switching method is suitable for the terminal and comprises the following steps:
receiving a first reconfiguration message sent by a source base station, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information;
switching to the target base station according to the first reconfiguration message;
And if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
16. A source base station, comprising:
a first sending module, configured to send a first reconfiguration message to a terminal, where the first reconfiguration message is obtained from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
17. A target base station, comprising:
the switching module is used for receiving a switching request message sent by a source base station, wherein the switching request message comprises slice information of the current operation of a terminal connected with the source base station;
the generation module is used for generating a first reconfiguration message according to the switching request message, wherein the first reconfiguration message comprises slice degradation information or slice rollback information;
a first sending module, configured to send the first reconfiguration message to the source base station;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
18. A terminal, comprising:
the first receiving module is used for receiving a first reconfiguration message sent by a source base station, wherein the first reconfiguration message is acquired from a target base station by the source base station, and the first reconfiguration message comprises slice degradation information or slice rollback information;
the switching module is used for switching to the target base station according to the first reconfiguration message;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
19. A source base station, comprising: a transceiver and a processor;
the transceiver is configured to send a first reconfiguration message to the terminal, where the first reconfiguration message is acquired from the target base station, and the first reconfiguration message includes slice degradation information or slice fallback information;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
20. A target base station, comprising: a transceiver and a processor;
the transceiver is configured to receive a handover request message sent by a source base station, where the handover request message includes slice information that a terminal connected to the source base station currently operates;
The processor is configured to generate a first reconfiguration message according to the handover request message, where the first reconfiguration message includes slice degradation information or slice fallback information;
the transceiver is further configured to send the first reconfiguration message to the source base station;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
21. A terminal, comprising: a transceiver and a processor;
the transceiver is configured to receive a first reconfiguration message sent by a source base station, where the first reconfiguration message is acquired by the source base station from a target base station, and the first reconfiguration message includes slice degradation information or slice fallback information;
the processor is configured to switch to the target base station according to the first reconfiguration message;
and if the target base station does not support the current running slice of the terminal or the loading of the slice, the first reconfiguration message comprises slice degradation information or slice rollback information.
22. A source base station, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the handover method according to any of claims 1 to 9.
23. A target base station, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, performs the steps in the handover method according to any one of claims 10 to 14.
24. A terminal, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, performs the steps in the handover method as claimed in claim 15.
25. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the handover method according to any one of claims 1 to 9; or the computer program when executed by a processor performs the steps in the handover method according to any of claims 10 to 14; or which computer program when being executed by a processor carries out the steps in a handover method as claimed in claim 15.
CN201910836413.6A 2019-09-05 2019-09-05 Switching method, source base station, target base station and terminal Active CN112449389B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910836413.6A CN112449389B (en) 2019-09-05 2019-09-05 Switching method, source base station, target base station and terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910836413.6A CN112449389B (en) 2019-09-05 2019-09-05 Switching method, source base station, target base station and terminal

Publications (2)

Publication Number Publication Date
CN112449389A CN112449389A (en) 2021-03-05
CN112449389B true CN112449389B (en) 2023-07-21

Family

ID=74733318

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910836413.6A Active CN112449389B (en) 2019-09-05 2019-09-05 Switching method, source base station, target base station and terminal

Country Status (1)

Country Link
CN (1) CN112449389B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392038A (en) * 2017-08-11 2019-02-26 华为技术有限公司 Communication means and source base station, target BS, equipment of the core network, terminal device
CN109803279A (en) * 2017-11-16 2019-05-24 电信科学技术研究院 A kind of slice management method, base station and terminal

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117255392A (en) * 2016-02-16 2023-12-19 交互数字专利控股公司 Network slicing operation
CN108696910B (en) * 2017-04-11 2020-10-09 华为技术有限公司 Method, device and storage medium for selecting target base station
CN109548105B (en) * 2017-06-16 2020-03-10 华为技术有限公司 Communication method, access network equipment and core network equipment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392038A (en) * 2017-08-11 2019-02-26 华为技术有限公司 Communication means and source base station, target BS, equipment of the core network, terminal device
CN109803279A (en) * 2017-11-16 2019-05-24 电信科学技术研究院 A kind of slice management method, base station and terminal

Also Published As

Publication number Publication date
CN112449389A (en) 2021-03-05

Similar Documents

Publication Publication Date Title
CN108811011B (en) Session management method, network device and communication system
US8213381B2 (en) Mobile communication system, core network node selection method, and base station and mobile station used therefor
RU2499363C2 (en) Mobile communication method, mobile communication switching station, radio base station and mobile station
US8054782B2 (en) Delivering services in a wireless communications system
US6687237B1 (en) Methods and systems for facilitating a multi-mode multi-pilot hard handoff
EP2384061A2 (en) Apparatus and method for automatic SIM card selection according to network environment in dual mode terminal
US11051215B2 (en) Switching method, terminal device, and network device
US9661567B2 (en) Method, apparatus and system for service establishment for multi-mode user equipment
JP2004511980A (en) Service priority in multi-cell networks
CN107306386B (en) Method for triggering terminal roaming by access point and access point
CN110662274A (en) Method for accessing network slice and user device using the same
CN109803279B (en) Slice management method, base station and terminal
CN111901895B (en) Method and device for establishing user plane
CN104618971A (en) Service switching control method and service switching control device
CN112449374B (en) Method and device for determining target main base station and associating target auxiliary base station
CN112449389B (en) Switching method, source base station, target base station and terminal
US10966208B2 (en) Voice service processing method and apparatus
CN114900825B (en) Terminal cross-zone cooperative relay switching communication method, system, equipment and storage medium
US8531965B2 (en) Message processing method and system
KR102624235B1 (en) Communication device, communication device control method, program, and non-transitory computer-readable storage medium
CN116195281A (en) Wireless communication method, communication device and communication system
US11246062B2 (en) Method for accessing inter-RAT cell and related device
CN109565724B (en) Switching processing method, network equipment and computer storage medium
CN113676962B (en) Handover processing method, communication equipment, target base station, source base station and terminal
WO2022263318A1 (en) Cellular telecommunications network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant