Method, network element and device for switching service RAN (Radio Access Network) and non-service RAN

Abstract

The invention provides a method, a network element and a device for switching a service RAN (Radio Access Network) and a non-service RAN, and the method comprises the steps: a first network element maps service RAN information into non-service RAN information according to a mapping relation between the service RAN and the non-service RAN, and the non-service RAN network element carries out the switching from the service RAN to the non-service RAN according to the non-service RAN information obtained through mapping; or, the first network element maps the non-service RAN information into service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs switching from the non-service RAN to the service RAN according to the service RAN information obtained by mapping; according to the invention, the problem of switching between RAN service and non-service RAN is solved, the problem of communication interruption is avoided, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a switching method, network element and device between a service-oriented RAN and a non-service-oriented RAN. Background Art

[0002] After the Radio Access Network (RAN) is service-oriented, there will be service-oriented RAN and non-service-oriented RAN in the network.

[0003] When it is necessary to switch from a serviced RAN to a non-serviced RAN, or when it is necessary to switch from a non-serviced RAN to a serviced RAN, there is currently no solution for how to switch between the serviced RAN and the non-serviced RAN. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a method, network element and device for switching between a serviced RAN and a non-serviced RAN, so as to solve the problem that the prior art does not specify how to switch between a serviced RAN and a non-serviced RAN.

[0005] In order to solve the above problem, an embodiment of the present application provides a method for switching between a serviced RAN and a non-serviced RAN, which is applied to a first network element. The method includes:

[0006] The first network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping;

[0007] or,

[0008] The first network element maps the non-service RAN information to the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs switching from the non-service RAN to the service RAN according to the service RAN information obtained by the mapping.

[0009] The first network element is any one of the following:

[0010] NRF network element with network storage function;

[0011] Service-oriented RAN network elements;

[0012] Non-service RAN network elements;

[0013] Service-oriented access and mobility management function AMF network element;

[0014] Non-service AMF network element;

[0015] Protocol data unit session anchor PSA network element.

[0016] Wherein, when the first network element is the NRF network element or the PSA network element, the method further includes:

[0017] receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information;

[0018] A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

[0019] Wherein, when the first network element is the NRF network element or the PSA network element, the method further includes:

[0020] receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information;

[0021] A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

[0022] Wherein, in a case where the first network element is the non-service RAN network element, the method further includes:

[0023] The non-service-oriented RAN network element receives the service-oriented RAN information sent by the service-oriented RAN network element.

[0024] Wherein, in the case where the first network element is the service-oriented RAN network element, the method further includes:

[0025] The service-oriented RAN network element receives the non-service-oriented RAN information sent by the non-service-oriented RAN network element.

[0026] Wherein, when the first network element is the service-oriented AMF network element, the method further includes:

[0027] A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

[0028] Wherein, when the first network element is the non-service AMF network element, the method further includes:

[0029] A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

[0030] Wherein, when the first network element is the NRF network element, the method further includes:

[0031] receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information;

[0032] A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

[0033] Wherein, when the first network element is the NRF network element, the method further includes:

[0034] receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information;

[0035] A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

[0036] The embodiment of the present application further provides a method for switching between a service-oriented RAN and a non-service-oriented RAN, which is applied to a non-service-oriented RAN network element. The method includes:

[0037] The non-service RAN network element obtains the mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information;

[0038] The non-service RAN network element performs switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0039] The first network element is any one of the following:

[0040] NRF network element with network storage function;

[0041] Service-oriented RAN network elements;

[0042] Non-service RAN network elements;

[0043] Service-oriented access and mobility management function AMF network element;

[0044] Non-service AMF network element;

[0045] Protocol data unit session anchor PSA network element.

[0046] The embodiment of the present application further provides a method for switching between a service-oriented RAN and a non-service-oriented RAN, which is applied to a service-oriented RAN network element. The method includes:

[0047] The service-oriented RAN network element obtains the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0048] The service-oriented RAN network element performs switching from the non-service-oriented RAN to the service-oriented RAN according to the service-oriented RAN information obtained by mapping.

[0049] The first network element is any one of the following:

[0050] NRF network element with network storage function;

[0051] Service-oriented RAN network elements;

[0052] Non-service RAN network elements;

[0053] Service-oriented access and mobility management function AMF network element;

[0054] Non-service AMF network element;

[0055] Protocol data unit session anchor PSA network element.

[0056] The embodiment of the present application further provides a first network element, including a memory, a transceiver, and a processor:

[0057] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0058] According to the mapping relationship between the serviced RAN and the non-serviced RAN, the serviced RAN information is mapped into the non-serviced RAN information, and the non-serviced RAN network element performs the handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping;

[0059] or,

[0060] According to the mapping relationship between the non-service RAN and the service RAN, the non-service RAN information is mapped to the service RAN information, and the service RAN network element performs the switching from the non-service RAN to the service RAN according to the mapped service RAN information.

[0061] The first network element is any one of the following:

[0062] NRF network element with network storage function;

[0063] Service-oriented RAN network elements;

[0064] Non-service RAN network elements;

[0065] Service-oriented access and mobility management function AMF network element;

[0066] Non-service AMF network element;

[0067] Protocol data unit session anchor PSA network element.

[0068] Wherein, when the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0069] receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information;

[0070] A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

[0071] Wherein, when the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0072] receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information;

[0073] A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

[0074] Wherein, when the first network element is the non-service RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0075] Receive service-oriented RAN information sent by the service-oriented RAN network element.

[0076] Wherein, when the first network element is the service-oriented RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0077] Receive non-serving RAN information sent by the non-serving RAN network element.

[0078] Wherein, when the first network element is the service-oriented AMF network element, the processor is further used to read the computer program in the memory and perform the following operations:

[0079] A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

[0080] Wherein, when the first network element is the non-service AMF network element, the processor is further used to read the computer program in the memory and perform the following operations:

[0081] A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

[0082] Wherein, when the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0083] receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information;

[0084] A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

[0085] Wherein, when the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0086] receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information;

[0087] A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

[0088] The embodiment of the present application also provides a non-service RAN network element, including a memory, a transceiver, and a processor:

[0089] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0090] Acquire the mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information;

[0091] The switching from the serviced RAN to the non-serviced RAN is performed according to the mapped non-serviced RAN information.

[0092] The first network element is any one of the following:

[0093] NRF network element with network storage function;

[0094] Service-oriented RAN network elements;

[0095] Non-service RAN network elements;

[0096] Service-oriented access and mobility management function AMF network element;

[0097] Non-service AMF network element;

