CN113329453A - Switching method and device - Google Patents
Switching method and device Download PDFInfo
- Publication number
- CN113329453A CN113329453A CN202010128843.5A CN202010128843A CN113329453A CN 113329453 A CN113329453 A CN 113329453A CN 202010128843 A CN202010128843 A CN 202010128843A CN 113329453 A CN113329453 A CN 113329453A
- Authority
- CN
- China
- Prior art keywords
- slice
- target node
- node
- supported
- slices
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000013507 mapping Methods 0.000 claims abstract description 165
- 238000012790 confirmation Methods 0.000 claims abstract description 16
- 230000006870 function Effects 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 10
- 238000012423 maintenance Methods 0.000 claims description 5
- 230000005540 biological transmission Effects 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 21
- 101150014328 RAN2 gene Proteins 0.000 description 20
- 101150069124 RAN1 gene Proteins 0.000 description 13
- 101100355633 Salmo salar ran gene Proteins 0.000 description 13
- 238000012545 processing Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 5
- 101100087393 Caenorhabditis elegans ran-2 gene Proteins 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
Abstract
The embodiment of the invention provides a switching method and equipment, wherein the method comprises the following steps: receiving a handover request message from a source node; mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice; and sending a switching request confirmation message to the source node. In the embodiment of the invention, when the connected UE moves across the registration area, the service network slice remapping can be utilized to ensure the data transmission continuity for the slice which is not supported by the target node.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a switching method and equipment.
Background
A slicing technique is introduced into a New Radio (NR) system of a fifth generation mobile communication technology (5th generation, 5G), different slicing types correspond to different service types or different service providers, an operator can flexibly configure network slices supported by the operator on a network side according to different requirements, and different cells independently configure deployed slicing types. However, due to the existing network architecture, the protocol provides that the types of the slices in the Registration Area (RA) of the terminal (e.g., User Equipment (UE)) are consistent continuously. I.e. the serving cell can only be designated by the network as registration area for the UE if the supported slice types are identical. Once the UE moves to a cell that is not consistent with the slice type supported by the registration area, the UE needs to reinitiate registration and the network reallocates the registration area. When the UE moves across the registration area in the connected state, if the activated data connection network slice target node does not support, the target node will refuse the handover, and the data connection will be interrupted.
Referring to fig. 1, when a UE initiates a registration request in a cell 1, slice 1 and slice 2 request information carried by the UE, a 5G-Core Network (CN) returns a registration confirmation message for accepting slice 1 and slice 2 to the UE, and provides a registration area for the UE, for example, including the cell 1 and the cell 2. The UE may use slice 1 and slice 2 when cell 1 activates a data connection. When the connected UE moves within the registration area, slice 1 and slice 2 are always supported, so the continuity of data connection can be ensured through the handover procedure. If the UE moves to cell 3, since cell 1 and cell 2 in the registration area of cell 3 are different and cannot support slice 2 related data connection, slice 2 based data connection carried by the connected UE will be rejected by cell 3 according to the current standard. Thereby breaking the slice 2 based data connection.
Disclosure of Invention
An object of the embodiments of the present invention is to provide a handover method and device, which solve the problem of how to remap a network slice of a serving cell when a connected UE moves across registration areas to ensure data transmission continuity.
In a first aspect, an embodiment of the present invention provides a handover method, which is applied to a radio access network node, where the radio access network node is a target node, and the handover method includes:
receiving a handover request message from a source node;
mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice;
and sending a switching request confirmation message to the source node.
Optionally, the mapping the first slice to the slice supported by the target node includes:
and mapping the first slice to the slice supported by the target node according to the mapping relation between the slice supported by the target node and the mappable slice stored in the target node.
Optionally, the method further comprises:
acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
agreement is agreed;
operation, maintenance and management (OAM) configuration;
a neighbor node of the target node;
a core network.
Optionally, the obtaining, by the node adjacent to the target node, a mapping relationship between a slice supported by the target node and a mappable slice includes:
when an Xn interface between the target node and an adjacent node is established, acquiring a mapping relation between a slice supported by the target node and a mappable slice through the adjacent node;
alternatively, the first and second electrodes may be,
the obtaining, by the core network, a mapping relationship between a slice supported by the target node and a mappable slice includes:
and when the NG interface is established or the access and mobility management function AMF configuration is updated, acquiring the mapping relation between the slices supported by the target node and the mappable slices through the core network.
Optionally, the mapping the first slice to the slice supported by the target node includes:
mapping the first slice to a slice supported by the target node according to the switching request message;
wherein the handover request message includes: mapping relation between slices supported by the target node and mappable slices;
or, the handover request message includes: a mapping relationship of the first slice to slices supported by the target node.
Optionally, the mapping the first slice to the slice supported by the target node includes:
if the target node stores the mapping relationship between the slices supported by the target node and the signed slices, mapping the first slice to the slices supported by the target node according to the mapping relationship and the switching request message, wherein the switching request message comprises: the information of the first slice and the information of the contracted slice corresponding to the first slice;
alternatively, the first and second electrodes may be,
and if the target node does not store the mapping relation between the slices supported by the target node and the signed slices, mapping the first slice to a default slice configured in the target node, wherein the default slice is the slice supported by the target node.
Optionally, the handover request confirm message includes: slice remapping information, the slice remapping information indicating that the first slice maps to a slice supported by the target node.
Optionally, the method further comprises:
sending a path switching request message to a core network element, wherein the path switching request message comprises: the slice remapping information;
and receiving a path switching request confirmation message from the core network element.
In a second aspect, an embodiment of the present invention provides a handover method, which is applied to a radio access network node, where the radio access network node is a source node, and the handover method includes:
sending a switching request message to a target node;
receiving a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
Optionally, the handover request message includes: and mapping relation between the slices supported by the target node and the mappable slices.
Optionally, the method further comprises:
acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
agreement is agreed;
operation, maintenance and management (OAM) configuration;
the target node, which is a neighbor node of the source node;
a core network.
Optionally, the handover request message includes: a mapping relationship of the first slice to slices supported by the target node.
Optionally, the method further comprises:
and if the source node stores the mapping relation between the terminal signing slice and the mappable slice, determining the mapping relation between the first slice and the slice supported by the target node according to the mapping relation between the terminal signing slice and the mappable slice and the slice supported by the target node.
In a third aspect, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a target node, and the radio access network node includes:
a first receiving module, configured to receive a handover request message from a source node;
a mapping module, configured to map a first slice to a slice supported by the target node, where the first slice is a slice used by a data connection for which a terminal applies for handover, and the target node does not support the first slice;
a first sending module, configured to send a handover request acknowledgement message to the source node.
In a fourth aspect, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a target node, and the radio access network node includes: a first transceiver and a first processor;
the first transceiver transmits and receives data under control of the first processor;
the first processor reads a program in a memory to perform the following operations: receiving a handover request message from a source node; mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice; and sending a switching request confirmation message to the source node.
In a fifth aspect, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a source node, and the radio access network node includes:
a third sending module, configured to send a handover request message to a target node;
a third receiving module, configured to receive a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
In a sixth aspect, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a source node, and the radio access network node includes: a second transceiver and a second processor;
the second transceiver transmits and receives data under the control of the second processor;
the second processor reads a program in the memory to perform the following operations: sending a switching request message to a target node; receiving a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
In a seventh aspect, an embodiment of the present invention further provides a communication device, including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, performs steps comprising the handover method according to the first or second aspect.
In an eighth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps including the handover method according to the first aspect or the second aspect.
In the embodiment of the invention, when the connected UE moves across the registration area, the service network slice remapping can be utilized to ensure the data transmission continuity for the slice which is not supported by the target node.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic diagram of a network slice deployment scenario;
FIG. 2 is a schematic diagram of a 5G network architecture;
FIG. 3 is a diagram illustrating a handover method according to an embodiment of the present invention;
FIG. 4 is a second schematic diagram illustrating a handover method according to an embodiment of the present invention;
FIG. 5 is a third exemplary diagram illustrating a handover method according to the present invention;
FIG. 6 is a third schematic diagram illustrating a handover method according to an embodiment of the present invention;
FIG. 7 is a diagram illustrating one embodiment of a target node;
FIG. 8 is a second schematic diagram of a target node according to the second embodiment of the present invention;
FIG. 9 is a diagram illustrating a source node according to an embodiment of the present invention;
FIG. 10 is a second schematic diagram of a source node according to the second embodiment of the present invention;
fig. 11 is a schematic diagram of a communication device according to an embodiment of the present invention.
Detailed Description
In order to facilitate understanding of the embodiments of the present invention, the following technical points are introduced below: and (5) network slicing.
Fig. 2 is a schematic diagram of a 5G network architecture. The network slicing technology is a technology that enables an operator to slice a plurality of virtual end-to-end network slicing instances in a 5G network to provide various types of services with different feature requirements. The operator may also deploy slice instances of the same service type but different service providers to serve different customer groups.
In the figure, NSSF is a Network Slice Selection Function (Network Slice Selection Function); AUSF is Authentication Server Function (Authentication Server Function); AMF is Access and Mobility Management Function (Access and Mobility Management Function); UDM is Unified Data Manager; SMF is Session Management Function (Session Management Function); the PCF is a Policy Control Function (Policy Control Function); AF is an Application function (Application function); UPF is User Plane Function (User Plane Function); DN is a Data Network (Data Network).
Different Network slices are identified with a Single Network Slice Selection Assistance Information (S-NSSAI), which contains two characteristics: Slice/Service type (SST) and Slice Specifier (SD).
In a 5G NR environment, when applying for network registration, the UE carries a supported network slice identifier (S-NSSAI) stored by the UE, and a network end returns a network slice service identifier (allowed S-NSSAI) and a registration area received by the UE according to a user subscription and a network support condition.
According to the protocol, when the network is deployed, the network slices in the same Tracking Area (TA) are deployed consistently, and when the UE registers, the 5G Core network (5G-Core network, 5G-CN) assigns a registration Area consisting of a Tracking Area list (TA list) supporting the same network slices to the UE.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.
In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
The techniques described herein are not limited to Long Time Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems.
The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.
Referring to fig. 3, an embodiment of the present invention provides a handover method, where an execution subject of the handover method is a radio access network node, and the radio access network node is a target node, including: step 301, step 302 and step 303.
Step 301: receiving a handover request message from a source node;
for example, the handover request message includes information of a first slice, and further includes: and the information of the contracted section corresponding to the first section.
Step 302: mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which the terminal applies for switching, and the target node does not support the first slice;
it is understood that the target node does not support the first slice, i.e. the target node supports a slice of a different type than the first slice;
step 303: and sending a switching request confirmation message to the source node.
In some embodiments, if the target node configures the mapping list, step 302 may be implemented by:
and mapping the first slice to the slice supported by the target node according to the mapping relation between the slice supported by the target node and the mappable slice stored in the target node. Namely, the target node sends the remap according to the configuration mapping list.
In some embodiments, the mapping relationship between slices supported by the target node and mappable slices is obtained by one or more of:
(1) agreement is agreed;
(2) operation, Maintenance and Administration (OAM) configuration;
(3) a neighbor node of the target node;
for example, when an Xn interface between the target node and an adjacent node is established, a mapping relationship between a slice supported by the target node and a mappable slice is obtained through the adjacent node;
(4) a core network.
For example, when an NG interface is established or an access and mobility management function (AMF) configuration is updated, a mapping relation between the slices supported by the target node and the mappable slices is obtained through the core network.
That is, when the connected terminal initiates Xn handover, if the slice target node used by the data connection applying for handover does not support, but the slice obtained by querying the mapping relationship can be mapped to the slice supported by the target node, the target node can accommodate the data connection of the slice and redirect to a new slice.
In some embodiments, if the target node does not configure the mapping list, step 302 may be implemented by:
mapping the first slice to a slice supported by the target node according to the switching request message;
wherein the handover request message includes: mapping relation between slices supported by the target node and mappable slices; or, the handover request message includes: a mapping relationship of the first slice (source slice) to slices supported by the target node (target slices).
That is, the target node sends the remap according to the mapping list of the terminal carried in the handover request message.
For example, when the connected UE initiates Xn handover across the registration area, if the source node obtains and stores the mapping relationship between the subscription slice and the mappable slice, the source node queries the mapping relationship, and performs slice remapping according to the slice supported by the target node obtained when the Xn interface is established, and the handover request message may carry: the method comprises the following steps of signing slices, source slices and the mapping relation of target slices, and the target nodes carry out admission processing according to the mapping relation.
In some embodiments, step 302 may be implemented by:
if the target node stores the mapping relationship between the slices supported by the target node and the signed slices, mapping the first slice to the slices supported by the target node according to the mapping relationship and the switching request message, wherein the switching request message comprises: the information of the first slice and the information of the contracted slice corresponding to the first slice.
In some embodiments, step 302 may be implemented by:
and if the target node does not store the mapping relation between the slices supported by the target node and the signed slices, mapping the first slice to a default slice configured in the target node, wherein the default slice is the slice supported by the target node.
That is, if the source node does not obtain and store the mapping relationship between the subscription slice and the mappable slice, the source node carries in the handover request message: slice information and contract slice information corresponding to the slice. If the target node stores the mapping relation between the signed slice and the target node support slice, the target node can perform remapping and admission processing according to the mapping relation. And if the target node does not store the mapping relation between the signed slice and the slice supported by the target node, the target node maps the slice which is not correspondingly supported by the target node to the configured default slice or rejects the slice.
In some embodiments, the handover request confirm message comprises: slice remapping information, the slice remapping information indicating that the first slice maps to a slice supported by the target node.
In some embodiments, the method further comprises:
sending a path switching request message to a core network element, wherein the path switching request message comprises: the slice remapping information;
and receiving a path switching request confirmation message from the core network element.
That is, the target node can admit the data connection of the slice and redirect to a new slice, and notify the 5G-CN network element that the slice is remapped when the link is switched.
In the embodiment of the invention, when the connected UE moves across the registration area, the service network slice remapping can be utilized to ensure the data transmission continuity for the slice which is not supported by the target node.
Referring to fig. 4, an embodiment of the present invention provides a handover method, where an execution subject of the method may be a radio access network node, where the radio access network node is a source node, and the handover method includes: step 401 and step 402.
Step 401: sending a switching request message to a target node;
for example, the handover request message includes information of the first slice. Further, still include: and the information of the contracted section corresponding to the first section.
Step 402: receiving a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
In some embodiments, the handover request message comprises: and mapping relation between the slices supported by the target node and the mappable slices.
In some embodiments, the method further comprises:
acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
(1) agreement is agreed;
(2) OAM configuration;
(3) the target node, which is a neighbor node of the source node;
(4) a core network.
In some embodiments, the handover request message comprises: a mapping relationship of the first slice to slices supported by the target node.
In some embodiments, the method further comprises:
and if the source node stores the mapping relation between the terminal signed slice and the mappable slice, determining the mapping relation between the first slice and the slice supported by the target node according to the mapping relation between the terminal signed slice and the mappable slice and the slice supported by the target node.
It can be understood that the mapping relationship between the terminal subscription slice and the mappable slice includes a mapping relationship between the first slice and the mappable slice, and the mappable slice may include a slice supported by the target node, so that the mapping relationship between the first slice and the slice supported by the target node can be determined accordingly.
In the embodiment of the invention, when the connected UE moves across the registration area, the service network slice remapping can be utilized to ensure the data transmission continuity for the slice which is not supported by the target node.
Examples of the present invention will be described below with reference to embodiment mode 1 and embodiment mode 2.
Embodiment 1: RAN node initiates remapping according to configured mapping list information
(1) The RAN node obtains and stores mapping relations between the supported slices and the mappable slices, and the mapping relation obtaining comprises the following methods:
a) when the NG interface is established or the AMF configuration is updated, the 5G-CN issues the mapping relation.
b) The mapping relationship list is provided by the neighboring RAN node when it is established by Xn.
c) Configured by RAN node OAM
d) RAN node Pre-configuration
(2) When the connected UE initiates Xn switching, if the slice target node used by the data connection applying for switching does not support, the slice can be mapped to a certain slice supported by the target node by inquiring the mapping relation. The target node may admit the data connection for that slice and redirect to a new slice. And informs the 5G-CN network element slice of remapping when the link is switched.
Referring to fig. 5, step 501 to step 512 are included.
Step 501: RAN1 initiates the NG interface setup.
It is to be understood that the RAN1 is a source node, the RAN2 is a target node, and the core network elements are 5G-CN elements.
Step 502: the 5G-CN network element replies an NG interface establishment response message carrying slice mapping information, wherein the slice mapping information comprises: the mapping of the slices supported by RAN2 to mappable slices.
Wherein the mappable slice includes: slices not supported by RAN 2.
Step 503: the RAN1 initiates the Xn interface setup.
Step 504: RAN2 replies an Xn interface setup response message, which carries slice mapping information, where the slice mapping information includes: the mapping of the slices supported by RAN2 to mappable slices.
It is understood that steps 501 and 502 are optional in relation to steps 503 and 504, that is, the slice mapping information may be obtained from a 5G-CN network element through steps 501 and 502, or from a neighboring node through steps 503 and 504, or from Operation Management Application (OMA) configuration.
Step 505: the RAN1 sends a handover request message to the RAN2 carrying the slice mapping information.
Step 506: if the slice RAN2 used for the data connection for handover does not support, the RAN2 queries slice mapping information to obtain slices that are not supported by the RAN2 according to the slices supported by the node, and can map the slices that are not supported by the RAN2 to the slices that are supported by the RAN2, so as to remap the slices that are not supported by the RAN 2.
Step 507: RAN2 responds to the handover request acknowledge message and carries slice remapping information indicating that the slice used for the data connection for which handover is applied is mapped to the slice supported by RAN 2.
Step 508-510: RAN1 informs a User Equipment (UE) to initiate handover;
optionally, the RAN1 carries the slice remapping information when notifying the UE to initiate handover, and the UE completes the handover procedure.
Step 511: the RAN2 sends a path switch request message to the 5G-CN network element, the path slice request message carrying slice remapping information.
Step 512: and the 5G-CN network element replies a path switching confirmation message.
Embodiment 2: and the RAN sends out remapping according to the mapping list information of the UE.
(1) After the UE is registered, the 5G-CN issues UE accepted slice (accepted nsai) information and subscription slice information corresponding to the accepted slice to the RAN, optionally including a mapping relationship between the subscription slice and a mappable slice. The mapping relationship can also be obtained by four ways of obtaining the mapping relationship in embodiment 1.
(2) When a connected UE initiates an Xn handover across registration areas,
a) if the source node obtains and stores the mapping relation between the signed slice and the mappable slice, the source node inquires the mapping relation and performs slice remapping according to the slice supported by the target node obtained when the mapping relation is established by Xn, the mapping relation between the signed slice and the mappable slice is carried when a switching request is sent, the UE applies for the slice used by the switched data connection, and the target node performs admission processing according to the mapping relation.
b) And if the source node does not obtain and store the mapping relation between the subscription section and the mappable section, the source node carries the section information used by the data connection which is applied for switching by the UE and the subscription section information corresponding to the section when the switching request is carried. If the target node stores the mapping relation between the signed slice and the target node support slice, the target node can perform remapping and admission processing according to the mapping relation. And if the target node does not store the mapping relation between the signed slice and the slice supported by the target node, the target node maps the slice which is not correspondingly supported by the target node to the configured default slice or rejects the slice.
Referring to FIG. 6, the method includes steps 601-612.
Step 601: the UE initiates a registration procedure.
Step 602: the 5G-CN network element responds to the registration confirmation.
Step 603: the 5G-CN network element initiates a UE initial context establishment procedure to the RAN1, carrying one or more of the following: and the UE receives the slice information, the signed slice information corresponding to the slice and the mapping relation between the signed slice and the mappable slice.
It is to be understood that the RAN1 is a source node, the RAN2 is a target node, and the core network elements are 5G-CNs.
Step 604: the RAN1 responds to the UE initial context setup confirmation.
It is understood that steps 603 and 604 may be procedures carrying slice information accepted by the UE in other protocol standards.
Step 605: the RAN1 sends a handover request message to the RAN2, the handover request message including one or more of: and receiving the slice information, receiving the contract slice information corresponding to the slice and the mapping relation of the mappable slices of the contract slice.
Step 606: the RAN2 queries the slice mapping information provided by the RAN1 or stored by the node according to the slices supported by the node to obtain the slices that the RAN2 does not support and can be mapped to the slices supported by the RAN2, and remaps the slices that the RAN2 does not support.
Step 607: RAN2 responds to the handover request acknowledge message and carries slice remapping information indicating that the slice used for the data connection for which handover is applied is mapped to the slice supported by RAN 2.
Step 608 to step 610: RAN1 informs the UE to initiate handover;
optionally, the RAN1 carries the slice remapping information when notifying the UE to initiate handover, and the UE completes the handover procedure.
Step 611: the RAN2 sends a path switch request message to the 5G-CN network element, the path slice request message carrying slice remapping information.
Step 612: and the 5G-CN network element replies a path switching confirmation message.
Referring to fig. 7, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a target node, and the target node 700 includes:
a first receiving module 701, configured to receive a handover request message from a source node;
a mapping module 702, configured to map a first slice to a slice supported by the target node, where the first slice is a slice used by a data connection for which the terminal applies for handover, and the target node does not support the first slice;
a first sending module 703 is configured to send a handover request acknowledgement message to the source node.
In some implementations, the mapping module 702 is further to: and mapping the first slice to the slice supported by the target node according to the mapping relation between the slice supported by the target node and the mappable slice stored in the target node.
In some embodiments, the target node 700 further comprises:
an obtaining module, configured to obtain a mapping relationship between a slice supported by the target node and a mappable slice by one or more of:
(1) agreement is agreed;
(2) OAM configuration;
(3) a neighbor node of the target node;
(4) a core network.
In some embodiments, the obtaining module is further configured to: when an Xn interface between the target node and an adjacent node is established, acquiring a mapping relation between a slice supported by the target node and a mappable slice through the adjacent node; or, when the NG interface is established or the access and mobility management function AMF configuration is updated, acquiring the mapping relationship between the slice supported by the target node and the mappable slice through the core network.
In some implementations, the mapping module 702 is further to: mapping the first slice to a slice supported by the target node according to the switching request message;
wherein the handover request message includes: mapping relation between slices supported by the target node and mappable slices;
or, the handover request message includes: a mapping relationship of the first slice to slices supported by the target node.
In some implementations, the mapping module 702 is further to: if the target node stores the mapping relationship between the slices supported by the target node and the signed slices, mapping the first slice to the slices supported by the target node according to the mapping relationship and the switching request message, wherein the switching request message comprises: the information of the first slice and the information of the contracted slice corresponding to the first slice;
alternatively, the first and second electrodes may be,
and if the target node does not store the mapping relation between the slices supported by the target node and the signed slices, mapping the first slice to a default slice configured in the target node, wherein the default slice is the slice supported by the target node.
In some embodiments, the handover request confirm message comprises: slice remapping information, the slice remapping information indicating that the first slice maps to a slice supported by the target node.
In some embodiments, the target node 700 further comprises:
a second sending module, configured to send a path switching request message to a core network element, where the path switching request message includes: the slice remapping information;
a second receiving module, configured to receive a path switch request acknowledgement message from the core network element.
The target node provided in the embodiment of the present invention may execute the method embodiment shown in fig. 3, which has similar implementation principles and technical effects, and this embodiment is not described herein again.
Referring to fig. 8, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a target node, and the target node 800 includes: a first transceiver 801 and a first processor 802;
the first transceiver 801 sends and receives data under the control of the first processor 802;
the first processor 802 reads a program in the memory to perform the following operations: receiving a handover request message from a source node; mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice; and sending a switching request confirmation message to the source node.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: and mapping the first slice to the slice supported by the target node according to the mapping relation between the slice supported by the target node and the mappable slice stored in the target node.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
(1) agreement is agreed;
(2) OAM configuration;
(3) a neighbor node of the target node;
(4) a core network.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: when an Xn interface between the target node and an adjacent node is established, acquiring a mapping relation between a slice supported by the target node and a mappable slice through the adjacent node; or, when the NG interface is established or the access and mobility management function AMF configuration is updated, acquiring the mapping relationship between the slice supported by the target node and the mappable slice through the core network.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: mapping the first slice to a slice supported by the target node according to the switching request message;
wherein the handover request message includes: mapping relation between slices supported by the target node and mappable slices;
or, the handover request message includes: a mapping relationship of the first slice to slices supported by the target node.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: if the target node stores the mapping relationship between the slices supported by the target node and the signed slices, mapping the first slice to the slices supported by the target node according to the mapping relationship and the switching request message, wherein the switching request message comprises: the information of the first slice and the information of the contracted slice corresponding to the first slice;
alternatively, the first and second electrodes may be,
and if the target node does not store the mapping relation between the slices supported by the target node and the signed slices, mapping the first slice to a default slice configured in the target node, wherein the default slice is the slice supported by the target node.
In some embodiments, the handover request confirm message comprises: slice remapping information, the slice remapping information indicating that the first slice maps to a slice supported by the target node.
In some embodiments, the first processor 802 reads the program in the memory and performs the following operations: sending a path switching request message to a core network element, wherein the path switching request message comprises: the slice remapping information; and receiving a path switching request confirmation message from the core network element.
The target node provided in the embodiment of the present invention may execute the method embodiment shown in fig. 3, which has similar implementation principles and technical effects, and this embodiment is not described herein again.
Referring to fig. 9, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a source node, and the source node 900 includes:
a third sending module 901, configured to send a handover request message to a target node;
a third receiving module 902, configured to receive a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
In some embodiments, the handover request message comprises: and mapping relation between the slices supported by the target node and the mappable slices.
In some embodiments, the source node 900 further comprises:
an obtaining module, configured to obtain a mapping relationship between a slice supported by the target node and a mappable slice by one or more of:
(1) agreement is agreed;
(2) OAM configuration;
(3) the target node, which is a neighbor node of the source node;
(4) a core network.
In some embodiments, the handover request message comprises: a mapping relationship of the first slice to slices supported by the target node.
In some embodiments, the source node 900 further comprises: and the determining module is used for determining the mapping relation between the first slice and the slice supported by the target node according to the mapping relation between the terminal signed slice and the mappable slice and the slice supported by the target node if the mapping relation between the terminal signed slice and the mappable slice is stored in the source node.
The source node provided in the embodiment of the present invention may execute the method embodiment shown in fig. 4, which has similar implementation principles and technical effects, and this embodiment is not described herein again.
Referring to fig. 10, an embodiment of the present invention further provides a radio access network node, where the radio access network node is a source node, and the source node 1000 includes: a second transceiver 1001 and a second processor 1002;
the second transceiver 1001 transmits and receives data under the control of the second processor 1002;
the second processor 1002 reads a program in the memory to perform the following operations: sending a switching request message to a target node; receiving a handover request acknowledgement message from the target node; wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
In some embodiments, the handover request message comprises: and mapping relation between the slices supported by the target node and the mappable slices.
In some embodiments, the second processor 1002 reads the program in the memory to further perform the following operations: acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
(1) agreement is agreed;
(2) OAM configuration;
(3) the target node, which is a neighbor node of the source node;
(4) a core network.
In some embodiments, the handover request message comprises: a mapping relationship of the first slice to slices supported by the target node.
In some embodiments, the second processor 1002 reads the program in the memory to further perform the following operations: and if the source node stores the mapping relation between the terminal signing slice and the mappable slice, determining the mapping relation between the first slice and the slice supported by the target node according to the mapping relation between the terminal signing slice and the mappable slice and the slice supported by the target node.
The source node provided in the embodiment of the present invention may execute the method embodiment shown in fig. 4, which has similar implementation principles and technical effects, and this embodiment is not described herein again.
Referring to fig. 11, fig. 11 is a structural diagram of a communication device applied in the embodiment of the present invention, and as shown in fig. 11, the communication device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, wherein:
in one embodiment of the present invention, the communication device 1300 further comprises: a computer program stored on the memory 1103 and executable on the processor 1101, the computer program, when executed by the processor 1301, implementing the steps in the embodiments shown in fig. 3 to 4.
In fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1101, and various circuits, represented by memory 1103, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1102 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium, it being understood that the transceiver 1102 is an optional component.
The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing operations.
The communication device provided in the embodiment of the present invention may execute the method embodiments shown in fig. 3 to fig. 4, which have similar implementation principles and technical effects, and this embodiment is not described herein again.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable hard disk, a compact disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (19)
1. A handover method is applied to a radio access network node, wherein the radio access network node is a target node, and the handover method comprises the following steps:
receiving a handover request message from a source node;
mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice;
and sending a switching request confirmation message to the source node.
2. The method of claim 1, wherein mapping the first slice to a slice supported by the target node comprises:
and mapping the first slice to the slice supported by the target node according to the mapping relation between the slice supported by the target node and the mappable slice stored in the target node.
3. The method of claim 1, further comprising:
acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
agreement is agreed;
operation, maintenance and management (OAM) configuration;
a neighbor node of the target node;
a core network.
4. The method according to claim 3, wherein the obtaining, through the target node's neighboring node, a mapping relationship between slices supported by the target node and mappable slices comprises:
when an Xn interface between the target node and an adjacent node is established, acquiring a mapping relation between a slice supported by the target node and a mappable slice through the adjacent node;
alternatively, the first and second electrodes may be,
the obtaining, by the core network, a mapping relationship between a slice supported by the target node and a mappable slice includes:
and when the NG interface is established or the access and mobility management function AMF configuration is updated, acquiring the mapping relation between the slices supported by the target node and the mappable slices through the core network.
5. The method of claim 1, wherein mapping the first slice to a slice supported by the target node comprises:
mapping the first slice to a slice supported by the target node according to the switching request message;
wherein the handover request message includes: mapping relation between slices supported by the target node and mappable slices;
or, the handover request message includes: a mapping relationship of the first slice to slices supported by the target node.
6. The method of claim 1, wherein mapping the first slice to a slice supported by the target node comprises:
if the target node stores the mapping relationship between the slices supported by the target node and the signed slices, mapping the first slice to the slices supported by the target node according to the mapping relationship and the switching request message, wherein the switching request message comprises: the information of the first slice and the information of the contracted slice corresponding to the first slice;
alternatively, the first and second electrodes may be,
and if the target node does not store the mapping relation between the slices supported by the target node and the signed slices, mapping the first slice to a default slice configured in the target node, wherein the default slice is the slice supported by the target node.
7. The method of claim 1, wherein the handover request acknowledge message comprises: slice remapping information, the slice remapping information indicating that the first slice maps to a slice supported by the target node.
8. The method of claim 7, further comprising:
sending a path switching request message to a core network element, wherein the path switching request message comprises: the slice remapping information;
and receiving a path switching request confirmation message from the core network element.
9. A switching method is applied to a wireless access network node, the wireless access network node is a source node, and the switching method is characterized by comprising the following steps:
sending a switching request message to a target node;
receiving a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
10. The method of claim 9, wherein the handover request message comprises: and mapping relation between the slices supported by the target node and the mappable slices.
11. The method of claim 10, further comprising:
acquiring the mapping relation between the slices supported by the target node and the mappable slices through one or more of the following steps:
agreement is agreed;
operation, maintenance and management (OAM) configuration;
the target node, which is a neighbor node of the source node;
a core network.
12. The method of claim 9, wherein the handover request message comprises: a mapping relationship of the first slice to slices supported by the target node.
13. The method of claim 12, further comprising:
and if the source node stores the mapping relation between the terminal signing slice and the mappable slice, determining the mapping relation between the first slice and the slice supported by the target node according to the mapping relation between the terminal signing slice and the mappable slice and the slice supported by the target node.
14. A radio access network node, the radio access network node being a target node, comprising:
a first receiving module, configured to receive a handover request message from a source node;
a mapping module, configured to map a first slice to a slice supported by the target node, where the first slice is a slice used by a data connection for which a terminal applies for handover, and the target node does not support the first slice;
a first sending module, configured to send a handover request acknowledgement message to the source node.
15. A radio access network node, the radio access network node being a target node, comprising: a first transceiver and a first processor;
the first transceiver transmits and receives data under control of the first processor;
the first processor reads a program in a memory to perform the following operations: receiving a handover request message from a source node; mapping a first slice to a slice supported by the target node, wherein the first slice is a slice used by a data connection which a terminal applies for switching, and the target node does not support the first slice; and sending a switching request confirmation message to the source node.
16. A radio access network node, the radio access network node being a source node, comprising:
a third sending module, configured to send a handover request message to a target node;
a third receiving module, configured to receive a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
17. A radio access network node, the radio access network node being a source node, comprising: a second transceiver and a second processor;
the second transceiver transmits and receives data under the control of the second processor;
the second processor reads a program in the memory to perform the following operations: sending a switching request message to a target node; receiving a handover request acknowledgement message from the target node;
wherein the handover request confirm message includes: and slice remapping information, wherein the slice remapping information indicates that a first slice is mapped to a slice supported by the target node, the first slice is a slice used by a data connection which is applied for switching by a terminal, and the target node does not support the first slice.
18. A communication device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements steps comprising the handover method according to any of claims 1 to 13.
19. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out steps comprising the handover method according to any one of claims 1 to 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010128843.5A CN113329453A (en) | 2020-02-28 | 2020-02-28 | Switching method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010128843.5A CN113329453A (en) | 2020-02-28 | 2020-02-28 | Switching method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113329453A true CN113329453A (en) | 2021-08-31 |
Family
ID=77412681
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010128843.5A Pending CN113329453A (en) | 2020-02-28 | 2020-02-28 | Switching method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113329453A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116489731A (en) * | 2023-06-21 | 2023-07-25 | 中国电信股份有限公司 | Slice information mapping method, apparatus, computer device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108366365A (en) * | 2017-01-26 | 2018-08-03 | 华为技术有限公司 | A kind of method and equipment of access Target cell |
| CN108632927A (en) * | 2017-03-24 | 2018-10-09 | 华为技术有限公司 | Mobile network's switching method and communication device |
| CN109804671A (en) * | 2016-11-04 | 2019-05-24 | 华为技术有限公司 | A kind of method for switching network, device and relevant device |
| CN110838927A (en) * | 2018-08-15 | 2020-02-25 | 中国移动通信有限公司研究院 | Slice mapping remapping method and access network element |
-
2020
- 2020-02-28 CN CN202010128843.5A patent/CN113329453A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109804671A (en) * | 2016-11-04 | 2019-05-24 | 华为技术有限公司 | A kind of method for switching network, device and relevant device |
| CN108366365A (en) * | 2017-01-26 | 2018-08-03 | 华为技术有限公司 | A kind of method and equipment of access Target cell |
| CN108632927A (en) * | 2017-03-24 | 2018-10-09 | 华为技术有限公司 | Mobile network's switching method and communication device |
| US20200022061A1 (en) * | 2017-03-24 | 2020-01-16 | Huawei Technologies Co., Ltd. | Handover Method in Mobile Network and Communications Apparatus |
| CN110838927A (en) * | 2018-08-15 | 2020-02-25 | 中国移动通信有限公司研究院 | Slice mapping remapping method and access network element |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116489731A (en) * | 2023-06-21 | 2023-07-25 | 中国电信股份有限公司 | Slice information mapping method, apparatus, computer device and storage medium |
| CN116489731B (en) * | 2023-06-21 | 2023-09-29 | 中国电信股份有限公司 | Slice information mapping method, apparatus, computer device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10911990B2 (en) | Network handover method and related device | |
| CA3042745C (en) | Inter-network change method and apparatus, and related device | |
| CN109561423B (en) | Method and device for accessing target cell | |
| KR102329156B1 (en) | Methods and devices for selecting session management features | |
| US11265768B2 (en) | EPS bearer identifier allocation method and device, SMF and PCF | |
| US9264450B2 (en) | Method of seamless policy based network discovery, selection and switching | |
| KR102394891B1 (en) | Wireless communications method and device | |
| US11228560B2 (en) | Mobility functionality for a cloud-based access system | |
| CN110972126B (en) | Path, path information processing method and device | |
| US11259344B2 (en) | Network architecture and information exchange method and apparatus | |
| CN111836319B (en) | Method and device for acquiring domain name address | |
| JP2004519179A (en) | Method for supporting handover between radio access networks | |
| CN110913439A (en) | Network element selection method and device | |
| US10219189B2 (en) | Method for policy converging, UE, and server | |
| EP3817453A1 (en) | Communication method and apparatus | |
| CN104618976A (en) | Method and device for maintaining continuity of IP addresses | |
| EP4054241A1 (en) | Network function database, mobile communication network component, method for selecting a network function and method for registering a network function | |
| ES2901967T3 (en) | Procedure for establishing a communication connection of a communication terminal via a communication network partition | |
| US20230054991A1 (en) | Method for slice information update | |
| CN113329453A (en) | Switching method and device | |
| CN113348727A (en) | Network configuration device, server and communication system | |
| JP7014600B2 (en) | UE, TWAG, and communication method | |
| CN113329452B (en) | Switching method and equipment | |
| CN113329451B (en) | Switching method and device | |
| WO2014179928A1 (en) | Flow control method and apparatus of operator sharing 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210831 |
|
| RJ01 | Rejection of invention patent application after publication |