[0098] Protocol data unit session anchor PSA network element.

[0099] The embodiment of the present application also provides a service-oriented RAN network element, including a memory, a transceiver, and a processor:

[0100] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0101] Acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0102] The switching from the non-service RAN to the service RAN is performed according to the service RAN information obtained by mapping.

[0103] The first network element is any one of the following:

[0104] NRF network element with network storage function;

[0105] Service-oriented RAN network elements;

[0106] Non-service RAN network elements;

[0107] Service-oriented access and mobility management function AMF network element;

[0108] Non-service AMF network element;

[0109] Protocol data unit session anchor PSA network element.

[0110] The embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0111] a first mapping unit, configured to map the serviced RAN information into the non-serviced RAN information according to a mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs a handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping;

[0112] and / or,

[0113] The second mapping unit is configured to map the non-service RAN information into the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs a handover from the non-service RAN to the service RAN according to the service RAN information obtained by the mapping.

[0114] The embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0115] A first acquisition unit is used to acquire the mapped non-service RAN information; wherein the service RAN information is mapped to the non-service RAN information by the first network element;

[0116] The first switching unit is configured to perform switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0117] The embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0118] A second acquisition unit is used to acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0119] The second switching unit is configured to perform switching from the non-service RAN to the service RAN according to the service RAN information obtained by mapping.

[0120] An embodiment of the present application further provides a processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method as described above.

[0121] The above technical solution of the present application has at least the following beneficial effects:

[0122] In the switching method, network element, and device of the serviced RAN and non-serviced RAN in the embodiments of the present application, the mapping relationship between the serviced RAN and the non-serviced RAN is stored at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the switching between the serviced RAN and the non-serviced RAN is performed by the non-serviced RAN network element or the serviced RAN network element, which solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0123] Figure 1 A block diagram showing a wireless communication system to which the embodiments of the present application can be applied;

[0124] Figure 2 One of the flowcharts showing the method for switching between a service-oriented RAN and a non-service-oriented RAN provided in an embodiment of the present application;

[0125] Figure 3 A schematic diagram showing the principle of Example 1 provided in an embodiment of the present application;

[0126] Figure 4 A schematic diagram showing the principle of Example 2 provided in an embodiment of the present application;

[0127] Figure 5 A schematic diagram showing the principle of Example 3 provided in an embodiment of the present application;

[0128] Figure 6 A schematic diagram showing the principle of Example 4 provided in an embodiment of the present application;

[0129] Figure 7 A schematic diagram showing the principle of Example 5 provided in an embodiment of the present application;

[0130] Figure 8 A schematic diagram showing the principle of Example 6 provided in an embodiment of the present application;

[0131] Fig. 9 A schematic diagram showing the principle of Example 7 provided in the embodiments of the present application;

[0132] Fig.10 A schematic diagram showing the principle of Example 8 provided in an embodiment of the present application;

[0133] Fig.11 A schematic diagram showing the principle of Example 9 provided in an embodiment of the present application;

[0134] Fig.12 A schematic diagram showing the principle of Example 10 provided in an embodiment of the present application;

[0135] Fig.13 A schematic diagram showing the principle of Example 11 provided in an embodiment of the present application;

[0136] Fig.14 A second flowchart showing the method for switching between a service-oriented RAN and a non-service-oriented RAN provided in an embodiment of the present application;

[0137] Fig.15 A flowchart showing the steps of the method for switching between a service-oriented RAN and a non-service-oriented RAN provided in an embodiment of the present application;

[0138] Fig.16 A schematic diagram showing the structure of a first network element provided in an embodiment of the present application;

[0139] Fig.17 A schematic diagram showing the structure of a non-service RAN network element provided in an embodiment of the present application;

[0140] Fig.18 A schematic diagram showing the structure of a service-oriented RAN network element provided in an embodiment of the present application;

[0141] Fig.19 One of the structural schematic diagrams showing the switching device between the service-oriented RAN and the non-service-oriented RAN provided in the embodiment of the present application;

[0142] Fig. 20 A second structural diagram showing a switching device between a service-oriented RAN and a non-service-oriented RAN provided in an embodiment of the present application;

[0143] Fig.21 The third structural diagram of the switching device between the service-oriented RAN and the non-service-oriented RAN provided in the embodiment of the present application. DETAILED DESCRIPTION

[0144] In order to make the technical problems, technical solutions and advantages to be solved by the present application clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0145] Figure 1 A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal device 101 and a network side device 102. Among them, the terminal device 101 may also be referred to as a terminal or a user terminal (User Equipment, UE). It should be noted that the specific type of the terminal 101 is not limited in the embodiment of the present application. The network side device 102 can be a base station or a core network. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0146] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0147] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0148] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0149] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0150] The terminal device involved in the embodiments of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the names of terminal devices may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device may communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0151] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0152] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0153] like Figure 2 As shown, an embodiment of the present application provides a method for switching between a service-oriented RAN and a non-service-oriented RAN, which is applied to a first network element, and the method includes:

[0154] Step 201: The first network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs a handover from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information;

[0155] or,

[0156] Step 202: The first network element maps the non-service RAN information to the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs a handover from the non-service RAN to the service RAN according to the mapped service RAN information.

[0157] In the embodiment of the present application, the mapping relationship between the service-oriented RAN and the non-service-oriented RAN, or the mapping relationship between the non-service-oriented RAN and the service-oriented RAN, is stored in the first network element.

[0158] In one implementation, when the serviced RAN is to be switched to the non-serviced RAN, the first network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and then the non-serviced RAN network element parses the non-serviced RAN information to complete the switch from the serviced RAN to the non-serviced RAN.

[0159] In another implementation, when the non-service RAN is to be switched to the service RAN, the first network element maps the non-service RAN information to the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and then the service RAN network element parses the service RAN information to complete the switching from the non-service RAN to the service RAN.

[0160] Optionally, when switching from a non-service RAN to a service RAN, the mapped service RAN information is the context information of the terminal, session information, information between the XN interfaces, etc. That is, the RAN service can be only the N2 interface service, or only the XN interface service, or both the N2 interface and the XN interface service, which is not specifically limited here. Among them, the XN interface refers to the interface between RAN nodes; the N2 interface refers to the interface between the gNB (base station) and the AMF.

[0161] In at least one embodiment of the present application, the first network element is any one of the following:

[0162] Network Repository Function (NRF) network element;

[0163] Service-oriented Radio Access Network (RAN) network elements;

[0164] Non-service RAN network elements;

[0165] Service-based access and mobility management function (AMF) network element;

[0166] Non-service AMF network element;

[0167] Protocol Data Unit Session Anchor (PSA) network element.

[0168] As an optional embodiment, when the first network element is the NRF network element or the PSA network element, the method further includes:

[0169] receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information;

[0170] A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

[0171] In the above embodiment, after the serving RAN network element receives the first mapping query response and determines the mapped non-serving RAN information, it sends the mapped non-serving RAN information to the non-serving RAN network element, and the non-serving RAN network element performs switching from the serving RAN to the non-serving RAN according to the mapped non-serving RAN information.

[0172] As another optional embodiment, when the first network element is the NRF network element or the PSA network element, the method further includes:

[0173] receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information;

[0174] A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

[0175] In the above embodiment, after the non-service RAN network element receives the second mapping query response and determines the mapped service RAN information, it sends the mapped service RAN information to the service RAN network element, and the service RAN network element performs switching from the non-service RAN to the service RAN according to the mapped service RAN information.

[0176] Example 1: Figure 3 As shown in the figure, under the network element fusion, there is a switch between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) without user plane function (UPF) redistribution. The first network element is the NRF network element, and the mapping is performed at the NRF network element.

[0177] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting to map FRAN information to RAN information.

[0178] Step 2: After NRF maps the FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN.

[0179] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0180] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0181] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0182] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF. SMF initiates PDU session modification based on the PDU session information to be switched and FRAN's auxiliary RAT usage data, and sends RAN's AN (access node) tunnel information to UPF+FUPF, while requiring UPF+FUPF to allocate CN (core node) tunnel information.

[0183] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0184] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0185] Step 9: Start the registration process.

[0186] It should be noted that in the embodiment of the present application, FRAN represents a serviced RAN, RAN represents a non-serviced RAN, AMF+FAMF represents a fused AMF network element after service and non-service, SMF+FSMF represents a fused SMF network element after service and non-service, and UPF+FUPF represents a fused UPF network element after service and non-service.

[0187] Example 2: Figure 4 As shown in the figure, under the network element fusion, the switching between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) without UPF redistribution, the first network element is the PSA (UPF+FUPF) network element, and the mapping is performed at the PSA network element

[0188] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to map FRAN information to RAN information;

[0189] Step 2: After UPF+FUPF maps FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN. Different sessions may use different PSAs. If there are multiple sessions, there will be multiple PSAs. When there are multiple PSAs, the mapping relationship can be placed on all PSAs or on the first PSA when the session is established. There is no specific limitation here.

[0190] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0191] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0192] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0193] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF. SMF initiates PDU session modification based on the PDU session information to be switched and FRAN's auxiliary RAT usage data, and sends RAN's AN (access node) tunnel information to UPF+FUPF, while requiring UPF+FUPF to allocate CN (core node) tunnel information.

[0194] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0195] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0196] Step 9: Start the registration process.

[0197] Example 3: Figure 5 As shown, under the network element fusion, the switching between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) with the intermediate UPF (I-UPF) inserted, the first network element is the NRF network element, and the mapping is performed at the NRF network element

[0198] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting to map FRAN information to RAN information.

[0199] Step 2: After NRF maps the FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN.

[0200] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0201] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0202] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0203] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0204] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0205] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0206] Step 9: Start the registration process.

[0207] Example 4: Figure 6 As shown, under the network element fusion, the switching between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) with the intermediate UPF (I-UPF) inserted, the first network element is the PSA (UPF+FUPF) network element, and the mapping is performed at the PSA network element

[0208] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to map FRAN information to RAN information;

[0209] Step 2: After UPF+FUPF maps FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN. Different sessions may use different PSAs. If there are multiple sessions, there will be multiple PSAs. When there are multiple PSAs, the mapping relationship can be placed on all PSAs or on the first PSA when the session is established. There is no specific limitation here.

[0210] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0211] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0212] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0213] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0214] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0215] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0216] Step 9: Start the registration process.

[0217] Example 5: Figure 7 As shown in the figure, under the network element fusion, the switching between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) with intermediate UPF redistribution, the first network element is the NRF network element, and the mapping is performed at the NRF network element

[0218] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to NRF, requesting to map FRAN information to RAN information.

[0219] Step 2: After NRF maps the FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN.

[0220] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0221] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0222] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0223] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0224] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0225] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0226] Step 9: Start the registration process.

[0227] Step 10: SMF+FSMF starts the source S-UPF+S-FUPF release process by sending N4 session release request (release reason).

[0228] Example 6: Figure 8 As shown in the figure, under the network element fusion, the switching between the service-oriented RAN (FRAN for short) and the non-service-oriented RAN (RAN for short) with intermediate UPF redistribution, the first network element is the PSA (UPF+FUPF) network element, and the mapping is performed at the PSA network element

[0229] Step 1: When FRAN switches to RAN, FRAN calls an information mapping query request to UPF+FUPF to map FRAN information to RAN information;

[0230] Step 2: After UPF+FUPF maps FRAN information into RAN information, it sends a mapping query response to FRAN and sends the mapped RAN information to FRAN. Different sessions may use different PSAs. If there are multiple sessions, there will be multiple PSAs. When there are multiple PSAs, the mapping relationship can be placed on all PSAs or on the first PSA when the session is established. There is no specific limitation here.

[0231] Step 3: FRAN sends the data mapped from service-oriented to non-service-oriented to RAN. In the prior art, data is directly transmitted without mapping the data.

[0232] Step 4: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0233] Step 5: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0234] Step 6: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0235] Step 7: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0236] Step 8: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0237] Step 9: Start the registration process.

[0238] Step 10: SMF+FSMF starts the source S-UPF+S-FUPF release process by sending N4 session release request (release reason).

[0239] As an optional embodiment, when the first network element is the non-service RAN network element, the method further includes:

[0240] The non-service-oriented RAN network element receives the service-oriented RAN information sent by the service-oriented RAN network element.

[0241] In the above embodiment, the non-service RAN network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the received serviced RAN information and the non-serviced RAN; and performs switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0242] As another optional embodiment, when the first network element is the service-oriented RAN network element, the method further includes:

[0243] The service-oriented RAN network element receives the non-service-oriented RAN information sent by the non-service-oriented RAN network element.

[0244] In the above embodiment, the service-oriented RAN network element maps the non-service-oriented RAN information to the service-oriented RAN information according to the mapping relationship between the received non-service-oriented RAN information and the non-service-oriented RAN and performs switching from the non-service-oriented RAN to the service-oriented RAN according to the mapped service-oriented RAN information.

[0245] Example 7: Fig. 9 As shown in the figure, under the network element fusion, the switching between FRAN and RAN without UPF redistribution, the first network element is a non-service RAN network element, and the mapping is performed at the non-service RAN network element

[0246] Step 1: FRAN sends the service-oriented RAN data to RAN;

[0247] Step 2: RAN converts the data of the service-oriented RAN into the data of the non-service-oriented RAN according to the mapping relationship.

[0248] Step 3: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0249] Step 4: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0250] Step 5: FAMF+AMF sends the PDU session information to be switched to SMF. SMF initiates PDU session modification based on the PDU session information to be switched and FRAN's auxiliary RAT usage data, and sends RAN's AN (access node) tunnel information to UPF+FUPF, while requiring UPF+FUPF to allocate CN (core node) tunnel information.

[0251] Step 6: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0252] Step 7: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0253] Step 8: Start the registration process.

[0254] Example 8: Fig.10 As shown in the figure, under the network element fusion, the switching between the serviced RAN and the non-serviced RAN is inserted in the middle UPF. The first network element is the non-serviced RAN network element, and the mapping is performed at the non-serviced RAN network element.

[0255] Step 1: FRAN sends the service-oriented RAN data to RAN;

[0256] Step 2: RAN converts the data of the service-oriented RAN into the data of the non-service-oriented RAN according to the mapping relationship.

[0257] Step 3: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0258] Step 4: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0259] Step 5: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0260] Step 6: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0261] Step 7: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0262] Step 8: Start the registration process.

[0263] Example 9: Fig.11 As shown, under the network element fusion, the switching between the service RAN (FRAN for short) and the non-service RAN (RAN for short) with intermediate UPF redistribution, the first network element is the non-service RAN network element, and the mapping is performed at the non-service RAN network element

[0264] Step 1: FRAN sends the service-oriented RAN data to RAN;

[0265] Step 2: RAN converts the data of the service-oriented RAN into the data of the non-service-oriented RAN according to the mapping relationship.

[0266] Step 3: If Secondary RAT usage reporting has been configured, the source NG-RAN node during the handover execution phase may provide a RAN usage data report (Secondary RAT usage data, Handover Flag) to the AMF.

[0267] Step 4: Path switching request (PDU session list for session management information switching, PDU session list rejected for each PDU session, including session management SM information of rejection reason, UE location information).

[0268] Step 5: FAMF+AMF sends the PDU session information to be switched to SMF, and SMF selects an I-UPF between RAN and the original PSA. Since RAN and PSA cannot establish a user plane path, an I-UPF is inserted to complete the user plane path establishment.

[0269] Step 6: Path switching request confirmation (switched PDU session information, PDU session failure, CN tunnel information).

[0270] Step 7: RAN confirms the handover is successful by sending a Release Resources message to the source FRAN. It then triggers the release of resources with the FRAN.

[0271] Step 8: Start the registration process.

[0272] Step 9: SMF+FSMF starts the source S-UPF+S-FUPF release process by sending N4 session release request (release reason).

[0273] As an optional embodiment, when the first network element is the service-oriented AMF network element, the method further includes:

[0274] A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

[0275] In the above embodiment, the serviced AMF network element maps the serviced RAN information to the non-serviced RAN information according to the first switching request and the mapping relationship between the serviced RAN and the non-serviced RAN; and the serviced AMF network element transmits the mapped non-serviced RAN information to the non-serviced RAN network element, and the non-serviced RAN network element performs switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0276] In other words, when switching between FRAN and RAN under non-network element fusion, when FRAN determines to switch to RAN, after S-AMF receives the data sent by FAMF, S-AMF parses the FRAN information into RAN according to the mapping relationship configured locally.

[0277] As another optional embodiment, when the first network element is the non-serviced AMF network element, the method further includes:

[0278] A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

[0279] In the above embodiment, the non-serviced AMF network element maps the non-serviced RAN information to the serviced RAN information according to the second switching request and the mapping relationship between the non-serviced RAN and the serviced RAN; and the non-serviced AMF network element transmits the mapped serviced RAN information to the serviced RAN network element, and the serviced RAN network element performs switching from the non-serviced RAN to the serviced RAN according to the mapped serviced RAN information.

[0280] Example 10: Fig.12 As shown in the figure, the switching between FRAN and RAN under non-network element fusion, the first network element is the source AMF (abbreviated as S-AMF), and the mapping is done at the S-AMF

[0281] A PDU session has been established under the serviced RAN.

[0282] Step 1: FRAN initiates handover start;

[0283] Step 2: FRAN initiates a switching request to FAMF, carrying the target ID, source-to-target transparent container, and system switching instructions.

[0284] Step 3: FAMF sends a handover request to S-AMF, and S-AMF can store the last used serviced PLMN ID in the UE context. The initial AMF converts the received serviced MM context into a non-serviced MM context. This includes converting the serviced security context into a mapped non-serviced security context. The FAMF UE context includes IMSI, FAMF identity, UE security context, UE network capabilities and serviced bearer context. The FAMF bearer context includes the IP address and FQDN of the FSMF+SMF for each serviced connection, and the IP address and CN tunnel information at the FUPF+UPF for each serviced bearer. S-RAN selects a T-AMF that can serve the mobile UE. The specific selection method can be queried through the NRF or according to the original local configuration.

[0285] Step 4: S-AMF calls the Nsmf_PDUSession_UpdateSMContext (PDU Session_Create SM Context) request to SMF, carrying the main information including UE service connection, S-AMF ID, direct forwarding flag, target ID) and indicating the switching preparation indication (to avoid switching the UP path)).

[0286] Step 5: SMF may send an N4 session modification to UPF to establish a CN tunnel for the PDU session.

[0287] Step 6: SMF sends Nsmf_PDUSession_CreateSMContext (PDU Session_Create SM Context) response (PDU Session ID, S-NSSAI, N2 SM information (PDU Session ID, S-NSSAI, QFI(s)), QoS profile, Serviced Bearer Setting List, Mapping between FBI(s) and QFI, CN Tunnel Information, Reason Code)) to the initial AMF to S-AMF.

[0288] Step 7: S-AMF calls Namf_Communication_CreateUEContext (Create UE context) request to T-AMF, and the main information carried includes target ID, source to target transparent container, UE context information, tracking requirements, PDU session ID list, and corresponding SMF information and corresponding S-NSSAI (PCF ID and DNN).

[0289] Step 8: T-AMF to T-RAN: Handover Request (Source to Target Transparent Container, N2 MM Information, N2 SM Information List, Tracking Request). If the subscription information includes the tracking requirement, the target AMF provides the tracking requirement to the target RAN in the handover request.

[0290] Step 9: T-RAN to T-AMF: Handover Request Acknowledgement (target to source transparent container, PDU session list N2 SM information to be switched for each PDU session, PDU session list failed to set N2 SM information for each PDU session containing the reason for failure).

[0291] Step 10: AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM Response received from T-RAN in step 10).

[0292] Step 11: SMF may send an N4 session modification to UPF to establish a CN tunnel for the PDU session.

[0293] Step 12: SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext (PDU session_update SM context) response (N2 SM information).

[0294] Step 13: T-AMF to S-AMF: Namf_Communication_CreateUEContext (Create UE context) response (S-AMF sends the N2 information required for the handover command to S-RAN, including the target to source transparent container, PDU session cannot be set list, N2 SM information (N3 DL forwarding information, PCF ID)).

[0295] Step 14: T-AMF sends a reallocation response to FAMF, which mainly carries the reason, target to source transparent container, CN tunnel information for data forwarding, service-oriented bearer establishment list, target AMF tunnel endpoint identifier for the control plane, address and TEID).

[0296] As an optional embodiment, when the first network element is the NRF network element, the method further includes:

[0297] receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information;

[0298] A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

[0299] In the above embodiment, after the non-service AMF network element receives the third mapping query response, it sends the mapped non-service RAN information to the non-service RAN network element, and the non-service RAN network element performs switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0300] In other words, in the case of switching between FRAN and RAN without network element fusion, when FRAN determines to switch to RAN, S-AMF queries NRF for the mapping relationship between the information between FRAN and RAN, and then parses the FRAN information into RAN.

[0301] As yet another optional embodiment, when the first network element is the NRF network element, the method further includes:

[0302] receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information;

[0303] A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

[0304] In the above embodiment, after receiving the fourth mapping query response, the service-oriented AMF network element sends the mapped service-oriented RAN information to the service-oriented RAN network element, and the service-oriented RAN network element performs switching from the non-service-oriented RAN to the service-oriented RAN according to the mapped service-oriented RAN information.

[0305] Example 11: Fig.13 As shown in the figure, the switching between FRAN and RAN under non-network element fusion, the first network element is the NRF network element, and the mapping is performed at the NRF network element

[0306] A PDU session has been established under the serviced RAN.

[0307] Step 1: FRAN initiates handover start;

[0308] Step 2: FRAN initiates a switching request to FAMF, carrying the target ID, source-to-target transparent container, and system switching instructions.

[0309] Step 3: FAMF sends a handover request to S-AMF, and S-AMF can store the last used serviced PLMN ID in the UE context. The initial AMF converts the received serviced MM context into a non-serviced MM context. This includes converting the serviced security context into a mapped non-serviced security context. The FAMF UE context includes IMSI, FAMF identity, UE security context, UE network capabilities and serviced bearer context. The FAMF bearer context includes the IP address and FQDN of the FSMF+SMF for each serviced connection, and the IP address and CN tunnel information at the FUPF+UPF for each serviced bearer. S-RAN selects a T-AMF that can serve the mobile UE. The specific selection method can be queried through the NRF or according to the original local configuration.

[0310] Step 4: S-AMF sends a NF query request to NRF, queries the mapping relationship in NRF according to the ID of FAMF, and converts the service information sent by FAMF into that of AMF.

[0311] Step 5: S-AMF calls the Nsmf_PDUSession_UpdateSMContext (PDU Session_Create SM Context) request to SMF, carrying the main information including UE service connection, S-AMF ID, direct forwarding flag, target ID) and indicating the switching preparation indication (to avoid switching the UP path)).

[0312] Step 6: SMF may send an N4 session modification to UPF to establish a CN tunnel for the PDU session.

[0313] Step 7: SMF sends Nsmf_PDUSession_CreateSMContext (PDU Session_Create SM Context) response (PDU Session ID, S-NSSAI, N2 SM information (PDU Session ID, S-NSSAI, QFI(s)), QoS profile, Serviced Bearer Setting List, Mapping between FBI(s) and QFI, CN Tunnel Information, Reason Code)) to the initial AMF to S-AMF.

[0314] Step 8: S-AMF calls Namf_Communication_CreateUEContext (Create UE context) request to T-AMF, and the main information carried includes target ID, source to target transparent container, UE context information, tracking requirements, PDU session ID list, and corresponding SMF information and corresponding S-NSSAI (PCF ID and DNN).

[0315] Step 9: T-AMF to T-RAN: Handover Request (Source to Target Transparent Container, N2 MM Information, N2 SM Information List, Tracking Request). If the subscription information includes the tracking requirement, the target AMF provides the tracking requirement to the target RAN in the handover request.

[0316] Step 10: T-RAN to T-AMF: Handover Request Acknowledgement (target to source transparent container, PDU session list N2 SM information to be switched for each PDU session, PDU session list failed to set N2 SM information for each PDU session containing the reason for failure).

[0317] Step 12: AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM Response received from T-RAN in step 10).

[0318] Step 12: SMF may send an N4 session modification to UPF to establish a CN tunnel for the PDU session.

[0319] Step 13: SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext (PDU session_update SM context) response (N2 SM information).

[0320] Step 14: T-AMF to S-AMF: Namf_Communication_CreateUEContext (Create UE context) response (S-AMF sends the N2 information required for the handover command to S-RAN, including the target to source transparent container, PDU session cannot be set list, N2 SM information (N3 DL forwarding information, PCF ID)).

[0321] Step 15: T-AMF sends a reallocation response to FAMF, which mainly carries the reason, target to source transparent container, CN tunnel information for data forwarding, service-oriented bearer establishment list, target AMF tunnel endpoint identifier for the control plane, address and TEID).

[0322] In summary, the embodiment of the present application stores the mapping relationship between the serviced RAN and the non-serviced RAN at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0323] like Fig.14 As shown, the embodiment of the present application also provides a method for switching between a service-oriented RAN and a non-service-oriented RAN, which is applied to a non-service-oriented RAN network element, and the method includes:

[0324] Step 1401: The non-service RAN network element obtains mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information;

[0325] Step 1402: The non-service RAN network element performs a handover from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0326] In the embodiment of the present application, the mapping relationship between the service-oriented RAN and the non-service-oriented RAN is stored in the first network element.

[0327] In one implementation, when the serviced RAN is to be switched to the non-serviced RAN, the first network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and then the non-serviced RAN network element parses the non-serviced RAN information to complete the switch from the serviced RAN to the non-serviced RAN.

[0328] In at least one embodiment of the present application, the first network element is any one of the following:

[0329] NRF network element with network storage function;

[0330] Service-oriented RAN network elements;

[0331] Non-service RAN network elements;

[0332] Service-oriented access and mobility management function AMF network element;

[0333] Non-service AMF network element;

[0334] Protocol data unit session anchor PSA network element.

[0335] In summary, the embodiment of the present application stores the mapping relationship between the serviced RAN and the non-serviced RAN at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0336] like Fig.15 As shown, the embodiment of the present application also provides a method for switching between a service-oriented RAN and a non-service-oriented RAN, which is applied to a service-oriented RAN network element, and the method includes:

[0337] Step 1501: The service-oriented RAN network element obtains the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0338] Step 1502: The service-oriented RAN network element performs a handover from the non-service-oriented RAN to the service-oriented RAN according to the service-oriented RAN information obtained through mapping.

[0339] In the embodiment of the present application, the mapping relationship between the non-service RAN and the service RAN is stored in the first network element.

[0340] In one implementation, when the non-serviced RAN is to be switched to the serviced RAN, the first network element maps the non-serviced RAN information to the serviced RAN information according to the mapping relationship between the non-serviced RAN and the serviced RAN, and then the serviced RAN network element parses the serviced RAN information to complete the switch from the non-serviced RAN to the serviced RAN.

[0341] Optionally, when switching from a non-service RAN to a service RAN, the mapped service RAN information is the context information of the terminal, session information, information between the XN interfaces, etc. That is, the RAN service can be only the N2 interface service, or only the XN interface service, or both the N2 interface and the XN interface service, which is not specifically limited here. Among them, the XN interface refers to the interface between RAN nodes; the N2 interface refers to the interface between the gNB (base station) and the AMF.

[0342] In at least one embodiment of the present application, the first network element is any one of the following:

[0343] NRF network element with network storage function;

[0344] Service-oriented RAN network elements;

[0345] Non-service RAN network elements;

[0346] Service-oriented access and mobility management function AMF network element;

[0347] Non-service AMF network element;

[0348] Protocol data unit session anchor PSA network element.

[0349] In summary, the embodiment of the present application stores the mapping relationship between the serviced RAN and the non-serviced RAN at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, solves the switching problem between the serviced RAN and the non-serviced RAN, avoids the problem of communication interruption, and improves user experience.

[0350] like Fig.16 As shown, the embodiment of the present application further provides a first network element, including a memory 1620, a transceiver 1610, and a processor 1600:

[0351] The memory 1620 is used to store computer programs; the transceiver 1610 is used to send and receive data under the control of the processor 1600; the processor 1600 is used to read the computer program in the memory 1620 and perform the following operations:

[0352] According to the mapping relationship between the serviced RAN and the non-serviced RAN, the serviced RAN information is mapped into the non-serviced RAN information, and the non-serviced RAN network element performs the handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping;

[0353] or,

[0354] According to the mapping relationship between the non-service RAN and the service RAN, the non-service RAN information is mapped to the service RAN information, and the service RAN network element performs the switching from the non-service RAN to the service RAN according to the mapped service RAN information.

[0355] As an optional embodiment, the first network element is any one of the following:

[0356] NRF network element with network storage function;

[0357] Service-oriented RAN network elements;

[0358] Non-service RAN network elements;

[0359] Service-oriented access and mobility management function AMF network element;

[0360] Non-service AMF network element;

[0361] Protocol data unit session anchor PSA network element.

[0362] As an optional embodiment, when the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0363] receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information;

[0364] A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

[0365] As an optional embodiment, when the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0366] receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information;

[0367] A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

[0368] As an optional embodiment, when the first network element is the non-service RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0369] Receive service-oriented RAN information sent by the service-oriented RAN network element.

[0370] As an optional embodiment, when the first network element is the service-oriented RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0371] Receive non-serving RAN information sent by the non-serving RAN network element.

[0372] As an optional embodiment, when the first network element is the service-oriented AMF network element, the processor is further used to read the computer program in the memory and perform the following operations:

[0373] A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

[0374] As an optional embodiment, when the first network element is the non-service AMF network element, the processor is further used to read the computer program in the memory and perform the following operations:

[0375] A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

[0376] As an optional embodiment, when the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0377] receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information;

[0378] A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

[0379] As an optional embodiment, when the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations:

[0380] receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information;

[0381] A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

[0382] Among them, Fig.16 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1600 and various circuits of memory represented by memory 1620 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1610 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 1600 is responsible for managing the bus architecture and general processing, and the memory 1620 may store data used by the processor 1600 when performing operations.

[0383] The processor 1600 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0384] In the embodiment of the present application, a mapping relationship between the serviced RAN and the non-serviced RAN is stored at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, thereby solving the switching problem between the serviced RAN and the non-serviced RAN, avoiding the problem of communication interruption, and improving user experience.

[0385] It should be noted here that the above-mentioned first network element provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0386] like Fig.17 As shown, the embodiment of the present application further provides a non-service RAN network element, including a memory 1720, a transceiver 1710, and a processor 1700:

[0387] The memory 1720 is used to store computer programs; the transceiver 1710 is used to send and receive data under the control of the processor 1700; the processor 1700 is used to read the computer program in the memory 1720 and perform the following operations:

[0388] Acquire the mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information;

[0389] The switching from the serviced RAN to the non-serviced RAN is performed according to the mapped non-serviced RAN information.

[0390] As an optional embodiment, the first network element is any one of the following:

[0391] NRF network element with network storage function;

[0392] Service-oriented RAN network elements;

[0393] Non-service RAN network elements;

[0394] Service-oriented access and mobility management function AMF network element;

[0395] Non-service AMF network element;

[0396] Protocol data unit session anchor PSA network element.

[0397] Among them, Fig.17 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1700 and various circuits of memory represented by memory 1720 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1710 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 1700 is responsible for managing the bus architecture and general processing, and the memory 1720 may store data used by the processor 1700 when performing operations.

[0398] The processor 1700 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0399] In the embodiment of the present application, a mapping relationship between the serviced RAN and the non-serviced RAN is stored at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, thereby solving the switching problem between the serviced RAN and the non-serviced RAN, avoiding the problem of communication interruption, and improving user experience.

[0400] It should be noted here that the above-mentioned non-service RAN network element provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0401] like Fig.18 As shown, the embodiment of the present application further provides a service-oriented RAN network element, including a memory 1820, a transceiver 1810, and a processor 1800:

[0402] The memory 1820 is used to store computer programs; the transceiver 1810 is used to send and receive data under the control of the processor 1800; the processor 1800 is used to read the computer program in the memory 1820 and perform the following operations:

[0403] Acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0404] The switching from the non-service RAN to the service RAN is performed according to the service RAN information obtained by mapping.

[0405] As an optional embodiment, the first network element is any one of the following:

[0406] NRF network element with network storage function;

[0407] Service-oriented RAN network elements;

[0408] Non-service RAN network elements;

[0409] Service-oriented access and mobility management function AMF network element;

[0410] Non-service AMF network element;

[0411] Protocol data unit session anchor PSA network element.

[0412] Among them, Fig.18 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1800 and memory represented by memory 1820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1810 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor x10 is responsible for managing the bus architecture and general processing, and the memory 1820 may store data used by the processor 1800 when performing operations.

[0413] The processor 1800 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0414] In the embodiment of the present application, a mapping relationship between the serviced RAN and the non-serviced RAN is stored at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, thereby solving the switching problem between the serviced RAN and the non-serviced RAN, avoiding the problem of communication interruption, and improving user experience.

[0415] It should be noted here that the above-mentioned service-oriented RAN network element provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0416] like Fig.19 As shown, the embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0417] The first mapping unit 1901 is configured to map the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs a handover from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information;

[0418] and / or,

[0419] The second mapping unit 1902 is configured to map the non-service RAN information into the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs the handover from the non-service RAN to the service RAN according to the service RAN information obtained by the mapping.

[0420] As an optional embodiment, the first network element is any one of the following:

[0421] NRF network element with network storage function;

[0422] Service-oriented RAN network elements;

[0423] Non-service RAN network elements;

[0424] Service-oriented access and mobility management function AMF network element;

[0425] Non-service AMF network element;

[0426] Protocol data unit session anchor PSA network element.

[0427] As an optional embodiment, when the first network element is the NRF network element or the PSA network element, the device further includes:

[0428] A first receiving unit, configured to receive a first mapping query request sent by a service-oriented RAN network element, wherein the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information;

[0429] The first sending unit is configured to send a first mapping query response to a serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

[0430] As an optional embodiment, when the first network element is the NRF network element or the PSA network element, the device further includes:

[0431] A second receiving unit, configured to receive a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map the non-serving RAN information to the serving RAN information;

[0432] The second sending unit is configured to send a second mapping query response to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

[0433] As an optional embodiment, when the first network element is the non-service RAN network element, the device further includes:

[0434] The third receiving unit is configured to receive service-oriented RAN information sent by a service-oriented RAN network element.

[0435] As an optional embodiment, when the first network element is the service-oriented RAN network element, the device further includes:

[0436] The fourth receiving unit is configured to receive non-serving RAN information sent by a non-serving RAN network element.

[0437] As an optional embodiment, when the first network element is the service-oriented AMF network element, the device further includes:

[0438] The fifth receiving unit is configured to receive a first handover request sent by a service-oriented RAN network element, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

[0439] As an optional embodiment, when the first network element is the non-service AMF network element, the device further includes:

[0440] The sixth receiving unit is configured to receive a second handover request sent by a non-serving RAN network element, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

[0441] As an optional embodiment, when the first network element is the NRF network element, the device further includes:

[0442] a seventh receiving unit, configured to receive a third mapping query request sent by a non-serving AMF network element, wherein the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information;

[0443] The seventh sending unit is used to send a third mapping query response to the non-service AMF network element, and the third mapping query response carries the mapped non-service RAN information.

[0444] As an optional embodiment, when the first network element is the NRF network element, the device further includes:

[0445] an eighth receiving unit, configured to receive a fourth mapping query request sent by the service-oriented AMF network element, wherein the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information;

[0446] An eighth sending unit is used to send a fourth mapping query response to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

[0447] like Fig. 20 As shown, the embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0448] The first acquisition unit 2001 is configured to acquire the mapped non-service RAN information; wherein the service RAN information is mapped to the non-service RAN information by the first network element;

[0449] The first switching unit 2002 is configured to perform switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

[0450] As an optional embodiment, the first network element is any one of the following:

[0451] NRF network element with network storage function;

[0452] Service-oriented RAN network elements;

[0453] Non-service RAN network elements;

[0454] Service-oriented access and mobility management function AMF network element;

[0455] Non-service AMF network element;

[0456] Protocol data unit session anchor PSA network element.

[0457] like Fig.21 As shown, the embodiment of the present application further provides a switching device between a service-oriented RAN and a non-service-oriented RAN, including:

[0458] The second acquisition unit 2101 is configured to acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information;

[0459] The second switching unit 2102 is configured to perform switching from the non-service RAN to the service RAN according to the service RAN information obtained by mapping.

[0460] As an optional embodiment, the first network element is any one of the following:

[0461] NRF network element with network storage function;

[0462] Service-oriented RAN network elements;

[0463] Non-service RAN network elements;

[0464] Service-oriented access and mobility management function AMF network element;

[0465] Non-service AMF network element;

[0466] Protocol data unit session anchor PSA network element.

[0467] In the embodiment of the present application, a mapping relationship between the serviced RAN and the non-serviced RAN is stored at the first network element, and the first network element performs mapping between the serviced RAN information and the non-serviced RAN information, so that the non-serviced RAN network element or the serviced RAN network element performs switching between the serviced RAN and the non-serviced RAN, thereby solving the switching problem between the serviced RAN and the non-serviced RAN, avoiding the problem of communication interruption, and improving user experience.

[0468] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0469] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0470] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0471] The embodiment of the present application also provides a processor-readable storage medium, the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to perform the various steps in the method embodiment described above. The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0472] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0473] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0474] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0475] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0476] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for switching between a service-oriented RAN and a non-service-oriented RAN, characterized in that: Applied to a first network element, the method includes: The first network element maps the serviced RAN information to the non-serviced RAN information according to the mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping; or, The first network element maps the non-service RAN information to the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs switching from the non-service RAN to the service RAN according to the service RAN information obtained by the mapping.

2. The method according to claim 1, characterized in that The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

3. The method according to claim 2, characterized in that In the case where the first network element is the NRF network element or the PSA network element, the method further includes: receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information; A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

4. The method according to claim 2, characterized in that: In the case where the first network element is the NRF network element or the PSA network element, the method further includes: receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information; A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

5. The method according to claim 2, characterized in that: In the case where the first network element is the non-service RAN network element, the method further includes: The non-service-oriented RAN network element receives the service-oriented RAN information sent by the service-oriented RAN network element.

6. The method according to claim 2, characterized in that In the case where the first network element is the service-oriented RAN network element, the method further includes: The service-oriented RAN network element receives the non-service-oriented RAN information sent by the non-service-oriented RAN network element.

7. The method according to claim 2, characterized in that In the case where the first network element is the service-oriented AMF network element, the method further includes: A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

8. The method according to claim 2, characterized in that: In the case where the first network element is the non-serviced AMF network element, the method further includes: A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

9. The method according to claim 2, characterized in that: In the case where the first network element is the NRF network element, the method further includes: receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information; A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

10. The method according to claim 2, characterized in that In the case where the first network element is the NRF network element, the method further includes: receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information; A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

11. A method for switching between a service-oriented RAN and a non-service-oriented RAN, characterized in that: Applied to a non-service RAN network element, the method comprises: The non-service RAN network element obtains the mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information; The non-service RAN network element performs switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

12. The method according to claim 11, characterized in that The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

13. A method for switching between a service-oriented RAN and a non-service-oriented RAN, characterized in that: Applied to a service-oriented RAN network element, the method includes: The service-oriented RAN network element obtains the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information; The service-oriented RAN network element performs switching from the non-service-oriented RAN to the service-oriented RAN according to the service-oriented RAN information obtained by mapping.

14. The method according to claim 13, characterized in that The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

15. A first network element, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: According to the mapping relationship between the serviced RAN and the non-serviced RAN, the serviced RAN information is mapped into the non-serviced RAN information, and the non-serviced RAN network element performs the handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping; or, According to the mapping relationship between the non-service RAN and the service RAN, the non-service RAN information is mapped to the service RAN information, and the service RAN network element performs the switching from the non-service RAN to the service RAN according to the mapped service RAN information.

16. The network element according to claim 15, characterized in that: The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

17. The network element according to claim 16, characterized in that: In a case where the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations: receiving a first mapping query request sent by a service-oriented RAN network element, where the first mapping query request is used to request an NRF network element or a PSA network element to map service-oriented RAN information to non-service-oriented RAN information; A first mapping query response is sent to the serving RAN network element, where the first mapping query response carries the mapped non-serving RAN information.

18. The network element according to claim 16, characterized in that: In a case where the first network element is the NRF network element or the PSA network element, the processor is further configured to read the computer program in the memory and perform the following operations: receiving a second mapping query request sent by a non-serving RAN network element, where the second mapping query request is used to request an NRF network element or a PSA network element to map non-serving RAN information to serving RAN information; A second mapping query response is sent to the non-serving RAN network element, where the second mapping query response carries the mapped serving RAN information.

19. The network element according to claim 16, characterized in that: In a case where the first network element is the non-service RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations: Receive service-oriented RAN information sent by the service-oriented RAN network element.

20. The network element according to claim 16, characterized in that: In a case where the first network element is the service-oriented RAN network element, the processor is further configured to read the computer program in the memory and perform the following operations: Receive non-service RAN information sent by the non-service RAN network element.

21. The network element according to claim 16, characterized in that: In a case where the first network element is the service-oriented AMF network element, the processor is further configured to read the computer program in the memory and perform the following operations: A first handover request sent by a service-oriented RAN network element is received, where the first handover request carries a handover indication from the service-oriented RAN to the non-service-oriented RAN.

22. The network element according to claim 16, characterized in that: In a case where the first network element is the non-serviced AMF network element, the processor is further configured to read the computer program in the memory and perform the following operations: A second handover request sent by a non-serving RAN network element is received, where the second handover request carries a handover indication from the non-serving RAN to the serving RAN.

23. The network element according to claim 16, characterized in that: In the case where the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations: receiving a third mapping query request sent by a non-serving AMF network element, where the third mapping query request is used to request the NRF network element to map the serviced RAN information to the non-serving RAN information; A third mapping query response is sent to the non-serviced AMF network element, where the third mapping query response carries the mapped non-serviced RAN information.

24. The network element according to claim 16, characterized in that: In the case where the first network element is the NRF network element, the processor is further configured to read the computer program in the memory and perform the following operations: receiving a fourth mapping query request sent by the service-oriented AMF network element, where the fourth mapping query request is used to request the NRF network element to map the non-service-oriented RAN information to the service-oriented RAN information; A fourth mapping query response is sent to the service-oriented AMF network element, where the fourth mapping query response carries the mapped service-oriented RAN information.

25. A non-service RAN network element, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Acquire the mapped non-service RAN information; wherein the first network element maps the service RAN information to the non-service RAN information; The switching from the serviced RAN to the non-serviced RAN is performed according to the mapped non-serviced RAN information.

26. The non-service RAN network element according to claim 25, characterized in that: The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

27. A service-oriented RAN network element, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information; The non-service RAN is switched to the service RAN according to the service RAN information obtained by mapping.

28. The service-oriented RAN network element according to claim 27, characterized in that: The first network element is any one of the following: NRF network element with network storage function; Service-oriented RAN network elements; Non-service RAN network elements; Service-oriented access and mobility management function AMF network element; Non-service AMF network element; Protocol data unit session anchor PSA network element.

29. A switching device between a service-oriented RAN and a non-service-oriented RAN, characterized in that: include: a first mapping unit, configured to map the serviced RAN information into the non-serviced RAN information according to a mapping relationship between the serviced RAN and the non-serviced RAN, and the non-serviced RAN network element performs a handover from the serviced RAN to the non-serviced RAN according to the non-serviced RAN information obtained by the mapping; and / or, The second mapping unit is configured to map the non-service RAN information into the service RAN information according to the mapping relationship between the non-service RAN and the service RAN, and the service RAN network element performs the switching from the non-service RAN to the service RAN according to the service RAN information obtained by the mapping.

30. A switching device between a service-oriented RAN and a non-service-oriented RAN, characterized in that: include: A first acquisition unit is used to acquire the mapped non-service RAN information; wherein the service RAN information is mapped to the non-service RAN information by the first network element; The first switching unit is configured to perform switching from the serviced RAN to the non-serviced RAN according to the mapped non-serviced RAN information.

31. A switching device between a service-oriented RAN and a non-service-oriented RAN, characterized in that: include: A second acquisition unit is used to acquire the mapped service-oriented RAN information; wherein the first network element maps the non-service-oriented RAN information to the service-oriented RAN information; The second switching unit is configured to perform switching from the non-service RAN to the service RAN according to the service RAN information obtained by mapping.

32. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of claims 1 to 10, or the computer program is used to cause the processor to execute the method according to claim 11 or 12, or the computer program is used to cause the processor to execute the method according to claim 13 or 14.

Images